[1.0] ninja: error: '../../../../../../../../../../../../../Volumes/Data', needed by 'obj/src/app/libCHIPDataModel.AttributeAccessInterface.cpp.o', missing and no known rule to make it

Reproduction steps
+ mkdir -p /Users/aelposhi/Library/Developer/Xcode/DerivedData/Darwin-fiarwprtkzhzakagiaewjawagrju/Build/Intermediates.noindex/Matter.build/Debug-maccatalyst/Matter.build
+ export
+ defines=()
+ declare -a defines
+ read -r -a defines
+ declare target_defines=
+ for define in '"${defines[@]}"'
+ case "$define" in
+ continue
+ for define in '"${defines[@]}"'
+ case "$define" in
+ target_defines+=',"CHIP_ADDRESS_RESOLVE_IMPL_INCLUDE_HEADER=<lib/address_resolve/AddressResolve_DefaultImpl.h>"'
+ for define in '"${defines[@]}"'
+ case "$define" in
+ target_defines+=',"DEBUG=1"'
+ for define in '"${defines[@]}"'
+ case "$define" in
+ target_defines+=',"CHIP_ADDRESS_RESOLVE_IMPL_INCLUDE_HEADER=<lib/address_resolve/AddressResolve_DefaultImpl.h>"'
+ for define in '"${defines[@]}"'
+ case "$define" in
+ target_defines+=',"MTR_NEWLY_AVAILABLE="'
+ for define in '"${defines[@]}"'
+ case "$define" in
+ target_defines+=',"MTR_NEWLY_DEPRECATED(message)="'
+ target_defines='["CHIP_ADDRESS_RESOLVE_IMPL_INCLUDE_HEADER=<lib/address_resolve/AddressResolve_DefaultImpl.h>","DEBUG=1","CHIP_ADDRESS_RESOLVE_IMPL_INCLUDE_HEADER=<lib/address_resolve/AddressResolve_DefaultImpl.h>","MTR_NEWLY_AVAILABLE=","MTR_NEWLY_DEPRECATED(message)="]'
+ declare target_arch=
+ declare target_cpu=
+ declare target_cflags=
+ read -r -a archs
+ for arch in '"${archs[@]}"'
+ '[' -z ']' ']'
+ '[' -n '' ']'
+ target_cflags+='"-arch","x86_64"'
+ [[ NO == YES ]]
+ args=('default_configs_cosmetic=[]' 'chip_crypto="boringssl"' 'chip_build_tools=false' 'chip_build_tests=false' 'chip_enable_wifi=false' 'chip_log_message_max_size=4096' 'chip_disable_platform_kvs=true' "target_cpu=\"$target_cpu\"" "target_defines=$target_defines" "target_cflags=[$target_cflags]" "mac_target_arch=\"$target_arch\"" "mac_deployment_target=\"$LLVM_TARGET_TRIPLE_OS_VERSION$LLVM_TARGET_TRIPLE_SUFFIX\"")
+ declare -a args
+ [[ Debug == Debug ]]
+ args+=('is_debug=true')
+ [[ macOS != macOS ]]
+ [[ macOS == macOS ]]
+ args+=('target_os="mac"')
+ cd '/Volumes/Data Disk/Matter/ConnectedHomeIP/connectedhomeip'
++ find_in_ancestors chip_xcode_build_connector_env.sh
+ ENV=
+ [[ -n '' ]]
+ scripts/checkout_submodules.py --shallow --platform darwin
Checking out: nlassert, nlfaultinjection, nlio, nlunit-test, mbedtls, qrcode, pigweed, openthread, nanopb, zap, third_party/pybind11/repo, third_party/jsoncpp/repo, editline, third_party/boringssl/repo/src, open-iot-sdk-storage
+ [[ -z '' ]]
+ env -i PW_ENVSETUP_NO_BANNER=1 PW_ENVSETUP_QUIET=1 bash -c '. scripts/activate.sh'
20221101 11:08:12 WRN Current uname (22.1.0 Darwin Kernel Version 22.1.0: Sun Oct  9 20:15:09 PDT 2022; root:xnu-8792.41.9~2/RELEASE_ARM64_T6000 arm64) does not match Bootstrap uname (22.1.0 Darwin Kernel Version 22.1.0: Sun Oct  9 20:15:09 PDT 2022; root:xnu-8792.41.9~2/RELEASE_ARM64_T6000 arm64), you may need to rerun bootstrap on this system
+ set +ex
20221101 11:08:12 WRN Current uname (22.1.0 Darwin Kernel Version 22.1.0: Sun Oct  9 20:15:09 PDT 2022; root:xnu-8792.41.9~2/RELEASE_ARM64_T6000 arm64) does not match Bootstrap uname (22.1.0 Darwin Kernel Version 22.1.0: Sun Oct  9 20:15:09 PDT 2022; root:xnu-8792.41.9~2/RELEASE_ARM64_T6000 arm64), you may need to rerun bootstrap on this system
+ cd /Users/aelposhi/Library/Developer/Xcode/DerivedData/Darwin-fiarwprtkzhzakagiaewjawagrju/Build/Intermediates.noindex/Matter.build/Debug-maccatalyst/Matter.build
+ gn '--root=/Volumes/Data Disk/Matter/ConnectedHomeIP/connectedhomeip' gen --check out '--args=default_configs_cosmetic=[] chip_crypto="boringssl" chip_build_tools=false chip_build_tests=false chip_enable_wifi=false chip_log_message_max_size=4096 chip_disable_platform_kvs=true target_cpu="" target_defines=["CHIP_ADDRESS_RESOLVE_IMPL_INCLUDE_HEADER=<lib/address_resolve/AddressResolve_DefaultImpl.h>","DEBUG=1","CHIP_ADDRESS_RESOLVE_IMPL_INCLUDE_HEADER=<lib/address_resolve/AddressResolve_DefaultImpl.h>","MTR_NEWLY_AVAILABLE=","MTR_NEWLY_DEPRECATED(message)="] target_cflags=["-arch","x86_64"] mac_target_arch="" mac_deployment_target="ios13.4-macabi" is_debug=true target_os="mac"'
Done. Made 4767 targets from 221 files in 346ms
+ exec ninja -v -C out
ninja: Entering directory `out'
ninja: error: '../../../../../../../../../../../../../Volumes/Data', needed by 'obj/src/app/libCHIPDataModel.AttributeAccessInterface.cpp.o', missing and no known rule to make it

Bug prevalence
Every time
GitHub hash of the SDK that was being used
Drawin
Platform
darwin
Platform Version(s)
1.0
Type
Platform Issue
Anything else?
Hello,
While compiling the IOS mobile app in MACOS M1 I got the above error.
Can anyone advise, please?

Compare:
 gn '--root=/Volumes/Data Disk/Matter/ConnectedHomeIP/connectedhomeip'

and
ninja: error: '../../../../../../../../../../../../../Volumes/Data'

Something is not handling the path with a space in it correctly...  @mspang @andy31415
In the meantime, I expect putting connectedhomeip somewhere that does not have spaces in the path will work.

I think there is a good chance chip scripts in general to not handle spaces in names well. Maintaining such a support is unlikely to gain high priority. I suggest using some symlinks/names without spaces.

I think there is a good chance chip scripts in general to not handle spaces in names well. Maintaining such a support is unlikely to gain high priority. I suggest using some symlinks/names without spaces.

I respect your comment regarding the priority, but I still can't compile the APP.

Our scripts should actually be OK, it's GN that's buggy. The wrong escaping mode is used in two places.
This patch to GN seems to be sufficient
diff --git a/src/gn/ninja_action_target_writer.cc b/src/gn/ninja_action_target_writer.cc
index 60d4204d..01bfb2cd 100644
--- a/src/gn/ninja_action_target_writer.cc
+++ b/src/gn/ninja_action_target_writer.cc
@@ -141,10 +141,16 @@ std::string NinjaActionTargetWriter::WriteRuleDefinition() {
     out_ << std::endl;
   }

+  // The command line requires shell escaping to properly handle filenames
+  // with spaces.
+  PathOutput command_output(path_output_.current_dir(),
+                            settings_->build_settings()->root_path_utf8(),
+                            ESCAPE_NINJA_COMMAND);
+
   out_ << "  command = ";
-  path_output_.WriteFile(out_, settings_->build_settings()->python_path());
+  command_output.WriteFile(out_, settings_->build_settings()->python_path());
   out_ << " ";
-  path_output_.WriteFile(out_, target_->action_values().script());
+  command_output.WriteFile(out_, target_->action_values().script());
   for (const auto& arg : args.list()) {
     out_ << " ";
     SubstitutionWriter::WriteWithNinjaVariables(arg, args_escape_options, out_);
diff --git a/src/gn/path_output.cc b/src/gn/path_output.cc
index d2886d7e..86c92e67 100644
--- a/src/gn/path_output.cc
+++ b/src/gn/path_output.cc
@@ -145,7 +145,7 @@ void PathOutput::WriteSourceRelativeString(std::ostream& out,
   } else {
     // Ninja (and none) escaping can avoid the intermediate string and
     // reprocessing of the inverse_current_dir_.
-    out << inverse_current_dir_;
+    EscapeStringToStream(out, inverse_current_dir_, options_);
     EscapeStringToStream(out, str, options_);
   }
 }

Our scripts should actually be OK, it's GN that's buggy. The wrong escaping mode is used in two places.
This patch to GN seems to be sufficient
diff --git a/src/gn/ninja_action_target_writer.cc b/src/gn/ninja_action_target_writer.cc
index 60d4204d..01bfb2cd 100644
--- a/src/gn/ninja_action_target_writer.cc
+++ b/src/gn/ninja_action_target_writer.cc
@@ -141,10 +141,16 @@ std::string NinjaActionTargetWriter::WriteRuleDefinition() {
     out_ << std::endl;
   }

+  // The command line requires shell escaping to properly handle filenames
+  // with spaces.
+  PathOutput command_output(path_output_.current_dir(),
+                            settings_->build_settings()->root_path_utf8(),
+                            ESCAPE_NINJA_COMMAND);
+
   out_ << "  command = ";
-  path_output_.WriteFile(out_, settings_->build_settings()->python_path());
+  command_output.WriteFile(out_, settings_->build_settings()->python_path());
   out_ << " ";
-  path_output_.WriteFile(out_, target_->action_values().script());
+  command_output.WriteFile(out_, target_->action_values().script());
   for (const auto& arg : args.list()) {
     out_ << " ";
     SubstitutionWriter::WriteWithNinjaVariables(arg, args_escape_options, out_);
diff --git a/src/gn/path_output.cc b/src/gn/path_output.cc
index d2886d7e..86c92e67 100644
--- a/src/gn/path_output.cc
+++ b/src/gn/path_output.cc
@@ -145,7 +145,7 @@ void PathOutput::WriteSourceRelativeString(std::ostream& out,
   } else {
     // Ninja (and none) escaping can avoid the intermediate string and
     // reprocessing of the inverse_current_dir_.
-    out << inverse_current_dir_;
+    EscapeStringToStream(out, inverse_current_dir_, options_);
     EscapeStringToStream(out, str, options_);
   }
 }

Can you advise how to patch it, please?

Our scripts should actually be OK, it's GN that's buggy. The wrong escaping mode is used in two places.
This patch to GN seems to be sufficient
diff --git a/src/gn/ninja_action_target_writer.cc b/src/gn/ninja_action_target_writer.cc
index 60d4204d..01bfb2cd 100644
--- a/src/gn/ninja_action_target_writer.cc
+++ b/src/gn/ninja_action_target_writer.cc
@@ -141,10 +141,16 @@ std::string NinjaActionTargetWriter::WriteRuleDefinition() {
     out_ << std::endl;
   }

+  // The command line requires shell escaping to properly handle filenames
+  // with spaces.
+  PathOutput command_output(path_output_.current_dir(),
+                            settings_->build_settings()->root_path_utf8(),
+                            ESCAPE_NINJA_COMMAND);
+
   out_ << "  command = ";
-  path_output_.WriteFile(out_, settings_->build_settings()->python_path());
+  command_output.WriteFile(out_, settings_->build_settings()->python_path());
   out_ << " ";
-  path_output_.WriteFile(out_, target_->action_values().script());
+  command_output.WriteFile(out_, target_->action_values().script());
   for (const auto& arg : args.list()) {
     out_ << " ";
     SubstitutionWriter::WriteWithNinjaVariables(arg, args_escape_options, out_);
diff --git a/src/gn/path_output.cc b/src/gn/path_output.cc
index d2886d7e..86c92e67 100644
--- a/src/gn/path_output.cc
+++ b/src/gn/path_output.cc
@@ -145,7 +145,7 @@ void PathOutput::WriteSourceRelativeString(std::ostream& out,
   } else {
     // Ninja (and none) escaping can avoid the intermediate string and
     // reprocessing of the inverse_current_dir_.
-    out << inverse_current_dir_;
+    EscapeStringToStream(out, inverse_current_dir_, options_);
     EscapeStringToStream(out, str, options_);
   }
 }

Can you advise how to patch it, please?

You'd have to build from source, described at https://gn.googlesource.com/gn/#getting-a-binary
At least until such fix is landed & a new release cut.

Our scripts should actually be OK, it's GN that's buggy. The wrong escaping mode is used in two places.
This patch to GN seems to be sufficient
diff --git a/src/gn/ninja_action_target_writer.cc b/src/gn/ninja_action_target_writer.cc
index 60d4204d..01bfb2cd 100644
--- a/src/gn/ninja_action_target_writer.cc
+++ b/src/gn/ninja_action_target_writer.cc
@@ -141,10 +141,16 @@ std::string NinjaActionTargetWriter::WriteRuleDefinition() {
     out_ << std::endl;
   }

+  // The command line requires shell escaping to properly handle filenames
+  // with spaces.
+  PathOutput command_output(path_output_.current_dir(),
+                            settings_->build_settings()->root_path_utf8(),
+                            ESCAPE_NINJA_COMMAND);
+
   out_ << "  command = ";
-  path_output_.WriteFile(out_, settings_->build_settings()->python_path());
+  command_output.WriteFile(out_, settings_->build_settings()->python_path());
   out_ << " ";
-  path_output_.WriteFile(out_, target_->action_values().script());
+  command_output.WriteFile(out_, target_->action_values().script());
   for (const auto& arg : args.list()) {
     out_ << " ";
     SubstitutionWriter::WriteWithNinjaVariables(arg, args_escape_options, out_);
diff --git a/src/gn/path_output.cc b/src/gn/path_output.cc
index d2886d7e..86c92e67 100644
--- a/src/gn/path_output.cc
+++ b/src/gn/path_output.cc
@@ -145,7 +145,7 @@ void PathOutput::WriteSourceRelativeString(std::ostream& out,
   } else {
     // Ninja (and none) escaping can avoid the intermediate string and
     // reprocessing of the inverse_current_dir_.
-    out << inverse_current_dir_;
+    EscapeStringToStream(out, inverse_current_dir_, options_);
     EscapeStringToStream(out, str, options_);
   }
 }

Can you advise how to patch it, please?

You'd have to build from source, described at https://gn.googlesource.com/gn/#getting-a-binary
At least until such fix is landed & a new release cut.

I'm compiling the APP using Xcode, as my plan is to compile the IOS app. So can you please advise how I can bypass the GN bug with Xcode?


Alexa could not find devices

I set up node red to use the alexa Home node with my account, etc.
I also set up a simple LED device to turn on/off on the site.
When I use the EchoSim.io to test for devices, Alexa reports back there are no devices.
In my node red alexa node it shows my LED device.
Why does Alexa not recognize my device?

The skill has not been made public yet, so you can not add it to your device in the Alexa Mobile App. Until you add the skill it will not be able to discover your devices

The skill is now live if you want to have another go

Cool, thanks I will check it out this weekend...

-Tony
----- Original Message -----
From: "Ben Hardill"<EMAIL_ADDRESS>To: "hardillb/node-red-alexa-home-skill-web"<EMAIL_ADDRESS>Cc: "tonyc770"<EMAIL_ADDRESS>"Author"<EMAIL_ADDRESS>Sent: Thursday, March 23, 2017 4:14:01 PM
Subject: Re: [hardillb/node-red-alexa-home-skill-web] Alexa could not find devices (#1)
The skill is now live if you want to have another go
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub , or mute the thread .


[OpenAI GPT3] Support GPT4

Extension
https://www.raycast.com/simicvm/openai-gpt3
Description
Please support GPT4, love the extension
Who will benefit from this feature?
me
Anything else?
No response

@simicvm maybe I am missing something but I don't see how to select any model other than these two:

How do you actually use GPT4 when creating a new model?

@dylanjrae  Can you please try to reinstall the extension? This is how it should look like. I can't reproduce the bug.

Reinstalled from store, no luck. I am not sure how the store works, maybe an out of date version is still up there? Is there a way I can stall directly?

@dylanjrae   Actually you might be using a different extension. Your screenshot has a field “Pinned”, while mine doesn’t.

@simicvm Fairly sure it is the same as this repo - when I click "About this extension" from my installed extensions, this is the link I get.
Perhaps this is an out of date version? Here is the full new model screen:

Never mind, I am looking at the wrong extension 🤦♂
Thanks for the help.

@simicvm I see that the old extension was updated to the new one. The problem however is that the new extension doesn't support Azure AI like the old one. Request you to consider adding the support for it. Until then I am forced to use the old extension :(

@simicvm I see that the old extension was updated to the new one. The problem however is that the new extension doesn't support Azure AI like the old one. Request you to consider adding the support for it. Until then I am forced to use the old extension :(

hm, I am not sure that the old version supported Azure AI. You might be using another extension 🤔


ConversationsOperations.get_conversations not supported?

Version
4.4.0b1
Describe the bug
Any call to ConversationsOperations.get_conversations returns HTTP request with status 405 and b'{"message":"The requested resource does not support http method \'GET\'."}'
Expected behavior
I hope it would work and return past conversations. Unfortunately I'm not even it should work as it is missing from the supported API calls listed here.
If supported, some fix. If not, remove the method from the SDK.
Screenshots
https://cl.ly/a1bdaf

@AlmogCohen - What channel are you using?

Microsoft Teams

Teams doesn't support the "get conversations" API.
If you're interested the API is documented in the SDK reference for .NET and Node:
https://docs.microsoft.com/en-us/dotnet/api/microsoft.bot.connector.conversationsextensions.getconversationsasync
https://docs.microsoft.com/en-us/javascript/api/botframework-connector/conversations?view=botbuilder-ts-latest#getconversations-conversationsgetconversationsoptionalparams-
I've raised an issue about the missing REST API documentation: https://github.com/MicrosoftDocs/bot-docs/issues/1179


If any test fails pw-test should return as error

Without that any testing / CI tool wouldn't detect the failed test.

Good point. I will fix this.


Auto-remove docker containers after run

Description
I'm using atom-beautify with beautysh on docker. Every time it executes, a new container is created and not autoremoved. The same container is not being used anymore, so after a few saves I end up with the same number of beautysh containers that times I saved a file.
Steps to Reproduce

Add code to Atom editor (bash in my case)
Run command Atom Beautify: Beautify Editor
A new container is created in Docker every time but they don't remove itself after executing.

Docker have a flag '--rm' you can specify when running the container so it automatically remove itself when the task finishes. Can that be
Checklist
I have:

[X] Tried uninstalling and reinstalling Atom Beautify to ensure it installed properly
[X] Reloaded (or restarted) Atom to ensure it is not a caching issue
[X] Searched through existing Atom Beautify Issues at https://github.com/Glavin001/atom-beautify/issues
so I know this is not a duplicate issue
[ ] Filled out the Input, Expected, and Actual sections above or have edited/removed them in a way that fully describes the issue.
[ ] Generated debugging information by executing Atom Beautify: Help Debug Editor command in Atom and added link for debug.md Gist to this issue

I think the bug is in https://github.com/Glavin001/atom-beautify/blob/bb9428a4fa483fa6ffe958cdcb519b27e00cb770/src/beautifiers/executable.coffee#L451-L460
Looks like other users have experienced this, too: https://twitter.com/lambdafu/status/987116195538141184

I can reproduce:
❯ docker ps --all
CONTAINER ID        IMAGE                                                 COMMAND                  CREATED                  STATUS                      PORTS               NAMES
f64baf9722a0        unibeautify/elm-format                                "elm-format --yes in…"   Less than a second ago   Exited (0) 27 seconds ago                       elated_mccarthy
265d8f5a1ad4        unibeautify/elm-format                                "elm-format --help"      Less than a second ago   Exited (0) 28 seconds ago                       epic_swirles

@RixzZ You can use the following to clean up:
docker ps --all | grep "unibeautify/" | awk '{ print $1 }' | xargs docker rm

Published fix to v0.33.4


Have a depth > 1 in left side navbar toc

Hello,
Despite my many searches, I can't get a proper toc on the left side navbar...
I need some support on this please.
According to this quick documentation I just need to write a toctree in my index.rst file and the output should be a 2-level depth.
I can't have this with the following simple test project, I can see the + button enabled with the collapse_navigation set to False, but I was expecting to see the navbar already expanded at level 2.
Thanks.

index.rst
Welcome to test navbar's documentation!
=======================================

.. toctree::
   :maxdepth: 4
   :caption: Contents:

   test1
   test2

test1.rst
Title 1
=======

Subtitle 1
----------

SubSubtitle 1
.............

SubSubSubtitle 1
################

SubSubSubSubtitle 1
*******************

test2.rst
Title 2
=======

Subtitle 2
----------

SubSubtitle 2
.............

conf.py
html_theme = 'sphinx_rtd_theme'
html_theme_options = {'navigation_depth': 2, 'collapse_navigation': False}

Screen capture

Hi @Djedouas, thank you for taking the time to report this.
There appears to be a bug with the collapse_navigation option. The only effect that is producing is adding the + buttons.
Besides that, setting collapse_navigation to True or False doesn't affect neither appearance or behaviour of the toctree. In both cases:

When in a top level page, the toctree starts collapsed and remains collapsed until you move to a lower level page.
When in a lower level page the toctree expands until reaching its direct children. All other items remain collapsed.

Thanks @nienn for the answer 🙂
I was sure I was missing something... but you confirm that it's not that obvious!
I experience the same behavior as you with collapse_navigation also.

Hey, I'm experiencing the same issue... any updates on this? Thanks!

I also have the same issue.

Besides that, setting collapse_navigation to True or False doesn't affect neither appearance or behaviour of the toctree.

Came here to report this 😢
Related: #455


Fix password argument in command

There is a space missing in the command where the password argument is specified

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Remember to delete this note before submitting your pull request.
For pull requests on 1.15 Features: set Milestone to 1.15 and Base Branch to dev-1.15
For pull requests on Chinese localization, set Base Branch to release-1.14
For pull requests on Korean Localization: set Base Branch to dev-1.14-ko.<latest team milestone>
If you need Help on editing and submitting pull requests, visit:
https://kubernetes.io/docs/contribute/start/#improve-existing-content.
If you need Help on choosing which branch to use, visit:
https://kubernetes.io/docs/contribute/start#choose-which-git-branch-to-use.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

@xyzblocks Please feel free to /reopen when you're ready to continue with feedback.
/close


AdminQuery: API AdminQueries does not exist

Before opening, please confirm:

[X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
v10.15.1
Amplify CLI Version
4.25.0
What operating system are you using?
Mac
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
"No manual changes made"
Amplify Categories
auth, storage, function, hosting
Amplify Commands
Not applicable
Describe the bug
AdminQuery is returning an exception "API AdminQueries does not exist"

amplify status shows the AdminQuery
API Gateway shows the Lambda function linked to it
The lambda execution policy has the required Action "cognito-idp:AdminListGroupsForUser",
CloudWatch has no records on the lambda invocation
I deleted and added the AdminQuery once again

The function that I have to list the groups of a user (listGroupsForUser):
async isQCAuditor(cognitoUsername) {
    if (!cognitoUsername) return false;

    let isQcAuditor = false;
    let nextToken;
    let apiName = "AdminQueries";
    let path = "/listGroupsForUser";
    let myInit = {
      queryStringParameters: {
        username: cognitoUsername,
        token: nextToken
      },
      headers: {
        "Content-Type": "application/json",
        Authorization: `${(await Auth.currentSession())
          .getAccessToken()
          .getJwtToken()}`
      }
    };

    try {
      const { NextToken, ...cognitoGroups } = await API.get(
        apiName,
        path,
        myInit
      );
      nextToken = NextToken;

      for (let group of cognitoGroups.Groups) {
        if (group.GroupName === "qcauditor") {
          isQcAuditor = true;
          break;
        }
      }
    } catch (e) {
      console.log(e);
    }

    return isQcAuditor;
  }
};

The REST endpoint is still returning the same error.
Can you provide some hints to resolve this issue?
Expected behavior
The AdminQueries API should return the list of groups for a user.
Reproduction steps

Add the admin query as documented
Invoke the above-mentioned function (code provided above)
The API fails and the exception gets caught in the catch block and the error shows "API AdminQueries does not exist"

I cannot upgrade the version of amplify cli as of now. This is a working setup and is a part of my production setup that suddenly stopped working.

GraphQL schema(s)

# Put schemas below this line

Log output

# Put your logs below this line

Additional information
No response

I have asked for help in Discord community as well:
https://discord.com/channels/705853757799399426/957602716312543262

Hi @stayingcool,

I deleted and added the AdminQuery once again

How did you delete the Admin Queries API the first time?

Hey @stayingcool :wave: unfortunately I have not been able to reproduce this issue after adding, testing, removing & re-adding AdminQueries, etc. The error you are experiencing: API AdminQueries does not exist is likely returned from the aws-amplify API module. Can you confirm whether the AdminQueries API was successfully added and restricted to a group?

@josefaidt - This issue can be closed.
Please refer:
https://github.com/aws-amplify/amplify-js/issues/9746


docs: add readme for the access-decision-manager-express package

What does this PR do?

Add readme for the access-decision-manager-express package
Why is this important?

Explain how this package works so developers can use it

Awesome.

Thanks a lot for your review and comment!
All your suggestions were implemented now it's ready to start to using it professionally!


Update to latest stable Nginx

Can you update to 1.10.1 to save from forking and maintaining a separate version?

Would be happy to — could you send a PR?

I made a pull request to update this


Support reference count for varlen columns

When creating a new version of a tuple in the update executor, if a column:

is of VARCHAR or VARBINARY type
and is not inlined
and is not updated
then, instead of allocating a copy of the varlen value, we can add to its reference count in the varlen pool.

To support this, we need to

support reference count in the varlen pool
support copy by reference in update executor/project info
(maybe) make garbage collection manager aware of the reference count

Related issues:

#349. After we have inlined varchar, extra check needs to be done in the executor to determine whether we should copy by reference or not.
#395. When primary key is of varlen type, we need to modify its update logic too.

While implementing this feature, I had a feeling that we need to rethink our design of the type system.
In order to copy
@MattPerron @apavlo

Why do you think we need to re-implement our type system?

I think we may need to rewrite the code for varlen type.
Currently, we memcpy the varlen value whenever we call GetValue. I think what we can do is to copy varlen value by reference and make it as our default setting. Whenever we do need a physical copy of it, we can use something like a deep copy method.
In my local branch, I have partially supported this feature. Now the update executor will not memcpy a varlen value when projecting it directly. I will send a PR once I have fully tested it.

As stated in the PR, now we can fully support reference count in varlen type. However, it's kind of hacking the type system to support the shallow copy feature we want.
I have profiled the performance gain from this feature with the YCSB micro-benchmark. Here is the result.
Basically, we get 10x throughput at 10 thread compared to the original varlen pool. The performance is closed to the YCSB using integer instead of string. Compared to our old varlen pool, the new one is way too slow and not scalable.


Add a map waypoint feature

A way-point system would be a really good feature to have especially for new players in my opinion.
It would work the same way that it works in RS3 and you already have a lot of the tools necessary for it; for example how the clue scroll plugin guides you towards where you need to dig.
I don't see any downsides to this idea except the time someone has to spend making it.

I think this is duplicate of https://github.com/runelite/runelite/issues/4496?

I think this is duplicate of #4496?

Yeah you're right, did not find that one while searching.


How to config the TESSDATA_PREFIX environment variable?

I want put eng.traineddata in Documents directory, but always print:

Please make sure the TESSDATA_PREFIX environment variable is set to the parent directory of your "tessdata" directory.

It seems that .traineddata must bu put in the directory named 'tessdata'

It's not working @ZhizhiHu ....
:(

I have a lot of errors with the Tessaract :/

don't put your eng.traineddata in a path contains Chinese
it work for me

I am with the same issue here, any good?

这是一封自动回复邮件。已经收到您的来信，我会尽快回复。


Cleanup the rules list in Rules Configuration of Demo

The Demo section has very useful .eslintrc.json configurator, the only problem it contains deprecated, duplicated, and actual rules.
It would be great:

to remove duplicated (renamed) rules/aliases, e.g. id-blacklist vs. id-denylist.
to split the Demo's Rules section to two sections:

actual rules
deprecated rules

So we could in one click activate just actual rules, not caring about deprecated ones.

We would gladly accept a pull request for these changes. :)

@nzakas , I've have a look on Configuration.jsx which is looks like to be responsible for Demo content:
<RulesConfig
    config={this.props.options.rules}
    ruleNames={this.props.ruleNames}
    docs={this.props.docs}
    onUpdate={this.handleRulesConfigUpdate}
/>

Unfortunately, I don't see where this.props.options.rules is populated and if this list contains a rule state property (e.g. ative/deprecated).

It looks like it’s coming from here:
https://github.com/eslint/website/blob/c7ee67d8deec5c0d347c0f62b94a4ed8f6da72af/src/js/demo/components/App.jsx#L225
Each rule has a meta property that should give you the data you need:
https://github.com/eslint/eslint/blob/44f7de5ee4d934dee540d3d55305126c670f6bfc/lib/rules/no-process-exit.js#L14

Unfortunately, currently I can't allocate enough time to implement the issue in a reasonable time.

No worries. Unfortunately the demo is a pretty low priority for the team right now so it’s unlikely this will get addressed anytime soon. I’ll leave the issue open in case anyone else wants to take this.

I opened a PR that will differentiate the deprecated rules by adding (deprecated) next to the rule.


office-toolbox validation doesn't match sideloading validation for Office Web

My manifest will pass the office-toolbox validation described on this page. However, when I try to sideload the same manifest using Excel Web, it returns "Your add-in manifest is not valid". Note that my manifest also passes the validator built into Visual Stuido. Additionally, when trying to validate against a schema using xmllint, it returns "Schemas parser error : The XML document 'OfficeAppManifestV1_1.xsd' is not a schema document. WXS schema OfficeAppManifestV1_1.xsd failed to compile".
It is frustrating that my manifest can pass two methods of validation but fail when trying to sideload to Excel Web. Additionally, the error "Your addin manifest is not valid" is not helpful in rooting out the problem. Additionally, the documentation is then with regard to which schema should be used from https://github.com/OfficeDev/office-js-docs-pr/tree/master/docs/overview/schemas. I've read the documentation on github and I can't even find a reference to which schema should be used for each type of application.
I've documented this at https://stackoverflow.com/questions/57136595/manifest-file-passes-visual-studio-test-but-fails-when-side-loading-to-office-we but thus far, I haven't received any helpful suggestions. My boss has given me till the end of this week to resolve this, if I can't he is going to make me rewrite the entire function for Google Sheets, which I really don't want to do. Any help would be appreciated.
The following would be helpful.

A single document which specifies all the tags in the manifest, what they are for, are they required or optional, and what order (major issue right now) they must be in.
Common validation of manifest between Visual Studio, office-toolbox, etc.
Documentation on github or this page for which schema should be used for each type of addin.

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

ID: a89c40a2-3e90-a295-7375-6d52ba597808
Version Independent ID: 8cd2f086-5c18-ee17-9ced-ffeba1de0b78
Content: Validate and troubleshoot issues with your manifest - Office Add-ins
Content Source: docs/testing/troubleshoot-manifest.md
Product: non-product-specific
Technology: add-ins
GitHub Login: @o365devx
Microsoft Alias: o365devx

@plmayfield Sorry to hear that you're facing issues with this. The following are some links that I hope are helpful or point you in the right direction.
Office Add-ins XML manifest
How to find the proper order of manifest elements
We'll take a look at the lack of validation consistency across these areas.
Thanks for raising this!

For internal folks, the item tracking validation inconsistency is OC\OPX\Content 3508629

Elizabeth,
Thank you for your response, but I believe the problem is more severe than you think. The schema TaskPaneAppVersionOverridesV1_0.xsd from doesn’t appear to be valid. Below are screen shots of both xmllint and W3C XSD Validation. They both fail to validate the schema file. Note that this has nothing to do with the xml, the schema itself is failing.
An example of the problem is in line 9 of TaskPaneAppVersionOverridesV1_0.xsd. It references the url http://schemas.microsoft.com/office/officeappbasictypes/1.0. When I try to load that url, my browser reports “The resource you are looking for has been removed, had its name changed, or is temporarily unavailable.” If you read the screen shots below both xmllint and W3C are having the same problem. I tried https with the same link to no avail.
OfficeAppBasicTypesV1_0.xsd and OfficeAppBasicTypesV1_0.xsd also do not validate.  Is it possible that this schema problem is why my manifest is being rejected by Excel Web?
My problem is pretty obvious. How do I validate my xml when 2 of the 3 methods to validate (Visual studio and npx with office-toolbox) and the third method, validation against a schema, won’t work as the schema’s are invalid?
Xmllint errors
<EMAIL_ADDRESS>W3C XML Errors
<EMAIL_ADDRESS>Best Regards,
Philip Mayfield
From: Elizabeth Samuel<EMAIL_ADDRESS>Sent: Tuesday, July 23, 2019 11:44 AM
To: OfficeDev/office-js-docs-pr<EMAIL_ADDRESS>Cc: Philip Mayfield<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [OfficeDev/office-js-docs-pr] office-toolbox validation doesn't match sideloading validation for Office Web (#1196)
@plmayfieldhttps://github.com/plmayfield Sorry to hear that you're facing issues with this. The following are some links that I hope are helpful or point you in the right direction.
Office Add-ins XML manifesthttps://docs.microsoft.com/office/dev/add-ins/develop/add-in-manifests?tabs=tabid-1
How to find the proper order of manifest elementshttps://docs.microsoft.com/office/dev/add-ins/develop/manifest-element-ordering
We'll take a look at the lack of validation consistency across these areas.
Thanks for raising this!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/OfficeDev/office-js-docs-pr/issues/1196?email_source=notifications&email_token=AHQXBHNH6AKOYRBNXEQHGH3QA4RLBA5CNFSM4IF425B2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2TRSPY#issuecomment-514267455, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AHQXBHK2PB2QC3Q2QPIUJ7DQA4RLBANCNFSM4IF425BQ.

@plmayfield Thanks for sharing this additional information about the schemas. However, could you include the errors images directly in GitHub? I think you added them by replying to the email but they don't show in the GitHub issue UI.
Also, could you share your manifest (or some version that you can safely share) so that we can also work on getting you unblocked while we get the larger issues resolved?
Thanks.

I posted it at https://github.com/OfficeDev/office-js/issues/635
I may have found two bugs. See ...
https://stackoverflow.com/questions/57169164/showheaders-false-results-in-unexpected-table-range-using-javascript
https://stackoverflow.com/questions/57172497/setsolidcolor-throwing-unexpected-error-in-excel-javascript-on-chart-series
Best Regards,
Philip Mayfield
From: Elizabeth Samuel<EMAIL_ADDRESS>Sent: Wednesday, July 24, 2019 11:56 AM
To: OfficeDev/office-js-docs-pr<EMAIL_ADDRESS>Cc: Philip Mayfield<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [OfficeDev/office-js-docs-pr] office-toolbox validation doesn't match sideloading validation for Office Web (#1196)
@plmayfieldhttps://github.com/plmayfield Thanks for sharing this additional information about the schemas. However, could you include the errors images directly in GitHub? I think you added them by replying to the email but they don't show in the GitHub issue UI.
Also, could you share your manifest (or some version that you can safely share) so that we can also work on getting you unblocked while we get the larger issues resolved?
Thanks.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/OfficeDev/office-js-docs-pr/issues/1196?email_source=notifications&email_token=AHQXBHNHD6QOXOMYOT72U53QBB3SDA5CNFSM4IF425B2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2WZI2Y#issuecomment-514692203, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AHQXBHNGIOT3OETLSJEK3PDQBB3SDANCNFSM4IF425BQ.

@plmayfield Thanks for taking the time to report these bugs and issues. I'll go ahead and close this. Depending on the resolution of the related issues, we'll update the documentation accordingly.
If you have any further questions on this, let us know and we can reopen this issue.
Thanks.


Publish video of the third WCAG 2.2 inspection workshop (Accessible authentication)

What
Publish subtitled video the third WCAG 2.2 workshop with the community focused on Accessible authentication criterion.
Why
Some criterion in WCAG 2.2 can be complicated to test for and teams will need to do more than update to the latest version of Frontend to ensure they meet it.
We want to build a consistent approach to meet WCAG 2.2 so we’re giving the community early opportunity to feed into our work.
Who needs to work on this
TBC
Who needs to review this
GDS YouTube owner
Done when
Post-workshop

[ ] Moved notes into suitable format for sharing
[ ] Prepare transcript and publish video to YouTube
[ ] Shared recording and notes with participants
[ ] Reviewed retro feedback and made changes for next workshop

Here are the files for this work:

Main folder with video files
Video description (to put under the YouTube video)
Unedited video
Video thumbnail

Here's an edited version of the video, with all the workshop stuff removed (and removing the time my internet crashed)

Edited video
VTT file for the edited video (from YouTube auto-transcription)

The captions / transcript still need to be cleaned up, but everything else needed is now in that Google Drive folder!
Main folder with video files

Shared editing doc here.

Currently blocked whilst Nikitas uploads video and captions to YouTube

Sent chasing email


Adding Base Nearest Neighbors model to Main Branch

Cleaned up notebook, added functions, Base Nearest Neighbors model ready to be incorporated into main branch

Going to add Pipfile to gitignore


Remove duplicate admin key in de.json

Remove a duplicate admin translation in the German translation file.
L65 & L671

your right sorry for that ... my fault

Also looks like the English local is missing the admin_subtitle which German does have.


Library doesn't compile for ESP8266

Hello knolleary,
I'm referring to my pull request on this topic.
I think that its, of course, better to check if PROGMEM is defined, instead of just checking if you are on that one platform, like the ESP8266.
The problem is: It doesn't work. PROGMEM seems to be still defined on an ESP8266. Your library would only compile, if I insert #undef PROGMEM in both the header and cpp-files.
Maybe, you could combine the two?
Thanks, l-sch.

So what exact compiler error do you get when compiling? If progmem is defined, it ought to be valid code....

This is the error I'm getting when compiling through the arduino-ide: (Using your lib inside another library called Espanol):
/Volumes/homes/leons/Documents/Arduino/libraries/Espanol/utility/PubSubClient.h:97:46: error: section attribute not allowed for '<anonymous>'
    boolean publish_P(char *, uint8_t PROGMEM *, unsigned int, boolean);
                                              ^

Ok, got to the bottom of it - this wasn't to do with PROGMEM missing, it was a specific way the code was trying to use progmem. I think I've sort it - it compiles cleanly against an ESP8266 target now, but I don't have the hardware to test.
Let me know how you get on.

I just tested the latest release and I am able to compile it with the Arduino IDE v1.6.5.  I was able to upload it to an Adafruit Huzzah and subscribe and publish.. looks good to me.
Thanks for the work.. I use this for all my IOT stuff.. it's great!

@tomn46037 Great! Want to do some more testing for some of the other changes I've made, but will get a new release done today.


[FIX]: Clear timeline

Hi, and by the way thanks for this repository, it's been really helpful to me !
Everything worked fine for me except the "Clean Timeline" part, apparently the targeted aria-attribute is not here anymore.
Here's an updated version targeting a data attribute instead
setInterval (function () {
  $("html, body").animate({ scrollTop: $(document).height() }, "slow");
  $('*[data-tooltip-content="Hidden from Timeline"]').each(function () {
    $(this).parents('.bottomborder').remove();
  });
  var allowed = $('*[data-tooltip-content="Allowed on Timeline"] span').last();
  allowed.click();
  $('.uiContextualLayer').find('li:nth-child(2)').find('a span').click();
  allowed.parents('.bottomborder').remove();
}, 400);

Have a nice day :)

Thanks, @dtnmr! :sparkles:
Can you create a pull request with that?
Thanks!


Fix for the recent tweetdeck update

I wrote a quick fix for the latest tweetdeck update.
Changes:

Usernames are now padded by the profile picture
Pictures in tweets are now in the correct position again.

This is just a quick and dirty fix, but maybe you want to use this.

thank you so much for that ^^ since this is long expired, I'll close it, but I really appreciate your help to make moderndeck better.


Indexing cupy with list of slices fails where tuple of slices works

Cupy doesn't like indexing with lists of slices, but is ok with tuples of slices. Numpy works with either one.
import numpy as np
import cupy as cp
a = cp.ones((2,3))
b = np.ones((2,3))
l = [slice(None), slice(None)]
a[l]  # TypeError: Invalid index type: <type 'list'>
b[l]  # ok
l = (slice(None), slice(None))
a[l] # ok
b[l] # ok

Thank you for reporting the issue. Currently, CuPy automatically triggers basic indexing when the indexing object of __getitem__ is a list. But actually, there are cases in which NumPy triggers basic indexing although the indexing object is a list. So, we should support such cases.
By the way, according to the NumPy document, non-tuple sequence objects should trigger basic indexing. Is it the inconsistency between the document and the implementation?

It seems already resolved.


Account creation issues with unstable indexers

When one or more indexers are having status issues, creating accounts using the following pattern results in loading never stopping and the following logs.
Steps to reproduce:

Create wallet and select zero default accounts.
Create a new account where an indexer is unavailable.

Before scanning, the wallet is then support to first check status on this network (which was not used before). When that fails for some reason, it doesn't appear to continue with the scheduled scan of the account.

This is likely the problem, in the fetch with timeout checking of status, we do this:

And then in the else, we do this:

data is likely undefined here, so it will crash setting the failed network status for the indexer.

There is a try/catch around all of this logic too, so it would likely still work as expected, so maybe this is not the real issue.

Missing await on the persistence of network state, which persist both NetworkStatusStore and StateStore. This could likely cause random issues:


escaped: Use raw strings in example

I think raw strings read easier than trying to count the number of backslashes and that figuring out the Rust escaping vs. the escape output is confusing currently.

thanks


Feature request: Updating components using bound string name

It would be great if you could update components using an object's ID, the component's name as a string, and a string to deserialize data from. It already supports binding names to components.
Also, "update" means creating a new component if it doesn't exist, and then setting the component (calling deserialize). This would be more convenient than having the user do these steps all the time.
The reason I need this feature is for the level loading code in my game. That way I can just override the components with everything in the level file, since objects will vary across levels. It would probably be useful in other cases too, such as synchronizing components/objects across a network.

Good idea. I'll come up with something

Check the pull requests, I wrote something like this but it should probably be refactored.

oh yeah. I'll check it out.Maybe tonight. We'll see.......


Problems when using babel plugins

In current version of istanbul-lib-instrument ("^1.7.3") Instrumenter class method _createClass does not take into account babel plugins which being used in our project. This method only uses hardcoded list of plugins.
In version 3.0.0 this problem was resolved. Please, update version of istanbul-lib-instrument package to 3.0.0 in your package.json.

There's a PR for that now: https://github.com/webpack-contrib/istanbul-instrumenter-loader/pull/100


SAA-1504: Show deleted appointments with isDeleted flag

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

Comparison is base (c12688c) 86.98% compared to head (345a3fc) 86.98%.

Files
Patch %
Lines

...ementapi/service/DailyAppointmentMetricsService.kt
0.00%
0 Missing and 1 partial :warning:

Additional details and impacted files
@@            Coverage Diff            @@
##               main     #764   +/-   ##
=========================================
  Coverage     86.98%   86.98%
- Complexity     3439     3443    +4
=========================================
  Files           358      358
  Lines         11959    11969   +10
  Branches        999      999
=========================================
+ Hits          10402    10411    +9
  Misses         1093     1093
- Partials        464      465    +1

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


Intellisense not working

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version: Code 1.66.1 (8dfae7a5cd50421d10cd99cb873990460525a898, 2022-04-06T14:50:12.141Z)
OS Version: Windows_NT x64 10.0.22000

Steps to Reproduce:

The Intellisense does not seem to be working for any language like C, JavaScript, Python or any other language.
I am using VS Code with WSL2, Ubuntu Distro, to be precise. I tied disabling and enabling the extensions, tried uninstalling and reinstalling the extensions, that does not seem to work as well. It has also started showing syntax errors for correct syntax. When I try and compile the program, it works. I even tried uninstalling and installing VS Code, that also does not seem to work.

What could be a solution to this? This problem seems to be occurring after the recent update.

Same here. I tried reloading window with extensions disabled but it doesn't solve issue... :(
The odd thing is that I can't see log window named 'Typescript language server' in the output panel. (image attatched below)

I have a related issue. Intelisense only works for native Python modules. Anything pip installed doesn't work with intelisense or at best will work if full paths to everything are used. Path variabls are set by Python install, VSCode default install with Python extension. I've sepent days and days trying to get this to work, but no joy.

Every language is different. Also @ColonelGeneral mentions WSL, which makes it special too. Therefore I focus @ColonelGeneral. @Quasar-Kim @hockinsk Please file separate issues and please add a small code example that demonstrates the issue.
@ColonelGeneral Do you have a small code sample that shows the issue? What language mode is the editor in. Do you have anu extension installed for that language? Are you in a remote WSL window?

@aeschli Like this, this is just an example from python.
I do have the extension installed (screenshot attached), and yes, I am in a remote WSL Window


"Open File on Remote" does not open Command Palette to select branch to open file on

GitLens Version: 10.2.2

VSCode Version: 1.47 (and several versions before)
OS Version: OS X Catalina 10.15.5

Description:
In the majority of cases whenever i want to open a file on remote (via tab context menu), a new browser tab is opened, navigating to the file hosted on the remote repository against the branch i am working on. However, in-between this process the VS Code Command Palette does not open at all, which should expose a list of selectable branches.
However, it should instead display the VS Code Command Palette, exposing the list of selectable branch names, which then when selected, opens a new browser tab and then navigates to the remotely hosted file against the selected branch. Sometimes this actually works, but in most cases, the command palette does not open..
Am i missing something here? Is there a particular condition to which the command palette does open? If so what is that condition? Or is this a bug?
Steps to Reproduce:

Right-click on any tab of an open file to open the context menu for the file
Select the context menu option "Open File on Remote"

EXPECT --> The VS Code Command Palette to open, displaying selectable branch names to open the file against (see GIF below).

ACTUAL --> The VS Code Command Palette does not open, and instead the file opens up in a browser against the current working branch.

UPDATE 👉 : I figured out the scenario / pattern as to how to expose the VS Code Command Palette to be able to select the branch of choice to open the target file against. And that is, it will only open the Command Palette if your current working branch is not pushed up (i.e. current branch not available remotely). That makes sense.
However, i would prefer it if there was a configurable option for GitLens to always open the Command Palette to list the branches to which i want to open the file against when i click on Open File on Remote.

Any plans for adding this config?

I would also love this feature - I always want to open the file on master, not my working branch.
I use this, for example, when I am referencing a code file to someone.

I would also love this feature - I always want to open the file on master, not my working branch.
I use this, for example, when I am referencing a code file to someone.

@TylerYep That is also the most common use-case for me too.
To send a reference link to someone else, of the code file sitting on the master branch.

I added 2 new commands:

Open File on Remote From... command (gitlens.openFileOnRemoteFrom) to open a file or revision on a specific branch or tag on the remote provider
Copy Remote File Url From... command (gitlens.copyRemoteFileUrlFrom) to copy the url of a file or revision on a specific branch or tag the remote provider

Can you please verify this fix in tomorrow's insiders edition? Be sure to disable/uninstall the stable version of GitLens first.
You can install the insiders edition from here.

@eamodio thanks for looking into this!
I've tried the today's Insiders edition, and noticed you've included a new very convenient context menu option; Open File on Remote From..., and i found this very handy, as it will list all available branches to select from (see GIF below for reference) 👍

@eamodio Also, as you've instructed, i'll test the two new configuration settings tomorrow,  re-downloading and installing the Insiders Edition again, as today's Insiders Edition does not recognise the new configuration settings.
I suspect that i'll set the new configuration settings values like so (using branch name: master for example):
{
  "gitlens.openFileOnRemoteFrom": "master",
  "gitlens.copyRemoteFileUrlFrom": "master",
}

@Sayvai thanks for verifying. Although there are only those new commands, which show up in the menus and command palette, not any new configuration settings.
Are the new commands enough?

@eamodio Oh i see. I misread your initial comment, and realise they're just new commands!
Yes, I believe these new commands are certainly enough, as i really like the alternative command Copy Remote File URL From... , it really speeds my process up when sending file reference links to the desired branch without having a new browser tab automatically open the file, amongst all the other tabs i have open 👍
Just for reference to others, I also attach a GIF demo of this command. Also to note, the command is only accessible via the Command Palette Cmd + Shift + P (not via the context menu)

Works perfectly 👌

@eamodio which stable version of the GitLens extension do you expect this to go in, and are you able to give an estimate of when? 😬

Either this weekend or early next week.


Bug: Need to remove "/" from column names

It looks like R janitor's clean_names() function removes "/" from column names, whereas Cleaner.polish_names() does not.
See here for a reproducible example: https://github.com/TidierOrg/TidierData.jl/issues/52
Would be great to fix this to match the janitor package's behavior.

Just released version 1.0.4 fixing this issue


test for workbasket main page.

 [DIT] As a Tariff Manager, I want a Main Menu so that I can access various "Manage" / "Create" / "Find & Edit" screens, plus a list of anything the user is already working on


Grammar Fixes and Additional info on Ruby Gems

I noticed some grammatical issues in this article,  I also wanted to add some more information on Ruby Gems and a link to RubyGems.org

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Thank you @tfantina for your contribution and congratulations on your first PR merge to this repo. 🎉


Outdated date is calculated incorrectly

Describe the bug
Days expired is not being calculated correctly. It's currently using the delta between the last two versions.
Expected behavior
Days outdated should be computed from present day against the publish date of the most recent version.
Screenshots

Yargs version info
    "16.2.0": "2020-12-05T23:09:55.514Z",
    "17.0.0-candidate.0": "2021-01-09T19:38:25.444Z",
    "17.0.0-candidate.1": "2021-02-15T21:30:17.357Z",
    "17.0.0-candidate.2": "2021-02-16T00:32:22.009Z",
    "15.5.0-candidate.0": "2021-02-22T00:55:05.770Z",
    "17.0.0-candidate.3": "2021-02-22T02:11:38.450Z",
    "17.0.0-candidate.4": "2021-03-08T17:40:55.172Z",
    "17.0.0-candidate.5": "2021-03-10T21:24:50.182Z",
    "17.0.0-candidate.6": "2021-03-11T22:11:34.793Z",
    "17.0.0-candidate.7": "2021-03-14T22:52:06.309Z",
    "17.0.0-candidate.8": "2021-03-26T20:27:43.508Z",
    "17.0.0-candidate.9": "2021-04-04T03:14:39.548Z",
    "17.0.0-candidate.10": "2021-04-04T03:18:29.406Z",
    "17.0.0-candidate.11": "2021-04-11T04:26:22.108Z",
    "17.0.0-candidate.12": "2021-04-12T02:41:27.306Z",
    "7.1.2": "2021-04-25T03:54:49.822Z",
    "17.0.0-candidate.13": "2021-04-26T02:28:04.627Z",
    "17.0.0": "2021-05-02T19:02:58.536Z",
    "17.0.1": "2021-05-03T23:57:22.380Z"

This should be handled alongside #43

Okay so after revisiting this the spirit of the original calculation is what I want to go for, at least for a default, but there is an interesting case here.
The way it's determined now is if a current version was released 100 days ago and a new version is released today this will fail immediately because it will be calculated as 100 days out of date. I'm thinking this calculation needs to be more of a measurement between version NEXT and NOW. In the scenario outlined above you would be 1 day out of date and not 100 as a new release published.
I also think measuring days since latest release could be the non-default thing to check on but I don't want to tackle that for the scope of this issue.


Filler tweet generator

update on PR #29

good. it drops the tweets and not just accounts now 🎉

note: adding the destroy_all tweets that belong to twitter handles would be a good thing to have in the models (i.e. dependent: :destroy)


Issue 336

Fixes #336

Merge me!
Tests are are running - skipped ones need to be fixed :-)
https://scrutinizer-ci.com/g/lizards-and-pumpkins/magento-connector/inspections/3f8318b7-0118-45a8-93f7-1690231cc29e


Document how to download CI docs part II.

in #4961 @lucyleeow improved the documentation with step by step on how to download the built doc.
@Czaki suggested an improvement by using maybe the "Check" tab instead of scrolling down.

I think that going though checks tab is better as you could reach it from the top of PR page

Select the check tab:

Click build Docs

and download:

But this is my personal preference (work better on PR with long discussions) and requires less scrolling searching for a docs entry (normal PR has 30 checks) and is accessible without logging to GitHub.

_Originally posted by @Czaki here
@melissawm also suggested to use circle-ci and directly expose the built docs.

@melissawm also suggested to use circle-ci and directly expose the built docs.

I think this should be a separate issue. I believe @jni had some suggestions/thoughts about this?
I'm happy to change the workflow the above and address: https://github.com/napari/napari/pull/4961#issuecomment-1222173594ttps://github.com/napari/napari/pull/4961#issuecomment-1222179435

we're not supposed to merge pngs that are not managed by lfs

at the same time. @jni how do I do this lfs thing?

See if https://git-lfs.github.com/ has enough informations.


DS-2701 dspace-rdf

Small patch to make dspace-rdf compile cleanly. dspace-rdf does not have any tests.
Most of the code to support RDF is part of dspace-api (org.dspace.rdf). I will test if everything still works within the next days and submit more PRs if necessary.
@KevinVdV This should be easy to review and can be merged to the service API feature branch.

Changes look good, do you want to merge now or wait for the initial testing ?

@KevinVdV thanks for the review. I merged it so everyone can compile the module. I'll create more PRs if I find something during the tests.

@pnbecker Thanks!


issue/1: refactor pages to page bundles

refactor-pages-to-page-bundles.sh
Helps migrate from v2.4.0 to v3.0.0
Refactor a page named X.md to content/<section>/X/index.md to use the new page bundles and featured image system

E.g. a post content/post/X.md is converted to content/post/X/index.md

See results from using on hugo-academic:exampleSite:

branch
commit

Please revert the Switch from bash to sh commit as per the discussion in #1 . Thanks.

The work is already done to make the script POSIX compliant without sacrificing functionality. The small things I removed provided no major benefit in this script. That commit also removes the "SCRIPTDIR" code, which assumes that the script lives in "./scripts" of someone's hugo site repo.
POSIX compliant scripts are better than bash scripts unless you actually take advantage of the nice features of bash.

Thank you for your really helpful contribution @NGenetzky :)
Sure, sh POSIX can be used more widely. However, I expect most *nix users of Academic use a more modern shell as default, such as bash or zsh, and I assumed that maybe you were "taking advantage of the nice features of bash".


[INTEL MKL] Reverting a change from an earlier commit.

Fixes regressions caused by this commit https://github.com/tensorflow/tensorflow/commit/844aa275fd31fb6f3ac5c607d4ce9b143143d55a  Removed TF_CHECK_OK , since GetAttr can legally return non-ok here.

pinging @penpornk  for review.

@penpornk  thanks, I will add to our backlog.


windowDisablePreview not working as expected

When I start almost any Android app, the system shows a white screen before the app UI.
In my pure Android (no Flutter) app I have resolved this (no more white screen on startup) by setting the following code in the theme:
        <item name="android:windowActionBar">false</item>
        <item name="android:windowNoTitle">true</item>
        <item name="android:windowDrawsSystemBarBackgrounds">true</item>
        <item name="android:statusBarColor">@android:color/transparent</item>
        <item name="android:windowDisablePreview">true</item>

The same code does not work on a bare Flutter app.
Steps to Reproduce

Android Studio 4.1.1 - Create New Flutter Project -> Flutter Application
Update styles.xml as follows:

    <style name="LaunchTheme" parent="android:Theme.Material.NoActionBar">
        <item name="android:windowActionBar">false</item>
        <item name="android:windowNoTitle">true</item>
        <item name="android:windowDrawsSystemBarBackgrounds">true</item>
        <item name="android:statusBarColor">@android:color/transparent</item>
        <item name="android:windowDisablePreview">true</item>
    </style>
    <style name="NormalTheme" parent="android:Theme.Material.NoActionBar">
        <item name="android:windowActionBar">false</item>
        <item name="android:windowNoTitle">true</item>
        <item name="android:windowDrawsSystemBarBackgrounds">true</item>
        <item name="android:statusBarColor">@android:color/transparent</item>
        <item name="android:windowDisablePreview">true</item>
    </style>

Run the app

Expected results:
App should start slower, and go directly to the first widget
Actual results:
App starts quickly, shows a white screen, pauses there for 3 seconds, then goes  to the first widget
Tested on 2 devices, Galaxy S8 Android 8, Galaxy S10, Android 10

Logs

[√] Flutter (Channel stable, 1.22.5, on Microsoft Windows [Version 10.0.18363.1256], locale en-US)
    • Flutter version 1.22.5 at c:\flutter_sdk
    • Framework revision<PHONE_NUMBER> (10 days ago), 2020-12-10 11:54:40 -0800
    • Engine revision ae90085a84
    • Dart version 2.10.4

[√] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
    • Android SDK at C:\android-sdk-windows
    • Platform android-30, build-tools 29.0.2
    • Java binary at: C:\android-studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
    • All Android licenses accepted.

[!] Android Studio (version 4.1.0)
    • Android Studio at C:\android-studio
    X Flutter plugin not installed; this adds Flutter specific functionality.
    X Dart plugin not installed; this adds Dart specific functionality.
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)

[√] VS Code (version 1.52.1)
    • VS Code at ...
    • Flutter extension version 3.17.0

[√] Connected device (1 available)
    • SM G950F (mobile) • android-arm64 • Android 8.0.0 (API 26)

Hi @adrianvintu
Tried to reproduce this on Realme and on S10 by @darshankawar
However, the real issue is slow, start it's not happening here. Ref
Preview

multiple flutter doctor -v
[✓] Flutter (Channel stable, 1.22.5, on macOS 11.1 20C69 darwin-x64, locale en-GB)
    • Flutter version 1.22.5 at /Users/tahatesser/Code/flutter_stable
    • Framework revision<PHONE_NUMBER> (11 days ago), 2020-12-10 11:54:40 -0800
    • Engine revision ae90085a84
    • Dart version 2.10.4

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    • Android SDK at /Users/tahatesser/Code/sdk
    • Platform android-30, build-tools 30.0.2
    • ANDROID_HOME = /Users/tahatesser/Code/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 12.3)
    • Xcode at /Volumes/Extreme/Xcode.app/Contents/Developer
    • Xcode 12.3, Build version 12C33
    • CocoaPods version 1.10.0

[!] Android Studio (version 4.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)

[✓] VS Code (version 1.52.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.17.0

[✓] Connected device (3 available)
    • RMX2001 (mobile)     • EUYTFEUSQSRGDA6D                     • android-arm64 • Android 10 (API 29)
    • Taha’s iPad (mobile) • 00008020-000255113EE8402E            • ios           • iOS 14.3
    • iPhone 12 (mobile)   • 01685E98-F396-4EB9-9C58-8B92677E24D5 • ios           •
      com.apple.CoreSimulator.SimRuntime.iOS-14-3 (simulator)

! Doctor found issues in 1 category.

[✓] Flutter (Channel master, 1.26.0-2.0.pre.86, on macOS 11.1 20C69 darwin-x64, locale en-GB)
    • Flutter version 1.26.0-2.0.pre.86 at /Users/tahatesser/Code/flutter_master
    • Framework revision b793285329 (3 days ago), 2020-12-18 10:14:36 -0800
    • Engine revision 7983c6fda0
    • Dart version 2.12.0 (build 2.12.0-167.0.dev)

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    • Android SDK at /Users/tahatesser/Code/sdk
    • Platform android-30, build-tools 30.0.2
    • ANDROID_HOME = /Users/tahatesser/Code/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 12.3)
    • Xcode at /Volumes/Extreme/Xcode.app/Contents/Developer
    • Xcode 12.3, Build version 12C33
    • CocoaPods version 1.10.0

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)

[!] Android Studio
    • Android Studio at /Applications/Android/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    ✗ Android Studio not found at /Applications/Android/Contents
    • Try updating or re-installing Android Studio.

[✓] VS Code (version 1.52.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.17.0

[✓] Connected device (5 available)
    • RMX2001 (mobile)     • EUYTFEUSQSRGDA6D                     • android-arm64  • Android 10 (API 29)
    • Taha’s iPad (mobile) • 00008020-000255113EE8402E            • ios            • iOS 14.3
    • iPhone 12 (mobile)   • 01685E98-F396-4EB9-9C58-8B92677E24D5 • ios            •
      com.apple.CoreSimulator.SimRuntime.iOS-14-3 (simulator)
    • macOS (desktop)      • macos                                • darwin-x64     • macOS 11.1 20C69
      darwin-x64
    • Chrome (web)         • chrome                               • web-javascript • Google Chrome
      87.0.4280.88

! Doctor found issues in 1 category.

@TahaTesser I don't understand.
My issue is not the 3 seconds delay, I expect that from the debug build. My issue is the white screen, clearly visible also in your video.
The loading white screen gets very ugly, for example, when the user sets a dark theme, even by default.
The app loads the white screen, then switches to the dark theme.
I avoid this this terrible flickering by using windowDisablePreview  in the pure Android app. No idea why this does not work on Flutter.
I hope it's more clear now.

Hi @adrianvintu
That's my point but you mentioned 3 seconds, it is not reproducible, if that reproduces that could be a bigger issue than this. FYI
labeled the issue for for  windowDisablePreview, updated myhttps://github.com/flutter/flutter/issues/72689#issuecomment-748989067

Thank you @TahaTesser, here is more info. The 3-5 seconds white screen is normal for me for my app, built in debug mode.
For the example in our case, the bare bone default Flutter app Android Studio 4.1.1 - Create New Flutter Project -> Flutter Application on cold startup takes 1-2 seconds of white screen loading, in debug mode, on both mentioned phones - after closing the app with BACK, not HOME, of course.

@adrianvintu
Revisiting this issue, I tried replicating it using the details provided in original description using latest stable version and running on Samsung S10 device with which I get below behavior.
https://github.com/flutter/flutter/assets/67046386/233cd5f2-f3a1-43f4-9f19-19c475785ba5
Although I didn't get white screen, but a black one before rendering the app. I also tried with darkTheme with which I saw same behavior.
You may want to read about splash screen feature for your reference and see if it helps in your case or not.
We also would like to know if the latest behavior is something still considered to be an issue at your end or not, so as to properly update status of this issue.

Maybe this can show transparent background https://docs.google.com/presentation/d/1az1lb-p-aI6abv6w-jgMXKCKbl6qwfEwwR98mbJavbE/edit#slide=id.g256b3b3ed96_1_57

@adrianvintu  See if this helps.


Cannot link object files without OpenMP

If one object file uses -fopenmp -fopenmp-targets=..., I get an error if I want to link in object files that were compiled without OpenMP:
error: Invalid bitcode signature

You should be able to reproduce this problem by compiling an empty file with only -c and linking it to an object file with OpenMP target code.

Thank you for reporting this problem.   Sorry it has taken so long to respond.   I believe this problem is resolved in version 0.5-3 which is released today.    This was a driver problem where the -lm flags were passed to the llvm-link step.   This was fixed in the HIP driver for 0.5-3.   Please give it a try and open a new issue if you get a problem.   I promise to move this to our short list of TODOs if it still is causing you trouble.   FYI, please review the new simplified openmp makefiles.


Blinded Pedersen Commitment Scheme In ACL Paper

https://eprint.iacr.org/2012/298.pdf
@seresistvanandras just want to note that there's a Blinded Pedersen Commitment Scheme described in Section 2.7 of Anonymous Credentials Light paper.

https://github.com/zkSNACKs/WabiSabi/issues/30


Karma server crashing with isparta/istambul

I have a grunt karma configuration with browserify options like this:
browserify: {
    debug: true,
    transform: [['browserify-istanbul', {instrumenter: require('isparta')}]]
}

When I run grunt karma:unit:start watch, the server never starts and I get an anonymous ">> Error" with no explanation, even with --verbose.  The server is not running, and so the tests can't run.
grunt karma:once (with singleRun: true) works great.
I wouldn't expect this to have anything to do with isparta except that when I change my browserify options to simply
transform: ['babelify']

Then it works fine (though of course coverage isn't right)
My config roughly looks like this:
{
        options: {
            basePath: '',
            frameworks: ['browserify', 'jasmine'],

            preprocessors: {
                '<%= config.source %>/**/!(*spec|templates).js': [ 'browserify']
            },

            browserify: {
                debug: true,
                transform: [['browserify-istanbul', {instrumenter: require('isparta')}]]
                //This one works:
                //transform: [['babelify', { 'sourceMapRelative': '<%= config.source %>' }]]
            },

            reporters: ['dots', 'coverage'],
            coverageReporter: {
                reporters: [
                    { type: 'html' }
                ]
            },
            port: 9888,
            logLevel: 'INFO',
            browsers: ['PhantomJS']
        },
        unit: {
            background: true,
            singleRun: false,
            files: {
                src: ["<%= config.source %>/**/*.js"]
            }
        },
        once: {
            singleRun: true,
            files: '<%= karma.unit.files %>'
        }
    }

I'm closing this for now. Feel free to reopen it if you still have this issue.

It is still an issue but so much time has passed that it will take some work to look at this again.  I have been running only in singlerun mode though, so I would love to get it resolved.  Don't know if it's a grunt issue or not, so I guess running native karma would be the first step.


Added bullet to avro limitations on byte changes

Fixes DOC-3651
Added a bullet to the Avro limitations outlining how byte types can be changed by Avro clients downstream.

This change is


doc(contributing): removed enum_kind from ARCHITECTURE.md

Description:
EnumKind is removed in this PR https://github.com/swc-project/swc/pull/7137

BREAKING CHANGE:

Related issue (if exists):

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

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


You have not installed wrangler

How the title says, when using the wrangler command it says that it's not installed.
Nodemon is also globally installed and it works, so it's not a permission or path issue that I've seen online.

Same here.

I have the same issue on Linux.
It happens because wrangler was installed not by the same user that is executing it.
In my case i installed wrangler as root (sudo npm install -g @cloudflare/wrangler), but execute it with my own user.
To solve it, I uninstalled wrangler, reconfigured my npm to install global packages in my home directory and reinstalled wrangler. Then it works.

try
node $(dirname $(realpath $(which wrangler)))/install-wrangler.js

as @rbx  mentioned, I uninstalled the @cloudflare/wrangler package, and reinstalled sudo npm install -g wrangler on my home directory and the error has gone by that.

Thanks for reporting this issue! Wrangler v1 is now deprecated and support is only being provided for critical updates or security concerns. As such, we are closing this issue.
New versions of Wrangler are maintained in the workers-sdk repo. If you are running into a similar issue with wrangler v2, please report it in the workers-sdk repo. For more info about wrangler v1 deprecation, please check out our blog post.


[BUG] Failed to build k-means-constrained

Describe the bug
When trying to install k-means-constrained 0.7.1 on a Linux machine under Spark, I get the following error:

Failed to build k-means-constrained

22/09/05 10:06:58 INFO SharedDriverContext: Failed to attach library dbfs:/FileStore/jars/df01ffad_9c82_47d0_af9f_d58e5a9167f7/activity_discovery_web_extension-4.0-py3-none-any.whl to Spark
org.apache.spark.SparkException: Process List(/databricks/python/bin/pip, install, --upgrade, --find-links=/local_disk0/spark-418a7f7d-d386-417e-badc-e56ea3a21c6e/userFiles-6ca93792-2269-488d-b718-a0c3fb538085, /local_disk0/spark-418a7f7d-d386-417e-badc-e56ea3a21c6e/userFiles-6ca93792-2269-488d-b718-a0c3fb538085/activity_discovery_web_extension-4.0-py3-none-any.whl, --disable-pip-version-check) exited with code 1.   ERROR: Command errored out with exit status 1:
   command: /databricks/python3/bin/python /databricks/python3/lib/python3.8/site-packages/pip/_vendor/pep517/_in_process.py build_wheel /tmp/tmp4ehqh6yz
       cwd: /tmp/pip-install-_5fx8ys_/k-means-constrained_4ee597c098d6445ea4b8d6ca9744eeb4
  Complete output (38 lines):
  running bdist_wheel
  running build
  running build_py
  creating build
  creating build/lib.linux-x86_64-3.8
  creating build/lib.linux-x86_64-3.8/k_means_constrained
  copying k_means_constrained/mincostflow_vectorized.py -> build/lib.linux-x86_64-3.8/k_means_constrained
  copying k_means_constrained/__init__.py -> build/lib.linux-x86_64-3.8/k_means_constrained
  copying k_means_constrained/k_means_constrained_.py -> build/lib.linux-x86_64-3.8/k_means_constrained
  creating build/lib.linux-x86_64-3.8/k_means_constrained/sklearn_import
  copying k_means_constrained/sklearn_import/__init__.py -> build/lib.linux-x86_64-3.8/k_means_constrained/sklearn_import
  copying k_means_constrained/sklearn_import/fixes.py -> build/lib.linux-x86_64-3.8/k_means_constrained/sklearn_import
  copying k_means_constrained/sklearn_import/base.py -> build/lib.linux-x86_64-3.8/k_means_constrained/sklearn_import
  copying k_means_constrained/sklearn_import/funcsigs.py -> build/lib.linux-x86_64-3.8/k_means_constrained/sklearn_import
  copying k_means_constrained/sklearn_import/exceptions.py -> build/lib.linux-x86_64-3.8/k_means_constrained/sklearn_import
  creating build/lib.linux-x86_64-3.8/k_means_constrained/sklearn_import/metrics
  copying k_means_constrained/sklearn_import/metrics/__init__.py -> build/lib.linux-x86_64-3.8/k_means_constrained/sklearn_import/metrics
  copying k_means_constrained/sklearn_import/metrics/pairwise.py -> build/lib.linux-x86_64-3.8/k_means_constrained/sklearn_import/metrics
  creating build/lib.linux-x86_64-3.8/k_means_constrained/sklearn_import/utils
  copying k_means_constrained/sklearn_import/utils/__init__.py -> build/lib.linux-x86_64-3.8/k_means_constrained/sklearn_import/utils
  copying k_means_constrained/sklearn_import/utils/sparsefuncs.py -> build/lib.linux-x86_64-3.8/k_means_constrained/sklearn_import/utils
  copying k_means_constrained/sklearn_import/utils/fixes.py -> build/lib.linux-x86_64-3.8/k_means_constrained/sklearn_import/utils
  copying k_means_constrained/sklearn_import/utils/extmath.py -> build/lib.linux-x86_64-3.8/k_means_constrained/sklearn_import/utils
  copying k_means_constrained/sklearn_import/utils/validation.py -> build/lib.linux-x86_64-3.8/k_means_constrained/sklearn_import/utils
  creating build/lib.linux-x86_64-3.8/k_means_constrained/sklearn_import/preprocessing
  copying k_means_constrained/sklearn_import/preprocessing/__init__.py -> build/lib.linux-x86_64-3.8/k_means_constrained/sklearn_import/preprocessing
  copying k_means_constrained/sklearn_import/preprocessing/data.py -> build/lib.linux-x86_64-3.8/k_means_constrained/sklearn_import/preprocessing
  creating build/lib.linux-x86_64-3.8/k_means_constrained/sklearn_import/externals
  copying k_means_constrained/sklearn_import/externals/__init__.py -> build/lib.linux-x86_64-3.8/k_means_constrained/sklearn_import/externals
  copying k_means_constrained/sklearn_import/externals/funcsigs.py -> build/lib.linux-x86_64-3.8/k_means_constrained/sklearn_import/externals
  creating build/lib.linux-x86_64-3.8/k_means_constrained/sklearn_import/cluster
  copying k_means_constrained/sklearn_import/cluster/__init__.py -> build/lib.linux-x86_64-3.8/k_means_constrained/sklearn_import/cluster
  copying k_means_constrained/sklearn_import/cluster/k_means_.py -> build/lib.linux-x86_64-3.8/k_means_constrained/sklearn_import/cluster
  running build_ext
  creating build/temp.linux-x86_64-3.8
  creating build/temp.linux-x86_64-3.8/k_means_constrained
  x86_64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security -g -fwrapv -O2 -fPIC -I/tmp/pip-build-env-j0gh3wdg/overlay/lib/python3.8/site-packages/numpy/core/include -I/databricks/python3/include -I/usr/include/python3.8 -c k_means_constrained/mincostflow_vectorized_.c -o build/temp.linux-x86_64-3.8/k_means_constrained/mincostflow_vectorized_.o
  error: command 'x86_64-linux-gnu-gcc' failed: No such file or directory
  ----------------------------------------
  ERROR: Failed building wheel for k-means-constrained
ERROR: Could not build wheels for k-means-constrained which use PEP 517 and cannot be installed directly

Minimum working example
pip install k_means_constrained
Versions:

Python: 3.8
Operating system: Linux
k-means-constrained: 0.7.1
numpy: 1.23.2
scipy: 1.8.0
ortools: 9.3.10497
joblib: 1.1.0
cython (if installed): 0.29.32

Encountered same issue today. No solution found so far.

Encountered same issue today. No solution found so far.

I've solved it eventually by installing build essentials (on Ubuntu):
sudo apt -y install build-essential
However on Mac-OS I did not have to do that at all ... either way, it this is a per-requisite it would be good to have it noted in the installation instructions

Im closing this for now. let me know if you require more assistance


⚠ Bofrost.de has degraded performance

In 52b1d19, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1213 ms

Resolved: Bofrost.de performance has improved in 7047799 after 6 minutes.


After import account finished, app stays at CreateAccountEntryPage

the app should navigate to the EncointerHomePage instead

There used to be an observer in
https://github.com/encointer/encointer-wallet-flutter/blob/770a5bab5608b82d6df6fb345674778a7f1ce2bf/lib/app.dart#L143
Maybe this is the issue

good spot. that could be it indeed


fix encoding errors

the lobbyingregister.json file have some encoding problems with the german special characters (ä, ö, ü, etc). the html is fine, but the json generated out of it includes lots of encoding errors.

http://www.w3.org/International/tutorials/tutorial-char-enc/

fixed it with commit https://github.com/OKFNat/lobbyscraper/commit/e2da86fadfbe01d09ce8fc310fe7475b8bd6622a
the problem was in the json.dumps() function. added the ensure_ascii=False attribute.


IPv4/DHCP Let the application indicate a preferred IP-address

Description
Many DHCP servers keep track of what IP-addresses have been leased to which MAC-address.
Some servers however seem to prefer to give randomly chosen IP-addresses. This PR gives the possibility to indicate a preferred IP-address, using DHCP option 50 when asking for an offer.
Test Steps
I tested the PR as follows:
    /* Tell DHCP that this device likes to receive the address <IP_ADDRESS>. */
    uint32_t ulPreferredIPAddress = FreeRTOS_inet_addr_quick( 192, 168, 2, 136 );
    vDHCPSetPreferredIPAddress( ulPreferredIPAddress );

    FreeRTOS_IPInit( ucIPAddress, ucNetMask, ucGWAddr, ucDNSAddr, ucMACAddr );

Related Issue
Users complain that their DHCP server doesn't seem to memorise leases. See this post on the FreeRTOS forum, item 4.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@htibosch Thanks for your contribution. Your PR is under review.

I wrote:

/* Tell DHCP that this device likes to receive the address <IP_ADDRESS>. */
uint32_t ulPreferredIPAddress = FreeRTOS_inet_addr_quick( 192, 168, 2, 136 );
vDHCPSetPreferredIPAddress( ulPreferredIPAddress );
FreeRTOS_IPInit( ucIPAddress, ucNetMask, ucGWAddr, ucDNSAddr, ucMACAddr );

In the above sample code, ucIPAddress is the IP-address to be used as a default, in case DHCP is not used, or in case DHCP fails.
I have considered making it one and the same, use ucIPAddress automatically as the preferred IP-address.
I think that it not desirable for everyone: some developers will prefer not to use a preferred IP-address at all.
And adding yet another define (ipconfigDHCP_USE_STATIC_IP_AS_PREFERRED_ADDRESS) would add too much complexity in my opinion.
@gshvang wrote:

Thanks for your contribution. Your PR is under review.

Great, thank you!
Fortunately it is a simple and quite isolated change.


Flaky test: Aspire.Hosting.Tests.Dashboard.ResourcePublisherTests.ProducesExpectedSnapshotAndUpdates

https://dev.azure.com/dnceng-public/public/_build/results?buildId=500597&view=results
Error message
Assert.Throws() Failure
Expected: typeof(System.OperationCanceledException)
Actual:   (No exception was thrown)

Stack trace
   at Aspire.Hosting.Tests.Dashboard.ResourcePublisherTests.ProducesExpectedSnapshotAndUpdates() in /_/tests/Aspire.Hosting.Tests/Dashboard/ResourcePublisherTests.cs:line 53
--- End of stack trace from previous location ---

cc @drewnoakes

This one's interesting. I ran the unit test 100 times on my PC using the "Run until failure" command, and it didn't fail. This will require some deeper investigation.

For now we can just disable the test so we don't waste time on builds having unrelated changes.


RadzenDayView does not show appointments after 23:59

If one sets the EndTime > 24 hours of the RadzenDayView then the rendering works just fine, but appointments wont be shown.
To fix this this line https://github.com/radzenhq/radzen-blazor/blob/b56d4d1ca3fef94ad82dbbc1870b61d0bcc27a39/Radzen.Blazor/RadzenDayView.razor#L11 should be changed to:
var appointments = Scheduler.GetAppointmentsInRange(StartDate, EndDate).ToList();
You can find the same line in RadzenWeekView: https://github.com/radzenhq/radzen-blazor/blob/b56d4d1ca3fef94ad82dbbc1870b61d0bcc27a39/Radzen.Blazor/RadzenWeekView.razor#L9
If you want me to fix this, then I can do a pull request (same for https://github.com/radzenhq/radzen-blazor/issues/468)

Sure thing. You can open a pull request for us to review and test. The suggested change sounds reasonable.


[Dependencies] Upgrade Storybook from v5 to v6

What & Why
This PR upgrades Storybook from v5 to v6. This branch started by running npx sb upgrade and then running through the migration guides to get a working build:
Medium migration guide: https://medium.com/storybookjs/storybook-6-migration-guide-200346241bb5
Comprehensive migration guide: https://github.com/storybookjs/storybook/blob/next/MIGRATION.md#from-version-53x-to-60x
Fortunately (or unfortunately) most of the changes do not apply to us because we're using the old storiesOf syntax instead of the Component Story Format. However, this is fine (for now) since storybook-readme does not yet support v6. Longer-term we should migrate away and use MDX Docs instead for first-class support, but my early attempts at adding them actually broke most of our stories 🙃.
CHANGELOG:

Removes temporary .babelrc (added in #334 for TypeScript compat), TypeScript webpack loader (since Storybook supports it by default), but adds @babel/preset-typescript to babel.config.js

This seemed to be the arrangement to get type-checking + build working without issue.

Adds .storybook/main.ts

This is the new preferred method for loading stories, not .storybook/preview.js
It's also preferred to include addons in this file instead of /register imports in .storybook/manager.js

This PR started as mere curiosity to figure out how much work would be required to upgrade, but we are entering into a technical spike for incorporating multiple storybooks/themes, so we may end up actually needing to take advantage of new functionality sooner rather than later.

@daigof Going to keep working on this branch, FYI. If you've got other work in radiance-ui coming up feel free to let me know if it blocks you. I don't think it should, though.