Gitleaks version supported should be 8 and above

##[error]This version of the task only supports GitLeaks version 8. Specified version is 18.8.4
Specifying v18.8.4 and got the error above.

You are specifing version 18?

oops my mistake! should be 8.18.4.

[like]  Joost Voskuil reacted to your message:

From: Chee Kiam @.>
Sent: Friday, September 20, 2024 6:07:15 AM
To: JoostVoskuil/azure-devops-gitleaks @.>
Cc: Joost Voskuil @.>; Comment @.>
Subject: Re: [JoostVoskuil/azure-devops-gitleaks] Gitleaks version supported should be 8 and above (Issue #91)
oops my mistake! should be 8.18.4.
—
Reply to this email directly, view it on GitHubhttps://github.com/JoostVoskuil/azure-devops-gitleaks/issues/91#issuecomment-2362900104, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AA7DUTVZLYAETNUR2GPP6WTZXO3RHAVCNFSM6AAAAABORDQEYOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNRSHEYDAMJQGQ.
You are receiving this because you commented.Message ID: @.***>


Deleting space before a word trigger meaningless completion

Hi spyder devs,
I've find a new way of improving the completion:
Problem Description
Deleting space before a word trigger meaningless completion.
What steps reproduce the problem?

In a new document type None;
add a space before it;
remove this space.

What is the expected output? What do you see instead?
I would expect nothing, I see the completion with all possibilities.
Versions

Spyder version: 4.1.3
Python version: 3.8

I'm sorry, but this time I don't have time to investigate more.

The same problem, when real-time code completion is available

Hi @ElieGouzien and @leavor,
We are going to fix this for spyder 4.1.4 release. Thanks for reporting!


Upgrade to zcbor 0.6.0

cc @VeijoPesonen

@jheiskan81 Please review.

@oyvindronningstad Out of curiosity, I was under the impression that this code was autogenerated and there's not much room for modifications?

@rlubos The generated code is formatted with clang-format, and then a patch is applied.

@carlescufi You gave me 1minute to approve ;). I know that I am to slow with reviews, but at least give me a chance :D.
Just kidding: I have already approved yesterday, and there were no changes.


[Hub Generated] Review request for Microsoft.ResourceGraph to add version 2019-04-01

If you are a MSFT employee you can view your work branch via this link.
Contribution checklist:

[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.

Can one of the admins verify this patch?

Automation for azure-sdk-for-go

Automation for azure-sdk-for-js

Automation for azure-sdk-for-ruby

Automation for azure-sdk-for-python

Automation for azure-sdk-for-node

@demyanenko can you please review these changes.

Automation for azure-sdk-for-net
A PR has been created for you:
https://github.com/azure/azure-sdk-for-net/pull/5519
.NET SDK Commits:
https://github.com/adxsdknet/azure-sdk-for-net/pull/5519/commits/21cb93209ba4c7e2e632feec5a3925c8e6e2cf2a

Automation for azure-sdk-for-java

@demyanenko can you please review these changes.

Looks good to me.


Sorting delivery methods doesn't work for Local Delivery

Here function output is defining the sorting of the shipping methods, but that is NOT what happens on the checkout. Local delivery seems to have a mind of it's own and sometimes appears randomly as the last shipping method, which is not what the sorting function specified. Is this known behaviour or issue?
Function Stdin:

Function Stdout:

Checkout:

Store name:
https://sylab-store.myshopify.com/

It seems when checkout page is rendered, then function runs 3 or 4 times. Some of those runs generate no op as shown below.

Some of those runs only show 2 shipping methods, seems like it takes time to load Local Delivery.

The problem happens when a no op run happens last, then all shipping methods just appear randomly without any sorting. One would assume that even if the same function runs multiple times, it should generate same output, how is that possible that sometimes there is no output generated? There is literally no change in the function input or function code/meta field.
PS. There is only one function I've deployed which tries to sort shipping methods.

Found something interesting, when a no op run happens, then the metafield input is null. I didn't update metafield value, it just shows null in some of the runs.

Any solution for this?

We used to have some specific sorting logic for local delivery and instore pickup before, but it shouldn't be overriding function outputs. @SaeedYasin , are you able to share the checkout token (the url) of a checkout when you encountered this issue? We'd be able to get a better understanding of what's happening if we have that info.


Is a node its own neighbour?

Hi @melifluos, I have finished an open-source implementation in Rust of the sketching features described in this paper, but after I ran it on a graph as sparse as directed WikiData I realized that many if not all features in the leaves are zeros if I consider each node not as part of its neighbourhood, aka introducing self-loops.
I was wondering what was your opinion in the matter, as I am not sure whether your paper suggests including them or not.
I guess I'll just add a flag and the user can decide for himself - as you may find in my implementation I have added the option to ingest as part of the sketch several other features, such as node types and edge types.
Please find attached the performance of running it on WikiData (over 1 billion nodes a 5 billion edges) on my desktop.

@LucaCappelletti94 this is so cool! Thanks for sharing.
In answer to your question, you must add self loops. This is done before hashes are generated here
https://github.com/melifluos/subgraph-sketching/blob/main/src/hashing.py#L146
If you don't, then in the trivial case of a graph that contains only 2 connected nodes, you will think that the cardinality of their 1-hop intersection is zero.

Perfect, thank you - I have now switched the default flag to true.

@LucaCappelletti94 this is so cool! Thanks for sharing.
In answer to your question, you must add self loops. This is done before hashes are generated here https://github.com/melifluos/subgraph-sketching/blob/main/src/hashing.py#L146 If you don't, then in the trivial case of a graph that contains only 2 connected nodes, you will think that the cardinality of their 1-hop intersection is zero.

Actually, I got a bit more confused about this. For the trivial case you mentioned, isn't that what we want is the cardinality of their 1-hop intersection is zero? since there are only 2 connected nodes, there is 0 common neighbor.

I think 90/100 the effectiveness of either choices depend on the graph topology and you'll need to try both out as part of hyperparameter tuning. I am setting up an experimental setup to do exactly that.


Exploratory analysis Part 1

Merging current changes for exploratory analysis. Have completed:

Proper data subsetting and generation
Fixed plotting issues with type and word frequency using built in plotting methods
Made a function for word cloud generation
Made function to return rows containing a specific string pattern

Still to do in exploratory analysis:

Get counts of hashtags, mentions, retweets, urls, etc.
Counts of above by user, by personality type, average per user and more

Everything looks good; merging


In-game chat system

This may have been mentioned before (I can't find an issue on it, however), but it would be nice to have an in-game chat system so there was a way you could communicate with your opponent during the game.

This may not be too hard to do with the new Vue.js client, we would just need to find a way to persist a chat component between page loads, perhaps we could try putting a JSON object in localStorage and then loading it into a smaller version of the chat?
One idea is perhaps this mini-chat could be accessed from top navbar at any time (except before login). Let's revisit this after #147 is done.

There might be some components on https://vuetifyjs.com/en/ that could be used for this.


Custom Secret Phrase.

I had added 21 million in custon secret phrase and got these errors.

Cause: Base 64 encoding of the hint/note(to retain special characters, like spaces), base 64 has / as a valid char and therefore the deeplink was breaking(as it uses / as the separator)
Solution: Hex encoding of hint/note

Verified this issue on dev app v2.0.67(408)


How to force a specific color.

As said in the title, how can I force the log to be in a specific colour.

Please see #95.


OS edit navigation whilst in file rename mode disables save ability

Reproduce - go into Rename mode, press CMD+Left to go to the start of the file name.
The selection appears to include the icon at the start, grays out the overall selection and whilst it is possible to still type, you can't save the new name, only press Escape to exit.
Thanks!

does it also rename is incorrectly adds tribar ( ≡ ) to the start of the filename ?


[Bug]: An error occurs when creating an empty list after opening the app for the first time and removing it

解决方案检查

[X] 我已阅读常见问题(https://lyswhut.github.io/lx-music-doc/desktop/faq)，并没有找到解决方案
[X] 我已搜索issue列表(https://github.com/lyswhut/lx-music-desktop/issues?utf8=✓&q=)，并没有发现类似的问题

预期行为
No errors will occur when operating as described in the title
实际行为

Open a clean instance (npm run dev or delete the old data and reinstall it)
Create a list in Your Library (我的列表) with any name you want
Right-click on this list and select Remove
Confirm removing it

Lx Music 版本
2.9.0/2.10.0-beta.9
最后正常的版本
No response
操作系统版本
Windows 11, version 24H2
附加信息
This is very distressing for me being in development mode — I wonder if it's a bug from my previous PRs.
v2.9.0 also has this problem.
The following prompt will not appear in the production environment, but will be logged in the developer tools console.

It's not your problem. It is a bug

fixed: https://github.com/lyswhut/lx-music-desktop/pull/2178


programmatic checking for suspicious entries

Motivation: I want to be confident there are no duplicated entries in the database.
Idea: Create a little tool to flag potential duplicates, initially targeting exact copies and then having ones that are suspiciously similar. Even a simple command line tool to print out details of entries that require a human eye. We shouldn't aim for total automation.

Now that we have documentation for the data, that can act as a specification for further tests on the entries to check there are no obvious errors.


Bump the package rev for a bugfix

It would be helpful to include a short description of the changes in the new package version in the commit message when updating external references, but looks good.


Collapse big proposal descriptions

It would be good if the proposal descriptions were collapsed to reduce the scroll over the registered proposals.
A good baseline would be to collapse if description has more than two paragraphs.

This is a nice and simple issue to be fixed who will impacto in a good way in all events, do you have interest on doing this? I can follow you through the steps needed to doit, if you want.
o/

Well, it's a longtime since I wrote something for a webapp code, but I think I can handle this.
What frameworks are used for CSS and JS? According to what I saw in the source, it's bootstrap and jquery (because bootstrap), that's correct?

Yep, Bootstrap, jquery and a bootstrap based theme.

Ok, I'm going to check if I can make it. I'll keep you informed about progresses here!

After a while I had some time to work at this issue :smile:
I digged up the web for solutions to this subject but all I found uses some technique of rewrite the HTML to collapse/expand the text.
So I decided to write a code using the least JavaScript possible. I ended up in the following solution:

After page loads, I look at every .proposal-description and check if its height is greater than 150px, setting the height to 150px if it is. The following image show how is rendered on Google Chrome. Note in the collapsed area that the bottom has some opacity to show that the text was collapsed.

The collapsed area is clickable (cursor: pointer), so when someone clicks, it expands.

Comments

With this solution, JavaScript is loaded only when the page loads and when the collapsed area is clicked: there is no event trigger.
After the long text is expanded, it can't be collapsed again (unless the page is reloaded).
I used 150px for height because looked good for me.
Other ways to show that the text is collapsed:

Change the background color of the area to some light yellow or green or something.
Add a div between the description and vote areas with the text "Show more". That was my first idea, but I didn't do it because would introduce a new i18n string.

What do you think?
Here the patch: collapse-proposal.txt

You should make a pull request instead of this patch, with a patch your
contribution will not be credited to you o/
Em sáb, 8 de out de 2016 01:59, Wagner Macedo<EMAIL_ADDRESS>escreveu:

After a while I had some time to work at this issue 😄
I digged up the web for solutions to this subject but all I found uses
some technique of rewrite the HTML to collapse/expand the text.
So I decided to write a code using the least JavaScript possible. I ended
up in the following solution:

After page loads, I look at every .proposal-description and check if
its height is greater than 150px, setting the height to 150px if it is. The
following image show how is rendered on Google Chrome. Note in the
collapsed area that the bottom has some opacity to show that the text was
collapsed.
[image: collapsed]
https://cloud.githubusercontent.com/assets/428341/19210385/f8eaa82a-8cf7-11e6-9606-d9f8f1d7c085.jpg
2.
The collapsed area is clickable (cursor: pointer), so when someone
clicks, it expands.
Comments

With this solution, JavaScript is loaded only when the page loads
and when the collapsed area is clicked: there is no event trigger.
After the long text is expanded, it can't be collapsed again (unless
the page is reloaded).
I used 150px for height because looked good for me.
Other ways to show that the text is collapsed:

Change the background color of the area to some light yellow or
green or something.
Add a div between the description and vote areas with the text
"Show more". That was my first idea, but I didn't do it because would
introduce a new i18n string.

What do you think?
Here the patch: collapse-proposal.txt
https://github.com/luanfonceca/speakerfight/files/517430/collapse-proposal.txt
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/luanfonceca/speakerfight/issues/140#issuecomment-252403142,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABa_u2RX5TBd779CAEe8eJWbsrFSDa0Xks5qxyMmgaJpZM4I1VwY
.

Oh, of course. I wanted to discuss here before I make the PR.
But you are right, I'll do it and move the discussion to there.

Thanks, we cab discuss and review it on the PR o/
Em sáb, 8 de out de 2016 13:58, Wagner Macedo<EMAIL_ADDRESS>escreveu:

Oh, of course. I wanted to discuss here before I make the PR.
But you are right, I'll do it and move the discussion to there.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/luanfonceca/speakerfight/issues/140#issuecomment-252435706,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABa_u-5QeuSxhgWfvmWt9FByzuihy-8dks5qx8udgaJpZM4I1VwY
.


OAuth 2.0 new SDK feature documentation

Proposed changes
Adding OAuth information to Node and Python
Merge timing
Depending on OAuth release

@rchinn-segment I'll take care of merging this PR in as it'll go out with the OAuth docs that I'm releasing later this week


[Feature] Check if crc daemon process is reachable in case the network mode set as vsock

On all the platforms we need crc daemon to be running to work with vsock, It would be great if we can detect it as part preflight if the network mode is vsock ?

s/running/reachable...

The reason for reachable is a possible cause of it not running; at the moment we do not perform any checks if we can bind to these ports. They might be in use by something else. So we need to check if the port is reachable (and followed by a process or API check). If no expected response, we might have to start the daemon... but if this fails, we need to act on the error. The problem might be that these ports are already in use and need to be suffixed or offset for the new process.


Support for multi-turn conversation benchmark

Would harness plan to support multi-turn conversation benchmark such as MT-bench?

Hi! We likely will not support general multi-LM call evals, because the complex case would need e.g. asynchronous building and dispatching of requests and would require significant internal reworking to do efficiently. There has, however, been interest in LLM-as-a-Judge which we'll be considering adding as a special case.
This might change depending on user interest and if maintainer bandwidth freed up at all, though I think in general it might be preferable to consolidate the library around supporting static evals and e.g. first expanding to improve long-context eval support and code generation task support.
One library you might find useful for more complex multi-call control flow is Inspect AI, which has been designed around this use case. https://github.com/UKGovernmentBEIS/inspect_ai

Thank you for your feedback! While multi-LM integration may not be my main focus, multi-turn conversation is a pressing need for us.


Possibly improve LIBASSERT_UNREACHABLE macro

Make it function-like and use std::unreachable() if C++23

I'm going to close this for now since it'll now conflict with dev and there were issues with the CI runs, however, happy to discuss further or revisit once merge conflicts are resolved


[UX] - Fix: Browser back in assistant builder

Browser back should ideally bring user back the previous state (from "select data source" to "assistant builder", from "select a Notion data source" to "select data source" and so on)

@PopDaph I think you tackled this one did you not?

iirc I fixed part of it, there was still a bug left on the datasource modal but that is supposed to disappear with vault since we're reworking this modal so we agreed to keep living a bit with it


[XL] feat(AST parser): Polyglot split - tests + lint passing

This PR converts the Python AST parser into two subcomponents:

The language-specific (in this case, Python-specific) part parses sample code, and dumps the relevant {snippet, test} method data into a language-agnostic JSON file.
The "core" component uses this JSON file to associate specific test methods with their matching snippets.

(Apologies in advance for such a large PR - the parser itself was completely re-architected, so it was kinda hard to avoid. 😕 )
DO NOT MERGE until python-docs-samples is updated to work with this (or, alternatively, locked to a specific commit hash).

This PR is being split into smaller sub-PRs. Marking as draft. 🙂

FYI: this PR is being split into smaller, multi-stage sub-PRs.
(I'll close it once those smaller PRs have all been merged.)

This is now obsolete; closing.

This is now obsolete; closing.


guile-lzma: init at 0.1.1

Description of changes
Add guile-lzma. Will eventually be using this for packaging Guix.
cc @cafkafk

Things done

Built on platform(s)

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

[ ] 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
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 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.

Result of nixpkgs-review pr 257957 run on x86_64-linux 1

1 package built:

guile-lzma


Install on Linux with no root or network access

I'm trying to install elastalert in a Linux stage environment and I don't have root or network access. The linux machine also don't have pip, but I might be able to install it if having it can make this work.
I've tried using pip to install elastalert and the required packages in my local machine then transfer the files to my Linux however, I'm not able to start elastalert.

It seems to be not able to find my blist even though it's in my /elk/elastalert directory.
I'm just wondering if this is something that's possible and if so, what's the best way to do this?
Thanks.

Did you copy over _blist.so? Some libraries, like blist, contain compiled c code that ends up in a .so file. I think It should also appear in the site-packages/blist/ folder.
An easier way to manage this would be to use a virtualenv to install all the packages to, and then copy the virtualenv folder. I'm not sure if its actually any better than coping over /usr/lib/python files, but it is a little more self contained.
I've never attempted to do this but I think it should be possible.

Sorry for the late reply.
I didn't see any _blist.so. I had install elastalert on another Linux machine that works and I've checked there's no _blist.so.
I've tried using virtualenv but the problem is I've different paths between the two machines so I'm having trouble to make that work.

Hmm, there is a _blist.so file somewhere. Where did you check? It might be platform dependent where it gets installed to. You can also search for a wheel (.whl) file online that exists for your specific Linux distro, or, build one yourself. There may also be other third party tools for this.


Command-specific Permissions

Add a settings file for permissions for each command. Example
-Blacklisting can only be done by Admin role
-Requesting an announcement can be done by anyone

Finished this feature. Closing for now.


add failing test for #121

Fixed, are we good to go?

i am concerned that right now tests are covering only SSR

while error happened without it

added tests for that

i am concerned that right now tests are covering only SSR

JssProvider was involved, it is most of the time used for SSR, also it has reproduced the issue, so I wouldn't know what to cover otherwise.

@kof original issue was reproducible with JssProvider but without ssr, so i added tests for that

It was reproducible with both, renderToString and render, so it doesn't matter. The nature of the issue was independent of environment. I removed those other tests because after fixing the issue covered by ssr test other tests were fixed too, so I though it doesn't make sense to have tests where it is not 100% clear why they are needed.

my idea behind additional test is that issue is reproducible without SSR, so i thought it makes sense to have additional test wo/ ssr

@oliviertassinari i cant find you comment

I wish we have kept that feature for https://github.com/callemall/material-ui/pull/7461

I have removed this comment. I have added that feature to the MuiThemeProvider instead of the JssProvider.

i mean we fixed a bug, why would you rely on it?


When export CSV files column separate error with column value contains CSV  comma separator.

Description
As the title description and as we known, The CSV file use the COMMA [  ,  ]  to separate different columns , But in some column data value its contains one or more COMMA  ,and the CSV column separate cannot work properly .
Maybe my export setting was error or  dbeaver have other solution for export , why we use CSV,because our user need Microsoft's  OFFICE's Excel.exe to open it ,Without dbeaver CSV export we have no choise.
It's can not be define as a BUG in feature aspect, if you can add new feature: add new export file type like *.xls or *.xlsx .
DBeaver Version
<IP_ADDRESS>404211624
Operating System
windows10
Database and driver
MySQL 8.0.25
MySQL Connector/J mysql-connector-j-8.0.33
Steps to reproduce
DDL
-- test.test definition

CREATE TABLE `test` (
  `id` varchar(32) NOT NULL COMMENT '主键',
  PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb3 COMMENT='测试表';

DML
INSERT INTO test (id) VALUES('1,112,1');
INSERT INTO test (id) VALUES('102,3');
INSERT INTO test (id) VALUES('3,1');
INSERT INTO test (id) VALUES('4');

Images of reproduce steps

test_202405131053.csv
Additional context
Thank you to everyone of dbeaver for their contributions to open source projects, as you see , I'm Chinese and the some Chinese translation in export setting not Chinese , So I want to  do something for this  ,but I have no idea about this, can yours do me a favor or some tips, THANKS again.

about additional context,  I mean some export setting selector  English value not Chinese under this image .

The software you use to view csv files uses , as a columns delimiter. There should be a setting to change it. When I open the result of such export in Excel, I don't experience this issue. You can try opening it with Notepad to see, that here we have just a strings in quotes:
"主键"
"1,112,1"
"102,3"
"3,1"
"4"

Yes, we can change setting with other columns delimiter, but the column value can contains other columns delimiter too.  the csv file type only use comma delimiter whatever you have quotes in strings, so I'll close this bug issue and still hope it's can be export by the *.xls or *.xlsx file type in the future .

see https://marketplace.eclipse.org/content/dbeaver-office-integration


Annotate Generate Traces With RAG results

We should annotate the generate traces with the rag results.
We should probably add a concept of spans to the trace
https://github.com/jlewi/foyle/blob/5a63b466f2ff68b7120fbe10159dd7f5f81f28c3/protos/foyle/logs/traces.proto#L25
The span could then be a oneoff with different types of results.
We log the RAG results here
https://github.com/jlewi/foyle/blob/5a63b466f2ff68b7120fbe10159dd7f5f81f28c3/app/pkg/learn/in_memory.go#L104
So we can update our analyze code to get those entries.

We don't currently log the query but we probably should
https://github.com/jlewi/foyle/blob/5a63b466f2ff68b7120fbe10159dd7f5f81f28c3/app/pkg/learn/in_memory.go#L54


feat(frontend): expose Vnode function as __rw_vnode for easy debugging

I hereby agree to the terms of the Singularity Data, Inc. Contributor License Agreement.
What's changed and what's your intention?
Expose Vnode function as __rw_vnode for debug purpose.
Checklist

[x] I have written necessary rustdoc comments
[x] I have added necessary unit tests and integration tests
[x] All checks passed in ./risedev check (or alias, ./risedev c)

Refer to a related PR or issue link (optional)
https://github.com/singularity-data/risingwave/pull/4262#pullrequestreview-1053889717

I think prefix it with rw_ is enough, without the __ ☺


Prevent erroneous parsing of Bible verses in usernames.

I believe discord.js uses an object type called "Snowflake" for user tags, so maybe the code for this will involve checking if it's a Snowflake or what have you.

Testing shows no detection of the usernames as actual verses, but as user IDs (how Discord normally does). Might be a fluke, might not, we'll see.


Error Handling using exceptions and middleware

In this PR we are trying to implement an Error Handling mechanism.

[x] A global way to throw and handle business or unhandled errors
[ ] Identify and Categorize errors with codes
[x] Create a suitable result to be handled by clients or notify users
[x] Create suitable logs

@MostafaTech are you still working on this branch? Please close PR, delete branch in case you are done.


fix: remove unused deps RNCKakaoUser in social

Type of change

[x] Bug fix (non-breaking change which fixes an issue)

What does this change?
Remove the unused dependency RNCKakaoUser in the social package, which causes an error during pod install.

what error? you should add user package if want to use social. it is described in docs

@mym0404
I'm trying to use share package, and it is not documented in here.

ok we should change share package's installation docs instead.

I've got a question.
In the share package, the only part of use something relative to social is here. However, it doesn't seem to be part of social but rather of core.
Therefore, I think that social can be removed from the dependencies of share. What do you think?
If my understanding of your library is incorrect, please let me know.

social depends on talk and share RNCKakaoShareModule depends on talk so talk is a transitivity dependency. In the monorepo design, I thought we had to prevent two RN package depends on same kakao native sdk.

code you indicated is unrelated to social package, yes

thanks 👍


Add a guide to use KO_DATA_PATH for operator-sdk up local

This patch adds a guide to use KO_DATA_PATH for operator-sdk up local.
Fixes https://github.com/knative/serving-operator/issues/51

Thanks, but this is obviated by https://github.com/knative/serving-operator/pull/48
/close


light-client: test against a real full node in CI

We should run the light node against a real full node in CI per https://github.com/informalsystems/tendermint-rs/issues/120#issuecomment-644173634
We already run the RPC integration tests against a local full node, but we're not running the light node against it.
The first and simplest thing to do is to run the light-node against that full node. Since it will just be a 1 validator blockchain that doesn't change, this will not test much of the light-client functionality, but is more about ensuring the light-node init/config/process is working correctly and can sync with a real full node.
Future iterations could introduce a lot more complexity:

talking to multiple full nodes (where one of the full nodes may be faulty or may serve a fork)
enabling validator set changes on the chain (this would require other full nodes to actually be set up to be the new validators, even if the light node doesn't talk directly to them!)
talking to remote full nodes from a live mainnet/testnet Gaia blockchain

Since there's a lot to do re scoping the more complex set ups, let's start with the simplest for now.

ref: https://github.com/tendermint/tendermint/pull/5087
Context: when new docker images for tendermint-go are published, it should simplify testing against CI slightly.

Hey is this done with #431?

Yeah this is done but made a follow up for the binary initiazation process specifically in #445.


Strange column header alignment with PSCustomObject

Steps to reproduce
In PowerShell terminal enter the following:
[PSCustomObject]@{
    Column1 = 'Test'
    Column2 = 'This is some text'
    Column3 = 'This is some more text'
    Column4 = $true
}

Expected behavior
Column4 is correctly positioned over the dotted separator line.

Actual behavior
Column4 is butted up against Column3 and is not positioned over its content.

Environment data

> $PSVersionTable
Name                           Value
----                           -----
PSVersion                      6.1.0-preview.2
PSEdition                      Core
GitCommitId                    v6.1.0-preview.2
OS                             Microsoft Windows 10.0.16299
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Note: this appears to be a new bug with the 6.1 build, it works as expected in 6.0 GA release (I have not tested against 6.0.1, 6.0.2, or 6.1-preview1 so it may have existed before 6.1)
.

/cc @SteveL-MSFT Again edge case in Format-Table.

This is already fixed as part of the format-table changes since Preview.2.  Just validated it works fine off master build.


Limit bounce effect

I've been digging in the source code and trying to figure out a way to limit the bounce effect.
As far as I know the bounce animation is dependable on the fling which makes it possible to bounce the page on almost the entire screen.
What I would like to accomplish is to limit that bounce to, let's say, half the screen size (for example).
The bezier curve on the bounce only have effect on the animation speed so if someone could point me in the right direction that would be great.

+1, please report back if you find something, @MippinTeam!


Use Mac OS 13 for building

The Xcode version used in the Mac OS 14 runners was upgrade to 15.4 beta, which has broken Qt 5.15.2 builds.

Closing unneeded PR.


refactor(Quickstarts): Updated the meta details of 26 quickstarts

update the page title and meta description of top 26 quick-starts.
list of the quickstarts

Amazon web services
Apache
CircleCI
CodeStream
Databricks
Django
.Net
Express
FastAPI
Flask
IBM MQ
Java
Kafka
Lacework
Laravel
MongoDB
MySQL
NGINX
PHP
Redis
Salesforce Event logs
Slack notifications
Synthetics SSL certification
Apache Tomcat
WordPress
Python

Hey @smamindla57, this repository does not support pull request from forks. In the future could you submit pull requests from a branch on this repository? If you need access we can get you added!

Hi @aswanson-nr, yes please, grant me access. thank you

I built and tested this locally, looks good. The workflow won't run since this is from a fork so I'm going to force the merge, in the future lets keep PRs from branches within this repository instead of a fork workflow.


Cannot read property 'status' of null

VSCode Version: The latest
OS Version: Win10

Steps to Reproduce:

git can not open error：Cannot read property 'status' of null

Full error from Developer console:

VSCode Versions: Latest Insiders
OS: Win10

Hi,
I can verify that this is also happening on VS Code latest insiders on Windows. Error from developer console attached below
index.html?config={"pathArguments"%3A[]%2C"programStart"%3A0%2C"enablePerformance"%3Afalse%2C"verbo…:28 [uncaught exception]: TypeError: Cannot read property 'status' of nullonError @ index.html?config={"pathArguments"%3A[]%2C"programStart"%3A0%2C"enablePerformance"%3Afalse%2C"verbo…:28```

duplicates #7597


DPF: improve token validation for synchronous data transfers

Current implementation
The DPF public API takes as input a signed bearer token. This token contains as claims the contract id and the data address  of the actual data. The data address is encrypted using a private key in order to make it not-readable outside of the EDC environment (see #585).
When the DPF receives receives a sync data request, it first sends the input token to the validation API exposed by the Control Plane, which is in charge of:
• checking token signature to ensure the the present Control Plane has generated this token,
• checking that token is not expired,
• checking that contract still allows access to the data (note that at time of writing the contract validation consists only in checking the contract expiration date),
• decrypting the data address,
• returning the set of token claims in the response.
In current implementation the token is generated only once at artifact request time and saved in the consumer environments by the registered EndpointDataReferenceReceiver (see diagram below).

If validation is successful, then the Data Plane uses the decoded data address returned by the API in order to generate the DataSource object that will be used to retrieve the data.
Limitations
This approach has several drawbacks:
• token has necessarily the same lifetime as the contract as it is never renewed --> short-live token are good practice,
• not scalable as each call to the public DPF API leads to a call to the Control Plane,
Proposed alternative
We cannot afford to call the Control Plane for each call to the DPF public API as both entities scale differently. Thus the DPF should be able to verify by itself the signed token. This means that Control Plane must share with the DPF the key pair used for token signing AND for the data address encryption (if different key pairs are used).
Also short-live tokens must be preferred, which implies to be able to renew tokens frequently as they expire. This is obtained by:
• introducing a Token Renewal API in the Control Plane that will actually replace the current Validation API,
• adding the endpoint of this Token Renewal API as claim in the token.
Thus when a request is received by the consumer Data Plane, the input token will be verified first (internally, see above) and the expiration date of the token will be inspected. If token is expired then the Token Renewal endpoint provided in the claims will be called to ask for a token renewal.
This API will be in charge of validating that the contract is still valid before generating a new token. The newly generated token is then:
• returned back in the call response in order to enable the Data Plane to process the current data request.
• forwarded within the consumer environment using the set same of registered EndpointDataReferenceReceiver used at initial generation time (see steps (1), (2) and (3) in diagram below).

Limitation
If contract is revoked for any reason, the consumer will still be able to access the provider data until the lastly generated token (when contract was still valid) finally expires. However this is not a strong limitation as tokens are short live (few minutes).

Hi @algattik @jimmarino @paullatzelsperger
follow-up of our meeting last week. Asking for your kind review :)

thanks, Ben, definitely an important topic we should solve!

I'm in doubt if we should pass internal information inside of the token, even if it's encrypted (need to double check with an security expert).
Asking from another perspective: I understood that we encode some information to the token to keep the dataplane statelesse and avoid calls to the control plane. Are we sure that we can encode all necessary information? Or better improve the communication between dataplane and controlplane (share more data; caching; ...) and use just random strings as token?
We should force a backend application to use the dataplane and not being able to bypass it as we need to provide some policy enforcement (log every call etc.)
What are the security benefits of having a token that is just valid for a short time in our scenario? We could invalidate a token easily and immediately (dataplane is under control of control plane) and both token issuer and audience belong to the same entity. Is it more about forcing a participants to regularly exchange messages via control plane to check the claims against the policy of the contract?

 Moritz Keppler<EMAIL_ADDRESS>Daimler TSS GmbH, legal info/Impressum

Provided that state-of-the art encryption mechanisms are used, I wouldn't worry too much about someone being able to decrypt the token.
In case there are company rules in place that forbid the dissemination of private information, even if encrypted, there is an easy way around this:
We could simply put the asset ID in the token claims. The only modification the would be that the ProviderDPF would need a DataAddressResolver to get to the DataAddress.
As to your third point: one advantage of having short-lived tokens is that we can keep the refresh mechanism stateless. We don't need a record of all valid tokens, which we would with long-lived ones.
Another, if smaller, advantage is that when cancelling a contract, we wouldn't have to also go and invalidate the token, which reduces transactional complexity, as this would be implicit during the next (then-failing) refresh cycle.

Would definitely prefer a solution that limits the information encoded in the token to a minimum. Agree that it should work having a token that can be used to look up the corresponding data transfer process (isn't it the TransferProcessId that we need instead of the contractId?)


Fix sort by date bug when there is no json file upon first initialization

Codecov Report

Merging #150 into master will increase coverage by 0.02%.
The diff coverage is 0.00%.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 45153c9...0a332ac. Read the comment docs.


[3.50] RenderTexture - drawFrame ignores alpha

Version
3.50 - latest from the repo
Description
drawFrame  ignores alpha param and always draws with alpha = 1

Example Test Code
        preload() {
		this.load.image('bg', 'assets/graphics/bg.png')
		this.load.image('red_rect', 'assets/graphics/red_rect.png')
	}

	create() {
		this.addImage()
		this.addRenderTexture()
	}

	private addImage() {
		this.addLabel("Original Image", 250, 40)
		this.image = this.add.image(250, 320, "bg")
	}

	private addRenderTexture() {
		this.addLabel("Render Texture", 750, 40)

		this.renderTexture = this.add.renderTexture(750, 320, this.image.width, this.image.height)
		this.renderTexture.drawFrame("bg")
		this.renderTexture.setOrigin(0.5)

		let position = this.image.getTopLeft()
		let rect = this.add.image(position.x, position.y, "red_rect")
		rect.setOrigin(0)
		rect.alpha = 0.5

		this.renderTexture.drawFrame("red_rect", null, 0, 0, rect.alpha)
                // this.renderTexture.draw(rect, 0, 0) // simple draw works fine
	}

Additional Information
The issue occurs only with canvas renderer. When I use the draw method and draw a game object to render texture it respects the alpha value of this game object.
Probably related to #5412, #5422

Thank you for submitting this issue. We have fixed this and the fix has been pushed to the master branch. It will be part of the next release. If you get time to build and test it for yourself we would appreciate that.


Gpu Swap Bugfixes

A series of bugfixes to make swapping work. Changes includes (but not limited to):

(history) Use environment variable to determine swapping algorithm
(history) Remove FIFO algorithm. Replaced with LRU algorithm
(history) Fix native history based algorithm to prevent a bug that cause illegal memory access
(storage) Fix free function in storage manager to correctly delete obsolete address
(swap) Replace all rlock with wlock to prevent a bug that seems to cause illegal memory access
(swap) Remove a CUDA condition that seems to cause a bug.
(swap) Add error logging to all cuda call.
(prefetch) Disabled in current version for further debugging
(memory) Add a naive memory manager as a placeholder for the more complex version
(benchmark) Add sleep to prevent binding and first loop from mixing with each other

Since there is already a version of mem_mgr on gpu_swap, I renamed the naive one to mem_mgr.ccbakup.

@fegin Requested changes are up


Add BlueLight

Website: https://bluelightos.github.io/

Thanks for the suggestion, but I'm going to pass on this.


Mono: Fix detection of MsBuild from Visual Studio

This was a wrong check as an exit code of 0 means success,
not failure. It used to be fine as blocking mode always returned
-2, but this was changed in #32033 to return the exit code.
Fixes #32424.

@KellyThomas @piratesephiroth Can you confirm that it fixes the issue?

The fix is likely find, but I'm actually not sure about my interpretation that it was caused by #32033. OS.execute() should return an Error code, so it's 0 (OK) when it succeeds. What #32033 changed is the value of the optional exit_code 6-th argument, which is not used here. Or does Godot.OS.Execute return that instead of an Error code?

The scripting method OS.execute() (Godot.OS.Execute() in C#) is implemented in C++ with _OS::execute. It returns the same as that method, an int (-1 on error, and exit code or pid), not Error. So your interpretation was correct.

yep, it's working again, thank you

Yes, this fixes the issue for me.


HashToCurve: What is extra data for?

The HashToCurve trait's hash function takes as input three strings domain, message, extra data.
Its unclear to me what the purpose of extra data is. At the moment, it acts the same as a message in the try and increment hashes. (here: https://github.com/celo-org/celo-bls-snark-rs/blob/master/crates/bls-crypto/src/hash_to_curve/try_and_increment.rs#L97 and here: https://github.com/celo-org/celo-bls-snark-rs/blob/master/crates/bls-crypto/src/hash_to_curve/try_and_increment_cip22.rs#L92)
Can this be removed from the API from it?

The use of it after CIP22 is that the extra data is only part of the outer hash while the message is in the inner hash. This is useful when the inner hash is very expensive, and the extra data can contain data that is relevant only for some clients in the outer hash. For example, we use extra data to include the "epoch number" and the "round number" from consensus, so that we can slash validators on double-signing on-chain, without having to perform the inner hash, it's provided as an opaque blob.
Before CIP22 it's not very useful but we keep it to maintain backwards compatibility at this point.

I see (I missed the inner hash in the cip22 logic), totally makes sense for the double hashing paradigm! Is the inner hash relatively expensive natively as compared to signature verification? (Just trying to understand the decision!)
I wonder if it would make most sense if there were two traits, HashToCurve and DoubleHashToCurve, with DoubleHashToCurve capturing that the HashToCurve's dependence on the message is XOF(H(msg)). Then extra data could be become outer hash only data for DoubleHashToCurve. And DoubleHashToCurve could auto-implement HashToCurve.
Is this a change you'd be interested in having? If so I can try to add it. (I wanted to re-use the hash to curve logic implemented here for another project I'm working on)

Yep, that inner hashing is very expensive in one of Celo's cases :) The inner hash is a Pedersen hash on 14k bytes (150 validator public keys).
I'd definitely like that contribution, it'll make things nicer!
To be exact, the current hash to curve doesn't add an extra hash compared to Blake2Xs, it's a variant of it. Blake2Xs already has an inner hash, it's just always Blake2s and doesn't support "extra data". So maybe DoubleHashToCurve is not the best name, but I don't have a better idea yet.

Ah, that definitely makes sense for why you're doing it! Thanks for the expl.
Perhaps the name CrhAndXofHashToCurve is more accurate?


Add awesome-gocui/gocui to the examples list

At awesome-gocui/gocui we just released v1.0.0-beta-1 and with this we moved away from termbox to tcell!
This has been a long awaited change for us and gives gocui a brighter further as termbox was kinda depricated.
Sooo my questions was can our fork of gocui be added to the examples list?
If you want to wait for a stable release i think it should be in a few weeks as we didn't encounter any bugs so far.

Feel free to submit a PR -- no need to wait for your stuff to have any particular level of "stability".

Cool i'll create a pr soon


Execute actions on multiple issues

Like assigning labels, milestones and such to multiple issues at the same time.

This would be a huge timesaver for people using Gogs issues for their project management.


Default form styles in mobile browsers

I wanted to make an open discussion about if default browser styles should be integrated/used to reduce the amount of CSS or giving more focus on setting the styles for each browser the same.

Adding appearance: none to all form elements and updates the styles for each property e.g. border, box-shadow, outline, etc. Therefore the elements could be customized even more.
Just adding missing properties to override browser defaults

Screenshot from iPhone in Safari

fixed in #25

Please assign this issue to me


cimg: 2.9.4 -> 2.9.6

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/cimg/versions.
meta.description for cimg is: "A small, open source, C++ toolkit for image processing"
meta.homepage for cimg is: "http://cimg.eu/"
meta.changelog for cimg is: ""
Updates performed

Version update

To inspect upstream changes

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

directory tree listing: https://gist.github.com/7f65d4bae091d22bec7e2ed551e86e37

du listing: https://gist.github.com/65e8e26b1248d23c047ba319d75f17fe

Rebuild report (if merged into master) (click to expand)

11 total rebuild path(s)

3 package rebuild(s)

3 x86_64-linux rebuild(s)
3 i686-linux rebuild(s)
2 x86_64-darwin rebuild(s)
3 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
cimg
phash
wxcam

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/a91cbm7jh12bv10nplq9325vkainz4w8-cimg-2.9.6 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A cimg https://github.com/r-ryantm/nixpkgs/archive/44d0a09633d3c3cd0e2e79e812b0143c6eeb3042.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/a91cbm7jh12bv10nplq9325vkainz4w8-cimg-2.9.6
ls -la /nix/store/a91cbm7jh12bv10nplq9325vkainz4w8-cimg-2.9.6/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

3 packages built:

cimg
phash
wxcam

Maintainer pings
cc @AndersonTorres for testing.

Result of nixpkgs-review pr 112856 at 44d0a096 run on aarch64-linux 1

3 packages built:

cimg
phash
wxcam

1 suggestion:

warning: missing-phase-hooks
installPhase should probably contain runHook preInstall and runHook postInstall.
Near pkgs/development/libraries/cimg/default.nix:14:3:
   |
14 |   installPhase = ''
   |   ^


update log4j dependency

Please update log4j dependency https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228

Done.
Maven Central needs some time to publish.


Homepage Down & Instructions for Launch Image

Hi, the link to the Homepage from the readme is down.
As well, (and I'm guessing they were on the homepage), so instructions on what images sizes to use in the Launch Images area would be good.

Hi @tonydehnke,
I've added a custom domain for my GitHub Pages, the new url is: https://raphaelhanneken.com/iconizer
I haven't thought about the effects it would have on my other repos. Thanks a lot for letting me know.

Cool, thanks.. I like how you have the recommended sizes for Launch images, might be good to add to the Image Sets area too?

Image Sets can be anything, so there is no recommended size or aspect ratio. Iconizer will just scale the image you dropped down to its @2x and @1x sizes.


Warning: DatePickerAndroid has been merged with DatePickerIOS and will be removed

Warning: DatePickerAndroid has been merged with DatePickerIOS and will be removed in a future release. It can now be installed and imported from '@react-native-community/datetimepicker' instead of 'react-native'. See https://github.com/react-native-community/react-native-datetimepicker

same with me, have you found a solution?

just read documentation how to migrate from old component to new way
https://github.com/react-native-community/react-native-datetimepicker#migration-from-the-older-components


Journal.ByPath index out of range error

Describe the bug
[
Traceback (most recent call last):
File "", line 373, in JournalFromPath
IndexError: index out of range: -1
,
Traceback (most recent call last):
File "", line 487, in JournalFromPath
IndexError: index out of range: 1
]
Steps to Reproduce
Opened sample files 2.x Journal_Crash Investigator and Journals_Healthcheck.dyn and found that the Journal.bypath gives traceback errors: [
Traceback (most recent call last):
File "", line 373, in JournalFromPath
IndexError: index out of range: -1
,
Traceback (most recent call last):
File "", line 487, in JournalFromPath
IndexError: index out of range: 1
]
Expected behavior
This error feeds nulls into downstream nodes
My setup

Operating System: Windows 10, Revit <IP_ADDRESS>6
Dynamo version: Dynamo Revit <IP_ADDRESS>40

Housekeeping
Please make sure these boxes are checked before submitting your issue:

[ ] I am running the latest available version of Journalysis (2.3.1)

Hi @rizzoblo, did this hppen with multiple journals or just one specific journal?

@rizzoblo I made a couple of changes (0e07c815173ed506a18ea1ab84586c670fcb66ab) to the Journal.ByPath node that fix some issues I had with a number of journals not being processed correctly. Perhaps this will fix your issue as well. Try downloading the latest version of that node and replace the existing version in your package directory with it:
https://raw.githubusercontent.com/andydandy74/Journalysis/master/nodes/2.x/Journal.ByPath.dyf
I will probably release an updated version on the package manager early next year.

It is still giving me traceback errors.
On Wed, Dec 8, 2021 at 3:20 AM Andreas Dieckmann @.***>
wrote:

@rizzoblo https://github.com/rizzoblo I made a couple of changes (
0e07c81
https://github.com/andydandy74/Journalysis/commit/0e07c815173ed506a18ea1ab84586c670fcb66ab)
to the Journal.ByPath node that fix some issues I had with a number of
journals not being processed correctly. Perhaps this will fix your issue as
well. Try downloading the latest version of that node and replace the
existing version in your package directory with it:
https://raw.githubusercontent.com/andydandy74/Journalysis/master/nodes/2.x/Journal.ByPath.dyf
I will probably release an updated version on the package manager early
next year.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/andydandy74/Journalysis/issues/50#issuecomment-988636757,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALZL4G2JWO5JGOFN6KL6SQTUP4PPLANCNFSM5JABEBXQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

@rizzoblo I'm afraid I will need to have a look at the journal file that is causing this. Are you able to share it?

I'm also getting this error (line 487). Happens on all journals.
Revit 2022.1, Dynamo 2.12

@bll85 Would you be willing to provide a sample journal file?

journal.0605.txt

I updated the dyf file from the repository. Error is gone. Thanks

@bll85 Good to know. I should probably update the package then.

I believe this should be fixed with the latest commits


ENH: signal: add firls and freqz, freqz_zpk, sosfreqz

This complements firwin, which is available in cuSignal.
Heavy lifting is delegted to solve and special matrices (hankel, toeplitz), so there is not much to optimize at this level. Will need to test a bit the behavior with ill-conditioned matrices, where scipy switches from solve to lstsq.
Testing uses freqz, so add that as well. While at it, also add sosfreqz to finish up frequency response functions.
All implementations and their tests are pretty much straight vendoring scipy.signal sources, with minimal modifications.
Two small things:

scipy.signal.freqz uses an evaluation routine from numpy.polynomial.polynomial. This uses the Horner's scheme, unlike the old-style cupy.poly1d which just straight multiplies monomials. So this PR just vendors the evaluation routine. If it turns out that we use a lot of new-style polynomial API, we can think of exposing it in cupy. For now it's juts a private routine. These routines are added to cupy.polynomial.polynomial.
0D cupy arrays do not decay to python scalars in the same way numpy 0D arrays do. E.g. operator.index(np.array(5)) succeeds but cupy.array(5) raises. Not sure if it's a deliberate choice or bug.

Also, there's a general design question for this filter design functionality. Scipy.signal versions accept array_likes (e.g. lists), while typically CuPy is more strict and requires cupy arrays. Which convention do we want to follow?

0D cupy arrays do not decay to python scalars in the same way numpy 0D arrays do. E.g. operator.index(np.array(5)) succeeds but cupy.array(5) raises. Not sure if it's a deliberate choice or bug.

This behavior is CuPy's choice.

Also, there's a general design question for this filter design functionality. Scipy.signal versions accept array_likes (e.g. lists), while typically CuPy is more strict and requires cupy arrays. Which convention do we want to follow?

We generally want to have a stricter way that requires only CuPy arrays to avoid implicit sync, however, there would be exceptional cases where it is expected that users almost always pass a list to an argument. Let's discuss it when you have such a case.

We generally want to have a stricter way that requires only CuPy arrays to avoid implicit sync, however, there would be exceptional cases where it is expected that users almost always pass a list to an argument. Let's discuss it when you have such a case.

Sure, so the decision is to disallow the usage with this, unless there's a very compelling reason:
In [4]: import cupyx.scipy.signal as signal

In [5]: w, h = signal.freqz([1, 2, 3], [4, 5, 6])

Implementation-wise, this amount to not starting scipy.signal clone functions with cupy.asarray.

Sure, so the decision is to disallow the usage with this, unless there's a very compelling reason

Indeed.

/test mini

/test mini

I've reran the static check.

Updated:

xfailed firls tests which run into https://github.com/scipy/scipy/issues/18533
added a test copied from scipy, which only looks at the extreme values of the filtered signal instead of a direct comparison with scipy.signal
removed tests which depend on *ord functions. These tests are fixed up and included into https://github.com/cupy/cupy/pull/7632

This is PR is now I think ready from my side.

/test mini

CUDA 102 and 11x CI failures are most likely the same as those dealt with gh-7627

Thanks, @ev-br!


fix: (android) text colour not applied on API > 30

Platforms affected
Motivation and Context

Description

Testing

Checklist

[ ] I've run the tests to see all new and existing tests pass
[ ] I added automated test coverage as appropriate for this change
[ ] Commit is prefixed with (platform) if this change only applies to one platform (e.g. (android))
[ ] If this Pull Request resolves an issue, I linked to the issue in the text above (and used the correct keyword to close issues using keywords)
[ ] I've updated the documentation if necessary

This is implemented on the dark content branch and PR submitted to merge to that branch.


1.0.11 does not work with 6.6.1

Hi,
thanks for this great plugin, ...but it stopped working with 6.6.1
error:
2019-09-05 07:22:17,322 ERROR [spring-startup]  c.a.plugin.osgi.factory.OsgiPlugin Detected an error (BundleException) enabling the plugin 'ru.andreymarkelov.atlas.plugins.prom-bitbucket-exporter' : Unable to resolve ru.andreymarkelov.atlas.plugins.prom-bitbucket-exporter [126](R 126.0): missing requirement [ru.andreymarkelov.atlas.plugins.prom-bitbucket-exporter [126](R 126.0)] osgi.wiring.package; (&(osgi.wiring.package=com.atlassian.bitbucket.dmz.permission)(version>=6.6.1)(version<=6.6.1)) Unresolved requirements: [[ru.andreymarkelov.atlas.plugins.prom-bitbucket-exporter [126](R 126.0)] osgi.wiring.package; (&(osgi.wiring.package=com.atlassian.bitbucket.dmz.permission)(version>=6.6.1)(version<=6.6.1))].  This error usually occurs when your plugin imports a package from another bundle with a specific version constraint and either the bundle providing that package doesn't meet those version constraints, or there is no bundle available that provides the specified package. For more details on how to fix this, see https://developer.atlassian.com/x/mQAN
2019-09-05 07:22:17,322 WARN  [spring-startup]  c.a.plugin.impl.AbstractPlugin Unable to enable plugin 'ru.andreymarkelov.atlas.plugins.prom-bitbucket-exporter'
Thomas

On it
Will fix ASAP
чт, 5 сент. 2019 г. в 8:23, webtomyfd<EMAIL_ADDRESS>
Hi,
thanks for this great plugin, ...but it stopped working with 6.6.1
error:
2019-09-05 07:22:17,322 ERROR [spring-startup]
c.a.plugin.osgi.factory.OsgiPlugin Detected an error (BundleException)
enabling the plugin
'ru.andreymarkelov.atlas.plugins.prom-bitbucket-exporter' : Unable to
resolve ru.andreymarkelov.atlas.plugins.prom-bitbucket-exporter [126](R
126.0): missing requirement
[ru.andreymarkelov.atlas.plugins.prom-bitbucket-exporter [126](R 126.0)]
osgi.wiring.package;
(&(osgi.wiring.package=com.atlassian.bitbucket.dmz.permission)(version>=6.6.1)(version<=6.6.1))
Unresolved requirements:
[[ru.andreymarkelov.atlas.plugins.prom-bitbucket-exporter [126](R 126.0)]
osgi.wiring.package;
(&(osgi.wiring.package=com.atlassian.bitbucket.dmz.permission)(version>=6.6.1)(version<=6.6.1))].
This error usually occurs when your plugin imports a package from another
bundle with a specific version constraint and either the bundle providing
that package doesn't meet those version constraints, or there is no bundle
available that provides the specified package. For more details on how to
fix this, see https://developer.atlassian.com/x/mQAN
2019-09-05 07:22:17,322 WARN [spring-startup]
c.a.plugin.impl.AbstractPlugin Unable to enable plugin
'ru.andreymarkelov.atlas.plugins.prom-bitbucket-exporter'
Thomas
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/AndreyVMarkelov/prom-bitbucket-exporter/issues/20?email_source=notifications&email_token=AAPXM4GSZZ342BEUBKKJGSTQICJVFA5CNFSM4ITZORKKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HJNWEKA,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAPXM4F33347SQY5B64AIULQICJVFANCNFSM4ITZORKA
.

--
-- Andrey Markelov

Done in version 1.0.12


bump react-split-pane version

this should fix issue #1352
Issue: #1352
What I did
Bump a version number
How to test
Run the storybook in IE11 and check that the side panel renders correctly

We have one more issue with react-split-pane:  #1465
should we consider it as well?

Consider closing it? What do you mean?


cant compile php 7.3.7 x86

when trying to build the x86 version of php 7.3.7 the file  https://dl.bintray.com/dfabric/apps-static/curl-static_7.64.1_linux_x86-64.tar.xz is downloaded and installed which is for 64bit os's , please compile for 86 and add to the repo for the SHA512SUMS file
the work around is to compile curl static locally and inject into the docker image before you manually kick off main.sh (in dev mode).

I understand the problem, I would like to be fixed upstream on Alpine but that's not that easy.
I think I figured out how to do, and will work on it and test it when I will have the time.


PTZ_CONTROL

I am using this integration in HOME ASSISTANT for 2 RLC-410W model cameras.
Entities for the 2 devices have been successfully created.
I wanted to insert zoom buttons in lovelace but from the developer test menu I can't get the cameras to accept them.
These are the test lines for the service
service: reolink_dev.ptz_control
data:
entity_id: camera.garden
command: ZOOMDEC
speed: 25
Surely I am wrong in something but at the moment I have only the doubt that the RLC-410W model does not exhibit the service. Unless some different settings to be made with its proprietary APP.
Thank you for your suggestions and I hope this report will improve the software

I'm very sure the RLC-410W has no PTZ controls and/or zoom.
More here.


ARROW-16467: [Python] Add helper function _exec_plan._filter_table to filter tables based on Expression

The function is focused on Tables, as it will be the foundation for Table.filter, but as the extra work was minimal I added support for Dataset too.

Does the exec plan already support tagging batches and reordering them when gathering into a table? I seem to recall that we do that for the Dataset to_table (but I don't know if this logic still lives in the scanner or has moved to exec plan)

cc @westonpace

Yes, to_table supports this and it looks like that is what is being used here so it should work.

What I observed from trying out this branch is that it does not preserve:
In [18]: table1 = pa.table({'a': [1, 2, 3, 4], 'b': ['a'] * 4})

In [19]: table2 = pa.table({'a': [1, 2, 3, 4], 'b': ['b'] * 4})

In [20]: table = pa.concat_tables([table1, table2])

In [21]: ep._filter_table(table, pc.field('a') == 1)
Out[21]:
pyarrow.Table
a: int64
b: string
----
a: [[1],[1]]
b: [["b"],["a"]]

In [22]: ep._filter_table(table, pc.field('a') == 1)
Out[22]:
pyarrow.Table
a: int64
b: string
----
a: [[1],[1]]
b: [["a"],["b"]]

But the current cython wrappers of the ExecPlan are not using a "to_table" method, it is using Table::FromRecordBatchReader, with a record batch generator created using MakeGeneratorReader, which explicitly says it does not preserve order:
https://github.com/apache/arrow/blob/5a4b3db396f88898917620de50863b6d3a477a7a/cpp/src/arrow/compute/exec/exec_plan.h#L440-L447
I see that we currently use a "sink" node as final output node, but there is also a "table_sink" node. That might simplify the code a bit to get a Table (without manually creating a record batch reader and creating a table from that), but  don't think that would help with the ordering? (at least in the code I also don't see any ordering handling for this sink)

For the dataset scanner, I think the reordering logic lives in AsyncScanner::ToTable() / AsyncTableAssemblyState, which uses the fragment index to put the EnumeratedRecordBatch objects in the correct order in the resulting vector of batches.

I see that we currently use a "sink" node as final output node, but there is also a "table_sink" node. That might simplify the code a bit to get a Table (without manually creating a record batch reader and creating a table from that), but don't think that would help with the ordering? (at least in the code I also don't see any ordering handling for this sink)

I tried and can confirm that using table_sink node doesn't help with preserving the order.

Given that preserving order in the proper way requires a non trivial amount of work from what I can see (not much of the required infrastructure is available outside of Datasets) I pushed a work-around in the current branch and I made https://issues.apache.org/jira/browse/ARROW-16518 to come up with a solution that works with threads too.

Yes, that will indeed require some non-trivial work in the engine. Leaving it as is for now is good for me!


lib: introduce fca a module for formal concept analysis

Building a FormalContext
We use the example from https://en.wikipedia.org/wiki/Formal_concept_analysis:
var fc = new FormalContext[Int, String]
fc.set_object_attributes(1, ["odd", "square"])
fc.set_object_attributes(2, ["even", "prime"])
fc.set_object_attributes(3, ["odd", "prime"])
fc.set_object_attributes(4, ["even", "composite", "square"])
fc.set_object_attributes(5, ["odd", "prime"])
fc.set_object_attributes(6, ["even", "composite"])
fc.set_object_attributes(7, ["odd", "prime"])
fc.set_object_attributes(8, ["even", "composite"])
fc.set_object_attributes(9, ["odd", "square", "composite"])
fc.set_object_attributes(10, ["even", "composite"])

Computing the set of FormalConcept
var concepts = fc.formal_concepts
for concept in concepts do
	print concept
end

Visualizing formal concept with ConceptLattice
var cl = new ConceptLattice[Int, String].from_concepts(concepts)
cl.show_dot

Signed-off-by: Alexandre Terrasa<EMAIL_ADDRESS>

Reroll: removed the main


fix: incorrect expectation api docs

Explanation
Fix an incorrect expectation api docs.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (a06d0eb) 79.51% compared to head (d750bdc) 79.51%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #833   +/-   ##
=======================================
  Coverage   79.51%   79.51%
=======================================
  Files         104      104
  Lines        3227     3227
=======================================
  Hits         2566     2566
  Misses        510      510
  Partials      151      151

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

@eddycharly can we improve this a little bit :)


Extend SplittingBAMIndexer to allow index creation while writing

a BAM file, like BAMIndexer in htsjdk.

@tomwhite added minor comments, otherwise looks good to me. I guess the idea is to write the index transparently when merging the BAM parts in ReadsSparkSink?

@AndreSchumacher the main driver for this was to make it possible to generate standard (.bai) indexes and splitting indexes at the same time. BuildBamIndex in GATK could be extended to do this for example.
I'm thinking it may also be useful to generate splitting indexes from BAMRecordWriter too, but this would be a follow-on issue.


Java 1.7 Dependency Missing on Fedora 28

I tried installing the google-cloud-sdk-app-engine-java package on Fedora 28, but one of the dependencies are java-1.7.0-openjdk-devel which is missing because it is no longer supported. The output I have is below.
$ sudo dnf install google-cloud-sdk-app-engine-java.noarch
Last metadata expiration check: 0:32:36 ago on Thu 06 Sep 2018 11:33:02 AM EDT.

We are working on a strategy to upgrade to newer versions of JDK. Please stand by.

...also this is app-engine not google-cloud-java libraries. app-engine java 7 is shutting down too.


FIX: act installation in CI/CD

Merging this, some spurious errors from non-working HTTP requests.


[django] expand tests to cover tastypie

This also corrects an issue with recursion behavior in transaction names, exhibited by standard tastypie URLs.
Fixes GH-940

breaking django changes out into https://github.com/getsentry/raven-python/pull/960 since I have no idea why the tests dont pass on Travis

@mitsuhiko @mattrobenolt one of you mind taking a quick pass on review here?


[edn/rtl] enable bit 2 of ERR_CODE

Bit 2 of the ERR_CODE is defined as an error bit that when set will cause a fatal error.
This bit is associated with the Output FIFO.
Fixes #16218.

Need to start again.


BigQuery Runner Extension EISDIR: Illegal operation on a directory, read

I have been working in the VS Code/GitLab environment for over six months and suddenly am receiving an error in VS Code: EISDIR: Illegal operation on a directory, read. I have worked for hours trying to resolve this error and haven't been able to resolve it. Any assistance is appreciated.

Does this error occur when I run the query? If you can give me more details about the circumstances under which the error occurs, I may be able to help.

It happens after opening VS Code and clicking on a .bqsql file. I don't have to try to run it to get the error, but I also get the error when I try to run a .bqsql file.
Python is installed and operating correctly.
Eva
Sent from my T-Mobile 5G Device
Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: Daisuke Mino @.>
Sent: Saturday, January 13, 2024 10:12:35 AM
To: minodisk/bigquery-runner @.>
Cc: Trevathan, Eva @.>; Author @.>
Subject: Re: [minodisk/bigquery-runner] BigQuery Runner Extension EISDIR: Illegal operation on a directory, read (Issue #51)
Does this error occur when I run the query? If you can give me more details about the circumstances under which the error occurs, I may be able to help. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving
Does this error occur when I run the query? If you can give me more details about the circumstances under which the error occurs, I may be able to help.
—
Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https://github.com/minodisk/bigquery-runner/issues/51*issuecomment-1890558678__;Iw!!POAF-4Fp!5J6o4UBMM6WmCGEWuy8SlINchB46kCOAIXuBO1uI_60sZMYJu5V-AsETBtljFLny6-KiiEvrP0r0MozD7pbAcaDoD7Z_v48$, or unsubscribehttps://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/AYMGFRFHUDKXA7EAK6RBH2LYOKW7HAVCNFSM6AAAAABBXNZ5AOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJQGU2TQNRXHA__;!!POAF-4Fp!5J6o4UBMM6WmCGEWuy8SlINchB46kCOAIXuBO1uI_60sZMYJu5V-AsETBtljFLny6-KiiEvrP0r0MozD7pbAcaDoM1xUfAw$.
You are receiving this because you authored the thread.Message ID: @.***>

@etrevathan
Would the same error occur after uninstalling BigQuery Runner?

Yes, it occurs after uninstalling BigQuery Runner. It also occurs after obtaining a different VM and setting everything up from scratch.

@etrevathan
It seems that BigQuery Runner is not the cause of the error then. I'm afraid I can't help you.

I don't get the error until I get to the step where I install the BigQuery Runner extension, so I guess I'll just find a replacement for it.

Unfortunately, that sounds better for you.


Fix path with white space issues for cocos 2.1 parser test

This is because the server to take to the file name didn't handle with white space.
Not a test case problem.
On the web is to support white space as the file name.


[SPARK-40376][PYTHON] Avoid Numpy deprecation warning

What changes were proposed in this pull request?
Use bool instead of np.bool as np.bool will be deprecated (see: https://numpy.org/devdocs/release/1.20.0-notes.html#deprecations)
Using np.bool generates this warning:
UserWarning: toPandas attempted Arrow optimization because 'spark.sql.execution.arrow.pyspark.enabled' is set to true, but has reached the error below and can not continue. Note that 'spark.sql.execution.arrow.pyspark.fallback.enabled' does not have an effect on failures in the middle of computation.
3070E                     `np.bool` is a deprecated alias for the builtin `bool`. To silence this warning, use `bool` by itself. Doing this will not modify any behavior and is safe. If you specifically wanted the numpy scalar type, use `np.bool_` here.
3071E                   Deprecated in NumPy 1.20; for more details and guidance: https://numpy.org/devdocs/release/1.20.0-notes.html#deprecations

Why are the changes needed?
Deprecation soon: https://numpy.org/devdocs/release/1.20.0-notes.html#deprecations.
Does this PR introduce any user-facing change?
The warning will be suppressed
How was this patch tested?
Existing tests should suffice.

Seems fine, though is this just an alias for previous versions of numpy that are currently supported too?

Correct.

Can we add a [PYTHON] tag for the title ?
Also check the https://spark.apache.org/contributing.html out when you find some time.

Would you check the "Workflow run detection failed" in https://github.com/apache/spark/pull/37817/checks?check_run_id=8226916282 for enabling Github Actions ??

I think How was this patch tested? in the PR description should contain how do we verify this patch within Apache Spark code base.
In this case, we can just simply mention like: Using the existing test for example.

The PR description usually started from "What changes were proposed in this pull request?"
So, can we put the description
"""
Using np.bool generates this warning:
UserWarning: toPandas attempted Arrow optimization because 'spark.sql.execution.arrow.pyspark.enabled' is set to true, but has reached the error below and can not continue. Note that 'spark.sql.execution.arrow.pyspark.fallback.enabled' does not have an effect on failures in the middle of computation.
3070E                     `np.bool` is a deprecated alias for the builtin `bool`. To silence this warning, use `bool` by itself. Doing this will not modify any behavior and is safe. If you specifically wanted the numpy scalar type, use `np.bool_` here.
3071E                   Deprecated in NumPy 1.20; for more details and guidance: https://numpy.org/devdocs/release/1.20.0-notes.html#deprecations

"""
into "What changes were proposed in this pull request?" ??
e.g.
What changes were proposed in this pull request?
Using np.bool generates this warning:
UserWarning: toPandas attempted Arrow optimization because 'spark.sql.execution.arrow.pyspark.enabled' is set to true, but has reached the error below and can not continue. Note that 'spark.sql.execution.arrow.pyspark.fallback.enabled' does not have an effect on failures in the middle of computation.
3070E                     `np.bool` is a deprecated alias for the builtin `bool`. To silence this warning, use `bool` by itself. Doing this will not modify any behavior and is safe. If you specifically wanted the numpy scalar type, use `np.bool_` here.
3071E                   Deprecated in NumPy 1.20; for more details and guidance: https://numpy.org/devdocs/release/1.20.0-notes.html#deprecations

Use bool instead of np.bool as np.bool will be deprecated (see: https://numpy.org/devdocs/release/1.20.0-notes.html#deprecations)
Why are the changes needed?
...

Looks fine otherwise, thanks for the your first contribution!

@itholic

Can we add a [PYTHON] tag for the title ?

Done

Also check the https://spark.apache.org/contributing.html out when you find some time.

I am sorry, you are right.

Would you check the "Workflow run detection failed" in https://github.com/apache/spark/pull/37817/checks?check_run_id=8226916282 for enabling Github Actions ??

I did that and the build in my folk went through: https://github.com/ELHoussineT/spark/actions/workflows/build_main.yml
But the actions in the PR are still red, thoughts?

So, can we put the description into "What changes were proposed in this pull request?" ??

Done

Thanks for the your first contribution to Apache Spark!

Its a tine one! You're welcome :)

Hm, try pushing an empty commit?

Can one of the admins verify this patch?

Oh, remove the type ignore comment:
annotations failed mypy checks:
python/pyspark/sql/pandas/conversion.py:298: error: unused "type: ignore" comment
Found 1 error in 1 file (checked 339 source files)

Ping @ELHoussineT

@srowen Sorry for the late reply.
Updated, let's see if it will go through.

Merged to master

Cool !

Hello all. Is this only going to be released in PySpark 3.4?
I looked at the branch-3.3 code and failed to see this change, if I saw correctly.
Thanks

It's in 3.4, not 3.3, yes: https://github.com/apache/spark/blob/v3.4.0-rc1/python/pyspark/sql/pandas/conversion.py#L301
See the JIRA

@srowen: Although this is causing an issue:
If you try to build your own docker image of Spark including pyspark while trying to be compliant with Databricks you will observe that Databricks Runtime 12.1 and 12.2(which is currently in beta), both support officially until Spark 3.3.1 (while current version is 3.3.2).
Actually all of the LTS versions in the support matrix are not EOLed and since numpy 1.20.0 was released in 01/2021, which means that most spark compliant versions carry this bug. If you try to use Pandas by using toPandas() you end up with the numpy error, consequently being blocked from upgrading your spark versions.
Is there any chance of back-porting this commit into previous pyspark versions?

This is just a deprecation warning, not an error, right? I don't see a particular urgency here.
I don't think this is related to Databricks, particularly, either - Databricks can do what it likes with patches, etc. It will have a runtime based on 3.4 shortly after it's released.

Hi @srowen,
Thank you for your very prompt reply.
You are not correct about the error, after 1.20.0 it creates an attribute error
          if attr in __former_attrs__:
>           raise AttributeError(__former_attrs__[attr])
E           AttributeError: module 'numpy' has no attribute 'bool'.
E           `np.bool` was a deprecated alias for the builtin `bool`. To avoid this error in existing code, use `bool` by itself. Doing this will not modify any behavior and is safe. If you specifically wanted the numpy scalar type, use `np.bool_` here.
E           The aliases was originally deprecated in NumPy 1.20; for more details and guidance see the original release note at:
E               https://numpy.org/devdocs/release/1.20.0-notes.html#deprecations

/usr/local/lib/python3.9/site-packages/numpy/__init__.py:305: AttributeError

This is the end of an error, coming after calling the function toPandas() from my tests:
/usr/local/lib/python3.9/site-packages/<my-pkg>/unit/test_case_runner.py:26: in run_test
    self.assert_df_are_equal(expected_df, actual)
/usr/local/lib/python3.9/site-packages/<my-pkg>/unit/test_case_runner.py:58: in assert_df_are_equal
    self.handler.compare_df(result, expected, config=self.compare_config)
/usr/local/lib/python3.9/site-packages/<my-pkg>/spark_test_handler.py:38: in compare_df
    actual_pd = actual.toPandas().sort_values(by=sort_columns, ignore_index=True)
/usr/local/lib/python3.9/site-packages/pyspark/sql/pandas/conversion.py:216: in toPandas
    pandas_type = PandasConversionMixin._to_corrected_pandas_type(field.dataType)
/usr/local/lib/python3.9/site-packages/pyspark/sql/pandas/conversion.py:298: in _to_corrected_pandas_type
    return np.bool  # type: ignore[attr-defined]

And the error does not come from the numpy in the system but by the numpy inside pyspark
I agree about the comments on databricks but as shown above this does not work on Spark 3.3.1 independently if you want to be compliant with Databricks.

Well, I think we're talking about numpy 1.20 here, not >1.20. You're correct that you therefore would not use the latest versions of numpy with Spark 3.3, but would work with 3.4. If that presents a significant problem during the lifetime of Spark 3.3, sure I think that's a decent argument to back-port. Do you know what version of numpy actually removed this ? if it not a recent removal, yeah I think we should back port this simple change

Yes we agree that users can limit their numpy system installation to < 1.20.0, if they use Spark 3.3
I will have to check and test the different versions but I believe according to the notes from numpy should be from the numpy 1.20.0 according to 1,2. I will have to verify it to be sure though.
Well numpy 1.20.0 was released in 01/2021 which makes it 2 year old but the final decision is up to you.

Looks like 1.22 removed it actually. That's still not recent. Yeah I think this is worth back porting

Also merged to 3.3

Thank you @srowen, really appreciated

Also merged to 3.3

Thank you so much! Here I was assuming I would pick up this thread on monday but you delivered it 😄
Cheers


ensure gossip ordering required for fast topology convergence

Fixes #1793.
NB: this is branched off #1832.

Replaced by #1899.


Want place to dump data, and modeling ideas

There are many inbound suggestions for data to include, and for modeling (feature vectors, AI/ML algs).
TODO: find a way

Solution: In main README, link to two new sub-readmes, one for data and one for modeling. It currently looks like:

Future Accuracy Improvements
We want to lower the friction for users getting good results. The following may go into future READMEs.

More data sources
Modeling approaches


Rollback NU5 testnet 1, and set consensus parameters for testnet 2

Motivation
As part of the zcashd mainnet support release, their developers want to change the Orchard circuit on both mainnet and testnet. So we need to rollback testnet to before NU5 activation.
Specifications
https://zips.z.cash/zip-0252
Tasks
Consensus parameters:

change the NU5 testnet consensus branch ID
change the NU5 testnet activation height

Zebra-specific:

do a testnet rollback by incrementing Zebra's database version
update Zebra's current network protocol version - the version scheme has changed
#2982

Zebra-specific test changes:

update NU5 and Orchard tests, if needed, including:

NU5 block test vectors from the first testnet activation
NU5 Orchard shielded data test vectors from the first testnet activation
any other tests that fail

Note that the ZIP-221 history tree, which is stored in state, commits to the consensus branch ID: https://zips.z.cash/zip-0221#tree-node-specification
I guess we'd need to regenerate the state anyway for the rollback, but maybe that warrants also bumping the database version?

Note that the ZIP-221 history tree, which is stored in state, commits to the consensus branch ID: https://zips.z.cash/zip-0221#tree-node-specification
I guess we'd need to regenerate the state anyway for the rollback, but maybe that warrants also bumping the database version?

I'll update this part of the ticket to say "database version":

do a testnet rollback by incrementing Zebra's state version

Every v5 transaction also commits to the consensus branch ID.

I just added "zebra-specific test changes" to this ticket, because the testnet fixes will break some test vectors from the first NU5 testnet activation.
Other tests might also have changed.


[bug] [v2] undo and redo shortcuts don't work in popular editor on MacOS

Describe the bug
In tauri v2-beta, the undo and redo shortcuts don't work in popular editor on MacOS. (Focus the editor, then press enter key, then undo, you will see the bug without any error message.)
I also test on windows 10,  they work fine. Then I test on MacOS with lastest tauri v1, they also work fine.

ps: I notice this issue #9426, but it doesn't help for me.

Here is the test demo.  https://github.com/percy507/test-tauri-v2/tree/undo-redo-donot-work-in-editor
# v2-beta on MacOS
textarea                works
contenteditable         works
the rest editors        doesn't work

Reproduction
https://github.com/percy507/test-tauri-v2/tree/undo-redo-donot-work-in-editor
Expected behavior
No response
Full tauri info output
[✔] Environment
    - OS: Mac OS 13.2.1 X64
    ✔ Xcode Command Line Tools: installed
    ✔ rustc: 1.75.0 (82e1608df 2023-12-21)
    ✔ cargo: 1.75.0 (1d8b05cdd 2023-11-20)
    ✔ rustup: 1.26.0 (5af9b9484 2023-04-05)
    ✔ Rust toolchain: stable-aarch64-apple-darwin (default)
    - node: 20.7.0
    - pnpm: 8.3.1
    - yarn: 1.22.21
    - npm: 10.1.0

[-] Packages
    - tauri [RUST]: 2.0.0-beta.22
    - tauri-build [RUST]: 2.0.0-beta.17
    - wry [RUST]: 0.40.1
    - tao [RUST]: 0.28.1
    - @tauri-apps/api [NPM]: 2.0.0-beta.13
    - @tauri-apps/cli [NPM]: 2.0.0-beta.20

[-] App
    - build-type: bundle
    - CSP: unset
    - frontendDist: ../dist
    - devUrl: http://localhost:1420/
    - framework: React
    - bundler: Vite

Stack trace
No response
Additional context
No response

Tauri with unstable feature enabled will create a webview as child and fall into #9426.

True. I remove unstable  feature and refactor the related code. The problem seems been resolved.


Remove unused mypy type ignore

Change Summary
The typechecking job fails due to an unused type: ignore[...]. See: https://github.com/pydantic/pydantic/actions/runs/11446111308/job/31844612840?pr=10676
This PR removes this comment.
Related issue number

Checklist

[x] The pull request title is a good summary of the changes - it will be used in the changelog
[ ] Unit tests for the changes exist
[x] Tests pass on CI
[ ] Documentation reflects the changes where applicable
[x] My PR is ready to review, please add a comment including the phrase "please review" to assign reviewers

please review

Ok so turns out the test is still flaky. It was enabled today in https://github.com/pydantic/pydantic/pull/10671. Could you please instead re-add the same condition here? I'll debug in a separate PR.

@Viicos Okay, that explains why it suddenly appeared again. Changed as requested.


Update Reason
The model is neither used in a standard document or triangle document, which indicates that the model is not used anymore.
If there are still reasons to still have this model in the repository, please provide a short rationale in the comments. If not, please indicate with a "+1" that you are OK with deprecating the model.
Deprecating a model means, that it will be removed after two Tractus-X releases from the repository. For details, please refer to the GOVERNANCE process.
MS1 Criteria

[ ] The model that should be deprecated exists and is not deprecated already
[ ] The respective model does not affect existing use cases (aspect is either used in higher versions or replaced by a different aspect)
[ ] A shared aspect, which will be deprecated, is not used by any released aspect model

@catroest please check this request

@bs-jokri because this is the only version, please let it be and do not deprecate

Model Deprecation not required.


TensorFlow 0.10.0rc fails to detects CUDA device on my Macbook Pro (with nvidia 750M graphic card)

NOTE: Only file GitHub issues for bugs and feature requests.  All other topics will be closed.
For general support from the community, see StackOverflow.
To make bugs and feature requests more easy to find and organize, we close issues that are deemed
out of scope for GitHub Issues and point people to StackOverflow.
For bugs or installation issues, please provide the following information.
The more information you provide, the more easily we will be able to offer
help and advice.
What related GitHub issues or StackOverflow threads have you found by searching the web for your problem?

This one is related, but it is for Ubuntu
https://github.com/tensorflow/tensorflow/issues/2882
This one is related also
https://github.com/tensorflow/tensorflow/issues/2940#issuecomment-238952433

Environment info
Operating System: mac os 10.12
Installed version of CUDA and cuDNN:
(please attach the output of ls -l /path/to/cuda/lib/libcud*):
ls -l /usr/local/cuda/lib/libcud*
-rwxr-xr-x@ 1 root   admin   8.1K Sep 28 14:39 /usr/local/cuda/lib/libcuda.1.dylib*
-rwxr-xr-x@ 1 root   wheel   8.1K Apr 13 08:02 /usr/local/cuda/lib/libcuda.dylib*
lrwxr-xr-x@ 1 root   wheel    45B Apr 13 08:03 /usr/local/cuda/lib/libcudadevrt.a@ -> /Developer/NVIDIA/CUDA-7.5/lib/libcudadevrt.a
lrwxr-xr-x@ 1 root   wheel    50B Apr 13 08:03 /usr/local/cuda/lib/libcudart.7.5.dylib@ -> /Developer/NVIDIA/CUDA-7.5/lib/libcudart.7.5.dylib
lrwxr-xr-x@ 1 root   wheel    46B Apr 13 08:03 /usr/local/cuda/lib/libcudart.dylib@ -> /Developer/NVIDIA/CUDA-7.5/lib/libcudart.dylib
lrwxr-xr-x@ 1 root   wheel    49B Apr 13 08:03 /usr/local/cuda/lib/libcudart_static.a@ -> /Developer/NVIDIA/CUDA-7.5/lib/libcudart_static.a
-rwxr-xr-x@ 1 qdang  staff    56M Apr 23 02:19 /usr/local/cuda/lib/libcudnn.5.dylib*
lrwxr-xr-x@ 1 qdang  staff    16B Apr 23 04:10 /usr/local/cuda/lib/libcudnn.dylib@ -> libcudnn.5.dylib
-rw-r--r--@ 1 qdang  staff    53M Apr 23 02:19 /usr/local/cuda/lib/libcudnn_static.a

If installed from binary pip package, provide:

A link to the pip package you installed:
TF_BINARY_URL=https://storage.googleapis.com/tensorflow/mac/gpu/tensorflow-0.10.0-py2-none-any.whl
The output from python -c "import tensorflow; print(tensorflow.__version__)".

python -c "import tensorflow; print(tensorflow.__version__)"
I tensorflow/stream_executor/dso_loader.cc:108] successfully opened CUDA library libcublas.dylib locally
I tensorflow/stream_executor/dso_loader.cc:108] successfully opened CUDA library libcudnn.dylib locally
I tensorflow/stream_executor/dso_loader.cc:108] successfully opened CUDA library libcufft.dylib locally
I tensorflow/stream_executor/dso_loader.cc:108] successfully opened CUDA library libcuda.1.dylib locally
I tensorflow/stream_executor/dso_loader.cc:108] successfully opened CUDA library libcurand.dylib locally
0.10.0

If installed from source, provide

The commit hash (git rev-parse HEAD)
The output of bazel version

If possible, provide a minimal reproducible example (We usually don't have time to read hundreds of lines of your code)
I just run the iris_monitor.py example at https://github.com/tensorflow/tensorflow/tree/master/tensorflow/examples/tutorials/monitors and got the error
I tensorflow/stream_executor/dso_loader.cc:108] successfully opened CUDA library libcublas.dylib locally
I tensorflow/stream_executor/dso_loader.cc:108] successfully opened CUDA library libcudnn.dylib locally
I tensorflow/stream_executor/dso_loader.cc:108] successfully opened CUDA library libcufft.dylib locally
I tensorflow/stream_executor/dso_loader.cc:108] successfully opened CUDA library libcuda.1.dylib locally
I tensorflow/stream_executor/dso_loader.cc:108] successfully opened CUDA library libcurand.dylib locally
E tensorflow/stream_executor/cuda/cuda_driver.cc:491] failed call to cuInit: CUDA_ERROR_NO_DEVICE

What other attempted solutions have you tried?
I ran torch on my GPU successfully before, so I could confirm that GPU computing is possible on my computer.
Logs or other output that would be helpful
(If logs are large, please upload as attachment or provide link).

@vinhqdang is there any other information returned in the failure?
Based on #255, you might try running the device query binary from nvidia's samples, to see whether the GPU is properly detected.

Here is the nvcc I have
nvcc --version

nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2015 NVIDIA Corporation
Built on Mon_Apr_11_13:23:40_CDT_2016
Cuda compilation tools, release 7.5, V7.5.26

Oops, I think the problem is: I am running Mac OS 10.12 with Xcode 8, clang 8 and CUDA 8.0, but CUDA 8.0 does not support clang 8
/Developer/NVIDIA/CUDA-8.0/samples/1_Utilities/deviceQuery$ make

/Developer/NVIDIA/CUDA-8.0/bin/nvcc -ccbin clang++ -I../../common/inc  -m64  -Xcompiler -arch -Xcompiler x86_64  -gencode arch=compute_20,code=sm_20 -gencode arch=compute_30,code=sm_30 -gencode arch=compute_35,code=sm_35 -gencode arch=compute_37,code=sm_37 -gencode arch=compute_50,code=sm_50 -gencode arch=compute_52,code=sm_52 -gencode arch=compute_60,code=sm_60 -gencode arch=compute_60,code=compute_60 -o deviceQuery.o -c deviceQuery.cpp
nvcc warning : The 'compute_20', 'sm_20', and 'sm_21' architectures are deprecated, and may be removed in a future release (Use -Wno-deprecated-gpu-targets to suppress warning).
**nvcc fatal   : The version ('80000') of the host compiler ('Apple clang') is not supported**
make: *** [deviceQuery.o] Error 1

so, How to solve? I also have this problem? now, I run the mac os and Xcode8, cuda 7.5

@wwxFromTju Have you followed the instructions here:
https://www.tensorflow.org/versions/r0.11/get_started/os_setup.html#prepare-environment-for-mac-os-x
Note the following section:

If you want to compile tensorflow and have the XCode 7.3 installed, note that Xcode 7.3 is not yet compatible with CUDA 7.5. You will need to download Xcode 7.2 and select it as your default:
$ sudo xcode-select -s /Application/Xcode-7.2/Xcode.app

I am not an expert on the mac environment, but perhaps you can try XCode 7.2?

Closing automatically due to lack of recent activity. Please reopen when further information becomes available. Thank you.


fix(resolve): prioritize main field over mainFields for requires

Description

When a require is performed the modules resolution currently prioritizes the mainFields option over the fact that a require has been used, this (especially given the default mainFields value) can lead to requires being resolved to browser entries instead of a potential cjs module entry. This PR addresses this by priotizing a potential main field over the mainField.

Details on how we encountered this issue
This was encountered as an issue when trying to run Remix code inside the workerd runtime via the environments API, there we encountered situations in which some modules imported via require would require packages but would receive esm entries instead of cjs ones, causing the following issue:
TypeError: Cannot use require() to import an ES Module.

This happened when
react-router-dom (package.json) was being required from @remix-run/react (code)
by adding some ad-hoc hacks to make the above work this issue would show up again
for react-router (packae.json) required from react-router-dom itself (code)
by also hacking the above we'd re-encounter the issue with:
@remix-run/router (package.json) being required from react-router (code)
and so on...

I'm not sure if this is correct. require() if building for browsers should use the browser entry if so. Bundlers can also handle if require resolves to an ESM file. Is there a specific package this is trying to fix? And could it use the exports field with the require condition instead? (if needed)

I'm not sure if this is correct. require() if building for browsers should use the browser entry if so. Bundlers can also handle if require resolves to an ESM file. Is there a specific package this is trying to fix? And could it use the exports field with the require condition instead? (if needed)

@bluwy I've just updated the PR's description with the package(s) that I was having issues with 👍
Also to give you more context, the whole thing here is that I'm trying to run a Remix application inside workerd via the Vite Environment API without prebundling the react code.

I'm curious how this happens in the first place. According to https://github.com/vitejs/vite/blob/c373251123ffbfddf2f703b6a62a5d9b1a03db67/packages/vite/src/node/ssr/fetchModule.ts#L39-L48 Only main field should be used when resolving bare imports. If it's not a bare import (e.g. it's in noExternal which Vite rewrites to a different path. Or a plugin resolves it to something else. Or perhaps you're testing the packages linked locally?), then Vite will process these packages, however Vite won't handle CJS and require() correctly.
In that case, I'd recommend passing the packages to resolve.external in the environment api. But I guess with the workerd environment, it's not possible to do so? Then prebundling seems like the only solution here 🤔

This happened when
react-router-dom (package.json) was being required from @remix-run/react (code)

If the problem started from this, would it be possible for remix-run/react to import react-router-dom first?

Is this PR still needed?

Is this PR still needed?

Thanks for the ping @bluwy 🙂
This is probably not needed, let me close the PR and we can hopefully always revisit it at some point if needed 🙂


Ability to use PUT requests for bot stats

AFAIK BotBlock will only allow POST requests for bot stats. dlist.gg uses PUT requests, resulting in a 405: Method not allowed.

I'm thinking an api_post_method optional field in the botlist JSON should be fine? ATM the stats endpoint is api_post, and we're providing an HTTP method for it.
On one hand, the field names won't make much sense. On the other hand, no new name needs to be made and other JSON files do not need to be updated.

Agreed with that approach, seems like the best way to do it such that everything remains backwards compatible.
Just needs to be added in here: https://github.com/botblock/api-worker/blob/5c5469547e9f34d548fad0f2e70ebdb2759b6cc5/src/routes/count.js#L69