Git repos error individually

When getting the list of git repos you get a list of GitRepoResult's which are either ok -> GitRepoInfo or err -> string. An error is not returned unless all of the repos error out. Because chances are in that case something not repo-specific is afoot.
The gui experience is that you get a global error for each erroring repo, but the rest of your repos show up fine. Previously an error would make none of your repos appear.
This breaks service<->gui compatibility across this PR for the git tab.

:no_entry: Error rendering the commits 5db72ca3c43d...d51b4b0c7913 on linux. :mag_right: 23 errored, 1 new, 6 removed, 64 changed

Error in d51b4b0c7913: Chat_Participant_Rekey-Normal-ERROR

Error in 5db72ca3c43d: Devices_Devices_List-Devices-ERROR

Error in d51b4b0c7913: Devices_Devices_List-Devices-ERROR

Error in 5db72ca3c43d: Chat_No_Conversation-normal-ERROR

Error in 5db72ca3c43d: Chat_Input-Normal-ERROR

Error in d51b4b0c7913: Chat_Input-Normal-ERROR

Error in 5db72ca3c43d: Chat_Inbox-You_Rekey_Selected-ERROR

Error in d51b4b0c7913: Chat_Inbox-You_Rekey_Selected-ERROR (view)
Error in 5db72ca3c43d: Chat_Inbox-You_Rekey-ERROR (view)
Error in d51b4b0c7913: Chat_Inbox-You_Rekey-ERROR (view)
Error in 5db72ca3c43d: Chat_Inbox-Selected_Normal-ERROR (view)
Error in 5db72ca3c43d: Chat_Inbox-Selected_Muted-ERROR (view)
Error in 5db72ca3c43d: Chat_Inbox-Part_Rekey_Selected-ERROR (view)
Error in d51b4b0c7913: Chat_Inbox-Part_Rekey_Selected-ERROR (view)
Error in 5db72ca3c43d: Chat_Inbox-Part_Rekey-ERROR (view)
Error in d51b4b0c7913: Chat_Inbox-Part_Rekey-ERROR (view)
Error in 5db72ca3c43d: Chat_Inbox-Normal-ERROR (view)
Error in 5db72ca3c43d: Chat_Inbox-Long_Top-ERROR (view)
Error in d51b4b0c7913: Chat_Inbox-Long_Top-ERROR (view)
Error in 5db72ca3c43d: Chat_Inbox-Long_Bottom-ERROR (view)
Error in d51b4b0c7913: Chat_Inbox-Long_Bottom-ERROR (view)
Error in 5db72ca3c43d: Chat_Inbox-Empty-ERROR (view)
Error in d51b4b0c7913: Chat_Inbox-Empty-ERROR (view)
Added: Chat_No_Conversation-normal (view)
Changed: You_Rekey-Normal (before) (after) (diff)
Changed: Text-Header_Terminal (before) (after) (diff)
Changed: Text-Header_Big_Terminal (before) (after) (diff)
Changed: Text-Body_Wrap_Normal (before) (after) (diff)
Changed: Text-Body_Small_Success_Normal (before) (after) (diff)
Changed: Text-Body_Small_Secondary_Link_Normal (before) (after) (diff)
Changed: Text-Body_Small_Italic_High_Risk (before) (after) (diff)
Changed: Text-Body_Small_Error_Normal (before) (after) (diff)
Changed: Text-Body_Semibold_Normal (before) (after) (diff)
Changed: Text-Body_Semibold_Link_Normal (before) (after) (diff)
Changed: Text-Body_Secondary_Link_High_Risk (before) (after) (diff)
Changed: Text-Body_Normal (before) (after) (diff)
Changed: Text-Body_Announcements (before) (after) (diff)
Changed: Standard_Screen-Success_w_Custom_Notification_Element (before) (after) (diff)
Changed: Standard_Screen-Error (before) (after) (diff)
Changed: Standard_Screen-Back_Button (before) (after) (diff)
Changed: Markdown-Quotes (before) (after) (diff)
Changed: Markdown-Code_block (before) (after) (diff)
Changed: Markdown-Blank_lines (before) (after) (diff)
Changed: List_Item-Small_list_item_with_icon_desktop_only (before) (after) (diff)
Changed: List_Item-Small_list_item_with_button_action (before) (after) (diff)
Changed: List_Item-Small_list_item_with_avatar_40_mobile_only (before) (after) (diff)
Changed: Input-Password_visible_filled (before) (after) (diff)
Changed: Input-Password_filled (before) (after) (diff)
Changed: Input-Multiline_error (before) (after) (diff)
Changed: Input-Multi_Label_Styled (before) (after) (diff)
Changed: Input-Long_Multiline (before) (after) (diff)
Changed: Input-Hint_Multiline_Empty (before) (after) (diff)
Changed: Input-Floating_Label_Multiline_Filled (before) (after) (diff)
Changed: Input-Floating_Label_Multiline_Empty (before) (after) (diff)
Changed: Input-Default_Empty (before) (after) (diff)
Changed: Input-Auto_cap_none (before) (after) (diff)
Changed: Icon-Icon_Icon_Font (before) (after) (diff)
Changed: Colors-white_ffffff (before) (after) (diff)
Changed: Colors-grey_cccccc (before) (after) (diff)
Changed: Colors-green_3_E_8_FAF_3 (before) (after) (diff)
Changed: Colors-green_2_36_b_37_c (before) (after) (diff)
Changed: Colors-blue_5_F_8_FAFD (before) (after) (diff)
Changed: Colors-blue_4_ebf_5_fc (before) (after) (diff)
Changed: Colors-blue_3_60_rgba_168_215_255_0_6 (before) (after) (diff)
Changed: Colors-black_10_rgba_0_0_0_0_10 (before) (after) (diff)
Changed: Colors-black_05_rgba_0_0_0_0_05 (before) (after) (diff)
Changed: Colors-black_000000 (before) (after) (diff)
Changed: Buttons-Secondary_waiting (before) (after) (diff)
Changed: Buttons-Secondary_small_waiting (before) (after) (diff)
Changed: Buttons-Secondary_full_Width_waiting (before) (after) (diff)
Changed: Buttons-Secondary_full_Width (before) (after) (diff)
Changed: Buttons-Secondary_disabled (before) (after) (diff)
Changed: Buttons-Follow_small_waiting (before) (after) (diff)
Changed: Buttons-Danger_small_waiting (before) (after) (diff)
Changed: Buttons-Danger_full_Width (before) (after) (diff)
Changed: Buttons-Danger (before) (after) (diff)
Changed: Avatar-Normal_x_40 (before) (after) (diff)
Changed: Avatar-Normal_x_32 (before) (after) (diff)
Changed: Avatar-Normal_x_24 (before) (after) (diff)
Changed: Avatar-Mutual_Follow_x_80 (before) (after) (diff)
Changed: Avatar-Mutual_Follow_x_64 (before) (after) (diff)
Changed: Avatar-Mutual_Follow_x_48 (before) (after) (diff)
Changed: Avatar-Follows_You_x_80 (before) (after) (diff)
Changed: Avatar-Follows_You_x_176 (before) (after) (diff)
Changed: Avatar-Follows_You_x_112 (before) (after) (diff)
Changed: Avatar-Following_x_176 (before) (after) (diff)
Changed: Avatar-Fallback_x_24 (before) (after) (diff)
Changed: Avatar-Fallback_x_16 (before) (after) (diff)
Removed: Chat_Banner_Invite-Invite (view original)
Removed: Chat_Banner_Info-Info (view original)
Removed: Chat_Banner_Error-Error (view original)
Removed: Chat_Banner_Broken-Broken_Tracker_3 (view original)
Removed: Chat_Banner_Broken-Broken_Tracker_2 (view original)
Removed: Chat_Banner_Broken-Broken_Tracker_1 (view original)

:no_entry: Error rendering the commits e45b61ae8734...47b36e229c49 on linux. :mag_right: 25 errored, 6 new, 35 changed

Error in 47b36e229c49: Chat_Inbox-Normal-ERROR

Error in e45b61ae8734: Devices_Devices_List-Devices-ERROR

Error in 47b36e229c49: Devices_Devices_List-Devices-ERROR

Error in e45b61ae8734: Chat_No_Conversation-normal-ERROR

Error in 47b36e229c49: Chat_No_Conversation-normal-ERROR

Error in e45b61ae8734: Chat_Input-Normal-ERROR

Error in 47b36e229c49: Chat_Input-Normal-ERROR

Error in e45b61ae8734: Chat_Inbox-You_Rekey_Selected-ERROR (view)
Error in 47b36e229c49: Chat_Inbox-You_Rekey_Selected-ERROR (view)
Error in e45b61ae8734: Chat_Inbox-You_Rekey-ERROR (view)
Error in 47b36e229c49: Chat_Inbox-You_Rekey-ERROR (view)
Error in e45b61ae8734: Chat_Inbox-Selected_Normal-ERROR (view)
Error in 47b36e229c49: Chat_Inbox-Selected_Normal-ERROR (view)
Error in e45b61ae8734: Chat_Inbox-Selected_Muted-ERROR (view)
Error in 47b36e229c49: Chat_Inbox-Selected_Muted-ERROR (view)
Error in e45b61ae8734: Chat_Inbox-Part_Rekey_Selected-ERROR (view)
Error in 47b36e229c49: Chat_Inbox-Part_Rekey_Selected-ERROR (view)
Error in e45b61ae8734: Chat_Inbox-Part_Rekey-ERROR (view)
Error in 47b36e229c49: Chat_Inbox-Part_Rekey-ERROR (view)
Error in e45b61ae8734: Chat_Inbox-Long_Top-ERROR (view)
Error in 47b36e229c49: Chat_Inbox-Long_Top-ERROR (view)
Error in e45b61ae8734: Chat_Inbox-Long_Bottom-ERROR (view)
Error in 47b36e229c49: Chat_Inbox-Long_Bottom-ERROR (view)
Error in e45b61ae8734: Chat_Inbox-Empty-ERROR (view)
Error in 47b36e229c49: Chat_Inbox-Empty-ERROR (view)
Added: Chat_Banner_Invite-Invite (view)
Added: Chat_Banner_Info-Info (view)
Added: Chat_Banner_Error-Error (view)
Added: Chat_Banner_Broken-Broken_Tracker_3 (view)
Added: Chat_Banner_Broken-Broken_Tracker_2 (view)
Added: Chat_Banner_Broken-Broken_Tracker_1 (view)
Changed: Text-Header_Terminal (before) (after) (diff)
Changed: Text-Header_Big_Terminal (before) (after) (diff)
Changed: Text-Body_Wrap_Normal (before) (after) (diff)
Changed: Text-Body_Small_Success_Normal (before) (after) (diff)
Changed: Text-Body_Small_Semibold_Italic_Documentation (before) (after) (diff)
Changed: Text-Body_Small_Secondary_Link_Normal (before) (after) (diff)
Changed: Text-Body_Small_Error_Normal (before) (after) (diff)
Changed: Text-Body_Semibold_Normal (before) (after) (diff)
Changed: Text-Body_Semibold_Link_Normal (before) (after) (diff)
Changed: Text-Body_Normal (before) (after) (diff)
Changed: Text-Body_Big_Documentation (before) (after) (diff)
Changed: Standard_Screen-Success_w_Custom_Notification_Element (before) (after) (diff)
Changed: Standard_Screen-Error (before) (after) (diff)
Changed: Standard_Screen-Back_Button (before) (after) (diff)
Changed: Markdown-Quotes (before) (after) (diff)
Changed: Markdown-Code_block (before) (after) (diff)
Changed: Markdown-Blank_lines (before) (after) (diff)
Changed: List_Item-Small_list_item_with_icon_desktop_only (before) (after) (diff)
Changed: List_Item-Small_list_item_with_button_action (before) (after) (diff)
Changed: List_Item-Small_list_item_with_avatar_40_mobile_only (before) (after) (diff)
Changed: Input-Password_visible_filled (before) (after) (diff)
Changed: Input-Password_filled (before) (after) (diff)
Changed: Input-Multiline_error (before) (after) (diff)
Changed: Input-Multi_Label_Styled (before) (after) (diff)
Changed: Input-Long_Multiline (before) (after) (diff)
Changed: Input-Hint_Multiline_Empty (before) (after) (diff)
Changed: Input-Floating_Label_Multiline_Filled (before) (after) (diff)
Changed: Input-Floating_Label_Multiline_Empty (before) (after) (diff)
Changed: Input-Default_Empty (before) (after) (diff)
Changed: Input-Auto_cap_none (before) (after) (diff)
Changed: Icon-Icon_Icon_Font (before) (after) (diff)
Changed: Colors-white_0_rgba_255_255_255_0 (before) (after) (diff)
Changed: Colors-green_3_E_8_FAF_3 (before) (after) (diff)
Changed: Colors-blue_4_ebf_5_fc (before) (after) (diff)
Changed: Colors-black_05_rgba_0_0_0_0_05 (before) (after) (diff)

@keybase/react-hackers this change to shared/actions/git/index.js ok?


[Add-ins] (tutorial) Remove section about adding support page info.

This portion of the tutorial is no longer required, since new(er) version of Yo Office creates the project with SupportUrl already populated in the manifest.

Docs Build status updates of commit 36e2a0a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/add-ins/addin-tutorial.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Adding xcodeproj() attr to force x86 binaries for sim on M1

Summary
This PR adds the opt-in ability to force simulator builds to use --ios_multi_cpus=x86_64 only on Apple Silicon.  The goal is to allow simulator builds that use external dependencies that aren't built for M1 yet to run under rosetta, while maintaining their ability to run on device.
Details
A new boolean attribute was added to xcodeproj() called force_x86_sim_on_apple_silicon that will trigger this behavior.  The rule now injects a user defined build setting into the generated .xcodeproj that will be picked up by the bazel-wrapper.sh script.  To determine if the host architecture is Apple the script uses sysctl looking for cpu branding.  One alternative considered is using uname instead, however uname will report x86 if its parent process is running under rosetta.
The attribute defaults to false which is a no-op, and realistically only needs to be used during the transition to M1 compatible frameworks.

Did you guys try to flip on device deps?
--features apple.arm64_simulator_use_device_deps

If you're feeding apple_framework xcframeworks setting that should automatically set it up to use the device deps on M1 sim. I suspect it might work out of the box depending on what kind of deps you have..

if you just set that in .bazelrc it will only take effect for sim_arm64 only on Bazel 5+

@jerrymarino  you are right, It works for the most part... We have one pre-compiled dependency AzureCommunications that would crash after the arm-to-sim. binary patch. We have some of these dependencies either not publishing xcframework or blocked by this migration  to bump to newer versions with xcframeworks.
We plana to use this workaround for the interim.


WhatIf only works on Subsccription and ResourceGroup Level Deployments

Describe the bug
WhatIf only works on Subsccription and ResourceGroup Level Deployments
To Reproduce
Steps to reproduce the behavior:
Run a template deployment with -whatif switch on either a management group or tenant scoped deployment
Expected behavior
WhatIf would document all changes
Screenshots
If applicable, add screenshots to help explain your problem.
Client
Any
Additional context
I know this is outlined in the docs here: https://docs.microsoft.com/en-us/azure/azure-resource-manager/templates/template-deploy-what-if?tabs=azure-powershell however it would be good to get some clarity iff this functionality is part of the design roadmap as this is something Terraform supports such as deployment of a management group and is table to run terraform plan successfully.
https://www.terraform.io/docs/providers/azurerm/r/management_group.html

Hi @liamfoneill, the What-If backend already supports tenant and MG level deployments now:

https://docs.microsoft.com/en-us/rest/api/resources/deployments/whatifattenantscope
https://docs.microsoft.com/en-us/rest/api/resources/deployments/whatifatmanagementgroupscope

We've updated the Azure CLI and PowerShell modules, and they'll be available soon, see PRs:

https://github.com/Azure/azure-cli/pull/14568
https://github.com/Azure/azure-powershell/pull/12548

Great thanks for letting me know. Will mark this as closed.


GL-S10 and other diy proxies aren't available on the install page anymore

GL-S10 and other diy proxies aren't available on the install page anymore

Slightly off-topic, sorry. Noticed you had requested a photo of the new version of the GL-S10 on an issue in the old repository, so thought I would share here. I am using your web flasher but not sure which button to press to put the GL-S10 v2.1 into flashing mode.

I'm noticing this as well, it seems the advanced/DIY option is gone from the webpage.

Yes, we felt that they did not "fit" well with the aim of the new ready made projects page.
We still build the firmware files, and a better place to have a page for flashing specific devices could potentially be on https://devices.esphome.io

I've put up firmware for both versions of GL-S10 on https://blakadder.github.io/bluetooth-proxies/


TypeError: Cannot read property 'kind' of undefined in 'Object.isIdentifier' during 'getApplicableRefactors'

This issue comes from crash dumps in telemetry. We've tried to de-duplicate issues on a best-effort basis, comparing the sequence of methods called and the command requested while ignoring line numbers.
TypeScript Version Prefix: 2.7.1
VSCode Version 1.19.3
command requested: getApplicableRefactors
hitting sessions: 5469
proportion of all sessions: 0.0204163913496321
stack
TypeError: Cannot read property 'kind' of undefined
    at Object.isIdentifier (tsserver.js:9638:20)
    at Object.isExportsIdentifier (tsserver.js:7262:19)
    at Object.isExportsOrModuleExportsOrAlias (tsserver.js:19987:19)
    at isAtTriggerLocation (tsserver.js:80032:31)
    at isAtTriggerLocation (tsserver.js:80037:44)
    at Object.getAvailableActions (tsserver.js:80009:21)
    at unknown (tsserver.js:77123:128)
    at getIterator (tsserver.js:1733:23)
    at Object.next (tsserver.js:1728:35)
    at Object.arrayFrom (tsserver.js:2267:32)
    at Object.getApplicableRefactors (tsserver.js:77122:23)
    at Object.getApplicableRefactors (tsserver.js:83337:32)
    at IOSession.Session.getApplicableRefactors (tsserver.js:90194:53)
    at Session.handlers.ts.createMapFromTemplate._a.(anonymous function) (tsserver.js:89150:61)
    at unknown (tsserver.js:90393:88)
    at IOSession.Session.executeWithRequestId (tsserver.js:90384:28)
    at IOSession.Session.executeCommand (tsserver.js:90393:33)
    at IOSession.Session.onMessage (tsserver.js:90413:35)
    at Interface.<anonymous> (tsserver.js:91614:27)
    at emitOne (events.js:96:13)
    at Interface.emit (events.js:191:7)
    at Interface._onLine (readline.js:241:10)
    at Interface._normalWrite (readline.js:384:12)
    at Socket.ondata (readline.js:101:10)
    at emitOne (events.js:96:13)
    at Socket.emit (events.js:191:7)
    at readableAddChunk (_stream_readable.js:178:18)
    at Socket.Readable.push (_stream_readable.js:136:10)
    at Pipe.onread (net.js:560:20)

This is in the "Convert to ES6 module" code fix.

VariableDeclaration.initializer is optional and isExportsOrModuleExportsOrAlias doesn't handle undefined.

This issue reproduced in the following context:
TypeScript Version Prefix: 2.7.2
VSCode Version 1.20.1
command requested: getApplicableRefactors
hitting sessions: 996
proportion of all sessions: 0.020447966494898273
stack
TypeError: Cannot read property 'kind' of undefined
    at Object.isIdentifier (tsserver.js:9640:20)
    at Object.isExportsIdentifier (tsserver.js:7264:19)
    at Object.isExportsOrModuleExportsOrAlias (tsserver.js:19989:19)
    at isAtTriggerLocation (tsserver.js:80192:31)
    at isAtTriggerLocation (tsserver.js:80197:44)
    at Object.getAvailableActions (tsserver.js:80169:21)
    at unknown (tsserver.js:77283:128)
    at getIterator (tsserver.js:1734:23)
    at Object.next (tsserver.js:1729:35)
    at Object.arrayFrom (tsserver.js:2268:32)
    at Object.getApplicableRefactors (tsserver.js:77282:23)
    at Object.getApplicableRefactors (tsserver.js:83497:32)
    at IOSession.Session.getApplicableRefactors (tsserver.js:90354:53)
    at Session.handlers.ts.createMapFromTemplate._a.(anonymous function) (tsserver.js:89310:61)
    at unknown (tsserver.js:90553:88)
    at IOSession.Session.executeWithRequestId (tsserver.js:90544:28)
    at IOSession.Session.executeCommand (tsserver.js:90553:33)
    at IOSession.Session.onMessage (tsserver.js:90573:35)
    at Interface.<anonymous> (tsserver.js:91774:27)
    at emitOne (events.js:96:13)
    at Interface.emit (events.js:191:7)
    at Interface._onLine (readline.js:241:10)
    at Interface._normalWrite (readline.js:384:12)
    at Socket.ondata (readline.js:101:10)
    at emitOne (events.js:96:13)
    at Socket.emit (events.js:191:7)
    at readableAddChunk (_stream_readable.js:178:18)
    at Socket.Readable.push (_stream_readable.js:136:10)
    at Pipe.onread (net.js:560:20)


Roll Dart SDK to 2.0.0-dev.8.0

Roll Dart SDK to 2.0.0-dev.8.0
Remove all places where --assert-initializer is passed, as this feature is always-on, and thus not a supported option, in Dart 2: https://github.com/dart-lang/sdk/commit/fa57f54572bb006b4a7e8f9b946285f5498721df

I tried the same roll some times ago and regarding the issue reported I prefered to wait for the support of type parameters in constructors.

Yes, looks like there are a bunch of analysis issues to tackle. Do you have a link to the type parameter issue?

Several issues : dart-lang/sdk#30355, dart-lang/sdk#26392, dart-lang/sdk#26391 ...

Here is a direct link to the analysis issues we are seeing: https://travis-ci.org/flutter/flutter/jobs/306314548

@a14n I'm not sure I understand the relationship between those language feature request and the concrete analysis issues I linked to?

for instance the following code reports 2 issues:
return JSON.encode(new Map<String, double>.fromIterable(
  _results,
  key: (_BenchmarkResult result) => result.name,
  value: (_BenchmarkResult result) => result.value,
));

[hint] A function of type '(_BenchmarkResult) → double' can't be assigned to a variable of type '(dynamic) → double'. (dev/benchmarks/microbenchmarks/lib/common.dart, line 56, col 14)
[hint] A function of type '(_BenchmarkResult) → String' can't be assigned to a variable of type '(dynamic) → String'. (dev/benchmarks/microbenchmarks/lib/common.dart, line 55, col 12)

If the above language features  was implemented we could fix them with
-return JSON.encode(new Map<String, double>.fromIterable(
+return JSON.encode(new Map<String, double>.fromIterable<_BenchmarkResult>(
  _results,
  key: (_BenchmarkResult result) => result.name,
  value: (_BenchmarkResult result) => result.value,
));

But without that we have to do one of the following alternative:

use an unsafe property access (no check on property names by analyzer):
return JSON.encode(new Map<String, double>.fromIterable(
  _results,
-  key: (_BenchmarkResult result) => result.name,
-  value: (_BenchmarkResult result) => result.value,
+  key: (dynamic result) => result.name,
+  value: (dynamic result) => result.value,
));

use a cast (but not allowed by avoid_as lint):
return JSON.encode(new Map<String, double>.fromIterable(
  _results,
-  key: (_BenchmarkResult result) => result.name,
-  value: (_BenchmarkResult result) => result.value,
+  key: (dynamic result) => (result as _BenchmarkResult).name,
+  value: (dynamic result) => (result as _BenchmarkResult).value,
));

use a downcast (but it's really ugly):
return JSON.encode(new Map<String, double>.fromIterable(
  _results,
-  key: (_BenchmarkResult result) => result.name,
-  value: (_BenchmarkResult result) => result.value,
+  key: (dynamic result) { _BenchmarkResult r = result; return r.name; },
+  value: (dynamic result) { _BenchmarkResult r = result; return r.value; },
));

None of the workaround above looks good to me.
There are perhaps other alternatives. @floitschG : any advices ?

cc @leafpetersen @lrhn

For the Map.fromIterable I just proposed a change that would relax the typing so that these functions would work again: https://dart-review.googlesource.com/23440
It's still untested (want to know first, if that's what we want to do).

@floitschG, I imagine your change to Map.fromIterable would take a while to land (as in, not in the timeframe of this PR)?
@Hixie, do any of the above look like reasonable alternatives? Another option is to land with // ignore:s.

A little more context: these warnings are coming from the ongoing plan to remove support for "fuzzy arrows" in 2.0. The main tracking bug for that is https://github.com/dart-lang/sdk/issues/29630.

Two additional ways to work around this:
Via a library of static helper methods, e.g.
// constructors.dart
import 'dart:core' as core;
class Map {
  static core.Map<K, V> fromIterable<K, V, T>(core.Iterable<T> items, {K Function(T) key, V Function(T) value}) {
    var map = <K, V>{};
    for(var item in items) {
      map[key(item)] = value(item);
    }
    return map;
  }
}

// flutter_file.dart
import 'constructors.dart' as constructors;

return JSON.encode(constructors.Map.fromIterable(
  _results,
  key: (_BenchmarkResult result) => result.name,
  value: (_BenchmarkResult result) => result.value,
));

Using Iterable.forEach
var map = <String, double>{}'
_results.forEach((result) => map[result.name] = result.value);
return JSON.encode(map);

I'm going to close this PR for now, as we are not ready to land this. We'll make another attempt soon hopefully.
https://github.com/flutter/flutter/issues/13214 was opened to track the only non-language related change (the removal of --assert-initializer)


Unable to add multiple LCS projects to app

Hi ,
I logged in my personal account and now I am unable to login with customer account. Is there any way we can log off/remove LCS project and re login/re add with different account??

I will add a possibility to logout in the coming release. For now you can delete config file stored in AppData\local\Microsoft\2LCS... folder.


Add a pull request template as a checklist before submitting a PR

When an opening a pull request, this checklist will populate the description to direct developers to resources so we don't have to nag them. Everyone wins!
Closes #6223.

See https://github.com/plone/volto/pull/6366 for a fix for the failing readme linkcheck.

I previously thought that we might include something that could potentially run afoul of Plone community guidelines, but I omitted those items because the incidents of "class assignments" have died down to almost nothing. And here we are in Hacktoberfest 🤮! I attribute that to our documented Contributing guidelines. I think they moved on to the Collective 🤣.


LocalJumpError: no block given (yield)

Describe the problem
Warmup and within helpers do not work
expect { create(:assigned_tag) }.to perform_faster_than.within(0.4).warmup(0.2) { AssignedTag.create }
# => LocalJumpError: no block given (yield)
# => from /bundle/gems/benchmark-perf-0.6.0/lib/benchmark/perf/iteration.rb:25:in `call_times'

Expected behaviour
to warm up CPU and execute the test without errors
Describe your environment

OS version: Mac OS 10.15.6
Ruby version: 2.6.3
RSpec version: 4.0.1
RSpec::Benchmark version: 0.6.0

Hi Daniel 👋
Thanks for using this gem and submitting this issue.
I was initially surprised to learn that this doesn't work as I used it many times before. On a second look, I realised that the documentation is wrong! This should be:
expect { create(:assigned_tag) }.to perform_faster_than { AssignedTag.create }.within(0.4).warmup(0.2)

All the other matcher examples are correct to call within and warmup after the matcher.
Alternatively, the perform_faster_than matcher can accept parameters:
expect { create(:assigned_tag)  }.to perform_faster_than(time: 0.4, warmup: 0.2) { AssignedTag.create }


Workspace - Duplicate expense preview avatar after workspace is deleted

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 9.0.41-2
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Email or phone of affected tester (no customers<EMAIL_ADDRESS>Issue reported by: Applause - Internal Team
Action Performed:

Go to staging.new.expensify.com
Create a new workspace
Submit an expense
Delete the workspace
Go to the workspace chat (now archived)

Expected Result:
The expense preview avatar will remain the same after the workspace is deleted
Actual Result:
The expense preview avatar changes after the workspace is deleted
It changes to stacked avatars with both avatars from the workspace
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

https://github.com/user-attachments/assets/f6a48007-9caa-4421-a435-4eb8ee84e876
View all open jobs on GitHub

Front-end issue, removing DeployBlockerCash label.

Reverting https://github.com/Expensify/App/pull/49403 did not fix the issue, looking further

Pinpointed the offending PR using git bisect: https://github.com/Expensify/App/pull/49172

@grgia would you be able to take a look at this and see if this can be easily fixed or reverted?

It's late for me let's revert https://github.com/Expensify/App/pull/49172 for now

We reverted the problematic PR https://github.com/Expensify/App/pull/49945. Gonna remove the label but keep this open so @grgia can fix this in a followup.

This was solved long back. I was C+ on the revert PR. Can we please assign someone from BZ to make the payment?

@Expensify/bug-zero pinging you here

Sorry friends! Looking now

Payment Summary

@parasharrajat due $250 via manual New Expensify request

If i'm missing anyone, please let me know!

$250 approved for @parasharrajat


quiche: disable giant request/response tests in quic_http_integration_test under TSAN

Signed-off-by: Dan Zhang<EMAIL_ADDRESS>Commit Message: these tests fails under TSAN CI, see #16493

/assign @antoniovicente @snowp


-l compress

hi
when i use ex; ( -l compress ) in the bigining it will show will search for uncompressed only and inverse if i use -l uncompress
just text error or inversed setting?

That is right, is a bug
albertobsd $ ./keyhunt -f test.txt -r ffecfb9cc56f67fac021fabb2bf62624192bface4df87d11153e5c2130ac0000 -l compress
[+] Version 0.1.20210318 K*BSGS
[+] Search uncompress only
[+] Opening file test.txt
[+] Setting search for btc adddress
[+] Allocating memory for 2 elements: 0.00 MB
[+] Initializing bloom filter for 2 elements.
[+] Loading data to the bloomfilter
[+] Bloomfilter completed
[+] Sorting data
[+] 2 values were loaded and sorted
Thread 0 : Setting up base key: ffecfb9cc56f67fac021fabb2bf62624192bface4df87d11153e5c2130ac0000
HIT!! PrivKey: ffecfb9cc56f67fac021fabb2bf62624192bface4df87d11153e5c2130ac52dd
pubkey: 04edff198aec58bcdc434910a8ea7ae8ca7c21c1de31d7fe9872474b5e9ec0c11b89cae684e4053781daa9b59b6d97bce10d2c70160a188b1f999d2aaf84f7eba3
address: 1MEujqv2Zqpu6X9sW8K6Y6EWfq6Kbg82Mg
^C

The program only hit the uncompress.
ffecfb9cc56f67fac021fabb2bf62624192bface4df87d11153e5c2130ac52dd
public address compressed: 15ggL3aMP5gsqSNWfmui1XkvwmNG8q6C5C
public address uncompressed: 1MEujqv2Zqpu6X9sW8K6Y6EWfq6Kbg82Mg

I already solve it, it will be solve in the next commit.
thanks, best regards!

Solved in last commit: https://github.com/albertobsd/keyhunt/commit/519cbfd78ee9f7c5f68b94f642214c932b48061b


[VL] Large timestamp outside of range

Backend
VL (Velox)
Bug description
Timestamps that great then 32767 years without but do not overflow will be outside of range.
Seq(
<PHONE_NUMBER>675l)
).toDF("time")

spark.sql("""
  select from_unixtime(event_timestamp, 'HH') from test
""")

// vanilla: 56577-04-30 00:11:15
// gluten: Timestamp is outside of supported range of [-32767-01-01, 32767-12-31]

It may be because std::chrono::time_point is used in time conversion, which has range limitations.
Spark version
None
Spark configurations
No response
System information
No response
Relevant logs
No response

Seems to be a known issue https://github.com/facebookincubator/velox/pull/10641

Seems to be a known issue facebookincubator/velox#10641

It maybe not same issue, https://github.com/facebookincubator/velox/pull/10641 still use std::chrono. But the expected result is 56577, which std::chrono not supported.

I

Seems to be a known issue facebookincubator/velox#10641

It maybe not same issue, facebookincubator/velox#10641 still use std::chrono. But the expected result is 56577, which std::chrono not supported.

I am trying to remove the dependency on std::chrono to get rid of the limitations.


Make globalstep optional

Now you can sit down and get up by clicking on a chair.
So globalstep becomes optional, which may be useful for the server.
The screenshot was compressed without loss of quality.
A few minor fixes

Thank you for your contribution, this looks very promising.
I will try to review and test this as soon as possible.

Simplified the code a bit more. Tell me if something is wrong.
Very cool mod, by the way. I felt I had to do backport...

@Thomas--S, there was something else, but I will leave it for the future PR.
Changed what you requested. I was glad to help!


macOS: add EventTouchFrame

Hopefully last thing for #249.
This event allows us to do something at the end of a touch frame.  e.g. PanelTouch now uses it to request a redraw after it receives all the touch events for that frame.

Do you mind if I challenge this design a little? Neither AppKit nor Web seems to have anything like it. Usually only one touch event happens at once (either you moved your finger or added/removed one), no?
If you are worried about scheduling frames, multiple requestFrames are collapsed if painting didn’t happen yet.
Can you think of a use-case for this?

Sure, I don’t really like it either.  The Web API sends all touch events for a given frame all at once.  I didn’t know how to send an array of touches in this way, so the current API just sends them individually.  That’s why I added a frame end event.  Maybe I will work on a separate PR that collates them into an array on the Java side.

You mean they group new touch with all the stationary touches from before? even if they didn’t change?

Not stationary touches— there can be multiple “moved” touches per frame.

Oh I see, TouchEvent.changedTouches is a list, and there’s also TouchEvent.touches
I can help with array. I still think we shouldn’t group “by frame” and send them as soon as macOS reports them to us

Does this help? https://github.com/HumbleUI/JWM/blob/382e7626f25f15b797dc693548da33e43501f936/linux/cc/AppX11.cc#L118-L125
To be clear: as soon as touchesBeganWithEvent/touchesMovedWithEvent/etc is received on ObjC side, you’ll produce and report an event to Java side, but that event could have an array of multiple “changed touches” (because of your logic that computes the difference, or maybe because user was very fast/moved multiple fingers) and also an array of “all currently active touches”. At least this is how I see it, let me know if you want it differently

That sounds good to me!  Sorry if “frame” was confusing— I only meant that we should signal concurrent touch movements as macOS reports them.


[Task] added field "planned" #TDB-147

@anjakammer this doesn't make any sense - sprint planning can be completed per group (by a regular user who also doesn't have sprint write permissions), so just setting it on the sprint won't work


Send GsProcess>>_isTerminated before performing a debugger action

Working on some new debugger code, doing a stepOver, got the attached error.  In the GsProcess, the arStack variable was nil. Allen tracked it to primitive 719 which does have some logic for nil'ing that inst var if the process has been terminated.
The likely scenario was the somehow the process had been terminated before the stepOver took place. A recommendation is to do send _isTerminated to the process before any debugger action takes place that would continue the execution.
Need to discuss with @dalehenrich at some point.
20210324 Stack not convertable error.txt

This is fixed in the tools layer, and a process terminating unexpectedly from under the debugger will result in a process terminated pane.

Through quite a few server and Sparkle tools changes to termination, I think this is no longer a problem. Please reopen or re-file if the problem persists.


Add CancellationTokenSource pooling

Saves all cancellation-related allocation overhead in YARP's control.
That is: the linked CTS and its internals - CTS Registrations, CTS CallbackNode and TimerQueueTimer.
We reuse CTSs, but also avoid resetting the underlying timer (CancelAfter) within time buckets to save some TimerQueueTimer allocations and registations with the TimerQueue.
Open questions:

This doesn't really have to be a configurable instance pool - we could save a few instructions by having it be static and hardcoding values
Majority of pooled CTSs will eventually end up on Gen 2, which means any cancellation will result in throwing away objects on Gen 2. Could this be a concern?
What are reasonable defaults? Right now it's using a 2 second precision, which means a request might be canceled after 98 seconds instead of 100. This seems very conservative, but increasing the window also wouldn't give us much.

For the HTTP-HTTP 100B scenario, this gives us:

~1% throughput increase
~5% fewer allocated bytes (4 objects/request)

On 5.0 the difference is bigger since CTS machinery in 6.0 was already improved.
I will look into exact numbers for 5.0 allocations and post profiles here.

cc: @davidfowl @stephentoub

I was under the impression we were only going to do this on .NET 6 once https://github.com/dotnet/runtime/issues/48492 is available.  Not the case?

once dotnet/runtime#48492 is available

For Kestrel, yes.
Yarp doesn't hand the CancellationTokens to user-code, so we can be sure there aren't any leftover registrations on the CTS.

Yarp doesn't hand the CancellationTokens to user-code, so we can be sure there aren't any leftover registrations on the CTS.

What about user provided DelegatingHandlers?

Meeting notes: Please benchmark the simple version that pools CTS's but not timers. See what proportion of the gains we still get.

Perf difference between the approaches is within the margin of error, not justifying the complexity of the original.
Allocations on 5.0.201 and 6.0.100-preview.3.21153.9:

For completeness, I tested it on 6.0.100-preview.4.21208.1 (which includes https://github.com/dotnet/aspnetcore/pull/31466).
We are down to ~0 cancellation allocations/request! 🎉

Closing in favour of https://github.com/MihaZupan/reverse-proxy/commit/6d9d97279ecbdc573276cb58f361a7e8ca103b2b for when we retarget for 6.0.


Fix compound bugs of in-const predicates

ref: https://github.com/StarRocks/starrocks/issues/2450

The first bug is following: we can only create const null column if not eq_null.  Otherwise null be will evaluated to 1/0.
    ColumnPtr evaluate(ExprContext* context, vectorized::Chunk* ptr) override {
        ColumnPtr lhs = _children[0]->evaluate(context, ptr);
        if (ColumnHelper::count_nulls(lhs) == lhs->size()) {
        if (!_eq_null && ColumnHelper::count_nulls(lhs) == lhs->size()) {
            return ColumnHelper::create_const_null_column(lhs->size());
        }

The second bug is related to defect of VectorizedInConstPredicate. It can not handle is_not_in and NULL value simutaneously.  If we evaluate following column

NULL -> true
0 -> true
1 -> true
2 -> true
3 -> false

We may want to construct VectorizedInConstPredicate with _is_not_in = true, eq_null = true( keep NULL and 3 in hash set) But in this way, NULL value can not be handled in right way. According to the following code, NULL value will be evaluated to 0(but we expect to be 1).
        for (int row = 0; row < size; ++row) {
            if (viewer.is_null(row)) {
                if constexpr (equal_null) {
                    builder.append(1);
                } else {
                    builder.append_null();
                }
                continue;
            }
      ....
        if (_is_not_in) {
            for (int i = 0; i < size; i++) {
                output[i] = 1 - output[i];
            }
        }

So to fix the second bug, we don't use _is_not_in = true. We still natural way to construct VectorizedInConstPredicate

run starrocks_clang-format

For https://github.com/StarRocks/starrocks/issues/2455


receiving WRONG_VERSION_NUMBER when pasting API key into extension

using VS Code on a Windows Desktop, using latest version of Coder CLI & server, 0.22.2. the session token input is the one received via the CLI auth flow:

despite the invalid token, Coder continues to attempt the connection. the user is even able to see the directory. here's the log output:
[16:37:14.540] Running script with connection command: "C:\Program Files\Git\usr\bin\ssh.exe" -T -D 52895 "coder-vscode--<username>--first" bash
[16:37:14.558] Terminal shell path: C:\WINDOWS\System32\cmd.exe
[16:37:16.415] > ssh: Could not resolve hostname coder-vscode--<username>--first: Name or service no > t known > ]0;C:\WINDOWS\System32\cmd.exe
[16:37:16.415] Got some output, clearing connection timeout
[16:37:16.429] > The process tried to write to a nonexistent pipe.
[16:37:17.812] "install" terminal command done
[16:37:17.813] Install terminal quit with output: t known
[16:37:17.813] Received install output: t known
[16:37:17.814] Failed to parse remote port from server output
[16:37:17.816] Resolver error: Error: at m.Create (c:\Users\nadendk\.vscode\extensions\ms-vscode-remote.remote-ssh-0.100.0\out\extension.js:1:584145) at t.handleInstallOutput (c:\Users\nadendk\.vscode\extensions\ms-vscode-remote.remote-ssh-0.100.0\out\extension.js:1:582705) at t.tryInstall (c:\Users\nadendk\.vscode\extensions\m

@kylecarbs @bpmct this seems to be a Windows-specific issue, as I confirmed with prospect that their macOS users are not seeing this behavior.

I regularly use windows and have never run into this
Are there any specific steps to reproduce?

@deansheather says this is likely proxy or cert related. I've followed up with the customer to check their proxy & certificate trust settings.

the VS Code proxy settings are the same as the Windows machine, and the Coder certificate is trusted. this is validated because they are able to connect via coder login <https://domain.com>.

It's possible the VS Code extension does not respect HTTP_PROXY. @rodrimaia said he's looking into this today. #78

related #105


MultiSim shrink() fails with uninitialized sim

import sciris as sc
import starsim as ss

sim = ss.Sim(diseases='sis', networks='random')
# sim.init() # required to run

msim = ss.MultiSim(base_sim=sim)
msim.run()
msim.shrink() # error

Also: add a keep kwarg to avoid shrinking/checking user-specified modules.

Closed by #831

But see also #832


SocialSample does not run on IIS Express

SocialSample runs fine when using the web profile in VS or via the command line. When running with the IIS Express profile, the following exception occurs and the sample crashes:
Exception thrown: 'System.DllNotFoundException' in Microsoft.AspNet.Server.Kestrel.dll
Exception thrown: 'Microsoft.AspNet.Server.Kestrel.Networking.UvException' in Microsoft.AspNet.Server.Kestrel.dll
Exception thrown: 'Microsoft.AspNet.Server.Kestrel.Networking.UvException' in mscorlib.dll
Exception thrown: 'System.AggregateException' in mscorlib.dll
Exception thrown: 'System.AggregateException' in Microsoft.AspNet.Server.Kestrel.dll
The thread 0x7e24 has exited with code 0 (0x0).
The thread 0x58b8 has exited with code 0 (0x0).
The thread 0x57a8 has exited with code 0 (0x0).
The thread 0x64d4 has exited with code 0 (0x0).
The thread 0x67c4 has exited with code 0 (0x0).
The thread 0x40a8 has exited with code 0 (0x0).
Exception thrown: 'System.AggregateException' in Microsoft.AspNet.Server.Kestrel.dll
Exception thrown: 'System.Reflection.TargetInvocationException' in mscorlib.dll
Exception thrown: 'System.AggregateException' in mscorlib.dll
Exception thrown: 'System.AggregateException' in mscorlib.dll
Exception thrown: 'System.AggregateException' in mscorlib.dll
Exception thrown: 'System.AggregateException' in mscorlib.dll
Exception thrown: 'System.AggregateException' in Microsoft.Dnx.ApplicationHost.dll
Exception thrown: 'System.Reflection.TargetInvocationException' in mscorlib.dll
Exception thrown: 'System.AggregateException' in mscorlib.dll
Exception thrown: 'System.AggregateException' in Microsoft.Dnx.Host.dll

Need to investigate further to see what the underlying issue is.

Hmm, it appears to work before your changes.

Port conflict in our settings thanks @Tratcher .


[Impeller] Determine what to do with submit batching.

After testing the removal of submit batching, I've found that several benchmarks have improved while several have regressed.
Improved
Advanced Blend
Regressed
Draw Vertices
Additional on local benchmarks on QC devices, I've found that with removal overall rendering is much faster - however we do not have any of these devices on CI. I'm leaning towards removal of submit batching for now.

I am going to remove this feature.


Add support for EXTENDED_SRGB_NONLINEAR_EXT color space

I got crashes on my AMD Radeon Pro 560X because of missing color space
Change-log:

Add support for EXTENDED_SRGB_NONLINEAR_EXT color space
Better error message for wrong color space value

It looks good, but "nonlinear" is written as one word in the Vulkan constant, so I think it should be one in Vulkano as well.

@VictorBulba Thank you for the improvement! Pull Request merged.


writing to single OME-zarr store from multiple processes

We need to be able to read & write a single OME-zarr store or chunked-TIFF store from multiple processes.
The ND image data supported by iohub is chunked and therefore amenable to multiprocessing. But, metadata is in serial format and it is best to write that from a single thread.  The consensus was that iohub should support the creation of an empty dataset to which metadata can be written. Image data can be written afterward.

Can this be closed by https://github.com/czbiohub/iohub/pull/87?


Tweak color of inputs placeholders

Color of input's placeholder should be tweaked, at least on :focus, so user won't get confused thinking placeholder is actual value of input

Implemented in https://github.com/LUI-3/forms-base/commit/842437b469ad3d4aba9a469c40c8cc96aa63c6ec
not in CSS reset yet tho


Fix sdk issue.

We get file not found error when building application which uses kernel header.
Because kernel header files are not installed properly in /usr/include.
This commit fix it.

Thanks!


Updated conserver/cutil.c and conserver/group.c to use snprintf( ) vi…

Updated conserver/cutil.c and conserver/group.c to use snprintf( ) vice sprintf( ) to prevent buffer overflows.
This code change should be carefully checked. I am not normally a coder.

I should note, for the record, this may not be the root cause, but is just my suspicion. Regardless, I do think snprintf( ) calls are an improvement.

I was a beautiful theory while it lasted.  Please feel free to abandon this merge as necessary.


chore: bump yarn version to v4

:tada: This PR is included in version 1.9.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Are the example files generated?

More of a question than issue. I was just wondering if the example files are generated by a script based on the "supported.jl" file? Or how do you automate this?


Detect prefix when document ready

Hi,
Thanks for sharing that plugin!
Here's a small improvement for older browsers. At the moment, every piece of code depending on jQuery.Keyframes needs to wait for the window's load event, as reported in #22, otherwise the browser prefix is not detected.
This PR intends to fix that, by detecting the browser prefix when the DOM is ready, rather than waiting for all assets to load.

Hi @xfra35 , thanks for pull request.
Unless @krazyjakee knows exact reason why is $(window).load preferred, I don't see why we shouldn't accept this.

.ready is really the correct time to start running that code so I have no problem with this but I wonder if there is a way around the wrapping function all-together. As long as the library is called at the end of the <body>, it should have access to everything it needs.
Thanks guys!


Clarification: Did the Bitcode enabled step upload the dsym file automatically

I have a clarification about uploading the dsym file.

Does the bitcode enabled method will upload the dsym file automatically.

If I upload a build in Testflight, then how it will reflect the crash and error report in bugsnag.(i.e) Shall I need to add the bugsnag.notify in all screen.

i.e) I have  setup all configuration and build the app and uploaded in testflight to verify. How can I know about the errors in bugsnag

This is a support question rather than an issue with the library so responding on your existing support query.


Copy soil layer setting csv to input folder + add a BMI MODFLOW coupling notebook

relates #103
:red_circle:  This branch is based on the branch bmi-groundwater-coupling in PR #101, should be merged after that.

If something is not clear, please let me know.

Thanks @SarahAlidoost for the comments and suggestions. I did all of them. Have a look again please and let me know if anything is still required.

If something is not clear, please let me know.

Many thanks @SarahAlidoost for the comments and suggestions. I did all of them and updated the notebook. Have a look again please at the notebook and let me know if anything is still required.

Thanks for addressing the comments. I saw the link to https://flopy.readthedocs.io/en/stable/tutorials.html#modflow-6. I created a model simulation using the code block in https://flopy.readthedocs.io/en/stable/Notebooks/mf6_data_tutorial01.html. However, I couldn't run the coupling notebook with the modflow files because some parameters needed to be adjusted. Can you please add a complete code block to your coupling notebook that creates the same mf6_model_base of your example?

@MostafaGomaa93 can you please merge the main branch to your branch in this pull request? So, the merge conflicts are resolved.

@MostafaGomaa93 can you please merge the main branch to your branch in this pull request? So, the merge conflicts are resolved.

Done


colmapWithCuda: build failure

Describe the bug
Build fails at link time: https://hercules-ci.com/accounts/github/SomeoneSerge/derivations/%2Fnix%2Fstore%2Fsz5rrd5k90incm69risxqx7pkcnb2xih-colmap-3.7.drv/log?via-job=9e2e3781-42da-4528-878e-8c36076d1d55
Steps To Reproduce
nix build -f ./. --arg config '{ cudaSupport = true; allowUnfree = true;  }' -L colmap
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
Notify maintainers
@NixOS/cuda-maintainers @lebastr

Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
output here

Add a :+1: reaction to issues you find important.

but I get C++ ABI unknown reference errors on a few packages.

I suspect colmap needs this: https://github.com/NixOS/nixpkgs/blob/40e221feff8a3cd68c683ef6e5f0bed3c769bace/pkgs/development/libraries/opencv/4.x.nix#L90-L93

Thank you, that's definitely more elegant. I ran it for GCC11 (which is still required by Colmap), it didn't rebuild as much and I didn't need the test patches.
{ pkgs, ... }:

let

    # https://github.com/NixOS/nixpkgs/issues/275113
    colmap = pkgs.colmap.override { mkDerivation = pkgs.cudaPackages_11.backendStdenv.mkDerivation; };
in

    colmap.overrideAttrs (final: prev: rec {

        version = "3.9.1";

        src = pkgs.fetchFromGitHub {
            owner = "colmap";
            repo = "colmap";
            rev = version;
            hash = "sha256-Xb4JOttCMERwPYs5DyGKHw+f9Wik1/rdJQKbgVuygH8=";
        };

        buildInputs = with pkgs; prev.buildInputs ++ [
            flann
            cgal
            gmp
            mpfr
            xorg.libSM
        ];

        nativeBuildInputs = with pkgs; prev.nativeBuildInputs ++ [
            qt5.wrapQtAppsHook
        ];

        # https://github.com/colmap/colmap/issues/1940
        cmakeFlags =
            [
                "-DCUDA_ENABLED=ON"
                "-DCMAKE_CUDA_ARCHITECTURES=86"
            ];
    })

I will read into contributing policy and try to make a PR sometime soon. Do you have any suggestions on cudaCapabilities? I couldn't find this config used anywhere (just the default in cuda-modules/flags.nix), but it seems like it should not be hardcoded right?

I will read into contributing policy and try to make a PR sometime soon. Do you have any suggestions on cudaCapabilities? I couldn't find this config used anywhere (just the default in cuda-modules/flags.nix), but it seems like it should not be hardcoded right?

Correct. Grep nixpkgs for CMAKE_CUDA_ARCHITECTURES, e.g. look at the nix expressions for cudaPackages.saxpy, python3Packages.torch, opencv4, etc

. I ran it for GCC11 (which is still required by Colmap)

Do you mean cudaPackages_11? That uses gcc11 btw.


Bump to 0.4.2

Coverage remained the same at 91.515% when pulling a7f0fd40949f20428d4ccae1c91f367dcf026f71 on release-0.4.2 into 74753f3a5f1058c8a3078a62ef81b206f6adc007 on main.


Interpolator issue

Im trying to run this example... but the second Interpolation sequence never gets called.
let duration = 5.0
let start = 0.2
let end = 0.9
        (start.interpolator(to: end, duration: duration*0.5, function: Easing.type(.sineIn)) { (value) in
            print("\(value)")
            if(value == 0.9){ //reverse
                (end.interpolator(to: start, duration: duration*0.5, function: Easing.type(.backIn)) { (value) in
                    print("\(value)")
                }).run()
            }

        }).run()

I clearly see the "0.9" printed in the console at the end of the animation. Any idea ?
0.834783264660673
0.843072425218097
0.851380677008584
0.859707158731858
0.868051016404468
0.876411403721092
0.884787482400993
0.89458297075934
0.9

The issue is because you're comparing floating point values which doesn't always work as expected due to precision of floats and doubles and small rounding errors that's not apparent when outputting one of these values as a string which uses less precision. This is a common programming concern that's not specific to Swift. You can observe this by outputting the values differently:
let duration = 5.0
let start = 0.2
let end = 0.9

start.interpolator(to: end, duration: duration*0.5, function: Easing.type(.sineIn)) { (value) in
	print("\(value), string: \(String(format: "%.20f", value)), end: \(String(format: "%.20f", end))")
	print(value == end)

	if value == end { //reverse
		end.interpolator(to: start, duration: duration*0.5, function: Easing.type(.backIn)) { (value) in
			print("\(value)")
		}.run()
	}
}.run()

Here's more info:
https://stackoverflow.com/a/43911753
https://stackoverflow.com/questions/43236212/surprising-difference-for-floating-point-arrithmetic-for-double-vs-float
http://www.floating-point-gui.de/errors/comparison/
The solution would be to explicitly provide the type for start and end as floats:
let start: Float = 0.2
let end: Float = 0.9

Also, to help resolve this, I've updated the library to add Float as an interpolatable type which works as expected alongside using the above change.


Changed message displayed on the user save.

This change is

Reviewed 1 of 1 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


FairRescoreBuilder: Queue construction for fair Rescore should be reviewed

int max = Math.min(topDocs.scoreDocs.length, rescoreContext.getWindowSize());
at line 277 in FairRescoreBuilder.java will fail at the following example:
Docs in index =25
WindowSize = 10
k=10
Top 9 docs are nonprotected
We will only have one protected element there
for p= 0.8 and alpha = 0,1 we will need 6 protected elements

However, this can be seen as intended for very large indices.
Idea: for Index-size<400 execute a full index search for protected documents.


Translation - Vietnamese

This is the Vietnamese translation of "IoT-For-Beginners"
### Tasks
- [x] README.md
- [x] translations/README.vi.md
- [x] translations/attributions.vi.md
- [ ] translations/CODE_OF_CONDUCT.vi.md
- [ ] translations/CONTRIBUTING.vi.md
- [ ] translations/SUPPORT.vi.md
- [ ] translations/SECURITY.vi.md
- [ ] translations/TRANSLATIONS.vi.md
- [ ] translations/clean-up.vi.md
- [ ] translations/for-teachers.vi.md
- [ ] translations/hardware.vi.md
- [ ] translations/recommended-learning-model.vi.md

Just create PR #493


fix: subnav scroll going a bit down

Pre-Flight checklist

[ ] Screenshots and design review for any changes that affect layout or styling

[ ] Desktop screenshots
[ ] Mobile width screenshots

[ ] Testing

[ ] Code is tested
[ ] Changes have been manually tested

What are the relevant tickets?
None
What's this PR do?
For mobile, When user clicks any subnav item, on about page or educator page, the smooth scroll do not stop at the start of the section, instead it goes a bit down. This PR fixes this issue.
How should this be manually tested?

Go to about us or educator page on mobile
Open the on-page sub navbar and click on any menu item.
Verify that smooth scroll stops at the beginning of the section

Screenshots (if appropriate)
Before:

After:

@alicewriteswrongs Whoops, I didn't realize you had assigned this to yourself and reviewed it

@gumaerc no worries, I assigned but didn't get to it yet :)

@gumaerc no worries, I assigned but didn't get to it yet :)


Add Ruby 3.0 to CI

jekyll-feed will be included in Fedora 34 which will also use Ruby 3.0
as system Ruby interpreter. This combination is known to work, so it
would make sense to add it to CI.

Both Travis and AppVeyor are in use. The reason for this is unclear for me. I updated only Travis, because it had newer versions of everything. Should also AppVeyor be updated?

Oh, build for Ruby 3.0 failed due to missing rss gem. In Ruby 3.0, it became a bundled gem, thus it needs to be added as a dependency. I will fix that in this pull request. On the other hand, I see that there is some GitHub actions work going on the master branch, does that mean that Travis on its way out?

@oturpe thanks I'm getting the same rss error on GitHub Actions, and yes the plan is to move all our CI to GitHub Actions

Rss gem fix added. Very common problem in Ruby 3.0 migration, because there was no warning in Ruby 2.7. Luckily, easy to fix too.
You can either merge this pull request, or just take the good parts if that fits the plan better.

The solution for the rss problem that went is better than my proposal. Ruby 3.0 is now included in ci, so what I was trying to achieve with this pull request has been achieved. Thank you for your effort!

Thank you @oturpe
@jekyllbot: merge +dev


What is the philosophy behind 'view' primitive

How to use it? A little baffling.

Why don't let it inherit from cpu_memory_t, and act like memory primitive. Seems a lot of case there would be zero-copy.

Hi @4pao,
Sorry for delay with response.
Yeah, view is not the simplest thing in MKL-DNN. One of the reason for that is we developed it with desire to have extendability at a price of loosing simplicity.
Let me try to describe how view works now (though that might be adjusted in future because it is definitely awful now).
View allows you only describes a part of memory (represented by memory descriptor and memory primitive descriptor). The only way to use it is to create view_pd and then either use it directly where memory primitive descriptor is required (e.g. to create a reorder, see example [1]) or query for corresponding memory descriptor (and then use it to create a primitive, see example [2]).
Example [1] based on intelcaffe.
Let's say you want to copy a part of memory into another buffer (and probably change the format).
Then your steps are:

create memory primitive descriptor in_mem_pd and memory primitive in_mem_p for the entire source data
create view primitive descriptor in_submem_pd based on in_mem_pd, initial offsets, and sub-sizes
create memory primitive descriptor out_mem_pd and memory primitive out_mem_p for the output (the logical sizes should much sub-sizes used in step 2, but the format might be arbitrary)
create reorder primitive descriptor reorder_pd based on in_submem_pd and out_mem_pd
create reorder primitive itself based on reorder_pd, in_mem_p, and out_mem_p

Please notice that there is no view primitive. There is only view primitive descriptor. And the reorder uses source memory as input but traverses it according to a view in_submem_pd.
Example [2] based on a hope that this works :).
Let's say you want to perform a convolution on a part of memory you need.
Then your steps are:

create memory primitive descriptor in_mem_pd and memory primitive in_mem_p for the entire source data
create view primitive descriptor in_submem_pd based on in_mem_pd, initial offsets, and sub-sizes
query in_submem_pd for memory descriptor in_submem_d (see mkldnn_query_memory_d in include/mkldnn_types.h)
create convolution descriptor conv_d based on in_submem_d and other parameters
...
n. create a convolution itself based on convolution primitive descriptor (which is based on conv_d), and in_mem_p

Again you pass initial memory, but convolution has to traverse only the part that is described by the view.
Of course there is some redundancy here. In particular view primitive descriptor is very close to a memory primitive descriptor. In fact to some extend:
memory_primitive_desc(view_pd->query(memory_d)) == view_pd

We might want get rid of view primitive descriptor and have clearer API for describing submemory in memory descriptor... In fact one can do that right now if he fully understands how memory descriptor works. Again, view is just a tool that helps to fill memory descriptor correctly.

Oh I see, the second case is enlighten. Use view_pd to create primitive instead use view as an input. And according to code it had something to do with memory's blocking access. Is it non-continues memory supported or in-progress?
We had a case, the Googlenet concat three memory into one and during backward it broke into three. Currently we use concat to copy into single chunk of memory and use view_pd/reorder to copy out three pieces. I wonder if there is any zero-copy chance.

Hi @4pao,

Is it non-continues memory supported or in-progress?

not sure I got the question... memory structure does support non-continuous memory thanks to strides. E.g. if sizes = {16, 6} and strides = {8, 1}, there would be an extra space of 2 elements between the rows. The same is applied to blocked memory: the strides between elements and blocks are controlled by strides[2][ndims] field in memory_desc_t.

I wonder if there is any zero-copy chance.

For forward pass the concat is required. MKL-DNN has a special primitive for that, so you don't need to do it yourself. There is no chance for zero-copy here.
The view might help to avoid explicit split operation, where you need only a part of channels. In theory that should work. I've never seen that on practice though..
IntelCaffe uses view+reorder for explicit extraction (most likely for simplicity).

Hi @emfomenk, thanks for the reply.
Yes, you get the question good. And we seeking zero-copy opportunity is a wrong direction. After carefully analyzed our performance data, we found the problem might related to other issues, so please see the mail I sent to you and the pull request I recently created. Thank you.

Hi @emfomenk, do all primitives guarantee to work on non-contiguous (but plain) memory?

Hi @pinzhenx,
I would expect that all primitives should at least be able to dispatch the reference implementation if strided inputs/outputs are used.
Currently, the following primitives are somewhat optimized for non-contiguous memory on CPU:

reorder: generic jit supports arbitrary strides and blocking
concat and sum: since there is an implementation that is based on reorders
matmul: since it uses inner product underneath that has native support for LD (leading dimension). note, that at least one stride should be 1 though

As I said, other primitives should at least use reference implementation. IMO, binary, as an auxiliary and quite popular primitive, should be optimized for strided input and outputs too. My suggestion will be to open an issue with relevant reproducer and comments on why you need this (for us to prioritize).


Test certain code properties using proptest crate

Feature description
proptest allows to test that certain properties of a code hold for arbitrary inputs, and if a failure is found, automatically finds the minimal test case to reproduce the problem. The minimal test cases found in a crate can then be added as unit tests.
Tests can be run with the cargo test command and if some minimal test cases are found, they will be added to the proptest-regressions directory. To consult the book, click me.
Feature motivation
proptest can be used, for example, to analyze whether a piece of code crashes on some determined inputs, thus it evaluates the robustness of burn crates when erroneous and insecure inputs are passed to APIs, leading to crashes or security vulnerabilities.

proptest is used inside tract, which may be used for some inspiration: https://github.com/sonos/tract/blob/0a83a9823045b08a65d6ed1f1c1ac554bb77d5d0/core/src/ops/change_axes.rs#L1028
I have also found this extension crate test-strategy to be quite useful in conjunction with proptest: https://github.com/frozenlib/test-strategy


https://developer.mozilla.org/en-US/docs/Web/HTML/Element/video

Request type

[ ] Please close this issue, I accidentally submitted it without adding any details
[ ] New documentation
[x] Correction or update

Details

In the Events section, two events mention that they do something with either the currentTime or duration attribute, however neither of these two are described in the attributes section.

Please advise what issues you found so we know what to update. Thank you.

These missing attributes have now been added to the  element page, as well as to . Also reviewed the other pages that are part of documenting these two properties across these elements and HTMLMediaElement:

https://developer.mozilla.org/en-US/docs/Web/API/HTMLMediaElement
https://developer.mozilla.org/en-US/docs/Web/API/HTMLMediaElement/currentTime
https://developer.mozilla.org/en-US/docs/Web/API/HTMLMediaElement/duration
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/video
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/audio


Use list-package-dirs rather than symlinks in the analyzer

Pub is planning on no longer producing package symlinks (issue #15103), but currently the analyzer relies on these symlinks to resolve "package:" imports. Ultimately it would be good for the analyzer to look up packages through barback, but until then it should use "pub list-package-dirs" to find the dependency paths so pub can safely cease producing symlinks.

Is this still required?
Tracking down everything we need for https://github.com/dart-lang/sdk/issues/24112

Nope.  Closing out.  Thanks!


Referenced newsletter in https://keptn.sh/docs/news/

Fixes: #1074

@oleg-nenashev Please take a look.

Thank you!


New extension for migrating data from Oracle to Azure SQL

Extension 'Data Migration for Oracle' for migrating data from Oracle source to Azure SQL.

Oops, looks like a license file was deleted recently. I went ahead and updated it here even though it's unrelated to your extension just to simplify the update...


Use with Rancher Cattle

You mention in the blog that Longhorn is compatible with Swarm and Kubernetes - what about Cattle?

Cattle uses standard Docker volume plugins and will of course be supported.

Any eta on when this is be available?

I'm also curious how this works given the wiki's statement of "swarm mode must be enabled" for a multi-host setup.  Will that continue to be, or is it currently, the only way to get a multi-host volume cluster?

@gaieges Swarm mode is currently only used to provide an overlay network for Longhorn. You can set up any other overlay networking across the hosts for Longhorn as well. The community is more familiar with swarm mode so we tested and showed case of Swarm mode overlay networking in our instruction.

@asthomasdk @machship-mm We're planning to support Rancher and Kubernetes at early second half of year.

Thanks for the info. I understand from the Meetup yesterday that you are re-writing the rancher support to something better - which makes sense.
I would have thought that supporting Rancher natively to start with would make the most sense though - as this puts Rancher in a very strong position. The work you guys are doing with Longhorn is an increasingly important part of the container management stack - and there is already so much you can do out of the box in Rancher. Easily, effectively and safely managing containers and data across hosts is very high on my list.
So you definitely have my vote for Rancher support :;-)

Any developments for Longhorn integration in Rancher?
If not, I'll be making my own Rancher catalog entry to create an infrastructure stack for Longhorn, but if an integration is coming soon I will not bother.

Hi @failedguidedog,
Feel free to try it in Docker way and make a catalog.
We're working on Rancher and Kubernetes integration but haven't had a date set yet. In our plan, it will be more complex than just a catalog because we're planning to use Rancher/Kubernetes to orchestrate the longhorn-engine instances around.

Checking in again here. I realize that you've probably re-focused to only support Rancher 2.0.
It's worth mentioning that everyone else is being left behind who's not comfortable with the Kubernetes transition. Of course I find it also odd that it wasn't initially integrated into Rancher right when it was being developed, but I understand there are many technical hurdles you're overcoming.
To-date, the alpha has not released any information on an automated upgrade path from cattle to Kubernetes, forcing people to rebuild their environments. I of course hope this changes.
Despite all this, I am very grateful to the Rancher Labs team. ❤

We've moved to using Kubernetes for orchestration. Rancher 2.0 will be native since it's based on K8S as well.
We will have more integration with Rancher 2.0 later.


TS-4167: Change default value of proxy.config.http2.active_timeout_in

FreeBSD build successful! See https://ci.trafficserver.apache.org/job/Github-FreeBSD/604/ for details.

Linux build successful! See https://ci.trafficserver.apache.org/job/Github-Linux/500/ for details.

FreeBSD build successful! See https://ci.trafficserver.apache.org/job/Github-FreeBSD/605/ for details.

Linux build successful! See https://ci.trafficserver.apache.org/job/Github-Linux/501/ for details.

Reviewed the change and it looks good.  Also verified that the same value should be used in Http2ClientSession.cc.

FreeBSD build successful! See https://ci.trafficserver.apache.org/job/Github-FreeBSD/606/ for details.

Linux build successful! See https://ci.trafficserver.apache.org/job/Github-Linux/502/ for details.

Looks good to me 👍


[BEAM-12422][no need to review] Testing BEAM-12422 by installing the vendored gRPC to local Maven repository

[BEAM-12422] Removing unnecessary log4j-api dependency
[BEAM-12422] Locally-installing vendored gRPC 1.36.0-0.2

Please add a meaningful description for your change here

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

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] 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.

GitHub Actions Tests Status (on master branch)

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

Run Java PostCommit

Run PostCommit_Java_Dataflow

Run PostCommit_Java_DataflowV2

Run Spark ValidatesRunner

Run SQL Postcommit

Run Java_Examples_Dataflow PreCommit

Run PostCommit_Java_Dataflow

Run Java Precommit

Run Java Precommit

https://ci-beam.apache.org/job/beam_PreCommit_Java_Phrase/3798/testReport/junit/org.apache.beam.runners.flink/PortableStateExecutionTest/testExecution_streaming__false_/
Test Result (2 failures / +1)
org.apache.beam.runners.flink.PortableStateExecutionTest.testExecution[streaming: false]
org.apache.beam.sdk.io.elasticsearch.ElasticsearchIOTest.testSizes

[grpc-default-executor-5] ERROR org.apache.beam.sdk.fn.data.BeamFnDataGrpcMultiplexer - Failed to handle for url: "InProcessServer_46"

org.apache.beam.vendor.grpc.v1p36p0.io.grpc.StatusRuntimeException: CANCELLED: Multiplexer hanging up
	at org.apache.beam.vendor.grpc.v1p36p0.io.grpc.Status.asRuntimeException(Status.java:535)
	at org.apache.beam.vendor.grpc.v1p36p0.io.grpc.stub.ClientCalls$StreamObserverToCallListenerAdapter.onClose(ClientCalls.java:478)
	at org.apache.beam.vendor.grpc.v1p36p0.io.grpc.internal.ClientCallImpl.closeObserver(ClientCallImpl.java:553)
	at org.apache.beam.vendor.grpc.v1p36p0.io.grpc.internal.ClientCallImpl.access$300(ClientCallImpl.java:68)
	at org.apache.beam.vendor.grpc.v1p36p0.io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInternal(ClientCallImpl.java:739)
	at org.apache.beam.vendor.grpc.v1p36p0.io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInContext(ClientCallImpl.java:718)
	at org.apache.beam.vendor.grpc.v1p36p0.io.grpc.internal.ContextRunnable.run(ContextRunnable.java:37)
	at org.apache.beam.vendor.grpc.v1p36p0.io.grpc.internal.SerializingExecutor.run(SerializingExecutor.java:123)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
...
[pool-69-thread-3] ERROR org.apache.beam.fn.harness.control.BeamFnControlClient - Exception while trying to handle InstructionRequest 1
java.lang.NullPointerException
	at org.apache.beam.fn.harness.control.BeamFnControlClient.delegateOnInstructionRequestType(BeamFnControlClient.java:139)
	at org.apache.beam.fn.harness.control.BeamFnControlClient$InboundObserver.lambda$onNext$0(BeamFnControlClient.java:110)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
[grpc-default-executor-3] INFO org.apache.beam.runners.fnexecution.control.FnApiControlClientPoolService - getProcessBundleDescriptor request with id 9-3
Exception in thread "pool-69-thread-3" java.lang.NullPointerException
	at org.apache.beam.fn.harness.control.BeamFnControlClient.sendInstructionResponse(BeamFnControlClient.java:165)
	at org.apache.beam.fn.harness.control.BeamFnControlClient$InboundObserver.lambda$onNext$0(BeamFnControlClient.java:111)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)

Run Java PreCommit

Run Java PostCommit

Run PostCommit_Java_Dataflow

Run PostCommit_Java_DataflowV2

Run Spark ValidatesRunner

Run SQL Postcommit

retest this please

Run Java PostCommit

Run PostCommit_Java_Dataflow

Run PostCommit_Java_DataflowV2

Run SQL Postcommit

Run Java Precommit

Run Python PreCommit

Run Python PreCommit


[android]: adaptive themes not updates on start

Description
I configured unistyles with dark and light theme, but when I change dark mode on my device or android emulator, theme is not changes. Theme only changes if app is opened and then I change dark mode but if I close app and opened then by default will be initialTheme.
Example:
// unistyles.ts

const light = {
  colors: {
    primary: '#673AB7',
    secondary: '#f7f9fc',
    background: '#ffffff',
    text: '#1E1E1E',
  },
} as const;

const dark = {
  colors: {
    primary: '#673AB7',
    secondary: '#1E1E1E',
    background: 'rgb(1, 1, 1)',
    text: '#fcfcfc',
  },
} as const;

type Theme = {
  light: typeof light;
  dark: typeof dark;
};

UnistylesRegistry.addThemes({ light, dark }).addConfig({
  adaptiveThemes: true,
  initialTheme: 'light',
});

//index.js

import './lib/unistyles';
import { AppRegistry } from 'react-native';
import { App } from './src/app';

AppRegistry.registerComponent(appName, () => App);

I use UnistylesRuntime with useColorScheme how as temporary solution for fix this behavior now.
// App.tsx

  const scheme = useColorScheme();

  useEffect(() => {
    UnistylesRuntime.setTheme(scheme === 'dark' ? 'dark' : 'light');
  }, [scheme]);

Steps to reproduce

setup unistyles with adaptive themes
close application (need use cold start)
turn on dark mode on your device
open app (you will see that dark theme is not applied)

Snack or a link to a repository (optional)
No response
Unistyles version
2.0.0
React Native version
0.73.2
Platforms
Android
Engine
Hermes
Architecture
Paper (old)

Do you have such key in the AndroidManifest?
https://reactnativeunistyles.vercel.app/reference/faq/#why-does-my-app-restart-on-theme-change-or-font-size-change-android
Without this key app won't respond to events about light/dark mode.

Do you have such key in the AndroidManifest?
https://reactnativeunistyles.vercel.app/reference/faq/#why-does-my-app-restart-on-theme-change-or-font-size-change-android
Without this key app won't respond to events about light/dark mode.

Yes this key is existed in the AndroidManifest, application is respond to events about light/dark mode.

For fix, it also can use this behavior
import { UnistylesRegistry } from 'react-native-unistyles';
import { Appearance } from 'react-native';

const light = {
  colors: {
    primary: '#673AB7',
    secondary: '#f7f9fc',
    background: '#ffffff',
    text: '#1E1E1E',
  },
} as const;

const dark = {
  colors: {
    primary: '#673AB7',
    secondary: '#1E1E1E',
    background: 'rgb(1, 1, 1)',
    text: '#fcfcfc',
  },
} as const;

type Theme = {
  light: typeof light;
  dark: typeof dark;
};

UnistylesRegistry.addThemes({ light, dark }).addConfig({
  adaptiveThemes: true,
  initialTheme: Appearance.getColorScheme() === 'dark' ? 'dark' : 'light',
});

Why do you set initial theme if you want to use adaptive theme?
You are overriding library automation to set it for you. Just remove it and Unistyles will pick proper theme ☺

Ohh sorry, I just thought it was a required option😅
It's really working right


Missing config options and config options repetition

CI VERSION: V4.1.1
Issue 01
Missing DBPrefix and sessionExpiration config items on env file.
Of course we can add them by ourselves. But its nice these options already included in the env file.
Issue 02
I see CSRF related config items get repeated in env file and also get repeated in app and security config files.
I wonder why same config items get repeated on two places. If its due to breaking changes, Then add deprecated notice on both config files and env file.

I know this is not a bug. But I posted on here because on the forum its hardly get attention.

Yes, the CSRF related config items below are deprecated.
https://github.com/codeigniter4/CodeIgniter4/blob/5c23a60c573835523e4011f1fd1656c5b8638252/env#L42-L48
When do we remove them in the env file?

Need to remove from both env file config/app file. If can't be removed, add 'deprecated' notice comment on both files. So its clear we dont have to mess with them.

Issue 01
Missing DBPrefix and sessionExpiration config items on env file.
Of course we can add them by ourselves. But its nice these options already included in the env file.

We can have those included in the shipped env file.

Issue 02
I see CSRF related config items get repeated in env file and also get repeated in app and security config files.
I wonder why same config items get repeated on two places. If its due to breaking changes, Then add deprecated notice on both config files and env file.

This repetition is caused by Config\App divesting its various configurations to their specific components in separate classes. The App version is being deprecated in favor of this new classes. For the env I do not see removing them as "breaking change" because users have their own .env (note the preceding dot). The only issue I see is when they copy env to .env then add their own values they might wonder why app.CSRFProtection is now missing.
Personally, I would vote to remove the deprecated options in the shipped env to "enforce" users to back away using the deprecated options. Maybe some docs explaining this change would be nice. Any thoughts, @MGatner ?

Yes, absolutely we can do anything to env and should. This should always be our "ideal template": not including ever possible Config value, but some helpful suggestions (and no deprecated items).

On Thu, 1 Apr 2021 at 05:51 MGatner @.***> wrote:

Yes, absolutely we can do anything to env and should. This should
always be our "ideal template": not including ever possible Config value,
but some helpful suggestions (and no deprecated items).
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/codeigniter4/CodeIgniter4/issues/4504#issuecomment-811516228,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABH5O2LYACMUHT3IAZNLD3TGORNNANCNFSM42BBMNJA
.

Could an alternative ViewPath be set in the .env configuration file?
--
Sent from Gmail Mobile

alternative ViewPath

Not as is. app/Config/Paths.php is not a CodeIgniter\Database\Config, because it is loaded pretty much before everything else. I could imagine adding some checks but at some point we need to have a "bottom line".

@zoruz could you do a follow up PR to remove the deprecated items in the env so we can close this ticket?

Is removing CSRFProtection config item from config files and env file was intentional? I'm asking because I still see this config item on test files.

@npwsamarasinghe CSRF moved to the Security Config. We've left the references in App to prevent breaking changes, but all references in the framework should point to Security now. If you see tests that need updating feel free to point them out.

@npwsamarasinghe CSRF moved to the Security Config. We've left the references in App to prevent breaking changes, but all references in the framework should point to Security now. If you see tests that need updating feel free to point them out.

Yeah, I get that. But I'm talking specifically about this single config item that is related to CSRF called "CSRFProtection". In previous versions of CI, We can disable CSRF protection with this config item. Now it's removed from config files (app and security) and env file. I wonder this config item removal was a mistake or an intentional change? If this was an intentional change, We can remove that config item from test files as well.

@npwsamarasinghe can you link here the commit hash that removed that config item? We may need to check that.

@npwsamarasinghe can you link here the commit hash that removed that config item? We may need to check that.

Sorry, Please forget about it. It was a misunderstanding.


Add a template for manual configuration of avalanchego.service file

The Problem...
People who choose to deploy a validator node manually need to set up a ".service" file to allow the node to run in the background of the server and not from the terminal directly. This would not be a problem, except that in the official documentation there is no template or example anywhere that gives you a main idea of how to configure said .service file.
The Solution
The ideal solution would be to add a template in a section of the official avalanche documentation like this:
[Unit]
Description=Avalanche Node service
After=network.target

[Service]
User='YourUserHere'
Group='YourUserHere'
Restart=always
PrivateTmp=true
TimeoutStopSec=60s
TimeoutStartSec=10s
StartLimitInterval=120s
StartLimitBurst=5
WorkingDirectory=/usr/local/bin/avalanchego
ExecStart=/usr/local/bin/avalanchego/./avalanchego \
   --network-id=fuji   <---Delete this entire line (including this warning itself) if you want to start the node on mainnet---

[Install]
WantedBy=multi-user.target

With a basic configuration that allows you to start running the node from the background and thus start the synchronization process.

https://github.com/ava-labs/avalanche-docs/pull/1502


Updated error handling in ifw_c_lib

I updated the error handling and a few other things for the InflowWind c-bindings library interface.
Also rearranged the source code, and moved the regression tests to where they belong.
A few other details:

Copyright is NREL since it was written while employed at NREL
added try except logic as needed
removed compile instructions (those are in readthedocs)
removed input files from the source directories -- these go in r-test
setup python regression testing and InflowWind_Driver regression test (same test, but python to ifw_c vs. fortran).  results are nearly identical
cleaned up notes in the code and adjusted formatting as needed
fixed a few missing error handling pieces (Calc_C and End_C only passed back single character of start of message)
other stuff that I don't remember
Updated CMake
Added VS Solution
Removed archive directory -- we don't keep such things (that's what Git history is for)

I just noticed this in the description
Added VS Solution

but I dont see it in the files changes.

Hmm.... Maybe I forgot to commit the VS solution.  I'll check the other computer and see if I have it there uncommitted...


CVE-2020-7788

https://github.com/advisories/GHSA-qqgx-2p2h-9c37
Due to security vulnerability, the package should either be updated or deprecated.
Furthermore, package should be unfrozen as npm is no longer reliant on config-chain.

I've made a package clone https://www.npmjs.com/package/configuration-chain


50copyHDD.sh is missing from 1.7.1, should be calling blitz.copychain.sh instead

98repairBlockchain.sh calls 50copyHDD.sh in several places.  It should instead be calling blitz.copychain.sh
I don't think I have permissions to do a PR, so putting it here so someone can create it.

Thanks for the report and you could open a PR, but this is fixed in dev.


Add: Kaichun Wu

Company
Kaichun Wu
Description
No current
Link
https://www1.coe.neu.edu/~wukaichun
Location
Seattle,WA
This entry was submitted by the form on the site

This isn't an apprenticeship. Looks like a portfolio.


Fix infinite loop due to rules D207 & W605

Closes #3522
Issue addressed
Given the following example case:
class A:
    """
\ a
    """

With the config:
select = [
  "D207", # bad docstring indentation
  "W605", # invalid escape sequence
]

Those two rules clash when autofixing, creating an infinite loop:

W605 schedules an insertion of a \ at column 0
D207 schedules an insertion of .... (four spaces) at column 0
End result: \ a -> \ +   + \ a -> \    \ a
GOTO 1

Solution
The culprit is the fairly simplistic way that "fix overlaps" are calculated.

Firstly, add an explicit ordering of the rules so that they are applied
in an order that doesn't break the intent (i.e. FIRST indent, THEN fix
the escape sequence.
For future, similar clashes: make W605 insert the second \ AFTER the
first one, rather than BEFORE. This marks one more character in the code
as "dirty", postponing other fixes in that same column for the next
autofix iteration.

Test plan

[ ] Add a new test covering this pathological case. (TODO: how?)
[x] Test manually that the above example now gets fixed correctly.

I would like to add a test that tests the interplay between these two rules, but not sure where to put it?

I would like to add a test that tests the interplay between these two rules, but not sure where to put it?

Hmm, yeah, there's not a natural place for this since it cuts across categories. But, the best I can think of is a dedicated test in crates/ruff/src/rules/ruff/mod.rs!

Hmm, yeah, there's not a natural place for this since it cuts across categories. But, the best I can think of is a dedicated test in crates/ruff/src/rules/ruff/mod.rs!

I gave it a shot, but couldn't quite think of an elegant way of testing it without pulling in half the world or reimplementing the rules in the test, which kinda defeats the purpose. My Rust skills are not great, I'm contributing to get better though :)
Anyway, gave up on the test for now! My intuition says that for nice testability it should be easier to compose the rules, but e.g. the indent rule takes the entire Checker object as a param, and checks if the rules are enabled from within the rule body. Itching to refactor that, but then again I'm not confident enough in the codebase to do that, and maybe it kills performance as well?

Not super stoked about the performance hit either... I'm guessing it's the added match case in the rule sorting?

Sounds good. It's possible that the performance hit is noise, I'm surprised by it.

Rock on, thank you! If you're interested in more good issues let me know :)


IE error,script1003 expected ':'  before eval

Do you want to request a feature or report a bug?

What is the current behavior?
If the current behavior is a bug, please provide the steps to reproduce.

What is the expected behavior?
If this is a feature request, what is motivation or use case for changing the behavior?
Please mention other relevant information such as the browser version, Node.js version, webpack version and Operating System.

@float90 I think you forgot to fill out the questions? :-)

It looks like you just deleted our lovely crafted issue template. It was there for good reasons. Please help us solving your issue by answering the questions asked in this template. I'm closing this. Please open a new issue with filled issue template. Also make sure your issue is not a question. Questions should be posted on Stack Overflow.


consumables, but not pretty

as discussed in #101
might be something salvage in here, but probably needs some refactoring.

Thanks! :-D
I merged it & uploaded a new SNAPSHOT release.

A question for @junkdog
Why is there a pom.xml file in https://github.com/libgdx/gdx-pay/tree/master/gdx-pay-android-googleplay?
Is that needed? Maybe we should remove it?

Why is there a pom.xml

ah, yes - remove it; we only used it to simplify our project builds.


Rename azure storage to azs

'spinnaker.azure.enabled' conflicted with the environment variable used for the Azure cloudprovider config. Since azure storage can be used with other providers (like Kubernetes) we want the names to be independent.

@rguthriemsft @scotmoor @duftler @ewiseblatt PTAL
We want to get this in ASAP since it'll be a breaking change for anyone that starts using Azure storage. See corresponding config PR here: https://github.com/spinnaker/spinnaker/pull/1417

Lgtm

merged and initiated a release
On Thu, Feb 9, 2017 at 9:18 PM, Richard Guthrie<EMAIL_ADDRESS>wrote:

Lgtm
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/spinnaker/front50/pull/190#issuecomment-278839114,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEKkGOiX7wQ_etYIF7B2kT48e6glH6Aiks5ra8jrgaJpZM4L858u
.


React Native compatibility

I'm happy with it. Seems to me that isn't a big problem the needs to use ethers object.

Okay - I agree!


Does not work with angularjs material on mobile

It doesn't work with angularjs material on mobile. The popup closes immediately after first click. If you open this plunker with mobile, you can not select a date.

I'm hitting the same issue.

Anyone got a work around for this? Hitting the same wall.

Anyone got a work around for this? Hitting the same wall.
Works with hours 0-11 but not 12-23.

Works with inline="true" - workaround if you are desperate.

Telling angular material to not intercept clicks did the trick for me
$mdGestureProvider.skipClickHijack();
https://material.angularjs.org/1.1.9/api/service/$mdGestureProvider


Support other propagators in Python Layer

We want to support other propagators besides the X-Ray propagator in the opentelemetry python lambda layer.
These changes allow that, by making the AwsLambdaInstrumentor class

Read from BOTH the HTTP headers (from the Lambda event) and the _X_AMZN_TRACE_ID environment variable
Use the global Propagator, NOT the X-Ray propagator to read out the parent context

Some other changes I made:

We only ever read the _HANDLER environment variable directly, never overwrite it, because AwsLambdaInstrumentor will already wrap that module so when Lambda calls it we can be sure our _instrument method gets called first
Move everything into just otel-instrument so we don't need otel_wrapper.py
Upgrade to OTel Python 1.4.1 Core and 0.23b2 Contrib

Fixes #123

It makes sense @NathanielRN
The only thing I wanted to add is highlight the behaviour when tracing=PassThrough, which should switch off X-Ray propagation, as per the document:

The environment variable will be set and the Context will be sampled only if AWS X-Ray has been enabled for the Lambda function. A user can disable AWS X-Ray for the function if this propagation is not desired.

@michaelhyatt

tracing=PassThrough, which should switch off X-Ray propagation, as per the document:

I didn't see the document mention tracing=PassThrough, did you see it somewhere else? In regards to the part you quoted, I think the document is saying that "switching off X-Ray" will mean that the environment variable is simply not set. Without the environment variable, we won't be able to use the X-Ray propagator anyways, so we can fallback to the user global configured propagator as they would expect 🙂 (Therefore, we don't need any additional configuration flags like tracing=PassThrough because it will just try possible actions after the other until a context is extracted).

I was under the impression that _X_AMZN_TRACE_ID gets populated automatically from the HTTP header X-Amzn-Trace-ID rather than being exposed to the end user to control whether the tracing is switched on or off, but I may be wrong. I just want to make sure that I can use OTEL_PTOPAGATORS=tracecontext and not get any parent.id references when I am sending a request without the externally set traceparent header.
I interpreted the requirement for X-Ray tracing to be switched off as turning the Tracing control in the lambda UI off, i.e. setting tracing=PassThrough (as opposed to Active), but I may be wrong here too. BTW, I believe these two values are from CloudFormation.

I was under the impression that _X_AMZN_TRACE_ID gets populated automatically from the HTTP header X-Amzn-Trace-ID rather than being exposed to the end user to control whether the tracing is switched on or off, but I may be wrong.

Thanks for that prompt! I did some investigation and found out that you're right about this, so I made a PR in the specifications to follow up on this: https://github.com/open-telemetry/opentelemetry-specification/pull/1867

I interpreted the requirement for X-Ray tracing to be switched off as turning the Tracing control in the lambda UI off, i.e. setting tracing=PassThrough (as opposed to Active), but I may be wrong here too.

Yes I agree with you that sounds like the ideal customer experience!

@NathanielRN I am curious if the fix made it into v1.5.0? Maybe not, I can see this one still being a draft.

@michaelhyatt Sorry about that, yes this change hasn't been merged in. Haven't had bandwidth to test this solution even though I think it should work, once it gets tested by publishing a built version of this layer we can merge this change.


Add open collective

Fixes #265
Remove lang URLs
Makes contact form send emails to<EMAIL_ADDRESS>so they can be triaged using MailClark

✅ By submitting this PR, I have verified the following

[x] Checked to see if a similar PR has already been opened 🤔
[x] Reviewed the contributing guidelines 🔍
[x] Added my name to the bottom of the list under the Contributors section in the README.md with a link to my personal website or GitHub profile 👥

@fvntr going to go ahead and force merge since I tested Formspree integration and its been a while since I opened this PR


consentBanner() doesn't work on the latest version

Hi,
in v.3.2.1 the consentBanner() function doesn't work anymore. I'am using the latest version of Nuxt (v3.13.0)
When I downgrade to v3.0.1 it works like intended.
I make use of following versions of packages:

node: v18.19.0
Nuxt: v3.13.0
Vue: 3.4.38

// nuxt.config.ts

cookiebot: {
    blockingMode: 'none',
    culture: 'en',
    autoConsentBanner: false,
    cookieBotId: process.env.COOKIEBOT_ID,
  },

// app.vue

const { consentBanner } = useCookiebot();

consentBanner();

Hi @ambitiondev,
I've had some time to dive deeper into my issue.
Currently I load the Cookiebot banner after an intro animation + timeout. With v3.0.1  that works perfectly. But in the newer version when you do something like a the following code, the Cookiebot banner doesn't load anymore.
// app.vue

<template>
  <CHeader/>

  <CIntro v-if="!introAnimated" @animated="onIntroAnimated"/>

  <div class="{ 'introAnimated' : introAnimated }" class="page-container">
    <NuxtPage/>
  </div>

</template>

<script setup lang="ts">
    const { consentBanner } = useCookiebot();
    const viewport = useViewport();

    const introAnimated = ref(false);

    function onIntroAnimated() {
        introAnimated.value = true;
        setTimeout(onAfterEnter, 1000);
    }

    // there's no intro animation on smaller viewports
    onMounted(() => {
        if (viewport.isLessThan('lg')) {
            introAnimated.value = true;
            setTimeout(onAfterEnter, 1000);
        }
    });

    function onAfterEnter() {
        consentBanner();
    }
</script>

When i place useCookiebot() in the root, everything works like it should be.
The website I'm working on => onlyhumans.com

@pieterjanmaes I think that I have a good grasp as to why your implementation doesn't work (anymore).
In more recent versions of the plugin, we've moved to rendering the script tag for cookiebot on the server side. Hence the only working usage is to call the consentBanner method outside the onMounted hook.
This is to make sure the script gets loaded in time, but from a Nuxt perspective it is also safer to inject scripts on the server side. My best guess in what you want to achieve is that you would like to show the consent banner after the intro animation is finished and not before, because that would look weird, am I right?
Maybe it's an idea to create a fromTo or enter animation for the div of the consent banner, so it gets loaded beforehand, but it doesn't mess up your intro, because it's not directly visible? You probably want to look for a div with the id CybotCookiebotDialogContentWrapper and add such an animation for it when the intro animation is finished.

Hi @pieterjanmaes, as this issue has become a bit stale, I will close it for now. Please feel free to follow up on any questions you have in another issue.