安装错误

pip install -r requirements.txt
有下面的错误
ERROR: Could not find a version that satisfies the requirement gm (from -r requirements.txt (line 8)) (from versions: none)
ERROR: No matching distribution found for gm (from -r requirements.txt (line 8))
我先后安装了
brew install imagemagick
brew install graphicsmagick
brew install node
npm install gm
还是不行

gm 是 掘金么

czsc模块安装不了啊


Trying to punch while in grid 0 causes an exception

Repro:

Through some bug or other method (vv doesn't seem to work) get to grid 0
Punch
Behold error

https://pastebin.com/2KWgzzJe

Fixed by space-wizards/RobustToolbox#1188


spec, add test case for pageable, focus on maxpagesize and nextLink

I currently put the test case in payload folder, as part of it tests the nextLink.
Though another part of the test is on maxpagesize query parameter (and emitter's handling of it).

PS: later we may add another case here, as pageable but without nextLink in response. We saw some backend write this (if new service, API would likely advise them to add nextLink just not send it; not able to do this to old service).
@pagedResult
model Page {
  @items
  value: Resource[];
}

Cadl Ranch Contribution Checklist:

[x] I have written a scenario spec
[x] I have meaningful @scenario names. Someone can look at the list of scenarios and understand what I'm covering.
[x] I have written a mock API
[x] I have used @scenarioDocs for extra scenario description and to tell people how to pass my mock api check.

Not sure what's the behavior should look like if both top and maxpagesize are specified ? And is it usually the case that top will be used with skip, I kind of don't see maxpagesize being used with skip a lot ?

My personal understanding of "top" is that is be the max number of resources returned by all these paginations. E.g. if service has 1000, top be 150, maxpagesize be 100, it gets 2 pages, 100+50.
I skip "top" here because there seems pending discussion, and it is not the focus of my test anyway. (and yes, it could be ambiguous with "maxpagesize", from other sources)
"skip" is actually a common one, if services done this via "client side driven" pagination.
https://learn.microsoft.com/en-us/odata/webapi-8/fundamentals/client-driven-paging
I can use "skipToken" instead, though I assume "skip" does not affect our test. For 2nd page, just take nextLink for it.

I've switched to use skipToken for paging, as focus here is not on skip parameter.
Personal understanding of the origin of maxpagesize is from odata preference header (it is query now)
https://docs.oasis-open.org/odata/odata/v4.01/odata-v4.01-part1-protocol.html#_Toc31358876


Fix errors in examples

@mvines some small improvements :)

oops, thanks for these fixes!

If you rebase over 9555474d2a1b6ad07ddda115eea273271523fd45 then the clippy issues reported by CI here should now be resolved

heh one more clippy link in the examples. latest rust update enabled https://rust-lang.github.io/rust-clippy/master/index.html#uninlined_format_args
if you've had enough, I can take over though

ty sir! 🖖🏼


Merge branch '2.x' into 2.5

Description
Merge branch '2.x' into 2.5
Check List

[ ] New functionality includes testing.

[ ] All tests pass, including unit test, integration test and doctest

[ ] New functionality has been documented.

[ ] New functionality has javadoc added
[ ] New functionality has user manual doc added

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #1260 (e96ce68) into 2.5 (6332529) will decrease coverage by 35.56%.
The diff coverage is n/a.

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

@@              Coverage Diff              @@
##                2.5    #1260       +/-   ##
=============================================
- Coverage     98.33%   62.76%   -35.57%
=============================================
  Files           346       10      -336
  Lines          8826      658     -8168
  Branches        560      119      -441
=============================================
- Hits           8679      413     -8266
- Misses          142      192       +50
- Partials          5       53       +48

Flag
Coverage Δ

query-workbench
62.76% <ø> (?)

sql-engine
?

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...c/main/java/org/opensearch/sql/expression/DSL.java

...arch/sql/expression/datetime/DateTimeFunction.java

...h/sql/expression/function/BuiltinFunctionName.java

...pensearch/sql/expression/function/FunctionDSL.java

...ssion/operator/arthmetic/MathematicalFunction.java

...n/java/org/opensearch/sql/utils/DateTimeUtils.java

...pensearch/sql/sql/parser/AstExpressionBuilder.java

...pensearch/sql/planner/physical/FilterOperator.java

...ensearch/sql/expression/parse/RegexExpression.java

...h/sql/expression/function/OpenSearchFunctions.java

... and 346 more

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


adding tests for ack_status check from Hydra, check for module in docv2 Solr collection.

thanks for the review @noopurmath3 :)


New make target bundle-for-test

@memodi I think it should fix the issue you have.
I tested this bundle-for-test generation, but not the whole integration with OLM.
It will generate a bundle versioned "0.0.0-main" (operator-sdk requires to have a semver-like version, we can't just use "main")

(PS: if you accept these changes it will automatically update your PR)


Showing the wrong status

[9/24/2019, 7:18:38 PM] [Xiaomi Mi Robot Vaccum 2 Generation] INF getSpeed | roborock.vacuum.s5 | Fanspeed is 100 over miIO "Max" > HomeKit speed 100%
This is what does the logs says, but the Vacuum Cleaner is on charging

FWIW I have the same issue and the only way I've been able to use Siri to start the vacuum is to first tell Siri to stop the vacuum, then issue a second command to her to start it.

@jaredbiehler this is what I also doing right now.
Actually I made shortcut for that, but anyway it look like workaround

Hey! The vacuum cleaner still reports the last speed when it was on. But you should see it’s reporting it’s in OFF status (speed: 100% but OFF). Is that not the case?

Even up to a few days after the vacuum runs the iOS fan icon’s blade is spinning and the tile itself is lit up as though the vacuum is still running. As well, the next time I want to use it I have to tell Siri to turn it off and then, in a separate command, to turn it back on - this is repeatable and happens every time for me. It’s as though the bridge never receives a message that the vacuum made it back to the base.
I do clean the vacuum every time it runs which usually triggers a voice message when I physically pick it up “error 3, try placing the vacuum...”. After cleaning, I hit then home button and the vacuum finds its way back fine - maybe something in that process interferes with the normal dock status message.

This is the logic to get the cleaning status: https://github.com/nicoh88/homebridge-xiaomi-roborock-vacuum/blob/master/index.js#L482
It could explain false negatives. But that’s weird that it gives false positives

I'm running the latest. If I get a few minutes this weekend I'll try to see if I can't figure out how to generate debug messages and I'll share the log(s).

@jaredbiehler any findings?

I’m having the same issue for a couple months now. Is there any updates? Thanks!

@ludgats can you find any pattern in the logs when it fails to report it's off? It would be nice to narrow this issue down to something we can tackle.

[Homebridge] }
Not sure if this helps..
[Homebridge] [12/27/2019, 20:30:57] [Vacuum] ACT setCleaning | roborock.vacuum.s6 | Stop cleaning and go to charge.
[Homebridge] [12/27/2019, 20:31:09] [Vacuum] ERR setCleaning | roborock.vacuum.s6 | Failed to set cleaning to false Error: Call to device timed out
[Homebridge] at retry (/home/hoobs/.hoobs/node_modules/@hoobs/miio/lib/network.js:493:18)
[Homebridge] at /home/hoobs/.hoobs/node_modules/@hoobs/miio/lib/network.js:506:8 {
[Homebridge] code: 'timeout'
[Homebridge] }

Ha! So the problem is a network timeout?
Maybe the robot was at a place where the WiFi signal is weak?
What was the behaviour? Did it fail to stop? Or did it successfully stop and go to the dock but homebridge won’t register the change?

If I manual push stop in the home app everything stops as intended. If it finishes the cleaning cycle it going back to the duck but the fan speed still shows spinning. If I ask Siri to stop cleaning it also goes to the dock but still shows as cleaning which makes it an issue the next time I try to run the vacuum.
This happens every time. The wifi is very strong so I don’t think it’s that.
Is there anything else I can provide?

Same problem. I have a Mesh network and I imagine it changes antenna during cleaning. Could some reconnection be added to the network?


ChefDK 0.5.1 knife Needs STDERR Redirection for Cookbook Version Selection Deletion

Zendesk 4209
Windows 7
ChefDK 0.5.1 / Chef Client 12.3.0
As a customer using Windows 7, I need the choice among deletion of multiple cookbook versions to work correctly.
Workaround:  I can redirect STDERR to a file and input the correct numeric selection and the desired cookbook is deleted.

Moved to https://github.com/chef/chef/issues/3379


mssql performance problem

Hi;
Same data is uploaded to postgre and microsoft sql db. When I'm trying to download data with polars (they are using connector-x), download duration is very different for postgre and mssql. With Postgre it is downloading data within 3 seconds but mssql takes nearly 24 seconds.
Is there any known performance issue for mssql?

Hi @hakantekbas,
We actually also see the performance difference between postgres and mssql in our test (https://github.com/sfu-db/connector-x/blob/main/Benchmark.md). But the difference is basically 2x instead of 8x in your case. Btw, we are using the official docker image for both postgres and mssql.
May I ask what's your query look like? Also if it it possible, can you show the log by setting the environment variable RUST_LOG before import connectorx like this:
import os
os.environ["RUST_LOG"]="connectorx=debug,connectorx_python=debug"
import connectorx as cx

df = cx.read_sql(db_url, query, return_type="polars")

It will help to identify which procedure takes most of the time.

I noticed MS SQL was the slowest for me as well.
The results of a query which is "select top 100000 * from table" from a pretty big table (couple hundred million rows) was about 2 minutes.
1min 50s ± 0 ns per loop (mean ± std. dev. of 1 run, 1 loop each)
[2021-12-20T13:08:33Z DEBUG connectorx_python::arrow] Running dispatcher
[2021-12-20T13:08:33Z DEBUG connectorx::dispatcher] Fetching metadata
[2021-12-20T13:08:34Z DEBUG connectorx::dispatcher] Do not need counts in advance
[2021-12-20T13:08:34Z DEBUG connectorx::dispatcher] Allocate destination memory: 0x202
[2021-12-20T13:08:34Z DEBUG connectorx::dispatcher] Create destination partition
[2021-12-20T13:08:34Z DEBUG connectorx::dispatcher] Start writing
[2021-12-20T13:10:23Z DEBUG connectorx::dispatcher] Finalize partition 0
[2021-12-20T13:10:23Z DEBUG connectorx::dispatcher] Partition 0 finished
[2021-12-20T13:10:23Z DEBUG connectorx::dispatcher] Writing finished

Same query with turbodbc (fetchallarrow()):
1min 19s ± 0 ns per loop (mean ± std. dev. of 1 run, 1 loop each)
It was faster when I used a partition column, but still felt slow. In comparison, Postgres is a lot faster than a mirror query using turbodbc.


wifidos.py help needed

hi
i am having the same problem when i run program it says scanning but no ap are seen can you advise thank you john

Hi John, can you please let me know which WiFi adapter you're using? Also please see this video https://youtu.be/UA-IJ8DWh_8 and confirm that your adapter supports monitor mode and injection.

Hi everybody, it seems like not every adapted is renaming itself to "wlanxmon". My AWUS036ACH  kept original name after enabling monitoring mode. I removed every + "mon" part in script and that fixed my issue.

@FromMun will be uploading a new script that doesn't use airmon-ng to set the adapter in monitor mode, and it should then always keep the same name.


Unexpected relay "connection" modification

Latest version of current package (v3.0.0) contains the following code:
https://github.com/spiral/goridge-php/blob/2ddd4d0257c28268111e042b7b8c60ca6d6606cf/src/Relay.php#L40
Note the strtolower($connection) - it changes, for example, socket path from unix:///tmp/justForTest.sock to unix:///tmp/justfortest.sock. I think this is not normal, right? For the linux-based systems file path is case sensitive.

Hmm... No, this line does not change the path.
This line takes the DSN in lower case in order to check the correctness of the its format.


Add support for es6 default import

I was wondering if it would be possible to add module.exports.default = auth; to add support to the default es6 style import import auth from "basic-auth"
Thanks

For background, see https://github.com/types/npm-basic-auth/pull/1 and https://github.com/typings/discussions/issues/32. Deferring to @dougwilson's opinion as mine has been stated elsewhere, but I can elaborate if needed.

After further discussion with @blakeembrey (in https://github.com/types/npm-basic-auth/pull/1) I came to the conclusion that while useful, still to many variables on the implementation of es6 in nodejs are left open, that could require the removal of the default export.


How can I use graphman to delete subgraph

I'm running a local node by build raw code, I want to delete some subgraph and stroe in the postgres. After saw some issues committed by others , I konw the graphman command, but I can't find any document about where and how to use it, I can not find the entrance.
Could someone help me, thanks!

Hi @bijianing97! You can use graphman --config <CONFIG> drop [OPTIONS] <DEPLOYMENT>. graphman --help is quite helpful, when you can't figure out how to do something.

Is this helpful? If so, feel free to close this issue.

Thanks both, closing now!


Typo in example?

https://docs.microsoft.com/en-gb/azure/frontdoor/front-door-faq#how-do-i-lock-down-the-access-to-my-backend-to-only-azure-front-door
The first example contains an underscore for frontend host C.
Bullet 4 shows the hosts that should be displayed, and instead the underscore is api.contoso.com.
I didn't understand what the underscore in the config was for, I expect it to be a typo?

Example – let’s say your Front Door config has the following frontend hosts contoso.azurefd.net (A), www.contoso.com (B), _ (C), and notifications.contoso.com (D). Let’s assume that you have two backends X and Y.
Backend X should only take traffic from host names A and B. Backend Y can take traffic from A, C, and D.
So, on Backend X you should only accept traffic that has the header 'X-Forwarded-Host' set to either contoso.azurefd.net or www.contoso.com. For everything else, backend X should reject the traffic.
Similarly, on Backend Y you should only accept traffic that has the header “X-Forwarded-Host” set to either contoso.azurefd.net, api.contoso.com or notifications.contoso.com. For everything else, backend Y should reject the traffic.

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

ID: f7be424c-f540-a753-6ecc-6ff3913368d5
Version Independent ID: dc80b25f-374d-8775-16e7-ae7d57b4b94f
Content: Azure Front Door Service - Frequently Asked Questions
Content Source: articles/frontdoor/front-door-faq.md
Service: frontdoor
GitHub Login: @sharad4u
Microsoft Alias: sharadag

@jeroenwo , Thank you for your feedback. We will investigate and get back to you shortly.

PR: https://github.com/MicrosoftDocs/azure-docs-pr/pull/100896


Host kernel version check for SRL

Check the host kernel version and compare it to the SRL required minimum version.
If the minimum requirement is not met, we log a warning.

implementing #1389


Organizations created as individual profiles

For an unrelated reason I was manually cleaning a bunch of data and about 15% of this list of user type profiles actually represented organizations. Our onboarding workflow is not succeeding enough at guiding people to create the right profile type.
Who is your user?
A person representing an organization, such as a vendor who will submit expenses to a Collective or a financial contributor.
What are they trying to achieve?
Setting up a profile on Open Collective for the first time.
How are they currently doing this?
They don't select the Organization profile option and instead create an individual profile named for their organization.
This isn't a total blocker for the user, unless they ever want to use the platform as themselves as an individual or manage multiple organization profile, but it's a real pain for the Host, who relies on data accuracy for stuff like compliance and tax queries. As a Host admin it's really helpful if the right profile types are used. Users who meant to create orgs but create individual profiles instead also miss out on org features, and don't get the proper onboarding email sent to them.
P3 high frequency, low impact

These signup flows have changed a lot in the past few years. When were these profiles created? The issue mentions the expense flow, is it the only one or are we also talking about the contribution flow and potentially others?

This particular issue was motivated by doing a worker classification review for OCF, where I looked at all individuals who have been paid over a certain threshold, and found that 15% of the list (which only included individual profiles) were actually organizations. So I don't know exactly how these profiles were created, but they were all in relation to submitting expenses. There very well could be other outcomes for profiles created in other contexts.


bad discovery cluster:

When testing the latest release (2.0.3) for the issue reported in #2297, I am seeing a new error:
Feb 16 08:54:26 VA1ACHMVP01 systemd[1]: Unit etcd.service entered failed state.
Feb 16 08:54:26 VA1ACHMVP01 systemd[1]: etcd.service: main process exited, code=exited, status=1/FAILURE
Feb 16 08:54:26 VA1ACHMVP01 etcd[10602]: 2015/02/16 08:54:26 etcd: bad discovery cluster: <nil>
Feb 16 08:54:26 VA1ACHMVP01 etcd[10602]: 2015/02/16 08:54:26 etcd: stopping listening for peers on http://<IP_ADDRESS>:7001
Feb 16 08:54:26 VA1ACHMVP01 etcd[10602]: 2015/02/16 08:54:26 etcd: stopping listening for peers on http://<IP_ADDRESS>:7001
Feb 16 08:54:26 VA1ACHMVP01 etcd[10602]: 2015/02/16 08:54:26 etcd: stopping listening for client requests on http://<IP_ADDRESS>:4001
Feb 16 08:54:26 VA1ACHMVP01 etcd[10602]: 2015/02/16 08:54:26 etcd: stopping listening for client requests on http://<IP_ADDRESS>:4001
Feb 16 08:54:26 VA1ACHMVP01 etcd[10602]: 2015/02/16 08:54:26 discovery: found 2 needed peer(s)
Feb 16 08:54:26 VA1ACHMVP01 etcd[10602]: 2015/02/16 08:54:26 discovery: found peer c941b1bd3872caf in the cluster
Feb 16 08:54:10 VA1ACHMVP01 etcd[10602]: 2015/02/16 08:54:10 discovery: found 1 peer(s), waiting for 1 more
Feb 16 08:54:10 VA1ACHMVP01 etcd[10602]: 2015/02/16 08:54:10 discovery: found self 9674d30268039d3e in the cluster
Feb 16 08:54:07 VA1ACHMVP01 etcd[10602]: 2015/02/16 08:54:07 discovery: during waiting for other nodes connection to https://discovery.etcd.io timed out, retrying in 2s
Feb 16 08:53:08 VA1ACHMVP01 etcd[10602]: 2015/02/16 08:53:08 discovery: found 1 peer(s), waiting for 1 more
Feb 16 08:53:08 VA1ACHMVP01 etcd[10602]: 2015/02/16 08:53:08 discovery: found self 9674d30268039d3e in the cluster
Feb 16 08:53:07 VA1ACHMVP01 etcd[10602]: 2015/02/16 08:53:07 etcd: listening for client requests on http://<IP_ADDRESS>:4001
Feb 16 08:53:07 VA1ACHMVP01 etcd[10602]: 2015/02/16 08:53:07 etcd: listening for client requests on http://<IP_ADDRESS>:4001
Feb 16 08:53:07 VA1ACHMVP01 etcd[10602]: 2015/02/16 08:53:07 etcd: listening for peers on http://<IP_ADDRESS>:7001
Feb 16 08:53:07 VA1ACHMVP01 etcd[10602]: 2015/02/16 08:53:07 etcd: listening for peers on http://<IP_ADDRESS>:7001
Feb 16 08:53:07 VA1ACHMVP01 etcd[10602]: 2015/02/16 08:53:07 no data-dir provided, using default data-dir ./mvp01.etcd
Feb 16 08:53:07 VA1ACHMVP01 systemd[1]: Started Etcd Server.
Feb 16 08:53:07 VA1ACHMVP01 systemd[1]: Starting Etcd Server...

This is a new cluster using the public discovery service.  No data-dir is created before the application dies, so I have no logs to provide.  This is a 2-node test cluster in case that makes a difference.

@colebrumley Can you provide the command line arguments you gave to the etcd members (all of them)?

I called etcd from a systemd unit with the following args:
/usr/bin/etcd \
 -advertise-client-urls=http://${CLUSTER_IP}:4001,http://<IP_ADDRESS>:4001 \
 -listen-client-urls=http://${CLUSTER_IP}:4001,http://<IP_ADDRESS>:4001 \
 -initial-advertise-peer-urls=http://${CLUSTER_IP}:7001,http://<IP_ADDRESS>:7001 \
 -listen-peer-urls=http://${CLUSTER_IP}:7001,http://<IP_ADDRESS>:7001 \
 -name=${NODE_NAME} \
 -discovery=${DISCOVERY}

The only differences between the two nodes are the NODE_NAME and CLUSTER_IP

@colebrumley You gave duplicated advertise-peer-url across the cluster.
Please check the doc at https://github.com/coreos/etcd/blob/master/Documentation/configuration.md#-initial-advertise-peer-urls.
We will improve the error message.

Ah I see it now, thanks for the quick reply!

@colebrumley The wrong error message is also fixed at #2320.


Stop pretending to support Kubernetes 1.17

At some point we lost the ability to test against Kubernetes 1.17; let's stop pretending to support it (it reached EOL on 2021-01-13).
Signed-off-by: Stephen Kitt<EMAIL_ADDRESS>

@skitt should we also update this? - https://github.com/submariner-io/subctl/blob/91a438f8e461da2536e966771fffb4319cc7d08c/pkg/version/version.go#L35

@skitt should we also update this? - https://github.com/submariner-io/subctl/blob/91a438f8e461da2536e966771fffb4319cc7d08c/pkg/version/version.go#L35

Yes, see https://github.com/submariner-io/subctl/pull/446


Expression generator: introduce uniforms to hold known values

Having some known vaues in uniforms (so that they are unknown to the shader compiler) will help make programs harder to statically optimize away to nothing.

Add a command line option, --max-uniforms, setting the maximum number of allowed uniforms (default: 10).

As well as being able to introduce new global and local variables, allow the expression generator to introduce known value uniform variables.  In this case, the type of the variable should be a BasicType (and not BasicType.Bool).

For now, do not allow matrix uniforms either, but file an issue and a TODO to support them in the future (the reason is that Amber currently has some problems with matrix uniforms).

A uniform with a known value should have the known value added to PipelineInfo.

Idea: add uniforms with no maximum, and then prune uniforms later to turn some of them into normal global variables.

Fixed via #693.


Make this crate no_std

I am interested in using this crate in a no_std application. The std imports in this crate could be made either entirely optional or replaced. I could implement this behavior if desired.

Can you make a PR for this?

Yes I can, I'll do it tomorrow


Set up routing for Task

User Story:
As a developer, I want to create the endpoints for Tasks so that requests from front-end can be processed.
Acceptance Criteria:

Add CRUD operations for Tasks into router.js
Pass unit tests

Why is the feature required?
Routing needs to be set up to process requests from front-end and to manage the storage of data in the database
Describe the solution you'd like
Create endpoints for creation, read, update and deletion for Task
Additional Context:
Depends on Issue#40
Refer to the README in the backend directory for what endpoints should be created.

@tnzhu is there any existing schema/model for these Tasks?

@tnzhu is there any existing schema/model for these Task?

Yup, @emzoo16 is still working on the schema, so we're waiting for that to be done before creating the routes/endpoints for anything related to Task

@tnzhu is there any existing schema/model for these Task?

Yup, @emzoo16 is still working on the schema, so we're waiting for that to be done before creating the routes/endpoints for anything related to Task

cool, thanks

@shane-dp @jonathanvenema98 how is this going? If you want some help or someone to look over what you've done so far, feel free to create a pr and just make a note that it is still WIP

API for Users seems to be working fine
Currently stuck on testing out the scheduling API, specifically the ones with params (':username') attached to the end of it.
Specifically, if anything is passed that is not the ':id', I don't know how to use this further, ie return all schedules that contain the same user.

@jonathanvenema98 are you having problems with dealing with the db itself or the payload? anyway, might be a good idea to create a pr on what you've done so far and i can help

#108
#109
I've thought that using promise class to handle connections to db, as it is async operations. Promise object is so much natural to js and to humans.


Render attachments in examples tables. Closes #1173

This is a fix for #1173.
Unexpanded:

Expanded:

Is it a problem that the image takes the full width? It's collapsed by default.
BTW, my change in the CCK seems to have triggered a test failure in json-formatter - I need to investigate that.

Is it a problem that the image takes the full width? It's collapsed by default.

Yeah I think that's a fair point, you're opting into it. Sold!


Import of netlify-cms-app unconditionally calls init

This may be related to the closed and stale issue #1908.
Describe the bug
The beta docs show that you can manually init and that the passed in config will override the values in config.yml if you set window.CMS_MANUAL_INIT = true before importing CMS.
This was true at one time, but the check for CMS_MANUAL_INIT seems to have been lost as the netlify-cms package got refactored into multiple packages.
Because of this, when manually calling CMS.init({...}), things have already been initialized and you cannot change the backend, for example.
To Reproduce

In CMS.tsx (typescript version), add these lines:

window.CMS_MANUAL_INIT = true;
import CMS from "netlify-cms-app";
const configOverride =
    window.location.hostname === "localhost"
        ? {
              config: {
                 local_backend: true,
                 backend: {
                      name: "proxy",
                      proxy_url: "http://localhost:8081/api/v1"
                 },
              },
           }
        : {
              config: {
                  local_backend: false,
                  backend: {
                       name: "github",
                       repo: "whatever/website",
                       branch: "master",
                  }
              },
          };

CMS.init(configOverride);

In config.yml, remove all mention of backend or local_backend.
In this variation, when setting the backend in the override, you'll get a Error: config should have required property 'backend' error. If you just do the local_backend bit, you get a weird mix of behaviors.

In any case, there doesn't seem to be a (documented) way to suppress the automatic running of init() on import.
Expected behavior
I should be able to have dynamic portions of configuration and to suppress the automatic import so I can manually call it with config overrides.
Applicable Versions:
I'm using these:

Netlify CMS version: netlify-cms-app 2.12.13, netlify-cms-core 2.27.0
Git provider: GitHub or local proxy for devs
OS: Mac
Node.JS version: 12.16.1

CMS configuration
Don't think this matters.
Additional context
I couldn't definitively figure out where this was introduced as the code handling CMS_MANUAL_INIT bounced around a few times.

I'm going to close this. The issue was not coming from netlify-cms, but from gatsby-plugin-netlify-cms which needed a manualInit: true option. Sorry for the bother.

Although it's worth noting that the documentation on the beta page is still outdated...

Thanks for reporting the issue and solution!
On a side not, you don't need to put local_backend: true behind a condition to test for localhost - the CMS handles that already:
https://github.com/netlify/netlify-cms/blob/5bbaf41f73c0debf31636dd38fd536268ae2c0f5/packages/netlify-cms-core/src/actions/config.js#L189


Use AbortAllOtherCommunicationOnFabric in RemoveFabric.

This prevents establishment of new sessions for the fabric, and shuts down other
communication on the sessions that do exist, which our old setup did not use to
do.
Fixes https://github.com/project-chip/connectedhomeip/issues/9642
Problem
Non-spec-compliant session teardown on RemoveFabric.
Change overview
Make it spec-compliant.
Testing
Manually tested that if I have a command in flight when RemoveFabric happens, on either the same session or a new one, things get canceled correctly.

Might be good to actually add a test that has a subscription previously setup on the session, and then you call RemoveFabric, and ensuring that the subscription is not responsive.
You could setup two fabrics, and issue a write on the second, functioning fabric and see if the report gets generated to the subscription on the now, expired fabric. This would ensure a faster test than actually waiting for the sub to fail (which can take some time).
You could then also read out the fabricsList from the op-creds cluster after that to validate that it indeed has gone away.
Not sure how easy it is to add this kind of test in YAML, but this is pretty straightforward in the Python side.
See similar tests I'm adding here.

@mrjerryjohns I'm happy to look into better tests here as a follow-up...


Add basic documentation of the CSRF validator

Signed-off-by: Matthew Setter<EMAIL_ADDRESS>

Q
A

Documentation
yes

Bugfix
no

BC Break
no

New Feature
no

RFC
no

QA
no

Description
This PR updates the documentation to add core documentation of the CSRF validator.
It includes the essentials of:

An introductory description
The additional required packages
The supported options
A basic usage example

@settermjd
Please use the 2.14.x branch for this pull request.

Closing in favour of #100.


Feature: Show head & base ref, cap markdown headings to h4

Added the base and head branches. Found myself losing context sometimes & to avoid going between github & teamwork, I'd rather have the branch information in teamwork itself.
Also added the base ref, useful when working in a long standing feature branch
Finally, I've capped all headings to h4 , as the headings in teamwork's markdown are quite big

It looks good to me, but I'm assuming you ran the bash scripts locally and made sure sed is doing what you want it to? 😅

act/docker is acting up actually... 2 secs

Yep so act has a bug right now, tested the event directly

Good enough for me! 👍

Yep so act has a bug right now, tested the event directly


Licence for repo

Hey this library is really nice, would you consider adding a license to it?

Thanks for mentioning,  license has been added.

Nice, thanks :)


Bump base etc.

This PR:

Updates base and other dependencies on Spine modules and those from config.
Removes extra version build properties.
Applies proto Kotlin DSL to TypeSystemSpec test suite.

There are some MakeTestFilterHappyTest.java files in this change set. They are needed because of this issue.

Pardon, does not see Kotlin DSL at CI again.

@armiol, @dmdashenkov, I had to rollback usage of Kotlin proto-DSL because it breaks compilation at CI (and locally, if you make a pause between clean and build).
This time it doesn't find DSL code which is part of ProtoData compiler artifact. The code is there. Why it's not visible to the Kotlin compiler in some circumstances is a mystery to me.
Anyway, PTAL.

@alexander-yevsyukov this whole story with DSL is weird to me. Not much changed in our codebase, and yet such a thing was never observed on CI previously. Can it be caused by some unfinished business in the Gradle nightly build that we started using everywhere recently?
Just out of curiosity, let's also try the latest nightly build (see https://gradle.org/release-nightly/).

@alexander-yevsyukov OK, I see that you are using the latest nightly build already. Maybe, that's what breaks stuff? Let's try rolling back to the previously used nightly build (the one we started to use first). Also, if we have any Gradle cache enabled at CI, let's disable it in the scope of GH Actions pipeline.

OK, I see that you are using the latest nightly build already.

I switched to this version in the hope that it's fixed by the latest Gradle code. I can switch back, but I've already tried many different nightbuilds of Gradle when trying to solve this issue in ProtoData. It didn't work.
I guess I need to have a closer look at how we filter KotlinCompile task input in ProtoData. There should be something wrong there.


Move overscoped_allow to experimental

I've decided that the churn this would cause for all of the workspaces that use this lint is not worth it.


add how to use sidebar

Add how to use sidebar

Issue: Add link to "How to Use" sectio  in sidebar

Great! Thank you.
@all-contributors please add @isonnymichael for code


Wrong rendering of multiplication sign

Seen with this setup:

PDF.JS as currently deployed in https://mozilla.github.io/pdf.js/web/viewer.html
Chrome  86.0.4240.198
Windows 10

Repro steps:

Download this document : https://www.dropbox.com/s/k8032s77j5c7l0f/latest-core.pdf?dl=0
Open this document with https://mozilla.github.io/pdf.js/web/viewer.html

Expected behavior:
Multiplication chars should be rendered correctly as here:

Actual behavior:
Instead, the chars are rendered as dots:

The font of these chars appears to be Symbol. I am wondering, if there's a workaround for this situation, like having a fallback font somewhere?

WFM, with PDF.js version 2.7.276 in Firefox Nightly 84 on Windows:

Chrome  86.0.4240.198

This could possibly suggest a Chromium-specific bug, rather a PDF.js one.

The font of these chars appears to be Symbol. I am wondering, if there's a workaround for this situation, like having a fallback font somewhere?

The best solution, to guarantee that fonts always render correctly, is to always embed all font data in the PDF file.

I've the same issue using https://mozilla.github.io/pdf.js/web/viewer.html with firefox nightly on debian but no problem with chrome (debian too). The default fallback font is likely not the same.

It's also broken for me using Firefox 82.0.3 on Arch Linux. The fonts are indeed not embedded properly, and Okular (in which it does work) falls back to another (system) font. The proper solution here is indeed to always embed fonts in the PDF file, otherwise correct rendering is not guaranteed.

Duplicate of #4244


chef-zero not working with 0.2.2

chef-zero does not work with 0.2.2. It neither uses the correct ruby environment, nor is there a link to /opt/chefdk/bin
# No link
$ ls -l /opt/chefdk/bin/chef-zero
ls: cannot access /opt/chefdk/bin/chef-zero: No such file or directory
# wrong ruby env
$ head -n 1 /opt/chefdk/embedded/bin/chef-zero
#!/usr/bin/env ruby

# compare it to:
$ head -n 1 /opt/chefdk/embedded/bin/chef-solo
#!/opt/chefdk/embedded/bin/ruby

# system information
$ rpm -qa|grep chef
chefdk-0.2.2-1.x86_64
$ cat /etc/centos-release
CentOS release 6.5 (Final)

We've since fixed the shebangs. With ChefDK 0.4.0:
$ head -n 1 /opt/chefdk/embedded/bin/chef-zero
#!/opt/chefdk/embedded/bin/ruby

To ensure the correct ruby environment, though, you still need to chef exec or use chef shell-init, otherwise environment variables like GEM_HOME can cause incorrect code to get loaded.


chore(consensus): set proposer address in propose block input

This change is

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#2346  👈 (View in Graphite)
#2345
#2342 : 1 other dependent PR (#2238 )
#2341
#2340
#2339
#2237
#2246 : 1 other dependent PR (#2230 )
#2245
#2244
#2269
#2243
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

crates/sequencing/papyrus_consensus_orchestrator/src/sequencer_consensus_context.rs line 293 at r1 (raw file):

            None => true,
        };
        if condition {

remove, this is not a part of this PR.
Code quote:
    ) {
        let condition = match self.current_height {
            Some(h) => h < height,
            None => true,
        };
        if condition {


Don't add "storages" to INSTALLED_APPS

"storages" does not need to be added to INSTALLED_APPS: https://github.com/jschneier/django-storages/pull/547

Description

Checklist:

[x] I've made sure that tests are updated accordingly (especially if adding or updating a template option)
[x] I've updated the documentation or confirm that my change doesn't require any updates

Rationale

Thanks!


Account for expert parameters when calculating the total number of pa…

…rameters in the model

Overall looks good, only few readability improvement suggestions. I wonder if the profiler has any unit tests at all.

There are unit tests but nothing useful


Document dropdown on-toggle attribute

Added some info to the dropdown menu directive's documentation for the on-toggle attribute

Oh, my bad. Put it in alphabetical order, and put it like onToggle(open), also remove the default thing.

I guess it was already in alphabetical order. Also changed the text a bit.

It was, I am blind sometimes. LGTM


added timezones api

get all timezones and random timezones

please accept with hacktoberfest label

hi @fadkeabhi , Thank you for the PR, this is awesome work. Are you able to update the swagger file with your new endpoints as well.

no, I have just done the coding part.

updated swagger in this commit, please look into it.

@all-contributors please add @fadkeabhi for code

Thank you @fadkeabhi for the work on this ticket :) Happy Hacktoberfest


How to convert the data？

I want to use BRATS 2015 to do the training, but it is mha format, any idea how to convert it into the data that suits deepmedic?

I have a similar problem, the data preprocessing section on the wiki doesn't make it very clear for beginners.
I have found similar libraries that have included preprocessing scripts as a reference to get started:
https://github.com/ellisdg/3DUnetCNN

https://github.com/Kamnitsask/deepmedic/issues/43


Debug and release android builds will not overwrite each other

CI gfxreconstruct build queued with queue ID 233175.

CI gfxreconstruct build # 4578 running.

CI gfxreconstruct build # 4578 passed.

Have recent changes to Android builds made this PR unnecessary?

As far as I can tell, no. Just tried doing assembleRelease -> assembleDebug -> assembleRelease -> assembleDebug and it compiled from scratch all 4 times.


Update os-lib to 0.7.6

Updates com.lihaoyi:os-lib from 0.7.5 to 0.7.6.
GitHub Release Notes - Version Diff
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!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.lihaoyi", artifactId = "os-lib" } ]

labels: library-update, semver-patch

+1

[X] Do all automated continuous integration checks pass?
Yes
[X] Is the update a patch, minor, or major update?
Patch update, only change is added support for Dotty RC3
[X] Is the license still compatible with ASF License Policy?
Yes, still ALv2
[X] Have any changes been made to LICENSE/NOTICE files that need to be incorporated?
No changes
[X] Have any transitive dependencies been added or changed?
com.lihaoyi.geny updated from 0.6.8 to 0.6.9, only change is updaes for Dotty RC3 and bug fix related to http we don't use


Fix to work with Unity

Really leaving this here as a placeholder and to get your input as I hope to do a PR myself when I have some time.
There's only a few things that don't seem to work in Unity at the moment and they all seem fixable. The JSON serializer, the zip library and one more thing I've forgotten :-)

Yeah, I think in order to run it in the stable build of unity (based on .NET 3.5) it is the zip library and JSON serializer, which if I remember right, both weren't introduced properly until .NET 4.5.
The tools can be used in Unity as they are by amending the Scripting Runtime Version to Experimental, I've just done a few tests and that seems to work correctly.
But a 3.5 build would be cool and be an awesome addition to the project :)


Implement stellar uncertainties

Two potential approaches.

Let users provide covariance matrices as extra input.
cons: this adds complexity to the interface. I'm trying to keep front end as simple as possible. This also adds ambiguity to how I interface with scikit-learn's mixture models.

Have covariance matrices encoded into the data array.
cons: Have to reconstruct covariance matrices every iteration. (though, since this is immediately followed by complex overlap integration, this is perhaps not too big a deal)

I elect for the second approach.

Another point of consideration is, how to do component parameter maximisation with stellar uncertainties.
I'd like to retain the performance improvement achieved by only exploring the age, and then deriving the mean and covariance matrix from that.
Cov-free approach
One approach could be: sample the star covariances ~100 times each (perhaps scaled dynamically by dimension of space), and then perform same routine which disregards covariance matrices.
I like this because it lends itself to reuse of code.
But one must consider correctness and performance:

is doing the cov-free approach 100x faster than doing an overlap integral?
is 100 random samples sufficiently accurate? (introduces some stochasticity too which is perhaps undesirable)

OG Chronostar
An alternative approach is to do a full parameter exploration of the component's parameter space: mean (6 pars), age (1 par) and covariance matrix (2 - 21 pars). One would also have to specifically implement which parameters are being explored and how those parameters build the covariance matrix. Truly a nightmare.
Hybrid
A hybrid approach could be to use the cov-free approach to get close to the solution, and then do a complicated full-parameter exploration to fine-tune the parameters.
Decision
For simplicity, I am electing to go for the cov-free approach.

Tim - the "Cov-free" approach really is not physical and should not work. e.g. just because stars in a cluster have uncertain distances, it doesn't mean the cluster is elongated in the distance direction. Covariance matrices will always be elongated in at least one direction (the radial velocity). Incorporating this into Chronostar was always anticipated to be a strength.

Some numbers: for a typical distance of 200pc, at G=13, we anticipate 5 micro-arcsec/year proper motions at Gaia DR5, which corresponds to 5 m/s. Compared to 1km/s for the radial velocity, and ~500m/s for the intrinsic velocity dispersion of a component. The 7 micro-arcsec parallax error corresponds to 0.3pc, which is admittedly not significant compared to the few pc minimum initial group size. But for fainter or more distant components, distance errors are again significant. Radial velocities will not exist for a great many stars we want to base a cluster model on.

Noted.
I acknowledge that fitting this way will "bloat" the component along axes of large uncertainty. I had overlooked that so thanks for pointing that out.
Though it's not obvious to me that this will result in super unrealistic components since any artificial bloating might be countered by intrinsic phase-space constraints. i.e. a component's velocity spread in the RV direction must remain consistent with the current day position spread. I note that this relationship is degenerate with the age, which is bad, but the two other phase-space planes would serve to constrain the age.
I think it's worth pursuing the simpler approach first - it aligns with my overall approach of producing a simple, light-weight chronostar into which more realistic, heavy-weight modules can be substituted in later. And who knows, it might actually yield surprisingly useful results. At the very least it should do a decent enough job at establishing component members, and then these components could be fit to in isolation to get a definite age.

Upon further reflection, I'm not sure what the difference would be.
The "Cov-free" approach is effectively doing a discrete (albeit stochastic) overlap integral.
The issue you pointed out, about a component not being elongated along some axis just because all its members are uncertain, is present in OG (paper 1 and 2) Chronostar too.
So the only differences OG Chronostar has are: 1) more accurate overlap integral, and 2) exploring all component parameters compared to just age.

I am near certain that "cov-free" is not doing a discrete overlap integral. So sampling the stellar covariance matrices is a tangent that I don't believe is publishable. So please prioritise everything else. We can meet with Mark about the math later. I do agree that the point samples have some use, but working with data that have no RV measurements or highly uncertain ones is much more important.

Acknowledged. I'll consider it an unpublishable stepping stone. FYI the cov-free is already implemented (it took less than an hour) so I won't be putting any more time into it.
I think an in depth discussion about missing/uncertain data is needed. Talking with Javier and Marusa,

Sorry, I couldn't help myself. We can say I did this off the clock if you like.
This is comparing relative error of computing an overlap integral by random sampling. The commit above has the script I used.

legend is dimension
nstars = 1_000_000
The average relative error is ~14% for 100 samples, and 1% for 10_000 samples.

A small bug is currently present in fit-chronostar for data with covariances


Automate setting up of the application using Docker Compose

Setting up the application currently is not a very fun process.It can be automated using docker-compose.
Write docker and docker-compose scripts for setting up PHP, MySQL and also creating the initial database and tables in MySQL.

I can get this one

Thanks @lai32290, go ahead with the issue.


Add the build badges to the top-level README.

To see how these look you need to check my branch:
https://github.com/coryan/google-cloud-cpp-spanner/tree/add-build-badges


Exception being thrown when using react strict mode

as reported by @merazgasalim in https://github.com/livekit/livekit-react/pull/79

I just upgraded livekit-client to v1.3.1 but still the same problem.
I'm sure it's related to the double useEffect call. I just downloaded the livekit/livekit-react and made the example app in React
Strict Mode so the bug appears
to reproduce the bug just update the App.tsx in example/src like that
import<EMAIL_ADDRESS>import { HashRouter as Router, Route, Routes } from 'react-router-dom';
import { PreJoinPage } from './PreJoinPage';
import { RoomPage } from './RoomPage';

import React from 'react';

const App = () => {
  return (

  <React.StrictMode>
    <Route path="/room" element={} />
    <Route path="/" element={} />
  </React.StrictMode>
  );
};
export default App;

Here's also the stack Error
Uncaught (in promise) TypeError: _b.reject is not a function at _callee85$ (Room.ts:366:1) at tryCatch (runtime.js:63:1) at Generator.invoke [as _invoke] (runtime.js:294:1) at Generator.next (runtime.js:119:1) at asyncGeneratorStep (asyncToGenerator.js:3:1) at _next (asyncToGenerator.js:25:1) at asyncToGenerator.js:32:1 at new Promise (<anonymous>) at Room.disconnect (asyncToGenerator.js:21:1) at LiveKitRoom.tsx:48:1

additional info by @merazgasalim:

I think that I found the issue!
Calling disconnect() while the room state is in connecting state causes this bug
I updated the useEffect return like that and the bug is fixed
if (roomState.room?.state === ConnectionState.Connected) { roomState.room?.disconnect(); }

sounds like a problem that might best be fixed in the livekit-client package

@merazgasalim I opened https://github.com/livekit/livekit-react/pull/89 to fix the issue and explicitly enabled strict mode for the example app.


Implement LossLess multiterminal HVDC model

Notes on pending capabilities:

[ ] move DC balance constraints to network constructor
[ ] Implement cost function depending on the network model x-ref #926
[ ] Implement System with Loss in the Line and the converter.
[ ] Implement basic AC interactions: Reactive power dispatch and rating limits.


Upload an project.json template to base

While developing the ViUR CLI i noticed, that we are creating a project.json to via the Cli to the project root directory.
I think the project.json is better suited in the viur base project.
Where the developer is not dependent on the viur cli.

Hello @Grashalmbeisser, project.json is already part of viur-base since a while.
For better understanding, here's an annotated version of the current project.json in viur-base, and also an annotation what would be nice to viur-cli.
{
    // On this level are profiles.
    // "default" is a profile, which is inherited by "develop" and "live" and can be customized for particular versions and/or GAE projects. Therefore, every profile can contain all keys from the "default" profile.
    "default": {
        "admin": "4.0.8",  // this is the admin-version *1
        "builds": {  // Here are steps for building for the `viur build` command
            "admin": {
                "command": "viur install admin 4.0.8",
                "kind": "exec"
            },
            "npm": {
                "command": "build",
                "kind": "npm",
                "source": ""
            }
        },
        "core": "3.5.1",  // this is the core-version *1
        "distribution_folder": "./deploy",  // The deploy folder, which is uploaded to GAE
        "format": "1.1.1",  // The file format of the project.json *2
        "pyodide": "0.19.1",  // THe pyodide version *1
        "sources_folder": "./sources",  // deprecated! The source folder for apps; This should be mainted by "builds" individually for every app, and removed from here
        "vi": "not-in-use",  // deprecated! *2
    },
    "develop": {  // "develop" is currently sometimes hard-coded in viur-cli *3
        "application_name": "my-dev-app-viur3",  // The name of the GAE project *4
        "version": "dev-$(user)"  // The version string; Variables can be used here.
    },
    "live": {
        "application_name": "my-live-app-viur3",
        "version": "live-$(year)-$(month)-$(day)-$(hour)-$(minute)-$(second)"
    }
}

Please see my annotations:

*1) Currently, core, admin, vi and pyodide only indicates the version that was installed by the user. But it should define the version to be installed for the project, and should also be maintained by viur-cli:

core will set the pipenv's viur-core-version to the provided version, optimally via e.g. viur install core 3.5.1
admin should install the specified admin version using e.g. viur install admin 4.0.8
vi should install the specified vi version using e.g. viur install vi 3.0.38
pyodide should install the specified pyodide version using e.g. viur install pyodide 0.24.0
Calling viur install should install all specified modules in a specific version
Calling viur install --update should update all installed modules to a specific version

*2) The format setting should not be part of the default-profil. It should be on top.
*3) "develop" should not be a hard-coded name. In case no profile is specified, "default" shall be used.
*4) This should be defaultly set in the default-profile

This is what an optimal project.json should look like, which only installs core and admin. Because no pyodide and no vi is providet, it is ignored. core setting should be mandatory!
{
    "format": "2.0.0",
    "default": {
        "admin": "4.0.8",
        "core": "3.5.1",
        "distribution_folder": "./deploy",
        "application_name": "my-live-app-viur3",
        "version": "live-$(year)-$(month)-$(day)-$(hour)-$(minute)-$(second)"
    },
    "develop": {
        "application_name": "my-dev-app-viur3",
    },
}

I hope this clarifies things a bit. Feed free to move it into an issue in viur-cli as well.

I no longer see any need for action regarding this ticket.

There is a recent project.json in viur-base
The description is in viur-cli

If I am wrong, please just open the ticket again.


Square bracket added to front of prompt of previous command

A square bracket appears at the front of the prompt of the previously executed command. I've only noticed this since I updated to OS X 10.11.1

Hi @plinto, try to disable "Automatically Mark Prompt Lines" from Terminal, like this http://superuser.com/a/975295

Thanks @amalucelli, that solved it


[IM] Implement IM command handler on client side

Problem
https://github.com/project-chip/connectedhomeip/blob/73b308ef6140b368f34447b89cbfca683000a4e8/src/app/CommandSender.cpp#L104
Here is where we process the messages in the IME(command sender). This PR will focus on handling the messages on server side, and there will be another PR later on the client (sender) side.
Currently, the command response is handled silently, however, the upper application may be interested in the command response, thus we need to make it available to applications.
Originally posted by @erjiaqing in https://github.com/project-chip/connectedhomeip/pull/5032#discussion_r585177193

Fixed by #5835


Future TLS work: Encrypt traffic of the gossip ring.

Tracking issue: canonical/cos-lite-bundle#75
Note that encrypting gossip traffic is an experimental feature at the moment (see also: https://github.com/prometheus/alertmanager/issues/3403).

Seems like the "experimental" part of this is TLS in general rather than TLS for gossip. Since we have used TLS for other parts of Alertmanager, we might as well do this also.


pull request for e2e test at 01/17/2017 23:15:11

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Seg/v1.13

Backports Dockerfile from master

breaks this https://github.com/jito-foundation/jito-solana/blob/master/version/src/lib.rs#L70


Added LuckyPandas to build page

Description

Added my new plugin to the builds page
Reason

Hitting off licks in the bando
Black X6, Phantom
White X6, look like a panda
Going out like I'm Montana
Hundred killers, hundred hammers
Black X6, Phantom
White X6, panda
Pockets swole, Danny
Selling bar, candy
Man I'm the macho like Randy

Thanks ❤

Done


participant lease can't be renewed

I don't think a lease duration that is not infinity works. What I observe is if I set a participant's lease duration to (for example) 10 seconds, and set the lease duration announce period to 2 seconds, the lease is never renewed and the participant is removed on the other end when the 10 second timer expires. The first announcement is received, but none of the announcements after that reset the timer.
What I think is happening is something like this:

I set "partitcipant1" lease duration to 10 seconds, announce period to 2 seconds
"participant2" recognizes participant1 and starts the 10 second timer
participant1 sends another announcement after 2 seconds
participant2 receives the announcement as far as StatelessReader::change_received
but in ReaderHistory::add_change, it fails to add the change to the history because (I think) the sequence number has not changed, and the change is discarded at that point.

I think it is correct that the sequence number has not changed, since the spec says the announcement is sent by just calling unsent_changes_reset. I do not know how the receiving end should handle the change, since it thinks it already has that change (since the sequence number is correct), but somehow it should reset the lease duration timer.

Thanks for the report!
I can't seem to reproduce this problem on the latest development version. This will probably not be an issue in the upcoming release, but please let me know if the behaviour resurfaces.

We can't trace the point where this bug went under, but it seems solved now. Thanks!


osu! linux

The readme gives instructions on how to decompile osu!lazer.appimage but not how to recompile it.

Assuming you've successfully extracted the files. You can repackage it using appimagetool


fix: fix poor clusterer performance by running some tasks outside of zone

PR Type
What kind of change does this PR introduce?

[x] Bugfix
[ ] Feature
[ ] Refactoring
[ ] Build or CI related changes
[ ] Documentation content changes

What is the current behavior?
Closes #194
What is the new behavior?
performance is improved
Does this PR introduce a breaking change?

[ ] Yes
[x] No

Unit testing with dummy zones are not trivial, in progress...

Figure out if we can add debounceTime

I will remove ngZone.run in v16. It looks that it's redundant and users can manually run cdr if they need for this event


Added auto-deploy to S3

r=me
On Mar 23, 2015 12:01 PM, Kieran Sedgwick<EMAIL_ADDRESS>wrote:

You can view, comment on, or merge this pull request online at:
https://github.com/humphd/brackets/pull/133
Commit Summary

Added auto-deploy to S3

File Changes

M .travis.ymlhttps://github.com/humphd/brackets/pull/133/files#diff-0 (27)
M package.jsonhttps://github.com/humphd/brackets/pull/133/files#diff-1 (4)

Patch Links:

https://github.com/humphd/brackets/pull/133.patch
https://github.com/humphd/brackets/pull/133.diff

—
Reply to this email directly or view it on GitHubhttps://github.com/humphd/brackets/pull/133.


Add new root_certificate_installation_enabled flag

Provide a general summary of your changes in the title above. You should
remove this overview, any sections and any section descriptions you
don't need below before submitting. There isn't a strict requirement to
use this template if you can structure your description and still cover
these points.
Description
Describe your changes in detail through motivation and context. Why is
this change required? What problem does it solve? If it fixes an open
issue, link to the issue using GitHub's closing issues keywords1.
Has your change been tested?
Explain how the change has been tested and what you ran to confirm your
change affects other parts of the code. Automated tests are generally
expected and changes without tests should explain why they aren't
required.
Screenshots (if appropriate):
Types of changes
What sort of change does your code introduce/modify?

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.
[x] This change is using publicly documented (api.cloudflare.com or developers.cloudflare.com) and stable APIs.

Codecov Report

Merging #1208 (d4dfbb5) into master (c07adfc) will decrease coverage by 0.04%.
The diff coverage is 100.00%.

:exclamation: Current head d4dfbb5 differs from pull request most recent head 0a96951. Consider uploading reports for the commit 0a96951 to get more accurate results

@@            Coverage Diff             @@
##           master    #1208      +/-   ##
==========================================
- Coverage   49.36%   49.33%   -0.04%
==========================================
  Files         128      128
  Lines       12430    12422       -8
==========================================
- Hits         6136     6128       -8
  Misses       4890     4890
  Partials     1404     1404

Impacted Files
Coverage Δ

devices_policy.go
49.47% <ø> (ø)

dlp_profile.go
37.93% <ø> (ø)

dns.go
72.72% <ø> (ø)

teams_accounts.go
53.84% <ø> (ø)

cloudflare.go
67.28% <100.00%> (-0.80%)
:arrow_down:

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


closure compiler duplicates/triplicates code in the compiled results + mixes it up

I'm seeing a weird behavior going on in closure-compiler (tried it with v20230502 and v20230411 with the same results), where the compiled content containes duplicated and triplicated code plus sode sections are mixed up, making the minufied content unusable.
For example this is a section that got messed up:
...${getHealthScoreIconContent(value)}
</div>`};ar dataObject=[];let...

as you can see, "v" from "var" was chopped up, plus the "...${getHealthScoreIconContent(value)}
`}" is placed in the middle of anothe function "ar dataObject=[];let..." that is also defined propely somewhere above
the pre compiled code containes 23k+ lines of code.
The way I'm calling the compiler is like this:
......
String copiledJS = compile("externs.js", "input.js", jsContent);
.......

public static String compile(String ext, String inp, String code) {
        Compiler compiler = new Compiler();

        CompilerOptions options = new CompilerOptions();

        CompilationLevel.SIMPLE_OPTIMIZATIONS.setOptionsForCompilationLevel(options);
        options.setBrowserFeaturesetYear(2019);

        SourceFile extern = SourceFile.fromCode(ext, "");

        SourceFile input = SourceFile.fromCode(inp, code);

        compiler.compile(extern, input, options);

        return compiler.toSource();
      }

I am seeing a similar behavior with CompilationLevel.WHITESPACE_ONLY too.
I won't be able to proved you the code content as it containts sensitive stuff.
Is there a way to see in details what is going on with the compiler? Why it is behaving like this? Any idea?
Thanks

If i will compile just the content of the 2 files containing the 2 methods that were messed up, the issue mentioned above is not visible. But I have to merge all my file and compile them in one go, else I will risk naming conflicts to pop up.

Found the problem. It was caused by my code logic.


Allow configuring the operator via the YAML manifest.

Up until now, the operator read its own configuration from the
configmap.  That has a number of limitations, i.e. when the
configuration value is not a scalar, but a map or a list. We use a
custom code based on github.com/kelseyhightower/envconfig to decode
non-scalar values out of plain text keys, but that breaks when the data
inside the keys contains both YAML-special elememtns (i.e. commas) and
complex quotes, one good example for that is search_path inside
team_api_role_configuration. In addition, reliance on the configmap
forced a flag structure on the configuration, making it hard to write
and to read (see
https://github.com/zalando-incubator/postgres-operator/pull/308#issuecomment-395131778).
This commit allows to supply the operator configuration in a proper YAML
file. That required registering a custom CRD to support the operator
configuration and provide an example at
manifests/postgresql-operator-default-configuration.yaml. At the moment,
both old configmap and the new CRD configuration is supported, so no
compatibility issues, however, in the future I'd like to deprecate the
configmap-based configuration altogether. Contrary to the
configmap-based configuration, the CRD one doesn't embed defaults into
the operator code, however, one can use the
manifests/postgresql-operator-default-configuration.yaml as a starting
point in order to build a custom configuration.
Since previously ReadyWaitInterval and ReadyWaitTimeout parameters
used to create the CRD were taken from the operator configuration, which
is not possible if the configuration itself is stored in the CRD object,
I've added the ability to specify them as environment variables
CRD_READY_WAIT_INTERVAL and CRD_READY_WAIT_TIMEOUT respectively.

Coverage decreased (-0.3%) to 10.86% when pulling ff80fa8b00c7b8089fd2a9b880ab52fca8ef4e44 on wip/operator_configuration_via_crd into d9d2c5cbe562a3bf74e6bdbc7df7a52e232aaacd on master.

👍

Only thing I am missing is the CRD def YAML for manual deployment. I would assume our example then changes to deploy config CRD, followed by default object and then the operator deployment over the earler config map?

This is the eventual plan, although this doesn't need to be part of this changeset. I think nothing stops us from adding the  CRD as a separate PR, to avoid blocking other changes on this one.

:+1:

👍


project pages participant link hack

https://github.com/gbif/portal16/blob/fcd56052c46c9ffbeeff66f815543501134c511c/app/views/pages/resource/key/project/about.nunjucks#L160
Please change the destination to "/participation" instead of "/about"
(fyi @kcopas)

This assumes that there always is a participation tab. But I believe you control this in contentful.


update Open Graph date format

The format of Open Graph dates today (i.e. “2020-08-05 10:06:15 -0500 -0500” from latest ADO episode) is not valid.
Adding a formatter as well as adding both article:publish_date and og:updated_time. Also, using .Lastmod for the updates/modifies instead of .Date.
Signed-off-by: Darin Pope<EMAIL_ADDRESS>

I had some issues in the past using .Lastmod, but they might have been resolved. I'll be happy to merge this one.


PX4FLOW LPE not working: Z is reversed

I am trying to get a stable position estimation using only PX4FLOW but it looks like the Z axis is reversed.
"M1:OPTICAL_FLOW_RAD.distance" is very stable around 1 m (based on sonar)
"M1:LOCAL_POSITION_NED.z" variation is reversed relative to "M1:OPTICAL_FLOW_RAD.distance". See the graph below.

M1:OPTICAL_FLOW_RAD.quality is around 250
LPE_FUSION is 162
I also tried LPE_FUSION = 34 (no baro) and "M1:LOCAL_POSITION_NED.z" stays close to zero.
Firmware version 1.6.0 rc
See also parameters file attached
PX4_param_4-1_params.txt

The graph is fine. Local Z in in NED, so it is reversed. You must have baro enabled, because there are some things hardcoded in the estimator.

Thanks! I got it, because the z is represented in NED (north-east-down) coordinates system the z value is reversed. Is this NED coordinate system "frame NED" or "earth NED"?
Then the main issue is that the M1:LOCAL_POSITION_NED.x and M1:LOCAL_POSITION_NED.y are not consistent. They stay around zero when I walk and the quadcopter few meters forward/reverse and left/right. I do not know how to troubleshoot this issue.
The goal is to get a stable position estimation to be able to go in offboard control mode and to be able to control the quadcopter based on a vision system that runs on a companion computer.

The frame is north, east, down with the projection following the vehicle. The z origin is sea level.
The reason that x and y don't move while you are walking is that land_detector is enabled. You can disable it in (LPE_FUSION) within qgroundcontrol and test it by walking, but then set it back on before you fly. While landed (the logic is throttle below ~40%, or disarmed, and not rotating), it prevents drift when the optical flow is not getting good data and will allow takeoff. There is a hand off when you takeoff from the land detector to the optical flow. If the optical flow doesn't get good data after takeoff, it will attempt to land if in auto, or fallback to altitude control mode if in position control.

Thank you! I will try that.
So when flying higher the LOCAL_POSITION_NED.z should always be negative.
Is LPE_FUSION = 162 the recommended setting for flying LPE with PX4FLOW only?
Should "flow gyro compensation" be OFF for LPE_FUSION?

What parameters should I monitor to make sure that the hand off from takeoff to the optical flow is going well? Is that happend at a fixed altitude?

@jgoppert I tried setting the land detector OFF in LPE_FUSION but it did not make a difference. See the graphs below:

LOCAL_POSITION_NED.x and M1:LOCAL_POSITION_NED.y walking the quadcopter 2 meters south-north back to the origin and then east-west and back to the origin.

For reference this graph is recorded directly connected to the flow camera and walking the quadcopter front-back and left-right.

In fact the LPE_FUSION = 162 means that the "fuse land detector" is off

Is there another means to turn on / off the land detector?
Do you have any troubleshooting suggestions based on the graphs shown above?

I would suggest enabling land detector and gyro compensation and giving it a test-fly in position control. It should work fine.

I always use flow gyro compensation. Make sure the camera is in focus as well.

Thanks! I will turn the flow gyro compensation on. It makes sense. I was just following other recommendations on github.
Is it a good test to align the vehicle facing north and move it forward/backward and observe positive/negative LOCAL_POSITION_NED.x changes, respectively and do the same moving it right/left for positive/negative LOCAL_POSITION_NED.y changes? Is this a good pre-flight test?
I will also try to give it a test flight after that in position control.

Yes.

Yes, you should be able to do that as long as loan detector is off. And
that is what I typically do when running new code or in a new environment
to make sure flow is working.
On Apr 2, 2017 5:07 PM, "Kabir Mohammed"<EMAIL_ADDRESS>wrote:

Yes.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/PX4/Firmware/issues/6957#issuecomment-291015198, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAc6rCrVv6DhYlBrwIrFBtfZFmx5pEGjks5rsA4YgaJpZM4MwrAs
.

Thanks! Is there a way to confirm that the land detector is off other than turning the bit off in LPE_FUSION?

@jgoppert are there other parameters that I should be watching during the pre-flight test?

Make sure you local z looks reasonable. Also, to test px4flow by itself you can just look at local_position topic on px4flow (when plugged into px4flow usb). This estimates position just using sonar on px4flow and the camera. It doesn't have a compass so this is only good for testing (doesn't know if you rotate around z), but I used it all the time to make sure flow is working well independent of the estimator.

@jgoppert, thank you! That makes sense. I tried that, but the question is, when you test the px4flow by itself are looking at x and y or only at z? Is there a x and y parameter that represents the distance moved from the origin? My OPTICAL.FLOW.flow_x and OPTICAL.FLOW.flow_y do not quite make sense (see the graph above).

@tomatac OPTICAL_FLOW.flow_x is confusing for a human to look at. Try looking at LOCAL_POSITION.x, y, z. You can see this by enabling the parameter send_lpos on the px4flow.

@jgoppert  A quick question here. Is there a way to debug px4flow with a tera ranger (or separate range finder than the native sonar? ).

@tuofeichen I typically use a lidar with flow and LPE. I still can debug the flow using its onboard sonar. If that works, the other sensor should give you similar results or better.

@jgoppert yeah I'm just wondering if there's a quick way to directly look at the LOCAL_POSITION topic of the flow even with a different rangefinder. (I desoldered the sonar). the flow probably need to read the i2c bus  in that case, not super critical, no worries!

@tuofeichen Yeah, it is not possible out of the box if you have desoldered it.

@tomatac Are you good closing this now? If you have any other questions we can move it to http://discuss.px4.io/.

I got more data I just recorded per your instructions. I will post in few minutes. The PX4FLOW data looks good but I think that the information is not processed correctly by the PX4 firmware.

@tomatac Please use the new logger, SYS_LOGGER=1, and upload a .ulg file to http://review.px4.io/  The new log format contains a lot more info that is helpful for me to debug your issues.

I connected to the PX4FLOW and set the SYS_SEND_LPOS to 1. That allows the PX4FLOW to temporarily publish LOCAL_POSITION_NED.x y and z values. Great debugging tool! When I walked the quadcopter back and forth couple of meters and the result looks good:

Then I disconnected the micro USB cable from the PX4FLOW and connected to the Pixhawk.
In the same conditions, walking the quadcopter back and forth couple of meters on north-south direction, the results do not make sense:

The graph below is recorded  with the quadcopter just sitting on the ground, and it does not make sense either:

I think this is a bug in the PX4 firmware because the values we get from the PX4FLOW are good.
The issue should be renamed to just: "PX4FLOW LPE not working" (the z is not the problem)
I also changed the LPE_FUSION to 226 (turned the "flow gyro compensation" on) as per your recommendation.
Thank you for your help! Do you have any other troubleshooting suggestions (try a different firmware version, ...)?

I will record a log and post it. Thanks for your help!

@jgoppert see below the link to the log file. In this test I walked the quadcopter south-north and east-west 2 meters in each direction. That is not reflected by the X Y coordinates from the log.
http://review.px4.io/plot_app?log=f6f06538-2452-4e91-adfb-a6e507d4298f
I set the SYS_LOGGER to "new logger" in the QGroundControl but I get ".px4log" log files instead of ".ulg" files.
Is the new logger available in the px4fmu-v2_lpe.px4 firmware?
Do you have any other troubleshooting suggestions? Thanks!

If the graphs (http://review.px4.io/plot_app?log=f6f06538-2452-4e91-adfb-a6e507d4298f) do not gives us an indication on what might be wrong I would like to try a previous firmware that works with PX4FLOW/LPE? I tried 1.5.5 (nuttx-px4fmu-v2-default.px4) and it did not work. What is good stable version for PX4FLOW/LPE? My plan is, if I get the previous version working, then come back and see what is wrong in 1.6.

I flew master a week ago, so I know that it is probably still  working.

Ok. Thanks! Do you have any troubleshooting suggestion? How do we know if the LPE is running based on PX4FLOW and it is not stuck in takeoff mode?

If you can't get it to work with land_detector disabled and walking around, it is best not to try flying it. This is what I do to troubleshoot before I fly. If it is drifting a lot, check your flow quality, it should be around 250. If you can't get your quality that high, you might need lights or try the px4flow firmware branch exposure_for_indoor.

See below the link to a real flight: south and then east - west (2-3 meters)
http://review.px4.io/plot_app?log=a38644bb-865c-4b67-bdb8-e1bebd7aaca9
The position control was rejected.

I had a look at your log.
Flow quality is good:

The sonar from the flow isn't publishing the distance to the px4. It must be the primary distance driver, see code here: https://github.com/PX4/Firmware/blob/master/src/drivers/px4flow/px4flow.cpp#L240
Also, the sonar readings themselves look very poor:

Also, it looks like you have a lot of vibrations, you might need to balance your props or something. Vibrations can also degrade sonar performance.

Thank you! Is the poor sonar readings the cause for sonar not publishing the distance to the px4? I followed the C++ code but I could not determine the possible cause.
Anyway I am going to purchase a lidar sensor. The quality on the sonar does not look good. Does LIDAR-Lite v3 integrate well with the PX4?
How did you get the flow quality graphs form the log file? I tried FlightPlot and it gave me an error loading the log file. I was in process of trying PX4Tools. Thank you again for your help!

Yeah I use px4tools or pyulog in jupyter notebook. Here is an example just using pyulog.
Untitled.pdf

Thanks! I am new to jupiter notebooks but after I read about them and I was planning to start using them in a Docker container (https://hub.docker.com/r/jupyter/). Do you have one that you recommend? Do you know if there is a Docker image that contains the pyulog and px4tool already?
I got the lidar lite and if everything goes ok we should fly it tomorrow.

@jgoppert I got the Lidar Lite 3 installed. The altitude control looks a lot better and the x y position graph looks better. Still the position control is rejected. Here it is one of the flight logs:
http://logs.px4.io/plot_app?log=95cb6bde-d118-4317-aa7b-ca82151c903e
I also got the pyulog on Jupiter notebook working and I can reproduce the graphs that you shared in the pdf file. It would be nice if I can create a notebooks specific for troubleshooting the LPE. I already made a Docker file that is really easy to use and I would like to share the results once I get this working. I am still learning how to extract some of the log parameters (any examples or tips will help here).
The main question remains : Why is the POSITION CONTROL REJECTED? Thanks again for your help!

I tried few more flights but I have the same issue: POSITION CONTROL REJECTED.
See the log below and the file attached:
http://logs.px4.io/plot_app?log=3f14be80-3596-4043-8aa6-dacb749d2b08
LPE_Flight_04-11.pdf
Is there a way to graph the input from the Lidar sensor?
How do I make sure that the LPE considers only the Lidar input and not the sonar sensor?
I still have LPE_FUSION:fuse_land_detector OFF. Can this be the reason the position control is rejected?
Do you have any other troubleshooting suggestions? Thanks!

To help debug this issue, can somebody share a log file of a successful flight where position control was achieved (PX4FLOW + Lidar-Lire, NO GPS). I am looking to compare the parameters and the flight graphs to find out why we are now having issues. I can develop a jupyter notebook to compare the key parameters between logs side by side to make troubleshooting easier.

Sorry I haven't been more responsive, have been on a business trip. I'll
take a look soon and share one of my good logs.
On Wed, Apr 12, 2017 at 3:17 PM, tomatac<EMAIL_ADDRESS>wrote:

To help debug this issue, can somebody share a log file of a successful
flight where position control was achieved (PX4FLOW + Lidar-Lire, NO GPS).
I am looking to compare the parameters and the flight graphs to find out
why we are now having issues. I can develop a jupyter notebook to compare
the key parameters between logs side by side to make troubleshooting easier.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/PX4/Firmware/issues/6957#issuecomment-293679745, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAc6rNhjJ_oOVBKelMH2JKbLXU1w5w3gks5rvSM6gaJpZM4MwrAs
.

@jgoppert Thank you! I learned a lot from this discussion. At issue #7002 @mhkabir mentioned that PWM for Lidar Lite is currently broken". I am not sure what version is he referring to. Do you use the Lidar Lite 2 or 3? I understood that is not a big difference between them.  It would be great to establish a version that works and then see what commit broke the functionality.

@jgoppert Sorry, I have a quick question here. I also use LPE+PX4Flow+sonar, and got drift problem maybe because of the same poor sonar reading. Is it possible to make it work with sonar? Would you please also share a log of PX4Flow+Sonar? Thank you very much!

@nancy03610 and @jgoppert it would be nice to establish a baseline that tells us in what conditions the sonar gives acceptable results. From my testing it really depends on the ground surface. Indoors, with propellers not running the tile flooring get very good results but the carpet gives very poor results. It looks like vibrations and air flow also affects the results. @jgoppert pointed out how poor the my sonar signal was in the graph above and I decided to buy the Lidar Lite (Garbage in, garbage out, I cannot expect magic from the software).

Please see this old PR https://github.com/PX4/Firmware/pull/4806. This is
the last time that I tested with sonar and at that point it was working
well.
Video:
https://www.youtube.com/watch?v=t7s8027uKZ4
Log:
http://logs.uaventure.com/view/beRXQ3uES9ctPkv2H5ymDQ
On Thu, Apr 13, 2017 at 1:44 PM, Toma Tacescu<EMAIL_ADDRESS>wrote:

@nancy03610 https://github.com/nancy03610 and @jgoppert
https://github.com/jgoppert it would be nice to establish a baseline
that tells us in what conditions the sonar gives acceptable results. From
my testing it really depends on the ground surface. Indoors, with
propellers not running the tile flooring get very good results but the
carpet gives very poor results. It looks like vibrations and air flow also
affects the results. @jgoppert https://github.com/jgoppert pointed out
how poor the my sonar signal was in the graph above and I decided to buy
the Lidar Lite (Garbage in, garbage out, I cannot expect magic from the
software).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/PX4/Firmware/issues/6957#issuecomment-293972080, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAc6rPndaG-lt3pkbuniE4hvTRQJe7Fkks5rvl8FgaJpZM4MwrAs
.

@jgoppert that was impressive! The sonar input was not very good on grass but you still achieved a nice stable flight. The raw accel was low.

@jgoppert do you use a PWM lidar now? Is it the Lidar-Lite? Now that I have the Lidar installed I prefer to use it. Could you please post a similar log for a Lidar based flight along with a pointer to the firmware version that worked? I would to start there, confirm that I can reproduce the results and then we can try to see at what point the present master got broken.

I'm now using an sf10a on serial from lightware. I haven't flown without vision recently, so give me some time to get a flight in.

@jgoppert Do you know if the PWM on the Lidar-Lite ever worked well in a specific commit? Also, when you mentioned vision, is that a companion computer that runs vision? Thank you, I really appreciate your help!

The last time I tested that config personally was about a year ago but I'm pretty confident that it is fine. @ecmnet any input? Yes I'm having a companion computer send the vision updates.

@jgoppert tanks. It looks like the pwm was broken on the master. I will watch for an update, try older firmware and report back. Now I am traveling so I will test in about a week.

Let's close this and move to http://discuss.px4.io/


Upgrade Node.js's Support

Maybe we should add 14 and 16 directly? Given that 10 is already out of support (but we probably should only drop it after Karma core drops it) and 12 goes out of support in May.
Originally posted by @devoto13 in https://github.com/karma-runner/karma-chrome-launcher/pull/249#discussion_r806583699

I think this should be a general cleanup across the whole Org's repos. Ofc, this should trigger new major releases for all the maintained repos. WDYT? I have proposed this work as part of my next quarter (i.e. '22Q2) objectives.
We should only support v14 and v16. Do you agree?

Yes, makes total sense to me!


Add evm typegen

Solidity also provides advanced types like structs and enums.
As far as I understand they can appear in logs, so we need to support them as well.

They get converted to other these set of types in abi: spec. So this should cover them

They get converted to other these set of types in abi: spec. So this should cover them

This is encoding. Like, e.g. the set of event params is just a tuple, but we still provide param names.

@eldargab should be good now


USHIFT-1059: fix: rbac generator for topolvm from lvms bundle starting with 4.13

Which issue(s) this PR addresses:
In the ClusterServiceVersion for LVM Operator / TopoLVM within Microshift there are encoded RBAC information for OLM deployments instead of RBAC yamls in the bundled operator.
Since microshift skips this installation through the bundle and uses a custom one based on extracted YAMLs, we have to extract the RBAC out of the CSV and recover the RBAC (Service Account, Roles Role Assignments) as if they were installed through the bundle instead.
This PR creates the necessary changes in rebase.sh which recovers the RBAC information starting with 4.13 of the LVMS operator bundle. It also corrects assets.yaml which references no longer existing files for the rebase and updates it accordingly. Also touches storage.go as the CSI driver now needs to use aggregated roles. (breaks upgrade path, but expected)
Setting to draft until I can successfully test the entire rebase procedure

/test ?

/test test-rebase

/retest

/test test-rebase

/test test-rebase

/test test-rebase

/test all

Synced w/ Jakob on the implementation and code changes earlier today.  All looks good.  The changes have passed the snapshotting tests on the metal-e2e job.
/lgtm


Prefix hostname to config file before committing

This MR prefixes the hostname to the config.xml file commited to git.
For users with more than one OPNSense, all utilising git backup, it is
not neccessarily practical to have one repository or one branch per OPNSense
instance. This MR prefixes the hostname to the config file to enable
more than one config in each repository.

can't accept this as it will break other peoples backups

You're right, my bad. I didn't find the config options for this plugin - if you can point me roughly in the right direction I'll make this configurable.
Would that be acceptable then?

Thanks. Closing this PR until I figure out how to best do this.


Layman's Instructions Needed

Hey there, Roman.  I would love to integrate the bot into our Slack team, but I am not sure I understand all the steps involved.  I added MS Translator to my Live account, but beyond that I am not sure what to do with the ENV file or integration into Slack.  Help, pls?  :)

Hello. Sorry for late response. Take .env.example and rename it into .env and edit it by following explanations of every field in this file. bot_name and bot_token are name and token of Slack bot which you should create. Go here https://redradix.slack.com/apps/build/custom-integration and select the second type of a bot. Follow the instructions to create a custom bot for your team, you'll find a name and token there. Once you added everything into env, continue following instructions in the README to this project.
I'll add this info into the README. Thanks for your interest!


Fix Shift+Key events on X11.

XKeysyms for shifted keypresses are distinct, so include their alternates in the table.
Fixes LaurentGomila/SFML#847
This lets me use keypress events for a game where the player holds shift.

Commit ef96295b42f400a7038625487e6086fe1d85fbfc of the bugfix/altf4_new branch (#825) should fix #847 as well, without the problematic mapping issue @mantognini referred to. If it does, feel free to close this pull request.

@mantognini, @harikattar if you don't mind, I'm going to close this pull request as superseded by #825.

Fine with me. ;)


W3C Validation Failed - Unsolvable CSS validation errors for variables

Version
@nuxtjs/tailwindcss: 6.11.4
nuxt: 3.10.2
Reproduction Link

Any Nuxt 3 project using this tailwind plugin
Steps to reproduce

Create Nuxt 3 project
Add @nuxtjs/tailwindcss plugin
Run npm run generate or yarn generate
Run yarn start or npx serve .output/public
Go to deployment - usually http://localhost:3000
View source for the webpage, search for empty variables like --tw-pan-x: ;--tw-pan-y: ; in <style>.

What is Expected?
W3C valid output is expected.
What is actually happening?
I'm aiming to create a sellable template using Tailwind and I can't lie about the code being w3c validation.
I don't know if it's significant or not in terms of sales, but I atleast hope to aim for creating a w3c valid code.
I have already tested and squashed almost all html validation errors. But yet regardless of what config I use I can't seem to remove CSS variables error. And there are more than 100's of them.

An example can be below:
https://validator.w3.org/nu/?doc=https%3A%2F%2Ftailwindcss.nuxtjs.org
This is validation run for https://tailwindcss.nuxtjs.org/, well regardless of it being tailwindcss plugin documentation site, any site using Nuxt 3 tailwind plugin has the same problem.
The configurations I have tried is below:
For nuxt.confg.ts
  postcss: {
    plugins: {
      autoprefixer: {},
      "postcss-import": {},
      "tailwindcss/nesting": "postcss-nesting",
      tailwindcss: {},
      "postcss-lightningcss": {
        browsers: ">= .25%",
      },
      ...(process.env.NODE_ENV === "production" ? { cssnano: {} } : {}),
    },
  },

  webpack: {
    extractCSS: false,
    optimizeCSS: true,
  },

My tailwindcss.config.js:
export default {
  theme: {},
  plugins: [require("@tailwindcss/typography")],
  content: [
    "./components/**/*.{vue,js,ts}",
    "./layouts/**/*.vue",
    "./pages/**/*.vue",
    "./composables/**/*.{js,ts}",
    "./plugins/**/*.{js,ts}",
    "./utils/**/*.{js,ts}",
    "./App.{js,ts,vue}",
    "./app.{js,ts,vue}",
    "./Error.{js,ts,vue}",
    "./error.{js,ts,vue}",
    "./app.config.{js,ts}",
  ],
};

I would have accepted that this might be a global problem but I have seen Next.js sites using same headless UI and tailwind css yet not have any of these kinds of errors.
Example:
https://swr.vercel.app/
https://validator.w3.org/nu/?doc=https%3A%2F%2Fswr.vercel.app%2F
The site above is using Next.js powered, Nextra (documentation generation site - similar to Nuxt Studio), Headless UI, Tailwind CSS and yet I don't see any variable errors in there.

Thanks for reporting. You're right to point this out; see related https://github.com/nuxt-modules/tailwindcss/issues/806#issuecomment-1936401819. Unfortunately, it would seem that even if these variables are not defined and removed, some styles may break.. maybe the behaviour isn't correct yet, but this needs to be investigated further, so I'll be leaving this issue open for now. 👍

I'll link this issue currently - https://github.com/tailwindlabs/tailwindcss/issues/7121

Is there any way to move inline css into local css file? @ineshbose
I thought switching of extractCSS would do it but it didn't

Is there any way to move inline css into local css file? @ineshbose
I thought switching off extractCSS would do it but it didn't

Yes! Sorry forgot to add.. you can get around this using-

export default defineNuxtConfig({
  experimental: {
    inlineSSRStyles: false
  }
})

Based on the discussion of the tailwindlabs/tailwindcss issue above, I'll close this for now and I encourage discussion over there! 🙂