uploading first time

Pull Request Template
Description
Please include a summary of the problem and about the approach to solve the solution. Please also include relevant motivation and context.
List any dependencies that are required for this change.
Put check marks:
Have you made changes in README file ?

[ y] Added problem & solution under correct topic.
[ ] Specified Space & Time complexity.
[ ] Specified difficulty level, tag & Note(if any).

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration.

[ ] Test A
[ ] Test B

Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] Any dependent changes have been merged and published in downstream modules

@Rudra407 Please update README.md file for the problem section, time, space complexity details.


document tfgrid_dashboard

https://github.com/threefoldfoundation/info_manual3/blob/development/wiki/dashboard/dashboard_readme.md


[FR] 支持追踪kafka server端内部链路

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Description
背景：kafka作为一款分布式实时消息处理系统，除传统的微服务场景外，在我们公司的大数据、数仓等场景有广泛使用，公司内有几十个不同的Kafka集群，规模从10-100台不等，提供稳定、易用、高效率运维的Kafka组件尤为重要。
问题：公司目前基于传统的Metric和Log方式，对kafka多个集群进行人工巡检和运维，遇到过Kafka服务端写入慢、消费堆积、消费者掉线、网卡配置有误等各类问题，从问题发现到解决的时间偏长（一定程度上影响用户体验），希望能够结合全链路工具，监控分析Kafka客户端和服务端内部链路。
全链路调研进展：

从目前调研试用来看，目前，deepflow能够trace kafka客户端、以及kafka服务端网卡链路，  我们希望deepflow能够trace kafka服务端内部链路，有助于我们快速排查各类kafka服务端问题。
目前与社区沟通，kafka服务端能够使用消息协议中的correlationid跟踪一条RPC消息的完整链路（消息说明见https://cwiki.apache.org/confluence/display/KAFKA/A+Guide+To+The+Kafka+Protocol#AGuideToTheKafkaProtocol-Requests），与社区讨论确认了deepflow集成kafka server端完整链路的可行性，希望社区能够帮忙完善。

价值：

提高kafka服务端运维能力，提升用户体验
deepflow-kafka服务端集成作为一个良好的开端和借鉴，后续能够接入其他大数据组件服务端（es、hbase等），提高大数据平台的全链路可观测性和运维能力

Background:
Kafka is a distributed real-time message processing system. In addition to traditional microservice scenarios, it is widely used in big data, data warehouse and other scenarios in our company. There are dozens of different Kafka clusters in the company, ranging in size from 10 -100 units, it is particularly important to provide stable, easy-to-use, and efficient operation and maintenance of Kafka components
Problem:
The company currently conducts manual inspection and operation and maintenance of multiple Kafka clusters based on traditional Metric and Log methods. It has encountered various problems such as slow writing on the Kafka server, accumulation of consumption, consumer disconnection, and incorrect network card configuration. The problem is that the time from problem discovery to solution is too long (which affects the user experience to a certain extent). It is hoped that full-link tools can be used to monitor and analyze the Kafka client and server internal links.
Full-link research progress:

Judging from the current research and trial, deepflow can currently trace the kafka client and kafka server network card links. We hope that deepflow can trace the internal links of the kafka server, which will help us quickly troubleshoot various kafka server problems.
Currently communicating with the community, the Kafka server can use the correlationid in the message protocol to track the complete link of an RPC message (for message description, see https://cwiki.apache.org/confluence/display/KAFKA/A+Guide+To +The+Kafka+Protocol#AGuideToTheKafkaProtocol-Requests), discussed with the community and confirmed the feasibility of deepflow integrating the complete link of kafka server, and hope that the community can help improve it.

Benefit:

Improve kafka server operation and maintenance capabilities and improve user experience
The deepflow-kafka server integration serves as a good start and reference. It can subsequently be connected to other big data component servers (es, hbase, etc.) to improve the full-link observability and operation and maintenance capabilities of the big data platform.

Use case
我们公司的大数据、数仓等场景广泛使用kafka传输消息.
Related issues
No response
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

@h453693821  could u plz provide the link that kafka team discuss the probability and benefit of integrate system like deepflow, thx!

@h453693821 could u plz provide the link that kafka team discuss the probability and benefit of integrate system like deepflow, thx!

+1  @flashmouse It seems the method you mentioned might not be applicable for tracking messages.

In the Kafka documentation (https://cwiki.apache.org/confluence/display/KAFKA/A+Guide+To+The+Kafka+Protocol#AGuideToTheKafkaProtocol-CommonRequestandResponseStructure), the description of CorrelationId is as follows:

CorrelationId
This is a user-supplied integer. It will be passed back in the response by the server, unmodified. It is useful for matching request and response between the client and server.

However, it is important to note that the Server here refers to the server in the Producer (ReqResp Client) -> Kafka -> Consumer (ReqResp Server) communication sequence, and not the TCP Server in the Producer -> Kafka (TCP Server) or Consumer -> Kafka (TCP Server) communication sequence. Reference: https://www.ankushchoubey.com/v1/kafka-request-response-redis/#:~:text=Each message sent by a,with the same correlation-id.
Therefore, the CorrelationID can be used for distributed tracing.


ESLint: Parsing error: Unexpected character '@'

I am trying to use vue3 and decorators in an electron app.
https://facing-dev.github.io/vue-facing-decorator/#/en/class-component/component/component
I have a simple component:
<template>

HomeView

  <n-button @click="redrawData()">
    naive-ui
  </n-button>

  This is the home page: {{ data }}
</template>

But the IDE (jetbrains) says for the decorator there:
ESLint: Parsing error: Unexpected character '@'

I could not find anything in the docs about the decorators for eslint, but i guess there is just a rule missing?
eslint looks like:
{
  "env": {
    "browser": true,
    "es6": true,
    "node": true
  },
  "extends": [
    "eslint:recommended",
    "plugin:@typescript-eslint/eslint-recommended",
    "plugin:@typescript-eslint/recommended",
    "plugin:import/recommended",
    "plugin:import/electron",
    "plugin:import/typescript",
    "plugin:vue/vue3-recommended"
  ],
  "parser": "vue-eslint-parser"
}

In addition, the ide cannot jump to data attrbute of the class or any of the methods...

It probably doesn't support decorator. Try https://stackoverflow.com/questions/40678196/eslint-unexpected-character-for-js-decorators

Hi & thanks for the reply
Yes, I was wondering this too but thought that with it bring 2024 there would have been a solution for this.
OK thanks I will give this a go.

https://facing-dev.github.io/vue-facing-decorator/#/en/quick-start/quick-start?id=vite


Can't upload PBIX File.

I configured custom authentication in Power BI Report Server.
But when i upload .pbix file, it throws an error.
( .rdl files and excel files can be uploaded successfully)
The log file (RSPowerBI.log) contains the following information.
2017-07-18 03:36:34.9195|ERROR|7|Unhandled Exception in the owin pipeline ExceptionSystem.NullReferenceException: Object reference not set to an instance of an object.
   at Microsoft.BIServer.Owin.Common.Services.AuthenticationService.GetUserInfo(RsRequestContext requestContext)
   at Microsoft.BIServer.Owin.Common.CustomAuthenticationMiddleware.Invoke(IOwinContext context)
   at Microsoft.BIServer.Owin.Common.GlobalExceptionHandlerMiddleware.<Invoke>d__0.MoveNext()
2017-07-18 03:36:45.6086|INFO|7|Dump result: External dump process return code 0x20000001.
External dump process returned no errors.
.

Have you copied your CustomSecurity.dll to the PowerBI folder?

Thanks ,Parthsha.
After I copied CustomSecurity.dll and CustomSecurity.pdb to the PowerBI folder, I successed to  upload PBI files.

How to fix : {"error":{"code":"102","message":"There was an error uploading your .pbix file.  Verify that the file has not been corrupted and that the file extension matches the format of the file."}}, when upload .pbix file into power bi reports server (9/2021). I use Power BI Desktop (9/2021) to create pbix file


Adds valid_range check

Checks for valid_range. If it is not present, this is followed by valid_min
and valid_max check.  Implements #38.

Tests are broken due to standard name table not downloading.

Going to fix and rename/rebase.


Remove the sample program aescrypt2

The sample program aescrypt2 shows bad practice: hand-rolled CBC implementation, CBC+HMAC for AEAD, hand-rolled iterated SHA-2 for key stretching, no algorithm agility. Remove it. Fix https://github.com/ARMmbed/mbedtls/issues/1906.
A replacement program pbcrypt is available in https://github.com/ARMmbed/mbedtls/pull/4216, but at the moment it's held up for review.
Needs backports to all branches: even in an LTS, we don't want people using this in any way. 2.x, 2.16.

The CI failure in pr-merge is an instance of https://github.com/ARMmbed/mbedtls/issues/3377. The CI has passed enough to validate this PR.


Datatype99 is always reporting missing comma syntax error

I can't seem to get this to work. It is not missing a comma.

$ uname -a
MINGW64_NT-10.0-22631 anakin 3.5.4-395fda67.x86_64 2024-11-25 09:49 UTC x86_64 Msys

$ ls
datatype99/  datatype99_test.c  metalang99/

$ cat datatype99_test.c
#include <datatype99.h>

// clang-format off
datatype(
    BinaryTree,
    (Leaf, int),
    (Node, BinaryTree *, int, BinaryTree *)
);
// clang-format on

int main(void) { return 0; }

$ clang --version
clang version 19.1.5
Target: x86_64-pc-windows-msvc
Thread model: posix
InstalledDir: C:\Program Files\LLVM\bin

datatype99 version:
$ git describe --tags
v1.6.4-9-g982a87b

metalang99 version:
$ git describe --tags
v1.13.3-14-gbbd4749

$ clang -Idatatype99 -Imetalang99/include -fmacro-backtrace-limit=1 datatype99_test.c
datatype99_test.c:4:1: error: static assertion failed: invalid term `(0args, DATATYPE99_PRIV_genDatatype, (0v, BinaryTree), (0args, ML99_listFromTuples, (0v, DATATYPE99_PRIV_parseVariant),
      (0v, (Leaf, int), (Node, BinaryTree *, int, BinaryTree *))), (0v, dummy))`, did you miss a comma?
    4 | datatype(
      | ^~~~~~~~~
    5 |     BinaryTree,
      |     ~~~~~~~~~~~
    6 |     (Leaf, int),
      |     ~~~~~~~~~~~~
    7 |     (Node, BinaryTree *, int, BinaryTree *)
      |     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    8 | );
      | ~
note: (skipping 36 expansions in backtrace; use -fmacro-backtrace-limit=0 to see all)
metalang99/include\metalang99/eval/rec.h:38:35: note: expanded from macro 'ML99_PRIV_REC_EXPAND'
   38 | #define ML99_PRIV_REC_EXPAND(...) __VA_ARGS__
      |                                   ^~~~~~~~~~~
1 error generated.

If you run ./scripts/test-all.sh in metalang99/, does it work? If yes, the problem is related to Datatype99. Otherwise, it is related to the way your preprocessor handles Metalang99.

Those scripts depend on cmake. I had to download and install that. Then the script picked the wrong compiler so it passed with the wrong compiler. It used msvc instead of clang.

So everything worked with MSVC but not with Clang?

yes, after messing around with cmake for close to an hour and having to install another dependency called ninja, I finally was able to get it to use clang. it failed again.
I had to do this otherwise it would always use MSVC.
$ git diff
diff --git a/scripts/test.sh b/scripts/test.sh
index ced5f53..ce5c762 100755
--- a/scripts/test.sh
+++ b/scripts/test.sh
@@ -4,8 +4,12 @@ set -e

 mkdir -p tests/build
 cd tests/build
-cmake ..
-cmake --build .
+
+# Specify the Ninja generator and the path to clang
+cmake -G "Ninja" -DCMAKE_C_COMPILER="C:/Program Files/LLVM/bin/clang.exe" -DCMAKE_CXX_COMPILER="C:/Program Files/LLVM/bin/clang++.exe" ..
+
+# Build the project using Ninja
+ninja

 if [[ "$OSTYPE" == "linux-gnu" ]]; then
     echo "Testing ./gen ..."

here is the first part of the output with full log attached.
-- The C compiler identification is Clang 19.1.5 with GNU-like command-line
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: C:/Program Files/LLVM/bin/clang.exe - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Configuring done (0.7s)
-- Generating done (0.1s)
CMake Warning:
  Manually-specified variables were not used by the project:

    CMAKE_CXX_COMPILER

-- Build files have been written to: C:/Users/arthu/git/metalang99/tests/build
[1/34] Building C object CMakeFiles/metalang99.dir/metalang99.c.obj
[2/34] Building C object CMakeFiles/stmt.dir/stmt.c.obj
[3/34] Building C object CMakeFiles/rec.dir/eval/rec.c.obj
[4/34] Building C object CMakeFiles/assert.dir/assert.c.obj
FAILED: CMakeFiles/assert.dir/assert.c.obj
C:\PROGRA~1\LLVM\bin\clang.exe  -IC:/Users/arthu/git/metalang99/tests/../include -O0 -g -Xclang -gcodeview -D_DEBUG -D_DLL -D_MT -Xclang --dependent-lib=msvcrtd -fmacro-backtrace-limit=1 -MD -MT CMakeFiles/assert.dir/assert.c.obj -MF CMakeFiles\assert.dir\assert.c.obj.d -o CMakeFiles/assert.dir/assert.c.obj -c C:/Users/arthu/git/metalang99/tests/assert.c
C:/Users/arthu/git/metalang99/tests/assert.c:6:1: error: static assertion failed: invalid term `(0args, ML99_assert, (0v, 1 == 1))`, did you miss a comma?
    6 | ML99_EVAL(ML99_assert(v(COND)));
      | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
note: (skipping 34 expansions in backtrace; use -fmacro-backtrace-limit=0 to see all)
C:/Users/arthu/git/metalang99/tests/../include\metalang99/eval/rec.h:38:35: note: expanded from macro 'ML99_PRIV_REC_EXPAND'
   38 | #define ML99_PRIV_REC_EXPAND(...) __VA_ARGS__
      |                                   ^~~~~~~~~~~
C:/Users/arthu/git/metalang99/tests/assert.c:7:1: error: static assertion failed: invalid term `(0args, ML99_assertEq, (0v, 1 == 1), (0v, 1 == 1))`, did you miss a comma?
    7 | ML99_EVAL(ML99_assertEq(v(COND), v(COND)));
      | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
note: (skipping 34 expansions in backtrace; use -fmacro-backtrace-limit=0 to see all)

make.log

in my testing:
clang 19.1.5 failed
clang 15.0.0 failed
MSVC 19.42.34435.0 succeeded

I've just tested with Clang 18.1.3 and everything works smoothly. I'm on Ubuntu 24.04. Our CI also doesn't show any signs of failure.
I'm therefore suspecting that it's because you're compiling under MinGW, although I've no idea how it's related to macro preprocessing. Does Datatype99 work for you outside of MinGW?

this is with building outside the mingw (git bash) environment and using a windows cmd.exe prompt:

C:\Users\arthu\git\metalang99\tests\build>cmake -G "Ninja" -DCMAKE_C_COMPILER="C:/Program Files/LLVM/bin/clang.exe" ..
-- The C compiler identification is Clang 19.1.5 with GNU-like command-line
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: C:/Program Files/LLVM/bin/clang.exe - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Configuring done (0.8s)
-- Generating done (0.0s)
-- Build files have been written to: C:/Users/arthu/git/metalang99/tests/build

C:\Users\arthu\git\metalang99\tests\build>ninja
[4/34] Building C object CMakeFiles/assert.dir/assert.c.obj
FAILED: CMakeFiles/assert.dir/assert.c.obj
C:\PROGRA~1\LLVM\bin\clang.exe  -IC:/Users/arthu/git/metalang99/tests/../include -O0 -g -Xclang -gcodeview -D_DEBUG -D_DLL -D_MT -Xclang --dependent-lib=msvcrtd -fmacro-backtrace-limit=1 -MD -MT CMakeFiles/assert.dir/assert.c.obj -MF CMakeFiles\assert.dir\assert.c.obj.d -o CMakeFiles/assert.dir/assert.c.obj -c C:/Users/arthu/git/metalang99/tests/assert.c
C:/Users/arthu/git/metalang99/tests/assert.c:6:1: error: static assertion failed: invalid term `(0args, ML99_assert, (0v, 1 == 1))`, did you miss a comma?
    6 | ML99_EVAL(ML99_assert(v(COND)));
      | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
note: (skipping 34 expansions in backtrace; use -fmacro-backtrace-limit=0 to see all)
C:/Users/arthu/git/metalang99/tests/../include\metalang99/eval/rec.h:38:35: note: expanded from macro 'ML99_PRIV_REC_EXPAND'
   38 | #define ML99_PRIV_REC_EXPAND(...) __VA_ARGS__
      |                                   ^~~~~~~~~~~
C:/Users/arthu/git/metalang99/tests/assert.c:7:1: error: static assertion failed: invalid term `(0args, ML99_assertEq, (0v, 1 == 1), (0v, 1 == 1))`, did you miss a comma?
    7 | ML99_EVAL(ML99_assertEq(v(COND), v(COND)));
      | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
note: (skipping 34 expansions in backtrace; use -fmacro-backtrace-limit=0 to see all)
C:/Users/arthu/git/metalang99/tests/../include\metalang99/eval/rec.h:38:35: note: expanded from macro 'ML99_PRIV_REC_EXPAND'
   38 | #define ML99_PRIV_REC_EXPAND(...) __VA_ARGS__
      |                                   ^~~~~~~~~~~
C:/Users/arthu/git/metalang99/tests/assert.c:9:1: error: expected expression
    9 | ML99_ASSERT(v(COND));
      | ^
note: (skipping 5 expansions in backtrace; use -fmacro-backtrace-limit=0 to see all)
C:/Users/arthu/git/metalang99/tests/../include\metalang99/eval/syntax_checker.h:12:46: note: expanded from macro 'ML99_PRIV_CHECK_TERM'
   12 |     ML99_PRIV_IF(ML99_PRIV_IS_UNTUPLE(term), ML99_PRIV_EMIT_SYNTAX_ERROR, default)

passing this flag to clang fixes it:
-fno-ms-extensions

by default clang enables -fms-extensions for windows targets, and that causes _MSC_VER and _MSC_FULL_VER macros to be defined.
https://clang.llvm.org/docs/UsersManual.html#microsoft-extensions

@hirrolot I discovered a difference in preprocessing with and without ms-extensions.
$ cat macro_test.c
#define A(...) B(__VA_ARGS__)
#define B(...) (0v, __VA_ARGS__)

A(1) // Case 1: Non-empty argument
A()  // Case 2: Empty argument

with ms-extensions (default behavior)
$ clang -E macro_test.c
# 1 "macro_test.c"
# 1 "<built-in>" 1
# 1 "<built-in>" 3
# 385 "<built-in>" 3
# 1 "<command line>" 1
# 1 "<built-in>" 2
# 1 "macro_test.c" 2

(0v, 1)
(0v)

with no-ms-extensions
$ clang -E -fno-ms-extensions macro_test.c
# 1 "macro_test.c"
# 1 "<built-in>" 1
# 1 "<built-in>" 3
# 401 "<built-in>" 3
# 1 "<command line>" 1
# 1 "<built-in>" 2
# 1 "macro_test.c" 2

(0v, 1)
(0v, )

you can see the difference (0v) vs (0v, )
I am not sure why MSVC works though.

@awmorgan, the output with -fno-ms-extensions is the standard-complying one. No wonder why Datatype99 doesn't work with MS extensions -- it heavily relies on comma usage internally.

I am not sure why MSVC works though.

I'm not totally sure about your situation with MSVC, but in the CI, we specify the /std:c11 option explicitly, which automatically enables a standard-conforming preprocessor via /Zc:preprocessor:

Because the new preprocessor is needed to support these standards, the /std:c11 and /std:c17 compiler options set the /Zc:preprocessor option automatically.

In fact, Metalang99 won't compile if you compile it with an improperly configured MSVC.

I’ve identified the root cause: Clang on Windows defaults to MS compatibility mode, which alters macro expansion behavior. Using -fno-ms-extensions returns the preprocessor to standard-conforming behavior, but then breaks MSVC headers.
A better solution is to use -fno-ms-compatibility while still enabling -fms-extensions. This combination preserves the standard macro expansion (so (0v, ) works as expected) and allows you to include MSVC standard headers without errors.
We can close this issue now.


Check & revise version requirements for “Configure Liveness, Readiness and Startup Probes”

This is a clean up issue

What would you like to be checkrf
Look at https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/
Make sure that all the version constraints in the page make sense and related to the list of Kubernetes versions that are supported for documentation.
There is a {{< version-check >}} shortcode in the page that expects a min-kubernetes-server-version:  value in the page front matter. Replace that shortcode with English text that explains in words what versions the reader should have.
(to save you having to check: you can only configure a startup probe if you have Kubernetes v1.16 or later and if you have enabled the StartupProbe feature gate)
Why is this needed
https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/ doesn't clearly tell readers about the version of Kubernetes they need to be running and the feature gate(s) they might need to enable.
Comments
/help
/kind cleanup
If you're looking at this, you might also want to tackle issue #16629

/remove-lifecycle stale

/language en
/lifecycle frozen

/assign
@sftim I'll probably be back with questions - where's better to post/ask, here on the issue, or in Slack?

Should I just add the info for Startup probes? I see that they came last with the feature gate in 1.16 onwards, checking now re: Liveness and Readiness but I guess they're earlier than the supported doc versions.
Still would be nice to mention though - as a reader with maybe a bit less context I would get confused if the page title mentions 3 kinds of probes and the docs only talk about version requirements for one type of probe.

Also at this point for the StartupProbe feature flag since it went beta in 1.18 and GA in 1.20 the text would be something like:
Kubernetes v1.16 and v1.17 require the StartupProbe feature gate to be set. Startup probes are enabled by default in Kubernetes v1.18 onwards.

IMO it's OK to focus on documenting for v1.21, the current documentation version. If we want to backport the equivalent change to the older documentation, that's an option too.
For example, if you want to revise https://v1-17.docs.kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/#define-startup-probes to explain the feature gate, that's OK (but also not a priority).

@sftim how do I go about editing the old version of the docs? Or is there a how-to/readme somewhere?
I've submitted a PR for the current version/file with the text I suggested: https://github.com/kubernetes/website/pull/27750
Do you know btw when Liveness and Readiness probes went alpha/beta/GA? I found Liveness probes introduced here but haven't found Readiness probes yet. Anyways given that it's all the way in 2014 I think it's safe to omit specific versions.
I updated the text to read:
Kubernetes v1.16 and v1.17 require the `StartupProbe` [feature gate](https://kubernetes.io/docs/reference/command-line-tools-reference/feature-gates/) to be set. Startup probes (as well as liveness and readiness probes) are enabled by default in Kubernetes v1.18 onwards.

lmk what you think

Since I opened this issue, several Kubernetes releases have come out and I didn't update the issue text to clarify it. I have now.

If all PRs were this simple 😂
Actually it turns out some of them really are :)


No Account Registration Links Available on Plandex.ai for Plandex Cloud Service

I was exploring the Plandex Cloud service as outlined on the Plandex.ai website. The service is described as an easy and reliable way to use Plandex. There are no visible links or buttons to register or start a trial on the website.

Hi @Tritaya, you can install Plandex as described here: https://github.com/plandex-ai/plandex?tab=readme-ov-file#install
Then run plandex new and you will be prompted to start a trial on cloud.


chore(main): release 1.0.8

:robot: I have created a release beep boop
1.0.8 (2022-05-30)
Bug Fixes

test ci (#73) (f8dd5ae)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/SecretHouseGame/ngx-design-system/releases/tag/v1.0.8 :sunflower:


[SPARK-19712][SQL] Pushdown LeftSemi/LeftAnti below join

What changes were proposed in this pull request?
This PR adds support for pushing down LeftSemi and LeftAnti joins below the Join operator.
This is a prerequisite work thats needed for the subsequent task of moving the subquery rewrites to the beginning of optimization phase.
The larger  PR is here . This PR addresses the comment at link.
How was this patch tested?
Added tests under LeftSemiAntiJoinPushDownSuite.

Test build #104453 has started for PR 24331 at commit a5f1f50.

Test build #104453 has finished for PR 24331 at commit a5f1f50.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/104453/
Test FAILed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/9783/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/9785/
Test PASSed.

Test build #104456 has started for PR 24331 at commit 14ed943.

Test build #104456 has finished for PR 24331 at commit 14ed943.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/104456/
Test PASSed.

cc @cloud-fan

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/9856/
Test PASSed.

Test build #104530 has started for PR 24331 at commit 813075f.

Test build #104530 has finished for PR 24331 at commit 813075f.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/104530/
Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/9916/
Test PASSed.

Merged build finished. Test PASSed.

Test build #104593 has started for PR 24331 at commit 9945c28.

Test build #104593 has finished for PR 24331 at commit 9945c28.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/104593/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/9933/
Test PASSed.

Test build #104612 has started for PR 24331 at commit 4a5b4ca.

Test build #104612 has finished for PR 24331 at commit 4a5b4ca.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/104612/
Test FAILed.

retest this please

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/9941/
Test PASSed.

Test build #104619 has started for PR 24331 at commit 4a5b4ca.

Test build #104619 has finished for PR 24331 at commit 4a5b4ca.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/104619/
Test PASSed.

Test build #104627 has started for PR 24331 at commit fe3e168.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/9949/
Test PASSed.

Test build #104627 has finished for PR 24331 at commit fe3e168.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/104627/
Test PASSed.

Test build #104642 has started for PR 24331 at commit a5ed3d9.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/9964/
Test PASSed.

Test build #104642 has finished for PR 24331 at commit a5ed3d9.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/104642/
Test FAILed.

retest this please

Test build #104650 has started for PR 24331 at commit a5ed3d9.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/9971/
Test PASSed.

Test build #104650 has finished for PR 24331 at commit a5ed3d9.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/104650/
Test PASSed.

thanks, merging to master!

@cloud-fan Thank you very much.


Upgrade Symfony Validator

[x] Change composer.json to work with new version symfony validator
[x] Update namespace ValidatorInterface
[x] Update tests

To resolve #289

Big thanks :heart:

Please release this update because it's very confusing that this lib does not work with SF 2.8 out of the box using stable release in composer

Thanks for the reminder, @borNfreee! Tagged as 0.20.0.


Merge 'holin activity', 'canonical holin activity' 'pinholin activity' into new term pore forming activity

Discussing with @dsiegele
Annotations are by CACAO, except for 1 by UniProt
These represent gene products that encode pore-forming proteins

obsolete

GO:1901217 regulation of holin activity
** consider molecular function regulator activity
GO:1901218 negative regulation of holin activity -> 4 EXP by CACAO
** consider molecular function inhibitor activity

Dear all,
The proposal has been made to obsolete GO:1901217 regulation of holin activity and GO:1901218 negative regulation of holin activity. The reason for obsoletion is that this represents a molecular function. There are 4 annotations to GO:1901218 by CACAO. Right now the recommendation is to use 'molecular function regulator/inhibitor activity'.
These terms are mapped to 2 InterPro and 2 UniRules
InterPro:IPR034688
InterPro:IPR034696
UniRule:UR000413060
UniRule:UR000433546
These terms are not present in any subsets.
You can comment on the ticket https://github.com/geneontology/go-ontology/issues/24028
Thanks, Pascale


Before you begin: Android Basics in Compose

URL of codelab
https://developer.android.com/courses/pathways/android-basics-compose-unit-2-pathway-2#codelab-https://developer.android.com/codelabs/basic-android-kotlin-compose-before-you-begin
In which task and step of the codelab can this issue be found?
In Chinese language version, both 2nd and 3rd tasks
Describe the problem
In Chinese language version, while landing into this url, it shows both my 2nd/3rd tasks were finished, but actually there are not, and while click the task buttons will lead to  lead to a wrong url: (https://developer.android.com/codelabs/basic-android-kotlin-compose-before-you-begin?continue=https%3A%2F%2Fdeveloper.android.com%2Fcourses%2Fpathways%2Fandroid-basics-compose-unit-2-pathway-2%23codelab-https%3A%2F%2Fdeveloper.android.com%2Fcodelabs%2Fbasic-android-kotlin-compose-before-you-begin#0).
When I try to switch language to English, problem solved.
Steps to reproduce?

In Chinese language channel, Go to https://developer.android.com/courses/pathways/android-basics-compose-unit-2-pathway-2#codelab-https://developer.android.com/codelabs/basic-android-kotlin-compose-before-you-begin
Click on "启动 Codelab" under either 2nd or 3rd task
See error... Just another wrong page

Versions
Android Studio version:
API version of the emulator:
Additional information
Include screenshots if they would be useful in clarifying the problem.

Hello @zhongdj,
The localization issue that you presented to us is extremely important, and I thank you for bringing it to our attention. The links are fixed and ready for your review:
https://developer.android.com/courses/pathways/android-basics-compose-unit-2-pathway-2?hl=zh-cn


Files missing from build-tools folder

build-ubuntu-binary.sh and build-windows-binary.sh are missing from the build-tools folder.

Hey, sorry.I made a mistake to remove it.

Fix it https://github.com/tzutalin/labelImg/commit/e86472a592f3740cb6d91f671ec69cecb93a4da1


Simplify Data URLs

To create a visualization currently from a URL we use:
Chart(Data(url='http://some.url/some/path.json', format='json')).mark_point()

I think we could pretty easily shorten this to
Chart('http://some.url/some/path.json').mark_point()

without introducing any ambiguity.

+1
On Mon, May 23, 2016 at 7:06 PM, Jake Vanderplas<EMAIL_ADDRESS>wrote:

To create a visualization currently from a URL we use:
Chart(Data(url='http://some.url/some/path.json', format='json')).mark_point()
I think we could pretty easily shorten this to
Chart('http://some.url/some/path.json').mark_point()
without introducing any ambiguity.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/ellisonbg/altair/issues/111

--
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
<EMAIL_ADDRESS>and<EMAIL_ADDRESS>

Done in https://github.com/ellisonbg/altair/commit/81eb6caa9a3874408be45d6371579899e4ae08bf


Extracting info from website into csv file

Hi I decided to use Github to get feedback for any issues that I am unable to solve after long time of working. Aside from also using snap to get the info image and convert it to csv file, I am also trying to use the xpath method.

Here are my codes:
https://www.dbs.com.sg/personal/rates-online/foreign-currency-foreign-exchange.page
dump Name,Price to number6.csv
rows = count('//*[@id="sgfx"]/div/div[2]/table[31]/tbody')
for row from 1 to rows
read ((//[contains(@class,"tbl-primary")]/tbody/tr)[row]//td)[1] to name
read ((//[@id="sgfx"]/div/div[2]/table[31])[row]//td)[3] to price
forex_rate = [name,price]
write csv_row(forex_rate) to number6.csv

Any help would be greatly appreciated. Thank you

您好，请问一下，桌面应用端可以提取数据吗，谢谢！

Hi @Sora1433, closing this issue as it's a duplicate of #822
Will have a look on that asap! Was away past few months - https://github.com/tebelorg/RPA-Python/issues/144
Hi @python-linming, yes it is possible but not directly. The general method is you can use read step using OCR to read from a region on the screen, or you can double click on the data and then use keyboard step to copy the data onto clipboard, before accessing the data using clipboard() function.
I'll reply at your issue #839 so that you can provide more details on your scenario.


[crush][1.20.1] while place "Fluid Infuser" near pipes with water an energy

beta6 version, also check latest from actions.
java.lang.NullPointerException: Cannot invoke "igentuman.nc.handler.sided.SidedContentHandler$RelativeDirection.ordinal()" because "relativeDirection" is null
crash-2024-05-12_00.19.06-server.txt

@tabr i was not able to reproduce this issue by any means. But latest commit should cover this problem

@tabr i was not able to reproduce this issue by any means. But latest commit should cover this problem

Yeah, its works, thanks!

there was a mekanism gas (oxygen) connection...


Add integration tests covering searching and reading translated entities

1. Why is this change necessary?
https://github.com/shopware/shopware/pull/3819 changes which translated fields are actually selected in database queries, i.e. reducing the selected fields to a minimum. Since those changes have not been covered by any tests yet, this PR adds integration tests that will serve as a baseline for that other PR.
2. What does this change do, exactly?
This PR adds integration tests covering Shopware\Core\Framework\DataAbstractionLayer\Dbal\EntitySearcher::search() and Shopware\Core\Framework\DataAbstractionLayer\Dbal\EntityReader::read() when working with translated fields. They should cover at least the scenarios mentioned in https://github.com/shopware/shopware/pull/3819#issuecomment-2270643347 plus more.
3. Describe each step to reproduce the issue or behaviour.
n/a
4. Please link to the relevant issues (if any).

https://github.com/shopware/shopware/pull/3819

5. Checklist

[x] I have rebased my changes to remove merge conflicts
[x] I have written tests and verified that they fail without my change
[x] I have created a changelog file with all necessary information about my changes
[ ] I have written or adjusted the documentation according to my changes
[x] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfil them.

Nice! Thanks @svenmuennich - can you maybe take a look at the PHPStan issues then we can get this imported 😄

Nice! Thanks @svenmuennich - can you maybe take a look at the PHPStan issues then we can get this imported 😄

Oh, I didn't see them because the CI passed 😄🤔

Thanks for the MR @svenmuennich it's merged 🥳 - maybe you can rebase https://github.com/shopware/shopware/pull/3819 now.


navigateUp not working as expected

Screen1
navigator.navigate(Screen2Destination) {
    launchSingleTop = true
    popUpTo(NavGraphs.root) {
        inclusive = true
    }
}

Screen2
navigator.navigateUp()
First time I do navigator.navigateUp() a new activity is opened and I don't understand why, but I have a clue.
First time:
destinationCountOnBackStack = 1 && extras?.getIntArray(KEY_DEEP_LINK_IDS)  == null

@MainThread
    public open fun navigateUp(): Boolean {
        // If there's only one entry, then we may have deep linked into a specific destination
        // on another task.
        if (destinationCountOnBackStack == 1) {
            val extras = activity?.intent?.extras
            if (extras?.getIntArray(KEY_DEEP_LINK_IDS) != null) {
                return tryRelaunchUpToExplicitStack()
            } else {
                return tryRelaunchUpToGeneratedStack()
            }
        } else {
            return popBackStack()
        }
    }

// So the calls are
tryRelaunchUpToGeneratedStack()
// And
parentIntents.startActivities()
activity?.finish()

Second time:
destinationCountOnBackStack = 1 && extras?.getIntArray(KEY_DEEP_LINK_IDS)  != null

//So it is calling tryRelaunchUpToExplicitStack() and this does nothing and does not finish the activity (i think it was the behavior of NavController in compose)...

Maybe destinationCountOnBackStack = 1 is incorrect since i have nothing on backstack. The Screen2 is the only one displayed

As another clue, system onBackPressed seams working well

Hi @rogersixtemia !
Thanks for deep analysis. It seems however that this is maybe an issue with official compose navigation so the best ideia is to open an issue on Google issues or ask first on stack overflow / Kotlin slack.
Would you mind doing that? Thanks 🙏
In the meantime we can close this issue since it’s really not related with Compose Destinations.

Hello, and thanks for the fast support, I'll try oppening and issue in Compose Destinations and see if they can fix it.
Btw, which option do you think is the best as a workaround. Trying to use onBackPressedDispatcher?.onBackPressed() of the activity or there is another method in your wrapper for that?

You mean open an issue on jetpack compose navigation 😁
No, there is nothing introduced here by compose destinations.


Remove retry from non-idempotent function

Hey fellows,
So, this is just a first step to address #303, just to avoid having incorrect results silently.
We should be mindful where to put retries in this code, because retries are really meant for code that will (probably, but as far as the code knows, always) return the same result if it is retried.
I couldn't find a good place to put more retries in this code, at least not as it is now, because it's depending on state for a good bunch of things.
So, I don't know what could be a next step to address this (leave it without retries, refactor some place?) -- would love to hear some ideas.

I'm merging this, and we can continue discussion at the issue https://github.com/scrapinghub/exporters/issues/303


Add a cron workflow to run TPC-C with async commit enabled

What problem does this PR solve?
Add a TPC-C workflow with async commit enabled
What is changed and how does it work?
Check List
Tests

No code

Code changes
Side effects
Related changes
Does this PR introduce a user-facing change?:

NONE

@mahjonp PTAL


App crashes on launch on Android

The app crashes on launch on Android. ADB logcat:
https://gist.github.com/vchimev/c0a0b1b8a55825e492a763ffc967fb07
Reproduced by: tns livesync android --watch

This issue seemed to be related with the initialization of Firebase.

[ ] TODO: Make sure it does not appear with<EMAIL_ADDRESS>when released.


Support emacs readline bindings when adding new log entry

My apologies if this request has come up, I searched but was unable to find anything.
Is your feature request related to a problem? Please describe.
Yes, readline keyboard shortcuts are inaccessible from the changie new prompt.
When creating a new entry using changie new, the emacs keyboard shortcuts for readline (using both bash & zsh shells) are unusable, making traversing the input prompt tedious.
Example shortcuts:

GNU Readline - Readline Movement Commands

Alt-B: Jump back one word (backward-word)
Alt-F: Jump back one word (backward-word)
Ctrl-A: Jump to start of line
Ctrl-E: Jump to end of line

GNU Readline - Readline Killing Commands

Ctrl-U: Delete current line to start
Ctrl-K: Delete current line to end

Describe the solution you'd like
Requesting support for the following emacs readline keyboard shortcuts:

C-a (beginning-of-line)
C-e (end-of-line)
M-b (backward-word)
M-f (forward-word)
C-w (unix-word-rubout)
C-u (unix-line-discard)
C-k (kill-line)
M-d (kill-word)
C-y (yank)

Listed from most important to least important, movement would be most helpful, the kill/yank commands aren't really needed but would be nice to have access to.
Describe alternatives you've considered
I've seen others mention using other tools for formatting text such as #385.
Additional context
References:

GNU Readline Library Documentation - Bindable Readline Commands - Commands supporting keybinding
Shortcuts list

chzyer/readline - shortcut.md – List of readline emacs shortcuts
Readline Cheat Sheet - Emacs editing mode keyboard shortcuts

@shambles07 Hey, so a PR was just merged a short time ago changing the prompt package from promptui to one based on bubbletea ( https://github.com/miniscruff/changie/pull/464 ). I do not use emacs or any of these shortcuts but if you wouldn't mind trying the source version of Changie.
The base package for inputs is now based on bubbletea, so in practice I believe this change would likely need to go in the text input package, I think bubbles.

@shambles07 v1.12.0 just released with the new prompt tool, this looks to support at least some of what you are looking for. For context, https://github.com/charmbracelet/bubbles is the base project of text input, so these keybindings would go there.

Thanks for the quick reply, your help is much appreciated! Let me try this out and I'll get back to you.

@miniscruff this worked perfectly—thanks again!


Confusing information on https://docs.microsoft.com/en-us/azure/storage/files/storage-files-identity-ad-ds-assign-permissions?tabs=azure-cli#which-configuration-should-you-use

[Enter feedback here]
This paragraph is confusing https://docs.microsoft.com/en-us/azure/storage/files/storage-files-identity-ad-ds-assign-permissions?tabs=azure-cli#which-configuration-should-you-use
It says "There are two ways you can assign share-level permissions" then a bit later it says "There are three scenarios where we instead recommend using default share-level permissions assigned to all authenticated identities"
It is not clear on how and when each type of permission should be granted. An example scenarios would be helpful.

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

ID: 8e3082ce-6408-d199-7fdc-361966b4c6a8
Version Independent ID: ed68d7f1-ade8-2988-309f-033480441252
Content: Control access to Azure file shares - on-premises AD DS authentication
Content Source: articles/storage/files/storage-files-identity-ad-ds-assign-permissions.md
Service: storage
Sub-service: files
GitHub Login: @roygara
Microsoft Alias: rogarana

Expanded this section and clarified when setting a default share-level permission is appropriate. #please-close


bread bot yes

what the heck should it mean bruh
Tinan is not the main priority right now + we close/ignore pull requests like this because it's enough events.


script failure, index x does not exist

Describe the bug
script failure, index x does not exist
Testing the commit:
Fix call a callback when exiting elevator (https://github.com/scemino/engge/commit/aeb37dae999a0187eb837858dd4839b22ee7ec93)
To Reproduce
In part 1, driving Boris, once crossed the door, clicking before the sign that has the light, in that area the failure happens, I have not been able to determine the right point, but when pressing several times for that area it ends up appearing .
Expected behavior
Screenshots
I have not taken, but if they are needed I contribute
Desktop (please complete the following information):

OS: Windows x64
Version 10

Additional context
Log:
[2020-05-31 00:40:28.504] [log] [trace] start thread (anonymous TutorialHelpers.nut(172)): 300322
[2020-05-31 00:40:28.507] [log] [error]
An error occured in the script: the index 'x' does not exist
[2020-05-31 00:40:28.507] [log] [error]
CALLSTACK
[2020-05-31 00:40:28.509] [log] [error] *FUNCTION [unknown()] TutorialHelpers.nut line [180]
[2020-05-31 00:40:28.509] [log] [error]
LOCALS
[2020-05-31 00:40:28.511] [log] [error] [dir] 1
[2020-05-31 00:40:28.512] [log] [error] [pos] TABLE
[2020-05-31 00:40:28.512] [log] [error] [this] TABLE
[2020-05-31 00:40:28.513] [log] [error]
An error occured in the script: call failed
[2020-05-31 00:40:28.515] [log] [error]
CALLSTACK
[2020-05-31 00:40:28.516] [log] [error] *FUNCTION [showTarget()] TutorialHelpers.nut line [172]
[2020-05-31 00:40:28.517] [log] [error] *FUNCTION [tutorialScreenPos()] TutorialHelpers.nut line [199]
[2020-05-31 00:40:28.517] [log] [error]
LOCALS
[2020-05-31 00:40:28.518] [log] [error] [dir] 1
[2020-05-31 00:40:28.519] [log] [error] [pos] TABLE
[2020-05-31 00:40:28.519] [log] [error] [this] TABLE
[2020-05-31 00:40:28.520] [log] [error] [i] 1
[2020-05-31 00:40:28.521] [log] [error] [pos] TABLE
[2020-05-31 00:40:28.521] [log] [error] [this] TABLE
[2020-05-31 00:40:28.526] [log] [trace] stop thread 300317
[2020-05-31 00:40:28.528] [log] [trace] stop thread 300322

Thank you I will try to reproduce it

Sorry I did my best to reproduce it, but no luck, it works for me, maybe a video can help me understand what I do wrong.

I'm sorry ... I think it was a bug derived from a corrupt save game, so the issue can be closed.

No problem, thank you for the feedback


WD_TABLE_ALIGNMENT has not CENTER member

Whenever i am setting the table cell alignment to center , i am writing
table.alignment = WD_TABLE_ALIGNMENT.CENTER
and it is throwing me the above title error

Please post support questions on StackOverflow using the "python-docx" tag. Post the minimum code required to reproduce the error and the full stack-trace produced.


app: Add createLink() API request implementation

The next commit will use this function to implement the click handler.

Coverage decreased (-0.1%) to 98.142% when pulling edbd138789c580580721763603b33a232b1f35a1 on ui-create-link into ab6828ae55fb0af7a3086c1e3337719b26dae395 on master.


Feature/full clean on save detached

Purpose
Currently, Django FSM field transitions do not check to see if the target state is a valid choice. This can lead to objects ending up in indeterminate states, breaking the point of a FSM to begin with. This PR adds field validations in the transition function before the save() function is called.
Methodology
Django does not check the validity of the CharField in it's save() function, but rather in the clean_fields() function that is part of full_clean(). Due to the way write-protection works, simply adding a full_clean before the save function was not enough; clean_fields() uses setattr() to ensure the value of the field is clean, which is not allowed as long as the field is protected. To get around this, I temporarily disable the field's write protection, do the full clean, then re-enable it prior to saving. This protects the field from unintended outside side-effects while still allowing it to be validated as a proper state.
Note
This PR targets version 1.6, prior to backwards-incompatible changes being introduced. I do not intend for this PR to be merged into the current master branch, but wanted to leave a record of the work here in case any other dev out there is stuck on 1.6 and looking for a solution like this.

thanks for this, i was wondering why full_clean kept blowing up with AttributeError: Direct state modification is not allowed
It can be easily replicated if you apply this patch to test_lock_mixin.py and run the tests
(fsm) root@af5f92afd27b:/home/django-fsm/tests# git diff
diff --git a/tests/testapp/tests/test_lock_mixin.py b/tests/testapp/tests/test_lock_mixin.py
index c619771..cf5f53e 100644
--- a/tests/testapp/tests/test_lock_mixin.py
+++ b/tests/testapp/tests/test_lock_mixin.py
@@ -18,6 +18,10 @@ class LockedBlogPost(ConcurrentTransitionMixin, models.Model):
     class Meta:
         app_label = 'testapp'

+    def save(self, *args, **kwargs):
+        self.full_clean()
+        super().save(*args, **kwargs)
+

 class ExtendedBlogPost(LockedBlogPost):
     review_state = FSMField(default='waiting', protected=True)


Develop a UTM without sandboxing

Describe the issue
Sandboxed applications cannot store virtual machines on an external hard disk, which is not conducive to hard disk storage, and my hard disk does not have enough space for me to store so many virtual machines.
If I use what is said on the network, create a virtual disk image, and then mount this image into a UTM container, I have tried this method, it will lead to instability of the virtual machine and even the host operating system.
I believe that many users have an urgent need to store virtual machine files on an external hard disk, and I hope this suggestion can be accepted.
Configuration

UTM Version: Latest Version
macOS Version: 13.3
Mac Chip : Apple Silicon

You can attach the virtual disk as a removable media, then its location can be anywhere.  I am doing exactly that since I don't want to sacrifice sandboxing (a security feature) for convenience.  However, please check #5170 for the current inconvenience (the removable drives are turning read-only on the UTM shutdown).

Can virtual removable disk image be used as a system disk for OS?

If the system disk can exist as a removable disk, can UTM develop the function of skipping the creation of the internal hard disk, because this function can ignore the creation of the virtual built-in hard disk and directly create an external virtual removable disk.

Thank you!

I don't see why not -- all in all this is how you install a Linux distro: you boot from the removable disk image.
Yeah, this would be nice, currently it forces you to create one (but you can re-arrange stuff before the VM launch, IIRC)

So, for the 2nd topic, do I need to open an issue again to suggest them to implement this function?

I've decided that I'll close this issue and create a new one.

#5172

I think releaseing a sandboxed UTM for macOS does more harm than good, so I think it's worth publishing an unsandboxed UTM.

Classic XY problem. Having sandbox is a reason that physical drives cannot be accessed directly but removing sandboxing does not automatically mean that such a feature will be supported. #5051 is one example of a feature request for booting off a physical drive. Sandboxing is good practice for all apps because it prevents malware that compromises your app (or a malicious app) from doing any damage to your system.


CI: Use repo/branch with SAI PTF DASH support

At this moment, all changes required to run SAI PTF Thrift tests on devices with fewer ports (like DASH devices) are done in dev repos. Meanwhile the changes are upstreaming into main SAI/PTF repos, changing CI to use this development repo to be able to run PTF tests now. Once all PTF/SAI Thrift changes are merged, this submodule needs to be changed back to use mainstream SAI repo.
Signed-off-by: Volodymyr Mytnyk<EMAIL_ADDRESS>

LGTM, you need to sign the CLA

CLA looks ok now and CI is happy with the change


Spark generic catalog supprt procedure

Purpose

Linked issue: close #2433

Tests

API and Format

Documentation

add in https://github.com/apache/incubator-paimon/pull/2414

Sorry for this @monkeyboy123


Pressing "My stakes" directs to the last selected bundle

Steps to reproduce:

On freshly loaded page press "My stakes"
Press "Details" for any bundle in the list
Press "My stakes" or "Dip staking" then:
previously selected bundle details are shown
Expected:
Bundles list is shown

Paid


Parsing error: Loader Url has no sync mode

Hi. I was trying out this eslint plugin today and I am facing this error in all my GQL files both when linting via the CLI as well as the VSCode extension.

This error is thrown for every GQL file I use.
I tried to isolate the problem by removing all other eslint rules and just having this plugin around and still had this issue.
My graphql-config is configured correctly cause both the codegen and the VSCode GraphQL extension which uses it are working correctly. I am using multiple projects with both remote and local schema which works well with codegen and extension.
I also noticed other people reporting similar error but with apollo eslint rather:
https://github.com/apollographql/eslint-plugin-graphql/issues/287
https://github.com/apollographql/eslint-plugin-graphql/issues/270#issuecomment-700032602
Any clues? Thanks.
My .eslintrc file:
{
  "overrides": [
    {
      "files": ["*.gql"],
      "parser": "@graphql-eslint/eslint-plugin",
      "plugins": ["@graphql-eslint"],
      "rules": {
        "avoid-operation-name-prefix": [
          "error",
          { "keywords": "get" }
        ],
        "input-name": [
          "error",
          { "checkInputType": true }
          ],
          "description-style": [
          "error",
          { "style": "block" }
          ],
          "naming-convention": [
          "error",
          {
            "FieldDefinition": "camelCase",
            "ObjectTypeDefinition": "PascalCase"
          }
          ],
          "no-anonymous-operations": ["error"],
          "require-deprecation-reason": "error",
          "no-case-insensitive-enum-values-duplicates": ["error"],
          "no-operation-name-suffix": ["error"],
          "require-id-when-available": ["error",
          {
            "fieldName": "id"
          }
          ],
          "validate-against-schema": ["error"],
          "require-description": [
            "error",
            { "on": ["ObjectTypeDefinition", "FieldDefinition"] }
          ]
      }
    }
  ]
}

My package.json
"name":"...",
"version":"...",
"scripts": {
    "lint": "eslint --ext=.gql ./packages",
}
"devDependencies": {
    "@graphql-codegen/add": "^2.0.1",
    "@graphql-codegen/cli": "^1.17.10",
    "@graphql-codegen/typed-document-node": "^1.17.9",
    "@graphql-codegen/typescript": "^1.17.10",
    "@graphql-codegen/typescript-operations": "^1.17.8",
    "@graphql-codegen/typescript-resolvers": "^1.17.10",
    "@graphql-eslint/eslint-plugin": "^0.4.1",
    "@graphql-typed-document-node/core": "^3.1.0",
    "@types/body-parser": "^1.19.0",
    "@types/express": "^4.17.8",
    "@types/node": "^14.11.8",
    "@types/qs": "6.9.5",
    "@typescript-eslint/eslint-plugin": "^4.4.1",
    "@typescript-eslint/parser": "^4.4.1",
    "concurrently": "^5.3.0",
    "eslint": "^7.11.0",
    "globby": "^11.0.1",
    "morgan": "^1.10.0",
    "nodemon": "^2.0.5",
    "plop": "^2.7.4",
    "rimraf": "^3.0.2",
    "typedoc": "^0.19.2",
    "typescript": "4.0.3",
    "utility-types": "^3.10.0"
  },
  "dependencies": {
    "graphql": "^15.4.0",
    "graphql-modules": "^1.0.0-alpha.2"
  }

CC: @dotansimha

I see, thank you for reporting this @tvvignesh .
@kamilkisiela @ardatan what do you think? Do you think there is a way to allow sync loading from a url? ESLint parser is limited to sync only

Doing http in sync will require to run it through child_process so it will be node-only. Not sure if it's an issue or might be in future.

I think it's node-only any way, no? we are using fs and other things there... just make sure to require it lazily..
Or maybe you can check the environment before running it.

I think it's node-only but Ricky did some work to run it in browser and to make it work with GraphiQL. We can go with node-only.

@kamilkisiela @dotansimha sync-fetch has both browser and node implementations.

Thank you @ardatan for the fix (https://github.com/ardatan/graphql-tools/pull/2192).
@tvvignesh can you please try to add a Yarn resolution for that specific version of that loader? It should allow you to check the fix before we merge it.
  "resolutions": {
     "@graphql-tools/url-loader": "6.4.0-alpha-00cebee1.0"
  }

@dotansimha Sure. Will check and report back in 10 minutes.

@dotansimha @ardatan Perfect! This works great. Just tested it out. You can close this.

Awesome, thanks, let's keep it open until we'll have graphql-tools > graphql-config > graphql-eslint released :)

graphql-config @ 3.1.0 available now, please update and it should fix that issue :)


Bump protobuf requirement to 3.12.x

Fixed #3110.

@googlebot please rescan

@googlebot has turned into "flakeybot"

Thank you - let's hold off the release until I understand the implications of the float truncation better.

@googlebot please rescan

Automerge cancelled: A required status check is not present.
Missing statuses: ['cla/google']


Loading page gets stuck when a network issue happens

Description
When there's a network issue, the loading page gets stuck forever.

is not producable any more
tried it on edge connection and still loads fine but takes time


Update Meet the Team photos for New Members

It's that time of the semester again, kids...
First, we'll check in with Julian to make sure everyone's photo has been taken / which are available.

Jaedyn and Brenna request that their photos do not change, please!


[azservicebus] Some naming changes for raw AMQP message support for consistency with other stacks

Some naming changes to be more consistent with other track 2 SDKs as well as the AMQP spec:

Rename the AMQPMessage to be AMQPAnnotatedMessage (track 2 consistency, also matches terminology in the spec)
Create an AMQPAnnotatedMessageBody type to house the .Value, .Sequence and .Data fields. This matches more with the logical format of an AMQP message, where the Body is comprised of sections (Data, Value, Sequence), rather than them just being free-floating fields on a message.

/azp run go - azservicebus


Link to files instead of database objects

The realtime reporter can open source objects from various contexts.

Location
Object
Double click action

Overview table
Row
Opens test package specification at line of test procedure

Failures table
Row
Opens test package body at failed line

Failure text
Hyperlink
Opens referenced object at referenced line

Errors
Hyperlink
Opens referenced object at referenced line

Warnings
Hyperlink
Opens referenced object at referenced line

Info
Hyperlink
Opens referenced object at referenced line

These links always open a database object (see use of DrllLinkClass in v1.1.0). This is unwanted in a file based development, where you want to maintain files under version control and deploy them in a subsequent step.
As @thatjeffsmith pointed out on this Twitter post it is possible to configure SQL Developer to use files instead of database objects. Unfortunately this works only for debugging sessions. However, SQL Developer stores the associated files and has a built-in feature to open it. The question is, if the relevant classes are exposed via OSGi bundles and can be used in our extension.
Even if the underlying API is not exposed, we can access the necessary information directly. The associated files are stored in project.qbql. In the folder ${ide.system.dir}/o.sqldeveloper/. The file structure is quite simple and can be easily parsed and used to implement a custom link feature.  Here's an example of the file content:
[fileURL dbURL]
 "file:/Users/phs/github/plscope-utils/database/utils/package/parse_util.pks" "sqldev.nav:IdeConnections%2523plscope-odb-macphs//PLSCOPE/PACKAGE/PARSE_UTIL"
 "file:/Users/phs/github/plscope-utils/database/utils/package/dd_util.pkb" "sqldev.nav:IdeConnections%2523plscope-odb-macphs//PLSCOPE/PACKAGE/DD_UTIL/PACKAGE+BODY/DD_UTIL"
 "file:/Users/phs/github/plscope-utils/database/utils/package/lineage_util.pks" "sqldev.nav:IdeConnections%2523plscope-odb-macphs//PLSCOPE/PACKAGE/LINEAGE_UTIL"
 "file:/Users/phs/github/plscope-utils/database/utils/package/plscope_context.pkb" "sqldev.nav:IdeConnections%2523plscope-odb-macphs//PLSCOPE/PACKAGE/PLSCOPE_CONTEXT/PACKAGE+BODY/PLSCOPE_CONTEXT"
 "file:/Users/phs/github/plscope-utils/database/utils/package/plscope_context.pks" "sqldev.nav:IdeConnections%2523plscope-odb-macphs//PLSCOPE/PACKAGE/PLSCOPE_CONTEXT"
 "file:/Users/phs/github/plscope-utils/database/utils/package/type_util.pkb" "sqldev.nav:IdeConnections%2523plscope-odb-macphs//PLSCOPE/PACKAGE/TYPE_UTIL/PACKAGE+BODY/TYPE_UTIL"
 "file:/Users/phs/github/plscope-utils/database/utils/package/dd_util.pks" "sqldev.nav:IdeConnections%2523plscope-odb-macphs//PLSCOPE/PACKAGE/DD_UTIL"
 "file:/Users/phs/github/plscope-utils/database/utils/package/type_util.pks" "sqldev.nav:IdeConnections%2523plscope-odb-macphs//PLSCOPE/PACKAGE/TYPE_UTIL"
 "file:/Users/phs/github/plscope-utils/database/utils/package/lineage_util.pkb" "sqldev.nav:IdeConnections%2523plscope-odb-macphs//PLSCOPE/PACKAGE/LINEAGE_UTIL/PACKAGE+BODY/LINEAGE_UTIL"
 "file:/Users/phs/github/plscope-utils/database/utils/package/parse_util.pkb" "sqldev.nav:IdeConnections%2523plscope-odb-macphs//PLSCOPE/PACKAGE/PARSE_UTIL/PACKAGE+BODY/PARSE_UTIL"

So, this is doable. We could even think about providing a bulk-link-file-population-feature. Maybe we should do that anyway to be independent of the SQL Developer's file linking feature which has a different scope.

In another project we are building a custom workspace for SQL Developer. These concepts might be used here as well. Therefore I moved this issue to milestone v1.3.0

Too complicated. Closing issue.


Collect telemetry on all unsupported features

In #11815, we collected telemetry on what error triggered the fallback bar. The first error message is what is shown in the fallback bar. We need expand this and collect telemetry on all error messages to give us a better understanding of the frequency of each type of error.
Example with more than one error:
https://www.irs.gov/pub/irs-pdf/f1040.pdf

One possible way of doing this could be to decouple the showing of the fallback bar from the reporting of telemetry data, to not complicate e.g. the PDFViewerApplication.fallback method unnecessarily; perhaps something along these lines:

Remove the PdfJsTelemetry.onFallback(featureId); line from ChromeActions.fallback; see https://searchfox.org/mozilla-central/rev/559b25eb41c1cbffcb90a34e008b8288312fcd25/browser/extensions/pdfjs/content/PdfStreamConverter.jsm#499
Add a new case, e.g. "fallback" (or perhaps something better named) to the switch-block in ChromeActions.reportTelemetry (perhaps similar to the "documentStats" case); see https://searchfox.org/mozilla-central/rev/559b25eb41c1cbffcb90a34e008b8288312fcd25/browser/extensions/pdfjs/content/PdfStreamConverter.jsm#424-481
Always report telemetry in PDFViewerApplication.fallback, by adding something likethis.externalServices.reportTelemetry({
  type: "fallback",
  featureId,
});

immediately after line https://github.com/mozilla/pdf.js/blob/8fc1126b5a2b6d2fa0cfa98a061882ef21c1abc9/web/app.js#L865-L869

Upstream bug to add telemetry in Firefox: https://bugzilla.mozilla.org/show_bug.cgi?id=1643402

/botio-linux preview


td_upload doesn't follow apikey in Td object

template embulk yaml file uses apikey: {{ env.TD_API_KEY }}.
Then, it always requires an environment variable instead of apikey in td object.
https://github.com/chezou/RTD/blob/a3a6bdd7daf4ca0d54eae96f84d82de9242d457f/inst/extdata/tsv_upload.yml.liquid#L6
When I want to use it like this, it doesn't work well.
client <- Td(apikey="xx/xxxxxxx", endpoint="api.treasuredata.com")

@toru-takahashi Thanks for your report. RTD should ensure setting TD_API_KEY in this line https://github.com/chezou/RTD/blob/master/R/td.R#L72 for embulk.

Thank you!


Multi Line properties support

(Original issue 445 created by None on 2009-10-20T21:35:43+00:00)
I have a .properties file which has multiple lines for some properties.
Example:
PROP = foo \
bar
This is valid content for a properties file, but it marks everything after the first line as an error.
Reported by guest

(Original issue was assigned to thatch)
(Original issue 445 last updated on 2010-08-22T10:07:56+00:00)
(Issue automaticaly closed due to status in Bitbucket: resolved)

(Original comment by gbrandl on 2010-08-22T10:07:56+00:00)
Merged in main.

(Original comment by None on 2010-07-23T08:21:22+00:00)
Please consider #494 also, line continuation symbol ('\') is not required to have multi-line property values.

(Original comment by thatch on 2010-06-07T22:22:04+00:00)
Done for 1.4 in my branch.

(Original comment by thatch on 2009-12-23T19:23:57+00:00)
True.  We'll need to revisit the ini lexer to fix this.


Add ability to pass CDS Service supplied parameter in a SMART app launch

@kpshek , @isaacvetter , @brynrhodes - I have made changes based on the discussion in https://github.com/cds-hooks/docs/issues/59. Please let me your thoughts

While at FHIR DevDays last week, I talked with a couple guys from @StayWell who asked me for the same functionality described in #59 (and what this PR is attempting to address). I just emailed them to ask them to provide their feedback on the various approaches we've been discussing for their input for an additional perspective.

I think a new attribute on a link (specifically for links of type smart only) is the most straightforward approach to solve this particular need. It is more explicit as to the use case we are attempting to solve and works when a card has multiple SMART app links.
It is not clear to me where else an opaque string on the CDS card would be used (outside of being passed to the SMART app on launch).

@kpshek Appreciate your input. I am ok to have something at the link level for this use case

It isn't clear to me why we are adding this card-level attribute for a value that is only intended to be passed to a SMART app via a launch parameter. Can you elaborate on why the proposal to add a new attribute on the link wasn't ideal?

I think a new attribute on a link (specifically for links of type smart only) is the most straightforward approach to solve this particular need

which proposal are you referring? Can you point to this? If not, can you propose what you have is mind in issue [#59]
For example : are you thinking of leveraging query params in the url like
{
      "cardid": "345"
      "summary": "Card 1 - Clinical Pathway 1",
      "indicator": "info",
      "detail": "This is an example app card.",
      "links": [
        {
          "label": "SMART App",
          "url": "https://smart.example.com/launch?foo=a",
          "type": "smart"
        }
      ]
    }

vs having an additional attribute like below. If so were you thinking extension vs dedicated attribute name
{
      "cardid": "345"
      "summary": "Card 1 - Clinical Pathway 1",
      "indicator": "info",
      "detail": "This is an example app card.",
      "links": [
        {
          "label": "SMART App",
          "url": "https://smart.example.com/launch",
          "type": "smart",
          "foo": "a"
        }
      ]
    }

@kpshek - thx for reviewing my changes, as for your comment https://github.com/cds-hooks/docs/pull/112#pullrequestreview-78423057, I will wait to arrive at a consensus on this https://github.com/cds-hooks/docs/pull/112#issuecomment-347258271 and redo the PR

@yashaskram - I was referring to something similar to the example noted under "A link in CDS card has params data" in #59. Here is a concrete proposal what I'm in favor of implementing here:
{
  "summary": "Example card",
  "indicator": "info",
  "source": {
    "label": "Example CDS Service"
  },
  "links": [
    {
      "label": "SMART App",
      "url": "https://smart.example.com/launch",
      "type": "smart",
      "cdsHooksContext": "Some opaque (to the EHR) string that will come back alongside your OAuth 2 access token on a SMART app launch"
    },
    {
      "label": "Another SMART App",
      "url": "https://smart2.example.com/launch",
      "type": "smart",
      "cdsHooksContext": "Another context value for this SMART app"
    },
    {
      "label": "An absolute link",
      "url": "http://cds-hooks.org",
      "type": "absolute"
    }
  ]
}

The cdsHooksContext field should only ever be valued if the link type is smart. cdsHooksContext is not valid for absolute links.
The cdsHooksContext field and value will be sent to the SMART app alongside the other launch context when the SMART app is launched. See "Launch context arrives with your access_token" in the SMART documentation. For instance, here is what would come back for the first SMART app in my example:
{
  "access_token": "secret-xyz",
  "patient": "123",
  "cdsHooksContext": "Some opaque (to the EHR) string that will come back alongside your OAuth 2 access token on a SMART app launch"
  // etc...
}

@kpshek - I like your proposal. looks like we are back to the start point
@isaacvetter , @brynrhodes - thoughts? based on your input I can make the changes to my PR

Hey @yashaskram , guys,
Yeah - the above sample message from @kpshek makes sense - the cardInstance that I was pushing towards had the disadvantage of not accounted for multiple smart links in a single card. Not allowing this parameter to be specified in an absolute link makes sense because this param should be passed as a SMART launch parameter (alongside the access token). A similar parameter should simply be put into the url (perhaps in the querystring) of an absolute link.
The only part of the above proposal that I object to, is the name: cdsHooksContext. Ultimately, it's not descriptive of the purpose of the element. How about: appSession or serviceAppId` or ... something that actually describes the intent and purpose of the field.
Isaac

@isaacvetter & team - how about the name - appcontext?

I struggled coming up with a descriptive name for this field as well. I originally named it appContext but changed it when I saw it alongside the other context variables in a SMART app launch. With that being said, I'm fine if we name this appContext (note the camelCase in keeping with our existing field naming conventions).

@travistcummings - can the HSPC Sandbox support passing arbitrary launch context to the SMART app per these proposed changes?
Tagging @zplata for the eventual cds-hooks/sandbox change that this will also require.

@kpshek The HSPC Sandbox launch will support additional parameters in the SOF launch url: https://example.com/launch.html?p1=abc&p2=xyz
When the CDS Hooks sandbox registers a launch context, it can also provide a params map object that will be passed to the client along side their access token:
launch context:
{
...
"parameters":{
"patient":"BILIBABY",
"appContext": {
"p1": "abc",
"p2": "xyz"
},
"need_patient_banner":false
}
}
SOF launch response:
{
"access_token": "eyJhbGc...",
"token_type": "Bearer",
"expires_in": 86399,
"scope": "patient/Observation.read launch patient/Patient.read patient/Observation.write",
"patient": "BILIBABY",
"need_patient_banner": false,
"appContext": {
"p1": "abc",
"p2": "xyz"
}
}

That's great, thanks @travistcummings!


Support for multiple users?

Hello Friends:
I'm thinking of running code-server on a well-equipped home server for a small class I'm giving.
Does code-server support multiple users out of the box? If not, perhaps running parallel instances, each listening on a unique HTTP port might do? Or maybe you have a better idea based on your knowledge of the product and it's roadmap?
Thank you in advance! (and for this solution). =:)

Ah, never mind. I found the main thread about this here. =:)

Awesome!


Move assets from public/ to assets/

[x] tinymce.css (requires that the TinyMCE editor be configured to use it with the relevant digest)
[ ] others?

Currently if we change the assets in public, they won't update for the user (due to the lengthy cache control).

Done in #515


css error all messed up

Describe the bug
I try to install the lib but the css gets all messed up.
To Reproduce
just install according to the documentation
Screenshots

The image above is how it looks in the browser. I don't have any errors in the console

the image above is how the code is.
am I doing something wrong?

I don't see any issue in your code, could you share some more details for example Vue and the plugin versions? Also it would be helpful if you could share a minimal working example that regenerates your issue.

Closed due to inactivity


Ask: change date label text

Change the label for the date on Ask answer pages.
Additions

last reviewed in translations file

Changes

Change date label text from updated to last reviewed on Ask answer pages

How to test this PR

Check out branch
Navigate to an Ask answer page and verify that date label is now last reviewed
Click link to Spanish version of page and verify that date label is now revisado

Screenshots
English page

Spanish page

Thanks for reviewing, @higs4281!


Generic class sometimes missing generic arguments in name after rename protection

I've got a case where a generic type does not have its generic arguments applied to the name - instead, the name is obfuscated and the generic arguments are trimmed off (A'1 -> _ujkljsfuoiu instead of the expected A'1 -> _ujkljsfuoiu'1. It seems to happen with the following setup:

Enable decodable renaming
Create a non-generic class, A
Create a generic class, A`1
Apply renaming protection

The problem only appears when the non-generic class A is loaded/obfuscated before the generic variant. If the generic class is processed first, it is named correctly.
As a result, attempting to run the program/load an assembly like this fails with a duplicate type exception similar to the following:
Unhandled Exception: System.BadImageFormatException: Duplicate type with name '_KXAnX9u6N2HxWpPt3OaOUtHSGLF' in assembly 'ConfuserTest, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null'.
Confuser version: 2.0-master
Minimal example: ConfuserTest.zip
Thanks!

Good find. The issue tracks back to the 1.x branch.
It will be fixed in 1.2 and 2.0.

The issue is fixed in master and release/2.0.
I'll keep the issue open until I also added a unit test for the issue. But you can use the current builds of both branches and have a working version.

Great, thank you!


[tool_crash] FileSystemException: Getting current working directory failed, OS Error: Operation not permitted, errno = 1

Command
flutter create --offline --template app --overwrite .

Steps to Reproduce

...
...
...

Logs
FileSystemException: Getting current working directory failed, OS Error: Operation not permitted, errno = 1
#0      _Directory.current (dart:io/directory_impl.dart:42:7)
#1      Directory.current (dart:io/directory.dart:136:25)
#2      FileSystemEntity._absolutePath (dart:io/file_system_entity.dart:555:32)
#3      _Directory.absolute (dart:io/directory_impl.dart:97:43)
#4      ForwardingFileSystemEntity.absolute (package:file/src/forwarding/forwarding_file_system_entity.dart:83:35)
#5      ForwardingFileSystemEntity.absolute (package:file/src/forwarding/forwarding_file_system_entity.dart:83:35)
#6      CreateBase.generateApp (package:flutter_tools/src/commands/create_base.dart:570:49)
<asynchronous suspension>
#7      CreateCommand.runCommand (package:flutter_tools/src/commands/create.dart:350:31)
<asynchronous suspension>
#8      FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:1336:27)
<asynchronous suspension>
#9      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
<asynchronous suspension>
#10     CommandRunner.runCommand (package:args/command_runner.dart:212:13)
<asynchronous suspension>
#11     FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:296:9)
<asynchronous suspension>
#12     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
<asynchronous suspension>
#13     FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:244:5)
<asynchronous suspension>
#14     run.<anonymous closure>.<anonymous closure> (package:flutter_tools/runner.dart:91:9)
<asynchronous suspension>
#15     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)

[✓] Flutter (Channel stable, 3.10.5, on macOS 13.3.1 22E772610a darwin-x64, locale en-QA)
    • Flutter version 3.10.5 on channel stable at /Users/mac/Documents/DEV/DEV_FILES/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 796c8ef792 (7 weeks ago), 2023-06-13 15:51:02 -0700
    • Engine revision 45f6e00911
    • Dart version 3.0.5
    • DevTools version 2.23.1

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0-rc4)
    • Android SDK at /Users/mac/Library/Android/sdk
    • Platform android-34, build-tools 34.0.0-rc4
    • Java binary at: /usr/bin/java
    • Java version Java(TM) SE Runtime Environment (build 17.0.7+8-LTS-224)
    • All Android licenses accepted.

[✗] Xcode - develop for iOS and macOS
    ✗ Xcode installation is incomplete; a full installation is necessary for iOS and macOS development.
      Download at: https://developer.apple.com/xcode/download/
      Or install Xcode via the App Store.
      Once installed, run:
        sudo xcode-select --switch /Applications/Xcode.app/Contents/Developer
        sudo xcodebuild -runFirstLaunch
    ✗ CocoaPods installed but not working.
        You appear to have CocoaPods installed but it is not working.
        This can happen if the version of Ruby that CocoaPods was installed with is different from the one being used to invoke it.
        This can usually be fixed by re-installing CocoaPods.
      To re-install see https://guides.cocoapods.org/using/getting-started.html#installation for instructions.

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

[✓] Android Studio (version 2022.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)

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

[✓] Connected device (3 available)
    • sdk gphone x86 64 (mobile) • emulator-5554 • android-x64    • Android 13 (API 33) (emulator)
    • macOS (desktop)            • macos         • darwin-x64     • macOS 13.3.1 22E772610a darwin-x64
    • Chrome (web)               • chrome        • web-javascript • Google Chrome 114.0.5735.133

[✓] Network resources
    • All expected network resources are available.

! Doctor found issues in 1 category.

Flutter Application Metadata
Exception: The flutter tool cannot access the file or directory.
Please ensure that the SDK and/or project is installed in a location that has read/write permissions for the current user.

Closing as duplicate of https://github.com/flutter/flutter/issues/98066


dry-run goal fails to provide a name as required by Helm 3

Helm is complaining that no name is provided in the "helm install" when the dry-run goal is executed.
Please add functionality to provide a name to the command or use the --generate-name flag.

Good catch, thank you!


Fix Travis OSX

They recently changed images, gotta tweak how we work with OpenSSL

r? @brson
(rust_highfive has picked a reviewer for you, use r? to override)

(should wait to land until travis is green)

@bors: r+

:pushpin: Commit 96fafda has been approved by alexcrichton

:hourglass: Testing commit 96fafda with merge b890f3f...

:sunny: Test successful - cargo-cross-linux, cargo-linux-32, cargo-linux-64, cargo-mac-32, cargo-mac-64, cargo-win-gnu-32, cargo-win-gnu-64, cargo-win-msvc-32, cargo-win-msvc-64
Approved by: alexcrichton
Pushing b890f3f44d7d266e3ed951f6beb884331c526049 to master...


multiwfn: fix hash

Jup, this was a longer journey than expected. Two additional dependencies, a type error and a new makeflags. Works now.


Accuracy Not Displayed in App

Saw this in Reddit and thought it was cool, so wanted to give it a try, The Loss function was correct but the accuracy wasn't displayed.
Colab notebook with which I tested this :
https://colab.research.google.com/drive/1o_-d_vbRIpNBq1F9ljj88GLnNvPvROO-
Attaching a Picture of the App

Thanks for bringing it to our concern. The package was made for tensorflow versions greater than 2.0. But colab uses tensorflow 1.14 by default.
We fixed the it to work with tensorflow versions lesser than 2.0. Please update the tensor-dash package to version 1.4.1.

*Kindly update to tensor-dash version 1.4.2


ReluOp - template brocken since 4cb09cb8b4d0859405e30f64087b76085d227bd3

Example from https://blog.hackster.io/simple-neural-network-on-mcus-a7cbd3dc108c does not compile any longer:
due to error:

.\models\deep_mlp.cpp:182:48: error: wrong number of template arguments (3, should be 2)
ctx.push(new ReluOp<uint8_t, float, uint8_t>(),
^
In file included from .\models\deep_mlp.cpp:8:
./uTensor/uTensor/ops/NnOps.hpp:76:7: note: provided for 'template<class T1, class TOut> class ReluOp'
class ReluOp : public Operator {
^~~~~~
.\models\deep_mlp.cpp:307:48: error: wrong number of template arguments (3, should be 2)
ctx.push(new ReluOp<uint8_t, float, uint8_t>(),
^
In file included from .\models\deep_mlp.cpp:8:
./uTensor/uTensor/ops/NnOps.hpp:76:7: note: provided for 'template<class T1, class TOut> class ReluOp'
class ReluOp : public Operator {
^~~~~~

caused, by commit of jakubvalis88 on 6 Mar commit 4cb09cb8b4d0859405e30f64087b76085d227bd3
previous commit (1c8eca4a7bbd952a87e5e9b2d055ba4131d16a3a) compiles.
Please have a look.

Hi, I actually have a PR for this open in codegen.
https://github.com/uTensor/utensor_cgen/pull/64

Hi,
sure I understand that, but what confused me also it that the TESTS, even if deprecated and the examples show 3 arguments instead of 2.
https://github.com/uTensor/uTensor/search?q=ReluOp&unscoped_q=ReluOp
Do you also have more a stable branch, where the releases bewteen cgen and uTensor core are synced with each other?
using the develop branch might not always be the best choice.
Thank you again for commenting!

Yes, we use master as stable :)

@miki89 I agree we should make the working combination more obvious. Perhaps, we should include the tags in the Readme?

The issue is we migrated the old RELU op (which was quantized) to one with "quantized" in the name for clarity.


Error overlay doesn't work on next

The build is complaining about process not being defined.

Solution for now is yarn build:prod --watch.


Added placeholder for extensions dropdown

Fixes https://github.com/microsoft/vscode/issues/193491

mini-demo


audit complaint "revision should not decrease" only shows after merging to master

Bug reports:
We recently updated a formula in one of our taps in https://github.com/osrf/homebrew-simulation/pull/146, which contained 3 commits.

https://github.com/osrf/homebrew-simulation/pull/146/commits/18106a93a06c44a1fa6738374daeb89d7efd94b6 updated the url and its sha256 (but forgot to reset the revision)
https://github.com/osrf/homebrew-simulation/pull/146/commits/bb4059ea61a2e05653e33d9388769cac3a2465b9 removed the revision and also an outdated patch
https://github.com/osrf/homebrew-simulation/pull/146/commits/7d7e2602551daa3bbfa6272821769097a6ea84a6 updated the bottle hash

Our travis script calls brew audit and a few other things on all the formulae in our tap, and it was happy with that third commit (not green because I merged and deleted before a 10.11 executor was available). Anyway, the point is that brew audit passed in that branch.
We merged to default with a merge commit (no squashing or rebasing), and now I see a brew audit complaint when I check that formula on master:
osrf/simulation/ignition-transport2:
  * revision should not decrease

I believe this happens because the first commit https://github.com/osrf/homebrew-simulation/pull/146/commits/18106a93a06c44a1fa6738374daeb89d7efd94b6 that has version 2.1.0_2 was merged to default without squashing. brew audit doesn't realize that was a mistake that was reverted and could have been squashed, but I didn't think it would matter.
To reproduce:

Find a formula that has a non-zero revision and checkout a new branch
Update a formula url and sha256 in one commit
Remove revision in second commit
brew audit should be happy on that branch
merge or rebase without squashing that branch to master, and then brew audit will start to complain

Workaround:
Always remove the revision in the same commit that bumps a formula version. I'm not sure if there's an easy way to detect this or if squashing should be recommended in the documentation.

I strongly advise your Travis script use brew test-bot --ci-auto for taps and additionally not use merge commits on formulae-based taps. I'm closing this out not because it's not a bug but as it doesn't affect our workflow we'll probably need a PR to get this fixed. Sorry but thanks for the great bug report.

I totally understand about closing the issue. If I get a flash of insight, I'll work on a fix, but in the meantime I'll try adding your recommendations to the Tap maintenance docs.

@scpeters Another thing I was thinking about that could be in the docs and/or https://github.com/Homebrew/brew/blob/master/Library/Homebrew/dev-cmd/tap-readme.rb is a default .travis.yml file that runs brew test-bot and sets the typical environment variables. Feel free to open a PR for either/both and we can discuss specifics there.


Upgrading 0.8 to 0.9

So I have tried to upgrade from Ghost 0.8 to 0.9 using the instruction shown your website. But it crashed.

Whats going on? I have no idea.
Edit
My NPM version is

@akshaybabloo Sorry to hear that! Unfortunately this is caused by somewhat unexpected behavior in npm. The solution is to delete your node_modules folder, and run npm install --production again.

I somehow remember that this was a problem before. Maybe the official docs should be changed to tell users delete the node_modules folder in EVERY error case, not only when the npm install --production step fails. Or even better (which I think would avoid many future problems): ALWAYS delete it before doing the upgrade. This would increase upgrade times slightly, but I think it is worth it.

@crepererum normally it's fine, the only time I recall this has been a problem was in the 0.9.0-beta2 release.
In the 0.9.0-beta.2 release, it was caused by a lodash dependency issue, explained in this comment.
In the main 0.9.0 release, the same problem is occuring, except it's with knex instead of bookshelf. A maintenance release will be issued sometime soon to fix the issue.

For the record this just happened to me while going from 0.8.0 to 0.9.0, and I found this by specifically searching for the lodash and ghost.
Seems like a step too many when including a note to try deleting the node_modules directory would resolve the situation for many.

@mattlacey sorry to hear you had this problem. Where did you expect to see the note? It is included in the troubleshooting section of the upgrade guide.

You know what, I spotted that right after! I think I missed it because I'd
scrolled down to just the command list after the first upgrade round (I was
going 0.7 -> 0.8 -> 0.9 -> 0.10.1) and then forgot about that.
I guess including it twice would be silly, maybe after the last step have
something like "If you encounter an issue refer to the troubleshooting
section above"?
On 15 September 2016 at 02:12, Hannah Wolfe<EMAIL_ADDRESS>wrote:

@mattlacey https://github.com/mattlacey sorry to hear you had this
problem. Where did you expect to see the note? It is included in the troubleshooting
section of the upgrade guide
http://support.ghost.org/how-to-upgrade/#troubleshooting.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/TryGhost/Ghost/issues/7158#issuecomment-247066500,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABMrWxZTXur_Bsinno6JCV_L2h_wK-o8ks5qqBzkgaJpZM4JX4o5
.

This has been done 😉


Add options for users to add their own config files and command

Which issue(s) this PR fixes (If applicable): #117

Checklist

[x] I have followed the Contribution Guidelines and Code of Conduct.
[x] I have commented my code following the Styleguide.
[x] Relevant documentation is changed or added.
[x] This is NOT A BREAKING CHANGE.

What kind of change does this PR introduce?

[ ] Bugfix.
[x] Feature.
[ ] Code style update (formatting).
[x] Refactoring (no functional changes).
[ ] Build or CI related changes.
[x] Documentation content changes.
[ ] Project automation.
[ ] Other...

[ ] Please describe:

Description of Change

Added three new functions:

emc add <name> <path/to/file/from/home> - Let users add their own config files
emc list - Let users see all their config files and their command. Good for seeing formatting issues if something is wrong or just to remember all commands.
emc remove <name> - Let users remove commands, even default ones

Added new txt file to store the commands and their respective config files, in conf.d/emc_options.txt
Refactored some of the code to reduce error prone repetition

What is the current behavior?

Currently there are no options to add or remove commands
What is the new behavior?

Ability to add or remove commands, and see all commands, including user made
Does this PR introduce a breaking change?

No.
I have tested the code a lot myself, and it work as expected. The old functionality works just the same and the new one as well.
Screenshots
Adding option

Adding option already added, even with another file

Listing out options after addition

Removing Option

Removing previously removed option

Listing out options after removal

Other Information

I am no expert so there is of course the possibility of some string manipulation could happen to not be the "proper" fish way or have some vulnerability, but it works when tested. I have only used the fish language.
I do not know if more needs to be added in terms of removing files if someone uninstalls the plugin
In the future it would be nice to automate the completion code to add the new stuff. Same with the help function

I'm a bit busy right now, but will do asap. I have done more on my branch which needs to be merged, so I might just create a new PR


SampleGen: Correctly initialize map objects in Java and Node.js

Java: use boxed types
Node.js: remove the comma when there is just one entry

Java generic types (those inside <>) cannot be primitive types.


TBOX-209: added delta export functionality to df_connect client

↪ Pull Request

✔ PR Todo

[x] Add documentation
[ ] Add examples
[x] Ensure you are following the practices in the contributor guide and coding_standards

Use consistent and descriptive name conventions
Uses google-style docstrings
Uses versioned API/client methods only
Avoid global variables
Avoid giant try/catch
Don't use mutable default variables
Use a main() function in your scripts

[x] Added/updated testing for this change (ensure you are testing any changes/new code!)
[x] Update title to link to TBOX issue (i.e. start pull request title with TBOX-xx)
[ ] Approval from first code-reviewer
[ ] Approval from second code-reviewer (only required if a second reviewer has left comments)
[x] Pass all checks

Closing for now as this PR is not complete and may be picked back up at a later time.


[FEA] Customizable escape characters in LIKE regexes

Tangentially related to https://github.com/apache/spark/commit/54a73ab7bb.
Spark SQL allows escape characters in LIKE regex strings to be customizable:
https://docs.databricks.com/sql/language-manual/sql-ref-syntax-qry-select-like.html
E.g.
SELECT * FROM person WHERE name LIKE '%$_%' ESCAPE '$';

This will need support from CUDF as well, to support in spark-rapids.

I think we already support this.
https://github.com/NVIDIA/spark-rapids/blob/291a20a742ca5510574579145f3ffbfc438f50a9/sql-plugin/src/main/scala/org/apache/spark/sql/rapids/stringFunctions.scala#L506

I think we already support this.
https://github.com/NVIDIA/spark-rapids/blob/291a20a742ca5510574579145f3ffbfc438f50a9/sql-plugin/src/main/scala/org/apache/spark/sql/rapids/stringFunctions.scala#L506

We believe we already support this.

We believe we already support this.


Wrongly reported dependency changes in GitHub app

Hey there, I hope this issue is in the correct place. Happy to report it in a different place, let me know where.
I have recently found more and more comments by the GitHub App that claim a dependency has been removed in a pure dependency upgrade PR.
There are plenty of examples in the xmldom repo
but the most recent on is here:
https://github.com/xmldom/xmldom/pull/521#issuecomment-1658965243
All of these are really bumping a dependency version, not dropping it.
I'm currently assuming this also relates to issues where already approved issues have to be approved again, but I don't have an example I can share of that right now. (And maybe this is a separate issue? But I think it makes sense to first solve this one.)

From my perspective this issues is ruining your reputation as a reliable source of information.
TO avoid that effect, I'm starting to disable the GitHub App in some repositories, to avoid the noise and misinformation.

Today I received a report/comment that claims an updated version of a dependency is new:
https://github.com/xmldom/xmldom/pull/526#issuecomment-1677617572
Maybe it's a different issue or just unfortunate wording, but the dependency was upgrades as you can see from the diff.

Is there any chance that you are looking into this?
This seems to still be the case after your announcement regarding improved reporting.
This is especially annoying since it renders the "new capabilities" and change in number of transient deps feature useless: if an updated version counts as removed and new version, all capabilities and transient deps of the new version always count as new.

I have now seen the same thing happening for a python package upgrade. So maybe this is the wrong repo for the report?

Hi Christian, I'm an engineer at Socket and I'd be happy to look into this. Can you let me know more details about where you're seeing this? Feel free to email me at @.*** if the details are private.On Mar 30, 2024, at 11:08 PM, Christian Bewernitz @.***> wrote:
I have now seen the same thing happening for a python package upgrade. So maybe this is the wrong repo for the report?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>

@reberhardt7 here is the most recent example from the public xmldom repository:
https://github.com/xmldom/xmldom/pull/643
This is a simple example since the updated packages does not have a lot of dependencies.
What other details do you need?


Backspace no longer works when inline editing a column of type list

Follow up issue from here: #2051
Fiddle: http://jsfiddle.net/nuoL1hbe/ based on http://w2ui.com/web/demos/#/grid/21

Closing as fixed, PR pending


After release of silero-mini, colab examples became outdated

After the release of silero-mini, you added a new function to the utils_vad.py, which made the following piece of code invalid. Raising 'Too many values to unpack' Exception
(get_speech_ts,
 _, read_audio,
 _, _, _) = utils

It should be the following instead:
(get_speech_ts,
 _, _,
read_audio,
 _, _, _) = utils

This is true for all examples.

@adamnsandle
plz check

Will fix collab examples asap

@narekvslife
Please check that this solves your problem
https://github.com/snakers4/silero-vad/pull/60

@snakers4
It does, thank you!


EE velocities and accelerations are always zeros in RobotState

O_dP_EE_d, O_dP_EE_c, O_ddP_EE_c in RobotState are always zero, and do not seem to be updated as the robot moves. Tested with the echo_robot_state example.

@justagist: did you resolve this somehow?