Rebuild for pypy v2

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Hi! This is the friendly automated conda-forge-linting service.
I was trying to look for recipes to lint for you, but it appears we have a merge conflict.
Please try to merge or rebase with the base branch to resolve this conflict.
Please ping the 'conda-forge/core' team (using the @ notation in a comment) if you believe this is a bug.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Meson fixed the logic issue when building for PyPy, and that change made it into the latest meson feedstock (0.62). Could you release the pinning and try again?

Ahh, nvrmind. I think this PR can be closed in favor of #55, which is passing on PyPy + linux but failing on macOS and windows.


Add new version number in extenstions tab

add new version number in extensions tab

Some link to the github/project homepage would be awesome too.

@rozzzly +1

The additional feature request for repository and homepage has it's own issue #19718

This is fixed.

thank you


Request: Show weeknumbers in MonthGrid

The possibility to show weeknumbers in the MonthGrid.

Can you provide some mockup of what it should look like?

May I suggest this?

Or something like this..


inside md-dialog

Hi,
I have a lot of problems to call date picker from inside md-dialog.
Try by yourself, and you will see.
Thank you.

.sm-calender-pane {
z-index: 81;
}
Please override z index, and picker will show up. problems is its on back drop. of mdDialog
I will commit changes soon and that will fix it.


Dark theme

That's the only basic feature I find it's missing. Otherwise, wonderful app.

it's coming soon..

added

Hi @jecelyin, thank you for your work. I've installed the new version.  I'm failing to find the dark theme option. Under the Theme and Highlighting section I just see a couple of highlighting related options.

press tab menu, you can see a clothing icon


Appstudio update test-component-pac-evoy

Pipelines as Code configuration proposal
To start the PipelineRun, add a new comment with content /ok-to-test
For more detailed information about running a PipelineRun, please refer to Pipelines as Code documentation Running the PipelineRun
To customize the proposed PipelineRuns after merge, please refer to Build Pipeline customization

Pipelines as Code CI/test-component-pac-evoy-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
6 seconds
init

✅ Succeeded
23 seconds
clone-repository

✅ Succeeded
58 seconds
build-container

✅ Succeeded
30 seconds
inspect-image

✅ Succeeded
32 seconds
deprecated-base-image-check

✅ Succeeded
3 minutes
clair-scan

✅ Succeeded
50 seconds
clamav-scan

✅ Succeeded
17 seconds
sbom-json-check

✅ Succeeded
13 seconds
label-check

✅ Succeeded
8 seconds
show-summary

✅ Succeeded
5 seconds
show-sbom

Pipelines as Code CI/test-component-pac-evoy-on-pull-request has successfully validated your commit.

StatusDurationName

✅ Succeeded
6 seconds
init

✅ Succeeded
20 seconds
clone-repository

✅ Succeeded
30 seconds
build-container

✅ Succeeded
13 seconds
inspect-image

✅ Succeeded
11 seconds
deprecated-base-image-check

✅ Succeeded
8 seconds
clair-scan

✅ Succeeded
33 seconds
clamav-scan

✅ Succeeded
7 seconds
sbom-json-check

✅ Succeeded
16 seconds
label-check

✅ Succeeded
6 seconds
show-summary

✅ Succeeded
5 seconds
show-sbom


Feature request : 2FA support

Is your feature request related to a problem? Please describe.
I tried to setup this integration but it kept failing with the following error:
File "/config/custom_components/librelink/config_flow.py", line 39, in async_step_user
await self._test_credentials(
File "/config/custom_components/librelink/config_flow.py", line 101, in _test_credentials
await client.async_get_token()
File "/config/custom_components/librelink/api.py", line 168, in async_get_token
monToken = reponseLogin["data"]["authTicket"]["token"]
~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^
KeyError: 'authTicket'

I then tried to log onto the LibreView website to ensure my credentials were correct, and it made me set up two-factor authentication. Unfortunately it doesn't seem like I can remove 2FA via the website, and this integration doesn't support the 2FA flow.
Describe the solution you'd like
When setting up this integration, if 2FA is setup on the account, the wizard should prompt for the one-time code and set itself up as a trusted app.
Describe alternatives you've considered
Interestingly, I tried to follow the code and send a request manually via requests.post, but kept getting a notAuthenticated error:
>>> login_url = "https://api-eu.libreview.io/llu/auth/login"
>>> data = {"email": "xxx", "password": "xxx"}
>>> headers = {"product": "llu.android", "version": "4.7", "Application": "application/json"}
>>> requests.post(login_url, data=data, headers=headers).json()
{'status': 2, 'error': {'message': 'notAuthenticated'}}

The only way I was able to start the 2fa negotiation is by using https://api-eu.libreview.io/auth/login as the endpoint:
$ curl 'https://api-eu.libreview.io/auth/login' \
  -H 'content-type: application/json;charset=UTF-8' \
  -H 'newyu-lv-web-version: 3.18.15' \
  -H 'product: lv' \
  --data-raw '{"email": "xxx", "password": "xxx"}'
{"status":4,"data":{"step":{"type":"2faVerify","componentName":"TwoFactorVerify","props":{"accountType":"patient","primaryMethod":"phone","primaryValue":"+*** *********","secondaryMethod":"email","secondaryValue":"***********@gmail.com"},"title":"AccountSignUp.verifyYourIdentity"},"user":{"accountType":"pat","country":"IL","uiLanguage":"en-US"},"authTicket":{"token":"xxx","expires":1724977478,"duration":3600000}}}

My bad - I kept trying to log into my LibreLink account instead of LibreLinkUp 🤦♂
With LibreLinkUp there's no 2FA and everything works correctly.
Would you be willing to accept a PR that adds this distinction to the docs?

Hello
Sure I will
Cordialement,
Gilles van Schendel
Le ven. 30 août 2024 à 02:32, Moshi Binyamini @.***> a
écrit :

My bad - I kept trying to log into my LibreLink account instead of
LibreLinkUp 🤦♂
With LibreLinkUp there's no 2FA and everything works correctly.
Would you be willing to accept a PR that adds this distinction to the docs?
—
Reply to this email directly, view it on GitHub
https://github.com/gillesvs/librelink/issues/28#issuecomment-2319548336,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMG6JI3SGNJ3HRCZJL3DW4LZT64QDAVCNFSM6AAAAABNLN5Z4WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMJZGU2DQMZTGY
.
You are receiving this because you were assigned.Message ID:
@.***>


debugServer property should be under configurations

Currently the debugServer property in launch.json is at the same level of version - that is, it's global.
In my opinion it would make more sense for it to be under the specific configurations; the benefits would be:

the extensions can fill launch.json appropriately (as far as I can see extensions can easily provide configurations when they are first clicked in the debug gear dropdown, but not global properties to launch.json)
debug extensions using programs and ones using debugServer properties could be mixed-up in the same project

Of course there is a high change that I'm missing something big - documentation about debugServer is hard to find and sparse, that being the case, sorry in advance :)

+1 for this
The downside is that we would break existing launch.json that have debugServer on top. Though most of them just have it for development of debug adapters so IMHO this might be fine
@weinand opinion?

@isidorn agreed, having debugServer per launch configuration makes sense (and becomes even more important if we start to support multiple sessions).
I suggest that we start to support this and keep the global debugServer as well (but deprecate it).

@weinand the only way to depricate the debugServer is via documentation since it is currently hidden in the launch.json inteli-sense.
I also propose to support top level debug server for one sprint and then depricate it

We should document both debugServer attributes in intellisense.

But I top level I would document it with a deprecation message.
And it can get a proper message inside the configuration

I just started using the debugServer property in the PowerShell extension and I agree, it'd be great to have it on a per-configuration basis!


The link referencing the documentation to integrate Terrascan into CI/CD is broken

terrascan version: N/A
Operating System: N/A

Description
The link referencing the documentation to integrate Terrascan into CI/CD is broken
What I Did
N/A

Thanks for raising this!


Update Dockerfile

v8.1.12 is installed by default.
Most packages require php 8.1.17 and above.

8.1.24 stable php upgrade

Docker will install the newer version automatically if you rebuild the container.
I think you can do that with:
sail build --no-cache
sail up

You can also change the image name in your docker-compose.yml from sail-8.1/app to sail-8.1-app2 which forces sail to rebuild the docker container.
You can also log into the root shell and to an update with:
sail root-shell

and in there execute
apt update && apt upgrade

I tested a new application with a custom image name, to check if with the current settings the correct php version is installed:
git clone git@github.com:Jubeki/sail-pr-630.git
cd sail-pr-630
cp .env.example
sail up
sail artisan key:generate
sail php -v


Widows filter

Widows/Widonts
Replaces the space between the last two words in a string with  .
Describe the solution you would like
{{ content|widont }}
Documentation suggests Widows are supported but when trying to call said filter, Twig error is thrown.

The way to do this is:
{{ content |typogrify }}

Which will apply all of your settings (including widow protection):
https://nystudio107.com/docs/typogrify/#configuring-typogrify


Update linux.md

Debian respects privacy more than Ubuntu does. I would also like to point out that TAILS is a better solution for privacy.

Tails is at the TL;DR on top. (But the design could be better, that is true.)
About debian, I already answered here:
https://news.ycombinator.com/item?id=9510793
I know that ubuntu is not perfect, but I think that it is a great first step from people coming from windows.
We really try to target people that are new to this area. I don't think recommending debian will hep them.
Maybe I'm wrong, I let this issue open to see what other people are thinking.
But thanks for the PR :)

Here is the discussion: https://news.ycombinator.com/item?id=9511812

Ubuntu sends all queries typed in Unity to Amazon by default.

yes, I know, but it's easier to use :/

So sacrifice privacy for ease of use? Why not recommend Mac OSX then?
On Fri, May 8, 2015 at 10:48 AM, Pierre Ozoux<EMAIL_ADDRESS>wrote:

yes, I know, but it's easier to use :/
—
Reply to this email directly or view it on GitHub
https://github.com/LisbonInternetFreedom/ihavesomethingtohi.de/pull/31#issuecomment-100258861
.

Complicated and old discussion, but I tend to agree with  @igangsta. We can't tell ppl and improove Free Software and telling them to use Ubuntu. There is a need of making a choice between these. It's very complicated, but ubuntu had very much problem with the FSF about privacy, but GPL licensing too. Ubuntu today is not the best distro to move from windows. I'm tester from distro, and elementaryos is way more interesting than Ubuntu about privacy, and GPL compliance.
Debian is way more better, as it's known for its stability.
Debian/Ubuntu-derivated distro are way more interesting for ease of use. For example Linux Mint.
Anyway, I will let the users chose it between 5 distro we could change every year. It's better. :-)  I close this for the moment.


Going back from table's visualization in full screen mode stretches the first column

Discord username
No response
What type of issue is this?
Permanent – Ocurring repeatably
Is this issue blocking you from using Enso?

[ ] Yes, I can't use Enso because of this issue.

Is this a regression?

[ ] Yes, previous version of Enso did not have this issue.

What issue are you facing?
When visualizing a table to a full screen mode it will, correctly, span to the whole width of the window.
When going back to the project view with all the nodes and the preview of the visualization it keeps the really long width of the first column making it unusable (see screenshot). Closing/reopening the visualization fixes the problem.
Expected behaviour
Should consistently keep column widths, even when coming back from full screen mode.
How we can reproduce it?

Visualize data from one of the bookclubs
Double-space to enter full screen mode
Single space to go back to the project
Notice how the column has the wrong width

Screenshots or screencasts
Bug in three acts:

Enso Version
develop
Browser or standalone distribution
Chrome
Browser Version or standalone distribution
110.0.5481.100
Operating System
Linux
Operating System Version
No response
Hardware you are using
No response

Duplicate of https://github.com/enso-org/enso/issues/5966


Terraform lint inconsistencies

Currently the lint tool forces the role_assignment variable to include the condition and condition_version parameter, which is not supported by most services. As far as I know, only the storage account resource supports ABAC. This makes the modules fragile as if someone specifies something there the deployment will fail (We can always ignore whatever the user put there but it will be still confusing for the user to have a parameter that is always ignored). In my opinion, we should not force those two parameters as it is more common to have problems than actually use them to do something useful.
For Customer managed keys, the AVM web pages suggest a structure (see here) while the avm-template repository has another one (see here). In my opinion, the correct one should be the one that is in the avm-template repository since to enable a CMK it is mandatory to specify the user managed identity resource id (Even the storage account module is doing something that conflicts with the tflint see here). Should we create a user managed identity if one is not specified and comply with the tflint or should we do what the old modules do?
Off topic. Could we have the "concurrency" parameter in the e2e tests github workflow? It is not a blocker, but it helps when doing multiple commits and the tf e2e tests are running. So pending ones are cancelled and we dont have to do it manually or wait for all of them to run.

Hi!
Thanks for reporting this.
We will look into you point 1.
As for point 2, the AVM spec is correct as it provides security when a supplied resource id is not known u til after apply.
In the above case it's not possible to use this value in a count expression.
Wrapping it in an object means we can test for the object being null, or not without knowing the resource id.
See: https://azure.github.io/Azure-Verified-Modules/specs/terraform/#id-tfnfr11---category-code-style---null-comparison-toggle

On your last point, there should be environment approvals set up to control deployments for e2e. Is this not happening?

I'm sorry but I didn't quite pick up your explanation for the 2do point.
Just to make sure we are on the same page. I'm complaining about this specific null as it doesn't make sense in most cases (not just in my modules). That parameter in my opinion should be mandatory as for example the storage account is doing it.

If someone doesn't specify the parameter "user_assigned_identity" then its default value would be null as per the AVM specification. Then, if this is the case how am I going to configure a CMK without this id? In my case in the SB and CosmosDB this value is mandatory and cannot be null or be a system assigned MI. The user must provide it. I'm very sure this is the case for most resouces in Azure. I'm already toggling depending on the variable "customer_managed_key" but in my opinion it is also overkill to have to check for the "user_assigned_identity" parameter as it is supposed to be mandatory if "customer_managed_key" is not null.
For the 3 point. I do have the deployment approval. But, I am suggesting an improvement since having a concurrency in the workflow means that if for some reason I make multiple commits (lets say 5) while one workflow is running/pending all the intermediate runs 1,2,3,4 will be automatically canceled and only the 5th one will be waiting for the current run to finish. For example, I recently had to manually cancel like 40 runs because they were all pending to run (I had problems with the runners in my repo). If I had had this concurrency those 39 runs would have been cancelled automatically for me.

For customer managed key the optional makes sense for those services which allows system managed identity.
See: https://github.com/Azure/Azure-Verified-Modules/pull/72
The object wrapping is a fix to an edge case when using datas
See: https://github.com/Azure/Azure-Verified-Modules/pull/623/files

Thanks - we will close this now

There is still the suggestions regarding the "conditions" in "role assignments"

Sorry - role assignment conditions
We must have these fields in the interface - I don't see any other way, do you?

Well, taking into consideration the result of the conversation we just had in our internal team regarding the "infrastructure_encryption" parameter. This means that this "condition" parameters should be a separate variable as it is only used by the storage account. Even less than the infrastructure encryption which is supported by multiple services

Thinking about the map(object(...)) schema, it would appear clumsy to split this out. You would need another map of objects.
I do get your point about these attributes being unnecessary, but I have just implemented them as per the spec and nobody has complained

Also constrained delegation also uses these attributes:
https://learn.microsoft.com/en-us/azure/role-based-access-control/delegate-role-assignments-overview?tabs=azure-powershell#how-to-delegate-role-assignment-management-with-conditions
These can be universal


feature modbus-rtu is required to run this example

I'm running the example and .toml file and getting:
feature modbus-rtu is required to run this example
Am I missing something?

I should probably archive the repo since it has not been updated in 3 years. And I no longer have access to the hardware.
My recommendation is to start from scratch using the current tokio-modbus version.


LCOE breakdown method for annual workflows

The purpose of this pull request is to introduce a new method that generates a dataframe structured as follows:

Component
Category
Value ($/kW)
Fixed charge   rate (FCR) (real)
Value ($/kW-yr)
Net AEP   (MWh/kW/yr)
Value ($/MWh)

Turbine
Turbine
1700.0000
0.0648
110.16
3.34632
32.91974467

Array System
Balance of System CapEx
251.0947
0.0648
16.27093499
3.34632
4.862336831

Export System
Balance of System CapEx
142.8433
0.0648
9.25624597
3.34632
2.766097077

Offshore Substation
Balance of System CapEx
187.4795
0.0648
12.14867238
3.34632
3.630457453

Substructure
Balance of System CapEx
1188.6430
0.0648
77.02406582
3.34632
23.0175434

Mooring System
Balance of System CapEx
519.4231
0.0648
33.65861661
3.34632
10.05839747

Array System Installation
Balance of System CapEx
284.9460
0.0648
18.46449855
3.34632
5.517852015

Export System Installation
Balance of System CapEx
265.5347
0.0648
17.2066501
3.34632
5.141961946

Offshore Substation   Installation
Balance of System CapEx
25.0795
0.0648
1.625152779
3.34632
0.485653727

Substructure Installation
Balance of System CapEx
157.7475
0.0648
10.22203655
3.34632
3.054709815

Mooring System Installation
Balance of System CapEx
120.8337
0.0648
7.830026741
3.34632
2.339891804

Project
Balance of System CapEx
98.2825
0.0648
6.368705038
3.34632
1.903196657

Lease Price
Balance of System CapEx
166.6667
0.0648
10.8
3.34632
3.227425949

Construction Insurance
Financial CapEx
58.9020
0.0648
3.816848855
3.34632
1.140610837

Decomissioning
Financial CapEx
147.3394
0.0648
9.547592913
3.34632
2.853161955

Construction Financing
Financial CapEx
254.9402
0.0648
16.52012267
3.34632
4.936803015

Procurement Contingency
Financial CapEx
245.3968
0.0648
15.90171331
3.34632
4.752000199

Install. Contingency
Financial CapEx
294.6788
0.0648
19.09518583
3.34632
5.706323912

Project Completion
Financial CapEx
58.9020
0.0648
3.816848855
3.34632
1.140610837

Labor   (technicians)
OpEx

4
3.34632
1.195342944

Materials
OpEx

3
3.34632
0.896507208

Equipment (vessels)
OpEx

49
3.34632
14.64295106

Management administration
OpEx

2
3.34632
0.597671472

Port fees
OpEx

14
3.34632
4.183700304

Insurance
OpEx

15
3.34632
4.48253604

This dataframe will combine the CapEx and OpEx outputs from ORBIT and WOMBAT, respectively, and will also incorporate key parameters from the configuration file, such as the FCR, along with relevant outputs from WAVES, including the net AEP.

Right now, it spits what we were looking for. I need to check with Tyler. Does the order of the capex components matter?

Also, add a note that once WAVES pulls the data from the new version of ORBIT, instead of the usual capex breakdown, it may be better to use the new capex breakdown with a detailed soft capex breakdown. Check with Rob how to tackle that one.

Tyler has approved the current process.
I spoke with him about the possibility that some categories may have different names or be grouped differently than in ORBIT/WOMBAT. We agreed that the COWER analyst can make adjustments (such as regrouping categories or renaming them) to the .csv before integrating it into the annual reporting workflow. This approach will prevent the need to modify the cost breakdowns generated by ORBIT or WOMBAT, as the number of such changes could be unlimited. It wouldn't be practical to update WAVES, ORBIT, or WOMBAT every time a request like this arises.
Tyler also mentioned it would be helpful to have documentation that explains what each cost in the breakdown represents. While ORBIT might be in decent shape in this regard, it’s worth confirming with Nick, and it would be good to check with Rob about WOMBAT as well.

Thanks for your suggested changes, @RHammond2! I followed your recommendations on most of the comments.
Your changes did alter the column order slightly, but this doesn't affect the annual reporting workflow, as the code retrieves values based on column names. However, I’ve added a line of code to preserve the original column order, as I think it makes the structure a bit more intuitive for the analyst.
# Re-order the columns so that it is more intuitive for the analyst         df = df[             [                 "Component",                 "Category",                 "Value ($/kW)",                 "Fixed charge rate (FCR) (real)",                 "Value ($/kW-yr)",                 "Net AEP (MWh/kW/yr)",                 "Value ($/MWh)",             ]         ]
Other than that, I didn’t make any further changes on my end.
After a few iterations, all the pre-commit tests passed successfully.

Everything looks good from my side, but feel free to reach out if you have any questions or concerns!


[WIP] Switch to public api for retriving QSS querysets

Switches from using an unsupported private API (which changed and broke
from django-querysetseqence>0.7) to a newly added public api method
(get_querysets) which achieves the same thing.
Depends on https://github.com/percipient/django-querysetsequence/pull/53
Supersedes #1056
Fixes #1050

Excellent work, passes tests for me ! Also nice upstream contribution, great testing and documentation, thank you very much pray :pray:

Upstream change is accepted and merged. Just waiting on a release before the [WIP] tag can be removed. For later reference, should be available in next QSS version after 0.10.

Grats for your contribution @optiz0r :+1:
Keep up the good work and have a great day :tophat:

Thanks, although by merging this before QSS has published a new release, I think you have broken master branch?


fix for #39 implement Error and Display for InitError

I would like to fix #39, so I followed the example in TRPL chapter 5.7.

Great, thanks! Maybe add a test that just coerces to Box<Error>, to make sure everything is setup right? Something like:
#[test]
fn coerce_to_box_error() {
    let _: Box<Error> = From::from(InitError::NumberOfThreadsZero); // check that coercion succeeds
}

Nice, I'll remember that. The test case passes, hope everything else is OK.

Thanks!


Generate QR codes locally

As requested by #114, this PR uses the zxing library to generate QR codes.
Checklist:

[ ] Merge LielAmar/LielsUtils#15
[ ] Implement an alternative for the clickable message, as we no longer have a URL. (See AuthHandler.java#277)

In order to build, build my GersomR-afk/LielsUtils fork, and place the jar inside a new directory called libs.

@gersomonline, could you share the jar of your work? I'm struggling with building.

@gersomonline, could you share the jar of your work? I'm struggling with building.

I won't be able to build a jar for at least a couple of days. However, in a previous comment I mentioned how one can build my modified 2FA plugin. Please let me know what stops you from building the plugin, so I can better help you.

Closing this MR. We're currently working on a new version which should allow users to compile custom jars, as well as adding built-in support for local QR generation.


test_bitcoin-qt failure

1.10-dev HEAD:
=============================================
   Bitcoin Core 0.11.0: src/test-suite.log
=============================================

# TOTAL: 2
# PASS:  1
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

FAIL: qt/test/test_bitcoin-qt
=============================

********* Start testing of URITests *********
Config: Using QtTest library 5.2.1, Qt 5.2.1
PASS   : URITests::initTestCase()
PASS   : URITests::uriTests()
PASS   : URITests::cleanupTestCase()
Totals: 3 passed, 0 failed, 0 skipped
********* Finished testing of URITests *********
********* Start testing of PaymentServerTests *********
Config: Using QtTest library 5.2.1, Qt 5.2.1
PASS   : PaymentServerTests::initTestCase()
QDEBUG : PaymentServerTests::paymentServerTests() PaymentServer::initNetManager: No active proxy server found.
FAIL!  : PaymentServerTests::paymentServerTests() Compared values are not the same
   Actual   (merchant)                   :
   Expected (QString("testmerchant.org")): testmerchant.org
   Loc: [qt/test/paymentservertests.cpp(87)]
PASS   : PaymentServerTests::cleanupTestCase()
Totals: 2 passed, 1 failed, 0 skipped
********* Finished testing of PaymentServerTests *********

PASS: test/test_bitcoin
FAIL: qt/test/test_bitcoin-qt
make[6]: Entering directory /home/kengyu/git/dogecoin/src' make[7]: Entering directory /home/kengyu/git/dogecoin/src'
make[7]: Leaving directory /home/kengyu/git/dogecoin/src' make[6]: Leaving directory /home/kengyu/git/dogecoin/src'
Testsuite summary for Bitcoin Core 0.11.0
TOTAL: 2
PASS:  1
SKIP:  0
XFAIL: 0
FAIL:  1
XPASS: 0
ERROR: 0
============================================================================
See src/test-suite.log
Please report to https://github.com/bitcoin/bitcoin/issues

We're aware of this issue, it is caused by payment protocol fixtures that need to be regenerated. Thank you for reporting it.

Assigning to myself as I probably should look at this. Likely to be Mon/Tues though, sorry.

@rnicoll the fixtures in question are these: https://github.com/dogecoin/dogecoin/blob/1.10-dev/src/qt/test/paymentrequestdata.h#L57-L460

Put the logs into ``` blocks to fix formatting. Not actually sure why those tests would break, even before we changed the payment request handling.
Not sure if this is still current, but it might come in handy: https://github.com/gavinandresen/paymentrequest

I'll look into this and try to have this patched for 1.10.1

fixed with #1341


Fix compile issue for missing ceil function

Missing 'ceil' function on OSX

oh wow thanks :)
you may also want to correct (remove) the include of cmath in
libsrc/hyperion/ImageProcessorFactory.cpp
... and i still wonder why its working for me without that include ...


REVIEWED: EXAMPLE: textures_bunnymark

This example wasn't added until 2.5, but the description said 1.6.

I was also wondering if the wabbit_alpha asset was made by someone working on raylib, since, on further investigation of this asset it was initially made in 2012/2013 (found here; original image found at) so we could add credits as in most examples.

Question: why did you review to raylib 2.5? And not something like 3.7

@catmanl Actually, this should probably reviewed in all examples, it's not clear the raylib version every example was created with, the minimal raylib version required and the last version the example was updated to. It should probably listed for every example:

This example was created with raylib x.x (minimal version required)
This example was reviewed with raylib x.x


make source code error

In file included from /home/work/xiaoxian/ClickHouse/ClickHouse-master/contrib/libtcmalloc/src/libc_override.h:79:0,
from /home/work/xiaoxian/ClickHouse/ClickHouse-master/contrib/libtcmalloc/src/tcmalloc.cc:156:
/home/work/xiaoxian/ClickHouse/ClickHouse-master/contrib/libtcmalloc/src/libc_override_glibc.h:132:71: error: conflicting declaration ‘void* (* volatile __malloc_hook)(size_t, const void*)’
void* (* MALLOC_HOOK_MAYBE_VOLATILE __malloc_hook)(size_t, const void*)
^
In file included from /home/work/xiaoxian/ClickHouse/ClickHouse-master/contrib/libtcmalloc/include/gperftools/tcmalloc.h:49:0,
from /home/work/xiaoxian/ClickHouse/ClickHouse-master/contrib/libtcmalloc/src/tcmalloc.cc:91:
/usr/include/malloc.h:165:16: note: previous declaration as ‘void* (* __malloc_hook)(size_t, const void*)’
extern void (__malloc_hook) __MALLOC_PMT ((size_t __size,
^
In file included from /home/work/xiaoxian/ClickHouse/ClickHouse-master/contrib/libtcmalloc/src/libc_override.h:79:0,
from /home/work/xiaoxian/ClickHouse/ClickHouse-master/contrib/libtcmalloc/src/tcmalloc.cc:156:
/home/work/xiaoxian/ClickHouse/ClickHouse-master/contrib/libtcmalloc/src/libc_override_glibc.h:134:79: error: conflicting declaration ‘void* (* volatile __realloc_hook)(void*, size_t, const void*)’
void* (* MALLOC_HOOK_MAYBE_VOLATILE __realloc_hook)(void*, size_t, const void*)
^
In file included from /home/work/xiaoxian/ClickHouse/ClickHouse-master/contrib/libtcmalloc/include/gperftools/tcmalloc.h:49:0,
from /home/work/xiaoxian/ClickHouse/ClickHouse-master/contrib/libtcmalloc/src/tcmalloc.cc:91:
sr/include/malloc.h:167:16: note: previous declaration as ‘void* (* __realloc_hook)(void*, size_t, const void*)’
extern void (__realloc_hook) __MALLOC_PMT ((void __ptr, size_t __size,
^
In file included from /home/work/xiaoxian/ClickHouse/ClickHouse-master/contrib/libtcmalloc/src/libc_override.h:79:0,
from /home/work/xiaoxian/ClickHouse/ClickHouse-master/contrib/libtcmalloc/src/tcmalloc.cc:156:
/home/work/xiaoxian/ClickHouse/ClickHouse-master/contrib/libtcmalloc/src/libc_override_glibc.h:136:67: error: conflicting declaration ‘void ( volatile __free_hook)(void*, const void*)’
void (* MALLOC_HOOK_MAYBE_VOLATILE __free_hook)(void*, const void*)
^
In file included from /home/work/xiaoxian/ClickHouse/ClickHouse-master/contrib/libtcmalloc/include/gperftools/tcmalloc.h:49:0,
from /home/work/xiaoxian/ClickHouse/ClickHouse-master/contrib/libtcmalloc/src/tcmalloc.cc:91:
/usr/include/malloc.h:163:15: note: previous declaration as ‘void (* __free_hook)(void*, const void*)’
extern void (__free_hook) __MALLOC_PMT ((void __ptr,
^
In file included from /home/work/xiaoxian/ClickHouse/ClickHouse-master/contrib/libtcmalloc/src/libc_override.h:79:0,
from /home/work/xiaoxian/ClickHouse/ClickHouse-master/contrib/libtcmalloc/src/tcmalloc.cc:156:
/home/work/xiaoxian/ClickHouse/ClickHouse-master/contrib/libtcmalloc/src/libc_override_glibc.h:138:80: error: conflicting declaration ‘void ( volatile __memalign_hook)(size_t, size_t, const void*)’
void* (* MALLOC_HOOK_MAYBE_VOLATILE __memalign_hook)(size_t,size_t, const void*)
^
In file included from /home/work/xiaoxian/ClickHouse/ClickHouse-master/contrib/libtcmalloc/include/gperftools/tcmalloc.h:49:0,
from /home/work/xiaoxian/ClickHouse/ClickHouse-master/contrib/libtcmalloc/src/tcmalloc.cc:91:
/usr/include/malloc.h:169:16: note: previous declaration as ‘void* (* __memalign_hook)(size_t, size_t, const void*)’
extern void (__memalign_hook) __MALLOC_PMT ((size_t __alignment,

It because source code contains tcmalloc library, that was pre-configured (by running configure script) for specific system, where signatures of malloc hooks may differ than corresponding signatures on your system.
There is few different ways to avoid this problem:

Edit contrib/libtcmalloc/src/config.h file, line 222, #define MALLOC_HOOK_MAYBE_VOLATILE according to your system.

Download libtcmalloc, run configure script, and copy resulting config.h file in place of contrib/libtcmalloc/src/config.h.

(More complicated) Edit CMakeLists.txt to correctly define MALLOC_HOOK_MAYBE_VOLATILE macro instead of config.h file.

Build on VM with Ubuntu and install on target system as described here:
https://github.com/yandex/ClickHouse/issues/61#issuecomment-236002259

Updated tcmalloc library to latest version, which was removed usage of obsolete malloc hooks.


Add kmeans algorithm

Title : Add Kmeans algorithm used for clustering
Issue no : #76
Description
A folder has been created by the name of Clustering Techniques. The folder should be designated for maintaining algorithms commonly used for clustering data. The kmeans algorithm has been added in this folder.
Checklist

[x] I have read and agree to abide by the Code of Conduct
[x] I have read and followed the Contributing Guidelines

Great job!
Thank you for contributing. Do give this repository a star if you feel like ✨


[OCSI: Adds new author AyaSadyk

Description
Adds new author AyaSadyk
Issues Resolved
[List any issues this PR will resolve]
Check List

[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 BSD-3-Clause License.

Nice PR!


[ISSUE] Incorrect function is used in the example for SQL statement execution

in example instead of .execute it should be the .execute_statement.

There are other places where the same issue is present. I can create the fix for it. Can this issue be assigned to me please? @tanmay-db

@mgyucht I have the fix ready, the changes are in:

grants/get_effective_tables.py
shares/update_shares.py
statement_execution/execute_shares.py
statement_execution/execute_tables.py
tables/get_tables.py

Can you please assign the issue to me? Thank you.


License for system.lsp

It says it is "distributed under the BSD License" but which BSD license? There is more than one.
https://en.wikipedia.org/wiki/BSD_licenses
My hope is for two-clause but any resolution to the ambiguity of exactly which one would be appreciated.

Ah, well there's a 3-clause in the project root. I'll go with that. If this is incorrect (like system.lsp is different from everything else) hopefully you'll clarify.


[Autocomplete] Add a way to translate "Loading more results"

Hello, as per title it could be useful to customize the "Loading more results" message that appears when scrolling down the select.
Thanks.

Yea, it looks like under render - https://github.com/symfony/ux/blob/2.x/src/Autocomplete/assets/src/controller.ts#L220 - we need to specify the loading_more from https://tom-select.js.org/plugins/virtual_scroll/ - set it to a value that can be passed in. PR welcome :)


get_meme_count looks like getmemecount in the ui

Describe the bug
In lesson 4 near view museum.testnet getmemecount should be near view museum.testnet get_meme_count. It looks like the _ are being read as "make italics"

To Reproduce
Steps to reproduce the behavior:

https://near.academy/near101/chapter-4
attempt to run near view museum.testnet getmemecount which will give an error
try near view museum.testnet get_meme_count which works

sorry, duplicate


Book Store: Redux in react components

Book Store 🚀
Hi there, 👋 In this PR:

[ ] At first, I created a new Branch then I use the redux state to display my book list. ✅
[ ] Then I dispatched a couple of actions to remove  add a book ✅
[ ] Then dispatched an action to check the categories page status and displayed the status on it conditionally. ✅

Thanks for visiting this PR 👍

@TedLivist Thank you so much for reviewing my project 👍


Compile errors building Sc2LadderServer on OSX

I am using OSX (MacOS, High Sierra, 10.13.6) and am getting the following error when building Sc2LadderServer.  Any help is appreciated.
Followed instructions and tried command:  make Sc2LadderServer.
Much of the code built (with lots of warnings) but the following error stopped the build:
Building C object s2client-api/contrib/civetweb/src/CMakeFiles/civetweb-c-library.dir/civetweb.c.o
[working-dir]/Sc2LadderServer/s2client-api/contrib/civetweb/src/civetweb.c:32:9: warning: macro name is a reserved identifier
[-Wreserved-id-macro]
#define _GNU_SOURCE /* for setgroups() /
^
[working-dir]/Sc2LadderServer/s2client-api/contrib/civetweb/src/civetweb.c:38:9: warning: macro name is a reserved identifier
[-Wreserved-id-macro]
#define _LARGEFILE_SOURCE / For fseeko(), ftello() /
^
[working-dir]/Sc2LadderServer/s2client-api/contrib/civetweb/src/civetweb.c:41:9: warning: macro name is a reserved identifier
[-Wreserved-id-macro]
#define _FILE_OFFSET_BITS 64 / Use 64-bit file offsets by default /
^
[working-dir]/Sc2LadderServer/s2client-api/contrib/civetweb/src/civetweb.c:44:9: warning: macro name is a reserved identifier
[-Wreserved-id-macro]
#define __STDC_FORMAT_MACROS / <inttypes.h> wants this for C++ /
^
[working-dir]/Sc2LadderServer/s2client-api/contrib/civetweb/src/civetweb.c:47:9: warning: macro name is a reserved identifier
[-Wreserved-id-macro]
#define __STDC_LIMIT_MACROS / C++ wants that for INT64_MAX */
^
[working-dir]/python/Sc2LadderServer/s2client-api/contrib/civetweb/src/civetweb.c:1556:9: warning: macro name is a reserved identifier
[-Wreserved-id-macro]
#define _DARWIN_UNLIMITED_SELECT
^
[working-dir]/Sc2LadderServer/s2client-api/contrib/civetweb/src/civetweb.c:5725:17: warning: implicit conversion loses integer precision:
'long' to '__darwin_suseconds_t' (aka 'int') [-Wshorten-64-to-32]
tv.tv_usec = (long)((ms_wait % 1000) * 1000);
~ ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[working-dir]/Sc2LadderServer/s2client-api/contrib/civetweb/src/civetweb.c:17867:32: error: unknown warning group '-Werror', ignored
[-Werror,-Wunknown-warning-option]
#pragma GCC diagnostic ignored "-Werror"
^
7 warnings and 1 error generated.
make[3]: *** [s2client-api/contrib/civetweb/src/CMakeFiles/civetweb-c-library.dir/civetweb.c.o] Error 1
make[2]: *** [s2client-api/contrib/civetweb/src/CMakeFiles/civetweb-c-library.dir/all] Error 2
make[1]: *** [src/CMakeFiles/Sc2LadderServer.dir/rule] Error 2
make: *** [Sc2LadderServer] Error 2

Hi @ericbroda
This is the sc2API issue, see https://github.com/Blizzard/s2client-api/issues/239

I fixed the civetweb issue (as per #239 referenced above) and now received the following error:
[ 96%] Building CXX object src/CMakeFiles/Sc2LadderCore.dir/sc2laddercore/AgentsConfig.cpp.o
[working-dir]/Sc2LadderServer/src/sc2laddercore/AgentsConfig.cpp:8:10: fatal error: 'filesystem' file not found
#include
^~~~~~~~~~~~
1 error generated.
make[2]: *** [src/CMakeFiles/Sc2LadderCore.dir/sc2laddercore/AgentsConfig.cpp.o] Error 1
make[1]: *** [src/CMakeFiles/Sc2LadderCore.dir/all] Error 2
make: *** [all] Error 2
It appears that XCode does not have  ... continuing to investigate...

This is broken by @Cryptyc
You should either comment this functionality, or install gcc6 e.g. using homebrew.

I installed gcc6 (using homebrew) as well as other gcc/g++ versions and the builds (each version) broke at the same point.  OSX support for "filesystem" is not very complete, it appears.
Any other ideas?

Here is the latest set of compile errors:
Building CXX object s2client-api/src/CMakeFiles/sc2utils.dir/sc2utils/sc2_manage_process.cc.o
In file included from /System/Library/Frameworks/CoreGraphics.framework/Headers/CGContext.h:21:0,
                 from /System/Library/Frameworks/CoreGraphics.framework/Headers/CGBitmapContext.h:9,
                 from /System/Library/Frameworks/CoreGraphics.framework/Headers/CoreGraphics.h:11,
                 from /System/Library/Frameworks/ApplicationServices.framework/Headers/ApplicationServices.h:35,
                 from /System/Library/Frameworks/Carbon.framework/Headers/Carbon.h:24,
                 from /Users/ericbroda/Development/python/Sc2LadderServer/s2client-api/src/sc2utils/sc2_manage_process.cc:41:
/System/Library/Frameworks/CoreGraphics.framework/Headers/CGPath.h:391:15: error: expected unqualified-id before '^' token
 typedef void (^CGPathApplyBlock)(const CGPathElement * element);
               ^
/System/Library/Frameworks/CoreGraphics.framework/Headers/CGPath.h:391:15: error: expected ')' before '^' token
/System/Library/Frameworks/CoreGraphics.framework/Headers/CGPath.h:393:53: error: 'CGPathApplyBlock' has not been declared
 CG_EXTERN void CGPathApplyWithBlock(CGPathRef path, CGPathApplyBlock CF_NOESCAPE block)
                                                     ^~~~~~~~~~~~~~~~
/Users/ericbroda/Development/python/Sc2LadderServer/s2client-api/src/sc2utils/sc2_manage_process.cc: In function 'void sc2::GetDirectory(std::__cxx11::string&, uint32_t, short int)':
/Users/ericbroda/Development/python/Sc2LadderServer/s2client-api/src/sc2utils/sc2_manage_process.cc:304:17: warning: 'OSErr FSFindFolder(FSVolumeRefNum, OSType, Boolean, FSRef*)' is deprecated [-Wdeprecated-declarations]
     OSErr err = FSFindFolder(domain, folderType, false, &fsref);
                 ^~~~~~~~~~~~
In file included from /System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/CarbonCore.h:176:0,
                 from /System/Library/Frameworks/CoreServices.framework/Frameworks/AE.framework/Headers/AE.h:20,
                 from /System/Library/Frameworks/CoreServices.framework/Headers/CoreServices.h:23,
                 from /System/Library/Frameworks/Carbon.framework/Headers/Carbon.h:20,
                 from /Users/ericbroda/Development/python/Sc2LadderServer/s2client-api/src/sc2utils/sc2_manage_process.cc:41:
/System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/Folders.h:286:1: note: declared here
 FSFindFolder(
 ^~~~~~~~~~~~
/Users/ericbroda/Development/python/Sc2LadderServer/s2client-api/src/sc2utils/sc2_manage_process.cc:304:63: warning: 'OSErr FSFindFolder(FSVolumeRefNum, OSType, Boolean, FSRef*)' is deprecated [-Wdeprecated-declarations]
     OSErr err = FSFindFolder(domain, folderType, false, &fsref);
                                                               ^
In file included from /System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/CarbonCore.h:176:0,
                 from /System/Library/Frameworks/CoreServices.framework/Frameworks/AE.framework/Headers/AE.h:20,
                 from /System/Library/Frameworks/CoreServices.framework/Headers/CoreServices.h:23,
                 from /System/Library/Frameworks/Carbon.framework/Headers/Carbon.h:20,
                 from /Users/ericbroda/Development/python/Sc2LadderServer/s2client-api/src/sc2utils/sc2_manage_process.cc:41:
/System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/Folders.h:286:1: note: declared here
 FSFindFolder(
 ^~~~~~~~~~~~
/Users/ericbroda/Development/python/Sc2LadderServer/s2client-api/src/sc2utils/sc2_manage_process.cc:308:9: warning: 'OSStatus FSRefMakePath(const FSRef*, UInt8*, UInt32)' is deprecated [-Wdeprecated-declarations]
         FSRefMakePath(&fsref, reinterpret_cast<unsigned char*>(pathBuffer), PATH_MAX);
         ^~~~~~~~~~~~~
In file included from /System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/Components.h:26:0,
                 from /System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/CarbonCore.h:87,
                 from /System/Library/Frameworks/CoreServices.framework/Frameworks/AE.framework/Headers/AE.h:20,
                 from /System/Library/Frameworks/CoreServices.framework/Headers/CoreServices.h:23,
                 from /System/Library/Frameworks/Carbon.framework/Headers/Carbon.h:20,
                 from /Users/ericbroda/Development/python/Sc2LadderServer/s2client-api/src/sc2utils/sc2_manage_process.cc:41:
/System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/Files.h:4086:18: note: declared here
 extern OSStatus  FSRefMakePath(const FSRef *ref, UInt8 *path, UInt32 pathBufferSize)     __OSX_AVAILABLE_BUT_DEPRECATED(__MAC_10_0, __MAC_10_8, __IPHONE_NA, __IPHONE_NA);
                  ^~~~~~~~~~~~~
/Users/ericbroda/Development/python/Sc2LadderServer/s2client-api/src/sc2utils/sc2_manage_process.cc:308:85: warning: 'OSStatus FSRefMakePath(const FSRef*, UInt8*, UInt32)' is deprecated [-Wdeprecated-declarations]
         FSRefMakePath(&fsref, reinterpret_cast<unsigned char*>(pathBuffer), PATH_MAX);
                                                                                ^
In file included from /System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/Components.h:26:0,
                 from /System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/CarbonCore.h:87,
                 from /System/Library/Frameworks/CoreServices.framework/Frameworks/AE.framework/Headers/AE.h:20,
                 from /System/Library/Frameworks/CoreServices.framework/Headers/CoreServices.h:23,
                 from /System/Library/Frameworks/Carbon.framework/Headers/Carbon.h:20,
                 from /Users/ericbroda/Development/python/Sc2LadderServer/s2client-api/src/sc2utils/sc2_manage_process.cc:41:
/System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/Files.h:4086:18: note: declared here
 extern OSStatus  FSRefMakePath(const FSRef *ref, UInt8 *path, UInt32 pathBufferSize)     __OSX_AVAILABLE_BUT_DEPRECATED(__MAC_10_0, __MAC_10_8, __IPHONE_NA, __IPHONE_NA);
                  ^~~~~~~~~~~~~
make[3]: *** [s2client-api/src/CMakeFiles/sc2utils.dir/sc2utils/sc2_manage_process.cc.o] Error 1
make[2]: *** [s2client-api/src/CMakeFiles/sc2utils.dir/all] Error 2
make[1]: *** [src/CMakeFiles/Sc2LadderServer.dir/rule] Error 2
make: *** [Sc2LadderServer] Error 2

I probably need to put something in the tools to replace this, I'll do that after I got the new season running, should be this week, sorry about this.

@ericbroda but as you can see here we have a different set of errors (again in the c++ API) which means that you should add some flags or do some fixes to make it work.
Perhaps lower version of gcc (e.g. 5th) would work, not sure. As far as I've head filesystem was added to gcc6, not sure about gcc5.

@ericbroda Now compilation is fixed. Feel free to try :)


Trigger on edits

Sooo... as my first test I of course mistyped the command and edited afterwards to fix it. The bot didn't care :-(.

The bot indeed currently ignores all edits, but it's certainly possible for it not to. Thanks for the issue!

I thought a little bit about this an envision edits working like this:

If a user creates a reminder, note down the event ID.
Watch for edits. If one comes in with a command, delete any reminder that was created by the previous edit.

That way in your situation a reminder would end up being created, and in other situations if someone edited a reminder's text, it would update the created reminder.
I guess the only edge case here is if someone created a relative reminder (ex. in 5 minutes). The new reminder would fire 5 minutes from the edit, instead of the original reminder. We could be clever and compare the text for the time in each reminder. If the text for timing was changed in the edit, only then should we update the time in the new reminder.


[BUG?] Error when set multiple: true in pages field type

route:
      type: pages
      size: medium
      classes: fancy
      label: PLUGIN_ADMIN.HOME_PAGE
      show_all: true
      show_modular: false
      show_root: false
      multiple: true  // false is ok
      help: PLUGIN_ADMIN.HOME_PAGE_HELP

// then in PHP

$route = $this->config->get('plugins.MYPLUGIN.route');

will throw an error like this

I would like to help tackle this bug. I'm new to this community and would love it if you guys could guide me.

It's not so much a bug, as it is a incompatibility.  Basically, it is that pages type is traditionally stored with a text field when it's singular. If you add multiple: true it stores it as an array, so the text field throws an error unless you have validate: commalist: true to handle the array.
It's a replica of this: https://github.com/getgrav/grav-plugin-admin/issues/1024
which is where it should be, so closing here.


Better configuration

In general, it is the configuration of DustDDS does not scale and is hard to work with. I'm opening this issue to discuss possible alternatives.
Inconsistent documentation on interfaces:
The docs mention that you can pass an array of interface names as configuration option: [string, null].
However, the implementation only accepts one String value xor null.
Env variables does not scale well
Environment variables are only ok for small number of config options and get cumbersome to use with great number of values.
Possible solutions:

RTI Connext uses XML
Eclipse CycloneDDS also uses XML

I think a TOML based configuration file would fit well into the rustacean philosophy. Then the configuration file path could be provided like DUST_DDS_CONFIGURATION=/etc/dds/config.toml.
I'd be glad to hear the opinion of the maintainers! 🙂

Thank you for opening this issue. It is a very interesting question and something we have indeed been recently considering how to handle.
Originally we picked for a JSON format because it is something we are personally used to and it was easy to integrate with our code given the dependencies we already had. It was also possible to generate a schema for it and use that schema for easy creation of configurations in the IDE and also the documentation. But as you mention in your issue description, the way JSON schemas are described are not so "compatible" with Rust (e.g. [String, null] meaning an option between a string or nothing and not an array of those things).
After giving some consideration to this we came to the view that it should not be the task of the DustDDS library to "impose" on our users a specific format for this configuration. Our preferred solution is to make the configuration available programmatically on the DomainParticipantFactory interface and then each application will have the freedom to import the configuration as they best see fit and use it.
We are still working on the technical solution but I will soon link the PR on this issue. It would be nice to get also your feedback on it.

The merged PR looks really promising, thank you.


Fix merging stores

We use single-user Nix installation provided by the nix-quick-install-action.
Scenario:

There's a store with /nix/var/nix/db.
Assume restore-prefixes-all-matches restores a store A, then store B.

These stores also have /nix/var/nix/db.

Assume B is the last store to be restored.
Then, the final store will have /nix/var/nix/db from B.

However, ideally, restore-prefixes-all-matches should really merge stores and databases, not just overwrite databases.
It's currently unclear how to merge stores.
Some links that may be helpful

https://github.com/NixOS/nix/issues/3091
https://discourse.nixos.org/t/super-colliding-nix-stores/28462
https://discourse.nixos.org/t/help-nix-store-sqlite-db-documentation/37729

Reproduce a similar scenario
To get two stores, run
nix build --no-link nixpkgs#hello --store store1
nix build --no-link nixpkgs#gawk --store store2

Then, the databases are in
store1/nix/var/nix/db/db.sqlite
store2/nix/var/nix/db/db.sqlite

I can copy paths from one store to another via cp.
Questions

How to merge the databases?
Where to merge?

In the main near restoreCache
Determine whether a cache contains a /nix/var/nix/db/db.sqlite

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/merge-two-nix-stores/41256/1

Should be resolved now. Here's the sql script.


 Also more magboots and hardsuits.
Why / Balance
HYPERWAR IS NOW
nukies are slowly becoming more powerful and also the station usually crumbles from shit like a single dragon and loneop spawning at same time
Technical details
i change numbers
Media

Requirements

[X] I have read and am following the Pull Request and Changelog Guidelines.
[X] I have added media to this PR or it does not require an ingame showcase.

Breaking changes

Changelog
:cl:

tweak: sec armory lockers now contain 2x ot more the amount of guns and ammo. also more hardsuits and you get magboots now. HYPERWAR IS NOW

Summary by CodeRabbit

New Features

Increased item quantities for various weapons and magazines in the GunSafe entities, enhancing resource availability for players.
Added new entity tables and updated existing locker-related entities, expanding the variety of items available.

Gameplay Impact

Adjustments may affect gameplay dynamics by providing players with more options and resources during their experience.

I personally don't like this.

It forces nukies/lone ops to only strike armory to win (lame)
If they do end up attacking armory giving sec extra guns in the armory won't help the problem of them dying because lack of weapons
Sec doesn't need extra guns to handle a space dragon, they got enough for it already.
me when fun isn't allowed (mald reason)

I personally don't like this.

It forces nukies/lone ops to only strike armory to win (lame)
If they do end up attacking armory giving sec extra guns in the armory won't help the problem of them dying because lack of weapons
Sec doesn't need extra guns to handle a space dragon, they got enough for it already.
me when fun isn't allowed (mald reason)

ok so how would u buff sec to match nukies nerd #owned #liberal
dont say nerf nukies btw thats boring asf and wizbrained

ok so how would u buff sec to match nukies nerd #owned #liberal dont say nerf nukies btw thats boring asf and wizbrained

It's all mapping problem. Armory shouldn't be close to space.

ok so how would u buff sec to match nukies nerd #owned #liberal dont say nerf nukies btw thats boring asf and wizbrained

In my opinion sec doesn't need a buff, they are fine as it is. The only problem I see sec having is lack of sec itself. What could be half fixed by rolling antag before sec rather than giving cadets 2 quazillion guns.  The only problem I see sec having is lack of sec itself. What could be half fixed by rolling antag before sec rather than giving cadets 2 quazillion guns.  Sec getting grav boots or nerfing lube is one thing I think about.

nvm i changed my mind i dont like secmains i close pr get more robust


This is a CI test!

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: JiaXiao243:x: Paddle CIPaddle CI seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Better output of default value for service option types

Also adds some unit tests for all the option types used the docker service

14:07:35 These files are not properly gofmt'd:
14:07:35  - api/client/service/opts_test.go

oops, my pre-commit hooks didn't use -s on gofmt. Fixed it.

LGTM

LGTM

it's green!

LGTM


Making --gcp-project optional by extracting project from gcloud

Fixes https://github.com/GoogleCloudPlatform/k8s-multicluster-ingress/issues/80
cc @csbell @madhusudancs @G-Harmon

Fixed the test and verified that the e2e test still passes!

Thanks for the review @madhusudancs
Updated code as per comments.
PTAL

/lgtm


feature wishlist & prioritize issues by donation

Over at RoboMongo they have a cool backlog, where each issue has a donation-button.
The number of donations decides about, which feature will be integrated next.
http://robomongo.org/backlog
Feature-based donations

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/5077564-feature-wishlist-prioritize-issues-by-donation?utm_campaign=plugin&utm_content=tracker%2F164029&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F164029&utm_medium=issues&utm_source=github).

The example site over at Robomongo is gone.
The donation panel is now available to paying customers only (paying for advanced user support).
I really wonder, if the Robomongo guys can make some money with this new strategy.
Anyway...for this project:
i've enabled Bountysource long time ago,
but the project hasn't received any donation via Bountysource, yet.
Original issue: will not implement. Closing.


add demo of rgb-node:0.1

Here is my proposal for a written guide that aims at reproducing the video demo on youtube. The structure is similar to the one I did for lnp-node.

@UkolovaOlga can you also pls review?

And does anybody has the idea why the CI fails?

And does anybody has the idea why the CI fails?

it's missing apt-get update, #105 fixes that


fpgad-vc: adjust sensor trip points

Pull the high/low temperature trip points down/up by 5 degrees.
Pull the high/low power trip points down/up by 5%.
This is done to enable catching overages before the BMC takes action.

@r-rojo I thought about the separate function approach, but it seemed like overkill to abstract two lines of code.


Update to Leaflet 1.0.3

Hello,
The example doesn't work if changes Leaflet version to 1.0.3.
Any idea?
Thanks in advance.

Did you take a look at these issues? Maybe they can help.
https://github.com/bmcbride/bootleaf/issues/27
https://github.com/bmcbride/bootleaf/issues/46


Crashing containers calling libpthread

I just pulled a fresh round of images from DockerHub today and they all crash out immediately with the following error:

/logstash_exporter: relocation error: /lib/libpthread.so.0: symbol h_errno, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference

Hi @pceric! Sorry about the inconvenience! The reason behind this is that we used prometheus glibc-image as a base, which includes libpthread because busybox didn't ship with it in the past. Now they have added it, and this results in two versions of libpthread in the resulting image. Fix is coming up in a few minutes. Thanks for reporting!

Thanks for the quick fix and for the docker tag. Great project!


Fails to compile: AluVM on Rust >1.74

Hi guys, I'm currently stuck trying to add rgb-lib as a dependency to a new project as I'm absolutely incapable of making it work... Not sure why this wasn't caught before but here is the error I get (see below). Everything was working fine for me and I've been working with rgb-lib for a while now but I decided to update my dependencies and all hell broke loose.
Version
I tried many versions:
rgb-lib = { version = "0.2.2" }
rgb-lib = { git = "https://github.com/RGB-Tools/rgb-lib", tag = "0.2.2" }
rgb-lib = { git = "https://github.com/RGB-Tools/rgb-lib", branch = "master" }
rgb-lib = { git = "https://github.com/RGB-Tools/rgb-lib", rev = "52571ebe81babd953cc75fe18fa6c0a8567a1856" } // I remember being able to run this commit successfully

No matter what I try, it will always fail for some reason.
Error
I checked and AluVM version 0.10.6 has been released 4 months ago so no clue why this is failing now. I updated my Rust version to 1.74 from 1.73 so that may be the issue but I'm incapable to revert to 1.73 because of clap that now needs Rust >= 1.74
error[E0308]: mismatched types
   --> /Users/darioanongbavarela/.cargo/registry/src/index.crates.io-6f17d22bba15001f/aluvm-0.10.6/src/reg/indexes.rs:425:9
    |
424 |     fn try_from(value: Reg32) -> Result<Self, Self::Error> {
    |                                  ------------------------- expected `Result<Reg16, OverflowError>` because of return type
425 |         u4::try_from(value as u8).map(Reg16::from)
    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected `Result<Reg16, OverflowError>`, found `Result<Reg16, OverflowError<u8>>`
    |
    = note: expected enum `Result<_, OverflowError<usize>>`
               found enum `Result<_, OverflowError<u8>>`

error[E0308]: mismatched types
   --> /Users/darioanongbavarela/.cargo/registry/src/index.crates.io-6f17d22bba15001f/aluvm-0.10.6/src/reg/indexes.rs:528:9
    |
527 |     fn try_from(value: Reg32) -> Result<Self, Self::Error> {
    |                                  ------------------------- expected `Result<Reg8, OverflowError>` because of return type
528 |         u3::try_from(value as u8).map(Reg8::from)
    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected `Result<Reg8, OverflowError>`, found `Result<Reg8, OverflowError<u8>>`
    |
    = note: expected enum `Result<_, OverflowError<usize>>`
               found enum `Result<_, OverflowError<u8>>`

error[E0308]: mismatched types
   --> /Users/darioanongbavarela/.cargo/registry/src/index.crates.io-6f17d22bba15001f/aluvm-0.10.6/src/reg/indexes.rs:620:9
    |
619 |     fn try_from(value: Reg32) -> Result<Self, Self::Error> {
    |                                  ------------------------- expected `Result<RegS, OverflowError>` because of return type
620 |         u5::try_from(value as u8).map(RegS::from)
    |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected `Result<RegS, OverflowError>`, found `Result<RegS, OverflowError<u8>>`
    |
    = note: expected enum `Result<_, OverflowError<usize>>`
               found enum `Result<_, OverflowError<u8>>`

   Compiling httpdate v1.0.3
For more information about this error, try `rustc --explain E0308`.
error: could not compile `aluvm` (lib) due to 3 previous errors
warning: build failed, waiting for other jobs to finish...

Reproduction
Just start a new project in which you try to add rgb-lib as a dependency.

Please try to add
amplify_num = "=0.5.1"

to your list of dependencies, it should fix the error.

Hi, it indeed fixed the error! Thanks for the quick answer. Feels like black magic though (would be nice to know how this fixed it).
Cheers,

I'm happy it worked. Closing this


Unable to generate crypto config

Unable to generate crypto config and genesis block. Getting some error.

This code was developed for the 1.1 version of Hyperledger Fabric. Just last week, a new version (1.2) was released, so if you cloned fabric and fabric-ca recently, you are going to get the 1.2 branch by default.
I suspect this is the cause of the error you are seeing. Can you clone the release-1.1 branch of the Fabric repositories?

https://github.com/hyperledger/fabric/tree/release-1.1
https://github.com/hyperledger/fabric-ca/tree/release-1.1
Then rebuild the configtxgen and cryptogen tools, and retry the trade script using the instructions.

@shalini-kad If you scroll down the instructions in the network folder, you'll see that the requirement to clone the release-1.1 branch is clearly stated.


How can I use protoc and generate protobuf related files from a .proto file that is in another dir

├── order
│   ├── proto
│   │   ├── order.proto
├── notification
│   ├── Makefile
I have my order.proto on the order/proto dir and I wanna generate protobuf files from it being on the notification dir
Makefile content:
build:
  env GOOS=linux go build -ldflags="-s -w" -o bin/main cmd/main.go

protogen:
  protoc \
          --go_out=. \
          --go_opt=paths=source_relative \
          --go-grpc_out=. \
          --go-grpc_opt=paths=source_relative \
          ../order/proto/order.proto

But when I try to run make protogen I have the following error

"../order/proto/order.proto: File does not reside within any path specified using --proto_path (or -I).  You must specify a --proto_path which encompasses this file.

Just generated proto result from order dir and point --go-out to be the notification dir


Add Analytic as a held ability to Enchanted Items

Maybe Analytic was forgotten while writing the EI script.

Nice job! I'd merge it if I still had contributor access, but I'm basically retired now, so instead I'll just tag @TheImmortal

Looking good to me.


new teleop from Tyler

new teleop
interlock code (incomplete)
Before issuing a pull request, please see the contributing page.

hopefully praying


Error while setting up control4 platform for light

Updated the light.py file. After the reintegration, a C4 switch appeared as a unknown device with class light. The lights no longer function correctly. Lights turn On, but the UI displays "Failed to call service light/turn_on 224" when attempting to dim or turn Off. These errors now appear in the log:
2020-08-16 03:19:52 ERROR (MainThread) [homeassistant.components.light] Error while setting up control4 platform for light
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 192, in _async_setup_platform
    await asyncio.gather(*pending)
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 301, in async_add_entities
    await asyncio.gather(*tasks)
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 474, in _async_add_entity
    entity.async_write_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 281, in async_write_ha_state
    self._async_write_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 305, in _async_write_ha_state
    sstate = self.state
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 595, in state
    return STATE_ON if self.is_on else STATE_OFF
  File "/config/custom_components/control4/light.py", line 170, in is_on
    return self._coordinator.data[self._idx]["value"] > 0
KeyError: 224
2020-08-16 03:19:52 ERROR (MainThread) [homeassistant.components.light] control4: Error on device update!
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 335, in _async_add_entity
    await entity.async_device_update(warning=False)
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 454, in async_device_update
    await self.async_update()  # type: ignore
  File "/config/custom_components/control4/__init__.py", line 224, in async_update
    await self._coordinator.async_request_refresh()
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 125, in async_request_refresh
    await self._debounced_refresh.async_call()
  File "/usr/src/homeassistant/homeassistant/helpers/debounce.py", line 60, in async_call
    await self.hass.async_add_job(self.function)  # type: ignore
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 192, in async_refresh
    update_callback()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 281, in async_write_ha_state
    self._async_write_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 305, in _async_write_ha_state
    sstate = self.state
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 595, in state
    return STATE_ON if self.is_on else STATE_OFF
  File "/config/custom_components/control4/light.py", line 170, in is_on
    return self._coordinator.data[self._idx]["value"] > 0
KeyError: 224
2020-08-16 03:19:57 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 118, in _handle_refresh_interval
    await self.async_refresh()
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 192, in async_refresh
    update_callback()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 281, in async_write_ha_state
    self._async_write_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 305, in _async_write_ha_state
    sstate = self.state
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 595, in state
    return STATE_ON if self.is_on else STATE_OFF
  File "/config/custom_components/control4/light.py", line 170, in is_on
    return self._coordinator.data[self._idx]["value"] > 0
KeyError: 224

The Task exception error repeats every poll. Screenshots;

@garyak I've made another change, please redownload and try again.
I'm trying a different way of determining whether a light supports dimming or not - please check to see if the lights that support dimming dim and the ones that do not support dimming do not.

Lights on the C4 dimmers work again. They turn On/Off and dim using the Light Card. They don't retain their settings though. Getting lots of these:
2020-08-16 13:18:55 ERROR (MainThread) [homeassistant.components.light] Error while setting up control4 platform for light
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 192, in _async_setup_platform
    await asyncio.gather(*pending)
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 301, in async_add_entities
    await asyncio.gather(*tasks)
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 474, in _async_add_entity
    entity.async_write_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 281, in async_write_ha_state
    self._async_write_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 305, in _async_write_ha_state
    sstate = self.state
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 595, in state
    return STATE_ON if self.is_on else STATE_OFF
  File "/config/custom_components/control4/light.py", line 163, in is_on
    return self._coordinator.data[self._idx]["value"] > 0
KeyError: 223

New device has appeared:

The Sunfire Amp is a C4 remote switch controlling AC power to the amp.  Not sure if the wireless_outlet_switch is the same device. I'm only using one in my installation.

I created a card for the Sunfire Amp entity and can switch the amp on/off. I get a "Failed to call service light_on/off 223 for each action.

Lights on the C4 dimmers work again. They turn On/Off and dim using the Light Card. They don't retain their settings though.

@garyak What do you mean by "they don't retain their settings"?
It seems that the switch devices might be using a different Control4 API variable to show their state. I've updated the custom component again to provide more logging - please redownload and try again.

The Hue lights retain their settings between illumination events. So, if I set the illumination value to 50% then shutoff the light. Next time I turn the light On, it turns On at 50% without automation.
I'll update and report back.

2020-08-16 16:10:19 ERROR (MainThread) [custom_components.control4.light] Couldn't get light state data for Wireless Outlet Switch, skipping setup. Available item variables: <coroutine object C4Director.getItemVariables at 0x7f5bca6ecbc0>

Sorry @garyak I made a typo in the new logging code 🤦♂ Can you redownload and try it again?
The Hue lights retaining their settings is probably just a Hue function - Home Assistant is not supposed to do that, as far as I know.

Lights and switch still working as expected. I'm not testing inclusion in scenes or automation, but based on current behavior, I'd expect the lights to function normally with a service call. Setting retention doesn't come into play there. Here's what's in the log now:
2020-08-16 17:03:23 ERROR (MainThread) [custom_components.control4.light] Couldn't get light state data for Wireless Outlet Switch, skipping setup. Available item variables: [
 {
  "id": 223,
  "varName": "Outlet 1 Minutes On",
  "type": "Number",
  "hidden": 0,
  "value": 0,
  "variableId": 1000,
  "name": "Wireless Outlet Switch",
  "roomName": "AV Rack"
 },
 {
  "id": 223,
  "varName": "Outlet 1 Minutes Off",
  "type": "Number",
  "hidden": 0,
  "value": 4661,
  "variableId": 1001,
  "name": "Wireless Outlet Switch",
  "roomName": "AV Rack"
 },
 {
  "id": 223,
  "varName": "Outlet 1 Minutes On Today",
  "type": "Number",
  "hidden": 0,
  "value": 0,
  "variableId": 1002,
  "name": "Wireless Outlet Switch",
  "roomName": "AV Rack"
 },
 {
  "id": 223,
  "varName": "Outlet 2 Minutes On",
  "type": "Number",
  "hidden": 0,
  "value": 0,
  "variableId": 1003,
  "name": "Wireless Outlet Switch",
  "roomName": "AV Rack"
 },
 {
  "id": 223,
  "varName": "Outlet 2 Minutes Off",
  "type": "Number",
  "hidden": 0,
  "value": 4661,
  "variableId": 1004,
  "name": "Wireless Outlet Switch",
  "roomName": "AV Rack"
 },
 {
  "id": 223,
  "varName": "Outlet 2 Minutes On Today",
  "type": "Number",
  "hidden": 0,
  "value": 0,
  "variableId": 1005,
  "name": "Wireless Outlet Switch",
  "roomName": "AV Rack"
 }
]

@garyak From the log output, it seems that the Wireless Outlet doesn't provide any variables that can tell Home Assistant whether its on or not.
Can you screenshot what the Outlet looks like in the official Control4 app? It would be interesting to see if it can display the on/off state or not.

Actually @garyak I've pushed another change to the custom component that dumps info about all the devices on your Control4 controller into the error log, could you redownload and post the error output? (warning: it will be very long)
This should help me investigate how the Wireless Outlet works - it seems to be different than the normal lights.

The outlet isn't displayed on the C4 app. I'm getting status indirectly through the Sunfire Amp. The switch serves as the power switch for the amp.  These are the switch properties displayed in composer:

It is a single-purpose device. I'm sure others have a need for direct control, but I don't.  Right now the switch doesn't appear in integrations or entities. I can live without it. I'll continue to help test to determine whether or not you can access its status directly.

ha.log

@garyak Ah, your setup that ties the outlet switch to the Sunfire AMP probably removes the ability to control it directly - the AMP has all the properties that would usually be on the switch itself.
As long as everything else works fine, I think this issue can be closed. Users who don't tie their outlets to other devices should be able to control them directly with the code I've written.

Thanks for you work on this. Could you post a replacement light.py that produces the minimum of log contents? I'd sure like to have more control over my C4 setup. I'm certain I'm not alone in that desire. :-)

@garyak I've pushed a change that removes the unnecessary logging. It'll also be part of Home Assistant codebase soon (hopefully) https://github.com/home-assistant/core/pull/38952

@garyak This just looks like the connection to the Control4 servers timed out before it could login. If this only happens on HassOS I'd be inclined to think its a OS issue.

I've moved the installation back to the NUC. The start-up errors no longer appear in the HA Log. All software and configurations are identical. So far haven't had to redo the integration. I'll close this again and hopefully everything will continue to work.


Can't run Puppeteer in AWS Lambda.

I got this error when I run my scripts that use Puppeteer in Node.js.
{
  "errorType": "Error",
  "errorMessage": "Failed to launch the browser process!\n/tmp/chromium: error while loading shared libraries: libnss3.so: cannot open shared object file: No such file or directory\n\n\nTROUBLESHOOTING: https://pptr.dev/troubleshooting\n",
  "trace": [
    "Error: Failed to launch the browser process!",
    "/tmp/chromium: error while loading shared libraries: libnss3.so: cannot open shared object file: No such file or directory",
    "",
    "",
    "TROUBLESHOOTING: https://pptr.dev/troubleshooting",
    "",
    "    at Interface.onClose (/var/task/node_modules/@puppeteer/browsers/lib/cjs/launch.js:259:24)",
    "    at Interface.emit (node:events:525:35)",
    "    at Interface.close (node:internal/readline/interface:533:10)",
    "    at Socket.onend (node:internal/readline/interface:259:10)",
    "    at Socket.emit (node:events:525:35)",
    "    at endReadableNT (node:internal/streams/readable:1359:12)",
    "    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)"
  ]
}

Here is my script.
const Chromium = require('chrome-aws-lambda');
const puppeteer = require('puppeteer-extra');
const StealthPlugin = require('puppeteer-extra-plugin-stealth')
puppeteer.use(StealthPlugin())

const browser = await puppeteer.launch({
    args: Chromium.args,
    defaultViewport: Chromium.defaultViewport,
    executablePath: await Chromium.executablePath,
    headless: Chromium.headless,
    ignoreHTTPSErrors: true,
})
const page = await browser.newPage();
await page.setUserAgent('Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36')

How can I solve this problem?

@dev1ninja  I am also facing the same issue.
Any solution you found or still the same issue

@pandeysoni I am still facing the same issue.
It seems to be impossible to pass Cloudflare using chromium.
Just have to use Real Chrome Browser.
For this, the solution is to use Docker to install Google Chrome on AWS Lambda environment.
But I don't know how to do it.
Please let me know once you have solution.
I am also trying to find good solution now.

I am having the same issue

Failed to launch the browser process!
/tmp/chromium: error while loading shared libraries: libnss3.so: cannot open shared object file: No such file or directory

Looks like there may be an issue in the examples in the readme, I'm guessing it should be
await Chromium.executablePath()

Looks like there may be an issue in the examples in the readme, I'm guessing it should be
await Chromium.executablePath()

Heyy, it seems that is not it :(
node is throwing "executablePath is not a function"
What worked for me was downgrading my lambda to Node14.x!!
since the end-of-life for both versions starts in October i think it may solve our issue for now!

I switched to this and so far it's running (Node 18) on Lambda without any issue.

chrome-aws-lambda is not working on node 16 and node 18, it is an existing issue.
"@sparticuz/chromium": "^109.0.5",
"puppeteer-core": "^19.4.0"
combination in working for me on node 18

I finally managed to make it worked and described the solution here, hope it's helpful: https://konarskis.substack.com/p/puppeteer-aws-lambda
The key was to match the versions of puppeteer and chromium, and download the chromium binary at runtime as opposed to trying to put it inside the Lambda itself. This way, we don't need any layers, external dependencies, or other configuration changes.

I came across many articles on getting Puppeteer to work with Lambda; however, most of them relied on hacks, older versions, or third-party libraries. Wanting to keep my implementation as close to native libraries as possible, I opted to containerize my Lambda function. Almost all of these things are documented in official docs of respective libraries.
Project using Typescript
// tsconfig.json
{
  "compilerOptions": {
    "rootDir": "src",
    "outDir": "dist",
    "strict": true,
    "target": "es6",
    "module": "commonjs",
    "sourceMap": true,
    "esModuleInterop": true,
    "moduleResolution": "node",
    "types": ["jest", "node"]
  },
  "include": ["src/**/*"],
  "exclude": ["node_modules", "**/__test__/*"]
}

Build command
"build": "esbuild index.ts --bundle --minify --sourcemap --platform=node --target=es2020 --outfile=dist/index.js"

Dockerfile
FROM public.ecr.aws/lambda/nodejs:20 as builder
WORKDIR /usr/app
COPY package.json .

# Copy all the code files
COPY common/ ./common/
# Copy your code files as per your folder structure.

# Install and build
RUN npm install
RUN npm run build

# Build the running container
FROM public.ecr.aws/lambda/nodejs:20
WORKDIR ${LAMBDA_TASK_ROOT}
COPY --from=builder /usr/app/dist/* ./

 I am still yet to deploy this in Lambda, if someone wants it, I can share that info too.

I came across many articles on getting Puppeteer to work with Lambda; however, most of them relied on hacks, older versions, or third-party libraries. Wanting to keep my implementation as close to native libraries as possible, I opted to containerize my Lambda function. Almost all of these things are documented in official docs of respective libraries.
Project using Typescript

// tsconfig.json

{

  "compilerOptions": {

    "rootDir": "src",

    "outDir": "dist",

    "strict": true,

    "target": "es6",

    "module": "commonjs",

    "sourceMap": true,

    "esModuleInterop": true,

    "moduleResolution": "node",

    "types": ["jest", "node"]

  },

  "include": ["src/**/*"],

  "exclude": ["node_modules", "**/__test__/*"]

}

Build command

"build": "esbuild index.ts --bundle --minify --sourcemap --platform=node --target=es2020 --outfile=dist/index.js"

Dockerfile

FROM public.ecr.aws/lambda/nodejs:20 as builder

WORKDIR /usr/app

COPY package.json .

# Copy all the code files

COPY common/ ./common/

# Copy your code files as per your folder structure.

# Install and build

RUN npm install

RUN npm run build

# Build the running container

FROM public.ecr.aws/lambda/nodejs:20

WORKDIR ${LAMBDA_TASK_ROOT}

COPY --from=builder /usr/app/dist/* ./

 I am still yet to deploy this in Lambda, if someone wants it, I can share that info too.

It worked ? Just tried something similar and chrome fails to start in lambda.

@kbourro Partly. The containerized approach works in headless mode, but my requests were blocked by the site's CAPTCHA. I concluded that using residential proxies + Lambda or paid scraper services would solve this. In the end, I decided to host it on my local machine for my use case.
It wasn't worth the time for my use case.


Introduce namedImport property

I would love to have also namedImport property to tell react-loadable to get non-default component from module.
It could be simple property passed to babelInterop something like
let babelInterop = ( obj, key) => {
  // $FlowIgnore
  return obj && obj.__esModule ? (key ? obj[key] : obj.default) : obj;
};

It looks more user friendly than doing it manually in every loading,
For example in examples code when I want my non-default exported Example2 component
let LoadableExample = Loadable(
  () => fakeDelay(400).then(() => import('./Example').then(result => result.Example2)),
  Loading,
  null,
  path.resolve(__dirname, './Example')
);

I talked to @benjamn about adding an option resolveModule which would allow you to grab the right value no matter how react loadable is getting it

@ShockiTV Where would you provide the namedImport property? In the JSX for LoadableComponent?


Can this run in the browser? or made to?

OK so I am a total noob to web front end.  Recently I have been playing with chocobozzz/peertube and I find the performance pretty disappointing.  I notice that you have a node.js stack for finding peers and for streaming torrents.  I'd love to run it in the browser, of course.
Please, ELI5.

@faddat, check out peerflix-server.

Yes you can, just put your ip with the port 8888 and done.
Example: <IP_ADDRESS>:8888
Whatever computer or mobile in your wifi can also open the link in the browser.


DATE and time part in OCI_DateToText() and OCI_DateFromText()

library.c defines timeless part for DATE fields
static otext * FormatDefaultValues[OCI_FMT_COUNT] =
{
OCI_STRING_FORMAT_DATE,
while ocilib.h defines
OCI_STRING_FORMAT_DATE              OTEXT("YYYY-MM-DD")
I suppose it's not fully correct, because the DATE fields can hold time part as well, that way time information will be lost in OCI_DateToText() and OCI_DateFromText()
I propose to implement OCI_DateToText() using two formats by default, if user did not override default format and did not specify fmt argument:
YYYY-MM-DD if the DATE value does not define time part (i.e. 00:00:00), and
YYYY-MM-DD HH24:MI:SS if DATE value contains valuable time part
and OCI_DateFromText() - it will be better to handle both stings - with and without timing part by default, if user did not override default DATE format and did not specify fmt value in the call.
Though this proposal is discussable, and backward compatibility has to be provided - users which do use DATE fields for date values only should not get unexpected 00:00:00 in OCI_DateToText()  results, of course

Hi,
Current behavior is conformant with to_date() and to_char() SQL function behavior.
It no user provided format, it uses the defautl buit-in format and time part is omitted.
Users can either provide a format to these functions or set once a default format  (globally or on the connection object).
Proposed changes adds extra computation in these functions that must handle both legacy OCIDate and OCIDateTime struct).
Default build-in formats are just provided to make optional to pass a format to string conversion functions. (as for SQL functions).
I don't think that setting a user default format once at library startup is such a big thing.
I prefer to stick to SQL methods behavior.
Regards,
Vincent

Ok, that was discussable proposal.
I implemented task using preliminary check of DATE string value - if strlen(value) > strlen("YYYY-MM-DD") then try to convert with non-default format, but it looked ugly for me so I proposed to change default behavior.
From other hand - this example works fine
SELECT to_char(to_date('2011-11-11', 'YYYY-MM-DD HH24:MI:SS'), 'YYYY-MM-DD HH24:MI:SS') FROM dual

to_date() is able to convert string without specified time part.
I guess that changing default date format to YYYY-MM-DD HH24:MI:SS might be more generic and loss-less. User can always truncate the 00:00:00 part


Change close code guard to favour happy path

Check two ranges instead of three.

Great work! Thanks for the PR!

Great work! Thanks for the PR!

Ha! It turned out to be not really matter much in the end, since there are still 3 guard clauses. At least one of them isn't a range, though...


[8.x] Add option to release unique job locks before processing

Based on our discussion at https://github.com/laravel/framework/pull/35042, there may be use cases where it is desirable to release unique job locks before the job starts processing (to avoid race conditions between job completion and unlocking). This PR allows the option to release the unique job lock before processing if the $uniqueUntilStart is set to true like so:
class ExampleJob implements ShouldQueue, ShouldBeUnique
{
    use InteractsWithQueue, Queueable, Dispatchable;

    public $uniqueUntilStart = true;
}

This is backwards-compatible. If the job raises an error, we don't attempt to re-acquire the lock and may be duplicate enqueued. This should be fine as anyone who wants to use this feature would need to make sure that the job is idempotent because a duplicate job dispatch can happen while the job is processing. This is similar to Sidekiq's unique_until start feature.

@taylorotwell I've added a variable to ensure the lock is released only once in the job lifecycle.

Are we certain that the failed method is called on the same instance so that the variable's value is still in place?

Got rid of property. Added interface:
class SomeJob implements ShouldBeUniqueUntilProcessing
{

}


stats: Add stats page_params to webpack.assets.json.

In commit bcf03890c8ab9a61bb5a04e79ff9c91b942a3285, a separate page_params.ts was added for the stats/analytics page, but adding it to the web/webpack.assets.json for "stats" was missed, so we add that here.
Confirmed via manually testing in the dev environment that the stats page loads for the "Analytics" realm with these changes.

Self-review checklist

[ ] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[ ] Each commit is a coherent idea.
[ ] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[ ] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

Thanks for the catch, @laurynmm!  The commit hash in the commit message isn't right -- it was merged as 640de3ad2946db388a2d816bd8cc0ac0b9884062.  bcf03890c8ab9a61bb5a04e79ff9c91b942a3285 was the commit hash of it pre-rebase and merge.

Merged, thanks @laurynmm! @jychen630 FYI -- please be careful to always re-test your PRs whenever you make changes -- it's really easy to break things otherwise.


Follow canonical references in _(rev)include searches

Coverage: 94.252% (-0.01%) from 94.265% when pulling 5eed14b4275b85d1ba6e459d241c07df1a8f437b on search_follow_canonical into 8ba175ddd03e7a9d6aae2d9a277347b5d9efbd5d on main.


Scenario - callback on Scenario submission status change

When a scenario is submitted, we want the application to be notified when its status changes.
This allows for providing visual feedback on what is going on.
The minimum would be Running and Completed.

We need to be precise and careful about this.
Submitting a scenario consists in creating and running a bunch of jobs (potentially a few tens).
There is no status attached to a Scenario. Statuses are attached to jobs.
We don't want to notify the user for each job created/running/completed.
So we need to define what it means a running scenario status or a completed scenario status.

We should also know it in the GUI so that related visual elements refresh when the scenario is 'completed'.

Based on a discussion we had:
Context
In the future, Core should provide a Submission entity that should hold information related to submission, particularly the related entities (list of jobs, submittable) and a new status (compiled from the job statuses). Since taipy-core has not yet provided the Submission entity, here is a proposal to implement in taipy.
Callback proposal
The idea is to add an on_submission_change callback on the scenario viewer. Taipy will monitor Core notifications (at the Jobs level) and interpret these notifications to create a high-level object that the user can receive in this callback. The callback should be triggered when there is a change in one of the job entities related to the submission.
The proposal's goal is to ensure that the API we would offer in version 3.0 remains stable in the future.
def on_submission_change(state, submittable: [Submittable], details: dict)

The details dictionary (Renamed from status to details to avoid confusion. What do you think?) would contain high and low-level information about what has happened. In particular, it should contain the submission status compiled from the various job statuses.
So, until Core provides a Submission Entity, Core Elements would link a submission_id to the submittable entity and manage the list of jobs. Event monitoring would be set up when a user triggers the submission themselves. At that point, we can send these events to the user, and no one else.
If, in the future, we have higher-level events (like a Submission change event), we would have a new 'submission' key with the future Submission entity provided by Core, and no 'job', no job_status, and no submission status.
Examples
Here is an example of the details dict for 3.0 version:
{
   "submission_status": ["submitted", "running", "completed", "blocked"],
   "job": Job,
   "job_status": ["submitted", "running", "completed", "blocked"]
   "information": "..." # whatever it may be
}

In the example above, the submission status is created by GuiCore based on all the job statuses.
Here is an example of the details dict for 3.X version:
{
   "submission": Submission,
   "information": "..." # whatever it may be
}

In the example above, the submission is provided by Core and could directly contain the submission status.
Submission statuses
Here is the submission status proposal:
SUBMITTED: All the jobs are submitted. (This happens before the submit method returns, so I believe there is no need for None status).
BLOCKED: All the jobs are blocked.
PENDING: All the jobs are pending.
COMPLETED: All jobs are completed or skipped.
CANCELED: At least one job has a canceled status.
FAILED: At least one job has a failed status.
ABANDONED: There is no job canceled, no job failed, and at least one job is abandoned.
RUNNING: There is no canceled job, no failed job, no abandoned job, and at least one job has a running status.

@jrobinAV What is the submission status if it has one abandoned Job ?

@jrobinAV What is the submission status if it has one abandoned Job ? IF there is an abandoned Job, that means there is at least a canceled job in the list of jobs. So the Submission status is canceled

Here is my implementation of the submission status: please review
    def _get_submittable_status(self, jobs_ids: t.List[str]):
        status = _SubmissionStatus.UNDEFINED
        blocked = False
        waiting = False
        running = False
        completed = False
        for id in jobs_ids:
            job = core_get(id)
            if not job:
                continue
            if job.is_failed():
                status = _SubmissionStatus.FAILED
                break
            if job.is_canceled():
                status = _SubmissionStatus.CANCELED
                break
            if not blocked and job.is_blocked():
                blocked = True
            if not waiting and job.is_pending():
                waiting = True
            if not running and job.is_running():
                running = True
            if not completed and (job.is_completed() or job.is_skipped()):
                completed = True
        if status is _SubmissionStatus.UNDEFINED:
            if waiting:
                status = _SubmissionStatus.WAITING
            elif blocked:
                status = _SubmissionStatus.BLOCKED
            elif running:
                status = _SubmissionStatus.RUNNING
            elif completed:
                status = _SubmissionStatus.COMPLETED
        return status

It looks good to me, but some unit tests would give more guarantees it is working.


Update port mapping 4000 to 80 for consistency

Proposed changes
As of now, docker-compose.yml file ports section is in https://docs.docker.com/get-started/part3/, is not consistent with terminal recording and also with what is specified in https://docs.docker.com/get-started/part5/
diff --git a/get-started/part3.md b/get-started/part3.md
index 9a1436f571..95c5132bbd 100644
--- a/get-started/part3.md
+++ b/get-started/part3.md
@@ -84,7 +84,7 @@ services:
       restart_policy:
         condition: on-failure
     ports:
-      - "4000:80"
+      - "80:80"
     networks:
       - webnet
 networks:

Required changes

Unreleased project version (optional)

Related issues (optional)

Deploy preview for docsdocker ready!
Built with commit e5f7eff73277eb6829480f8c91b5a0b7e08e1fcf
https://deploy-preview-7789--docsdocker.netlify.com

GTG

@RobertGwilliam see https://github.com/docker/docker.github.io/pull/7862#discussion_r241912032 and https://github.com/docker/docker.github.io/pull/7865


azure: Updated to Azure ARM SDK 3.0

This fixes the dependency issue Steven was having.

You need to git add vendor/github.com/dgrijalva/.
shwangster@airbears2-10-142-32-162 ~/go/src/github.com/NetSys/quilt/vendor
 % git status
On branch tian
Changes to be committed:
  (use "git reset HEAD <file>..." to unstage)

        new file:   github.com/dgrijalva/jwt-go/MIGRATION_GUIDE.md
        new file:   github.com/dgrijalva/jwt-go/claims.go
        new file:   github.com/dgrijalva/jwt-go/map_claims.go

Merged


Routing wrong if change edge encoder access  at caculate weight edge

Describe the bug
I tried adjusting the access encoder at runtime but there was a problem with the results
To Reproduce
Steps to reproduce the behavior. For examples:

build graph use landmark
change access edge in at caculate weighting edge for only access one way fordward (or backward)
routing use querygraph and landmark then will bug because routing access wrong edge direction

I fixed it by:
update edge at orther thread call edge.set(encoder.access,fase)
I hope it can be adjusted at edge weight calculation

I don't understand your description. Do you have some code or a unit test that reproduces the issue? If you want to use landmarks you need to rebuild the landmarks after you make changes to the graph.

or even better: use a custom model


Support option to mirror exit status

Support an option to internally call process.exit(result.status).

Is that something that Node.js does?


Adding Superdense Coding

As per issue #136. I've implemented the superdense coding algorithm. I made a new folder in the examples folder and placed the .ipynb and .py files inside. I've also uploaded it to the toctree, so that the static jupyter notebook tutorial appears in the torchquantum docs.

@Hanrui-Wang Some of my commits are carried over from my previous PR 134. Please merge that one before this one.