Implement filter_by_key in SparkRDDOperations

Context
On issue filter_by_key method was implemented in BeamOperations and LocalOperations.
Goals
Implement filter_by_key in SparkRDDOperations with API:
def filter_by_key(self, col, public_partitions)
col is a collection (multimap) of (partition_key, data) (type of data is not important)
public_partitions is a collection of (partition_key, ),
filter_by_key returns [record for record in collection if record[0] in public_partitions]

If public_partitions is some Python collection then we can assume that memory is enough, Map operations is enough.
If public_partitions is RDD then join is required

Open questions
Is it possible to unify more filter_by_key between BeamOperations/SparkRDDOperations? For example to come up with the join API in PipelineOperations and to implement filter_by_key using this API.

Hi Vadim, I'd like to work on this.

Sure, thank you!

I looked at the implementation of filter_by_key in BeamOperations and Apache Beam API to think if abstracting some logic to some method in PipelineOperations is possible.
Although it looks possible, I'm not sure if it'd be a good solution. There are 2 issues.
The smaller one is that equivalent methods in Beam API and Spark API are called differently. In Beam, it's a new object creation with passing the previous collection to the constructor. In Spark, it's calling a method on the previous RDD. For example, beam.CoGroupByKey(cols, "Filtering data from public partitions") vs rdd1.cogroup(rdd2). This incompatibility could be worked around by producing in BeamOperations.filter_by_key or SparkRDDOperations.filter_by_key auxiliary python constructs to be passed to PipelineOperations.join.
The bigger one is reliability. I'd use the join transformation of Spark because it may perform public partition selection even if the values corresponding to some public partition key don't feet into 1 Spark worker. spark.sql.autoBroadcastJoinThreshold defines how big the left RDD can be to be broadcast to worker nodes. If I use in SparkRDDOperations.filter_by_key's implementation cogroup and flatMap as counterparts of beam.CoGroupByKey() and beam.ParDo() for the sake of conformability with BeamOperations.filter_by_key, such implementation would crash in case of public partitions not fitting into 1 worker.
What do you think?

Thanks for investigation and explanation! I didn't know about difference between cogroup and join in Spark.

The smaller one is that equivalent methods in Beam API and Spark API are called differently.

That's fine, PipelineOperations hides that.

I'd use the join transformation of Spark because it may perform public partition selection even if the values corresponding to some public partition key don't feet into 1 Spark worker.

Thanks, that's a very good point! Let's use join. I believe here scalability is more important that unifying some logic among Beam and Spark and anyway that logic is not that complicated.
So please implement filter_by_key w/o any logic unifying.

Cool, I also think that unifying the logic is less important than scalability.
I've stuck to the filter_by_key's signature which Lovro used while implementing filter_by_key for other processing engines: filter_by_key(self, col, public_partitions, data_extractors, stage_name: str = None). Is this okay?


Open AI Bot

Script Title - Ai bot
A python script which will take user's input and it will use OpenAi to get results accordingly. It can be used for any purpose from generating blog posts to explaining code! -
Instructions

Create a new folder for your script and file/folder name should be appropriate.
Create a README.md (using this template) in your folder for program Instructions
add requirements.txt if needed

Programming Language

[x] Python

Happy Coding

hey mate I have created bots before and I'm sure that I can do this as well but I'm new to open source so please assign this task to me

Hi, is this issue still available?

Yes its

Thanks for letting me know @SpandyBoss. Can you please help me with the initial steps as I am new to Open Source Contributions.

I'm too new to open source @mahir118 and sorry to but I'm not aware about that, I thought I had to do it on my own, if you want me to assign you I can, and if you mean "that what to build in this issue" by "Initial Steps" then I can guide you through.
Thanks

@SpandyBoss Hi can you please assign this issue to me, I'll try to solve this.

Hi @SpandyBoss i have gone through it, if you can assign this to me i can start working on it.

Hi @SpandyBoss i have gone through it, if you can assign this to me i can start working on it.

Hi, @ShlokJswl as I also mentioned in one of the threads, I don't know how to assign issues, I thought I would create this on mu own.. I'm new to open source . If you have knowledge on how I can assign this issue to you kindly guide me through it I'll then look into it.
Thanks 😊

Hi @SpandyBoss i have gone through it, if you can assign this to me i can start working on it.

Hi, @ShlokJswl as I also mentioned in one of the threads, I don't know how to assign issues, I thought I would create this on mu own.. I'm new to open source . If you have knowledge on how I can assign this issue to you kindly guide me through it I'll then look into it.
Thanks 😊

Hi @SpandyBoss i have gone through it, if you can assign this to me i can start working on it.

Hi, @ShlokJswl as I also mentioned in one of the threads, I don't know how to assign issues, I thought I would create this on mu own.. I'm new to open source . If you have knowledge on how I can assign this issue to you kindly guide me through it I'll then look into it.
Thanks 😊

Hi @SpandyBoss maybe you can view this git document once? https://docs.github.com/en/issues/tracking-your-work-with-issues/assigning-issues-and-pull-requests-to-other-github-users#  Thank you.

Hi @SpandyBoss i have gone through it, if you can assign this to me i can start working on it.

Hi, @ShlokJswl as I also mentioned in one of the threads, I don't know how to assign issues, I thought I would create this on mu own.. I'm new to open source . If you have knowledge on how I can assign this issue to you kindly guide me through it I'll then look into it.
Thanks 😊

Hi @SpandyBoss maybe you can view this git document once? https://docs.github.com/en/issues/tracking-your-work-with-issues/assigning-issues-and-pull-requests-to-other-github-users#  Thank you.

I've gone through this ... I think that I don't have the write permission to the repo that's the reason maybe ...
Thanks

Yea sure, go ahead

Hi @SpandyBoss i have gone through it, if you can assign this to me i can start working on it.

Hi, @ShlokJswl as I also mentioned in one of the threads, I don't know how to assign issues, I thought I would create this on mu own.. I'm new to open source . If you have knowledge on how I can assign this issue to you kindly guide me through it I'll then look into it.
Thanks 😊

Hi @SpandyBoss maybe you can view this git document once? https://docs.github.com/en/issues/tracking-your-work-with-issues/assigning-issues-and-pull-requests-to-other-github-users#  Thank you.

I've gone through this ... I think that I don't have the write permission to the repo that's the reason maybe ...
Thanks

OH okay i understand but do i have your approval to work on this issue?

Yea sure, go ahead

Hi, is this still available?

Hi @SpandyBoss. Please assign this to me if it's still available. Thanks!

Hi @sehgalspandan can you please assign me to this issue. I am also new to open source but would love to contribute and try this out
Thanks and regards

@pawangeek is this still available?

@prathameshdol196 Hi, please help me as I'm new to open source contribution.

If this is still open please assign this task to me, I have done it, so that I can raise a PR for this issue.


Bootstrap views

You really have to add the Twitter Bootstrap and/or Foundation templates.

@Yachtsman @JasonBarnabe  OK, guys, very boring to edit the views, but for the rest of world, there is a new PR  mcasimir/devise-i18n-views#72  added by me. After merged it, we could use this cmd: rails g devise:views:i18n_templates:slim_simple_form_foundation to generate devise view templates written compat slim simple_form and foundation.

@Yachtsman @JasonBarnabe I've added a PR for bootstrap
@mcasimir please consider thus 2 PRs to merge on master or at least leave comment on what is not good and what we need to change for these PRs can be mergeable for you.

This project is being merged into devise-i18n. Please make all further contributions there.


[Feature Request] Add a function to transpose PyTree[Tuple] from the return values of a multiple output function, transpose_output_tree_to_outer_tree

Required prerequisites

[X] I have searched the Issue Tracker that this hasn't already been reported. (comment there if it has.)

Motivation

Thanks for all the brilliant work of contributors of this repo!
When we have a multiple output function
def foo(x):
    return x, 2*x

And we apply a tree_map:
tree_map(foo, [(1,2), 3,4])

the output will be a PyTree of type Tuple[int,int]. However, if we want to get 2 separate trees of the same structure with PyTree[int], we can only do a separate tree_transpose
    x, x_double = tree_transpose(
        tree_structure([(1,2), 3,4]),
        tree_structure(("*","*")),
        tree_map(foo, [(1,2), 3,4])
    )

however, when the returned value have further nested structure, this could be tedious as we need to do another is_leaf to determine the leaf node.
In the situation of separate return value of multiple output function, we know the existing PyTree structure, so it is possible to directly separate the PyTree.
There is a function called equinox.partition which could potentially serve this purpose, but it only support splitting pytree into 2 parts, and we still need to write a filter function to determine how to split.
Solution
In the best situation,
def foo(x):
    return x, 2*x
t = [(1,2), 3,4]
x, x_double = tree_map(foo, t, transpose_output_tree_to_outer_tree = True)

and for mapping object
def foo(x):
    return {"x":x, "x_double":2*x}
t = [(1,2), 3,4]
x_dict= tree_map(foo, t, transpose_output_tree_to_outer_tree = True)
# x_dict will be {"x":[(1,2), 3,4], "x_double":[(2,4), 6,8]}

Alternatives
No response
Additional context
If you have any idea or suggestion please feel free to comment, I can work on implement this feature if I have a guide on how to do it.

After looking at tree_map function, I came up with an idea of separate output into different PyTree. Currently only support tuple output of a function.
def tree_transpose_map(
    func: Callable[..., U],
    tree: PyTree[T],
    *rests: PyTree[S],
    is_leaf: Callable[[T], bool] | None = None,
    none_is_leaf: bool = False,
    namespace: str = "",
) -> Tuple[PyTree, ...]:
    leaves, treespec = _C.flatten(tree, is_leaf, none_is_leaf, namespace)
    flat_args = [leaves] + [treespec.flatten_up_to(r) for r in rests]
    output_tuple = zip(*map(func, *flat_args))
    return tuple(treespec.unflatten(o) for o in output_tuple)

Hi @gRox167, thanks for raising this. I think tre_transpose_map (or called something else) would be a great feature.

Currently only support tuple output of a function.

To support functions that return an arbitrary nested structure, we should specify the inner pytree structure.
def tree_transpose_map(
    func: Callable[..., U],
    tree: PyTree[T],
    *rests: PyTree[S],
    inner_treespec: PyTreeSpec | None = None,
    is_leaf: Callable[[T], bool] | None = None,
    none_is_leaf: bool = False,
    namespace: str = '',
) -> PyTree[U]:
    leaves, treespec = tree_flatten(
        tree,
        is_leaf=is_leaf,
        none_is_leaf=none_is_leaf,
        namespace=namespace,
    )
    flat_args = [leaves] + [treespec.flatten_up_to(r) for r in rests]

    outputs = list(map(func, *flat_args))
    if len(outputs) > 0 and inner_treespec is None:
        inner_treespec = tree_structure(
            outputs[0],
            is_leaf=is_leaf,
            none_is_leaf=none_is_leaf,
            namespace=namespace,
        )
    grouped = [inner_treespec.flatten_up_to(o) for o in outputs]
    transposed = zip(*grouped)
    subtrees = map(treespec.unflatten, transposed)
    return inner_treespec.unflatten(subtrees)

In [1]: def foo(x):
   ...:     return x, 2 * x
   ...:

In [2]: tree_transpose_map(foo, [(1, 2), 3, 4])
Out[2]: ([(1, 2), 3, 4], [(2, 4), 6, 8])

In [3]: def bar(x):
   ...:     return {'x': x, 'x_double': 2 * x}
   ...:

In [4]: tree_transpose_map(bar, [(1, 2), 3, 4])
Out[4]: {'x': [(1, 2), 3, 4], 'x_double': [(2, 4), 6, 8]}

Thanks for all your brilliant contribution! tree_transpose_map works perfectly fine for my use case. Please let me know if you need any further help such as documentation or examples.


Format document creates invalid code and removes comment

during formatting (STRG-K,D) a file with the following python code at the end:
class MyExitCode(IntEnum):
    ERROR = -1,
    OK = 0,

#--- end class MyExitCode

results in:
class MyExitCode(IntEnum):
    ERROR = -1,
    OK = 0,,

#--- end class MyExitCode

The format document functions adds a second comma to the end of the last enum member.
If there is no comma after the last enum member, everything works fine.
And if there is no blank line between the last enum member with two commas after it and the comment line then STRG-K,D will remove the comment.
class MyExitCode(IntEnum):
    ERROR = -1,
    OK = 0,,

#--- end class MyExitCode

results in:
class MyExitCode(IntEnum):
    ERROR = -1,
    OK = 0,,

Filed at https://developercommunity.visualstudio.com/content/problem/269095/python-format-document-add-unwanted-comma-and-remo.html
Confirmed on latest from master.

Should be covered by https://github.com/Microsoft/PTVS/issues/4698


Scala and GWT throws a compiling error

Issue details
When using Scala on libgdx (with gdx-setup) with Gradle, building :html throws an error.
Reproduction steps/code
Create a project on gdx-setup (Desktop and HTML)
Import the project (on IntelliJ ?)
Add Scala using this link : https://github.com/libgdx/libgdx/wiki/Using-libgdx-with-Scala (with Gradle)
Refresh gradle
Convert the main game class on core to Scala
Do :html:build
See the error
Version of LibGDX and/or relevant dependencies
LibGDX 1.9.4
Scala 2.11.7
Stacktrace
:html:addSource
:html:compileGwt
Compiling module fr.litarvan.gdxtest.GdxDefinition
   Validating units:
      [ERROR] Errors in 'file:/home/litarvan/Documents/Temp/GDXTest/html/src/fr/litarvan/gdxtest/client/HtmlLauncher.java'
         [ERROR] Line 17: No source code is available for type fr.litarvan.gdxtest.GdxTest; did you forget to inherit a required module?
   Finding entry point classes
      [ERROR] Errors in 'file:/home/litarvan/Documents/Temp/GDXTest/html/src/fr/litarvan/gdxtest/client/HtmlLauncher.java'
         [ERROR] Line 17: No source code is available for type fr.litarvan.gdxtest.GdxTest; did you forget to inherit a required module?
      [ERROR] Unable to find type 'fr.litarvan.gdxtest.client.HtmlLauncher'
         [ERROR] Hint: Previous compiler errors may have made this type unavailable
         [ERROR] Hint: Check the inheritance chain from your module; it may not be inheriting a required module or a module may not be adding its source path entries properly
:html:compileGwt FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':html:compileGwt'.
> Process 'command '/usr/lib/jvm/jdk-8-oracle-x64/bin/java'' finished with non-zero exit value 1

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

BUILD FAILED

Please select the affected platforms

[ ] Android
[ ] iOS (robovm)
[ ] iOS (MOE)
[x] HTML/GWT
[ ] Windows
[ ] Linux
[ ] MacOS

GWT uses source translation and only works with Java sources. You won't be able to target html if you use Scala.


Failed to ping DB, after cleaning up duplicate indexes

Hi,
I've been using the docker container without problems for a long time, but I recently stumbled into an issue: no images could be uploaded. This was caused by postgres errors like ERROR:  missing chunk number 0 for toast value 53340 in pg_toast_2619, un turn caused by duplicate indexes. I cleaned up the indexes, but after restarting the application fails with "Failed to ping DB".
I can connect to the database without problems (psql mattermost mmuser) and see the database content without problems. I am not sure how to increase the logging and understand what's exactly failing on the application side, but this is not firewalling or other network issues. The setup has not changed since it was last working, just the database content after the index drop and the reindexing of the affected table.
logs
The relevant application log lines are
mattermost_1  | {"timestamp":"2024-04-18 22:46:56.557 Z","level":"info","msg":"Server is initializing...","caller":"platform/service.go:173","go_version":"go1.20.7"}
mattermost_1  | {"timestamp":"2024-04-18 22:46:56.558 Z","level":"info","msg":"Pinging SQL","caller":"sqlstore/store.go:261","database":"master","dataSource":"postgres://%2A%2A%2A%2A:%2A%2A%2A%2A@postgres:5432/mattermost?connect_timeout=10&sslmode=disable"}
mattermost_1  | {"timestamp":"2024-04-18 22:46:56.579 Z","level":"error","msg":"Failed to ping DB","caller":"sqlstore/store.go:269","database":"master","dataSource":"postgres://%2A%2A%2A%2A:%2A%2A%2A%2A@postgres:5432/mattermost?connect_timeout=10&sslmode=disable","retrying in seconds":10,"error":"pq: the database system is shutting down"}

The database logs are:
postgres_1    | 2024-04-18 22:47:05.379 UTC [1] LOG:  starting PostgreSQL 13.14 on x86_64-pc-linux-musl, compiled by gcc (Alpine 13.2.1_git20231014) 13.2.1 20231014, 64-bit
postgres_1    | 2024-04-18 22:47:05.380 UTC [1] LOG:  listening on IPv4 address "<IP_ADDRESS>", port 5432
postgres_1    | 2024-04-18 22:47:05.381 UTC [1] LOG:  listening on IPv6 address "::", port 5432
postgres_1    | 2024-04-18 22:47:05.384 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
postgres_1    | 2024-04-18 22:47:05.395 UTC [23] LOG:  database system was interrupted; last known up at 2024-04-18 21:56:06 UTC
postgres_1    | 2024-04-18 22:47:05.537 UTC [23] LOG:  database system was not properly shut down; automatic recovery in progress
postgres_1    | 2024-04-18 22:47:05.543 UTC [23] LOG:  redo starts at 3/FA9FD500
postgres_1    | 2024-04-18 22:47:05.543 UTC [23] LOG:  invalid record length at 3/FA9FD5F8: wanted 24, got 0
postgres_1    | 2024-04-18 22:47:05.543 UTC [23] LOG:  redo done at 3/FA9FD5B8
postgres_1    | 2024-04-18 22:47:05.577 UTC [1] LOG:  database system is ready to accept connections

Thanks in advance for any help you can provide

well, I "solved" it by recovering what I could recover and created another instance

It's attempting to connect to the database defined by the configs default value
IMO the default value for a database connection should be an empty string, and the go application should exit on seeing an empty string for the sql connection string.
debugging this is not fun otherwise.


Make a stub for OpenAI API to be used in tests

Add a dummy class to mock OpenAI API so the OpenAI API is not used during the tests to make them faster and cheaper.

I do not think the issue has been addressed. Reopening it.

@lightaime FYI I am actively working on this.


Intended project deliverables

[ ] #29
[ ] #30
[ ] #31

closing as they are described in 3 other issues.


add a new tag

The latest tag appears to be v0.3.2 from 2021. Would it be possible to add a new tag to identify the latest stable version? Thank you!

That's maybe a good idea, yes :D
@troldal - do you think the latest version warrants an upgrade to v0.4.0?

maybe this solution will solve your problem click

@troldal when I downloaded version 0.3.2 I got a lot of errors and to fix it I #include  to XLCellReference.hpp, XLColor.hpp, XLDateTime.cpp. After that program compile fine.
I use " cmake -G "MinGW Makefiles" -B build " to compile.

@troldal when I downloaded version 0.3.2 I got a lot of errors and to fix it I #include to XLCellReference.hpp, XLColor.hpp, XLDateTime.cpp. After that program compile fine. I use " cmake -G "MinGW Makefiles" -B build " to compile. So please create new release

@Nazar-de-github : You'll have to be a bit more specific than "a lot of errors" and that you included some files (where?) before we can help you...


Add 1.17 compatibility

[HamsterAPI] Failed to inject player  please contact 2LStudios for support about HamsterAPI as this can lead to vulnerabilities.

server version 1.17

Hello! I am going to test it out...

I can confirm the same issue. I will see what changed in 1.17.

Okay I started to make some commits about this, but seems hard to do as Mojang changed every package.

Hi @linsaftw,
I tried to fix this problem and investigated a bit. I fixed a couple of things and the plugin seems to work fine on 1.17. Here is my code: https://github.com/Luccboy/HamsterAPI. This code may not be good, because I'm not very experienced with Reflections-stuff (that's why I didn't open a PR) but this code may help you fixing this issue.

Hi @linsaftw,
I tried to fix this problem and investigated a bit. I fixed a couple of things and the plugin seems to work fine on 1.17. Here is my code: https://github.com/Luccboy/HamsterAPI. This code may not be good, because I'm not very experienced with Reflections-stuff (that's why I didn't open a PR) but this code may help you fixing this issue.

Hello, thank you for this. We are looking for a way to inject HamsterAPI like ViaVersion does for better security and maintenance.

As a reminder, we need to implement an injector based on ViaVersion one to properly inject HamsterAPI without incompatibilities in the next versions.

I would say currently its not really a good idea to upgrade the library because of the mappings. Spigot switched to the mojang mappings. That has the great advantage that you dont need to use reflection anymore because the classes will be same for 1.17 and ongoing versions.

I would say currently its not really a good idea to upgrade the library because of the mappings. Spigot switched to the mojang mappings. That has the great advantage that you dont need to use reflection anymore because the classes will be same for 1.17 and ongoing versions.

But we still have to somehow be able to inject on new and old versions.

Hi @linsaftw,
this is my second attempt to fix this problem: https://github.com/Luccboy/HamsterAPI/commit/bac370bb6fd06de9bf590f323c66649642757697. I changed a few things and I think this code is better to maintain than the last one. I tested it on Spigot 1.8 and 1.17 and it works fine. I don't know if this is the best solution for this problem, but it may help you. :)

Hi @linsaftw,
this is my second attempt to fix this problem: Luccboy@bac370b. I changed a few things and I think this code is better to maintain than the last one. I tested it on Spigot 1.8 and 1.17.1 and it works fine. I don't know if this is the best solution for this problem, but it may help you. :)

Thank you! This might be a fast solution for now until we get a good decoder like viaversion one. I will review this and implement it if everything is ok.


Avoid first-chance MissingMethodException in Expander

When debugging MSBuild evaluations we see tons and tons of first-chance MissingMethodExceptions:
http://source.dot.net/#Microsoft.Build/Evaluation/Expander.cs,3143
Looking at the code there can be relatively straightforward fixes that would avoid the first-chance exception and also make evaluation faster.

Dup'ing this against https://github.com/Microsoft/msbuild/issues/2217 which has much more context. I'm working on a prototype.

Ha ha, so you saw that I filed this independently! I've been meaning to fix this eventually but life got in the way. Glad you're looking into this.


How to delete current draw tools on canvas

when  I  press keyboard 'delete',I want to delete current draw  with green color,Is there a solution？

We have a new eraser tool that was implemented in PR #433.
You can check it out on the allImageTools example page.

Per @JamesAPetts comment, you can find the eraser tool example demo + src here:
All Image Tools Example Page
All Image Tools Source Code
If you'd rather not enable the eraser tool, you can drag the annotation "off canvas" and it will be removed.


case insensitive matching for hdfs/hive monitoring

Use case insensitive checking for hdfs/hive monitoring, please help to review it
The following are treated as
HDFS:
a) /tmp/PRIVATE
b) /tmp/private
HIVE:
a) select a.phone_number from customer_details a, call_detail_records b where a. phone_number=b.phone_number;
b) select a.PHONE_NUMBER from CUSTOMER_DETAILS a, CALL_DETAIL_RECORDS b where a.PHONE_NUMBER =b.PHONE_NUMBER;

This looks good by cleaning code and adding case-insensitivity match


[Bug report] : Consistent Offline Handling Across All Pages

Current Behaviour:
Currently, we have implemented offline handling using window.addEventListener, which displays an error message stating "it appears that the user is currently offline." However, this implementation is limited to the home page. Users can navigate to the Help page, About page, and others even when they are offline. This inconsistency in handling offline situations results in a bad user experience.
Proposed Approach:
To improve the user experience, we should make the offline handling message consistent across all pages of the app. Regardless of the page the user is on when they lose internet connectivity, they should receive the message notifying them about their offline status.
Additional Information:
Consider the design and styling of the error message to ensure it fits seamlessly with the look and feel of each page.

Hello @Anandsg I can give a try to this. Have some ideas regarding this type of issue. Can you please assign me the task?

@theDevSoham Hey sure, looking forward for the good solution.


feat: add anonymous fields with type name

Enables support for anonymous fields with non-struct types.
Example
type MyString string

type A struct{
    MyString // Will create a field called `my_string` with VARCHAR/TEXT type
}

Is this any better than:
type A struct{
    MyString MyString
}

This way it is less code / tests / docs to write and support.

My situation is that I want to embed type so that its methods are promoted. If I don't embed it, then I need to manually write each of the methods I want to promote. So in a way, the burden of writing more code and tests is now pushed onto the developer.
I will be happy to add tests and docs to this PR if it will help it get approved :)

Looks like encoding/json supports patterns like this so we probably should too.
Please add some tests and maybe comments to the code, because I can't spot any changes in the diff :) I would add a InsertQuery test to query_test.go and more functional test to db_test.go.

Updated with tests and comments.

Looks good, thanks. I will merge this tomorrow.


seccomp gadget: add labels and annotations to SeccompProfiles

seccomp gadget: add labels and annotations to SeccompProfiles
SeccompProfiles can be created via 2 code paths:

upon pod termination
with the "generate" operation

Before this patch, the SeccompProfiles resources were only annotated
with the first code path. This patch prepares annotations for both
scenarios.
Fixes https://github.com/kinvolk/inspektor-gadget/issues/341
cc @ashu8912
How to use
[ describe what reviewers need to do in order to validate this PR ]
Testing done
kubectl apply -f https://github.com/jetstack/cert-manager/releases/download/v1.6.0/cert-manager.yaml
kubectl --namespace cert-manager wait --for condition=ready pod -l app.kubernetes.io/instance=cert-manager
kubectl apply -f https://raw.githubusercontent.com/kubernetes-sigs/security-profiles-operator/master/deploy/operator.yaml
make minikube-install
kubectl apply -f  pkg/resources/samples/trace-seccomp.yaml
kubectl annotate -n gadget trace/seccomp gadget.kinvolk.io/operation=start
kubectl run -ti --rm --image=busybox --restart=Never shell -- echo OK
kubectl run -ti --rm --image=busybox --restart=Never shell2
kubectl edit trace -n gadget seccomp # add: filter.podname=shell2
kubectl annotate -n gadget trace/seccomp gadget.kinvolk.io/operation=generate

Example of SeccompProfile annotations created upon pod termination:
$ kubectl get SeccompProfile -n gadget seccomp-ftm22 -o yaml
apiVersion: security-profiles-operator.x-k8s.io/v1alpha1
kind: SeccompProfile
metadata:
  annotations:
    seccomp.gadget.kinvolk.io/container: shell
    seccomp.gadget.kinvolk.io/node: minikube
    seccomp.gadget.kinvolk.io/pod: default/shell
    seccomp.gadget.kinvolk.io/trace: gadget/seccomp
  labels:
    team: devops

Example of SeccompProfile annotations created with the "generate"
operation:
$ kubectl get SeccompProfile -n gadget myseccomp -o yaml
apiVersion: security-profiles-operator.x-k8s.io/v1alpha1
kind: SeccompProfile
metadata:
  annotations:
    seccomp.gadget.kinvolk.io/container: shell2
    seccomp.gadget.kinvolk.io/node: minikube
    seccomp.gadget.kinvolk.io/pod: default/shell2
    seccomp.gadget.kinvolk.io/trace: gadget/seccomp
  labels:
    team: devops

Could you please describe why you removed the ContainerID and the ContainerPID from the annotations?

Those 2 fields were not directly available for the "generate" operation. It would be possible to get them by calling ContainerResolver.GetContainersBySelector() but would require more code, and they are not needed for the Headlamp plugin. So I chose to get a quick fix for #341 first, and those 2 fields could be added later if ever necessary.

@blanquicet Thank you!


Limit github permissions for Leethub

Current behavior:
Leethub requires authorization to read all public and private repositories.
Suggested change:
I want to be able to limit the access of github to public repositories. A more impressive addition to this would be to be able to select which private repositories leethub would have access to.

Hi @krishpy99,
thanks for opening the issue. I agree we should limit the permissions.
However, I am closing this because it is duplicate of #33.


Fixed minor typo in Welcome component

"projects" --> "project"

Thanks!

Cheers! Thanks for the great template


#2033 Made private fields in Violations.CVSKey final

Thanks for the contribution @alimustafashah and welcome to the Apache Accumulo community. If you would like to be listed as a contributor on Accumulo's people page please make a website PR for people.md. https://github.com/apache/accumulo-website/edit/main/pages/people.md
If you intend to make more contributions, please consider subscribing to the dev list and introducing yourself. Also, you can use the dev list or slack to reach out if you have questions about anything. https://accumulo.apache.org/contact-us/

I am trying to subscribe to the dev list but the button is unresponsive. Secondly should I add my name in people.md and make a pull request?

You can just send an email to<EMAIL_ADDRESS>and that should automatically subscribe you. And yes just add your name (or user name) under Contributors and then if you prefer, add an organization and time zone. Then make a pull request to the website repository.


Test for issue 952

@hideki
I think this test will show the problem of not being able to recall existing views (#952 ). I'm unable to test here (cannot compile forestdb because I'm using ubuntu x64)

@ajres
Any news from this one?
I couldn't compile to test, don't you have travis running for this repo?

@vbenso I haven't tried to run the unit test but I put a couple comments. Can you check? Thanks.

@vbenso Can you update the PR? Thanks.

Done

Thanks. I will look into the issue soon.

I just manually copied the unit test and run it. The test was passed on the current couchbase-lite-android master branch. @vbenso is the test failed on yours?

@pasin
Could't compile there is an open bug about compiling forestdb in x64, the error message I've got is #952.
Anyways, in my app assertEquals(expectedVersion,view2.getMapVersion()) will fail. getMapVersion() returns null.

If you disable x86 in https://github.com/couchbaselabs/couchbase-lite-java-forestdb/blob/master/jni/Application.mk, will it help you to test? Of course, you will not be able to run the test on x86 simulators / devices.
#APP_ABI := armeabi mips armeabi-v7a arm64-v8a x86_64 mips64

Thanks @pasin,
after adjusting Application.mk I've managed to compile forestdb.
The test fails here,  on SQLite getExistingView() returns a view, in ForestDB it returns null

        //https://github.com/couchbase/couchbase-lite-android/issues/952
    public void testViewCreationAndRecall() {
        try {
            String expectedVersion = "1.0";
            String viewName = "test/view";
            Database db1 = startDatabase();
            putDocs(db1);
            View view1 = db1.getView(viewName);
            view1.setMap(new Mapper() {
                @Override
                public void map(Map<String, Object> document, Emitter emitter) {
                    if (document.get("key") != null) {
                        emitter.emit(document.get("key"), null);
                    }
                }
            }, expectedVersion);
            view1.updateIndex();
            db1.close();

            Database db2 = manager.getExistingDatabase(DEFAULT_TEST_DB);
            View view2 = db2.getExistingView(viewName);
            Assert.assertNotNull(view2);
            //in the previous Assert it fails already, so I'll comment these 2 down here.
            //assertEquals(expectedVersion,view2.getMapVersion());
            //assertEquals(Status.NOT_MODIFIED,view2.updateIndex());
            db2.close();
        } catch (CouchbaseLiteException e) {
            e.printStackTrace();
        }
    }

Yes, I could reproduce the issue.

@vbenso,
Thank you for submitting test case!
Have you ever signed contributor license agreement?

Glad to help @hideki,
I'll sign the agreement later.
Em Qui, 18 de ago de 2016 21:55, Hideki Itakura<EMAIL_ADDRESS>escreveu:

@vbenso https://github.com/vbenso,
Thank you for submitting test case!
Have you ever signed contributor license agreement
https://github.com/couchbase/couchbase-lite-ios/wiki/Sign-the-contributor-license-agreement
?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/couchbase/couchbase-lite-android/pull/958#issuecomment-240899905,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AH6Uy8rVNVAl-p7xht6cCGboyXyOUnOSks5qhP8OgaJpZM4JgG5R
.


Thanks a ton!

Just wanted to say thanks for the corrections - I had these blog posts transcribed from the videos so there were some small syntax errors.
If you have any others - I've got everything online at https://github.com/wesbos/es6-articles

You are welcome!


fix(Elixir): improve regex for numbers

Elixir has a lot of different syntax for representing number literals:

...some of which aren't properly detected by the existing regex for numbers in the Elixir language definition:

I tweaked the regex and added some tests to check that they are being detected properly:

Merged. @cdbax thanks for fixing it!


Add common label to operator Pod

Resolves https://github.ibm.com/IBMPrivateCloud/roadmap/issues/59790

@Tirumalavasa pls review

it is against 4.3 release - seems I need to open it against release-cd branch. closing and will open another one

actually, which branch I shall use for 4.3 for mongo operator?

actually, which branch I shall use for 4.3 for mongo operator?

@pgodowski , it is master for 4.3 release(CD release)


typst-fmt: unstable-2023-04-16 -> unstable-2023-04-26

Description of changes
Added new Cargo.lock from repo.
Things done

Built on platform(s)

[x] x86_64-linux
[x] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[x] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

postPatch can now be deleted because of astrale-sharp/typst-fmt@145aff0

Many thanks!

Result of nixpkgs-review pr 228424 run on aarch64-darwin 1

1 package built:

typst-fmt


empty run_prefix blocks processing

if the run_prefix is present but it's not used (it has NA or the same value) the system doesn't work and fails.

This was not the case and the problem was something to do with the file setup in the study. Thus, closing.


Implement HTTP timeout and retries policy

Implementation of a timeout in our HTTP requests and a retries policy.

🆙 - the package has been tested and looks ready !

🌷 If i'm not wrong, this fork is unecessary. You just need to replace the http default client with a new one with a timeout and you're done.
http.DefaultClient = &http.Client{
	Timeout: 10 * time.Second,
}

Answered more explicitly in the universe's PR but yes, we explored this solution but want two things :

avoid as much as possible having to work on the library itself (excepted here to include context, something generic)
having easily configurable timeout and be able to cumulate timeouts

🆙 with context

@Nyks06 can you squash your commits?


Add an event for unhandled exceptions from delegates invoked by native code

These unhandled exceptions would otherwise immediately terminate the program once they reach the native code boundary. This event lets applications do any logging / message dialogs etc and decide whether they want to terminate the program or attempt to continue.
Currently this only supports signal handlers for testing purposes, but would need to be extended to the other callback types.
Bug: #845

[x] I agree that my contribution may be licensed either under MIT or any version of LGPL license.

I wonder if it should be an event at all? Is it useful to have more than one subscriber?
If not perhaps a simple callback should be used instead of an event?
Something similar to: GLib.UnhandledException.SetHandler(..) and GLib.UnhandledException.Raise(..)

Thanks! Updated with those changes.
That's a good question about it being an event .. this was mostly following GtkSharp's GLib.ExceptionManager, which I think in turn was probably following AppDomain.UnhandledException, so I guess there is some precedent there.
I suppose it might give a bit more flexibility for e.g. having one handler do logging, and a handler in another component adding some UI notification
In Pinta we only ever had one handler though, which pops open a message dialog and prints some info to the console

I wonder if the generic handler approach enables this scenario:

catch exception on the native side
wrap exception in custom exception and add the closure instance.
signal the unhandled exception
receive the event in the signal handler with the wrapped exception on the managed side
throw original exception

Replaced by #861


dircolors: update internal db

This PR updates the internal db of dircolors so that -b, -c, and -p return the same outputs as GNU dircolors.

Looks good.
Could you please document the update process in src/uu/ls/README.md?
thanks

Hm, why in src/uu/ls/README.md? Shouldn't it be in src/uu/dircolors?

oh yeah, sorry :)

thanks :)


jsonArrayFrom integer foreign keys are not converted to strings but the type says string

I have two Postgres tables like this:
Table A: id (auto increment)
Table B: id (auto increment), tableAFK (references Table A)
Then, I perform a select from with jsonArrayFrom:
jsonArrayFrom(
            eb.selectFrom("Table B")
              .select(["Table B.tableAFK"])
          ).as("blah")

The actual returned type is {tableAFK: number} like {tableAFK: 1} instead of {tableAFK: string} like {tableAFK: "1"}. But the typescript inferred type is correct: {tableAFK: string}, the return value is a number though.

Hey 👋
Can you provide a kyse.link?

Hey @igalklebanov I tried recreating something minimal: https://kyse.link/HiM0D
To explain, the select from table a is returning an id of type string. The select also returns a JSON array of what I expect to also be of type string[] since the column I am selecting from is type id, and generated columns return string. Instead it actually returns number[]


refactor: add dark version of the elements logo

Closes #947

The viewbox in the svg file for the non-dark version is not set as cleanly as with the new dark version. Maybe we could fix that as well to make sure the sizing is the same across both versions. Should be easily fixable with a cleaner export from the original design file.


setup: Pin CycloneDX behind the 1.0.0 release

The v1.0.0 release included a breaking schema change.
pip_audit/_format/cyclonedx.py:36: error: List comprehension has incompatible type List[str]; expected List[VulnerabilityAdvisory]
Found 1 error in 1 file (checked 50 source files)
make: *** [lint] Error 1

The new advisory type requires a URL (which we don't have) so it wasn't immediately obvious what to do about this. So I'm proposing to pin our version behind 1.0.0 while we figure this out.

Pushed out 1.1.2 with this fix.


renovate: do not bump major version for k8s.io/* deps

We shouldn't update major versions for k8s.io/* dependencies.
From k8s.io/client-go README:

We recommend using the v0.x.y tags for Kubernetes releases >=v1.17.0.

I am using k8s.io/ prefix instead of k8s.io/client-go explicitly because it is probably best that all k8s.io deps have same major versions, i.e. v0.x.y.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 7.572%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
34

Relevant Lines:
449

💛  - Coveralls

I would not want to block updates entirely if at all possible. Can we exclude the 1.x versions via constraint instead?

@majewsky this will not block updates. k8s.io deps are updated at minor version (reference).
So when a new tag is released, i.e v0.x.y, Renovate will update it.

On second thought, constraint sounds better.
What do you think about setting a constraint  on the same minor version as our k8s clusters?
E.g. we will be soon running v1.22 of k8s so we'll set a constraint of 0.22 for the k8s.io/* deps.


Branch clean up

As part of general housekeeping, I went ahead and deleted all branches that were already merged. There are a few remaining after that which may or may not be able to be deleted, could you check @parisk and then close this off? https://github.com/sourcelair/xterm.js/branches

Just left gh-pages as we might use it in the future.
I think it's good to go now.


local-exec provisioner error : cannot import name 'KeyInfo' from 'azure.mgmt.web.models

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az webapp deployment source config-zip
Errors:
The command failed with an unexpected error. Here is the traceback:
cannot import name 'KeyInfo' from 'azure.mgmt.web.models' (/home/mtaallah/.local/lib/python3.10/site-packages/azure/mgmt/web/models/__init__.py)
Traceback (most recent call last):
  File "/home/mtaallah/.local/lib/python3.10/site-packages/knack/cli.py", line 231, in invoke
    cmd_result = self.invocation.execute(args)
  File "/home/mtaallah/.local/lib/python3.10/site-packages/azure/cli/core/commands/__init__.py", line 561, in execute
    self.commands_loader.load_arguments(command)
  File "/home/mtaallah/.local/lib/python3.10/site-packages/azure/cli/core/__init__.py", line 515, in load_arguments
    self.command_table[command].load_arguments()  # this loads the arguments via reflection
  File "/home/mtaallah/.local/lib/python3.10/site-packages/azure/cli/core/commands/__init__.py", line 318, in load_arguments
    super(AzCliCommand, self).load_arguments()
  File "/home/mtaallah/.local/lib/python3.10/site-packages/knack/commands.py", line 104, in load_arguments
    cmd_args = self.arguments_loader()
  File "/home/mtaallah/.local/lib/python3.10/site-packages/azure/cli/core/commands/command_operation.py", line 125, in arguments_loader
    op = self.get_op_handler(self.op_path)
  File "/home/mtaallah/.local/lib/python3.10/site-packages/azure/cli/core/commands/command_operation.py", line 59, in get_op_handler
    handler = import_module(mod_to_import)
  File "/usr/lib/python3.10/importlib/__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1050, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1027, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1006, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 688, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 883, in exec_module
  File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed
  File "/home/mtaallah/.local/lib/python3.10/site-packages/azure/cli/command_modules/appservice/custom.py", line 37, in <module>
    from azure.mgmt.web.models import KeyInfo
ImportError: cannot import name 'KeyInfo' from 'azure.mgmt.web.models' (/home/mtaallah/.local/lib/python3.10/site-packages/azure/mgmt/web/models/__init__.py)

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az webapp deployment source config-zip --resource-group {} --name {} --src {}

Expected Behavior
Environment Summary
Linux-5.15.0-40-generic-x86_64-with-glibc2.35, Ubuntu 22.04.1 LTS
Python 3.10.4
Installer: PIP

azure-cli 2.37.0 *

Additional Context

route to CXP team

@Marwen-TAALLAH Thank you for reaching out, we are looking into it.

@Marwen-TAALLAH Did you get a chance to upgrade to latest version of az cli 2.39.0? if not, can you try and retry the command again please and let us know if it helps

Yes but now the code passes but not as it should, the idea is that i'm creating an azure app function via terraform and trying to upload the code on creation time, the function is created but i can't find the code! here's what it says on the azure portal:
Your app is currently in read only mode because you are running from a package file. To make any changes update the content in your zip file and WEBSITE_RUN_FROM_PACKAGE app setting.

@Marwen-TAALLAH Please go through this documentation https://docs.microsoft.com/en-us/azure/azure-functions/run-functions-from-deployment-package


Add a tool for getting the authors within a range of commits from GitHub

I've been using this to generate the list of contributors for each release.

@swift-ci Please test

@swift-ci Please test

@swift-ci Please test


Can't find unit tests for PivotsHL

Hi,
I think tests for PivotsHL are missing.
What is your reference implementation for testing?
Kind regards
https://github.com/nardew/talipp/blob/master/talipp/indicators/PivotsHL.py
https://github.com/search?q=repo%3Anardew%2Ftalipp PivotsHL&type=code

Same as for https://github.com/nardew/talipp/issues/87.

PivotsHL indicator has been deprecated in favour of ZigZag indicator. ZigZag indicator can be configured to act as PivotsHL, see ZigZag documentation for more details.


[Bug] Template Variables in cells URL - problem with "All"

Describe the bug
When using template variables in a cells URL and the template variable is set to "All", every panel has the variable "all" in it.
e.g.: You can choose between line 1, line 2 or all lines -> When choosing "all", two panels appear, first panel is line 1, second panel is line 2 (that works fine). When using the cells target URL with the variable [[Line]], "All" is not replaced by "1" or "2".
Screenshots
Template Variable

Link for every row

Version Details:

Grafana version : 6.2.5
Plugin version : downloaded master

Hi @florianwgnr  - Fix is now available in master. Feel free to test and let me know how this goes

@yesoreyeram Thank you for your help - the fix works great now!


Try to run unit tests with scalacheck

fpinscala shows an extension of a pbt library to present boolean values as prop (p. 138 1ed).  See if Scalacheck has this implemented, and if so, try to go away from the scalatest for all unit tests in the project (for simplicity).

Yes, we are now routinely doing this in adpro, so moving away from scalacheck is entirely possible

This works and we started migrating to scalacheck.


Use dynamic script switch instead of hot-dev-app.html

Instead of having a separate html file for dev purposes you could do something like this in app.html:
<script>
  const script = document.createElement('script');
  script.src = (process.env.HOT) ? 'http://localhost:3000/dist/app.js' : '../dist/app.js';
  document.write(script.outerHTML);
</script>

Looks good to me. Do you want to send a PR?


Does not work with plugins that try to hijack P, p keys

I ran into conflicts when I was trying to use tmux.nvim since this plugin also tries to hijack P key

Thanks for reporting this issue.
Can you provide a minimal config ?
Thanks

If you want to keep both plugins behavior, you should do something like :
vim.keymap.set("n", "p", function()
  yanky.put(type, false, function(state, callback)
    require("tmux").sync_registers('p')
    callback(state)
  end)
end, { silent = true })


HIVE-23483: Remove DynamicSerDe

Looks like my new commit messed up the labeling (fyi @kgyrtkirk)
The checkout step for http://ci.hive.apache.org/blue/organizations/jenkins/hive-precommit/detail/PR-1207/2/tests/ shows my second commit already (0ec9e25)

@ashutoshc, @pgaref could you please take a look at this? Thank you!

I've seen some additional usage, however I'm not sure how these are utilized, thus I left it in so far:
ql/src/java/org/apache/hadoop/hive/ql/io/HiveBinaryOutputFormat.java:76:          // DynamicSerDe always writes out BytesWritable
serde/src/java/org/apache/hadoop/hive/serde2/thrift/TBinarySortableProtocol.java:150:      // If the struct is null and level > 1, DynamicSerDe will call
serde/src/java/org/apache/hadoop/hive/serde2/thrift/TBinarySortableProtocol.java:418:    // slight hack to communicate to DynamicSerDe that the field ids are not
serde/src/java/org/apache/hadoop/hive/serde2/thrift/TCTLSeparatedProtocol.java:667:    // slight hack to communicate to DynamicSerDe that the field ids are not

Looks like my new commit messed up the labeling (fyi @kgyrtkirk)
The checkout step for http://ci.hive.apache.org/blue/organizations/jenkins/hive-precommit/detail/PR-1207/2/tests/ shows my second commit already (0ec9e25)

not really; what happened was that you submitted a commit while it have started processing - so it skipped the run with the first commit

Looks like my new commit messed up the labeling (fyi @kgyrtkirk)
The checkout step for http://ci.hive.apache.org/blue/organizations/jenkins/hive-precommit/detail/PR-1207/2/tests/ shows my second commit already (0ec9e25)

not really; what happened was that you submitted a commit while it have started processing - so it skipped the run with the first commit

I see, thanks. It was just strange that the pending label is left there, even though the test actually ran and passed.

I've seen some additional usage, however I'm not sure how these are utilized, thus I left it in so far:
ql/src/java/org/apache/hadoop/hive/ql/io/HiveBinaryOutputFormat.java:76:          // DynamicSerDe always writes out BytesWritable
serde/src/java/org/apache/hadoop/hive/serde2/thrift/TBinarySortableProtocol.java:150:      // If the struct is null and level > 1, DynamicSerDe will call
serde/src/java/org/apache/hadoop/hive/serde2/thrift/TBinarySortableProtocol.java:418:    // slight hack to communicate to DynamicSerDe that the field ids are not
serde/src/java/org/apache/hadoop/hive/serde2/thrift/TCTLSeparatedProtocol.java:667:    // slight hack to communicate to DynamicSerDe that the field ids are not

I am under the impression that TCTLSeparatedProtocol is also not only used by DynamicSerDe.
Regarding the DynamicSerDe comments I would either try to track why they are there (or if the functionality is needed at all) -- or completely remove them to avoid confusion. Backup option would be to note DynamicSerDe is now not supported (as you did above)

The record writing I've reverted is used by a number of other SerDes and the comment in it was due to DynamicSerDe being the first which used the related classes. The failing tests passed now locally.

I can't repro these failures locally. These tests look flaky:

Testing / split-19 / Archive / org.apache.hadoop.hive.ql.txn.compactor.TestMmCompactorOnMr.testMmMinorCompactionWithSchemaEvolutionAndBuckets

Testing / split-16 / Archive / org.apache.hadoop.hive.ql.TestWarehouseExternalDir.testExternalDefaultPaths

Testing / split-16 / Archive / org.apache.hadoop.hive.ql.TestWarehouseExternalDir.

Testing / split-14 / Archive / org.apache.hadoop.hive.cli.TestMiniDruidCliDriver.testCliDriver[druidmini_dynamic_partition]

+1 flaky:     Testing / split-14 / Archive / org.apache.hadoop.hive.cli.split20.TestMiniLlapLocalCliDriver.testCliDriver[schema_evol_text_vec_part_all_primitive]

+2 flaky / locally passing:

Testing / split-20 / Archive / org.apache.hadoop.hive.ql.parse.TestReplicationScenariosIncrementalLoadAcidTables.testAcidTableIncrementalReplication
Testing / split-20 / Archive / org.apache.hive.jdbc.TestJdbcWithMiniHS2.testParallelCompilation4

Thank you @pgaref, @kgyrtkirk for the reviews!


⚠ ClamAV has degraded performance

In a66b844, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 581 ms

Resolved: ClamAV performance has improved in b143d78.


Prompted to turn off accessibility service when using banking apps

Recently started getting promoted to turn off the accessibility service in order to log in to the bank.
Possible solution: specify the accessibility service metadata to not have access to anything not needed to turn off the screen? Might be that it has permission to retrieve window content, which the banking app doesn't like?

Confirmed by BankID that the app needs to be installed from Google Play Store in order for the Accessibility Service to be active while using BankID. For security reasons.


Add some notes about configuring Json formatters

Fixes https://github.com/aspnet/AspNetCore.Docs/issues/241

I'm intentionally leaving our IJsonHelper. We don't have a good section to put it in, but more importantly given how infrequently we hear of it, it seems like a fairly low use API.

🆙 📅

Thank you for the PR, @pranavkm!


GeometricProcedure.get_optimzation_keywords is misspelled

Optimization is missing its second i. Link to the code. I'm happy to submit a PR if only the code needs to change. I'm not sure how to update the documentation unless it's generated straight from the source.

Oops, I guess it's called optimzation_spec on the main branch and in the commit I linked to but get_optimzation_keywords on the next branch where I was working.

I'm in support of changing that. If we want to be extremely delicate we can probably have an alias function with the current spelling that throws some sort of warning and routes to the correctly-spelled function, with the intent to remove it sometime. I personally would be find with breaking it as long as everything is consistent within a single version.

I just made the changes on a branch starting from main, but now I'm wondering if we should just wait until the next branch gets merged since the method name changed anyway.  It's definitely a very minor duplication to do it twice, but maybe the version on main doesn't matter right now? I'm happy with whatever, I just noticed it while working on something else.

I don't think there's a plan to make a new release based off of main - I figure this change should be based off of next, or just included in that PR.
This also implies that the mega-PR shouldn't be merged, but the next branch should simply become main when it's ready to go. We did a similar thing the last time the toolkit had major breaking changes, though admittedly that was easier to pull off because it was part of a master -> main switch.

Ahh, okay. I was thinking about the merge, so that makes sense. I'll just push it to next with my other changes. Thanks!


Detect/avoid double-faulting in the host runtime

We've recently encountered a case where host function faults, tries to generate a DebugError with the error status. While in the middle of creating a DebugEvent, it runs out of budget and faults for the second time with an "out of budget" status. The original status was overridden.
This is a potential footgun. We need to avoid such double/multiple-faulting cases, or at the very least, be able to detect it. One potential solution @graydon suggested was to add a static counter to track the number of times the host have faulted, and asserting that number cannot exceed 1.
How to reproduce it:
Revert changes mentioned in this comment, and run the metered_xdr_out_of_budget test under budget_metering.

Done in https://github.com/stellar/rs-soroban-env/pull/806


Bug in prior assignment

When attempting to assign a prior the following is occurring:
comp.K_1.prior = Log_uniform_prior(lower_bound=1E-5,upper_bound=1E-1)

NotCallableOrErrorInCall                  Traceback (most recent call last)
<ipython-input-16-0a86e595c312> in <module>()
----> 1 comp.K_1.prior = Log_uniform_prior(lower_bound=1E-5,upper_bound=1E-1)
      2 comp.K_2.prior = Log_uniform_prior(lower_bound=1E0,upper_bound=1E4)
      3 comp.xp_1 = Log_uniform_prior(lower_bound=1E2,upper_bound=1E4)
      4 comp.xc_2 = Log_uniform_prior(lower_bound=1E2,upper_bound=1E4)
      5 comp.alpha_1=Uniform_prior(lower_bound=-2,upper_bound=1)

/usr/local/lib/python2.7/site-packages/astromodels-0.2.1-py2.7.egg/astromodels/dual_access_class.pyc in __setattr__(self, key, value)
     51                 warnings.warn("Attribute %s does not exist. Check for typos." % key, NonExistingAttribute)
     52
---> 53             super(DualAccessClass, self).__setattr__(key, value)
     54
     55     def _add_attribute(self, name, value):

/usr/local/lib/python2.7/site-packages/astromodels-0.2.1-py2.7.egg/astromodels/parameter.pyc in _set_prior(self, prior)
    589
    590             raise NotCallableOrErrorInCall("Could not call the provided prior. " +
--> 591                                            "Is it a function accepting the current value of the parameter?")
    592
    593         prior.set_units(self.unit, u.dimensionless_unscaled)

NotCallableOrErrorInCall: Could not call the provided prior. Is it a function accepting the current value of the parameter?

I'm looking into the issue, but do not know the guts of astromodels so well.

That's being corrected already, upgrade to the last version 😉
-----Original Message-----
From: "J. Michael Burgess"<EMAIL_ADDRESS>Sent: 6/26/2016 2:13 AM
To: "giacomov/astromodels"<EMAIL_ADDRESS>Subject: [giacomov/astromodels] Bug in prior assignment (#11)
When attempting to assign a prior the following is occurring:
comp.K_1.prior = Log_uniform_prior(lower_bound=1E-5,upper_bound=1E-1)
NotCallableOrErrorInCall                  Traceback (most recent call last)
 in ()
----> 1 comp.K_1.prior = Log_uniform_prior(lower_bound=1E-5,upper_bound=1E-1)
2 comp.K_2.prior = Log_uniform_prior(lower_bound=1E0,upper_bound=1E4)
3 comp.xp_1 = Log_uniform_prior(lower_bound=1E2,upper_bound=1E4)
4 comp.xc_2 = Log_uniform_prior(lower_bound=1E2,upper_bound=1E4)
5 comp.alpha_1=Uniform_prior(lower_bound=-2,upper_bound=1)
/usr/local/lib/python2.7/site-packages/astromodels-0.2.1-py2.7.egg/astromodels/dual_access_class.pyc in setattr(self, key, value)
51                 warnings.warn("Attribute %s does not exist. Check for typos." % key, NonExistingAttribute)
52
---> 53             super(DualAccessClass, self).setattr(key, value)
54
55     def _add_attribute(self, name, value):
/usr/local/lib/python2.7/site-packages/astromodels-0.2.1-py2.7.egg/astromodels/parameter.pyc in _set_prior(self, prior)
589
590             raise NotCallableOrErrorInCall("Could not call the provided prior. " +
--> 591                                            "Is it a function accepting the current value of the parameter?")
592
593         prior.set_units(self.unit, u.dimensionless_unscaled)
NotCallableOrErrorInCall: Could not call the provided prior. Is it a function accepting the current value of the parameter?
I'm looking into the issue, but do not know the guts of astromodels so well.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Aha. Good, it works now!


fixthe decimal type's precision and scale of set operation node is wrong

pick from master https://github.com/apache/doris/pull/32787
Proposed changes
Issue Number: close #xxx

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

run buildall


Logistic regression running with n_jobs=-1

Describe the bug
I am trying to run the logistic regression and seeing in to the logs that it is falling back to stock scikit-learn and then running accelerated version on CPU, is it expected bahaviour that as i am expecting to get only run on accelerated version.
To Reproduce
Steps to reproduce the behavior:

Setup
script used for running
lr.py
=============================================================
from sklearn.linear_model import LogisticRegression
from sklearn.datasets import make_classification
from timeit import default_timer as timer

from sklearnex import patch_sklearn
patch_sklearn()
import logging
logging.getLogger("sklearnex").setLevel(logging.INFO)
Generate Dataset
X, y = make_classification(n_samples=10000000,
n_features=20,
n_classes=2,
random_state=42)
Main
num_runs = 1  # Number of runs
elapsed_times = []
for _ in range(num_runs):
start = timer()
model = LogisticRegression()
model.fit(X, y)
elapsed = timer() - start
elapsed_times.append(elapsed)
Calculate average elapsed time
avg_time = sum(elapsed_times) / num_runs
print(f"Elapsed time list: {elapsed_times}")
print(f"Average time over {num_runs} runs: {avg_time} seconds")

Call : python3 lr.py
Use
'scikit-learn-intelex     2024.0.1
daal4py                  2024.0.1
See error
python3 lr.py
Intel(R) Extension for Scikit-learn* enabled (https://github.com/intel/scikit-learn-intelex)
INFO:sklearnex: sklearn.utils.validation._assert_all_finite: running accelerated version on CPU
INFO:sklearnex: sklearn.utils.validation._assert_all_finite: fallback to original Scikit-learn
INFO:sklearnex: sklearn.linear_model.LogisticRegression.fit: running accelerated version on CPU
Elapsed time list: [0.9992906190000213]
Average time over 1 runs: 0.9992906190000213 seconds
Expected behavior
only running on accelerated version

Output/Screenshots
output as shown above
Environment:

OS: Ubuntu 22.04.2
Hardware : Intel(R) Xeon(R) Platinum 8375C CPU @ 2.90GHz

It's expected behavior: y is of int type which is not checked by scikit-learn-intelex. X is processed as expected.
DEBUG logging level explains it:
INFO:sklearnex: sklearn.utils.validation._assert_all_finite: running accelerated version on CPU
DEBUG:sklearnex: sklearn.utils.validation._assert_all_finite: debugging for the patch is enabled to track the usage of Intel® oneAPI Data Analytics Library (oneDAL)
DEBUG:sklearnex: sklearn.utils.validation._assert_all_finite: patching failed with cause - X dtype is not float32 or float64.
INFO:sklearnex: sklearn.utils.validation._assert_all_finite: fallback to original Scikit-learn

LogisticRegression is trained with patching:
INFO:sklearnex: sklearn.linear_model.LogisticRegression.fit: running accelerated version on CPU

@Alexsandruss can we see similar logs for predict as well?
as in my run if i add predict
model.predict(X)
i see only
INFO:sklearnex: sklearn.utils.validation._assert_all_finite: running accelerated version on CPU
how to confirm if this also running using sklearnex?

@Alexsandruss but the X dtype shows float64 only. still it prints :
DEBUG:sklearnex: sklearn.utils.validation._assert_all_finite: patching failed with cause - X dtype is not float32 or float64.

@Alexsandruss i am getting the issue when n_jobs is -1 , it is not trained with patching.
if we add the below param to above script in issue
model = LogisticRegression( tol = 0,
C = 0.1,
multi_class = "multinomial",
solver = "lbfgs",
n_jobs = -1)
if we keep default or n_jobs=1 then only i see :
INFO:sklearnex: sklearn.linear_model.LogisticRegression.fit: running accelerated version on CPU

@Alexsandruss could you please help to look at the above issue?

This code with n_jobs=-1 works normally for sklearnex 2024.1.0:
from sklearnex.linear_model import LogisticRegression
from sklearn.datasets import make_classification
import logging as lg

lg.getLogger("sklearnex").setLevel("INFO")

x, y = make_classification(
    n_samples=200000,
    n_features=128,
    random_state=42
)
lr = LogisticRegression(
    tol=0,
    C=0.1,
    multi_class="multinomial",
    solver="lbfgs",
    n_jobs=-1
).fit(x, y)
print("Score:", lr.score(x, y))

Output:
INFO:sklearnex: sklearn.linear_model.LogisticRegression.fit: running accelerated version on CPU
INFO:sklearnex: sklearn.linear_model.LogisticRegression.predict: running accelerated version on CPU
Score: 0.924205

thanks @Alexsandruss for checking it, but if we use patching
from sklearnex import patch_sklearn
patch_sklearn()

then this issue is seen.
With direct import of from sklearnex.linear_model import LogisticRegression issue is not seen.

can you keep reopen the issue ? it will helpful.

from sklearn.linear_model import LogisticRegression
from sklearnex import patch_sklearn
patch_sklearn()
# from sklearnex.linear_model import LogisticRegression
from sklearn.datasets import make_classification
import logging as lg

lg.getLogger("sklearnex").setLevel("INFO")

x, y = make_classification(
    n_samples=200000,
    n_features=128,
    random_state=42
)
lr = LogisticRegression(
    tol=0,
    C=0.1,
    multi_class="multinomial",
    solver="lbfgs",
    n_jobs=-1
).fit(x, y)
print("Score:", lr.score(x, y))

This is the exact reproducer with the script you mentioned.
Basically we import sklearn Logistic regression and use patch with n_jobs=-1, not running with patch.
if you import sklearnex it is working fine, so seems like some issue with patch.

LogisticRegression import should be after patching

Thank you @Alexsandruss for all your quick help.


plant search with short terms

When typing e.g. "co" it does not show e.g. the many "corns". Possible fixes are:

telling the user that he/she must continue typing (what is the limit when the search starts to work?)
fixing the search to also work with shorter words
using an ILIKE search for very short words (only for beginning of word)

@kitzbergerg what do you think, what is easily doable?

#406 improved also this behavior a lot, let us close it.


Vague GitHub Apps error on invalid YAML key

Describe the bug
Logged as a Discuss issue: https://discuss.dockstore.org/t/workflow-not-showing-when-using-github-app/5152/4
In the case of an imroper key (i.e. a typo) in the .dockstore.yml file of a GitHub App, the logs reported to the user can be vague. For example, if a user mis-types the word subclass, the returned GitHub Apps log looks like:

This is caused during the validation stage of the YAML file and the error message is reported here: https://github.com/dockstore/dockstore/blob/c562b20d3d1037b72d4695284609f1320af9ef05/dockstore-common/src/main/java/io/dockstore/common/yaml/DockstoreYamlHelper.java#L374.
To Reproduce
Steps to reproduce the behavior:

This commit fixes a malformed .dockstore.yml: https://github.com/Richard-Hansen/cumulus/commit/ce34f740efa153d60e671d3253eb4088b2f20920, take the pre-commit file with key sublicass
Attempt to sync with GitHub Apps
View GitHub Apps logs and see must not be null

Expected behavior
Key validation errors for the .dockstore.yml should be verbose in pointing out the offending key. Ideally a message such as:
Missing dockstore.yml required key 'subclass' for workflow XYZ, or perhaps Unknown dockstore.yml key 'sublicass'. This will make it easier for a user to determine what is wrong with their file.
Note: The error in the above .dockstore.yml file is caused by subclass being a required key that is absent. We should provide errors for both cases of:

A required key is missing
An unknown key is provided

Additional context
Webservice - 1.11.12
UI - 2.8.5
Compose Setup - 1.11.1
Deploy - 1.11.2
┆Issue is synchronized with this Jira Story
┆Attachments: Screenshot 2022-05-03 at 09-47-30 Dockstore My Workflows.png | Screenshot 2022-05-03 at 10-30-57 Dockstore My Workflows.png | Screenshot 2022-05-03 at 10-41-53 Dockstore My Workflows.png
┆fixVersions: Dockstore 1.12.x
┆friendlyId: DOCK-2105
┆sprint: SEAB 83- Luca
┆taskType: Story

Re-iterating that https://github.com/dockstore/dockstore/pull/4843 ( https://github.com/dockstore/dockstore/pull/4843|smart-link ) which was targeted to the hotfix branch has not been verified yet.

I verified that it works in staging, at least for the original bug described by Richard. I do find it slightly disconcerting that message has an array index, even if there is only 1 workflow, Property "workflows[0].subclass" is missing, but the PR did say that, and this is a major improvement over what was there.
This ticket has a lot of discussion; @kathy-t, let me know if you feel it's OK to close this ticket or not.
Webservice - d50cfd6
UI - 2.9.1-78-g344740c0
Compose Setup - f0518f2
Deploy - 1.12.5-82-g1796ce1
galaxyParsingLambdaVersion: 0.0.7


Deprecate no-use-before-declare rule for typescript 2.9+

PR checklist

[x] Addresses an existing issue: fixes #4666
[ ] New feature, bugfix, or enhancement

[ ] Includes tests

[ ] Documentation update

Overview of change:
deprecate no-use-before-declare for TS 2.9+

Thanks for your interest in palantir/tslint, @waseemahmad31! Before we can accept your pull request, you need to sign our contributor license agreement - just visit https://cla.palantir.com/ and follow the instructions. Once you sign, I'll automatically update this pull request.

It seems like discouraging TSLint users from using no-use-before-declare might have been premature. There is a class of errors this rule helps catch and these errors are not detected by TypeScript itself.
Consider this example:
const consumer = () => {
  console.log(variable); // no-use-before-declare: "variable 'variable' used before declaration"
};

consumer();

const variable = 'foo';

This snippet represents perfectly valid TypeScript — no compile-time error will be issued. Yet, an attempt to run it will cause a runtime exception.
See TypeScript playground.
Thanks to @OliverJAsh for providing an example.

@karol-majewski one difficulty of rules like no-use-before-declare is figuring out which nodes are truly used before declaration vs. ones that just seem to be used before declaration.
const consumer = () => {
    setTimeout(() => {
        console.log(variable);
    }, 1);
};

consumer();

const variable = 'foo';

The rule has been somewhat marked as deprecation for a while (#4666); if you'd like to see it un-deprecated or generally re-implemented please file a new issue.

The docs seem to suggest this rule was deprecated because it no longer has any use (since var is no longer used. Is that correct?
In addition to @karol-majewski's point about catching runtime errors: I would still like this rule for a code style preference of mine: enforcing single direction of code definitions—details at top, composition/usages below. E.g.
Without
const y = 1;

const foo = () => {
    x;
    y;
}

const x = 1;

With
const x = 1;
const y = 1;

const foo = () => {
    x;
    y;
}

I'm a new user of typescript, and received this warning. However, I believe it's unclear:

Please use the built-in compiler checks instead.

Does this mean I need to enable a compiler option in order to have the same guarantees as I would have had before this rule was deprecated?
I propose changing the message to either "This rule is no longer necessary and can be safely removed" or pointing the user (in this case me) to documentation for which compiler options are relevant.

@Burgestrand I can't find an equivalent compiler option for this rule but it looks like you don't really need this rule if you don't use the "var" keyword. So, if you have the "no-var-keyword" rule enabled then this rule is not needed at all.

@bolatovumar Great, thank you!

@bolatovumar None of the examples in this thread is using the var keyword. 🤔 Yet using no-use-before-declare would have helped catch errors for them.

@karol-majewski you get compiler warnings if you use a const or let variable before it's declared so you don't need this rule in that case.

@bolatovumar TypeScript doesn't issue any warnings for this piece of code and yet it breaks in runtime:
const consumer = () => {
  console.log(variable);
};

consumer();

const variable = 'foo';

See for yourself in TypeScript playground.

@karol-majewski right, I see. You might wanna file a separate issue as @JoshuaKGoldberg suggested above . I'm not actually sure why this rule is deprecated specifically for TS 2.9+ so I can't really add much more here.

Posting again here: the rule seems to have some buggy behavior, such as the false positive mentioned in #2551. If you'd like the rule to be un-deprecated despite that (maybe the bug doesn't exist? maybe it's worth it to keep the rule?) please file a new issue so we can discuss there. PR responses aren't very search-discoverable.
Also, keep #4534 in mind: TSLint is in the process being deprecated.
Same goes for suggestions to improve the rule's docs or error messaging. I'm all for improving docs, but we should discuss them in a dedicated thread. It's hard to keep track of this one... 😞

please file a new issue so we can discuss there

Come on. I created new issue https://github.com/palantir/tslint/issues/4789, but you closed it with blocked status without any discussion.

Also, keep #4534 in mind: TSLint is in the process being deprecated.

Yes, maybe TSLint team will stop deprecate existing rules? False positive results is not a reason for removing rule. By this logic any buggy rule can be removed.

Posting again here: the rule seems to have some buggy behavior, such as the false positive mentioned in #2551. If you'd like the rule to be un-deprecated despite that (maybe the bug doesn't exist? maybe it's worth it to keep the rule?

So, example from issue #2551 is not isolated and contains some project specific entities.
I tried to test code from replies:
https://github.com/palantir/tslint/issues/2551#issuecomment-300904638
https://github.com/palantir/tslint/issues/2551#issuecomment-424837231
There are no errors with no-use-before-declare rule.

Come on. I created new issue #4789, but you closed it with blocked status without any discussion.

Oh oops, sorry!  That is entirely my fault; will re-open.


Add filtering of interpreter names for tests with multiple Python versions

Extends new filters for interpreter paths to apply to tests with multiple Python versions. Adds patch version filtering for them as well, which is needed for #4360 tests.

This feels kind of sloppy but it's blocking work I want to release today.


Fixed cmake warning that targets shouldn't be named test.

Fixed an issue with new behaviour in cmake 3.0.0 according to this policy:

Target names reserved by one or more CMake generators are not allowed.
Among others these include "all", "help" and "test".
The OLD behavior for this policy is to allow creating targets with
reserved names or which do not match the validity pattern.

The NEW behavior for this policy is to report an error
if an add_* command is used with an invalid target name.
This policy was introduced in CMake version 3.0.  CMake version
3.0.0 warns when the policy is not set and uses OLD behavior.  Use
the cmake_policy command to set it to OLD or NEW explicitly.

Super cool! Thanks!


Setting triggerTarget with a ref doesn't actually set Tippy instance's option

Bug description
I was trying to replicate the "Different Trigger Target" feature from tippy.js in React.
When I set the triggerTarget with the parent div's ref, React re-renders the component and inserts the prop as expected, with the correct reference to the parent node. However, Tippy doesn't update in this case. triggerTarget ends up being set in the underlying Tippy as null, even though the prop triggerTarget with the correct value is passed into it.
Reproduction
CodeSandbox

Notice that I logged the ref being set and that it is working as expected. It is initially null, then when the ref updates, it updates the prop.
However, the underlying Tippy instance's triggerTarget option REMAINS as null.

My findings
It seems like the problem is here:
https://github.com/atomiks/tippy.js-react/blob/846a3764e51d5bc315d433759639a606a7903f95/src/Tippy.js#L87-L96
This code doesn't run on the first or second render for optimization reasons. However, because my ref is updating in the 2nd render, the options never get updated. Commenting out the return fixes this problem, which proves my hypothesis.

I wonder if we can keep the optimization here, but probably not? Does changing < 3 to < 2 work?

Does changing < 3 to < 2 work?

I believe so. It is rendering only twice here.
CC @nguyen-darianhuy

I wonder if we can keep the optimization here, but probably not? Does changing < 3 to < 2 work?
I believe so. It is rendering only twice here.

Yes; when the ref updates, the component renders for the second time. Changing to < 2 allows the instance to update its options on the second render.

Just to explain things for clarity:

1st render: the instance only just got created so no need to update anything yet
2nd render: this is due to the creation effect (setMounted()) so that the component can re-render and use the portal content - it was assumed no options changed in this timeframe (except in this case you've listed which I didn't consider where you can cause a re-render before setMounted() does it itself).
3rd+ render: update any options dynamically while the instance is still alive. But, due to the above case you've listed, we can't assume setMounted() will be the "last" render before we can update things.

So we'll just need to change 3 to 2. Do you want to make a PR for this and a test case?

Just to explain things for clarity:

1st render: the instance only just got created so no need to update anything yet
2nd render: this is due to the creation effect (setMounted()) so that the component can re-render and use the portal content - it was assumed no options changed in this timeframe (except in this case you've listed which I didn't consider where you can cause a re-render before setMounted() does it itself).
3rd+ render: update any options dynamically while the instance is still alive. But, due to the above case you've listed, we can't assume setMounted() will be the "last" render before we can update things.

Oh, I didn't realize a 2nd render was forced due to setMounted() in the effect. Is it possible that React is optimizing itself by combining the setMounted() and the triggerTarget prop update in one render, and that's why there are only two renders occurring here?

So we'll just need to change 3 to 2. Do you want to make a PR for this and a test case?
Sure!


Folding "Filters" section in top-left block is impossible

In this block on the top left of the map view, I can't fold the Filters section, as it overlaps with a "back" button (whose functionality is not completely clear to me).

At one point I had accidentally folded the Filters and couldn't unfold it because of this issue.
Easy work around until the bug gets fixed in a future version:
The data.json file in the Map View plugin folder contains the applicable setting
Changing the filtersDisplayed value to true or false folds and unfolds the UI
"mapControls": {
"filtersDisplayed": true,
"viewDisplayed": false,
"presetsDisplayed": true,
"linksDisplayed": false

@pelegm can you provide more details so I can try to recreate this?

What version of Obsidian?
What platform (Linux/Mac/Windows/iOS/Android)?
Are you using a custom theme and/or custom CSS snippets?


If caching plugins like W3TC or WP Super Cache is Active AMP won't work

If W3TC or other caching plugin is active, it cache the main site, and call does not even reach this plugin.
Issue is even bigger when you do mobile redirection(which is not by default on, but coming in future update, and exist on commit before 0.6.0.
I am using this guide to resolve from caching plugin end.

I don't use either of those plugins, but I might be right in thinking the following:
If you put something along the lines of " */?amp " in what might be named something like "never cache these pages", then it should stop the caching plugin from caching amp pages.
You should also disable cache on mobile, you should do that anyway as it never works well.
Personally, I use WP Rocket, which is a pretty awesome pro cache plugin that has its own mobile detection. You can find it here: https://wp-rocket.me/

This issue was fixed after 0.8 update


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target/pull/964 is merged into live branch.
Auto archive content to https://github.com/opstest2/docs-archive-test-target.git

Docs Build status updates of commit 28a2822:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-GitBranchDeletedOrForcePushed] Cannot sync git repo to specified commit because branch Release_Archive_master_2021-07-19-03-38-50 has been deleted or has been force pushed

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Node.js version confusion for single tenant logic apps

[Enter feedback here]
There are two different mentions about the compatiable node.js version for single tenant logic apps on this page.
They are as below.
Uses Node.js version 8.11.1 for multi-tenant based logic apps or Node.js versions 12.x.x or 14.x.x for single-tenant based logic apps.
Single-tenant: Requires Node.js versions 10.x.x, 11.x.x, or 12.x.x. However, you don't need an integration account, but the Inline Code action is renamed Inline Code Operations and has updated limits.
Version 14.. seems to be working for single tenant apps. Please confirm.

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

ID: d660520b-e327-c1e5-e771-692cc9d254e4
Version Independent ID: d6a8c604-c51a-4d45-e2d9-678665fea0d1
Content: Add and run code snippets by using inline code - Azure Logic Apps
Content Source: articles/logic-apps/logic-apps-add-run-inline-code.md
Service: logic-apps
GitHub Login: @ecfan
Microsoft Alias: estfan

@sanket-borhade Thank you for your feedback! We will review and update as appropriate.

@sanket-borhade: Thanks for your feedback! We'll get this doc updated.

@sanket-borhade: The doc update should go live today.


Add 'forced on' flow control mode to mavlink UART

Added "always on" flow control mode (activated via '-z' flag). This is needed if flow control is used with companion computer which boot speed is slower than FMU boot. So flow control will not disabled by timeout if peer is not ready.

This looks good to me, let's just make sure it's working in all cases.

I've tested it on pixhawk connected to NanoPI NEO2 @1.5M bps

@dagar Can you merge it?

Could someone do a quick test with a 3dr radio (or equivalent) with and without flow control connected?
Please make sure there are no regressions for the common setups.

SiK radio with flow control still on by default and working
SiK radio without flow control connected, properly detected by mavlink and still working

@LorenzMeier @dagar Any chances to be merged?

Could someone do a quick test with a 3dr radio (or equivalent) with and without flow control connected?
Please make sure there are no regressions for the common setups.
SiK radio with flow control still on by default and working
SiK radio without flow control connected, properly detected by mavlink and still working

Tested. Works!
Merging!


1.14.0-dev.1.0: spawnUri is not yet supported on background isolates

Failure log from Angular 2 build: https://travis-ci.org/angular/angular/jobs/92763702
The only place we use spawnUri: https://github.com/angular/angular/blob/646b9200a2ea6373318fd88a83d721d46a571115/modules/angular2/src/web_workers/ui/application.dart#L30

@turnidge is looking at creating some Dartium special handling.


Drop obsolete function insert_subscription

Description
In #96 a new function events.insert_subscription accepting the hashed sourcefilter was introduced. The obsolete function that does not accept the hashed source filter as input should be dropped once #96 is deployed and running in all environments.
Additional Information
No response
Tasks

[x] Create migration script for dropping function
[x] QA
[x] Regression test of subscription functionality

Acceptance Criterias

[x] Only one function events.insert_subscription exists in the database

verified ok in at22


svg logo

svg version of micro logo

Is this the svg logo that you downloaded from the micro-editor.github.io website?

I converted the it from png, just haven't realized that it already was in svg.


Merge pull request #1 from lab2group6/develop

Added avatar to pix and created quote to Quotes.php

Change log update!


Support optimized try-catch in DBC

DBC currently bails out to the unoptimized bytecode on try-catch.

Fixed via https://github.com/dart-lang/sdk/commit/6d66f3dea89027c083af791becbce3dbc6e5d257


Fix text styles by removing uses of the non-custom text component

Details
Enforces the use of our custom text component throughout the app instead of the default RN text component. This ensures that our default styles are used. Also removes styles.textP, which is redundant when the default custom text component is used.
Fixed Issues
$ https://github.com/Expensify/Expensify.cash/issues/3387
Tests / QA Steps
Click through the various screens and components of the app - verify that everywhere you see the correct use of our fonts. Pro-tip: take a look at the g's – they look noticeably different in GT America with this distinctive tail:

Pay particular attention to IOU actions and previews, because we know these were previously using the incorrect font.
Tested On

[x] Web
[x] Mobile Web
[x] Desktop
[x] iOS
[x] Android

Screenshots
Web

Mobile Web

Desktop

iOS

Android

Because 59 files were changed here, this will be a nightmare to keep up-to-date. Quick reviews appreciated 🙇

Fixed merge conflicts, going to need another review @MonilBhavsar.

Looks like we have a conflict.

Conflicts resolved!

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to production         in version: 1.0.77-5🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Bounded Layout is broken after upgrade to v1.4.4

Describe the bug
cannot drag item,  and the dragged item will automatically move to the first position
Your Example Website or App
https://codesandbox.io/s/cocky-andras-hshv2c?file=/src/ShowcaseLayout.js
Steps to Reproduce the Bug or Issue
drag any item.
Expected behavior
can drag item to ajust position
react-grid-layout library version
1.4.4
Operating System Version
windows
Browser
Chrome
Additional context
No response
Screenshots or Videos

Yep, we are facing the same issue as well

Downgrading to ~1.3.0 fixes this issue. Here's another codepen showing the problem: https://codesandbox.io/s/5nevr?file=/src/App.js
The latest release you can't resize or drag any of the items :(

I'm having the same issue:
https://codesandbox.io/p/devbox/rgl-test-2-vanilla-react-pgmk4n?file=%2Fsrc%2FApp.js&layout=%257B%2522sidebarPanel%2522%253A%2522EXPLORER%2522%252C%2522rootPanelGroup%2522%253A%257B%2522direction%2522%253A%2522horizontal%2522%252C%2522contentType%2522%253A%2522UNKNOWN%2522%252C%2522type%2522%253A%2522PANEL_GROUP%2522%252C%2522id%2522%253A%2522ROOT_LAYOUT%2522%252C%2522panels%2522%253A%255B%257B%2522type%2522%253A%2522PANEL_GROUP%2522%252C%2522contentType%2522%253A%2522UNKNOWN%2522%252C%2522direction%2522%253A%2522vertical%2522%252C%2522id%2522%253A%2522clpva9hn600083b6n0pt0h1jt%2522%252C%2522sizes%2522%253A%255B70%252C30%255D%252C%2522panels%2522%253A%255B%257B%2522type%2522%253A%2522PANEL_GROUP%2522%252C%2522contentType%2522%253A%2522EDITOR%2522%252C%2522direction%2522%253A%2522horizontal%2522%252C%2522id%2522%253A%2522EDITOR%2522%252C%2522panels%2522%253A%255B%257B%2522type%2522%253A%2522PANEL%2522%252C%2522contentType%2522%253A%2522EDITOR%2522%252C%2522id%2522%253A%2522clpva9hn600023b6nkf00qyep%2522%257D%255D%257D%252C%257B%2522type%2522%253A%2522PANEL_GROUP%2522%252C%2522contentType%2522%253A%2522SHELLS%2522%252C%2522direction%2522%253A%2522horizontal%2522%252C%2522id%2522%253A%2522SHELLS%2522%252C%2522panels%2522%253A%255B%257B%2522type%2522%253A%2522PANEL%2522%252C%2522contentType%2522%253A%2522SHELLS%2522%252C%2522id%2522%253A%2522clpva9hn600053b6n4vkjqpe5%2522%257D%252C%257B%2522type%2522%253A%2522PANEL%2522%252C%2522contentType%2522%253A%2522SHELLS%2522%252C%2522id%2522%253A%2522clpva9w8o008m3b6ns3xuh1c9%2522%257D%255D%252C%2522sizes%2522%253A%255B50%252C50%255D%257D%255D%257D%252C%257B%2522type%2522%253A%2522PANEL_GROUP%2522%252C%2522contentType%2522%253A%2522DEVTOOLS%2522%252C%2522direction%2522%253A%2522vertical%2522%252C%2522id%2522%253A%2522DEVTOOLS%2522%252C%2522panels%2522%253A%255B%257B%2522type%2522%253A%2522PANEL%2522%252C%2522contentType%2522%253A%2522DEVTOOLS%2522%252C%2522id%2522%253A%2522clpva9hn600073b6nr4v93gfl%2522%257D%255D%252C%2522sizes%2522%253A%255B100%255D%257D%255D%252C%2522sizes%2522%253A%255B50%252C50%255D%257D%252C%2522tabbedPanels%2522%253A%257B%2522clpva9hn600023b6nkf00qyep%2522%253A%257B%2522id%2522%253A%2522clpva9hn600023b6nkf00qyep%2522%252C%2522tabs%2522%253A%255B%257B%2522id%2522%253A%2522clpvadz1800023b6nl1hfpmmo%2522%252C%2522mode%2522%253A%2522permanent%2522%252C%2522type%2522%253A%2522FILE%2522%252C%2522initialSelections%2522%253A%255B%257B%2522startLineNumber%2522%253A19%252C%2522startColumn%2522%253A23%252C%2522endLineNumber%2522%253A19%252C%2522endColumn%2522%253A23%257D%255D%252C%2522filepath%2522%253A%2522%252Fsrc%252FApp.js%2522%252C%2522state%2522%253A%2522IDLE%2522%257D%252C%257B%2522id%2522%253A%2522clpvi1jpm00023b6npqaicne5%2522%252C%2522mode%2522%253A%2522permanent%2522%252C%2522type%2522%253A%2522FILE%2522%252C%2522initialSelections%2522%253A%255B%257B%2522startLineNumber%2522%253A10%252C%2522startColumn%2522%253A13%252C%2522endLineNumber%2522%253A10%252C%2522endColumn%2522%253A13%257D%255D%252C%2522filepath%2522%253A%2522%252Fsrc%252Fstyles.css%2522%252C%2522state%2522%253A%2522IDLE%2522%257D%255D%252C%2522activeTabId%2522%253A%2522clpvadz1800023b6nl1hfpmmo%2522%257D%252C%2522clpva9hn600073b6nr4v93gfl%2522%253A%257B%2522tabs%2522%253A%255B%257B%2522id%2522%253A%2522clpva9hn600063b6nhdbtlqpa%2522%252C%2522mode%2522%253A%2522permanent%2522%252C%2522type%2522%253A%2522TASK_PORT%2522%252C%2522taskId%2522%253A%2522start%2522%252C%2522port%2522%253A3000%252C%2522path%2522%253A%2522%252F%2522%257D%255D%252C%2522id%2522%253A%2522clpva9hn600073b6nr4v93gfl%2522%252C%2522activeTabId%2522%253A%2522clpva9hn600063b6nhdbtlqpa%2522%257D%252C%2522clpva9hn600053b6n4vkjqpe5%2522%253A%257B%2522tabs%2522%253A%255B%257B%2522id%2522%253A%2522clpva9hn600033b6nmt1lpyta%2522%252C%2522mode%2522%253A%2522permanent%2522%252C%2522type%2522%253A%2522TASK_LOG%2522%252C%2522taskId%2522%253A%2522start%2522%257D%252C%257B%2522id%2522%253A%2522clpva9hn600043b6n16hmr1xm%2522%252C%2522mode%2522%253A%2522permanent%2522%252C%2522type%2522%253A%2522TASK_LOG%2522%252C%2522taskId%2522%253A%2522build%2522%257D%255D%252C%2522id%2522%253A%2522clpva9hn600053b6n4vkjqpe5%2522%252C%2522activeTabId%2522%253A%2522clpva9hn600033b6nmt1lpyta%2522%257D%252C%2522clpva9w8o008m3b6ns3xuh1c9%2522%253A%257B%2522tabs%2522%253A%255B%257B%2522id%2522%253A%2522clpva9ngh008h3b6nndc5ezm8%2522%252C%2522mode%2522%253A%2522permanent%2522%252C%2522type%2522%253A%2522TERMINAL%2522%252C%2522shellId%2522%253A%2522clpva9wb70047ehhfbvdgax2g%2522%257D%255D%252C%2522id%2522%253A%2522clpva9w8o008m3b6ns3xuh1c9%2522%252C%2522activeTabId%2522%253A%2522clpva9ngh008h3b6nndc5ezm8%2522%257D%257D%252C%2522showDevtools%2522%253Atrue%252C%2522showShells%2522%253Atrue%252C%2522showSidebar%2522%253Atrue%252C%2522sidebarPanelSize%2522%253A15%257D

I started getting this after upgrading from react 17 to 18.
Reverting the createRoot bit seemed to fix it again, so not sure if the draggable library has been affected by changes in the rendering engine?

We are having similar issues (especially on resize, item seems to not follow the cursor) after upgrading to React 18.

i

Describe the bug
cannot drag item, and the dragged item will automatically move to the first position
Your Example Website or App
https://codesandbox.io/s/cocky-andras-hshv2c?file=/src/ShowcaseLayout.js
Steps to Reproduce the Bug or Issue
drag any item.
Expected behavior
can drag item to ajust position
react-grid-layout library version
1.4.4
Operating System Version
windows
Browser
Chrome
Additional context
No response
Screenshots or Videos

Having similar issues, it's a regression in containerPadding change. One workaround it to pass containerPadding=[0,0]

Having similar issues, it's a regression in containerPadding change. One workaround it to pass containerPadding=[0,0]

it works~


merge: dev to master

:tada: This PR is included in version 0.120.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket: