[Merged by Bors] - chore: cleanup for mathport update

add_decl_doc already exists in core (this declaration was just shadowing it)
setup_tactic_parser is not planned for porting; the nearest equivalent is nothing at all
mk_simp_attribute can mostly be aligned to register_simp_attr, and the remaining part (the := ids,*) can't be supported at all and will give a suitable port message in mathport
std_next alignment consistently gives a stack overflow when porting on my machine; I think this is a recent regression (possibly leanprover-community/mathport#192?) but this is a quick fix since this function doesn't matter too much.

bors merge

alignment consistently gives a stack overflow when porting on my machine; I think this is a recent regression (possibly https://github.com/leanprover-community/mathport/issues/192?)

I don't think this is related to 192.  That issue is about binported type class instances that break Lean 4.  Those typically don't cause stack overflows.

Just to clarify, the issue that happens is that when synport is translating a theorem (the binport part, which translates the environment), it first tries to use the given definition, then stubs the value and then the type if it hits defeq issues.


Missing network passphrase in example compose file

When trying to start docker compose, I was seeing the following in the logs...

stellar-horizon-postgres_1  | 	    AS $$ SELECT $1 $$
stellar-horizon_1           | 2019/04/26 11:09:11 Invalid config: network-passphrase is blank. Please specify --network-passphrase on the command line or set the NETWORK_PASSPHRASE environment variable.
docker-stellar-horizon_stellar-horizon_1 exited with code 1

If I add - NETWORK_PASSPHRASE=Public Global Stellar Network ; September 2015 to the horizon ENV...
 stellar-horizon:
    image: satoshipay/stellar-horizon:0.17.2
    restart: on-failure
    ports:
    - 8000:8000
    environment:
      - DATABASE_URL=postgres://postgres@stellar-horizon-postgres/stellar-horizon?sslmode=disable
      - STELLAR_CORE_DATABASE_URL=postgres://postgres@stellar-core-postgres/stellar-core?sslmode=disable
      - STELLAR_CORE_URL=http://stellar-core:11626
      - NETWORK_PASSPHRASE=Public Global Stellar Network ; September 2015
      - INGEST=true

and now I can access the server on http://localhost:8000/

How did you provided password for connection to Horizon?  From where it takes password?
I installed postgres on local Linux and disabled both dockers that run db for core and for horizon. Instead of that I point both of them to my local db. The core is connecting to db and Horizon screams that connection failed due to password auth failed.
This is how the end of my .yml file looks like. So it is not clear from where Horizon takes password for its db.
stellar-horizon:
image: satoshipay/stellar-horizon:0.17.2
restart: on-failure
ports:
- 8000:8000
environment:
- DATABASE_URL=postgres://postgres@<IP_ADDRESS>/stellar_horizon?sslmode=disable
- STELLAR_CORE_DATABASE_URL=postgres://postgres@<IP_ADDRESS>/stellar_core?sslmode=disable
- STELLAR_CORE_URL=http://stellar-core:11626
- INGEST=true
- NETWORK_PASSPHRASE=Public Global Stellar Network ; September 2015
This is log i'm getting
root@virtualserver01:~# docker-compose -f /mnt/xvdc/github/docker-stellar-horizon/conf_horizon_docker-compose_extdb.yml up
Starting docker-stellar-horizon_stellar-core_1    ... done
Starting docker-stellar-horizon_stellar-horizon_1 ... done
Attaching to docker-stellar-horizon_stellar-horizon_1, docker-stellar-horizon_stellar-core_1
stellar-horizon_1  | Initializing Horizon database...
stellar-horizon_1  | 2019/09/17 00:03:39 connect failed: pq: password authentication failed for user "postgres"
stellar-horizon_1  | Horizon database initialization failed (possibly because it has been done before)
stellar-horizon_1  | 2019/09/17 00:03:39 pq: password authentication failed for user "postgres"
stellar-core_1     | Core db has already been initialized.
stellar-core_1     | Not initializing history archives (set INITIALIZE_HISTORY_ARCHIVES=true if you want to initialize them).
stellar-core_1     | Using DEPRECATED command-line syntax.
stellar-core_1     | Please refer to documentation for new syntax.
stellar-core_1     |
stellar-core_1     | 2019-09-17T00:03:41.160  [default INFO] Assigning calculated value of 1 to FAILURE_SAFETY
stellar-core_1     | 2019-09-17T00:03:41.165 GC2LC [default INFO] Starting stellar-core v10.2.0
stellar-core_1     | 2019-09-17T00:03:41.166 GC2LC [Database INFO] Connecting to: postgresql://dbname=stellar_core user=postgres password=******** host=<IP_ADDRESS>
stellar-core_1     | 2019-09-17T00:03:41.170 GC2LC [SCP INFO] LocalNode::LocalNode@GC2LC qSet: 1f303f
stellar-core_1     | 2019-09-17T00:03:41.170 GC2LC [default INFO] Listening on <IP_ADDRESS>:11626 for HTTP requests


vscode: 1.57.1 -> 1.58.0

Motivation for this change
Upgrades vscode from 1.57.1 to 1.58.0
This PR was automatically generated by nixpkgs-upkeep.

CI workflow that created this PR.
Internal tag: f62c33ce6af11035e350e35cf334e31a.

Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 129893 at d47d4971 run on aarch64-linux 1

2 packages built successfully:

vscode
vscode-with-extensions

VS Code has a native Apple Silicon version. Is there any plan to add support for that?

VS Code has a native Apple Silicon version. Is there any plan to add support for that?

Yeah that would be nice, perhaps another pr could add it to the derivation. I don't have an m1 to test on sadly

I've created #129969 which adds arm64-darwin support.


XML-RPC localization

Looking at libraries/xmlrpc, I see that it has a show_error early on, which should be left alone, but then a number of subsequent error mesages that could profit from localization with language settings. It looks like the XML_RPC_Response messages make good candidates for localization, but the error codes need to be preserved because they are part of the XML response.
Does this sound worthy?
@zhanghongyi You were proposing some language settings enhancements earlier; if this issue is deemed deserving, it could be a good one for you to tackle :)

@jim-parry Thanks for pinging me. Your idea suggests a better candidate for localization than mine. If this sounds a worthwhile thing to do, I am always willing to help :)

Surely a better candidate than @zhanghongyi's suggestions so far, indeed.
Still, translated error messages are supposed to be such that may end up being displayed to end users and I'd argue this isn't the case here. We're talking about a communication protocol that and end user shouldn't even know that you're using XML-RPC in the first place.

True ... but would the same not apply to the FTP language settings?
Applying language settings inside the XMLRPC libraries would clean them up, improving readability.
Just a thought :-/

Yep, same goes for FTP.
Do you mean that the FTP library has translated error messages? Those haven't been introduced on my watch. :D

The FTP library does have translated error messages, yes.
Consistency would suggest they be treated the same, either removing that from the FTP library, or introducing it to the XMLRPC libraries.

Well, you know my stance on obsession with consistency, but if I had to choose between the two, I'd remove the translations from CI_FTP.

I have raised a question on the forum to try to gauge the usage level and interest in this amongst the community. They might not even care, in which it can wait for later :)

Linking the forum thread here: http://forum.codeigniter.com/thread-63173.html
However, I'd expect either no replies at all or "sure, we always want more stuff" kind of posts, which isn't really useful feedback. :/

I agree ... we'll see if anyone cares about the issue one way or the other :-/


Convert "beta" endpoint to React

Original Description
We'd like to move towards a React-based frontend for MDN, but we need to figure out how to get there.
I'm filing this bug to track some experimental work we'll do to figure out whether we can incrementally convert Kuma to use React or if we need to start from scratch.
This experimental work will probably look like this:

Create a new Kuma endpoint en-US/beta/ that does exactly the same thing as en-US/docs/ (but that only works on the staging server and is never visible to end users).

Modify that new endpoint so that it uses React in some small way (like displaying the MDN logo). As part of this we'll also set up the webpack/babel toolchain, and get flow and jest snapshot tests working. Then we'll measure the performance of this new part-React, part-jQuery page and compare it to the existing /docs endpoint to get baseline data on the performance impact of adding React. (We'll have to decide whether to use React libraries from a CDN or not)

Do more substantial work with React, perhaps replacing the navigation header at the top of the page, and removing the jQueryUI library that it depends on. And see what the performance impact of that is.

Attempt to set up client-side navigation (possibly using react-router) to see how fast we can load new documents when we don't have to do a complete page load.

Investigate server-side rendering of our React content to see what the performance impact of that is and to figure out how to do that for both the logged-out and the logged-in case.

Original report
https://bugzilla.mozilla.org/show_bug.cgi?id=1525719

Bug 1525719 is roughly equivalent to the Kuma.Next epic. So all of my tasks this sprint are part of this one bug. But We don't need a separate issue for this because, https://github.com/mdn/sprints/issues/766 is this issue. So I'm going to close it.


Test the invoke transaction with a cairo1 contract declared with declarev2

Test the invoke transaction with a cairo1 contract declared with declarev2
Description
Partially closes #612 and also includes some fixes:

Cairo1 contracts now can be deployed with the Deploy transaction
Invoke::execute() now takes a remaining_gas parameter for setting ExecutionEntryPoint::initial_gas
The deprecated call_contract syscall now uses a INITIAL_GAS_COST constant for its ExecuteEntryPoint::initial_gas following the direction of cairo-lang and the blockifier.

Checklist

[x] Linked to Github Issue

I added a remaining_gas parameter to the invoke's execute() like the declarev2's but now after merging I saw that it was removed from the declare and instead used the INITIAL_GAS_COST constant. Should I leave it like it is now or change to use the constant? cc @juanbono

I also have some doubts about the expected transaction info, after merging with main it changed many things of the result info that I don't understand yet (like ExecutionResources) so I just matched with what the test was giving me to make it pass

Codecov Report

Merging #660 (a23eea9) into main (3efd683) will increase coverage by 0.01%.
The diff coverage is 100.00%.

:exclamation: Current head a23eea9 differs from pull request most recent head 403e069. Consider uploading reports for the commit 403e069 to get more accurate results

@@            Coverage Diff             @@
##             main     #660      +/-   ##
==========================================
+ Coverage   92.29%   92.30%   +0.01%
==========================================
  Files          51       51
  Lines       10561    10577      +16
==========================================
+ Hits         9747     9763      +16
  Misses        814      814

Impacted Files
Coverage Δ

...calls/deprecated_business_logic_syscall_handler.rs
94.48% <100.00%> (ø)

src/syscalls/deprecated_syscall_handler.rs
98.97% <100.00%> (ø)

src/transaction/deploy.rs
98.65% <100.00%> (+0.02%)
:arrow_up:

src/transaction/invoke_function.rs
99.27% <100.00%> (+<0.01%)
:arrow_up:

src/transaction/mod.rs
71.42% <100.00%> (ø)

About the TransactionExecutionInfo:
The ExecutionResources were fixed recently so that is why the test results changed after you pulled from main :D


Add TorQ Low Power Mode; Improve Timer Performance

reduce freq of subscription check to 60s and .timer to 1s; disable heartbeat and timer call logging; .timer.nextruntime added to hold value of next time .timer has to execute

PR description and the commit message of only commit are both quite unreadable, please improve pr description (e.g. Bullet point things or something, as well as adding an overview of why the changes are being made), and use better commit messages going forward (same rules apply as in prodsupport stuff)


Change request policy needed

An explicit "how to suggest changes" policy is needed, it should include a timeline as well. Some suggestions:

All suggestions must come in the form of a pull request or open issue on github.
Issues should be explicitly tagged as "Accepted" for inclusion when they will be.
Issues should be explicitly tagged as "Rejected" with a reason when the issue is closed.
When an Issue is to be "Accepted" a it should be added to a release milestone.
Accepted issues should have a 2 month comment period where objections to inclusion may be raised.

We decided not to do this. Changes will be made if necessary. Ad hoc, no official policy.


Lightspeed

Is there some way for this plugin to not use certain keys such as s and S? Lightspeed uses those keys and it doesn't work anymore.

Hi !
As you can see here, this plugin is not supposed to remap keys that have already been mapped, and lightspeed seems to work that way too.
I've you tried to call require("cutlass.nvim").setup() after require("lightspeed").setup() ?
If it doesn't works, I'll look further. Can you provide a minimal config to reproduce your problem ?

That actually worked. I forgot you could do that. Thanks! :heart:

FYI, I've implemented a new option to manage lightspeed, have a look to the documentation 😉


Enabling #define flags for optional messages

Wondering the possibility for expanding the #define flags in SpdmLibConfig.h to include different optional messages and/or capabilities, such that the code for handling the response to these messages is #define'd out and not compiled.
The scenario I had in mind is for a memory-constrained Responder. For example, if CERT_CAP isn't going to be utilized, a user would be able to set some define, say "#OPENSPDM_RESPONDER_CERT_CAP_SUPPORT 0". This define would then remove the related certificate handling code, leaving only the necessary error handling code - that way, in case the Requester still sent GET_DIGESTS/GET_CERTIFICATE, the Responder would respond with expected error.
It would require some thinking through - likely requiring warning/error if user tries to set a capability that was compiled out. However, it would be a great way for a consumer of OpenSPDM, with code-size limitations and a static set of capabilities, to easily trim down the code size without having to manually remove messages.
It is for microcontroller case - memory constrain environment. Compiler-time optimization to save space.

I can now look into this, will update when I have proposal implementation

Can also extend this to the cryptography functions as well. If, for example, a responder does not support encryption then all the encryption functionality can be removed more easily.

There's a lot that can be done here - creating #defines for certain capabilities also allows us to remove certain (often large) structures from the spdm_context_t struct as well, since they won't be used.
The tricky part would be balancing the ability to easily create a modular implementation of libspdm, alongside avoiding an intricate web of #ifdef and #ifndef macros littering the codebase. This may take some planning and investigation to determine what can be trimmed, especially cleanly.

I think we can start with SPDM_VERSION 1.0, 1.1, or 1.2, 2.0 in the future.

Providing a small update here. I have made a first attempt at this, but it ended up cluttering the codebase with #ifdef and #ifndef.
I'm going to try and clean up, post a proof-of-concept for feedback to see if this is something we think we can cleanly support.

You can take a look at my changes here: https://github.com/rkongintel/libspdm/pull/1
I'm new to the project, and still getting familiar with the code, so I didn't try to tackle trimming data sizes within the context. I can see how it can easily get out of hand.
Looking at the changes now, I touched a lot of files. It looks more messy than I first thought, but many of the #if/#endif in the library are around whole files rather than parts of functions.

I think it is good idea to add FLAG.
Some feedback:

I prefer to define it in include/library/spdm_lib_config.h instead of include/industry_standard/spdm.h.
I suggest we add capability check - if an entity includes disabled cap flag, the libspdm should ASSERT().
I feel we should use SPDM_DISABLE_*** instead of SPDM_ENABLE_***.

@jyao1 For #2, as an example for SPDM_DISABLE_CHALLENGE, do you mean in the spdm_set_data function, when receiving a SPDM_DATA_CAPABILITY_FLAGS parameter, ASSERT that the capability data does NOT have the (SPDM_GET_CAPABILITIES_RESPONSE_FLAGS_CHAL_CAP | SPDM_GET_CAPABILITIES_REQUEST_FLAGS_CHAL_CAP) set?

It seems like there are other non-capability related features a user would want to turn on/off based on a switch. (Currently defined as OPENSPDM_***_SUPPORT in spdm_lib_config.h). Maybe keep the switch as a separate name from caps for consistency, but the switch sets the capability to no on bits? And still use the switch for #if SWITCH/endif around the code?

@jyao1 For #2, as an example for SPDM_DISABLE_CHALLENGE, do you mean in the spdm_set_data function, when receiving a SPDM_DATA_CAPABILITY_FLAGS parameter, ASSERT that the capability data does NOT have the (SPDM_GET_CAPABILITIES_RESPONSE_FLAGS_CHAL_CAP | SPDM_GET_CAPABILITIES_REQUEST_FLAGS_CHAL_CAP) set?

That is correct.

Should we tie this directly to capabilities? And just have the defines be capabilities themselves?
Then, we wouldn't have to worry about some user enabling a set of messages that is incompatible with the capabilities they have set. And it would automatically trim the code size for messages user expects to support.
It would limit the ability to change the list of supported capabilities at runtime, but do we ever expect to do that? We can remove them still, depending on the capabilities of requester and responder. But we would never really expect to add any, right?

Sorry, I hardly understand what the proposal is. Can you provide some example, or sample code?

Sorry, I hardly understand what the proposal is. Can you provide some example, or sample code?

I.e.
Rather than defining the macros to remove support for individual messages, like so:
#define SPDM_DISABLE_GET_DIGESTS         1
#define SPDM_DISABLE_GET_CERTIFICATES 1
#define SPDM_DISABLE_CHALLENGE           1

and adding the following capability checks, for each possible message and capability combination:
#ifdef SPDM_DISABLE_GET_DIGESTS
ASSERT(spdm_is_capabilities_flag_supported( spdm_context, FALSE, 0,
		    SPDM_GET_CAPABILITIES_RESPONSE_FLAGS_CERT_CAP))
#endif
#ifdef SPDM_DISABLE_GET_CERTIFICATE
ASSERT(spdm_is_capabilities_flag_supported( spdm_context, FALSE, 0,
		    SPDM_GET_CAPABILITIES_RESPONSE_FLAGS_CERT_CAP))
#endif

We instead base the macros to add/remove support for specific capabilities.
For example, the defines could be as so
#define SPDM_DISABLE_CAPABILITY_CERT_CAP 1 #define SPDM_DISABLE_CAPABILITY_KEY_EX_CAP 1
Then, it would be simpler, since we can add the asserts only when the user sets the capabilities:
spdm_set_data (...)
{
	case SPDM_DATA_CAPABILITY_FLAGS:
#ifdef SPDM_DISABLE_CAPABILITY_CERT_CAP
               ASSERT(data == SPDM_DATA_CAPABILITY_CERT)
#endif
#ifdef SPDM_DISABLE_CAPABILITY_KEY_EX_CAP
               ASSERT(data == SPDM_DATA_CAPABILITY_KEY_EX)
#endif
}

The idea here, being that it would minimize the coverage matrix of testing what combination of messages is allowed, and what is not.

I prefer to have a base system that just supports the four required requests and then new capabilities are added at compile time with
#define SPDM_ENABLE_CAPABILITY_CERT_CAP 1

@steven-bellock yeah, that's most preferable.
Then, the supported capabilities can just be determined by the compile time flags, rather than requiring the user to set the capabilities at runtime with spdm_set_data().

I like the idea of having a baseline of support for required requests/responses, then adding in the optional ones with the SPDM_ENABLE_***_CAP. I feel it would be easier for users to add in any extras they want, rather than removing what they don't need.
If we are good with this method, I can get the changes started for a couple caps (CERT/CHALLENGE), and put it out for review.

Agree

There seem to be multiple CAP bits for GET MEASUREMENTS related.
#define SPDM_GET_CAPABILITIES_RESPONSE_FLAGS_MEAS_CAP (BIT3 | BIT4)
#define SPDM_GET_CAPABILITIES_RESPONSE_FLAGS_MEAS_CAP_NO_SIG BIT3
#define SPDM_GET_CAPABILITIES_RESPONSE_FLAGS_MEAS_CAP_SIG BIT4
#define SPDM_GET_CAPABILITIES_RESPONSE_FLAGS_MEAS_FRESH_CAP BIT5
Do you think a single compile switch (SPDM_ENABLE_GET_MEASUREMENTS_CAP) to control them all would be sufficient? And if users need finer grain of control, leave it up to them to make the change in their own versions of the code?
Same question for the PSK Cap.
#define SPDM_GET_CAPABILITIES_RESPONSE_FLAGS_PSK_CAP (BIT10 | BIT11)
#define SPDM_GET_CAPABILITIES_RESPONSE_FLAGS_PSK_CAP_RESPONDER BIT10
#define SPDM_GET_CAPABILITIES_RESPONSE_FLAGS_PSK_CAP_RESPONDER_WITH_CONTEXT BIT11

I put my changes here  and tried to update the comments in spdm_lib_config.h to be more detailed with what we are doing.

Voted to close at 6-Dec-2021 meeting.


Revert "Add jest tests"

Reverts janareddy1/github-actions-for-ci#6

##[error]Process completed with exit code 1.

n


chore(claim): move state update before call

move state update before call
Description
If the nonReentrant modifier is removed, the  claim function is prone to the reentrancy bug, by moving the state update above the transfer call we add redundancy to protect against the bug.
Type of change
Please delete options that are not relevant.

[ ] Bug fix

Fixes Least Authority Suggestion 1


Type: PlayerUpdate#state.position should be optional property

PlayerUpdate.state.position property does not exist when nothing is playing after joining a voice channel.
https://github.com/Deivu/Shoukaku/blob/2882a9718906011ca954d7604c1cd05db0489735/types/index.d.ts#L346-L354

Fixed in 2.1.6


chore(ci): update github lint and cache workflow

Description
While working on the cosmos-v046 branch, I found that our golangci-lint is not working correctly. Here is the fix.

Author Checklist
All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.
I have...

[ ] included the correct type prefix in the PR title
[ ] added ! to the type prefix if API or client breaking change
[ ] added appropriate labels to the PR
[ ] targeted the correct branch (see PR Targeting)
[ ] provided a link to the relevant issue or specification
[ ] added a changelog entry to CHANGELOG.md
[ ] included comments for documenting Go code
[ ] updated the relevant documentation or specification
[ ] reviewed "Files changed" and left comments if necessary
[ ] confirmed all CI checks have passed

Reviewers Checklist
All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.
I have...

[ ] confirmed the correct type prefix in the PR title
[ ] confirmed all author checklist items have been addressed
[ ] reviewed state machine logic
[ ] reviewed API design and naming
[ ] reviewed documentation is accurate
[ ] reviewed tests and test coverage
[ ] manually tested (if applicable)

The lint issues are going to be solved on this PR as well?

Codecov Report

Merging #1221 (af465d7) into main (857c28d) will increase coverage by 0.03%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main    #1221      +/-   ##
==========================================
+ Coverage   51.17%   51.20%   +0.03%
==========================================
  Files          67       67
  Lines        6654     6659       +5
==========================================
+ Hits         3405     3410       +5
  Misses       3009     3009
  Partials      240      240

Impacted Files
Coverage Δ

x/leverage/keeper/keeper.go
40.53% <ø> (ø)

ante/spam_prevention.go
77.77% <100.00%> (+0.41%)
:arrow_up:

x/leverage/keeper/liquidate.go
40.39% <100.00%> (+1.62%)
:arrow_up:

The lint warnings are going to be solved on this PR as well?

Only errors. We can fix warnings in a subsequent PR.

idk why golangci-price-feeder isn't running

It is running, I tested it. Revive doesn't work for some reason, and created follow up task for that.

The problem with golangci-price-feeder is that I removed it and merged it into the lint job. We need to change setting because it's set as a required. Since it's merged into the Lint job, we need to remove that entry.


Cannot position tour-element by config property

This is propably more of a featurerequest than a bug.
I cannot find any property in step-configuration that lets me manipulate the position of the step-element.
I would like to configure weather it is shown left, right, over or under the element it is anchored to.
this._tourService.initialize([             {                 anchorId: 'dashboard-centered',                 title:  'super cool title'),                 content: 'super cool content',                 route: '/dashboard'                 position: right             } ])
or even better, have position be an object that contains additional values to position relative to anchor-element
As a workaround i currently read the height and width of the anchor-element and use it to manually position
.cdk-overlay-connected-position-bounding-box.
I love the library, thanks to everyone who contributed!

ngx-ui-tour-md-menu doesn't support positioning yet. I'll see if this can be implemented sometime soon.

You can now configure step position in v6.1.

Thank you for your quick reaction and update!
I updated my verstion of the library and found that only the xPosition works, when i try to add placement with yPosition: 'above' the step still shows up under the touranchor (even though there is more than enough space above it).
Also even if everything works great, it is not possible to place the step completely after the touranchor, since it behaves the same as mat-menu positioning.
It would be great to have the the option to determine weather the step should show up behind the touranchor, plus an additional property to set a margin between anchor and step, and an additional property to set if the step should be shown, centered or top-aligned/bottom-aligned, and if there is an arrow pointing towards the tourAnchor:
`import {IStepOption} from 'ngx-ui-tour-md-menu';
const steps: IStepOption[] = [{
anchorId: 'start.tour',
content: 'Welcome to the Ngx-UI-Tour tour!',
title: 'Welcome',
placement: {
xPosition: 'after | before | center | alignLeft | alignRight',
yPosition: 'center | alignTop | alignBottom | above | below ',
margin: '5px',
},
arrow: true
}];`
I am considering to contribute, however i'm not sure if its not easier to just dump the whole mat-menu infrastructure plus i have zero experience in creating libraries ... do you think it would be possible for me to add all that functionality?

I updated my verstion of the library and found that only the xPosition works, when i try to add placement with yPosition: 'above' the step still shows up under the touranchor (even though there is more than enough space above it).

We are using Angular Material Menu xPosition and yPosition. If the Menu component determines, that there isn't enough space on top, it will be displayed on the bottom. If there is definitely enough space, the only other reason I can think of is misspelling in yPosition config key or value.

It would be great to have the the option to determine weather the step should show up behind the touranchor

Not sure I understand where exactly you want to place the tour step. How can it be behind tour anchor element?

plus an additional property to set a margin between anchor and step

You should be able to do that using touranchor--is-active global CSS class. Sth like the following:
.touranchor--is-active {
    padding-top: 1.5rem;
    margin-top: -1.5rem;
}

and an additional property to set if the step should be shown, centered or top-aligned/bottom-aligned, and if there is an arrow pointing towards the tourAnchor:

For that you'll have to use another tour UI like ng-bootstrap or ngx-bootstrap. That's not possible with md-menu.

I am considering to contribute, however i'm not sure if its not easier to just dump the whole mat-menu infrastructure plus i have zero experience in creating libraries ... do you think it would be possible for me to add all that functionality?

To be honest, I don't think so. If you are not happy with this library, you can also take a look at some alternatives like ng-tour or ngx-joyride.


Create zh_cn.json

Create zh_cn.json by myself (different from the version of MarinaMarissa and more accurate than that). By the way, what does "pythadendron" mean?

pythadendron is a name, combined from "Pythagoras" and "dendron" (meaning "tree" in Latin)


addConnection method do not edit connection data.

Hi! I'm not sure if it is a known issue or i'm doing something wrong.
When I use de addConnection method, connection event "connectionCreated" occurs, I can catch the event and the connection data is correct but the drawflow node connection data is not updated. The connection is not added to the graph. However, if I connect it via interface (drag and drop output to input), all is correct: connectionCreated event occurs and node connection data is updated.
I use editor.value.addConnection(out_id, in_id, 'output_1', 'input_1') and seems to be correct, event occurs. But node connection data is not updated.
Thanks!
Darío :)

It seems that the function is correct.
Maybe the values no out_id and in_id are not correct.
Try forcing node connections to refresh:
editor.updateConnectionNodes('node-5');

Remember that the use of the function is like this and the nodes must be created.
editor.addConnection(1, 2, 'output_1', 'input_1');

Thanks for the quick response, it seems that everything is correct and I also tried to force it. But I don't get it. I'll keep researching to see if I find anything I might be doing wrong. If I find the reason I'll show you. Thank you so much.

Sorry for the confusion, there was a procedure that was deleting my connections.
Thanks


Rstudio qt error

Issue description
RStudio does't start. (See also on Discourse)
Steps to reproduce
Create a default.nix as follows:
with import <nixpkgs> {};
let
  my-R-packages = with rPackages; [ mongolite ];
  R-with-my-packages = rWrapper.override{ packages = with rPackages; my-R-packages; };
  RStudio-with-my-packages = rstudioWrapper.override{ packages = with rPackages; my-R-packages; };
in stdenv.mkDerivation {
  name = "feeds";
  buildInputs = [ R-with-my-packages RStudio-with-my-packages ];
}

Then
nix-shell

Then this happens:
[nix-shell:~/test]$ rstudio
qt.qpa.plugin: Could not find the Qt platform plugin "xcb" in ""
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Technical details
 - system: `"x86_64-linux"`
 - host os: `Linux 4.14.74, NixOS, 18.09.932.09195057114 (Jellyfish)`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.1.1`
 - channels(root): `"nixos-18.09.932.09195057114, nixos-unstable-18.09pre149415.8395f9aa85e, nixpkgs"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

I'm fairly certain that this is due to an improperly configured QT_PLUGIN_PATH, let me see if I can fix it :)

hmm... testing your expression on nixpkgs<PHONE_NUMBER>4 (the commit you specified as commit of your nixos installation) seems to work fine though.

:/
Can it be that it's because I'm using i3 for wm?
Can I try anything to pinpoint the issue?

I use i3wm as window manager as well.

Can I try anything to pinpoint the issue?

Probably. Is there anything special in your QT_PLUGIN_PATH? I'm still fairly certain that this is related to such an issue, in the past I fixed several issues with an equal message.

Hmmm...
[nix-shell:/tmp]$  for i in $(echo $QT_PLUGIN_PATH | sed s"/[:]/\n/g"); do ls $i; done
ls: cannot access '/home/turing/.nix-profile/lib/qt4/plugins': No such file or directory
ls: cannot access '/home/turing/.nix-profile/lib/kde4/plugins': No such file or directory
ls: cannot access '/nix/var/nix/profiles/default/lib/qt4/plugins': No such file or directory
ls: cannot access '/nix/var/nix/profiles/default/lib/kde4/plugins': No such file or directory
ls: cannot access '/run/current-system/sw/lib/qt4/plugins': No such file or directory
ls: cannot access '/run/current-system/sw/lib/kde4/plugins': No such file or directory
ls: cannot access '/etc/profiles/per-user/mredaelli/lib/qt4/plugins': No such file or directory
ls: cannot access '/etc/profiles/per-user/mredaelli/lib/kde4/plugins': No such file or directory

yeah, I was obviously wrong with this idea. I fixed this in some packages where a component was missing and could be added manually into QT_PLUGIN_PATH, I guess I'm missing something here as your expression works perfectly fine for me.
Does rstudio itself work, when invoking ./result/bin/rstudio from nix-build -A rstudio?

It does!

that’s certainly good to know, at least the basic functionality is available.
Although I couldn’t reproduce it yet, I suspect a bug in the expression which breaks overrides in certain cases. I’ll have a deeper look at the expression tomorrow and report back:)

after having a look at the expression I couldn't find an obvious issue.
However a typical workaround for such issues usually looks like this:
diff --git a/pkgs/development/r-modules/wrapper-rstudio.nix b/pkgs/development/r-modules/wrapper-rstudio.nix
index dd9b0e9c538..51cd6298175 100644
--- a/pkgs/development/r-modules/wrapper-rstudio.nix
+++ b/pkgs/development/r-modules/wrapper-rstudio.nix
@@ -1,4 +1,8 @@
-{ stdenv, R, rstudio, makeWrapper, recommendedPackages, packages }:
+{ stdenv, R, rstudio, makeWrapper, recommendedPackages, packages, qtbase }:
+
+let
+  qtVersion = with stdenv.lib.versions; "${major qtbase.version}.${minor qtbase.version}";
+in

 stdenv.mkDerivation rec {

@@ -24,7 +28,8 @@ stdenv.mkDerivation rec {
     echo -n $R_LIBS_SITE | sed -e 's/:/", "/g' >> $out/${fixLibsR}
     echo -n "\"))" >> $out/${fixLibsR}
     echo >> $out/${fixLibsR}
-    makeWrapper ${rstudio}/bin/rstudio $out/bin/rstudio --set R_PROFILE_USER $out/${fixLibsR}
+    makeWrapper ${rstudio}/bin/rstudio $out/bin/rstudio --set R_PROFILE_USER $out/${fixLibsR} \
+      --prefix QT_PLUGIN_PATH : ${qtbase}/lib/${qtVersion}/plugins
   '';

   meta = {
diff --git a/pkgs/top-level/all-packages.nix b/pkgs/top-level/all-packages.nix
index d1ab34eba6f..60ed9787301 100644
--- a/pkgs/top-level/all-packages.nix
+++ b/pkgs/top-level/all-packages.nix
@@ -13084,7 +13084,7 @@ with pkgs;
     packages = [];
   };

-  rstudioWrapper = callPackage ../development/r-modules/wrapper-rstudio.nix {
+  rstudioWrapper = libsForQt5.callPackage ../development/r-modules/wrapper-rstudio.nix {
     recommendedPackages = with rPackages; [
       boot class cluster codetools foreign KernSmooth lattice MASS
       Matrix mgcv nlme nnet rpart spatial survival

Would you mind applying the patch in your local nixpkgs checkout and rebuild your expression?

Sorry it took me a while.
I patched it locally, but still get the same error.
Just to make sure I did it correctly, the point was to get the rstudio script to look like this (specifically, the QT_PLUGIN_PATH variable), right?
#! /nix/store/czx8vkrb9jdgjyz8qfksh10vrnqa723l-bash-4.4-p23/bin/bash -e
export R_PROFILE_USER='/nix/store/zmda1qdpg0gnlvj8rskaxd19zj283ikl-RStudio-1.1.456-wrapper/fix_libs.R'
export QT_PLUGIN_PATH='/nix/store/v1g34bsiwv0qi0q80pawjx3qvimlbhdg-qtbase-5.11.1-bin/lib/5.11/plugins'${QT_PLUGIN_PATH:+':'}$QT_PLUGIN_PATH
exec "/nix/store/4x2vjn0q8xqyridcznvv2vzzax817p5m-RStudio-1.1.456/bin/rstudio"  "${extraFlagsArray[@]}" "$@"
/nix/store/zmda1qdpg0gnlvj8rskaxd19zj283ikl-RStudio-1.1.456-wrapper/bin/rstudio

Anyway, the problem seems to be that the directory
/nix/store/v1g34bsiwv0qi0q80pawjx3qvimlbhdg-qtbase-5.11.1-bin/lib/5.11/plugins

does not exist. It should be
/nix/store/v1g34bsiwv0qi0q80pawjx3qvimlbhdg-qtbase-5.11.1-bin/lib/qt-5.11/plugins

(there's a qt- too much or too little).
But I have no clue how to fix that :)

does it work with the qt- prefix?

Lol, I should have mentioned :) Yes it does.
On 19/11 13:29, Maximilian Bosch wrote:

does it work with the qt- prefix?
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/NixOS/nixpkgs/issues/48826#issuecomment-440047993

Then it's likely that I screwed my patch up :)
But when it works with the qt- prefix, would you mind updating and filing the patch?

Ahhh I see what you mean.
Sure :)

Submitted PR #50964


Pro Template Maps

Is your feature request related to a problem? Please describe.
Create pre-generated maps inside AGP for specific functions.
Describe the solution you'd like
Have maps with appropriate symbology for functional use.
Describe alternatives you've considered
Making them from scratch at each incident.
Additional context
Add any other context or screenshots about the feature request here.

Thinking these should be webMaps in the AGOL org and be downloaded for offline use.

For map types:
Air Ops (FAA Base and Features)
Marine Ops (NOAA ENC Base and Features)

@t-mahon: Thanks...added those to the top layer comment.


Hydrawise Home Assistant integration error: last_contact is "Unknown"

Hi there! I recently got a Hydrawise controller and I'm running into an issue trying to connect it to Home Assistant. I've tracked the issue down to this repo which is why I'm posting the issue here rather than the HA repo or forums. Please let me know if there's a better place to post this.
The issue:
When trying to add the Hydrawise integration I'm running into an Unknown Error. From the home assistant logs the issue seems to be trying to parse  "last_contact": "Unknown" as a datetime in the legacy pydrawise API when calling get_user.
I'm able to connect and control my Hydrawise controller through the Android app so I don't think there's anything wrong with my physical setup.
The Hydrawise API docs (v1.6 here) suggest that the last_contact field is deprecated, which makes me think I will always see "Unknown" as the value for last_contact.
last_contact string Depreciated

Is this a known issue with a workaround? Or does _controller_from_json need to be updated to handle "Unknown"?
Thanks in advance for your help!
home assistant error
Most relevant part
File "/usr/local/lib/python3.11/site-packages/pydrawise/legacy.py", line 226, in _controller_from_json
    last_contact_time=datetime.fromtimestamp(controller_json["last_contact"]),
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: 'str' object cannot be interpreted as an integer

Full logs
Logger: aiohttp.server
Source: /usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py:421
First occurred: October 21, 2024 at 1:23:54 PM (4 occurrences)
Last logged: 6:13:34 AM

Error handling request
Traceback (most recent call last):
  File "/usr/local/lib/python3.11/site-packages/aiohttp/web_protocol.py", line 452, in _handle_request
    resp = await request_handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/aiohttp/web_app.py", line 543, in _handle
    resp = await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/aiohttp/web_middlewares.py", line 114, in impl
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/security_filter.py", line 85, in security_filter_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/forwarded.py", line 100, in forwarded_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 28, in request_context_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 80, in ban_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 233, in auth_middleware
    return await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/headers.py", line 31, in headers_middleware
    response = await handler(request)
               ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/view.py", line 149, in handle
    result = await handler(request, **request.match_info)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/decorators.py", line 63, in with_admin
    return await func(self, request, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 177, in post
    return await super().post(request, flow_id)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/http/data_validator.py", line 72, in wrapper
    result = await method(view, request, data, *args, **kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/data_entry_flow.py", line 110, in post
    result = await self._flow_mgr.async_configure(flow_id, data)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 320, in async_configure
    result = await self._async_handle_step(
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 416, in _async_handle_step
    result: FlowResult = await getattr(flow, method)(user_input)
                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/hydrawise/config_flow.py", line 82, in async_step_user
    return await self._create_entry(api_key, on_failure=self._show_form)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/hydrawise/config_flow.py", line 33, in _create_entry
    user = await api.get_user(fetch_zones=False)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/pydrawise/legacy.py", line 59, in get_user
    controllers=[_controller_from_json(c) for c in resp_json["controllers"]],
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/pydrawise/legacy.py", line 59, in <listcomp>
    controllers=[_controller_from_json(c) for c in resp_json["controllers"]],
                 ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/pydrawise/legacy.py", line 226, in _controller_from_json
    last_contact_time=datetime.fromtimestamp(controller_json["last_contact"]),
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: 'str' object cannot be interpreted as an integer

curl test
request
curl -X GET 'https://api.hydrawise.com/api/v1/customerdetails.php?api_key=AAAA-BBBB-CCCC-DDDD'

response
{
  "controller_id": YYYYYYY,
  "customer_id": ZZZZZZZ,
  "current_controller": "Garage Sprinkler Controller",
  "controllers": [
    {
      "name": "Garage Sprinkler Controller",
      "last_contact": "Unknown",
      "serial_number": "XXXXXXXXXX",
      "controller_id": YYYYYYY,
      "status": "Unknown"
    }
  ]
}

It looks like you're using an old version of Home Assistant. The integration was updated to use the newer Hydrawise API in 2024.5, and it does not have this problem.

Ah, thank you very much!


[FIX #1188] added fix for supporting weird filenames that look like JSONs

better check for JSON instead of regex.

Thanks for the feedback. I've incorporated both the changes in: https://github.com/openseadragon/openseadragon/pull/1189/commits/ce1360f5cb65e4c194183c96c7ae1c2221604ba7

Accidentally closed it.

Beautiful! Thank you for fixing this :)


Hide empty optgroups on search

I needed to hide empty optgroups during search, so I added at line 925 code:
          that.$lis.filter('.dropdown-header').each(function(index, header){
              header = $(header);
              var lastElem = header.nextUntil(':not(.hide)').last();
              var nextElem = lastElem.next();
              if ((lastElem.size() > 0 && nextElem.size() === 0) || nextElem.hasClass('divider')) {
                  header.addClass('hide');
                  nextElem.addClass('hide');
              }
          });

not sure if it is best, but if somebody needs it ;-)

Hello, the new version of the plugin where do you put the code to hide the divider?
Thx

It looks quite changed and in marginal ways, I use it in project with older version and would need more time to analyse new version. If you are in hurry, I can send old file.

Hello, thank you for taking the time to answer me.
I'll look at that!

this is already resolved with new version of download.


FirebaseUI-Auth: auth with Digits

Digits works pretty well already, because it's credentials are compatible with Twitter credentials
Also, since Google bought Fabric, I think it will work better soon
So, when Digits button will be available in library?
Is contributions for this are welcome?
Thanks

@drishi94 what's the plan around Digits?

Hi rostopira, we are still formulating our final plans with Digits please stay tuned for updates!

Is there a recommended alternative for the time being?

As of today, Firebase Authentication supports phone auth :)

Talk about timing!
Sent from my iPhone

On May 18, 2017, at 12:05 AM, drishi94<EMAIL_ADDRESS>wrote:
As of today, Firebase Authentication supports phone auth :)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.


Fatal Error - /usr/include/features.h:461:12: fatal error: sys/cdefs.h: No such file or directory

I’ve tried to install lfs via luarocks but received the following error.
admin@ubuntu2004:~/Documents$ sudo luarocks install luafilesystem
Installing https://luarocks.org/luafilesystem-1.8.0-1.src.rock
gcc -O2 -fPIC -I/usr/include/lua5.3 -c src/lfs.c -o src/lfs.o
In file included from /usr/include/errno.h:25,
                 from src/lfs.c:41:
/usr/include/features.h:461:12: fatal error: sys/cdefs.h: No such file or directory
  461 | #  include <sys/cdefs.h>
      |            ^~~~~~~~~~~~~
compilation terminated.

Error: Build error: Failed compiling object src/lfs.o

Other information that might help.
admin@ubuntu2004:~/Documents$ lua -v
Lua 5.3.3  Copyright (C) 1994-2016 Lua.org, PUC-Rio

admin@ubuntu2004:~/Documents$ luarocks
LuaRocks 2.4.2, a module deployment system for Lua

Ok, on Ubuntu the fix was to use the following instead..
sudo apt-get install -y lua-filesystem

Hi, nice to see you solve your problem.
Then maybe it's good to close issue, it will feel disheartened to see lots of bugs opens.
And it's still searchable after close.


Huge exported build size on Android in comparison with Desktop version

Godot version:
3.0.2
OS/device including version:
GNU/Linux X11
Issue description:
I'm the developer of Solaria. When exporting, I noticed that the Android build is +100MB while Desktop versions are about 25MB. Is this huge difference normal?
Thank you in advance!
Steps to reproduce:
Build for Android with official export templates.
Minimal reproduction project:
https://gitlab.com/atorresm/solaria

That's just the size of your game, you have 94 MB of assets:
$ LC_ALL=C ls -l
total 223512
-rw-r--r-- 1 akien akien 106338580 Apr  6 11:56 solaria.apk
-rw-r--r-- 1 akien akien  94985732 Apr  6 11:54 solaria.pck
-rwxr-xr-x 1 akien akien  27539593 Apr  6 11:54 solaria.x86_64*

The Linux version above is not 27 MB, it's 27 MB (binary) + 95 MB (assets).


[Nappy] -> [Stock Photos]

[Nappy] -> [Stock Photos]
A website offering Beautiful, high-res photos of black and brown people.
Link: https://www.nappy.co/
Checklist:

[X] I have performed a self-review of submitted resource and its follows the guidelines of the project.

Hello, sorry I tried to separate the pulls but it just end up merging.

@dridge737 Thanks for your contribution.
I Think you are now restricted to one ressource per PR.
I Guess you should split this into two PRs.


How do to find out what pulled in some package?

How do I find out the dependency chain that pulled in some package in vendor folder? Is there any equivalent of mvn dependency:tree command with dep?

You can visualize the tree with dep status -dot & graphviz: https://github.com/golang/dep/blob/master/README.md#visualizing-dependencies
It will group all packages belonging to same repo in the same node, but that usually should be enough

Thanks. I have tried to use tools that use graphviz but in my experience those are not useful in large code base. It takes too long and can't search in a image. glide had a command like glide tree. I can dump the output of that in a file and search. I would very much appreciate that.
In terms of large project, we work in the Kubernetes area and some of our projects have 200 top level dependency via the Kubernetes project. I takes me 10 mins to run a glide up some days.

https://github.com/KyleBanks/depth prints a textual tree

this is something we plan to add to dep status - when interrogating an individual dependency, it'll indicate its dependers. don't have it right now, though - @michael-go's suggestions are the same as what i'd have made.

@tamalsaha  I'm assuming this question has been answered. Please feel free to reopen the issue if you still looking for a different answer.


Update discussion of DID/VC

DID and VC are increasingly being adopted by real scaled use cases, something that should be better reflected in Chapter 4-1.  @Identitywoman would be a good person to do some of this, but I'd also love government implementers in Taiwan (like @mashbean) and the folks from Argentina to weigh in.

 Gov4Git notices
On Friday, 06-Sep-24 18:14:05 UTC by Gov4Git dev
Notice v6yn7u
Started managing this issue, using the Plural Management Protocol v1,  as Gov4Git concern 1003 with initial priority score of 0.000000.
This project is managed by Gov4Git, a decentralized governance system for collaborative git projects.
To participate in governance, install the Gov4Git desktop app.
Notice 6y3wf7
This issue's priority score is now 0.000000.
The cost of priority is 0.000000.
The projected bounty is now 0.000000.
Notice erqt7i
The set of eligible proposals claiming this issue is empty.

Received. Currently, we are drawing on international examples of privacy-enhanced, user-centric digital civic infrastructure as the blueprint for our domestic public infra projects. I might be able to provide some principled suggestions for future public sector implementers.

QuarkID and the Global Adoption of DID/VC Standards
As decentralized identity (DID) and verifiable credentials (VC) solutions gain traction globally, QuarkID stands as a leading example of how these technologies can be implemented in real-world scenarios. As an open-source self-sovereign identity (SSI) protocol, under the Apache 2.0 license, QuarkID has been deployed in various regions of Argentina, providing citizens with a decentralized way to manage their identities while interacting with public and private services. This has been particularly impactful in regions like Buenos Aires, where the government has embraced digital identity solutions, as well as in other jurisdictions across Latin America, such as Nuevo Leon and Monterrey in Mexico. Additionally, QuarkID is being registered as a Digital Public Good in the DPG Alliance, further solidifying its commitment to open standards and public accessibility.
The broader adoption of DID/VC standards, as outlined by the W3C, is not just a technological shift but a paradigm change in how identity is managed globally. Projects like QuarkID reflect a trend toward empowering individuals through decentralized systems that remove reliance on centralized authorities for identity verification.
The Importance of Open Standards and Open Protocols
However, the key to the success of such systems lies not only in the adoption of open standards like the DID/VC protocols developed by the W3C but in ensuring that these standards are implemented in open-source protocols, which are not controlled by any single government entity. The importance of deploying these solutions on open, non-permissioned distributed ledger technologies (DLTs) cannot be overstated.
Governments, while playing a critical role in managing trust registries within their governance layer—as outlined in the Trust over IP four-layer model—should not have the power to restrict access to the decentralized attestation systems that form the backbone of these digital identity frameworks. By ensuring that these protocols are governed by the community and free from centralized control, we create a system where identities can be verified and validated without the risk of governmental overreach or misuse. This model preserves individual freedom and maintains the open, decentralized nature of the digital identity ecosystem.

This feels like a product pitch for a particular implementation.
We could mention a dozen companies implementing - if we did that great.
There is also SSI whitewashing going on in the market.
I would be happy to contribute something that outlines actual
implementations from across the world. I would be more comfortable
mentioning specific companies if referring to them was in relation to
specific projects that are happening with the public sector - balances it
out to what is happening.
For example both SpruceID and Digital Bazaar are working with the State of
California for their implementation of VCs (and mDLs).

Kaliya

On Tue, Sep 10, 2024 at 7:22 AM fernandezdiegoh @.***>
wrote:

QuarkID and the Global Adoption of DID/VC Standards
As decentralized identity (DID) and verifiable credentials (VC) solutions
gain traction globally, QuarkID http://www.quarkid.org/ stands as a
leading example of how these technologies can be implemented in real-world
scenarios. As an open-source self-sovereign identity (SSI) protocol
https://github.com/ssi-quarkid, under the Apache 2.0 license
https://www.apache.org/licenses/LICENSE-2.0, QuarkID has been deployed
in various regions of Argentina, providing citizens with a decentralized
way to manage their identities while interacting with public and private
services. This has been particularly impactful in regions like Buenos
Aires, where the government has embraced digital identity solutions, as
well as in other jurisdictions across Latin America, such as Nuevo Leon and
Monterrey in Mexico. Additionally, QuarkID is being registered as a
Digital Public Good https://app.digitalpublicgoods.net/a/11563 in the
DPG Alliance, further solidifying its commitment to open standards and
public accessibility.
The broader adoption of DID/VC standards, as outlined by the W3C, is not
just a technological shift but a paradigm change in how identity is managed
globally. Projects like QuarkID reflect a trend toward empowering
individuals through decentralized systems that remove reliance on
centralized authorities for identity verification.
The Importance of Open Standards and Open Protocols
However, the key to the success of such systems lies not only in the
adoption of open standards like the DID https://www.w3.org/TR/did-core//
VC https://www.w3.org/TR/vc-data-model-2.0/ protocols developed by the
W3C but in ensuring that these standards are implemented in open-source
protocols, which are not controlled by any single government entity. The
importance of deploying these solutions on open, non-permissioned
distributed ledger technologies (DLTs) cannot be overstated.
Governments, while playing a critical role in managing trust registries
within their governance layer—as outlined in the Trust over IP four-layer
model https://trustoverip.org/toip-model/—should not have the power to
restrict access to the decentralized attestation systems that form the
backbone of these digital identity frameworks. By ensuring that these
protocols are governed by the community and free from centralized control,
we create a system where identities can be verified and validated without
the risk of governmental overreach or misuse. This model preserves
individual freedom and maintains the open, decentralized nature of the
digital identity ecosystem.
—
Reply to this email directly, view it on GitHub
https://github.com/pluralitybook/plurality/issues/1003#issuecomment-2340977627,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAW3CC2OU44DNFWKJNX5QCTZV36B5AVCNFSM6AAAAABNZBK4LKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNBQHE3TONRSG4
.
You are receiving this because you were mentioned.Message ID:
@.***>

I’d appreciate building on this for a more balanced illustration as you suggest Kaliya
Get Outlook for iOShttps://aka.ms/o0ukef

From: Kaliya - Identity Woman @.>
Sent: Tuesday, September 10, 2024 10:39:22 AM
To: pluralitybook/plurality @.>
Cc: Glen Weyl @.>; Author @.>
Subject: Re: [pluralitybook/plurality] Update discussion of DID/VC (Issue #1003)
This feels like a product pitch for a particular implementation.
We could mention a dozen companies implementing - if we did that great.
There is also SSI whitewashing going on in the market.
I would be happy to contribute something that outlines actual
implementations from across the world. I would be more comfortable
mentioning specific companies if referring to them was in relation to
specific projects that are happening with the public sector - balances it
out to what is happening.
For example both SpruceID and Digital Bazaar are working with the State of
California for their implementation of VCs (and mDLs).

Kaliya

On Tue, Sep 10, 2024 at 7:22 AM fernandezdiegoh @.***>
wrote:

QuarkID and the Global Adoption of DID/VC Standards
As decentralized identity (DID) and verifiable credentials (VC) solutions
gain traction globally, QuarkID http://www.quarkid.org/ stands as a
leading example of how these technologies can be implemented in real-world
scenarios. As an open-source self-sovereign identity (SSI) protocol
https://github.com/ssi-quarkid, under the Apache 2.0 license
https://www.apache.org/licenses/LICENSE-2.0, QuarkID has been deployed
in various regions of Argentina, providing citizens with a decentralized
way to manage their identities while interacting with public and private
services. This has been particularly impactful in regions like Buenos
Aires, where the government has embraced digital identity solutions, as
well as in other jurisdictions across Latin America, such as Nuevo Leon and
Monterrey in Mexico. Additionally, QuarkID is being registered as a
Digital Public Good https://app.digitalpublicgoods.net/a/11563 in the
DPG Alliance, further solidifying its commitment to open standards and
public accessibility.
The broader adoption of DID/VC standards, as outlined by the W3C, is not
just a technological shift but a paradigm change in how identity is managed
globally. Projects like QuarkID reflect a trend toward empowering
individuals through decentralized systems that remove reliance on
centralized authorities for identity verification.
The Importance of Open Standards and Open Protocols
However, the key to the success of such systems lies not only in the
adoption of open standards like the DID https://www.w3.org/TR/did-core//
VC https://www.w3.org/TR/vc-data-model-2.0/ protocols developed by the
W3C but in ensuring that these standards are implemented in open-source
protocols, which are not controlled by any single government entity. The
importance of deploying these solutions on open, non-permissioned
distributed ledger technologies (DLTs) cannot be overstated.
Governments, while playing a critical role in managing trust registries
within their governance layer—as outlined in the Trust over IP four-layer
model https://trustoverip.org/toip-model/—should not have the power to
restrict access to the decentralized attestation systems that form the
backbone of these digital identity frameworks. By ensuring that these
protocols are governed by the community and free from centralized control,
we create a system where identities can be verified and validated without
the risk of governmental overreach or misuse. This model preserves
individual freedom and maintains the open, decentralized nature of the
digital identity ecosystem.
—
Reply to this email directly, view it on GitHub
https://github.com/pluralitybook/plurality/issues/1003#issuecomment-2340977627,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAW3CC2OU44DNFWKJNX5QCTZV36B5AVCNFSM6AAAAABNZBK4LKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNBQHE3TONRSG4
.
You are receiving this because you were mentioned.Message ID:
@.***>

—
Reply to this email directly, view it on GitHubhttps://github.com/pluralitybook/plurality/issues/1003#issuecomment-2341046605, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABIRKSCNRV7DSXLHGSAJW53ZV4ABVAVCNFSM6AAAAABNZBK4LKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNBRGA2DMNRQGU.
You are receiving this because you authored the thread.Message ID: @.***>

I do, however, support highlighting examples lifting up developing world public sector examples where possible.

From: Kaliya - Identity Woman @.>
Sent: Tuesday, September 10, 2024 10:39 AM
To: pluralitybook/plurality @.>
Cc: Glen Weyl @.>; Author @.>
Subject: Re: [pluralitybook/plurality] Update discussion of DID/VC (Issue #1003)
This feels like a product pitch for a particular implementation.
We could mention a dozen companies implementing - if we did that great.
There is also SSI whitewashing going on in the market.
I would be happy to contribute something that outlines actual
implementations from across the world. I would be more comfortable
mentioning specific companies if referring to them was in relation to
specific projects that are happening with the public sector - balances it
out to what is happening.
For example both SpruceID and Digital Bazaar are working with the State of
California for their implementation of VCs (and mDLs).

Kaliya

On Tue, Sep 10, 2024 at 7:22 AM fernandezdiegoh @.***>
wrote:

QuarkID and the Global Adoption of DID/VC Standards
As decentralized identity (DID) and verifiable credentials (VC) solutions
gain traction globally, QuarkID http://www.quarkid.org/ stands as a
leading example of how these technologies can be implemented in real-world
scenarios. As an open-source self-sovereign identity (SSI) protocol
https://github.com/ssi-quarkid, under the Apache 2.0 license
https://www.apache.org/licenses/LICENSE-2.0, QuarkID has been deployed
in various regions of Argentina, providing citizens with a decentralized
way to manage their identities while interacting with public and private
services. This has been particularly impactful in regions like Buenos
Aires, where the government has embraced digital identity solutions, as
well as in other jurisdictions across Latin America, such as Nuevo Leon and
Monterrey in Mexico. Additionally, QuarkID is being registered as a
Digital Public Good https://app.digitalpublicgoods.net/a/11563 in the
DPG Alliance, further solidifying its commitment to open standards and
public accessibility.
The broader adoption of DID/VC standards, as outlined by the W3C, is not
just a technological shift but a paradigm change in how identity is managed
globally. Projects like QuarkID reflect a trend toward empowering
individuals through decentralized systems that remove reliance on
centralized authorities for identity verification.
The Importance of Open Standards and Open Protocols
However, the key to the success of such systems lies not only in the
adoption of open standards like the DID https://www.w3.org/TR/did-core//
VC https://www.w3.org/TR/vc-data-model-2.0/ protocols developed by the
W3C but in ensuring that these standards are implemented in open-source
protocols, which are not controlled by any single government entity. The
importance of deploying these solutions on open, non-permissioned
distributed ledger technologies (DLTs) cannot be overstated.
Governments, while playing a critical role in managing trust registries
within their governance layer—as outlined in the Trust over IP four-layer
model https://trustoverip.org/toip-model/—should not have the power to
restrict access to the decentralized attestation systems that form the
backbone of these digital identity frameworks. By ensuring that these
protocols are governed by the community and free from centralized control,
we create a system where identities can be verified and validated without
the risk of governmental overreach or misuse. This model preserves
individual freedom and maintains the open, decentralized nature of the
digital identity ecosystem.
—
Reply to this email directly, view it on GitHub
https://github.com/pluralitybook/plurality/issues/1003#issuecomment-2340977627,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAW3CC2OU44DNFWKJNX5QCTZV36B5AVCNFSM6AAAAABNZBK4LKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNBQHE3TONRSG4
.
You are receiving this because you were mentioned.Message ID:
@.***>

—
Reply to this email directly, view it on GitHubhttps://github.com/pluralitybook/plurality/issues/1003#issuecomment-2341046605, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABIRKSCNRV7DSXLHGSAJW53ZV4ABVAVCNFSM6AAAAABNZBK4LKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNBRGA2DMNRQGU.
You are receiving this because you authored the thread.Message ID: @.***>

Ok. Good to know. I have a focus on completing my IETF research this week.
I will be sure to download the current language and consider changes while
I'm flying to Taiwan next week.
On Tue, Sep 10, 2024 at 8:08 AM Glen Weyl @.***> wrote:

A month or so.

Research Lead, Plural Technology Collaboratoryhttps://aka.ms/plural,
Research Special Projects

From: Kaliya - Identity Woman @.>
Sent: Tuesday, September 10, 2024 10:58 AM
To: pluralitybook/plurality @.>
Cc: Glen Weyl @.>; Author @.>
Subject: Re: [pluralitybook/plurality] Update discussion of DID/VC (Issue
#1003)
What is the timeline for this round of changes?
On Tue, Sep 10, 2024 at 7:51 AM Glen Weyl @.***> wrote:

I do, however, support highlighting examples lifting up developing world
public sector examples where possible.

From: Kaliya - Identity Woman @.>
Sent: Tuesday, September 10, 2024 10:39 AM
To: pluralitybook/plurality @.>
Cc: Glen Weyl @.>; Author @.>
Subject: Re: [pluralitybook/plurality] Update discussion of DID/VC
(Issue
#1003)
This feels like a product pitch for a particular implementation.
We could mention a dozen companies implementing - if we did that great.
There is also SSI whitewashing going on in the market.
I would be happy to contribute something that outlines actual
implementations from across the world. I would be more comfortable
mentioning specific companies if referring to them was in relation to
specific projects that are happening with the public sector - balances
it
out to what is happening.
For example both SpruceID and Digital Bazaar are working with the State
of
California for their implementation of VCs (and mDLs).

Kaliya

On Tue, Sep 10, 2024 at 7:22 AM fernandezdiegoh @.***>
wrote:

QuarkID and the Global Adoption of DID/VC Standards
As decentralized identity (DID) and verifiable credentials (VC)
solutions
gain traction globally, QuarkID http://www.quarkid.org/ stands as a
leading example of how these technologies can be implemented in
real-world
scenarios. As an open-source self-sovereign identity (SSI) protocol
https://github.com/ssi-quarkid, under the Apache 2.0 license
https://www.apache.org/licenses/LICENSE-2.0, QuarkID has been
deployed
in various regions of Argentina, providing citizens with a
decentralized
way to manage their identities while interacting with public and
private
services. This has been particularly impactful in regions like Buenos
Aires, where the government has embraced digital identity solutions,
as
well as in other jurisdictions across Latin America, such as Nuevo
Leon
and
Monterrey in Mexico. Additionally, QuarkID is being registered as a
Digital Public Good https://app.digitalpublicgoods.net/a/11563 in
the
DPG Alliance, further solidifying its commitment to open standards and
public accessibility.
The broader adoption of DID/VC standards, as outlined by the W3C, is
not
just a technological shift but a paradigm change in how identity is
managed
globally. Projects like QuarkID reflect a trend toward empowering
individuals through decentralized systems that remove reliance on
centralized authorities for identity verification.
The Importance of Open Standards and Open Protocols
However, the key to the success of such systems lies not only in the
adoption of open standards like the DID <
https://www.w3.org/TR/did-core/>/

VC https://www.w3.org/TR/vc-data-model-2.0/ protocols developed by
the
W3C but in ensuring that these standards are implemented in
open-source
protocols, which are not controlled by any single government entity.
The
importance of deploying these solutions on open, non-permissioned
distributed ledger technologies (DLTs) cannot be overstated.
Governments, while playing a critical role in managing trust
registries
within their governance layer—as outlined in the Trust over IP
four-layer
model https://trustoverip.org/toip-model/—should not have the power
to
restrict access to the decentralized attestation systems that form the
backbone of these digital identity frameworks. By ensuring that these
protocols are governed by the community and free from centralized
control,
we create a system where identities can be verified and validated
without
the risk of governmental overreach or misuse. This model preserves
individual freedom and maintains the open, decentralized nature of the
digital identity ecosystem.
—
Reply to this email directly, view it on GitHub
<

https://github.com/pluralitybook/plurality/issues/1003#issuecomment-2340977627>,

or unsubscribe
<

https://github.com/notifications/unsubscribe-auth/AAW3CC2OU44DNFWKJNX5QCTZV36B5AVCNFSM6AAAAABNZBK4LKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNBQHE3TONRSG4>

.
You are receiving this because you were mentioned.Message ID:
@.***>

—
Reply to this email directly, view it on GitHub<

https://github.com/pluralitybook/plurality/issues/1003#issuecomment-2341046605>,

or unsubscribe<

https://github.com/notifications/unsubscribe-auth/ABIRKSCNRV7DSXLHGSAJW53ZV4ABVAVCNFSM6AAAAABNZBK4LKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNBRGA2DMNRQGU>.

You are receiving this because you authored the thread.Message ID:
@.***>
—
Reply to this email directly, view it on GitHub
<
https://github.com/pluralitybook/plurality/issues/1003#issuecomment-2341109644>,

or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AAW3CC2SUINY6UDCQDITFR3ZV4BPLAVCNFSM6AAAAABNZBK4LKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNBRGEYDSNRUGQ>

.
You are receiving this because you were mentioned.Message ID:
@.***>

—
Reply to this email directly, view it on GitHub<
https://github.com/pluralitybook/plurality/issues/1003#issuecomment-2341145259>,
or unsubscribe<
https://github.com/notifications/unsubscribe-auth/ABIRKSEVQZUT3SKCMIAFETDZV4CJDAVCNFSM6AAAAABNZBK4LKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNBRGE2DKMRVHE>.
You are receiving this because you authored the thread.Message ID:
@.***>
—
Reply to this email directly, view it on GitHub
https://github.com/pluralitybook/plurality/issues/1003#issuecomment-2341196420,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAW3CCZSTZCNCR2KX23SB23ZV4DQHAVCNFSM6AAAAABNZBK4LKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNBRGE4TMNBSGA
.
You are receiving this because you were mentioned.Message ID:
@.***>

I didn't mean it to sound like a product pitch, but maybe my heart got involved. I point out that DID/VC standards are insufficient; we must promote non-government-controlled protocols operating in open, non-permissioned DLTs. In my humble opinion, the fact that Buenos Aires, Salta, and Tucuman in Argentina, as well as Nuevo Leon and Monterrey in Mexico, are pursuing this path is worth highlighting. Thanks for your comments!


Update dllmain.cpp

If you change things, please keep the codestyle the same as mine, so it doesnt look like a mess.


[FLINK-22643][network] Reuse tpc connections between taskmanagers

What is the purpose of the change
Reuse tpc connections between taskmanagers
Brief change log
Reuse tpc connections between taskmanagers.
Verifying this change
Please make sure both new and modified tests in this PR follows the conventions defined in our code quality guide: https://flink.apache.org/contributing/code-style-and-quality-common.html#testing
(Please pick either of the following options)
This change added tests and can be verified as follows:
Added test that PartitionRequestClientFactoryTest#testReuseNettyPartitionRequestClient.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? yes
If yes, how is the feature documented? JavaDocs

@1996fanrui Thanks for your update. The change LGTM. Let's wait for @pnowojski review.

@flinkbot  run azure

@pnowojski It seems the test failure isn't related with this PR.  There is a table ci failure and previous ci is ok. I try to run azure again.

@1996fanrui Maybe rebasing the latest master can make the tests pass.

@flinkbot run azure

Hi @wsry @pnowojski , thanks for your help and review. Currently, the test has succeeded. A pleasant community journey!

Thanks @1996fanrui , can you squash the commits before merging?

done

I will help to merge after all tests pass.

Hi @wsry , do I need rerun CI again? It looks like kafka/gelly's IntegrationTest is failing and should not be related with this PR.

@flinkbot run azure

Merged.


Support changing the unit system

It looks like the unit system is currently read only. We should support setting the unit system and therefore unit conversion. This was skipped in the past because some part of the unit conversion happens in the ACP frontend.

Closed in #567


Border graphical corruption

I'm not sure what caused this.  I will let you know if I find out.

Does this happen every time? I've been testing loading/saving all day and I haven't ever seen this...

I have no idea.  I have also seen it in other screens.

It doesn't happen every time.  In the Civilopedia, clicking Hills, leaving, clicking Hills, etc. shows either no border or this corrupted border seemingly randomly.

This shouldn't happen... I will look into this.

I now have the same issue... working on a solution.

This issue has been solved with my recent graphics/sprites rewrite.


Quilt is considered Fabric for package replacement with ExpectPlatform

Pretty late so Ill elaborate later

This is intentional for code sharing between the "Fabric-like" platforms. That said, there could probably be a setting for that.

this is a bit frustrating


[feature] Homebrew cask for macOS

Is your feature request related to a problem? Please describe.
The installation steps require piping a shell script to bash, which is commonly associated with poor security posture.
https://moonrepo.dev/docs/install#installing
Describe the solution you'd like
Add a Homebrew cask.
https://docs.brew.sh/Adding-Software-to-Homebrew
Describe alternatives you've considered
Inspecting the bash script before executing it.
Additional context
N/A

We had homebrew support (https://github.com/moonrepo/homebrew-tap) and removed it as it's a major pain to support. We most likely won't be bringing this back anytime soon.


🐛 Fix handling validators for non-default values

https://github.com/tiangolo/sqlmodel/issues/230

Awesome, thanks for writing the tests for it too! :cake: :coffee:


0.15.5 release branch

the tests are failing because with all interfaces ipv6 enabled the node fails to start running, it seems


devicetree: gen_defines: Generate lists of children node identifiers

For each node, a list of identifiers of children nodes is generated
in form of:
DT_S_<path_to_node>_CHILD_IDENTIFIERS [, [, ...]]
Signed-off-by: Dominik Ermel<EMAIL_ADDRESS>Purpose of this commit is to generate list of identifiers from dts nodes, to be able to more automatically traverse dts tree.
For example useful to process list of flash partitions.

https://github.com/zephyrproject-rtos/zephyr/pull/24848 has been added on top, as there is currently no reason to review them separately.

not familiar with DT, but wandering is there any plan to implement the Marco to get all the parent nodes given a node? or we already have it? This should benefit power management.

If you want to traverse the DT path back, you can use the DT_PARENT() macro as defined in includes/devicetree.h. It will give you path to the parent of given path to node.
Check the include/generated/devicetree_unfixed.h file in your build directory to get more practical view on how are the PARENT references generated.

not familiar with DT, but wandering is there any plan to implement the Marco to get all the parent nodes given a node? or we already have it? This should benefit power management.

Don't you really want the dependency graph, not just parents.  I know @mbolivar-nordic and @pabigot are thinking about this.  It seems all tied up with how we move forward with struct device as well and work @tbursztyka has been looking at.

We do indeed have the dependency graph, and can produce the set of nodes that a given node depends on, but we need a simple handle to identify the corresponding devices and init sections.  The immediate blocker for that is the ability to represent devices and init routines by integral indexes, which is held up on the device structure rework.

Don't you really want the dependency graph, not just parents.

@galak @zephyrbot I think there are two kinds of use cases for the dependency graph on power management side, the first one is to power on/off all the device nodes following parent-children dependency, maybe a list where every node's parent is ahead of the node self can satisfy this case; the other one is when no traffic on one node and all of it's children are powered off, we can power off this node and then look at his parents,..., some like BFS of graph, not sure how the graph will be structured and represented, but seems easily getting children set and parent set can make the second case work.

not familiar with DT, but wandering is there any plan to implement the Marco to get all the parent nodes given a node? or we already have it? This should benefit power management.

If you want to traverse the DT path back, you can use the DT_PARENT() macro as defined in includes/devicetree.h. It will give you path to the parent of given path to node.
Check the include/generated/devicetree_unfixed.h file in your build directory to get more practical view on how are the PARENT references generated.

@de-nordic so if want to get a node's parent, first I should get node's path identifier, and then get the parent identifier with macro NODE_PATH_IDENTIFIER ## _PARENT (e.g. DT_N_S_cpus and DT_N_S_cpus_PARENT). But at runtime, we are doing things with struct device , how do we get parent with struct device?

how do we get parent with struct device?

If you have PARENT_ID, a node identifier for the node's parent, and you are sure there is a struct device for that node, you can just use device_get_binding(DT_LABEL(PARENT_ID)) in the same way you would any other time you wanted a struct device.
https://docs.zephyrproject.org/latest/guides/dts/howtos.html#get-a-struct-device-from-a-devicetree-node
Node identifiers are all the same; it doesn't matter how you get one.

how do we get parent with struct device?

If you have PARENT_ID, a node identifier for the node's parent, and you are sure there is a struct device for that node, you can just use device_get_binding(DT_LABEL(PARENT_ID)) in the same way you would any other time you wanted a struct device.
docs.zephyrproject.org/latest/guides/dts/howtos.html#get-a-struct-device-from-a-devicetree-node
Node identifiers are all the same; it doesn't matter how you get one.

@mbolivar-nordic thanks for the detail, not familiar with DTS so maybe I didn't describe the question clearly and yes, we can get the struct device by device_get_binding if we have node identifier. But at runtime, we are playing with struct device, in order to get the parent first we should know the child's node identifier following @de-nordic , but do we already have the method to get the node identifier for the given struct device? or we have other ways handling device dependency?

... do we already have the method to get the node identifier for the given struct device? or we have other ways handling device dependency?

No.  That's what we're discussing at https://github.com/zephyrproject-rtos/zephyr/issues/22941#issuecomment-636848156.  I expect a solution in the 2.4.0 development cycle.


Added check limits, plus read out shares from a file

First try, please kindly review. Thanks

Overall a very nice contribution, many thanks! I will give some comments which you may take care of in the original sharemon project (you are now a contributor).

You can make my life as a reviewer :smile:  easier if you use self-contained commits, ie. a single commit for a single purpose, ie. commit#1 "Added limit checks", commit#2 "Read shares from file"
Looking forward to more contributions from you :cat:


Adding matplotlib and pinning numpy in dependencies

Thanks for catching — what was the specific error? I'd like to be able to use NumPy 2 if possible!

You get RecursionError: maximum recursion depth exceeded while calling a Python object when you run from cloudcasting.dataset import SatelliteDataModule, SatelliteDataset, in the 02-data_loader_demo.ipynb. Shifting to numpy < fixed was an easy temporary fix


How to get access to properties?

I want to get the polygon properties even in string format. Is it possible to do this?

You can replace default functions which create markers, lines or polygon with your own functions. Just create them and specify them in parser setup.
These functions are defined as:
typedef MarkerCreationCallback = Marker Function(
LatLng point, Map<String, dynamic> properties);
typedef CircleMarkerCreationCallback = CircleMarker Function(
LatLng point, Map<String, dynamic> properties);
typedef PolylineCreationCallback = Polyline Function(
List points, Map<String, dynamic> properties);
typedef PolygonCreationCallback = Polygon Function(List points,
List<List>? holePointsList, Map<String, dynamic> properties);
typedef FilterFunction = bool Function(Map<String, dynamic> properties);
So write your own function (I name it here myPolygonCreationFunction) which accepts same parameters and then use it when you initialise parser:
GeoJsonParser geoJsonParser = GeoJsonParser(
defaultMarkerColor: Colors.red,
defaultPolygonBorderColor: Colors.red,
defaultPolygonFillColor: Colors.red.withOpacity(0.1),
defaultCircleMarkerColor: Colors.red.withOpacity(0.25),
/// define your function
polygonCreationCallback: myPolygonCreationFunction;
);
All these functions get properties as a map in their arguments. This way you will get direct access to properties which can be converted into the form you would like to have. You can then just call default creation function again or write your customised creation function.
Hope this will help you to solve your problem.
Merry Christmas and a happy new year!


Radiosonde Decoding Compatibility Table

May I suggest including a radiosonde support matrix such as the ones found here: https://github.com/projecthorus/radiosonde_auto_rx#radiosonde-support-matrix
https://github.com/dl9rdz/rdz_ttgo_sonde#radiosonde-support-matrix
I have included an example table but I'm not sure if all the fields are correct
Radiosonde Support Matrix

Manufacturer
Model
Position
Temperature
Humidity
Pressure

Vaisala
RS41-SG/SGP/SGM
:heavy_check_mark:
:heavy_check_mark:
:heavy_check_mark:
:heavy_check_mark: (for -SGP)

Graw
DFM06/09/17
:heavy_check_mark:
:heavy_check_mark:
:x:
:x:

Yep, good point.
I have included a table in the README. There's one in the repo for the new decoder backend, sondedump, but I guess having one directly in this repo doesn't hurt.


Update sbt-typelevel-no-publish to 0.6.5

About this PR
📦 Updates org.typelevel:sbt-typelevel-no-publish from 0.4.20 to 0.6.5
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.typelevel", artifactId = "sbt-typelevel-no-publish" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.typelevel", artifactId = "sbt-typelevel-no-publish" }
}]

labels: sbt-plugin-update, early-semver-major, semver-spec-minor, version-scheme:early-semver, commit-count:1

Superseded by #264.


Build fails on FreeBSD 13+

The build of traffic server 8.1.1 (and probably other versions as well fails on FreeBSD 13.x and newer.
As noted by Brian in the mailing list
FreeBSD 13 added eventfd(2) [1], which means that the check on HAVE_EVENTFD in EventNotify.cc [2] can no longer assume that if you have eventfd(2) you also have epoll.

https://github.com/freebsd/freebsd-src/commit/7a202823aa54ba18c485bdbcf355269bcfee1ab9#diff-7ea785358f7ef658d52a5d985ea53f03c09cd0bfee8e6a7403063774d3dc58a8
https://github.com/apache/trafficserver/blob/3d266379b816227928171d1f07de747f6a9a254b/src/tscore/EventNotify.cc#L34

Unfortunately i still receive that error after the replacement off #ifdef HAVE_EVENTFD by #if defined(HAVE_EVENTFD) && defined(TS_USE_EPOLL)
libtool: compile:  c++ -DHAVE_CONFIG_H -I. -I../../include -D_GLIBCXX_USE_C99 -D_GLIBCXX_USE_C99_MATH -D_GLIBCXX_USE_C99_MATH_TR1 -Dfreebsd -D_LARGEFILE64_SOURCE=1 -D_COMPILE64BIT_SOURCE=1 -D_REENTRANT -D__STDC_LIMIT_MACROS=1 -D__STDC_FORMAT_MACROS=1 -I/usr/ports/www/trafficserver/work/trafficserver-8.1.1/iocore/eventsystem -I/usr/ports/www/trafficserver/work/trafficserver-8.1.1/iocore/net -I/usr/ports/www/trafficserver/work/trafficserver-8.1.1/iocore/aio -I/usr/ports/www/trafficserver/work/trafficserver-8.1.1/iocore/hostdb -I/usr/ports/www/trafficserver/work/trafficserver-8.1.1/iocore/cache -I/usr/ports/www/trafficserver/work/trafficserver-8.1.1/iocore/utils -I/usr/ports/www/trafficserver/work/trafficserver-8.1.1/iocore/dns -I/usr/ports/www/trafficserver/work/trafficserver-8.1.1/include -I/usr/ports/www/trafficserver/work/trafficserver-8.1.1/include/records -I/usr/ports/www/trafficserver/work/trafficserver-8.1.1/lib -I/usr/local/include -I/usr/local/include/tcl8.6 -I/usr/ports/www/trafficserver/work/trafficserver-8.1.1/lib/yamlcpp/include -isystem /usr/local/include -D_GNU_SOURCE -I/usr/include -DOPENSSL_NO_SSL_INTERN -I/usr/local/include -std=c++17 -g -pipe -Wall -Wno-deprecated-declarations -Qunused-arguments -Wextra -Wno-ignored-qualifiers -Wno-unused-parameter -fno-strict-aliasing -Wno-invalid-offsetof -mcx16 -O2 -pipe -fstack-protector-strong -isystem /usr/local/include -fno-strict-aliasing -isystem /usr/local/include -c EventNotify.cc  -fPIC -DPIC -o .libs/EventNotify.o
EventNotify.cc:37:10: fatal error: 'sys/epoll.h' file not found
#include <sys/epoll.h>
^~~~~~~~~~~~~

Sorry my bad the autoconf script always defines TS_USE_EPOLL, you need to do:
The easiest fix is:
sed -Ei 's/#ifdef HAVE_EVENTFD/#if defined(HAVE_EVENTFD) \&\& TS_USE_EPOLL == 1' src/tscore/EventNotify.cc

That should fix it, but that whole class is kinda ridiculous anyway. Using eventfd + epoll in this way is overkill, the ink_condwait methods should be preferred for many reasons as they solve the same problem:

ink_condwait and friends will wrap into pthread_cond_(timed)wait which are as the name implies posix compliant.
When using pthread_cond_wait In the case of a signal before a wait no syscall is ever required on most platforms, ie. linux uses futex(2) on contention but it will check the state in userspace before making a syscall.
Using eventfd(2) in this way doesn't make sense as you're never acutally using the FD with anything other than this epoll fd.
Even if you choose to use eventfd(2) in this way it should probably use poll(2) as it's posix compliant, whereas epoll is linux specific.

Eventfds make sense in situations where you have an existing pollfd / epollfd / etc where you want to tack on some event notification, when you're creating an eventfd to use only with poll/epoll/etc there usually is a better way.
My suggestion is: just yank out all of this eventfd / epoll code and make it use ink_cond_wait/ink_cond_timedwait and be done with it.

Yah sorry you need to do the same for the header file:
sed -Ei 's/#ifdef HAVE_EVENTFD/#if defined(HAVE_EVENTFD) \&\& TS_USE_EPOLL == 1' src/tscore/EventNotify.{cc,h}

Someone want to make a PR for this? :-)

Yah I'll do it
On Wed, Apr 7, 2021, 14:04 Leif Hedstrom @.***> wrote:

Someone want to make a PR for this? :-)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/apache/trafficserver/issues/7656#issuecomment-815262049,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAHHNGM2GV36JRQCPPW4FVLTHTCFPANCNFSM42CXW36Q
.

@bgaff
Any progress regarding this issue?

Sending pull request right now.

Thanks!


Support acceptsFirstMouse prop (#531)

Please select one of the following

[ ] I am removing an existing difference between facebook/react-native and microsoft/react-native-macos :thumbsup:
[ ] I am cherry-picking a change from Facebook's react-native into microsoft/react-native-macos :thumbsup:
[x] I am making a fix / change for the macOS implementation of react-native
[ ] I am making a change required for Microsoft usage of react-native

Summary
Presently in RN macOS, clickable views (buttons, etc.) require two clicks when that window is not in the foreground. This counter to the typical behavior on macOS where controls will default to accepting the mouse event even when in the background (and simultaneously bring to the foreground unless the command key is held).
Fixes #531
Changelog

[macOS] [Added] - acceptsFirstMouse prop on View, Pressable, and Touchable* components
Test Plan
Confirmed in RNTester that we can successfully recognize clicks on buttons while the window is in the background, and this simultaneously brings the window to the foreground.
Microsoft Reviewers: Open in CodeFlow

@alloy I rebased and fixed the typos you caught.

I just merged master again and resolved new conflicts, letting CI run now.

:shipit:


Dexie is not widely known.

This is the biggest issue with Dexie. SRSLY. I've been in search of Dexie for quite a while, but didn't know that it existed. Instead, I've spent many hours evaluating the alternatives mentioned here:
https://github.com/dfahlander/Dexie.js/wiki/Dexie.js#other-competing-indexeddb-wrappers
How can we solve this problem?
Thank you for this great creation.

Logo idea:

Thanks for the logo suggestion. I think it's rather nice.

This looks like a great thread to tag onto. Came across Dexie in my weekend of googling angularjs stuff and when I got to the point of needing client side data, Dexie was in many of my search results. So far based on my 30 minutes with it, two thumbs up! :+1:

@Yuri, could I use your logo? Is it okay if I change background to transparent and text to white? (would work better on the site)

@dfahlander, sure, do whatever you want

@dfahlander maybe I can even attach source .ps file when I get home later today.

@dfahlander here is the source
https://drive.google.com/file/d/0B4txOhp64viVdHg4MTJoaEVnSE0/view

:+1: nice looking site

Thanks @YuriSolovyov , I've picked picked the graphics but kept the current font. Check out if you approve my changes on dexie.org

Ps. if you're on mobile, you can't see it because I hide it on small screens because the margin looked to bad there.

@dfahlander header icons looks good, but favicon feels cut off (right side of letter D)

@dfahlander how about this:

Thanks, much better!

Featured in Progressive Web Apps across all frameworks - Google I/O 2016

I created a demo site which includes the docs from the wiki under http://dexie.flexisitegen.com/docs/Home . There are a number of broken links because not every wiki link matches a file name and I didn't try to convert the links to match the files but I guess for a demo it is good enough.
If this is a wanted change, I can create a PR for https://github.com/dfahlander/dexie.js-web to add the docs. Assuming that the docs should be on the website, then there is the question of whether the github wiki should continue to exist. If we have docs on the site and the wiki, we will have to decide which docs are the "master" docs. So basically which docs will be updated and which ones will just be created. Depending on that I can solve the links issues and the code highlighting issues (we use for example "js" in the wiki but prism requires "javascript"). Personally I would prefer to just have the docs on the website as I am not a big fan of wikis in general.
As always feedback is welcome :)
As a side note, I think we should also promote the various addons on the website and maybe in the readme. Perhaps under a "Features" section like: "Dexie supports client/server synchronization with Dexie.Syncable" or "You can use dexie-mongoify to have a MongoDB like API with Dexie".

That would be nice, to have the docs on the site. The only thing I would be missing would be the super simple way to update typos etc directly from the page. But maybe this could be accomplished by linking to the github's web based file editor for each file. In that case I'm for moving it to the site entirely and replace each MD file in the current wiki with a reference to the site.
Indeed the addons / derived libs including sync-client must be more aggressively promoted. Dexie's Readme is one good place. Could also link to api docs for addons from the documentation page or include docs as well optionally

@dfahlander fixing typos directly on github should not be an issue, at least not for collaborators. If we write the docs in html then any change you make in the website repo should also be instantly online. If we write the docs in markdown we would have to have a build step. In this case the changes will only be online when you build the site and push the html files. I don't know if we can directly build from within github. Maybe that works with jekyll. So do you want to be able to just edit online and release later or do you want any change to be instantly online?

@dfahlander I am not familiar with jekyll. I used my own tool to build the demo site. It will take me some time to get familiar with jekyll (and github pages) but I can give it a try.

I just pushed a branch I made for some time ago for dexie.js-web. Check it out https://github.com/dfahlander/dexie.js-web/tree/jekyll

Let's follow up discussion on #464

README updated to promote addons in this PR https://github.com/dfahlander/Dexie.js/pull/465
It's just a draft.
Comments?

@dfahlander You should add appropriate github tags to the project. So it is discoverable on GitHub, and can be recommended by GitHub.
Recommended:
database javascript indexeddb offline storage

I only know about the npm keywords that we list in package.json: ["indexeddb", "browser", "database"].  What are the github tags and how do you add them?

@dfahlander  you can do this with the manage topics button under the repository description

Thanks @douglasg14b! Topics now set.

This has been the nicest issue I've ever got <3
But I believe it is time to close it.
Thanks all!


source maps env variable?

    ionic(
      team_id: options[:team_id],
      platform: 'ios',
      prod: true,
      release: true
    )

seems like it produces this command:
ionic cordova prepare ios --release --device --prod
How do I get it to execute with: IONIC_GENERATE_SOURCE_MAP=true which forces ionic to generate sourcemaps.

That looks like an environment variable to be set, correct? So set the env variable (depending on how your operating system does that).

Fair.