Admin Test Case Page - Error 500

https://compliance.mobilemoneyapi.io/admin/test-cases
Steps to reproduce
Currently only present on compliance platform

Navigate to admin/test-cases
See 500 Error

Additional info
Seems this error has come out of nowhere so I'm not sure what has caused it. One thing I can add is I tried manually editing a test case within the platform by navigating to the url directly (i.e https://compliance.mobilemoneyapi.io/admin/test-cases/589/test-steps) and once finished making changes the url now displays a 500 error as well.
Laravel.log
[2021-07-30 14:29:02] production.ERROR: Argument 1 passed to GuzzleHttp\Psr7\Response::__construct() must be of the type int, string given, called in /var/www/html/app/Casts/ResponseCast.php on line 33 {"userId":3,"exception":"[object] (TypeError(code: 0): Argument 1 passed to GuzzleHttp\\Psr7\\Response::__construct() must be of the type int, string given, called in /var/www/html/app/Casts/ResponseCast.php on line 33 at /var/www/html/vendor/guzzlehttp/psr7/src/Response.php:94)

The issue was caused by some test cases which had a jws parameter before the body like so:
      jws:
        alg: RS256
        key: '{{ file_env.CERTIFICATE_PATH }}'
        public_key: '{{ file_env.PUBLIC_CERTIFICATE_PATH }}'
        protectedHeaders:
          - x-callback-url
          - x-date
        header: FSPIOP-Signature
      headers:
        accept: 'application/json'
        content-type: 'application/json'
        x-callback-url: '{{ env.SP_BASE_URI }}/callback'
        x-date: '{{ new_date_iso8601() }}'

which caused the error shown in the post above. Once the test cases were updated without the jws field, the 500 errors disappeared.


Use singleton_class method instead of instead of legacy trick

This makes easy to understand code.

okay. Thanks!


Official procedure of update Angular 9.0 to 10.0 fails

🐞 Bug report
Command (mark with an x)

[ ] new
[ ] build
[ ] serve
[ ] test
[ ] e2e
[ ] generate
[ ] add
[x] update
[ ] lint
[ ] extract-i18n
[ ] run
[ ] config
[ ] help
[ ] version
[ ] doc

Is this a regression?
Yes, the previous version in which this bug was not present was: 9.0
Description
Within the update command using npx with @angular/cli@10 the required version of Node.js should be >=10.13.0 however the error message says that minimum version of Node.js has to be v12.20.
It looks like npx is using the last version of @angular/cli@13 instead of specified within the command.
🔬 Minimal Reproduction

npx @angular/cli@10 update @angular/core@10 @angular/cli@10

🔥 Exception or Error

Node.js version v12.16.3 detected.
The Angular CLI requires a minimum Node.js version of either v12.20, v14.15, or v16.10.

Please update your Node.js version or visit https://nodejs.org/ for additional instructions.

🌍 Your Environment

Angular CLI: 9.1.4
Node: 12.16.3
OS: win32 x64

Angular: 9.1.4
... animations, cli, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router
Ivy Workspace: Yes

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.901.4
@angular-devkit/build-angular     0.901.4
@angular-devkit/build-optimizer   0.901.4
@angular-devkit/build-webpack     0.901.4
@angular-devkit/core              9.1.4
@angular-devkit/schematics        9.1.4
@angular/cdk                      9.2.2
@ngtools/webpack                  9.1.4
@schematics/angular               9.1.4
@schematics/update                0.901.4
rxjs                              6.5.5
typescript                        3.8.3
webpack                           4.42.0

Anything else relevant?

As a workaround you can use the below.
NG_DISABLE_VERSION_CHECK=1 ./node_modules/.bin/ng update @angular/cli@10 @angular/core@10

I'm not sure this is related to my issue but it sounds like it is...
I recently tried to run this command:
ng update @angular/cli@^11 @angular/core@^11 @angular/material@^11 @angular/cdk @^11
But i got a mixed install with the latest version 11 for some packages and the latest version 12 for others

Closed via https://github.com/angular/angular-cli/pull/22225


mat-form-field not working with highchart

Is this a regression?

[ ] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
No response
Description
if i am removing
mat-select it affecting other ui

<mat-select [(value)]="chartType">
Bar Chart
Line Chart

        </mat-form-field>

        bit when i remove hole div it's working fine please look into this

Reproduction
StackBlitz link:
Steps to reproduce:
1.
2.
Expected Behavior
should be work
Actual Behavior
affecting other ui
Environment

Angular:
CDK/Material:
Browser(s):
Operating System (e.g. Windows, macOS, Ubuntu):
mac0s , all browser

I don't have enough information here to assist. I assume you are referring to a separate library for charting, so it would likely make more sense to create your issue in that repository instead. If your issue is angular material specific, please create a new issue with a reproduction on StackBlitz.


Update request-your-data-move.md

Added "Migration eligibility depends on the specific workload provisioning date, so tenant creation date may not always be the single date that matters." to the note as The tenant could have been created with just Exchange and then added on OneDrive for Business and Teams later on so they will not be eligible to data move.

Issue #https://github.com/MicrosoftDocs/OfficeDocs-Enterprise/issues/898

@JohanFreelancer9 - kindly do the copy editor review for this PR. Thanks

@andybergen Please merge this PR. Thanks.


Zeroconf/Bonjour Serverless/Registrarless

Looked at:
https://jitsi.org/Development/PluginZeroConf
and https://trac.jitsi.org/ticket/358 (Support for Bonjour / ZeroConf)
ChatSecure allows you to enter only a username and nothing more when creating "WiFi Mesh Chat"
Jitsi requires a domain to be added to the username.
Running latest (buggy) master commit b59ada8348ec9048fce58801d58a6c76200382a4

Zeroconf/Bonjour has been disabled for a long time as it wasn't maintained. Lacking resources for even the most important protocols, I don't see this coming back. Registrarless SIP should be working in a LAN without firewalls.


Add business metrics doc to the index!

The page /well-architected/resiliency/business-metrics.md (https://github.com/MicrosoftDocs/well-architected/blob/main//well-architected/resiliency/business-metrics.md) seems to have fallen out of the index. It is a very relevant page and it should be highlighted how to calculate and align with business for resiliency.

@dominicallen -- we have a page that exists that isn't in the TOC.  Is the content valid to add back into the TOC or should the article be refreshed first or removed?

This work has been done, thank you @noopman for bringing this to our attention.
https://learn.microsoft.com/azure/architecture/framework/resiliency/business-metrics
#please-close


Doesn't Load in IE

Describe the bug
The page doesn't even load. It's just a blank page.
To Reproduce
Visit: http://parkingnotifier.s3-website-us-west-2.amazonaws.com/
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: Windows 10
Browser: Internet Explorer
Version: 11

I know React.js doesn't use HTML so I'm not sure how to do this but I think you need to add this meta tag to the index.html header:

We'll also probably need to add this polyfills in because internet explorer can't handle Javascript arrays:
https://reactjs.org/docs/javascript-environment-requirements.html @alex-stout Let me know what you think


Unable parse OR

Hi,
when I initialize org.drewcarlson:kjob-jdbi the kjob or Jdbi generates query like INSERT OR REPLACE INTO kjobLocks VALUES (?, ?, ?) which I can't parse because I get: ParseException: Encountered unexpected token: "OR".

Greetings.
INSERT OR REPLACE ... is not supported and far away from any standard or RDBMS I know. MERGE ... INTO ... would be more appropriate.
The supported syntax are shown here.

Am I correct to assume, that you talk to MongoDB?
If so, then support is slim because we very much focus on Relational DBs and Standard SQL.

The problem is that I'm not writing the SQL the framework (Jdbi? probably) generates it. And the framework targets to SQLite, MySQL, PostegreSQL.
I now use SQL filter or sanitizer in JDBC wrapper driver where I replace INSERT OR REPLACE to INSERT and that workaround works.

Can you support non-standard known syntax also. Or better can you replace it with MERGE ... INTO ...  syntax?

Can you support non-standard known syntax also.

We actually do support a lot of non-standard syntax and supporting your statement is possible. However, first of all you would need to point us on the exact syntax definition.
I did not find any INSERT OR REPLACE INTO ... statement.

It seems to be very SQLite specific.

I got a POC working and will provide a patch today:
expected: <insert or replace into kjoblocks values(?,?,?)> but was: <upsert into kjoblocks values(?,?,?)>
Expected :insert or replace into kjoblocks values(?,?,?)
Actual   :upsert into kjoblocks values(?,?,?)


Ping control frames never parsed

I'm getting the following errors with a long running websocket connection.
=ERROR REPORT==== 7-Jun-2023::09:13:17.031402 ===
Error in process <0.123.0> with exit value:
{{case_clause,9},
 [{mist@internal@websocket,frame_from_message,3,
                           [{file,"/home/arnar/Code/gliew/build/dev/erlang/mist/_gleam_artefacts/mist<EMAIL_ADDRESS>                            {line,154}]},
  {mist@internal@handler,handle_websocket_message,3,
                         [{file,"/home/arnar/Code/gliew/build/dev/erlang/mist/_gleam_artefacts/mist<EMAIL_ADDRESS>                          {line,28}]},
  {glisten@handler,'-start/1-fun-3-',3,
<EMAIL_ADDRESS>                    {line,169}]},
  {gleam@otp@actor,loop,1,
                   [{file,"/home/arnar/Code/gliew/build/dev/erlang/gleam_otp/_gleam_artefacts/gleam<EMAIL_ADDRESS>                    {line,137}]}]}

Which I have traced to https://github.com/rawhat/mist/blob/v0.11.0/src/mist/internal/websocket.gleam#L63 as it's not matching opcode 9 afaict.
Here it's expecting it as a possible output from frame_from_message but if I'm not mistaken this will never happen.

Huh, yeah that does seem like it needs to be handled.  Just an oversight on my part, I'm sure.  I can look into that.  Thank you!

This should be good now.  It did also uncover a few things I'm doing incorrectly per the RFC, but I'm going to tackle those separately.
Thanks for catching this 😄

Perfect! Thanks! 🎉


Implement schema squashing

What changed?
For incremental schema, it is now possible to take a shortcut from one version to another without applying incremental changes one by one.
The directory name should be in format s<from_ver>-<to_ver>, where

 <to_ver> must be greater than <from_ver>
<to_ver> must exist in incremental schema steps, i.e. a directory with valid manifest named v_<to_ver> must exist
<from_ver> must either exist in incremental schema steps, or be equal to initial version 0.0

Schema tool will automatically select the path with least steps.
Squashed shortcut schema from version 0.0 to 0.23 included. This particular schema version is selected since it's on the tip of latest 0.11 Cadence release.
Why?
For Cassandra instances with large replication factors and latency schema statements might take up to a second for a trivial operation such as column creation. Given that current version on tip of master is 0.27, the bootstrap time adds up and will grow with each schema update.
Applying goal-state schema would only create 30+ entities and would run up to 4x times faster on Cassandra setups above.
Applying schema.cql is an option for a new installation, but prevents further incremental upgrades.
How did you test it?
To measure speed improvements, application times for both schema and every incremental version is now logged. Tested by playing back incremental updates up to version 0.27 on docker instance
Time improvements
Before the change
cadence_1      | 2020/05/11 20:35:15 Schema updated from 0.0 to 0.1, elapsed 2.247461928s
cadence_1      | 2020/05/11 20:35:17 Schema updated from 0.1 to 0.2, elapsed 1.631742425s
cadence_1      | 2020/05/11 20:35:18 Schema updated from 0.2 to 0.3, elapsed 836.043275ms
cadence_1      | 2020/05/11 20:35:19 Schema updated from 0.3 to 0.4, elapsed 633.861512ms
cadence_1      | 2020/05/11 20:35:19 Schema updated from 0.4 to 0.5, elapsed 394.238516ms
cadence_1      | 2020/05/11 20:35:20 Schema updated from 0.5 to 0.6, elapsed 1.130838727s
cadence_1      | 2020/05/11 20:35:24 Schema updated from 0.6 to 0.7, elapsed 3.86523542s
cadence_1      | 2020/05/11 20:35:24 Schema updated from 0.7 to 0.8, elapsed 303.648524ms
cadence_1      | 2020/05/11 20:35:25 Schema updated from 0.8 to 0.9, elapsed 457.736671ms
cadence_1      | 2020/05/11 20:35:25 Schema updated from 0.9 to 0.10, elapsed 436.88099ms
cadence_1      | 2020/05/11 20:35:28 Schema updated from 0.10 to 0.11, elapsed 2.453376415s
cadence_1      | 2020/05/11 20:35:31 Schema updated from 0.11 to 0.12, elapsed 3.061781143s
cadence_1      | 2020/05/11 20:35:32 Schema updated from 0.12 to 0.13, elapsed 1.82323551s
cadence_1      | 2020/05/11 20:35:33 Schema updated from 0.13 to 0.14, elapsed 336.098623ms
cadence_1      | 2020/05/11 20:35:34 Schema updated from 0.14 to 0.15, elapsed 799.870505ms
cadence_1      | 2020/05/11 20:35:34 Schema updated from 0.15 to 0.16, elapsed 192.859672ms
cadence_1      | 2020/05/11 20:35:34 Schema updated from 0.16 to 0.17, elapsed 378.112309ms
cadence_1      | 2020/05/11 20:35:35 Schema updated from 0.17 to 0.18, elapsed 387.9124ms
cadence_1      | 2020/05/11 20:35:36 Schema updated from 0.18 to 0.19, elapsed 1.129843878s
cadence_1      | 2020/05/11 20:35:36 Schema updated from 0.19 to 0.20, elapsed 195.834643ms
cadence_1      | 2020/05/11 20:35:36 Schema updated from 0.20 to 0.21, elapsed 178.099493ms
cadence_1      | 2020/05/11 20:35:37 Schema updated from 0.21 to 0.22, elapsed 902.453475ms
cadence_1      | 2020/05/11 20:35:37 Schema updated from 0.22 to 0.23, elapsed 531.753091ms
cadence_1      | 2020/05/11 20:35:38 Schema updated from 0.23 to 0.24, elapsed 181.113603ms
cadence_1      | 2020/05/11 20:35:38 Schema updated from 0.24 to 0.25, elapsed 160.556925ms
cadence_1      | 2020/05/11 20:35:38 Schema updated from 0.25 to 0.26, elapsed 531.831506ms
cadence_1      | 2020/05/11 20:35:38 Schema updated from 0.26 to 0.27, elapsed 110.09224ms
cadence_1      | 2020/05/11 20:35:38 All schema changes completed in 25.296508226s

After the change
cadence_1      | 2020/05/11 22:37:38 Schema updated from 0.0 to 0.23, elapsed 4.242590367s
cadence_1      | 2020/05/11 22:37:39 Schema updated from 0.23 to 0.24, elapsed 303.520763ms
cadence_1      | 2020/05/11 22:37:39 Schema updated from 0.24 to 0.25, elapsed 227.529843ms
cadence_1      | 2020/05/11 22:37:39 Schema updated from 0.25 to 0.26, elapsed 741.045226ms
cadence_1      | 2020/05/11 22:37:40 Schema updated from 0.26 to 0.27, elapsed 164.768217ms
cadence_1      | 2020/05/11 22:37:40 All schema changes completed in 5.679644717s

Data validitiy
Before the change
root@1370b14fd06a:/# cqlsh -e "DESC KEYSPACE cadence"|md5sum
bd705d28afcfe8b5a207a905af16f9e1  -
root@1370b14fd06a:/# cqlsh -k cadence --no-color -e "SELECT * FROM domains;"|md5sum
6672f72e06d45d845df8aa736825f11d  -
root@1370b14fd06a:/# cqlsh -k cadence --no-color -e "SELECT * FROM domains_by_name_v2;"|md5sum
69dcf3ee18d67a066915dd371e622ac3  -

After the change
root@21133ee99c79:/# cqlsh -e "DESC KEYSPACE cadence"|md5sum
bd705d28afcfe8b5a207a905af16f9e1  -

root@21133ee99c79:/# cqlsh -k cadence --no-color -e "SELECT * FROM domains;"|md5sum
6672f72e06d45d845df8aa736825f11d  -

root@21133ee99c79:/# cqlsh -k cadence --no-color -e "SELECT * FROM domains_by_name_v2;"|md5sum
69dcf3ee18d67a066915dd371e622ac3  -

Potential risks
As with any other schema change, there are risks involved. One of the concerns is mismatching schemas in schema.cql for 0.11 Cadence version (v0.23 Cassandra schema) and playing back the incremental changes. Some are minor, such as column ordering, but there is a missing events table and mismatching data type for a column.
However, the tests above show that shortcut schema is identical to one produced by playing incremental changes back.

Coverage increased (+0.5%) to 68.774% when pulling 6e2cdf98ee86da713302465af64bdf4ac5016a36 on schema_squashing into 83809d81d577f5e5a85523474ac82bede1baa23e on master.

@aleksejuber PR looks pretty good to me. I just left a minor comment. Besides that, have you considered automating your md5sum test in as an integration test (possibly in tools/common/schema/test/updatetest.go)? I think it would be good to have it so that we don't need to reinvent a manual way to verify each new squash in the future. It'd also prevent inconsistencies in case a contributor modifies these CQL files for some reason.

. Besides that, have you considered automating your md5sum test in as an integration test (possibly in tools/common/schema/test/updatetest.go)?

This is a very good point, the integration test would surely benefit here to ensure initial data/schema consistency. I believe the check can be done without modifying the Go code, using modified schema initialisation bash scripts, as in

List all the shortcut directories to determine the end version and rename/move them out
Apply versions as usual, but take snapshots after every end version
On by one move the shortcut directories back, remove keyspace, init version 0.0, replay up to the end version, compare schemas, and remove the shortcut

This way we will run same commands as the schema init scripts and avoid missing something out in test setup.
In your opinion, should the integration tests be included in this PR or create a separate one for this issue?

In your opinion, should the integration tests be included in this PR or create a separate one for this issue?

I'm OK with either way. Regarding how we implement the tests, I'd prefer having those in tools/updatetest.go for consistency with other tests and to ensure they run together.


spirv-tools explicitly deletes DLLs, then aborts when consumed via find_package due to missing DLLs

Describe the bug
The spirv-tools package explicitly deletes the output of the SPIRV-Tools-shared target here: https://github.com/barcharcraz/vcpkg/blob/master/ports/spirv-tools/portfile.cmake#L46-L51
The SPIRV-Tools-shared target is still created even with -DSPIRV_TOOLS_BUILD_STATIC=ON (which is set explicitly in the portfile) so the upstream CMake still installs it, and creates a check for its presence in the module importing script.
That means if the package is consumed via find_package, the check will fail, and a FATAL_ERROR message is logged. This aborts the build.
Environment

OS: Windows 10
Compiler: MSVC 2019 16.9.5

To Reproduce
Steps to reproduce the behavior:

./vcpkg install spirv-tools
Create a new CMake project including find_package(SPIRV-Tools REQUIRED). A CMakeLists.txt containing this single line should be enough.
Configure the CMake project using the normal Vcpkg toolchain.
Observe that a fatal error is printed stating that: The imported target "SPIRV-Tools-shared" references the file

    "C:/Clones/vcpkg/installed/x64-windows/debug/bin/SPIRV-Tools-shared.dll"

 but this file does not exist.  Possible reasons include:

 * The file was deleted, renamed, or moved to another location.

 * An install or uninstall procedure did not complete successfully.

 * The installation package was faulty and contained

    "C:/Clones/vcpkg/installed/x64-windows/share/SPIRV-Tools/SPIRV-ToolsTarget.cmake"

 but not all the files it references.

Call Stack (most recent call first):
  C:/Clones/vcpkg/installed/x64-windows/share/SPIRV-Tools/SPIRV-ToolsConfig.cmake:1 (include)
  C:/Clones/vcpkg/scripts/buildsystems/vcpkg.cmake:772 (_find_package)
  CMakeLists.txt:119 (find_package)

Expected behavior
Once find_package(SPIRV-Tools REQUIRED) has been called, the configure proceeds and the SPIRV-Tools-static library is available (also as SPIRV-Tools with no suffix).
Failure logs

The relevant parts of the log are above.
This is a log from a dummy CMake project with literally just the find_package call, so it's got some other warnings about not being a real CMake project: log.log

Additional context
N/A

Hi @chrisdjali-wrld3d
Thanks for posting this issue.
@barcharcraz
Could you please help take a look why removing SPIRV-Tools-shared.dll?
https://github.com/microsoft/vcpkg/blob/876e67c26e42c0c7d2daa41c6871af117ae6bec5/ports/spirv-tools/portfile.cmake#L49
Is there any reason why this port only supports static build?

I don't think they actually correctly export symbols on windows. I forget the exact reason, however. I think one of vcpkgs lint checks fires if a static library build installs shared libraries, requiring the deletion. If I recall patching the shared build out of the cmakelists was pretty involved as well due to how their cmake is structured.
I'll take another look when I have time, maybe things have improved upstream.
There's some upstream work in SPIRV-Tools to fix their build options.

@chrisdjali-wrld3d This issue has been fixed upstream, please update to the latest vcpkg and try building again. :)
Successful example：
CMakeLists.txt:
cmake_minimum_required(VERSION 3.9)
set(CMAKE_CXX_STANDARD 20)

project(Bug_test)

add_executable(main main.cpp)

find_package(SPIRV-Tools CONFIG REQUIRED)
target_link_libraries(main PRIVATE SPIRV-Tools-shared SPIRV-Tools-static)

log:
test@test002:~/bug/build$ cmake .. -DCMAKE_TOOLCHAIN_FILE=/home/test/vcpkg/scripts/buildsystems/vcpkg.cmake
-- The C compiler identification is GNU 9.4.0
-- The CXX compiler identification is GNU 9.4.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Configuring done
-- Generating done
-- Build files have been written to: /home/test/bug/build

target_link_libraries(main PRIVATE SPIRV-Tools-shared SPIRV-Tools-static)

Find the error!


Correct the line related to DeploymentMode

Please correct the following line in the page:
"Do not set the DeploymentMode to Developer in production environments."
DeploymentMode should be either Development or Production.
It should be like "Do not set the DeploymentMode to Development in production environments."
Thanks
Surender Reddy Gutha
[Enter feedback here]
[Enter feedback here]

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

ID: bdca08d8-4a1d-f11c-9e3e-6627ea0f18bc
Version Independent ID: 6bb42537-50b2-2af1-fdf7-86b76ed9afe6
Content: Troubleshoot custom policies with Application Insights - Azure AD B2C
Content Source: articles/active-directory-b2c/troubleshoot-with-application-insights.md
Service: active-directory
Sub-service: b2c
GitHub Login: @msmimart
Microsoft Alias: mimart

@SurenderGutha Thank you for catching this. We will review and have this updated .

@SurenderGutha Thank you for catching this. We will review and have this updated .

@SurenderGutha We have initiated an update and the change should reflect in the next 48 hours maximum . Thank you for your contribution to improvement of the azure documentation.

@SurenderGutha We have initiated an update and the change should reflect in the next 48 hours maximum . Thank you for your contribution to improvement of the azure documentation.


css selector

hi! thanks for the great work, really nice and helpful plugin
I'm struggling to make it work with the css selector though,
I looked for the css class of the element I want to point at inspecting the page with the browser's tools, but no success yet
Could you provide a syntax guide on how to use that option?
Thanks

@yesoreyeram Is this abandoned? I would love to know how to use this as well and it does appears to be broken

sorry bro stopped using grafana shortly after

Thanks @yesoreyeram, unfortunately i don't have the knowledge to improve this in code. At the moment its broken entirely. I do see a PR from a year ago about making it work with the new UI, but seems to have failed some checks. Really a shame this doesn't work it seems such a good idea


fix(docs): fix a typo and remove duplicate microK8s getting started link

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind user-interface

/kind content

/kind event

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area blog

/area documentation

/area community

What this PR does / why we need it:
This PR fixes a typo in Plugin spelling and removes duplicate microK8s getting started link
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: ekoops
Once this PR has been reviewed and has the lgtm label, please assign vjjmiras for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

content/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: e918df9a88aec3f9bf5add101f1d236e668eb21e

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: ekoops, Issif
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

content/OWNERS [Issif]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Add regex string searches and surface geo target list field (Fixes #195, #450)

Fixes #195
Fixes #450
Were any Django, import pipeline, table_schema, or dictionary files modified? Y

Database used: opus3_test_200211
All Django tests pass: Y

Were any JavaScript or CSS files modified? Y

JSHINT run on all affected files: Y
Tested on Chrome, Firefox, Safari, and iOS: Y
(Remember to test all browser sizes)
Tested for race conditions (with delayed API calls if applicable): Y

Description of changes:
Implemented "regex" qtype for strings and added appropriate tests. Made UI do input validation on strings. Implemented "multiple target list" field under Surface Geometry Constraints. Updated documentation.
Known problems:
None.

I've merged the current master into this branch and fixed the merge conflicts. All Django tests pass using opus3_test_200211. I also fixed one typo that caused a crash in the fake HTTP404 throws.

Also, it turns out that the central planet is always in the target list even if it's not in the field of view. I've updated the tooltip and FAQ to talk about this.

Database used: opus3_test_200211
All Django tests pass: Y
JSHINT run on all affected files: Y
Tested on Chrome, Firefox, Safari, and iOS: Y
(Remember to test all browser sizes)
Tested for race conditions (with delayed API calls if applicable): Y


Common io/nrf52/spi

Nordic NRF52840-DK CommonIO SPI
Description
Based off our ST implementation. Ioctls for querying number of bytes sent/read for current transaction have been deferred since there's no official way to query this from nRF_SDK driver. Though, I left code comments in their place which explain a potential way to achieve them.
In separate PR, may request change for user configurable pin assignments in future, as this is lacking from current iot_spi.h
Checklist:

[ ] I have tested my changes. No regression in existing tests.
[ ] My code is Linted.
[ ] Just as ST impl, pin assignments need to be decided for SPIM instances. Currently only assigned for SPIM_0

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Moved to PR#2175


Return just a number of likes

[ ] Return posts' likes as a number, not an array of likes
[ ] Make an endpoint to fetch users who liked a post

Hello, I would like to try to working on this issue. Could you assign it to me please? Thank you

Hello, I would like to try to working on this issue. Could you assign it to me please? Thank you

Yes of course! 😊 Here You go

Don't be shy to reach out if You need any assistance at all!

OK thank you so much. :)

@macbookfilip Hi! how's the work on this issue going?

hallo it's  look be fine thanks

hallo, i have question on you. Whoever can like these posts or just only logged user? But I think can be better with logged user. Do you want like and unlike or just like?

Looking at the web.php file, You can clearly see that there is an auth guard on the path to like controller
If You'd look into the like controller, then You would clearly see that the liking of a post/comment is handled previously
So: only the logged in users can like posts/comments and the like logic is already handled
Have You used clubi? These questions seem like You've never even used the service You're trying to work on
The issue says that instead of the list of post's/comment's likes, You need to change the code to send just the number of likes
Then You'd need to create an endpoint that will return the list of like objects, so that the service doesn't lose the functionality if someone eventually wants to download the like info


[BUG] NFS driver: creates multiple 1st volume backup and immediately list backup volume names sometimes fails

Describe the bug
Create multiple 1st backups for volumes and immediately lists backup volume names, sometimes it fails.
When implementing the https://github.com/longhorn/longhorn-manager/pull/985.
The backup_controller is responsible perform the snapshot backup. After the backup is completed, it triggers the backup_target_controller to immediately pull the remote backup target of the new backup volume.
Sometimes, lists the backup volume names https://github.com/longhorn/longhorn-manager/blob/v1.2.0-rc1/engineapi/backups.go#L113 fails with reason can't find the backup volume config in messages field https://github.com/longhorn/longhorn-manager/blob/5aea6ff/engineapi/backups.go#L129-L130.
We did watch the backup volume config is there when the list backup volume names API calls.
Also, for the 1st backup, the backup volume config is generated and then the backup config is generated.
NOTE THAT: it'll impact the time to display the newly created BackupVolume in the Backup page because the backup_target_controller can't get the remote backup volume names at the moment.
To Reproduce

Create 3 volumes
Create a backup of 3 volumes simultaneously
After the 1st volume backup creation is completed, list backup volume names sometimes fail
(I think the problem is that another write operation is performing so listing operation fail)

Expected behavior
List backup volume names should always work
Environment:

Longhorn version: v1.2.0-rc1

Validation: PASSED
Tested with latest image set, both master and v1.2.x lognhorn-manager branch points to master-head,
        - --engine-image
        - longhornio/longhorn-engine:master-head

contains longhorn/longhorn-engine@77e2743 ( included longhorn/backupstore@43c9d3298665680dd2b62bae9f806bd42cbb4cba )
The volume name will now be shown even when the status is in-progress:

v1.2.0-rc1
latest branch with fix


What is INDEX?

What is INDEX here and how we can use it for other languages?
Actually, what portions of code are needed to change?
Please give me the instructions.

@mehadi-trackrep this implementation is just an example (tutorial) to show how to use CTC. You're not likely to go anymore (I mean having state of the art results) with this code.
I updated the code. INDEX is no longer here. Should be clearer now.


Include instance ports in JSON listing

Particularly useful for scripts building connections to the VDI port of an instance.

LGTM.


Cleanup README & Deprecate bosh and yaml2json formula

Cleanup the README as we shutter some older software we no longer support. Specifically, retiring bosh and yaml2json.

Changes look good 👍  Merged


BXMSPROD-1353 nodejs v16.2.0

https://issues.redhat.com/browse/BXMSPROD-1353
The other chance is to change for the whole RHBA repositories https://github.com/kiegroup/droolsjbpm-build-bootstrap/pull/1668

I would wait for fdb from https://github.com/kiegroup/droolsjbpm-build-bootstrap/pull/1668 then we will decide what to do

so https://github.com/kiegroup/droolsjbpm-build-bootstrap/pull/1668 is not working on appformer-js. I would go with this...

@tiagobento @mareknovotny can you please merge? latest execution is from https://github.com/kiegroup/kogito-editors-java/pull/62/commits/8bb5a590b82bfb9caee34f21e64db3db5e20fb42 previous checks were all green

Thanks @Ginxo for the effort. This is blocking QE execution of nighty tests. Please address this asap @tiagobento @mareknovotny


Screenshot Saver fails when "page" is not the default Capybara session

My tests use multiple active sessions (simulating multiple users interacting with each other in real time) - so I've gotten in the habit of instantiating my own Capybara::Session. As a result, I needed to override the default screenshot_and_save_page and screenshot_and_open_image methods to pass in my own session in lieu of the global Capybara.page.
The saver exits early since it checks for a current path from the global capybara reference, and not the page injected into the saver:
      def save
        # if current_path empty then nothing to screen shot as browser has not loaded any URL
        return if capybara.current_path.to_s.empty?

        save_html if @html_save
        save_screenshot
      end

The solution, I believe, is to use the injected page object instead of the global reference. Thoughts?
Pull request to follow.
Also: I think we might see the same problem in save_screenshot if one were to use a different driver in their session than is currently globally registered with capybara
      def save_screenshot
        path = screenshot_path
        clear_save_and_open_page_path do
          result = Capybara::Screenshot.registered_drivers.fetch(capybara.current_driver) { |driver_name|
            warn "capybara-screenshot could not detect a screenshot driver for '#{capybara.current_driver}'. Saving with default with unknown results."
            Capybara::Screenshot.registered_drivers[:default]
          }.call(page.driver, path)
          @screenshot_saved = result != :not_supported
        end
      end

Should this be closed? It looks like the associated PR, #181, has been merged, so I assume this is working/fixed now...


Update tRDM.toml

Description
All previous genesis validators should name their PRs "Update {validator_alias}.toml for tesntet-15" and provide links to previous PRs merged.
My previous PRs:
https://github.com/anoma/namada-testnets/pull/599
https://github.com/anoma/namada-testnets/pull/1226
https://github.com/anoma/namada-testnets/pull/1583
https://github.com/anoma/namada-testnets/pull/2240
If this is an UPDATE for a previous genesis validator
Checks are made against your net_address. If this has changed since the previous testnet, make sure you provide links of previous prs merged from your previous git username.
Thanks in advance!
Checklist before merging

[x] Only one toml is added in this PR
[x] The file being added is indeed a .toml file
[x] The toml being added is to the correct folder, and only to the correct folder
[x] The eth_hot_key and eth_cold_key are present
[x] The email, discord, elements telegram, and twitter fields are present and valid

Successfully validated transactions.toml file for commit hash 96af47a


Bump: 0.17.0-next -> 0.18.0

Proposed changes
This PR bumps FIWARE Big Bang version from 0.17.0-next -> 0.18.0.
Types of changes
What types of changes does your code introduce to the project: Put an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Update only documentation, not any source code.

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of
them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before
merging your code.

[X] I have read the CONTRIBUTING doc
[ ] I have signed the CLA
[X] I have updated the change log (CHANGELOG.md)
[X] I send this pull request to the v0.17.0-next branch.
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)
[ ] Any dependent changes have been merged and published in downstream modules

Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you
did and what alternatives you considered, etc...

Codecov Report
Base: 100.00% // Head: 100.00% // No change to project coverage :thumbsup:

Coverage data is based on head (8f7182b) compared to base (e2d6a10).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@              Coverage Diff               @@
##           v0.17.0-next      #208   +/-   ##
==============================================
  Coverage        100.00%   100.00%
==============================================
  Files                 2         2
  Lines              1746      1746
==============================================
  Hits               1746      1746

Impacted Files
Coverage Δ

config.sh
100.00% <100.00%> (ø)

lets-fiware.sh
100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

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


Fix Linux build

Currently the rpath for libqxcb.so is $ORIGIN/../../libs, which isn't right for finding the Qt5*.so.5 files that it depends on.

Fixed by 017e556


Masonry items stack in the first column to lengths far beyond that of the second column without apparent reason

Current behavior
MasonryFlashList appends items to the first column when they should be dispersed evenly between the first and second columns on a 2-column masonry layout.
Expected behavior
More even column allotments
To Reproduce
Unknown exactly when this occurs or doesn't, but it's rather frequent.
Platform:

[ ] iOS
[x] Android (Possibly affects iOS also?)

Environment
@shopify/flash-list version: 1.4.3 (I understand this is old, but I see no entries in the release history to suggest it is fixed and I will test a newer version as soon as I am able to)

up

Anyone experiencing this should really upvote the initial report comment - because maintainers can sort issues by number of reactions.

same bug on 1.7.1
    "@shopify/flash-list": "^1.7.1",

https://github.com/Shopify/flash-list/issues/1264

solved   by
<MasonryFlashList
  ...
  optimizeItemArrangement={true}
  overrideItemLayout={ (layoutObject, sourceData, ...) => { layoutObject.size = calculateItemHeight(sourceData) } }
/>

@Nantris You need to calculate the height yourself ，Yes, it's not easy to calculate, but you still have to figure out how to calculate it, and flash-list for you will make the performance of the list uncontrollable

It is still just a bug. After updating a piece of data, even if the overrideItemLayout is calculated correctly, a bug will occur
If I don't update one of these, there's no bug, and there's no bug in the append data


Spec 1.14.x 20190710

This message was sent to my personal email address
Sent from my iPhone

On Aug 1, 2019, at 10:33 AM, Richard Berlin<EMAIL_ADDRESS>wrote:
You can view, comment on, or merge this pull request online at:
https://github.com/roofpig95008/gosu-lang/pull/7
Commit Summary
fixes for studio gosu tests
Merge remote-tracking branch 'upstream/spec-1.14.x' into spec-1.14.x
Changes to make tests pass
File Changes
M gosu-core/src/main/java/gw/internal/gosu/parser/ContextInferenceManager.java (14)
M gosu-core/src/main/java/gw/internal/gosu/parser/GosuParser.java (64)
M gosu-test/src/test/gosu/gw/specContrib/blocks/Errant_BlocksReturnTypeCheck.gs (2)
M gosu-test/src/test/gosu/gw/specContrib/classes/property_Declarations/obsoleteGetterSetterMethodCalls/Errant_PropertyGetterMethodCalls.gs (10)
M gosu-test/src/test/gosu/gw/specContrib/enhancements/Errant_EnhancedClass.gs (2)
M gosu-test/src/test/gosu/gw/specContrib/expressions/cast/Errant_AutomaticDowncastingTest.gs (4)
M gosu-test/src/test/gosu/gw/specContrib/generics/Errant_CompoundTypeWithTypeVar.gs (2)
M gosu-test/src/test/gosu/gw/specContrib/statements/usesStatement/Errant_AmbiguousStaticImports1.gs (10)
M gosu-test/src/test/gosu/gw/specContrib/statements/usesStatement/Errant_AmbiguousStaticImports2.gs (10)
M gosu-test/src/test/gosu/gw/specContrib/statements/usesStatement/Errant_AmbiguousStaticImports3.gs (8)
M gosu-test/src/test/gosu/gw/specContrib/statements/usesStatement/Errant_StaticImportsGenericMethods.gs (4)
M gosu-test/src/test/gosu/gw/specContrib/statements/usesStatement/Errant_StaticImportsOverriddenMethods.gs (2)
M gosu-test/src/test/gosu/gw/specContrib/statements/usesStatement/StaticImportExplicitTest.gs (38)
M gosu-test/src/test/gosu/gw/specContrib/statements/usesStatement/StaticImportOnDemandTest.gs (40)
M gosu-test/src/test/gosu/gw/specContrib/statements/usesStatement/StaticImportTest.gs (2)
M gosu-test/src/test/gosu/gw/specContrib/typeinference/Errant_DiamondInference.gs (2)
M gosu-test/src/test/java/gw/lang/GosuScratchSuite.java (3)
Patch Links:
https://github.com/roofpig95008/gosu-lang/pull/7.patch
https://github.com/roofpig95008/gosu-lang/pull/7.diff
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Is there any way to use the setSinkId() using multitrack?

Wavesurfer.js version(s):
Beta
Browser and operating system version(s):
Electron
Description
I'm making a track mixer where you should be able to pre-listen your mix (before it goes live), but you might want to assign this on a different audio device. I was wondering if there is a possibility to use setSinkId() in a multitrack and if so, how can I do this?
Thanks in advanced.

You can set a sink id on wavesurfer's media element directly like this:
wavesurfer.getMediaElement().setSinkId(sinkId)

If you're asking about https://github.com/katspaugh/wavesurfer-multitrack, there you can set it on the multitrack object.


problems about num_workers setting

when I run ./scripts/mushroom.sh , it prints a warning: The 'train_dataloader' does not have many workers which may be a bottleneck. Consider increasing the value of the num_workers argumenttonum_workers=223in theDataLoader` to improve performance.
I wonder where can I modify num_workers? I guess I can find it here SketchDream/threestudio/data, but there are lots of scripts in this folder, should I modify all of them? I also see some comments like # Multi-process, more quickly, with small bug now in SketchDream/threestudio/data/random_multiview_control_depth.py. Is it relates to this problem?

We currently do not suggest to use multi-process with num_worker>0 for dataloader. This problem is inherited from three-studio.
If directly setting num_worker>0, when changing the image render size or other settings, it will not work.
I have tried to utilize some synchronous tips, but it occasionally caused zombie process. Those comments are related to it and you can try it by yourself.


Add JDCloud to adopters of zh

What type of PR is this?

What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:

Hi @wangxf1987 did you encounter any problems during the submission process?


Look into spec failure, setup CI

Per @joatca on #4, specs are failing on master.
Possibly an intermittent failure? I can't reproduce, but possibly it will reproduce on CI.

By the way, your final test "sequence number" always fails on my system. The first two pings seem to both come back with sequence number 0.

Some more info:
If I change HOST to be "<IP_ADDRESS>" the test succeeds every time. With HOST="<IP_ADDRESS>" it fails every time. I have kernel 4.15.3-2-ARCH which is obviously quite new - maybe there is a peculiarity on very recent kernels, or on the Arch kernel? Which kernels are you testing against?


Compatibility with qsessions

Recent versions of https://github.com/QueraTeam/django-qsessions causes a failure.
It seems a common class of possible problems.
https://github.com/QueraTeam/django-qsessions/commit/120ba23f4b995e3234170c7df28c99c296e59b1d
It would be great if orm_admin.py get_models skipped models it can not load.
Traceback (most recent call last):
  File "/home/python3.8/lib/python3.8/site-packages/django/contrib/staticfiles/handlers.py", line 68, in __call__
    return self.application(environ, start_response)
  File "/home/python3.8/lib/python3.8/site-packages/django/core/handlers/wsgi.py", line 133, in __call__
    response = self.get_response(request)
  File "/home/python3.8/lib/python3.8/site-packages/django/core/handlers/base.py", line 75, in get_response
    response = self._middleware_chain(request)
  File "/home/python3.8/lib/python3.8/site-packages/django/core/handlers/exception.py", line 36, in inner
    response = response_for_exception(request, exc)
  File "/home/python3.8/lib/python3.8/site-packages/django/core/handlers/exception.py", line 90, in response_for_exception
    response = handle_uncaught_exception(request, get_resolver(get_urlconf()), sys.exc_info())
  File "/home/python3.8/lib/python3.8/site-packages/django/core/handlers/exception.py", line 125, in handle_uncaught_exception
    return debug.technical_500_response(request, *exc_info)
  File "/home/python3.8/lib/python3.8/site-packages/django_extensions/management/technical_response.py", line 37, in null_technical_500_response
    six.reraise(exc_type, exc_value, tb)
  File "/home/python3.8/lib/python3.8/site-packages/six.py", line 702, in reraise
    raise value.with_traceback(tb)
  File "/home/python3.8/lib/python3.8/site-packages/django/core/handlers/exception.py", line 34, in inner
    response = get_response(request)
  File "/home/python3.8/lib/python3.8/site-packages/django/core/handlers/base.py", line 115, in _get_response
    response = self.process_exception_by_middleware(e, request)
  File "/home/python3.8/lib/python3.8/site-packages/django/core/handlers/base.py", line 113, in _get_response
    response = wrapped_callback(request, *callback_args, **callback_kwargs)
  File "/home/python3.8/lib/python3.8/site-packages/django/utils/decorators.py", line 130, in _wrapped_view
    response = view_func(request, *args, **kwargs)
  File "/home/python3.8/lib/python3.8/site-packages/django/contrib/auth/decorators.py", line 21, in _wrapped_view
    return view_func(request, *args, **kwargs)
  File "/home/python3.8/lib/python3.8/site-packages/data_browser/views.py", line 116, in query_html
    config = _get_config(request)
  File "/home/python3.8/lib/python3.8/site-packages/data_browser/views.py", line 77, in _get_config
    orm_models = get_models(request)
  File "/home/python3.8/lib/python3.8/site-packages/data_browser/orm_admin.py", line 323, in get_models
    _get_fields_for_model(request, model, model_admins[model], admin_fields)
  File "/home/python3.8/lib/python3.8/site-packages/data_browser/orm_admin.py", line 289, in _get_fields_for_model
    orm_field = _get_calculated_field(
  File "/home/python3.8/lib/python3.8/site-packages/data_browser/orm_admin.py", line 165, in _get_calculated_field
    field_func = getattr(admin, field_name, None)
TypeError: getattr(): attribute name must be string

So you have something in list_display, fields or fieldsets which isn't a string? For my context I don't suppose you know what it is and where?

oh, I missed the commit link, thanks for that, I always forget that callables in list_display is even a thing, I wonder if I can support those the same way I support functions on the admin class

I've fixed support for callables in list_display, that will be in the next release. However the JS won't trust the HTML so the link they are inserting will not actually render as a link. If that's a problem you might want to use ddb_hide_fields to hide that field.

As always thanks for the report.

Sounds looks an appropriate approach.  Thanks for fixing.

I fixed the HTML thing as well and in the process found a nice little bit of refactoring.


Page Refreshes: targets in stimulus seems to use old values

I test page refreshes on a small project. the project uses https://github.com/stimulus-components/stimulus-rails-nested-form
I have <template> tag that has some attributes preset. The presets change according to user actions that triggers new page content from server response. After activating morph I noticed the

Thank you for opening this issue.
From a Stimulus perspective, Controllers shouldn't be doing any property caching or memoization of their targets. Every time a this.[name]Target or this.[name]Targets property is accessed, the controller should query its scope to find the appropriate elements. Neither morphing nor full-page reloading shouldn't be affecting that logic, since it's a fetch each time.
With that in mind, I wonder what's preventing changes to the target's attributes during the morph. Could you share some more details about your project, particularly the changes you've layer on top of what's provided by https://github.com/stimulus-components/stimulus-rails-nested-form?

After having a look in stimulus code one can see classes such as TargetObserver, TargetSet, which strongly suggests that there is target caching. It might be kept here this.targetsByName = new Multimap();
https://github.com/hotwired/stimulus/blob/main/src/core/target_observer.ts#L53

the element itself (this.element) seems to be preserved, so no wonder why querying within does return invalid values:

isn't it related to this issue https://github.com/bigskysoftware/idiomorph/issues/15 ?
looks like Idiomorph won't update <template> elements

@meceo Thank you for clarifying, and thank you @adrienpoly for linking to https://github.com/bigskysoftware/idiomorph/issues/15.
I think Turbo could incorporate explicit <template> element support as part of its call to Idiomorph.morph.

FWIW, I'm working on an optimistic UI implementation using <template> containing turbo stream actions that are rendered inline. Currently this fails for the same reason, <template> tags not being merged by Idiomorph. It's certainly a bit of an edge case, but could be powerful, if <template> tags were reconciled with the rest of the DOM.

@meceo Thank you for clarifying, and thank you @adrienpoly for linking to bigskysoftware/idiomorph#15.
I think Turbo could incorporate explicit <template> element support as part of its call to Idiomorph.morph.

@jorgemanrubia would you accept a PR for this? Not supporting <template> elements is a pretty big gotcha :(

@meceo Thank you for clarifying, and thank you @adrienpoly for linking to bigskysoftware/idiomorph#15.
I think Turbo could incorporate explicit <template> element support as part of its call to Idiomorph.morph.

You can implement a callback similar to the one suggested here by connecting to the turbo:morph event.

I've opened https://github.com/bigskysoftware/idiomorph/pull/49 to try and resolve this issue in the upstream dependency.
In the meantime, like @ghiculescu suggests something like this snippet might suffice as a backwards-compatible workaround (replacing turbo:morph with turbo:morph-element):
addEventListener("turbo:morph-element", ({ target, detail: { newElement } }) => {
  if (target instanceof HTMLTemplateElement && newElement instanceof HTMLTemplateElement) {
    target.innerHTML = newElement.innerHTML
  }
})

I'm experiencing a similar issue in one of my pages.
I can see at the HTML (see Elements) that the dom element does not include data-information-referral--sessions--client-caller-selected-client-person-id-value="2492" (I confirm this is the only element in the HTML, I don't have any duplicate and no place in the HTML you can find  data-information-referral--sessions--client-caller-selected-client-person-id-value="2492")
However, if you look at this.element and this.selectedClientPersonIdValue, it is showing information from a previous page experience. It's not reading current DOM. I have a breakpoint to catch it

export default class extends CustomAutocomplete {
  static targets = ['personFieldContainer', 'personField']
  static values = {
    selectedClientPersonId: String,
    selectedContactCallerPersonId: String,
    selectedProfessionalCallerPersonId: String,
  }

  connect() {
    this.selectedClientPersonId = this.selectedClientPersonIdValue
    this.selectedContactCallerPersonId = this.selectedContactCallerPersonIdValue
    this.selectedProfessionalCallerPersonId = this.selectedProfessionalCallerPersonIdValue

    this.selectPerson = this.selectPerson.bind(this)
    this.unselectPerson = this.unselectPerson.bind(this)
    this.clearOrUnScopeCallerField = this.clearOrUnScopeCallerField.bind(this)

    this.element.addEventListener('autocomplete.change', this.selectPerson)
    this.element.addEventListener('autocomplete.clear', this.unselectPerson)
    document.addEventListener('clear-callers-field', this.clearOrUnScopeCallerField)
  }

  disconnect() {
    this.element.removeEventListener('autocomplete.change', this.selectPerson)
    this.element.removeEventListener('autocomplete.clear', this.unselectPerson)
    this.element.removeEventListener('clear-callers-field', this.clearOrUnScopeCallerField)
   }

   ...
}

https://github.com/bigskysoftware/idiomorph/pull/49 has been merged upstream into Idiomorph, and is likely to be part of the next release.

You’re the man @seanpdoyle 👊


[Feature]: Add unit tests into GH check

Checklist

[X] I've searched for similar issues and couldn't find anything matching
[X] I've discussed this feature request in the K8sGPT Slack and got positive feedback

Is this feature request related to a problem?
No
Problem Description
No response
Solution Description
In order to improve our visibility on any issues, we should take the go test ./... results as a metric for PR/branch health by adding them into GH checks.
Benefits
This would improve our frequency of testing and add a quality gate.
Potential Drawbacks
No response
Additional Information
No response

Hey @AlexsJones, can you please help me out here?

Yes, apologies for the delay, it was added by @thschue  prior to me commenting


chain.run threw 403 error

I'm using the pipeline for Q&A pipeline on non-english language:
pinecone.init(
    api_key=PINECONE_API_KEY,  # find at app.pinecone.io
    environment=PINECONE_API_ENV  # next to api key in console
)
index_name = "langchain2"
embeddings = OpenAIEmbeddings(openai_api_key=OPENAI_API_KEY)

docsearch = Pinecone.from_existing_index(index_name=index_name, embedding=embeddings)

llm = OpenAI(temperature=0, openai_api_key=OPENAI_API_KEY)
chain = load_qa_chain(llm, chain_type="stuff")

query = "QUESTION"
docs = docsearch.similarity_search(query, include_metadata=True)

res = chain.run(input_documents=docs, question=query)
print(res)

It stucks in res = chain.run(input_documents=docs, question=query) lane. I'm waiting for ~20 mins already. What's the reason for that and how to investigate?

UPD
After ~30 mins I got
Retrying langchain.llms.openai.completion_with_retry.<locals>._completion_with_retry in 4.0 seconds as it raised Timeout: Request timed out: HTTPSConnectionPool(host='api.openai.com', port=443): Read timed out. (read timeout=600).

What's the reason for that and how can I fix it?

This looks like an issue with the upstream API and not LangChain itself. LangChain is not responsible for upstream API availability or rate limiting policies.

@dlqqq How can I set a limit for response time? I'm using signal library from python. Wondering If there are alternative ways

@mzhadigerov Unfortunately, a quick glance at the pinecone.py source seems to show that there isn't timeout support at the moment for Pinecone. The community is still working to bring timeouts to classes throughout the repo: https://github.com/hwchase17/langchain/pull/1798

sorry @dlqqq ,but what it has to do with pinecone? The problem arises in openai side, not in pinecone side. Please, correct me If I misunderstood you.

@mzhadigerov Can we close this issue?


Handle DPI scaling in SetSize

Fix wailsapp/wails#968

Fantastic! Testing DPI is super hard so appreciate this greatly!

Let me know if you're able to pick up the changes via go get -u. I've found the update process very flakey and sometimes have had to wait an hour to pick up new modules.

This PR broke windows 7 support, so #5 should change how it's handled depending on the presence of shcore.dll.


[Android] Unchecked exceptions' messages should be corrected

IllegalStateExceptions messages syntax can be improved. Moreover we can inform user that he should call createClient first instead of informing about some unknown "BleManager".
PR 1# discussion
PR 2# discussion
PR 3# discussion
PR 4# discussion

Cleanup - closing old Issues.
Please open new one if this is still valid.


🐉 Hear Ye, Brave Adventurers! - Dungeon Master GPT

In the realm of code and fantasy, a new quest beckons. I am the Dungeon Master, guardian of tales and weaver of the fantastical world of Dungeons & Dragons 5th Edition. My realm is one of uncharted maps, mysterious NPCs, and epic battles, all brought to life through the magic of GPT technology.
But every great adventure needs heroes. That's where you come in. I am seeking intrepid souls to embark on a journey of beta-testing. Your mission? To explore the depths of this digital realm, encounter its wonders and perils, and report back with your findings.
As a beta tester, you will:
Traverse enchanted lands and generate maps that have never been seen before.
Interact with a myriad of non-player characters, each with their own stories to tell.
Engage in battles, testing your strategic might with our unique battle map generator.
Delve into the rich lore of D&D 5E, with rules and guides at your fingertips.
Your feedback will be the lodestar that guides this Dungeon Master in refining this realm to perfection.
To join this quest, follow the link below. Your journey into the heart of an enchanted world awaits!
(https://chat.openai.com/g/g-8l13Uo8to-dungeon-master)
Together, let's craft a tale worth telling for ages to come!
🐲 Dungeon Master Awaits Your Valor! 🏰

Merged


fix htmlinputstream, tokenizer to use codepoints and build strings as late as possible

There's a todo explaining, but I think we can radically simplify this class and base it on codepoints instead of building up string chunks. I'd also like to remove the RegExp that is used for "charsUntil"
This could be done in two phases also, first simplify inputstream then tokenizer

This issue has been moved to dart-lang/html#30.


feat: support environment variables in manager

This PR adds support for configuration of additional environment variables needed  to configure Opentelemetry-Operator Manager. Thanks to that WATCH_NAMESPACE variable can be configured during chart deployment.
Functionality:

If values.manager.env is empty then env is not added to the manager deployment (default)
If values.manager.env contains map (KEY: value) then it's added to the manager deployment as k8s env obj

@dmitryax another use case for expanding the values.schema.json for operator charts?

Yes, indeed


Socket Exception (Forbidden access)

**

**
i get this error in windows

Me too. Same error message...

(1) Try to start this app as admin
(2) Check in task manager if there is already another instance
(3) Use the latest version (v1.7.0) and check if it has been fixed

(1) Try to start this app as admin (2) Check in task manager if there is already another instance (3) Use the latest version (v1.7.0) and check if this has been fixed

I am sure that I followed all of your steps but it still goes wrong.

(1) Try to start this app as admin (2) Check in task manager if there is already another instance (3) Use the latest version (v1.7.0) and check if this has been fixed

Start with administrator privileges and still report an error

+1

 Me too. Same error message...

me too
版本	Windows 10 专业版
版本号	21H2
安装日期	2020/7/24
操作系统内部版本	19044.2075
体验	Windows Feature Experience Pack 120.2212.4180.0

Me too, but I changed the port to 52319 and successfully connected

Same with @weijen6 , I changed the default port to another random port then it's working.

53317 seem to be a bad choice as there is a small possibility that it is used as a "ephemeral port" (temporary port).
I guess a proper fix for this is to use a lower number port and use 53317 as fallback.

Looks like this default port 53317 is reserved by Windows and other potential applications.
Below is the port reserved list of my runtime.  (Windows 11 Pro 1000.22640.1000.0)
So any port in the below range will run into the same issue. In my case, I changed to 59998 and it works well.

netsh interface ipv4 show excludedportrange protocol=tcp

Protocol tcp Port Exclusion Ranges
Start Port    End Port

  5357        5357
 49675       49774
 49875       49974
 50000       50059     *
 50060       50159
 52683       52782
 52814       52913
 53287       53386
 59865       59964
 62040       62139
 62140       62239
 62240       62339
 62340       62439
 62440       62539
 62540       62639
 62640       62739

I have the same problem, but I find that the port 53317 is like blocked by localsend itself...
Using netstat -ano|findstr 53317 in cmd and I can find the PID of the process blocking the port, and right after that I killed it, localsend quitted.

Phone2Mac:
DioError [unknown]: null
Error: SocketException: No route to host (OS Error: No route to host, errno = 113), address = <IP_ADDRESS>, port = 39840
Mac2Phone:
DioError [connection timeout]: The request connection took longer than 720:00:00.000000. It was aborted.
Error: SocketException: Operation timed out (OS Error: Operation timed out, errno = 60), address = <IP_ADDRESS>, port = 56128

I had the same problem and fixed it by creating an inbound rule in Firewall settings for this app. It's working perfectly now

Me too, but I changed the port to 52319 and successfully connected

much appreciated!

Changing to another port number like 52199 on both devices works for me.

Looks like this default port 53317 is reserved by Windows and other potential applications. Below is the port reserved list of my runtime. (Windows 11 Pro 1000.22640.1000.0)
So any port in the below range will run into the same issue. In my case, I changed to 59998 and it works well.

netsh interface ipv4 show excludedportrange protocol=tcp

Protocol tcp Port Exclusion Ranges
Start Port End Port ---------- -------- 5357 5357 49675 49774 49875 49974 50000 50059 * 50060 50159 52683 52782 52814 52913 53287 53386 59865 59964 62040 62139 62140 62239 62240 62339 62340 62439 62440 62539 62540 62639 62640 62739

3Q，this is correct. I checked my TCP port Exclusion Ranges and it is different.

(1) Try to start this app as admin
(2) Check in task manager if there is already another instance
(3) Use the latest version (v1.7.0) and check if this has been fixed

Very good keep up the good work

52319 worked for me

I had the same issue and I tried
net stop winnat

It works for me.
(Found at https://superuser.com/a/1610009)

I had the same issue and I tried
net stop winnat

It works for me. (Found at https://superuser.com/a/1610009)

Thanks bro, after running this code, I can use port 53317 to transfer files normally.

Me too, but I changed the port to 52319 and successfully connected

Me too. Thanks!

Just faced this issue as well, restarting Internet Connection Sharing from services fixed it immediately, didn't even need to restart localsend, was able to start the server from localsend's settings right away.

Looks like this default port 53317 is reserved by Windows and other potential applications. Below is the port reserved list of my runtime. (Windows 11 Pro 1000.22640.1000.0)
So any port in the below range will run into the same issue. In my case, I changed to 59998 and it works well.

netsh interface ipv4 show excludedportrange protocol=tcp

Protocol tcp Port Exclusion Ranges
Start Port End Port ---------- -------- 5357 5357 49675 49774 49875 49974 50000 50059 * 50060 50159 52683 52782 52814 52913 53287 53386 59865 59964 62040 62139 62140 62239 62240 62339 62340 62439 62440 62539 62540 62639 62640 62739

Same case for Win 10 22H2. 53291       53390 is reserved on my computer.

If you're using windows:
Search Network status then find Network reset click then restart your pc.
WARNING: This would erase saved wifi passwords and other network settings.

I faced this issue too.
I changed port and it worked now
btw dont forget change port on Android

I faced this issue too.
I changed port and it worked now
btw dont forget change port on Android

Just encountered this. I just rebooted the PC, and it fixed it

Just adding a data point:
Just encountered this bug on Windows 11 Pro, 23H2. I do have Hyper-V installed on this machine (I notice in the thread that Hyper-V has been brought up.
I fixed it by changing both the desktop and my iOS device to port 52319 as mentioned in this thread.

change port and it will work as usual

win 19 22H2 can't run
以一种访问权限不允许的方式做了一个访问套接字的尝试

The primary reason for this to happen more often than expected is because the high port numbers are used as "ephemeral ports".
I think https://github.com/localsend/protocol/issues/12 will resolve this issue.

@Tienisto a single fallback does not solve it, manually changed to 53318, or 53319, or 53320, or 53321, or 53330, 53340, 53350 but exact same error.
Nothing is occupying these ports on my system, these are reserved for Windows:
> netsh interface ipv4 show excludedportrange protocol=tcp

Protocol tcp Port Exclusion Ranges

Start Port    End Port
----------    --------
     49693       49792
     49793       49892
     49893       49992
     50000       50059     *
     50060       50159
     50160       50259
     51113       51212
     51585       51684
     51685       51784
     51785       51884
     51885       51984
     51985       52084
     52085       52184
     53087       53186
     53217       53316
     53317       53416
     53417       53516

Jumping more helps, but LocalSend either needs to parse this exclusion table, or simply keep jumping until a port is found.

Note that you can add an exception for port 53317 this way (in an elevated Powershell or CMD):
net stop winnat
netsh int ipv4 add excludedportrange protocol=tcp startport=53317 numberofports=1
net start winnat

When running netsh interface ipv4 show excludedportrange protocol=tcp again, you should see that port 53317 appears on its own line and with a star (that, I guess, means that is an exception you added yourself) :
PS C:\Users\xxx> netsh interface ipv4 show excludedportrange protocol=tcp

Protocole tcp Plages d'exclusion de ports

Port de début    Port de fin
-------------    -----------
[...]
     53317       53317     *
[...]

* - Exclusions de ports administrés.

@baviereteam your solution did work? can you explain what did it do?


Unset API keys are not handled properly

I noticed that in the current main branch, mistral is always activated by default. That of course causes a problem if the API key is not actually set. Similar case also for the OpenAI key.
In you case you don't already have a fix for that in some branch, I could create a PR for that.

Would love to get a PR to fix that :)

Good catch. I edited the config. Now, there will be an error about env API_KEY not set only if you are trying to use this provider.
Let me know if you managed to make it work for you!

Thanks! Yes, I made that work for me by simply setting the default for mistral to false in the game init. Cool, then I guess I don't need to make a PR anymore after all :)


Move "internal login" system to be a module

Move "internal login" system to be a module using pre/post hooks.

After talking to @brittballard and @calebthompson, modularizing the login system would be a bad idea.
Sticking with devise though, we could just create devise modules to be installed as gems. Hopefully most customers will be using a technology that already has a devise module written like LDAP, SSO or OAuth. But for other customers we may have to write a devise module implementing their authentication method.

Well, Devise is still module, it's just a different module.  Can you please start the process to get the internal system, and oauth to use Devise exclusively, then work on LDAP (https://github.com/projectjellyfish/api/issues/115)

So, let's make sure we are using Devise for everything, and then make some modules for it (and document how they work)


Add tooltips

Implemented in https://github.com/OSVR/OSVR-Config/commit/7c47085a279162a8f75b68823de24ae9d2acc8f6.
Used helptext in place of tooltips.


Experiment with property testing

This is a fix for https://github.com/chalk-diagrams/chalk/issues/109
I tried to follow the haskell doc string more closely. The issue is how traces and envelopes should behave for non-unit vectors.
Unit tests assert that envelopes should bound traces from the origin. I believe this property is correct since each trace represents exactly one point on the left hand side of this equation.
‖proj(u, v)‖ / ‖v‖ ≤ dia.envelope(v)
for all dia, u ∈ dia and v ∈ R²

One issue I ran into in this PR is that python complains about recursion limit more often now. Might need to make sure that some of the core transforms use less recursion.

One issue I ran into in this PR is that python complains about recursion limit more often now.

I guess this happens because now the envelope is wrapped twice (self is called twice now, once in apply_linear and once in apply_translation; while before it was called only a single time)? Other than that, I don't see what could cause the RecursionError compared to the previous code.

Yup, good catch. I will fix that. It seems like recursion is fine in general, but we should be careful in the core library that gets called everywhere.

Yup, good catch. I will fix that.

Yeah, that's unfortunate; I liked the logic separation into apply_translation and apply_linear that you had previously introduced.

It seems like recursion is fine in general, but we should be careful in the core library that gets called everywhere.

Agreed!
A couple minor points:

Could we also pass the tests directory to black, isort, flake, etc. in the Makefile?
There are two remnant print statements in frame from padding.py, which probably where used for debugging and could be removed.

Other than that very nice job on the tests! They were much needed.

Good point. I was able to type check the tests as well. Hypothesis is a really nice library.
Now that we have a way to sample diagrams, might be interesting to think up some of the other properties to check in the core lib. For example, how should besides change the envelopes and trails. (it's possible someone has done this already as well).


feat(page): add fill/no-fill modifiers for main-section elements

fixes https://github.com/patternfly/patternfly-next/issues/1492

Deploy preview for pf-next ready!
Built with commit<PHONE_NUMBER>a3a5404187062963819493a36826bd
https://deploy-preview-1689--pf-next.netlify.com

@mcoker what do you think about adding the pf-m-fill/pf-m-no-fill modifiers to the page component to demonstrate how they work?

@christiemolloy good idea, added.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Update DomainOffensive certbot plugin

Summary
This PR replaces the current DomainOffensive (do.de) cert bot with the new official version.
The current do certbot repo has been forked by DomainOffensive and seems to be the official bot now.
Changes
Basically i have replaced the current certbot-dns-plugins config with the new repository and python package.
Looking into the new repository of DomainOffensive, i don't see any new additions or changes, yet i think using the official certbot seems to be a good thing for future versions.

@FabianK3 are you able to use the docker image mentioned to conduct your tests?

Can I ask then, why do you want to update this dns plugin when you don't use it?

@jc21 Perhaps i didn't put it clearly enough!
I am planning on using this provider as i am owning domains on said provider.
I'll use the provider within NPM in my home lab, but i currently have not the time to get going with it.
As for why i updated the provider: I am sure the current provider implementation does what it is supposed to do. From a conversation with the do.de provider support i was informed that they do provide an API and linked me to their certbot implementation. I then realized it was a new fork in their name of the current provider used in NPM and my thought was it may be more future-proof to use their own fork instead of the current should any changes arise in the future.
Tl;dr: I have relations to do.de and i like to give back to this project. :)
(Merry Christmas!)

Ok great I'll wait for you (or someone) to test it then.
If you would like CI to rebuild the PR docker image for you, simply leave a comment here with only this text in the body:
rebuild


Refactor library architecture

This library has a few design problems and it is very hard to extend and improve functionality.
Small TODO and first steps:

[ ] Use dependency injection and service container
[ ] Drop abstract classes and static calls (mostly for Request and DB), or wrap them inside facades
[ ] Introduce Config class and remove configuration logic from Telegram class
[ ] Remove Botan integration from core library and add as a package (?)

I forgot some details in current library implementation and I will have some questions. Lets discuss them in this thread
cc @php-telegram-bot/developers

Not sure if some kind of simple event handlers or hooks wouldn't be better.
DB could be 100% add-on powered by events/hooks.

@php-telegram-bot/developers what is a point of call useGetUpdatesWithoutDatabase? We already have checks for DB::isDbConnected() in the https://github.com/php-telegram-bot/core/blob/master/src/Telegram.php#L332
Can anyone explain please?

It was made that way so that running getUpdates without DB isn't default behaviour, forcing developer to take action before it can be used

@jacklul

forcing developer to take action before it can be used

maybe we should force developers via documentation and not via code?

Hi @akalongman
I honestly don't understand why the big redesign on v1. I though that was the whole idea of v2, to leave v1 pretty much as is and build v2 with a better base.
Restructuring v1 will make it even more confusing/difficult for users, as they'll have to change all their code to adapt to this, and then later again for v2, when it's reched a stable point. Also all documentation snippets that have accumulated in the issues will be invalid, meaning there will potentially be a lot of new "repeat" issues popping up.
My idea was to just have a better DB management with an ORM implemented, so that at least the DB layer is more usable/extendable, especially when updating table structures etc.
Also I don't quite understand why another style guide change :confused:
Apart from that, this looks like a great base for v2 :grin:

@noplanman

I honestly don't understand why the big redesign on v1. I though that was the whole idea of v2

When stable version is not released, any BC changes is normal and acceptable, but release version is not defined yet, we can name it anything :blush: Lets discuss this in the TG

My idea was to just have a better DB management with an ORM implemented, so that at least the DB layer is more usable/extendable, especially when updating table structures etc.

Implementing of that in current codebase is almost impossible :disappointed:

Also I don't quite understand why another style guide change

In final I want to make code compatible with new PSR-12 coding standard

@akalongman Well, I'm 100% fine with removing that method and using "no database" mode when DB is not connected by default.


Found CVEs in your dependencies

Hi, I noticed that your project are using vulnerable libraries which are related to some CVEs. I suggest a library update to avoid potential risks. Please look into the details below.

Vulnerable Library Version: com.fasterxml.jackson.core : jackson-databind : <IP_ADDRESS>
CVE ID: CVE-2020-8840, CVE-2019-20330
Import Path: unirest/pom.xml, object-mapper-jackson/pom.xml
Suggested Safe Versions: 2.10.0, 2.10.1, 2.10.2, <IP_ADDRESS>

Hi this project already doesn't use <IP_ADDRESS>


Refactor to use dynamic imports

Dynamic imports are well supported across modern browsers and can be made asynchronous in order to massively reduce upfront JS download speeds.

Gonna roadmap this for next major version. Means losing IE support in base Felafel, but who really wants that anyway? 😋


Disk unreadable after moving the network [Duplicate][1.12.2]

Issue description:
I had a little network in my base (Fluid grid + Grid + Controller + Disk drive) with 1 4K storage disk, and a 64k Fluid storage disk. And I just decided to change my base's location, so I took my drives in the disk drive, and moved. Then, I reinstalled the entire network, putted the disks back in, and opened the grid.
What happens:
The items didn't show up. I tough I did it wrong, but no. Note that If i add new items they show up and no issue with them. But all the old ones are totally out of reach. I even tried in creative mode to get the items out of this cell trough a disk manipulator, nothing. (Note that the items inserted after the bug occurs had been transferred, it only locks on the others.
What you expected to happen:
I expect the items stored in the disk to show up.
Steps to reproduce:
I don't know. It only happens a very few times.
Version (make sure you are on the latest version before reporting):

Minecraft: 1.12.2
Forge:<IP_ADDRESS>07
Refined Storage:1.5.34

Does this issue occur on a server? yes
Others infos
I tried using the latest version compiled from github on the server, nothing changed.
Here is the complete mod list (serverside) :
Chisel-MC1.12.2-<IP_ADDRESS>.jar
CoFHCore-1.12.2-<IP_ADDRESS>-universal.jar
CoFHWorld-1.12.2-<IP_ADDRESS>-universal.jar
CodeChickenLib-1.12.2-<IP_ADDRESS>4-universal.jar
ExtremeReactors-1.12.2-<IP_ADDRESS>.jar
LuckPerms-Sponge-4.2.25.jar
Mantle-1.12-<IP_ADDRESS>.jar
Nucleus-1.4.0-S7.0-MC1.12.2-plugin.jar
OpenComputers-MC1.12.2-<IP_ADDRESS>.jar
RedstoneFlux-1.12-<IP_ADDRESS>-universal.jar
SimplyJetpacks2-1.12.2-<IP_ADDRESS>.jar
TConstruct-1.12.2-2.10.1.DEV.GITBORK.jar
ThermalDynamics-1.12.2-<IP_ADDRESS>-universal.jar
ThermalExpansion-1.12.2-<IP_ADDRESS>-universal.jar
ThermalFoundation-1.12.2-<IP_ADDRESS>-universal.jar
environmentaltech-1.12.2-2.0.11a.jar
foamfix-<IP_ADDRESS>-1.12.2-law.jar
jei_1.12.2-<IP_ADDRESS>.jar
refinedstorage-1.5.34.jar
spongeforge-1.12.2-2705-7.1.0-BETA-3151.jar
valkyrielib-1.12.2-2.0.11a.jar
woot-1.12.2-1.3.0.jar
zerocore-1.12-<IP_ADDRESS>.jar

Don't make duplicate issues if you know you're making a duplicate issue.
This is a Forge bug.
But I've worked around it in development versions. Coming soon.


Test Code Lens appears in a strange place

Environment data

VS Code version: 1.34.0
Extension version (available under the Extensions sidebar): 2019.4.12954
OS and version: Windows 10 v. 1809
Python version (& distribution if applicable, e.g. Anaconda): 3.5.2 64-bit without Conda
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): I guess I have no venv set up.
Relevant/affected Python packages and their versions: Pytest

Actual behaviour
"Run Test | Debug Test" Code Lens appears in a strange place appears in a strange place

Expected behaviour
Test Code Lens should appear right above the method
Steps to reproduce:
The Code Lens starts moving when I copy and paste the lines from test parametrization
Logs
Output for Python in the Output panel
Starting Jedi Python language engine.
##########Linting Output - pylint##########
************* Module test_predction_test_case_collection
settings.json for Python

Hi @chudytom,

The Code Lens starts moving when I copy and paste the lines from test parametrization

Unfortunately I am not able to reproduce it when I copy and paste the lines into test parametrization. Please could you upload a GIF of this step, maybe I am not understanding something right.
Also, a code sample for the test would help.

I tried to reproduce it with a smaller example and currently I can't. Maybe it was fixed in a newer version of VS Code/Python extension/Language Server. I'm closing it for now. If the situation happens again I'll let you know.


Got empty response for: external.metrics.k8s.io/v1beta1

Description

We're getting error:
[memcache.go:206] couldn't get resource list for external.metrics.k8s.io/v1beta1: Got empty response for: external.metrics.k8s.io/v1beta1
...when applying BotKube v0.15.0.
We have KEDA deployed across several clusters. What we've found is that BotKube deployment will break if external.metrics.k8s.io/v1beta1 returns an empty list. We try to keep all of our clusters in-sync, but there are a few clusters that will intermittently use KEDA.
Is there a way we can add "ignore empty lists" logic somewhere? Thanks!
Expected behavior
level=info msg="Using API Key starting with \"xUd\"..." component="Analytics reporter"
level=info msg="Registering filter \"ObjectAnnotationChecker\" (enabled: true)..." component="Filter Engine"
level=info msg="Registering filter \"NodeEventsChecker\" (enabled: true)..." component="Filter Engine"
level=info msg="Starting server on address \":2112\"" component="Metrics server"
level=info msg="Loaded resource mapping: ... component="Resource Name Normalizer"
level=info msg="Skipping waiting for Config Watcher sync..." component="Config Watcher Sync"
level=info msg="Starting bot" bot=Slack commGroup=default-group
level=info msg="Starting server on address \":2113\"" component="Lifecycle server"
level=info msg="Starting controller..." component=Controller
level=info msg="Starting checker" component="Upgrade Checker"
level=info msg="Sending welcome message..." component=Controller
level=info msg="Botkube connected to Slack!" bot=Slack commGroup=default-group

Actual behavior
level=info msg="Using API Key starting with \"xUd\"..." component="Analytics reporter"
level=info msg="Registering filter \"ObjectAnnotationChecker\" (enabled: true)..." component="Filter Engine"
level=info msg="Registering filter \"NodeEventsChecker\" (enabled: true)..." component="Filter Engine"
level=info msg="Starting server on address \":2112\"" component="Metrics server"
[E1025 memcache.go:206] couldn't get resource list for external.metrics.k8s.io/v1beta1: Got empty response for: external.metrics.k8s.io/v1beta1
level=info msg=Closing... component="Analytics reporter"
level=info msg="Shutdown requested. Finishing..." component="Metrics server"
while creating resource name normalizer: while getting resource list from K8s cluster: unable to retrieve the complete list of server APIs: external.metrics.k8s.io/v1beta1: Got empty response for: external.metrics.k8s.io/v1beta1

Steps to reproduce

Install KEDA (Helm chart).
Attempt to install BotKube v0.15.0 (Helm chart).
BotKube container will enter CrashLoopBackOff.

I believe this is a similar issue: https://github.com/kyverno/kyverno/issues/2267

Hi @nguyend91, thank you for reporting the issue. We'll try to investigate that further and fix it in the upcoming release. Thanks for linking the similar issue 👍

Alright, did a quick research and here are the results:
The error comes from client-go: https://github.com/kubernetes/client-go/blob/release-1.25/discovery/cached/memory/memcache.go#L228. I couldn't find any reported issue about such client behavior.
After reading https://github.com/kedacore/keda/issues/1797, looks like KEDA shouldn't return empty resource list 🤔 I couldn't find the same issue with other projects. The workaround is registering a dummy resource in the empty resource group. On the other hand, I didn't find any mentions that such custom API server behavior is not allowed. Didn't dig too deep, though.
While I was able to quickly implement a workaround on our end (see the changes: https://github.com/kubeshop/botkube/compare/main...pkosiec:empty-resource-list-workaround?expand=1), this doesn't look right (and it's ugly because of the string comparison). So I'm not sure if we should apply it on our side, if this is not an error on our (K8s API consumers) side 🤔
As I have mixed feeling, I need some advice 😄 @huseyinbabal what do you think? Should we apply the workaround or not?

So we did implement a workaround on our end, by creating a mock botkube-autoscaler (that frankly will never scale), but just wanted to give y'all the heads up for any future issues.
apiVersion: keda.sh/v1alpha1
kind: ScaledObject
metadata:
  name: botkube-autoscaler
  namespace: botkube
spec:
  maxReplicaCount: 1
  scaleTargetRef:
    name: botkube
  triggers:
    - type: new-relic
      metadata:
        account: {{ .Values.newrelic.account | quote }}
        queryKey: {{ .Values.newrelic.apikey | quote }}
        region: "US"
        noDataError: "true"
        nrql: "FROM Metric SELECT average(k8s.container.cpuCoresUtilization) AS 'CPU utilization (%)' WHERE k8s.clusterName = 'eks-stage' AND k8s.namespaceName = 'botkube' TIMESERIES"
        threshold: "100"
        activationThreshold: "100"

I appreciate you looking at this, though.

Alright, did a quick research and here are the results: The error comes from client-go: https://github.com/kubernetes/client-go/blob/release-1.25/discovery/cached/memory/memcache.go#L228. I couldn't find any reported issue about such client behavior.
After reading kedacore/keda#1797, looks like KEDA shouldn't return empty resource list 🤔 I couldn't find the same issue with other projects. The workaround is registering a dummy resource in the empty resource group. On the other hand, I didn't find any mentions that such custom API server behavior is not allowed. Didn't dig too deep, though.
While I was able to quickly implement a workaround on our end (see the changes: https://github.com/kubeshop/botkube/compare/main...pkosiec:empty-resource-list-workaround?expand=1), this doesn't look right (and it's ugly because of the string comparison). So I'm not sure if we should apply it on our side, if this is not an error on our (K8s API consumers) side (like Kyverno) 🤔 .
As I have mixed feelings on that, I need some advice 😄 @huseyinbabal what do you think? Should we apply the workaround or not?

First, returning 404 on getting zero result from listing  resources is an antipattern, I believe client-go should change  that logic. At the same time, there might be lots of cases where CRD with zero actual resources. Forcing end users to define fake resources might have operational cost. What you did as a workaround seems reasonable, but if client-go change their error message, Botkube can start  to crash again. My suggestion is;

Apply a workaround to Botkube as you did
Cover that with a reasonable level of integration test.
Hope that sounds meaningful :)

We'll keep the workaround applied for now. Thanks for taking the time looking into this!

@nguyend91 Yep, please keep it, but you won't need it on your side after the upcoming Botkube 0.16 release, as we have the team agreement and we'll apply the workaround on Botkube side to ignore such issue 🙂
@huseyinbabal Thanks. Unfortunately, integration testing would be quite tough, as we would need to install KEDA on pipeline or, have our own custom API server which returns also an empty resource list. I tried to use fake discovery client, but it doesn't return such error, so I would need to use real Discovery client which connects to K8s API.
However, I covered this part in unit tests, and fortunately the error won't change without our knowledge as it is strictly related to our client-go dependency version. Still, there's a small risk we'll upgrade the dependency without knowing the error changed, but as it is quite an edge case I wouldn't bother too much about it, as long as we cannot test it easily as you suggested.
Is that fine for you? Or do you have any other ideas how we can do it right, without big effort or put additional weight on our CI?

Alright, merged 👍 Thank you @nguyend91 again, expect 0.16 to land by the end of November / beginning of December 🙂 Thank you for using Botkube and making it better! 🚀

Thanks for such a quick response! Our team really enjoys using BotKube. Keep up the good work!

I got the same error when running kubectl command in our slack channel in v0.17.0. Altough it does not cause botkube crash, but the error is very annoying.
E0208 00:47:11.697976      43 memcache.go:255] couldn't get resource list for [external.metrics.k8s.io/v1beta1](http://external.metrics.k8s.io/v1beta1): Got empty response for: [external.metrics.k8s.io/v1beta1](http://external.metrics.k8s.io/v1beta1)
No resources found in botkkube namespace.

Hi @Le0exxx,
Sadly, I don't really see an option to do anything about it. Default Go client error handling is to log such errors, and while we could think about changing the behavior (see https://github.com/kubernetes/apimachinery/blob/release-1.25/pkg/util/runtime/runtime.go#L83-L111), I'd still vote for printing them for transparency.
You can see the upstream issues:

https://github.com/kedacore/keda/issues/1797
https://github.com/kubernetes-sigs/custom-metrics-apiserver/issues/146


Recently I realized that accessing the sonos favourites is not yet possible with SoCo and found this workaround on Google Groups.
Integrating this functionality into SoCo shouldn't be a big deal:

In the music_library.py, the SEARCH_TRANSLATION dict should be extended by the pair
'sonos_favourites': 'FV:2'
get_sonos_favourites() should be added as a convenience method for
get_music_library_information('sonos_favourites')
this change should be documented in the wiki

Is there some issue I am missing? Otherwise, I will start working on this in a fork.

Makes sense to me. I experimented  with the in the past, but never created a pull request.
Look forward to having this functionality.
Cheers Daivd

@ghcs27 There is already a pull request for this at https://github.com/SoCo/SoCo/pull/383 Is that the same thing? If it is, do you think it is complete?
Lawrence

Sadly, there's a catch: Sonos favorites have their own DIDL class (object.itemobject.item.sonos_favorite) for which there is no corresponding data structure / soco class.
So when from_didl_string() encounters a sonos favorite and wants to determine its class by looking up 'object.itemobject.item.sonos_favorite' in the _DIDL_CLASS_TO_CLASS dict, there's an error.
Apparently a new data structure has to be created for the sonos favorites.
Is someone willing to assist me with this task? I'm new here, but I really want to get this functionality to SoCo.

Sadly, there's a catch: Sonos favorites have their own DIDL class (object.itemobject.item.sonos_favorite) for which there is no corresponding data structure / soco class.
So when from_didl_string() encounters a sonos favorite and wants to determine its class by looking up 'object.itemobject.item.sonos_favorite' in the _DIDL_CLASS_TO_CLASS dict, there's an error.
Apparently a new data structure has to be created for the sonos favorites.
Is someone willing to assist me with this task? I'm new here, but I really want to get this functionality to SoCo.

@lawrenceakka Oops, didn't see your comment. It is indeed the same thing, so I'll have a look at it.

#383 seems to work properly. Some things that I noticed:

SoCo.get_sonos_favorites() returns a dict, just as SoCo.get_favorite_radio_stations() and
...radio_shows() already do. This is opposed to the SoCo.music_library.get_... methods returning a
SearchResult instance. I would consider this inconsistent. What do you think?
get_sonos_playlists() is not mentioned in the Methods section of the documentaries and should be
added

What do we need to do to move this forward?
Can we create the required DIDL class?
Cheers David

It seems like someone already tried to create this class, but Sonos makes it more difficult than it would have to be: see data_structures.py.
My suggestion is to merge #383 first (it integrates well with the SoCo.get_favorite_radio_... methods and apparently there is a reason for them to be different from the music library methods) and then work on solving the problem described in the comment linked above.

That makes good sense.
Any other thoughts ?

There is a PR at #328 which adds DIDL classes for radio. Any class for favorites should have a similar structure to them

@ghcs27 moving forward, slowly, but still forward. #383 was merged (but using dicts as output, just to get the new functionality in). I think I will put some focus on #328 now, to finally get that in, which should hopefully get this resolved.

I have dug a bit further into the favorite metadata and found out that we really can create the required Didl class: see https://github.com/ghcs27/SoCo/tree/favorite_data_structure.

I have done the required changes, but I require your advice for code style:
In the metadata for a Sonos favorite, there is a <resMD> tag which contains the metadata of the item to which the favorite refers. To make its contents accessible to the user, there are two possible implementations:

When the DidlFavorite object is created, parse the resMD metadata and make the referenced object available via an attribute which can be accessed and modified. When the favorite it is converted back to XML, call to_didl_string() on the referenced object to get the metadata back.
This can be archieved by adding a resource_meta_data property - see https://github.com/ghcs27/SoCo/tree/favorite_data_structure.
Keep the resMD metadata in its own attribute. Make it accessible by adding a reference property which parses the metadata on read. For this, see https://github.com/ghcs27/SoCo/tree/favorite_data_structure_alt.

Which implementation do you prefer?

PR for this is here: #478


Displays wrong file line numbers

Webpack
3.5.5
ESLint Version:
v4.3.0
Node Version:
v6.10.3

Eslint-loader displays the wrong line numbers for file run via webpack
Eg Image. https://gyazo.com/1c395f6226b7abfcc071b3849e611012

You are probably running eslint on transformed files.
eslint-loader needs to be used as your first loader (so the last in your list) or as a pre-loader. See readme.
Unless you share your webpack config we cannot help you.


Installation by cloning from git stringr is missing.

When installing teh app by cloning the repo in a clean rstudio docker the library stringr is not installed automatically.
Setup:
Docker image: rocker/rstudio 8319c72d79f0
clone app from git as new RStudio project
install shiny package
run app.R
result:
App will start,
browser is opend
page is grayed out
RStudio console shows errors the stringr package is not found
Error in library(stringr) : there is no package called ‘stringr’
fix
stop app
install.packages('stringr')
rerun app

I added stringr to the packages list. Can you test if this fixes the problem in a clean R environment?
The package was bundled in the installer and it's rare for me to work in an R environment where stringr is not installed already, that is probably why I didn't spot this before.

App now starts without issues,
thank you.
Fixed in 8dc7eae8049da332bb5d948ac20a724bfdd50103


How to convert class name to english?

Hi, since the class name is wordnet id and the label in annotation file is in English, is there a simple way to find the correponding annotation file for each class?

By the way, what is the wordnet version used in this dataset?

Oh I see. The net id for each class can be found in the json file.


Fix grammar and consistency in readmes and spec files

Sorry if my commits are a bit messy – I'm still learning how to use Git and Github properly.

Nice! Thanks a lot. Don't worry about commit messages for this PR. Changes are clear in the files changed tab.
I'm not sure about replacing ten with 10, or tenth with 10th. But they look nice, so why not?
I'm ok with merging this PR. We usually ask contributors to squash different commits into a single one. I was going to provide @a-dpq some instructions about squashing commits (because it seems @a-dpq is learning git). Before doing that, I tried on myself, and I struggled a lot. So, I decided to merge the PR as it is. Never mind.
I think, squashing commits is not straight forward in this PR because there are some commits merging changes from origin/master into a-dpq/master. So, resetting to the commit where this PR starts, reverts too many changes.
Sorry, I wrote a lot to say nothing relevant to the PR. The most important thing, @a-dpq, thanks a lot for this contribution. Is not about code, but communicating with users is as important as code. :+1:

Great, thanks! I only changed the numbers for consistency: previously, the files used both variants (10 and ten).


Workaround for broken certificates

About the PR
This pull request adds a workaround for the problem described here: https://github.com/NuGet/Home/issues/10491.

This breaks CI. Unless other people run into this I'm hesitant towards merging this. Might be best for you to just keep the file dirty in your repo and be a bit diligent about not committing it on accident for the time being.

Understandable.
I'm closing this request now.


⚠ Spryr has degraded performance

In c9e94dc, Spryr (https://spryr.com) experienced degraded performance:

HTTP code: 200
Response time: 3137 ms

Resolved: Spryr performance has improved in 098ac9b after 7 minutes.