ARROW-9402: [C++] Rework portable wrappers for checked integer arithmetic

Vendor relevant code from the portable-snippets library (~ public domain):
https://github.com/nemequ/portable-snippets/tree/master/safe-math
Also fix some bugs in checked arithmetic (null values had their value slots checked).
Add compute scaffolding for stateful binary scalar functions.

I think I finally squashed the horrid Windows preprocessor macro issues (Windows headers define OPTIONAL, but you can't undef it blindly because other subsequent includes may require it...).
AppVeyor build: https://ci.appveyor.com/project/pitrou/arrow/builds/34135787

@wesm You'll probably want to take a look at the codegen changes when you have some time.

Rebased. @wesm could you perhaps review this?

Or perhaps @bkietz .

I believe I addressed your comments @bkietz , so I'm going to merge now.


Version 2.3 Megalopullus request

Includes:

PR #618 Allow search bar to be hidden initially
PR #606 Adds capability for table_footer_view
PR #602 Add image inset support for tab bar item
PR #595 Feature/support module
PR #582 Allow setting of multiple nav bar buttons instead of just one left an one right
PR #581 Adds on_tab_selected
PR #579 implemented nav_bar_button class method RE #272
PR #565 Adds header_will_display method to PM::TableScreen

Will write a proper changelog soon.
I need help documenting the changes in /docs on this branch. @ryanlntn @silasjmatson @kevinvangelder @carlinisaacson.

Documented #618.

Documented #606.

Documented Checklist

[X] PR #618 Allow search bar to be hidden initially
[X] PR #606 Adds capability for table_footer_view
[ ] PR #602 Add image inset support for tab bar item
[ ] PR #595 Feature/support module
[ ] PR #582 Allow setting of multiple nav bar buttons instead of just one left an one right
[ ] PR #581 Adds on_tab_selected
[ ] PR #579 implemented nav_bar_button class method RE #272
[ ] PR #565 Adds header_will_display method to PM::TableScreen

@jamonholmgren The added features are now all documented.

@silasjmatson @kevinvangelder Thanks guys!

@jamonholmgren Updated docs per additional requests.

I think we're very close. However, I'd like to get all the outstanding bugs resolved (or as many as possible) before we merge this in. Maybe we can merge and launch Monday or Tuesday.

We are merged! I'll leave the version-2.3 branch alive for a while.


Not able to use 3 modal in a single page

Third popup is not visible
one
Two
Three

Your links all point to this issue!

no i want one modal at a time :)

please create a reduced testcase in jsfiddle.net or similar, so we can actually see the problem.

Please use StackOverflow, IRC, or Slack for troubleshooting questions; see https://github.com/twbs/bootstrap/blob/master/README.md#community for links.
If you're alleging a bug, there are specific requirements for bug reports; see https://github.com/twbs/bootstrap/blob/master/CONTRIBUTING.md#bug-reports

What's the answer to this question? I'm having the same problem.


Improve sync tool and add Berlin support

What was wrong?
The sync tool would deserialize blocks with the wrong hardfork for blocks near hardfork boundaries and did not support the new transaction types added in Berlin.
How was it fixed?
Split the Sync class into a Sync class and a Downloader class with independent tracking of the current fork. Add support for Berlin blocks.
Cute Animal Picture

Codecov Report

Merging #571 (ac050aa) into master (06a20af) will increase coverage by 2.84%.
The diff coverage is 98.47%.

@@            Coverage Diff             @@
##           master     #571      +/-   ##
==========================================
+ Coverage   77.82%   80.67%   +2.84%
==========================================
  Files         333      370      +37
  Lines       19219    21638    +2419
==========================================
+ Hits        14958    17456    +2498
+ Misses       4261     4182      -79

Flag
Coverage Δ

unittests
80.67% <98.47%> (+2.84%)
:arrow_up:

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

Impacted Files
Coverage Δ

src/ethereum/rlp.py
92.81% <73.07%> (-3.81%)
:arrow_down:

src/ethereum/berlin/utils/hexadecimal.py
87.50% <87.50%> (ø)

src/ethereum/base_types.py
88.73% <88.88%> (+<0.01%)
:arrow_up:

...ereum/berlin/vm/precompiled_contracts/ecrecover.py
93.33% <93.33%> (ø)

src/ethereum/berlin/spec.py
93.57% <93.57%> (ø)

src/ethereum/berlin/vm/interpreter.py
95.71% <95.71%> (ø)

src/ethereum/berlin/utils/message.py
96.00% <96.00%> (ø)

src/ethereum/berlin/trie.py
97.79% <97.79%> (ø)

src/ethereum/berlin/vm/gas.py
98.79% <98.79%> (ø)

src/ethereum/berlin/eth_types.py
99.00% <99.00%> (ø)

... and 32 more

Continue to review full report at Codecov.

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


Update dependencies and add workflow dispatch to test CI.

Description
This PR updates the composer dependencies to include PHPUnit, and modifies the minimum version of the johnpbloch/wordpress dependency from 5.4 to 6.1
The reason for the version bump is that the PHPUnit run appears to look for a wp-includes/class-wpdb.php file which has been introduced in WP 6.1. See: https://wordpress.org/support/topic/file-wp-db-php-is-deprecated-since-version-6-1-0/
Since this file was not present in 5.4, PHPUnit would fail.
Codeception
Codeception dependencies required version PHP 8.0 or above, so the CI would fail for the 7.2 and 7.3 versions of PHP. See comments for notes.
Additional Changes
Additionally, a .prettierrc file is added with settings to format the README.md file with line breaks automatically.

Closing this test PR and reopening in the main repo here: https://github.com/wp-graphql/wp-graphql-testcase/pull/26


The endpoint oauth2/token always throws "error": "invalid_client"

Describe the bug
The oauth2/authorize endpoint works to retrieve the code but when I try to exchange it I always get invalid_client.
From what I've seen when debugging the user is tested against the RegisteredClients and it always fails.

It seems that the two set of credentials (username:password, client_id:code+code verifier) get mixed up.
To Reproduce
I've implemented a basic Authorization server, link to github provided.

Generate code verifier + code challange
Go to the browser with the url http://localhost:9000/oauth2/authorize?response_type=code&client_id=client&scope=openid&redirect_uri=http://spring.io/auth&code_challange=8swP0rbhMPVIa20T9JSHXPMOLE1TcbC_SHrjMqg7fL4&code_challenge_method=S256 with the code challange value replaced. Get redirected to springio with the code in the url. - works fine
Postman post request to oauth2/token with the following parameters:

The username and password are base 64 encoded in the Authorization header

Also tried with postman basic auth and get the same result.

Expected behavior
To get the access token.
Actual behavior
Response: {
"error": "invalid_client"
}
Sample
[A link to a GitHub repository with a minimal, reproducible sample.
](https://github.com/cristian-ig/AuthCodeServer)
Reports that include a sample will take priority over reports that do not.
At times, we may require a sample, so it is good to try and include a sample up front.

@cristian-ig From what I can gather in your comments, the client is not authenticating at the token endpoint since you are not passing the client's credentials (only client_id and missing client_secret). Please review the default sample and the spec to understand how to setup the request parameters.


Rework subject sidebar to an overview

Given that we now have filtering on the table directly, the need for functional checkboxes on the subject sidebar is no longer needed. Rework SubjectHierarchy.tsx to an overview.

At the same time, remove the use of the any datatype and implement proper datatypes instead.


content write up - write articles related to Web Development or Textile

Write articles on Web Development or Textile on your own words.
Any article which will be copied from anywhere will not be accepted.
You will be an author of the article so send a photo, name, bio of yours(Optional).

Hello @sceary-expert, I would like to write an article on Web Development. Can you please assign it to me and help me.

Write your articles on README.md
, make a PR. If your article is unique and not copied from others I will surely merge that.

@Abhirv08 @anshrusia200 @lehmannrobb
Write your articles on README.md, make a PR. If your article is unique and not copied from others I will surely merge that.

I hope i can do the same @sceary-expert


Question on how to remove most (or all) of Preferences submenu

Hi. I'm sorry to open this as an Issue, but since there's no general discussion section, I didn't know how else to post this. Feel free to label this as a "Question"
This is going to sound odd and is admittedly an unorthodox request, but I'm looking for a way to remove almost all of the built in Preferences submenu that appears at the end of any BitBar plugin menu. I won't go in depth into the reasons for this, but suffice to say that the manner that I'm looking to use BitBar doesn't require the end user to be able to see things like the version string or the Quit menu line. I might want to keep the Refresh all in there as a failsafe in the event that a plugin gets stuck during a refresh from within the menu I've built.
Since this is obviously not something most people using BitBar would really want, I'm perfectly happy with using a custom build from Xcode to achieve this. I did some exploration in the Xcode project and I see the lines that generate most of the Preferences submenu, in the PluginManager.m file. The problem is, not being a developer, I'm not certain on the best approach to removing these without messing up BitBar's functionality. Also, as mentioned, i'd like to keep just the "Refresh all" line and remove the others from it if possible.
Can anyone provide a quick guide on what would need to be commented out from that file to remove those sections without breaking it completely?
Thanks in advance for any help with this.

Check this out: https://github.com/matryer/bitbar/blob/master/Docs/DistributingBitBar.md

Thanks. But, unless something has changed very recently, the BitBar distro version still shows those additional items under Preferences. I'm already using the plist key to disable advanced user settings with BitBar, which is great, but there are still "Refresh all", "Version" and "Quit" items under it. I don't care too much about the version string, but I would like to remove the Quit function from it. Basically, I don't want our users to quit it, either accidentally or on purpose.
To combat that, I already have a separate app (script wrapped as an executable) which will look to see if BitBar is running, and if not, launches it when its double clicked, or exits silently if it is running already. Its a "launcher" of sorts, since its possible for someone to quit it and not know exactly how to re-open it. I'm doing this because we're planning on putting BitBar into a normally hidden location on the system as part of the deployment.

Sounds a bit suspicious to me :D
The best place to discuss this is our Slack channel: https://getbitbar.herokuapp.com

Hmm. OK, I can understand why you might think that, but I assure you this is not some attempt to push malware or spyware onto users. I'm simply trying to make our plugin appear as much like a regular menu item as possible, and not like a separate application. I did state this was a little unorthodox right up front so I'm not looking for any built in functionality to be put into the product. Just wanted to see if there was a simple way to do this within the project code.
Anyway, thanks for the slack channel link - I wasn't aware there was one. I'll join up to be part of the discussions.

I was just kidding :)
One option is to fork the project and delete the code that adds those items. But if it’s something others might want, then perhaps making them configurable is a good idea.

On 28 Jun 2016, at 16:39, Mike M<EMAIL_ADDRESS>wrote:
Hmm. OK, I can understand why you might think that, but I assure you this is not some attempt to push malware or spyware onto users. I'm simply trying to make our plugin appear as much like a regular menu item as possible, and not like a separate application. I did state this was a little unorthodox right up front so I'm not looking for any built in functionality to be put into the product. Just wanted to see if there was a simple way to do this within the project code.
Anyway, thanks for the slack channel link - I wasn't aware there was one. I'll join up to be part of the discussions.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub https://github.com/matryer/bitbar/issues/347#issuecomment-229089162, or mute the thread https://github.com/notifications/unsubscribe/AAGNG_j_C9jDjdv560PdFOqJSuKJhIKtks5qQUA3gaJpZM4JANbs.

Yeah, I actually already got the Quit menu removed just now with the project. Its simple enough actually. I wasn't certain it would work, but it compiled perfectly and is running without the Quit item in it.
I'm not totally certain how useful this might be for others, but I guess I could float the idea on the Slack channel to see what others think. My only reservation with removing the whole of the Preferences submenu is that, I've seen an odd case or two of a machine waking from sleep and the plugin refreshes getting permanently stuck in a refresh state and never rendering. In those cases, the only thing that shows up is that Preferences submenu since its not tied to the plugin itself. When that's happened, the Refresh all or even the Quit has come in handy to force a refresh or kill it and then relaunch it.
I guess its something to ponder about whether its worth the risk of removing it altogether.


Headers

Adresses #18

I added comments quoting the QPACK spec where I thought it was needed.
I think this is ready for another review.


Unable Visualizing Data

Hello,

Grafana 8.2.2 and the plugin are installed inside container following your example,
Data Source is configured and test sucessfully passed (see attached screen shoot),

I'm using mosquito broker configured to use websocket,
Mqtt messages generated from Node Red, I can see posted messages using subscriber in Node Red Flow,
I can see client (Node red and Grafana) connected to the Mosquito and I can see messages sent to both.
At the End, no data are displayed inside my Time Series Panel. Panel is configured to use the same topic as NR of course, data is raw value in String UTF8, query inspector does display anything :

Thanks for your help

Hi @Vital91 thanks for raising this. I haven't had a chance to test with more recent versions of Grafana, and it's possible that something has changed.
I'm also aware that there is now an official MQTT plugin that's been developed and maintained by Grafana (it was announced shortly after I developed this one). Have you had a chance to give that one a shot?

Hi, thanks for your quick reply :-).
May be I can test with the grafana version you have used for the dev ?
I will have a look on this official MQTT plugins but so far I found your project, the one you are mentioning and this one : https://github.com/grafana/mqtt-datasource/blob/main/README.md

Hi again, I have checked the grafana plugins, looks like it is not really finished yet, my main concerne is that it must be installed using yarn and I want to install it in Docker image excactly in the way you did it.
Do you remind the grafana version used for your Dev ?

Ok I see - that's true, I think the other one does need to be built from source currently.
If I'm not mistaken I previously tested with Grafana 8.1.0. You can also check your browser's JavaScript console log for any potential error messages.


misaligned yaml format

https://github.com/Yelp/elastalert/blob/f4bad06f35e44d664072f9a7a80580650c62fbef/example_rules/ssh.yaml#L2

will create a pr

will open this one line code

https://github.com/Yelp/elastalert/pull/2692

@yabetsu93  ping

@nsano-rururu thanks


Feature Request: Be able to call shared_from_this after an object has been constructed in load_and_construct

It would be hugely beneficial for quite a few of my systems to be able to call shared_from_this after construct().  In many of my things when I create them I utilize shared_ptr in interfaces and being able to pass a shared_ptr after construction is part of my factory methods that make these objects in the first place.  In this regard, being able to do the same work my factory methods are doing in the deserialization process would be super streamlined.
Is there a technical reason that makes it impossible for shared_from_this to return a valid shared_ptr?
Or, atlernatively, is there a way you could expose the shared_ptr that's currently being populated via the cereal::construct object?  IE: Could I call construct.shared_ptr() or construct.shared_from_this() to get the shared_ptr.
#include <stringstream>
#include <iostream>
#include "cereal/cereal.hpp"

struct SharedFromThisPlease : public std::enable_shared_from_this<SharedFromThisPlease> {
	virtual ~SharedFromThisPlease(){}

	template <class Archive>
	void serialize(Archive & archive) {}

	template <class Archive>
	static void load_and_construct(Archive & archive, cereal::construct<SharedFromThisPlease> &construct) {
		construct();
		auto selfReference = construct->shared_from_this(); //Breaks here currently
	}
};

#include "cereal/archives/json.hpp"

int main(){
	std::stringstream stream;

	{
		cereal::JSONOutputArchive archive(stream);
		archive(std::make_shared<SharedFromThisPlease>());
	}

	std::shared_ptr<SharedFromThisPlease> loadedResult;
	{
		cereal::JSONInputArchive archive(stream);
		archive(loadedResult);
	}
}

I think we can resolve this.
If you are curious, the error occurs because when we hand things off to you to do your construction and initialization, this is all happening on a buffer of memory so as not to mess up the underlying weak_ptr that powers shared_from_this (when you do construction, it would overwrite the true weak_ptr). This also means that if you call shared_from_this, you are going to run into problems. When you exit the load_and_construct call, which happens on line 157 in memory.hpp, the destructor for the EnableSharedStateHelper restores the weak_ptr and you can call shared_from_this in peace.
So to fix it we just need to make sure that the weak_ptr is restored as soon as you call construct(), instead of after you exit load_and_construct, which will take some code shuffling to get working.

I'm really excited about this, I was using a goofy "initialized" bool in some places and doing an initialization conditional on that bool in an update method for some of my components.  This wasn't ideal and having this enhancement will be awesome for cleaning that up.

Rad, I had just implemented this, but not in as good a way as you did.  I'm giving this a try!  Thanks dude! :dancers:


CSS Variables

It would be nice to have a simple way for defining variables.
Inheritance is a nice feature, but it doesn't cover every use case.
How about supporting the  :root pseudo-class selector, so that we could have:
variables.css
.colors {
  --color-red: red;
  --color-blue: blue;
}

.fontSizes {
  --font-size-normal: 12px;
  --font-size-large: 14px;
}

component.css
:root {
  extends: colors from "shared/styles/variables.css";
}

.foo {
  color: var(--color-red);
}

transpiled to:
:root {
  --color-blue: blue;
  --color-red: red;
}

.foo {
  color: var(--color-red);
}

This works out of the box in Firefox and it can be transpiled back to CSS2 with postcss-custom-properties

I found an alternative solution by removing importLoaders from css-loader and using postcss-import instead.
With the following configuration in webpack.config.js:
module: {
  loaders: [
    { test: /\.css$/, loaders: ['style-loader', 'css-loader?module&localIdentName=[name]__[local]___[hash:base64:5]', 'postcss'] }
  ]
},

postcss: [
  require('postcss-import'),
  require('postcss-color-rebeccapurple'),
  require('postcss-custom-properties')()
  require('autoprefixer-core')
],
// ...

I can transpile something like:
colors.css
:root {
  --color-red: red;
}

component.css
@import url("../shared/styles/colors.css");

.foo {
  color: var(--color-red);
}

to:
.Component__foo___16yOh {
 color: red;
}


quotable talkback

note that just setting ADMIN_GROUP (and dropping https://github.com/mobilecoinofficial/forest/blob/main/forest/core.py#L433  and not utils.AUXIN once appropriate) does the thing we want

ilia_76ae ( +1555123XXXX ) says: testing testing

(hotline)

ilia_76ae says: love tree

(mainline)
I think this supports both?


MangaTales : Source request

Source name
MangaTales
Source link
https://mangatales.com/
Source language
Arabic
Other details
uses GMANGA theme
Acknowledgements

[X] I have checked that the extension does not already exist by searching the extension listing and verified it does not appear there.
[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a meaningful title with the source name.
[ ] I have admitted that I am a clown by having checked this box, as I have not read these acknowledgements.
[X] I will fill out all of the requested information in this form.

Uses GMANGA theme


PostgreSql - Added case sensitive table and field names and some conditions

Fixed #450 and added ILIKE, NOT ILIKE, BETWEEN and NOT BETWEEN where conditions for postgres.

Coverage remained the same at 93.329% when pulling 00f5697a8622854880a222b0de6d691b3ac3b4d7 on GuilhermeReda:master into 959ac7054d41173c4a151524db6729fdb176f11d on 75team:master.

@welefen and @GuilhermeReda this PR break queries.
Explain:
yield this.model("some_table")
          .field([
            '"some_table"."some_field_1" AS "field_1"',
            '"some_table"."some_field_2" AS "field_2"',
            '"some_table"."some_field_3" AS "field_3"',
            ...
            '"another_table"."some_field_N" AS "field_N"',
          ])
          .join('"another_table" ON (....)')
          .where(`"some_table"."some_field_1" = ${some_var}`)
          .select();

this will generate in PostgreSQL next query:
select ""some_table"."some_field_1" AS "field_1"",
            ""some_table"."some_field_2" AS "field_2"",
            ""some_table"."some_field_3" AS "field_3"",
            ...
            ""another_table"."some_field_N" AS "field_N"",
....

so, it's wrong.
problem here - https://github.com/75team/thinkjs/pull/451/files#diff-55a5d5e9ab2678195c04299e06527bdbR235

Ahh, ok.
Gotta check if " already exists.

@GuilhermeReda i'm create issue #459


Add docker engine version

We are now based AWS AMI ECS and following the official version up to date.
as today, the version in production are Docker version 17.03.1-ce, build 7392c3b/17.03.1-ce


network is not set correctly by tugbot for test containers with configured network

For instance, running this:
docker service create --name votests \
    --network voteapp \
    --env appHost=voting-app:80 \
    --env dbHost=db \
    --restart-condition none \
    gaiadocker/example-voting-app-tests

first run works fine and when we check the first run with docker inspect we can see this network:
 "Networks": {
                "voteapp": {
                    "IPAMConfig": {
                        "IPv4Address": "<IP_ADDRESS>"
                    },
                    "Links": null,
                    "Aliases": [
                        "e63376e6e919"
                    ],
                    "NetworkID": "0az17gx7v48dou7oxfkcz3fsq",
                    "EndpointID": "",
                    "Gateway": "",
                    "IPAddress": "",
                    "IPPrefixLen": 0,
                    "IPv6Gateway": "",
                    "GlobalIPv6Address": "",
                    "GlobalIPv6PrefixLen": 0,
                    "MacAddress": ""
                }
            }

on the second run by tugbot we can see this network configured:
 "Networks": {
                "bridge": {
                    "IPAMConfig": null,
                    "Links": null,
                    "Aliases": null,
                    "NetworkID": "1354094bfb54592eb23e92f7aab913ac6c511c7294bef0de24436ed66ea554c2",
                    "EndpointID": "",
                    "Gateway": "",
                    "IPAddress": "",
                    "IPPrefixLen": 0,
                    "IPv6Gateway": "",
                    "GlobalIPv6Address": "",
                    "GlobalIPv6PrefixLen": 0,
                    "MacAddress": ""
                }
            }

We need to get list of "connected" networks from exited container and connect newly created container to above networks using Docker API (ConnectNetwork).

Fixed


Add Quick Sort in C++

Added Quick Sort Algorithm in C++

congratulations on your hactoberfest contribution. if you like this repo then give it a star. Happy hacking..


Invalid JSON

The json file found here https://raw.githubusercontent.com/dzuk-mutant/blockchain/master/blockchain.json does not parse because it is missing a comma making it unusable for automated blocking.

I have corrected the issue in the following PR https://github.com/dzuk-mutant/blockchain/pull/3

I just published my own fix before I could read that you had made a PR. It should be fine now!


Content - Revise NoA wording & Self-Report Warnings

Description
Make several distinct changes to the content wording reflected on a student's NoA to ensure clarity & add more strict warnings whenever student uses the 'self-report' feature for their parent/partner income

Acceptance Criteria:

[ ] Add Disbursement Dates to Award Breakdown Column
[ ] Add PY max amounts to award breakdown column

@HRAGANBC can you please connect with Jeremy on this one. Astrid you can choose to edit this ticket or create a new one post convo

@JerPearson to recycle this ticket with his final suggestions for NoA revisiosn


Add TSLint

https://github.com/MasterLemon2016/LeanMood/wiki/TSLint

Good stuff, now we have to plan when to move this to the build process. I would say first let's comment this on the salck channel, let's add an issue to make all the code compliant, and then make this mandatory


Strip leading "I" from interface name

Is your feature request related to a problem?
When writing interfaces in C# i follow the naming convention of placing an I in front of the name, so an interface for a message becomes IMessage. When using this interface as a GraphQL interface type, I don't want to have the leading I, as this is not a common naming convention. Therefore I often find myself renaming interface types to strip of  the leading "I":
[InterfaceType("Message")]
public interface IMessage
{
}

The solution you'd like
Hot Chocolate should introduce a new naming Convention that strips of the leading "I", if the type is an interface type and if the second character is also capital (optional).
Maybe there will be some false positives with people not naming their C# interfaces per convention, but those shouldn't be the norm and they can still opt to explicitly naming the interface type.
Product
Hot Chocolate

This could be a option ... There are interfaces without the leading I that is why I did not add something until now. But we can provide an output on the the schema options.

We currently add our own type interceptor to do exactly this.


Find header picture for "Register" page

Find header picture for "Register" page: https://2023.foss4g.org/register/
Picture should be dark enough so the text is readable.

I've put a "random" picture for now but we need to find a picture related to the venue/topic.


backport: bitcoin#18788, #18974, #19230, #19239, #19441, #19568, #19668, #20226, #21049 (descriptor wallets part II)

What was done?
This PR continues supporting of Descriptor Wallets, see https://github.com/dashpay/dash/pull/5579 for prior work.
Particularly:

bitcoin/bitcoin#18974
bitcoin/bitcoin#19230
bitcoin/bitcoin#19239
bitcoin/bitcoin#19441
bitcoin/bitcoin#19568
bitcoin/bitcoin#19668
bitcoin/bitcoin#20226
bitcoin/bitcoin#21049
bitcoin/bitcoin#18788
And some minor dashification for  bitcoin/bitcoin#18067

How Has This Been Tested?
Run unit + functional test. Backport bitcoin#18788 enables descriptor wallets for multiple functional tests.
Breaking Changes
N/A
Checklist:

[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have added or updated relevant unit/integration/functional/e2e tests
[ ] I have made corresponding changes to the documentation
[x] I have assigned this pull request to a milestone

Any objects to delaying this to post v20.1?

Any objects to delaying this to post v20.1?
no, it can't be merged before https://github.com/dashpay/dash/pull/5579 anyway


Issue :Change the Hard disk size in current Vm

@rajesh-rajagopal                                                                                yesterday i create one VM name Rapro in Centos and Hd size 303 gb but Customer says only 4 gb show the

Disk size so pls check and  solve it then let me know

yesterday i create one VM name Rapro in Centos and Hd size 303 gb but Customer says only 4 gb show the
Disk size so pls check and  solve it then let me know @rajesh-rajagopal

Ok. I will check it

VM root size is changed..


Automate_OpenSwan.sh

#!/bin/bash
clear
# echo "Hello $USER"
# echo
# echo "Today's date is `date`, this is week `date +"%V"`."
# echo
# echo "These users are currently connected:"
# w | cut -d " " -f 1 - | grep -v USER | sort -u
# echo
# echo "This is `uname -s` running on a `uname -m` processor."
# echo
# echo "This is the uptime information:"
# uptime
# echo
echo "This script is provided by cloud-gateway team to configure your network for scaling to public clouds on peak workloads.  Automation starts now."

# Q. Will I be needing any information from the user or from the user's environment?
# A. 5 : left IP,subnet and right IP,subnet and PSK

# Q. How will I store that information?
# A. Variables

# Q. Are there any files that need to be created? Where and with which permissions and ownerships?
# A. Everything here needs sudo priveledges

# Q. What commands will I use? When using the script on different systems, do all these systems have these commands in the required versions?
# A. https://github.com/BU-NU-CLOUD-SP16/cloud-gateway/issues/2#issuecomment-186081235

# Q. Does the user need any notifications? When and why?
# A. - Success on openswan install
#    - Enabled Redirects
#    - Sysctl configured
#    - ipsec configured
#    - Pre Shared Key created as "cloud-gateway"
#    - Tunnel Started
#    - Verifying tunnel status

# We can even prompt user but i don't think thats the way admins would like
# echo -n "Enter your LEFT IP and press [ENTER]: "
# read LEFT_IP

if [ $# -lt 5 ]; then
        echo "Usage: ./automate.sh LEFT_IP LEFT_SUBNET RIGHT_IP RIGHT_SUBNET PSK"
        exit 1
fi
# Below command is used to extract Left IP from a user's VM
# ifconfig | grep -A 1 enp0s3 | grep "inet addr:" | cut -d ":" -f2 | cut -d " " -f1
# ifconfig | grep -A 1 enp0s3 | grep "Bcast:" | cut -d ":" -f2 | cut -d " " -f1
LEFT_IP=$1
LEFT_SUBNET=$2
RIGHT_IP=$3
RIGHT_SUBNET=$4
PSK=$5
# Need to color these variables later on
echo "Your IP Address: $LEFT_IP"
echo "Your Subnet Address: $LEFT_SUBNET"
echo "Public Gateway IP Address: $RIGHT_IP"
echo "Public Gateway Subnet Address: $RIGHT_SUBNET"
echo "Pre Shared Key: $PSK"

echo "Installing openswan"
apt-get install openswan

echo "Enable Redirects"
for path in /proc/sys/net/ipv4/conf/*;
do echo 0 > $path/accept_redirects;
echo 0 > $path/send_redirects;
done

echo "Configuring Sysctl"
echo net.ipv4.ip_forward = 1 >> /etc/sysctl.conf
echo net.ipv4.conf.all.accept_redirects = 0 >> /etc/sysctl.conf
echo net.ipv4.conf.all.send_redirects = 0 >> /etc/sysctl.conf
echo 1 > /proc/sys/net/ipv4/ip_forward

echo "Configuring ipsec"
# sed 's/^#.*id$/leftid=$LEFT_IP/' /etc/ipsec.conf

echo "Creating PSK"
cat $LEFT_IP $RIGHT_IP: PSK "cloud-gateway" >> /etc/ipsec.secrets

echo "Tunnel Started"
service ipsec restart

echo "Verifying tunnel status"
ipsec verify

echo "Tunnel status"
service ipsec status

Would u mind also posting the output of running this script?

start with sudo
USAGE: ./Automate_OpenSwan.sh LEFT_IP LEFT_SUBNET RIGHT_IP RIGHT_SUBNET PSK

It relies upon us to make it interactive or not.
We want to replace data or just append i.e. SED or basic >> would work.
I don't have Ubuntu so would check tomorrow with you guys.

please add validity checks to the user inputs.

let's put that to next sprint... just make sure it work first

@ChienliMa how do we guarantee as the devices to be configured.. e.g. eth0 or enp0s3 ?

@singhay: i think we can add a smoke test at the end of the script for that.


Suggest

Can u add fitrue depends area pos1 pos2

No, Please look again at the plugin name or use this plugin https://poggit.pmmp.io/p/MagicWE2


fixed todo item

I'd recommend this https://gasprice.poa.network

Thanks, must have missed this. Brownie uses the gasnow API for it's native gas_strategies (never heard of it until brownie), so I'll probably stick with that.


 Thats the same behavior of https://lodash.com/docs/4.17.11#throttle and https://underscorejs.org/#throttle as well.
Right now throttleTime does it more like:
      const e1 =   hot('abcdefabcdefabcdefabcdefa|');
      const expected = 'a----fa----fa----fa----fa|';

@benlesh I seem to always come at the worst time ... when you prepare the next major version :D. But was there the possibility to include this in rxjs7?

Is this not a duplicate of #4727?

Oh indeed it is. Haven't seen it. But https://github.com/ReactiveX/rxjs/pull/4727 schedules the timer after emitting the value. IMO it's important that scheduling always happens upfront, so user code (if slow) doesn't mess with the timings.

i give up again, I hope @MatthiasKunnen has more stamina

I got you @sod. I wanna see this through.


Create a new safe divide cross db macro

Describe the feature
I want to add a "safe divide" cross dbt macro (like DIV0 in snowflake) to prevent errors when dividing by 0.
Describe alternatives you've considered
Additional context
Who will this benefit?
Package developers - we're currently using nullif() on the denominator in dbt_project_evaluator package and would like to replace this with a simple safe divide macro.
Are you interested in contributing this feature?

Yes. I, @angelica-lastra, and @deanna-minnick will be collaborating on this!

We talked about this internally - excited to see it come together!


reload

like nginx

Could you explain because nginx allows reloading of its config but it is done differently, specifically through sending a signal to the process and acting on that, which may result in downtime but assuming nothing is wrong like an error, its usually not noticeable. With how torchbear is designed, it may not be straight forward.

Yea, I think this is rather an issue for Lighttouch.  I just want to run the loaders over again with new code.

on second thought, having to restart Torchbear to make Lua script changes take effect is related


Fix re-sync from bad position

This pull request fixes an issue where siddontang skips a transaction when re-connecting to the database after its connection is severed.

Thanks @ianzapolsky
CI failed.

ping @ianzapolsky , thanks for your pr, please fix CI

BTW, please also fix the issue
does this still have a problem with the Query event BEGIN in DML event sequences like following
| bin.000001 | 16597 | Gtid           |       101 |       16662 | SET @@SESSION.GTID_NEXT= '9afe121c-40c2-11e9-9ec7-0242ac110002:55'                                                                                |
| bin.000001 | 16662 | Query          |       101 |       16730 | BEGIN                                                                                |
| bin.000001 | 16730 | Table_map      |       101 |       16791 | table_id: 11993 (sharding1.t2)                                                                                |
| bin.000001 | 16791 | Update_rows    |       101 |       17277 | table_id: 11993 flags: STMT_END_F                                                                                |
| bin.000001 | 17277 | Xid            |       101 |       17308 | COMMIT /* xid=51083 */

Originally posted by @amyangfei in https://github.com/siddontang/go-mysql/pull/416

@gleonid has a good solution to this in #420. Let's go with that.

thanks @ianzapolsky
I will close this PR.


Fixed Mission File

Removed the missing .paa's from stuff, Will now boot normally.

Hi Hootsir,
Thank you for submitting a pull request.
I have a question, did you have any DLCs enabled when you changed this? I guess you changed it in the mission editor (3DEN)?

All I did was removal of .paas nothing else was added, it was a simple fix,
it was done via 3DEN
On Sun, Sep 23, 2018 at 09:40 Simon Arledal<EMAIL_ADDRESS>wrote:

Hi Hootsir,
Thank you for submitting a pull request.
I have a question, did you have any DLCs enabled when you changed this? I
guess you changed it in the mission editor (3DEN)?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/SimZor/A3RPGFramework/pull/11#issuecomment-423821397,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQcWD1Sr7MblTEKN04lb7omnbLa4qJvKks5ud51egaJpZM4W1sv0
.

I got you bud no worries
On Wed, Sep 26, 2018 at 05:25 Simon Arledal<EMAIL_ADDRESS>wrote:

Merged #11 https://github.com/SimZor/A3RPGFramework/pull/11 into master.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/SimZor/A3RPGFramework/pull/11#event-1868007611, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AQcWD_BvDfNA7-zGpL-T-0a89fGxWbtYks5ue1YBgaJpZM4W1sv0
.


feat: Recent generative nft mints in drop page

PR Type

[ ] Bugfix
[x] Feature
[ ] Refactoring

Context

[x] Closes #9476

Needs Design check

@exezbcz please review

Did your issue had any of the "$" label on it?

[x] Fill up your DOT address: Payout

Screenshot 📸

[x] My fix has changed something on UI;

bullish

top margin to 80px please

- padding to 12px at least? (inside the card for the text)

top margin to 80px please

only margin-top

on mobile it can probably stack on top of each other

so on top is heading, under are filters

i think some unneeded parameters are being passed if you filter and click on an nft
?listed=true https://deploy-preview-9536--koda-canary.netlify.app/ahp/gallery/99-92?listed=true
otherwise looks good

as @hassnian discovered is actually from canary, will open issue

Thanks, very well made!
pay 70 usd

😍 Perfect, I’ve sent the payout
💵 $70 @ 7.88 USD/DOT ~ 8.883 $DOT
🧗 16faLfsywwNATaEfbH2ah75dn6ZmctQWpMS5G4KFhbmj5hnD
🔗 0xa148fe1b9c1542ab878595eba9d27879de91828239e8251da63523ce6ad563e3
🪅 Let’s grab another issue and get rewarded!
🪄 github.com/kodadot/nft-gallery/issues


ISS-159 neovim failed during compilation with invalid pointer dereference

neovim failed during compilation with invalid pointer dereference
../neovim/src/nvim/buffer.h:141:          && *ml_get_buf(buf, (linenr_T)1) == '\0';
^ type.c invalid pointer dereference

it seems that neovim project uses lots of old style some functions not defined in h files but in C files...


DynamoDB - also look at Global indexes to see if the value of a sort key is too big

Closes #3974
This PR also moves some tests around to make it more readable/searchable - the relevant new tests is test_put_long_string_gsi_range_key_exception

Codecov Report

Merging #4632 (cdfe1c3) into master (5fa932c) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master    #4632   +/-   ##
=======================================
  Coverage   95.23%   95.24%
=======================================
  Files         535      535
  Lines       59878    59886    +8
=======================================
+ Hits        57023    57036   +13
+ Misses       2855     2850    -5

Flag
Coverage Δ

servertests
47.63% <83.33%> (+0.01%)
:arrow_up:

test_responses
32.38% <8.33%> (-0.01%)
:arrow_down:

unittests
95.15% <100.00%> (+<0.01%)
:arrow_up:

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

Impacted Files
Coverage Δ

moto/dynamodb2/models/__init__.py
96.48% <100.00%> (+0.56%)
:arrow_up:

Continue to review full report at Codecov.

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


Select menu for mime type, driven by authority config files

Removing conforms_to in favor of mime_type values with extra attributes to differentiate different XML-based metadata formats

Fixes #87

@drh @johnhuck @jrgriffiniii @yulgit1 what do you think of this approach? It seems reasonable to indicate FileSet type for external metadata files in the same way as vector, raster, and image file sets - using mime type with a parameter instead of conformsTo. I think having two separate mechanisms for this is overly complex.

That's fine with me. MODS already has the MIME type application/mods+xml

@escowles In regards to metadata MIME types, MODS is the only officially registered type in the group. I don't think we should be using application/*+xml for all of them.

What would you do instead? I don't think I'd recommend the x- syntax:
https://tools.ietf.org/html/rfc6838#section-3.4
Maybe better to go with what the assumed media type would be, and then start the registration process? I don't think it's too difficult.

The previous versions were application/xml; schema=iso19139 and application/xml; schema=fgdc.  The schema= part is completely made up, but follows the ogr-format and gdal-format pattern used for the other formats.
If you google "application/fgdc+xml", you'll see a few hits, though it isn't registered at https://www.iana.org/assignments/media-types .

@jpstroop We thought about that, but the issue is the same with geospatial data formats. That's why the data modeling group settled on noting the file format with a parameter. Except in cases where there is an existing registered type.

I'm not sure of the rules, but it seems reasonable to me that the group responsible for creating and maintaining standards should register the mime type.

@eliotjordan yes. We did this for MODS and MARC, etc. when I was on the MODS editorial committee:
https://tools.ietf.org/html/rfc6207
I'd definitely recommend pressuring whoever is in charge of these GIS specs to get them registered. I don't recall it being difficult.


Totsugeki unable to patch - Message: "Could not patch GGST..."

Does this issue happen when you don't use Totsugeki?
No, the error is a result of totsugeki not being able to patch GGST
Totsugeki Version and logs
Version:  v1.1.4

Steps to Reproduce

Start GGST from the steam library and run totsugeki.exe with the -no-launch argument or double click totsugeki.exe without the -no-launch argument
Wait for totsugeki.exe to run
Totsugeki errors out with the below message in step 3.1
3.1 Could not patch GGST. Steam/GGST may be running as Administrator. Try re-running Totsugeki as Administrator
repeat steps 1-2. at step 1 run totsugeki.exe as administrator.  The message from step 3.1 will still show

The error occurs every time I try to run totsugeki.exe

Additionally, running the program from the command line gives the below error message.

That's the first time I've seen that error. Is your game modded, or are you running an old version of Strive?
Try having Steam Re-Verify the game.

I don't have any mods running. I'll try to Re-Verify and see if that fixes the issue.

verifying the game solved the issue. Thanks for that suggestion. closing this out.


Is there a way to install openssl 1.1.1 or later on centOS 6?

Using centOS 6 (i know..eol, but I can't switch or upgrade quite yet.).
If relevant, please remember to tell us in what OpenSSL version you
found the issue.
Trying to install OpenSSL 1.1.1s by compiling from source
Downloaded the openssl source code from openss.org (openssl-1.1.1s.tar.gz) to /usr/src/openssl-1.1.1s.tar.gz
Then I unzipped it to to /usr/src/openssl-1.1.1s
Then I cd'ed into /usr/src/openssl-1.1.1s
issued the following commands
./config
make
make test
make install

After that it appears that it it installed the new open SSL binary in /usr/local/bin (so /usr/local/bin/openssl is the location), and that it installed shared objects? in /usr/local/lib64 (libssl.so.1.1, libcrypto.so.1.1, libcrypto.a, libssl.a). When I move the old openssl (v 1.0.1e-fips) for safekeeping and copy /usr/local/bin/openssl and then do a ./openssl version I get:
./openssl: error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory
So, how can I get this to work? Any help is appreciated.
Thank you!

Do NOT replace the system openssl library, you will certainly break your system. The system applications built against the 1.0.1e version will not run with 1.1.1.
However, you can install the new version of openssl in /usr/local as you did. You might need to run ldconfig or configure the /usr/local/lib64 in /etc/ld.so.conf if the system cannot find the libcrypto.so.1.1 and libssl.so.1.1 placed there.

You just put a line with /usr/local/lib64 in /etc/ld.so.conf and run ldconfig as root.

So this will not replace anything, but include that path, right?Martin Lerch
702.321.0908 (mobile)
Sent from my iPhone (mobile)

The information contained in this communication is potentially confidential, and intended only for the use of the addressee. If you received this communication in error, please notify us by return e-mail and delete this communication and all copies, including all attachments.
*************************On Nov 28, 2022, at 10:40 AM, Tomáš Mráz @.> wrote:
You just put a line with /usr/local/lib64 in /etc/ld.so.conf and run ldconfig as root.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

So this will not replace anything, but include that path, right?Martin Lerch

Yes

Tomas, you rock. Thank you! That worked!
Martin

One more question. How can I get SSH to use the new OpenSSL?
SSH -v output:
OpenSSH_5.3p1, OpenSSL 1.0.1e-fips 11 Feb 2013
openssl version output:
OpenSSL 1.1.1s  1 Nov 2022
Is it even possible?
Thanks.

You would have to build the openssh yourself to link it against the new openssl build. I personally would not recommend doing that unless you know what you're doing.

You just put a line with /usr/local/lib64 in /etc/ld.so.conf and run ldconfig as root.

help! It's not work for me. It also 'openssl: error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory'
environment: centos7 & python 3.8
This is my /etc/ld.so.conf:
include ld.so.conf.d/*.conf
/usr/local/openssl/lib
/usr/local/lib64/

Closing since this is marked as resolved.


ERC721 and ERC1155 support

Add support for ERC721 and ERC1155.
Breaking change: change balanceOf to explicit etherBalanceOf and erc20BalanceOf
This implementation follows the same design pattern of the support of ether and ERC20.
Test has 100% coverage now.
To run tests, there is an issue with vitest not supporting import assertion.
So the best I could do for now was to comment out the assert { type: "json" } from packages/wallet/wagmi.config.ts so pnpm run test works.

Still missing batch transfer of ERC1155 and batch withdraw of ERC1155.
Will work on that

Batch operations of ERC1155 implemented.

Problem of running test fixed

I prefer balanceOfEther.
Not a big deal

I prefer balanceOfEther.

I agree it's a little strange, but the context is:
The name of the method was a reflection of the name of the ERC20 method, balanceOf(account)
So it's of account, not of erc20
To be fair ERC71 also has a balanceOf(owner) which we don't have.


Schedule is not marked as a mandatory field in a CronJob create page

On master-head - commit id: 33f755f18

Workloads --> Cron Job --> create
Schedule is not marked as a mandatory field in a CronJob create page

Expected Result:
Cron Job should be marked as a mandatory field

Verified on 2.5-head - commit id: eb990af66 and ui-offline-preferred - false

Schedule is marked as a mandatory field for Cron Job

If given empty, and user tries to create a deployment --> Error is seen


featureAdd switch enable_cgroup_cpu_soft_limit

Proposed changes
1 support cpu soft limit based on cgroup.
2 add switch for cgroup cpu soft limit.

run buildall


View Monitoring Qualifications Data

Definition of Ready

[x] Does this meet the INVEST criteria?
[x] Does this have a clearly defined user?
[x] Does this have an estimate?
[x] Does this have acceptance criteria?
[x] Does this have sufficient context for the specific functionality being developed (design, business rules, etc.)
[x] Does this have a dev link been provided in the design?
[x] Is this traceable to a feature, epic, or PI?

User Story
As an ECMPS user, I want to view production Monitoring Qualifications Data so that I can look at real-time data.
Acceptance Criteria
Given a user selects Qualifications from the Sections dropdown
When Monitoring Qualifications Data is displayed
Then the data is displayed in a single table (see list below for columns and order)
Qualification Type Code
Start Date
End Date
Given a user is viewing Monitoring Qualifications Data
When the data is displayed in a table
Then the default sort order is alphanumeric descending by the contents in the 1st column
And the user will have the option to sort the columns in ascending or descending alphanumeric order

[x] The fields and their order specified

Pagination?

[ ] Yes
[x] No

Filter by keyword?

[ ] Yes
[x] No

Columns are sortable?

[x] Yes
[ ] No

Nested rows, expandable?

[ ] Yes
[x] No

Reporting Instructions (Page 125): https://ecmps.camdsupport.com/documents/ECMPS Monitoring Plan Reporting Instructions 2021 Q2.pdf
Testing
Test Case: TC442
Tester: @mosesdeeCVP
Definition of Done

[x] Have all Acceptance Criteria been agreed to and validated by the scrum team?
[x] Has the code been unit tested and peer reviewed?
[x] Have the functional tests been executed?
[x] Have all defects been reviewed and dispositioned, resolved, or deferred?
[x] Has the user story been accepted by the Product Owner?
[x] Is the user story ready to be deployed to the test/staging environments?

Test Passed


Refs #29628, Refs #33178 -- Made createsuperuser validate password against required fields passed in options.

@hramezani Thanks for checking :+1:


1.13 Clients get kicked for Spam (Need to solve ASAP)

What is the output link of /viaversion dump?
https://www.spigotmc.org/resources/viaversion.19254/ (updated 1.13)
Are you using any additional software like BungeeCord? If so, what software and version? (Please list your plugins as well)
Spigot 1.12.2
How does this error happen? login? Using an item?
Just kick players for using a command 2 times or sometimes even once, if they write in chat same thing happens.
Is there an error in the console? Use pastebin.com. Is there a kick message?
[05:29:56 INFO]: Niko302 issued server command: /deop Niko302

[05:29:56 INFO]: Niko302 lost connection: Kicked for spamming

[05:29:57 WARN]: handleDisconnection() called twice

Download latest build from ci.viaversion.com and use config option.


user12986714: Watch auto-machine.csa-challenge.com

user12986714 requests the watch of the watch_keyword auto-machine\.csa-challenge\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

auto-machine\.csa-challenge\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Daniil in Charcoal HQ


SendAsync Method doesn't exit, Nuget package outdated.

Looks like nuget packages are outdated. Documentation doesn't reflect actual version of nuget package via visual studio package manager.

NuGet package has been updated, version 2.7.1 has been pushed and should be avaiable soon.


Toolbar coloring

How can I disable the automatic toolbar coloring that occurred since the last couple of versions?
I don't like to have a pink, green or white toolbar, especially not when using the DarkReader extension...

Turning on dark theme. Turns your toolbar into black-grey. The toolbar color isn't affected while using dark theme.

Thanks for the mti tip, @karl-pae
I'm using dark theme all the time in Kiwi and also on my phone, but I'm still getting a colored toolbar - but this didn't happen a few versions ago.
Well, I'll try the mti extension...

Looks like a bug yes, working on a fix today

Thank you very much for spotting the issue!
This was clearly not intended, and is now resolved in the upcoming build.

Wow, thanks a lot for looking after!


Make the iterator method public

The iterator method in RedissonSet is public. It would be useful to make the RedissonMap iterator public, too, enabling iteration over hashes with millions of keys without memory issues.

Thank you! :sparkles:


VPN connects, but not data routes through VPN

The VPN does connect, so that that much works, but a simple trace route shows the data does not transport through the VPN.  Since your container does not include ping, or trace route, I had to use another container that I linked to the vpn container to POC test.  the other VPN I have works fine, but this one does not (same scenario for testing).

I found a solution.

Hey, thanks for letting me know, may I ask how you fixed the issue? Is there something I should fix on my side?

It was how I linked to your new vpn.  I made a mistake.  Your vpn works fine.


[WIP] DQM refactoring for Q/A and design discussion.

@arcondello  your input will be helpful here :) thanks.

@arcondello  your input will be helpful here :) thanks.

Codecov Report

Merging #776 (34769c1) into main (f4d2744) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #776   +/-   ##
=======================================
  Coverage   91.81%   91.81%
=======================================
  Files          63       63
  Lines        4667     4667
=======================================
  Hits         4285     4285
  Misses        382      382

Continue to review full report at Codecov.

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

Codecov Report

Merging #776 (34769c1) into main (f4d2744) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #776   +/-   ##
=======================================
  Coverage   91.81%   91.81%
=======================================
  Files          63       63
  Lines        4667     4667
=======================================
  Hits         4285     4285
  Misses        382      382

Continue to review full report at Codecov.

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


Fatal Exception: java.lang.IllegalArgumentException: millis < 0: -432345564227567616

Getting this issue on Google pixel and note 8 sometimes.
The log:
Fatal Exception: java.lang.IllegalArgumentException: millis < 0: -432345564227567616
at java.lang.Thread.sleep(Thread.java:346)
at java.lang.Thread.sleep(Thread.java:314)
at com.viro.core.internal.keys.KeyValidator$1.run(SourceFile:87)
at java.lang.Thread.run(Thread.java:764)

Hi @EricSKCheng, thanks for this bug report. We've resolved the issue and it will be available in the next release.

This issue has been fixed in the latest update, ViroCore 1.5. Release notes and upgrade instructions here -> https://virocore.viromedia.com/docs/releases
Let us know if you are still having issues after upgrading.


Introduce benchmarking with JMH

We need to make sure that we are faster than our competition at reading and writing files.
Introducing benchmarks by means of JMH is easy: https://github.com/ktoso/sbt-jmh

Done


TF2: Out of Memory using model.fit with class_weight parameter

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):

Yes

OS Platform and Distribution (e.g., Linux Ubuntu 16.04):

Container derived from nvidia/cuda:10.0-cudnn7-runtime-ubuntu18.04 running on Ubuntu 18.04 via Kubernetes 1.13

TensorFlow installed from (source or binary):

pip3 install tensorflow-gpu==2.0.0-beta1

TensorFlow version (use command below):

v1.12.1-6250-g37eafe0e74 2.0.0-dev20190715

Python version:

Python 3.6.8

CUDA/cuDNN version:

NVIDIA-SMI 410.78       Driver Version: 410.78       CUDA Version: 10.0

        libcudnn.so.7 -> libcudnn.so.7.6.0
libcudnn is installed

GPU model and memory:

name, pci.bus_id, vbios_version
Tesla V100-SXM2-32GB, 00000000:1B:00.0, <IP_ADDRESS>.03

Describe the current behavior
Doing a training with tf.keras results in out of memory after some time when including the class_weight parameter. Also there is a long delay between the start of each epoch. If I omit the class_weight parameter, training proceeds normally with constant memory.
Describe the expected behavior
Training proceed normally when the class_weight parameter is included without running out of memory.
Code to reproduce the issue
import tensorflow as tf

################ Data
def _parse_fn2(fn, label):
    img = tf.random.uniform([224, 224, 3])
    return img, label

train_data2 = tf.data.Dataset.from_tensor_slices(
  (tf.random.uniform([100]), tf.random.uniform([100], maxval=9, dtype=tf.dtypes.int32))
)

val_data2 = tf.data.Dataset.from_tensor_slices(
  (tf.random.uniform([100]), tf.random.uniform([100], maxval=9, dtype=tf.dtypes.int32))
)
train_data2 = (train_data2.map(_parse_fn2)).batch(32)
val_data2 = (val_data2.map(_parse_fn2)).batch(32)

############### Model
IMG_SHAPE = (224, 224, 3)

base_model = tf.keras.applications.ResNet50(input_shape=IMG_SHAPE,include_top=False, weights=None)
base_model.trainable = True
maxpool_layer = tf.keras.layers.GlobalMaxPooling2D()
prediction_layer = tf.keras.layers.Dense(9, activation='softmax')

model = tf.keras.Sequential([
    base_model,
    maxpool_layer,
    tf.keras.layers.Dropout(0.4),
    prediction_layer
])

model.compile(optimizer=tf.keras.optimizers.Adam(lr=0.01), loss='categorical_crossentropy', metrics=['accuracy'])

model.summary()
history = model.fit(train_data2.repeat(),
                epochs=100,
                steps_per_epoch = 50,
                validation_data=val_data2.repeat(),
                validation_steps=10,
                class_weight={0:1,1:1,2:1,3:1,4:1,5:1,6:1,7:1,8:1,9:1},
                callbacks = [])

Other info / logs
Memory Usage at Each Epoch:
              total        used        free      shared  buff/cache   available
E1:           502G         11G        461G        140M         30G        487G
E2:           502G         16G        456G        140M         30G        483G
E3:           502G         22G        449G        140M         30G        476G
E4:           502G         30G        441G        141M         30G        468G
E5:           502G         40G        431G        141M         30G        458G
E6:           502G         52G        419G        141M         30G        446G

vmstat output:
vmstat_output.txt

@814HiManny I was able to reproduce the issue with tf-nightly-gpu-2.0-preview==2.0.0.dev20190718. However, when I remove class_weights from the model.fit, the model runs without any issue. Thanks!

This looks like it's the same as #31253?

Yep, looks like a duplicate, I'll close this one to unify threads


Telenor MM new range

Telenor Myanmar introduced a new number series in market starting with
+95978.

Thanks for the report! Added to our internal bug triage queue. There are currently a lot of updates (also from ITU), so it might take a bit longer.

Was a bit fast there...
Do you have any evidence (government or from the telco) for this change?

This will be part of the next release

This change is in libphonenumber 7.0.6 which we released a few weeks ago.


Nil Assertion Compiler Bug

I came across this issue with the compiler while starting a project that consists of a "shell" made with crystal. It is mostly just an experiment to mess around with crystal, so code optimization was not in mind. I am using Crystal v1.0.0, and am running Garuda Linux (based on Arch). Here is the code (I am sorry for the size, it was necessary because when shrinking it down to something that focused only on the error, I was not able to get the compiler to tell me there was a bug):
require "colorize"

Permission = begin
  io = IO::Memory.new
  Process.run("echo $UID", shell: true, output: io)
  if io.to_s.to_i == 0
    "#"
    Root = true # I believe the issue is caused from this
  else
    "$"
    Root = false # and this
  end
end

Root = begin
  if Permission == '#'
    true
  else
    false
  end
end

Err = "[".colorize(:blue).to_s + "!".colorize(:red).to_s + "]".colorize(:blue).to_s

SynErr = Err + " Not recognized as a command, file, or program".colorize(:blue).to_s

Signal::INT.trap do
  puts "\b\b  \n#{Err} Type \"exit\" or \"quit\" to leave"
  prompt
end

def parse(s)
  if s.index(' ')
    parseArgs s.split(' ')
  else
    parseSingle s
  end
end

def parseArgs(args)
  case args[0]
  when "ch"
    begin
      Dir.cd(args[1])
    rescue File::NotFoundError
      puts Err + " No such directory"
    end
  else puts SynErr
  end
end

def parseSingle(arg)
  case arg
  when "exit", "quit" then exit
  when "me", "who", "whoami", "?"
    if Root
      puts "root"
    else
      puts "normal user (this is not fully implemented yet)"
    end
  when "back"  then Dir.cd("..")
  when "clear" then print "\33c\e[3J"
  else
    puts SynErr
  end
end

def prompt
  while 1
    dir = Dir.current.split('/').last.colorize(:magenta).to_s
    dir = "/".colorize(:magenta).to_s if dir == ""
    print "╭─[ ".colorize.magenta.bold.to_s + dir + " ]".colorize.magenta.bold.to_s + "\n╰─#{Permission}> "
    ans = gets
    parse ans.chomp.strip if ans && ans.chomp.strip != ""
  end
end

prompt

The issue goes away when I comment out 'Root = something' in the 'Permission' block, however, when I tested it where i only had those two blocks of code, the issue did not appear, hence the reason I did not want to shrink it down any further. Here is the shrunken down code that did not reproduce the issue:
Var1 = begin
  if rand(2) == 0
    "0"
    Bool1 = true
  else
    "1"
    Bool1 = false
  end
end

Bool1 = begin
  if rand(2..4) == 2
    true
  else
    false
  end
end

And here is the bug report that the compiler gave me:
$ crystal build myst.cr
Nil assertion failed (NilAssertionError)
  from ???
  from ???
  from ???
  from ???
  from ???
  from ???
  from ???
  from ???
  from ???
  from ???
  from ???
  from ???
  from ???
  from ???
  from ???
  from ???
  from ???
  from ???
  from __crystal_main
  from main
  from __libc_start_main
  from _start
  from ???
Error: you've found a bug in the Crystal compiler. Please open an issue, including source code that will allow us to reproduce the bug: https://github.com/crystal-lang/crystal/issues

I wish I could give more detail on exactly what is going wrong, but I am still pretty new to the Crystal language.

Duplicate of #2874

I did not see that issue when I searched. Sorry about that


fix: default CliCommand generic to any

CliCommand with context can't be used because the Context is not compatible with {}

:tada: This PR is included in version 2.4.3 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


"Bad state: No element" error caused by palette_generator's empty response

Steps to Reproduce

I created a Stateful Widget.
I inserted the following code which is from palette_generator's example into the widget in order to get the color palette of an image:

Future<void> _updatePaletteGenerator(Rect newRegion) async {
    paletteGenerator = await PaletteGenerator.fromImageProvider(
      widget.image,
      size: widget.imageSize,
      region: newRegion,
      maximumColorCount: 20,
    );
    setState(() {});
}

I called the code inside initState().
I used Iterable paletteGenerator.colors.first to change the background color of a widget.
I tested it on iOS Simulator and it smoothly worked.
It hardly worked on Android. I had to do hot restart to run it again. It never worked in the second time without hot restart and I got an error when I navigated to different screens and came back to the same screen.

What I see is that it works only in the beginning on Android Simulator whilst iOS Simulator is fine. However, PaletteGenerator.fromImageProvider() returns null for the raw image when I try to call it after rerender the widget. So, the rest of the process can't work properly due to the null parameter. As a result, I always receive an empty list for the second try. Something like this: PaletteGenerator#b6f11(paletteColors: [], targets: null)
Logs
I/flutter (13109): ══╡ EXCEPTION CAUGHT BY WIDGETS LIBRARY ╞═══════════════════════════════════════════════════════════
I/flutter (13109): The following StateError was thrown building HomeScreen(dirty, state: _HomeScreenState#e3fe0):
I/flutter (13109): Bad state: No element
I/flutter (13109):
I/flutter (13109): When the exception was thrown, this was the stack:
I/flutter (13109): #0      Iterable.first (dart:core/iterable.dart:518:7)
I/flutter (13109): #1      _HomeScreenState.build (package:test/screens/home_screen.dart:76:41)
I/flutter (13109): #2      StatefulElement.build (package:flutter/src/widgets/framework.dart:3766:27)
I/flutter (13109): #3      ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:3678:15)
I/flutter (13109): #4      Element.rebuild (package:flutter/src/widgets/framework.dart:3531:5)
I/flutter (13109): #5      BuildOwner.buildScope (package:flutter/src/widgets/framework.dart:2273:33)
I/flutter (13109): #6      _WidgetsFlutterBinding&BindingBase&GestureBinding&ServicesBinding&SchedulerBinding&PaintingBinding&SemanticsBinding&RendererBinding&WidgetsBinding.drawFrame (package:flutter/src/widgets/binding.dart:670:20)
I/flutter (13109): #7      _WidgetsFlutterBinding&BindingBase&GestureBinding&ServicesBinding&SchedulerBinding&PaintingBinding&SemanticsBinding&RendererBinding._handlePersistentFrameCallback (package:flutter/src/rendering/binding.dart:208:5)
I/flutter (13109): #8      _WidgetsFlutterBinding&BindingBase&GestureBinding&ServicesBinding&SchedulerBinding._invokeFrameCallback (package:flutter/src/scheduler/binding.dart:990:15)
I/flutter (13109): #9      _WidgetsFlutterBinding&BindingBase&GestureBinding&ServicesBinding&SchedulerBinding.handleDrawFrame (package:flutter/src/scheduler/binding.dart:930:9)
I/flutter (13109): #10     _WidgetsFlutterBinding&BindingBase&GestureBinding&ServicesBinding&SchedulerBinding._handleDrawFrame (package:flutter/src/scheduler/binding.dart:842:5)
I/flutter (13109): #11     _invoke (dart:ui/hooks.dart:139:13)
I/flutter (13109): #12     _drawFrame (dart:ui/hooks.dart:128:3)
I/flutter (13109): ════════════════════════════════════════════════════════════════════════════════════════════════════

[✓] Flutter (Channel dev, v0.9.6, on Mac OS X 10.14 18A391, locale en-US)
    • Flutter version 0.9.6 at /Users/test/Library/Android/flutter
    • Framework revision 13684e4f8e (9 days ago), 2018-10-02 14:15:17 -0400
    • Engine revision f6af1f20ba
    • Dart version 2.1.0-dev.6.0.flutter-8a919426f0

[✓] Android toolchain - develop for Android devices (Android SDK 28.0.1)
    • Android SDK at /Users/test/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-28, build-tools 28.0.1
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1024-b01)
    • All Android licenses accepted.

[✓] iOS toolchain - develop for iOS devices (Xcode 10.0)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 10.0, Build version 10A255
    • ios-deploy 1.9.2
    • CocoaPods version 1.5.3

[✓] Android Studio (version 3.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 27.1.1
    • Dart plugin version 173.4700
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1024-b01)

[✓] VS Code (version 1.28.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 2.19.0

[✓] Connected device (1 available)
    • Android SDK built for x86 • emulator-5554 • android-x86 • Android 8.1.0 (API 27) (emulator)

• No issues found!

@gspencergoog

Please add the output of flutter doctor -v.

I've added the output

Is this on the Android emulator, or on a real device?
If it's on the emulator, can you try adding --enable-software-rendering to your flutter run command? There are known bugs in the hardware rendering on the emulators that may be causing this problem.

I tested on both different emulators and a real device.
It is working on Android emulators after adding --enable-software-rendering to the command. As you said, the problem could be the emulator itself. However, it doesn't work on a real Android device either.

@gspencergoog
Useing this command flutter run --enable-software-rendering  issue resolved. But app stauck , slow performance & sometime lost connection.
Here is some log before lost connections.
I/Choreographer( 2299): Skipped 51 frames!  The application may be doing too much work on its main thread.
D/        ( 2299): HostConnection::get() New Host Connection established 0xee992eb0, tid 2314
Syncing files to device Google Nexus 5, 6 0 0, API 23, 1080x1920...
F/libc    ( 2299): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x3 in tid 2320 (le.tabbarbottom)
Lost connection to device.

@afnx, What kind of device are you using (make/model)?
It appears that this is exercising part of the graphics stack that isn't properly implemented in the emulators, but I'm wondering why it still fails on a device.

@hupptechnologies, was the "But app stuck , slow performance & sometime lost connection." comment for the emulator, or for a physical device? (your log snippet mentions "Nexus 5", so I'm not sure)

@gspencergoog, Samsung Galaxy S7 Edge - Android 8.0 Oreo.
I have a red error screen which says Bad State: No Element. It works anytime I clear the data of the app.

@gspencergoog, the palette generator works when I clear the data. It works for once and then the error appears for all next attempts.
For example, I launch the app and it works for once. After that, I navigate to another screen or close the app. Henceforth, the error will always appear. If I clear the data of the app, it will work again for once and the same process will happen again and again.

Same here. On the first run (Android - hot reload) works, but every subsequent run silently fails and returns empty palette.

@gspencergoog For simulator. Not tried in real device yet.

@

Closing this, as it appears to not be reproducible, at least in the ways in which I tried to reproduce it.  If you still have problems with this, and have more information about the context in which it is used, that may help.

I can reproduce it using simple:
  List<PieChartSectionData> _showingSections(final List<Vote> snapshot) {
    print('length ${snapshot.length}');
    return List.generate(
      0,
      (i) {
        return _pieChartFromVote(snapshot[i]);
      },
    );
  }

When snapshot.length is == 0 I get the following stacktrace:
Performing hot reload...                                               ⡿I/flutter (16258): length 0
⣟I/flutter (16258): ══╡ EXCEPTION CAUGHT BY WIDGETS LIBRARY ╞═══════════════════════════════════════════════════════════
⣯I/flutter (16258): The following StateError was thrown building StreamBuilder<List<Vote>>(dirty, state:
I/flutter (16258): _StreamBuilderBaseState<List<Vote>, AsyncSnapshot<List<XXXXX>>>#2532c):
I/flutter (16258): Bad state: No element
I/flutter (16258):
I/flutter (16258): The relevant error-causing widget was:
I/flutter (16258):   StreamBuilder<List<Vote>> file:///home/agilob/xxxx/xxxx/lib/pages/xxxxx.dart:39:22
I/flutter (16258):
I/flutter (16258): When the exception was thrown, this was the stack:
I/flutter (16258): #0      ListIterable.reduce (dart:_internal/iterable.dart:182:22)
I/flutter (16258): #1      new PieChartData (package:fl_chart/src/chart/pie_chart/pie_chart_data.dart:38:51)
I/flutter (16258): #2      _CreateTeamPageState._buildChartData (package:XXXXX/pages/create_team_page.dart:155:9)
I/flutter (16258): #3      _CreateTeamPageState.build.<anonymous closure> (package:XXXXX/pages/create_team_page.dart:44:26)
I/flutter (16258): #4      StreamBuilder.build (package:flutter/src/widgets/async.dart:425:74)
I/flutter (16258): #5      _StreamBuilderBaseState.build (package:flutter/src/widgets/async.dart:125:48)
I/flutter (16258): #6      StatefulElement.build (package:flutter/src/widgets/framework.dart:4334:27)
I/flutter (16258): #7      ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4223:15)
I/flutter (16258): #8      Element.rebuild (package:flutter/src/widgets/framework.dart:3947:5)
I/flutter (16258): #9      StatefulElement.update (package:flutter/src/widgets/framework.dart:4413:5)
I/flutter (16258): #10     Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
I/flutter (16258): #11     ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4243:16)
I/flutter (16258): #12     Element.rebuild (package:flutter/src/widgets/framework.dart:3947:5)
I/flutter (16258): #13     ProxyElement.update (package:flutter/src/widgets/framework.dart:4557:5)
I/flutter (16258): #14     Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
I/flutter (16258): #15     RenderObjectElement.updateChildren (package:flutter/src/widgets/framework.dart:5161:32)
I/flutter (16258): #16     MultiChildRenderObjectElement.update (package:flutter/src/widgets/framework.dart:5561:17)
I/flutter (16258): #17     Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
I/flutter (16258): #18     SingleChildRenderObjectElement.update (package:flutter/src/widgets/framework.dart:5452:14)
I/flutter (16258): #19     Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
I/flutter (16258): #20     ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4243:16)
I/flutter (16258): #21     Element.rebuild (package:flutter/src/widgets/framework.dart:3947:5)
I/flutter (16258): #22     StatelessElement.update (package:flutter/src/widgets/framework.dart:4298:5)
I/flutter (16258): #23     Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
I/flutter (16258): #24     ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4243:16)
I/flutter (16258): #25     Element.rebuild (package:flutter/src/widgets/framework.dart:3947:5)
I/flutter (16258): #26     StatelessElement.update (package:flutter/src/widgets/framework.dart:4298:5)
I/flutter (16258): #27     Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
I/flutter (16258): #28     ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4243:16)
I/flutter (16258): #29     Element.rebuild (package:flutter/src/widgets/framework.dart:3947:5)
I/flutter (16258): #30     ProxyElement.update (package:flutter/src/widgets/framework.dart:4557:5)
I/flutter (16258): #31     Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
I/flutter (16258): #32     ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4243:16)
I/flutter (16258): #33     Element.rebuild (package:flutter/src/widgets/framework.dart:3947:5)
I/flutter (16258): #34     ProxyElement.update (package:flutter/src/widgets/framework.dart:4557:5)
I/flutter (16258): #35     Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
I/flutter (16258): #36     RenderObjectElement.updateChildren (package:flutter/src/widgets/framework.dart:5161:32)
I/flutter (16258): #37     MultiChildRenderObjectElement.update (package:flutter/src/widgets/framework.dart:5561:17)
I/flutter (16258): #38     Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
I/flutter (16258): #39     ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4243:16)
I/flutter (16258): #40     Element.rebuild (package:flutter/src/widgets/framework.dart:3947:5)
I/flutter (16258): #41     StatefulElement.update (package:flutter/src/widgets/framework.dart:4413:5)
I/flutter (16258): #42     Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
I/flutter (16258): #43     ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4243:16)
I/flutter (16258): #44     Element.rebuild (package:flutter/src/widgets/framework.dart:3947:5)
I/flutter (16258): #45     ProxyElement.update (package:flutter/src/widgets/framework.dart:4557:5)
I/flutter (16258): #46     Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
I/flutter (16258): #47     ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4243:16)
I/flutter (16258): #48     Element.rebuild (package:flutter/src/widgets/framework.dart:3947:5)
I/flutter (16258): #49     StatefulElement.update (package:flutter/src/widgets/framework.dart:4413:5)
I/flutter (16258): #50     Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
I/flutter (16258): #51     SingleChildRenderObjectElement.update (package:flutter/src/widgets/framework.dart:5452:14)
I/flutter (16258): #52     Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
I/flutter (16258): #53     ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4243:16)
I/flutter (16258): #54     Element.rebuild (package:flutter/src/widgets/framework.dart:3947:5)
I/flutter (16258): #55     StatelessElement.update (package:flutter/src/widgets/framework.dart:4298:5)
I/flutter (16258): #56     Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
I/flutter (16258): #57     SingleChildRenderObjectElement.update (package:flutter/src/widgets/framework.dart:5452:14)
I/flutter (16258): #58     Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
I/flutter (16258): #59     ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4243:16)
I/flutter (16258): #60     Element.rebuild (package:flutter/src/widgets/framework.dart:3947:5)
I/flutter (16258): #61     StatefulElement.update (package:flutter/src/widgets/framework.dart:4413:5)
I/flutter (16258): #62     Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
I/flutter (16258): #63     ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4243:16)
I/flutter (16258): #64     Element.rebuild (package:flutter/src/widgets/framework.dart:3947:5)
I/flutter (16258): #65     StatefulElement.update (package:flutter/src/widgets/framework.dart:4413:5)
I/flutter (16258): #66     Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
I/flutter (16258): #67     ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4243:16)
I/flutter (16258): #68     Element.rebuild (package:flutter/src/widgets/framework.dart:3947:5)
I/flutter (16258): #69     ProxyElement.update (package:flutter/src/widgets/framework.dart:4557:5)
I/flutter (16258): #70     Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
I/flutter (16258): #71     ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4243:16)
I/flutter (16258): #72     Element.rebuild (package:flutter/src/widgets/framework.dart:3947:5)
I/flutter (16258): #73     ProxyElement.update (package:flutter/src/widgets/framework.dart:4557:5)
I/flutter (16258): #74     Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
I/flutter (16258): #75     ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4243:16)
I/flutter (16258): #76     Element.rebuild (package:flutter/src/widgets/framework.dart:3947:5)
I/flutter (16258): #77     StatefulElement.update (package:flutter/src/widgets/framework.dart:4413:5)
I/flutter (16258): #78     Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
I/flutter (16258): #79     ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4243:16)
I/flutter (16258): #80     Element.rebuild (package:flutter/src/widgets/framework.dart:3947:5)
I/flutter (16258): #81     StatefulElement.update (package:flutter/src/widgets/framework.dart:4413:5)
I/flutter (16258): #82     Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
I/flutter (16258): #83     ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4243:16)
I/flutter (16258): #84     Element.rebuild (package:flutter/src/widgets/framework.dart:3947:5)
I/flutter (16258): #85     StatefulElement.update (package:flutter/src/widgets/framework.dart:4413:5)
I/flutter (16258): #86     Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
I/flutter (16258): #87     ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4243:16)
I/flutter (16258): #88     Element.rebuild (package:flutter/src/widgets/framework.dart:3947:5)
I/flutter (16258): #89     StatelessElement.update (package:flutter/src/widgets/framework.dart:4298:5)
I/flutter (16258): #90     Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
I/flutter (16258): #91     ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4243:16)
I/flutter (16258): #92     Element.rebuild (package:flutter/src/widgets/framework.dart:3947:5)
I/flutter (16258): #93     StatelessElement.update (package:flutter/src/widgets/framework.dart:4298:5)
I/flutter (16258): #94     Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
I/flutter (16258): #95     ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4243:16)
I/flutter (16258): #96     Element.rebuild (package:flutter/src/widgets/framework.dart:3947:5)
I/flutter (16258): #97     ProxyElement.update (package:flutter/src/widgets/framework.dart:4557:5)
I/flutter (16258): #98     Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
I/flutter (16258): #99     ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4243:16)
I/flutter (16258): #100    Element.rebuild (package:flutter/src/widgets/framework.dart:3947:5)
I/flutter (16258): #101    ProxyElement.update (package:flutter/src/widgets/framework.dart:4557:5)
I/flutter (16258): #102    Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
I/flutter (16258): #103    RenderObjectElement.updateChildren (package:flutter/src/widgets/framework.dart:5161:32)
I/flutter (16258): #104    MultiChildRenderObjectElement.update (package:flutter/src/widgets/framework.dart:5561:17)
I/flutter (16258): #105    Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
I/flutter (16258): #106    ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4243:16)
I/flutter (16258): #107    Element.rebuild (package:flutter/src/widgets/framework.dart:3947:5)
I/flutter (16258): #108    StatefulElement.update (package:flutter/src/widgets/framework.dart:4413:5)
I/flutter (16258): #109    Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
I/flutter (16258): #110    ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4243:16)
I/flutter (16258): #111    Element.rebuild (package:flutter/src/widgets/framework.dart:3947:5)
I/flutter (16258): #112    ProxyElement.update (package:flutter/src/widgets/framework.dart:4557:5)
I/flutter (16258): #113    Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
I/flutter (16258): #114    ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4243:16)
I/flutter (16258): #115    Element.rebuild (package:flutter/src/widgets/framework.dart:3947:5)
I/flutter (16258): #116    StatefulElement.update (package:flutter/src/widgets/framework.dart:4413:5)
I/flutter (16258): #117    Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
I/flutter (16258): #118    SingleChildRenderObjectElement.update (package:flutter/src/widgets/framework.dart:5452:14)
I/flutter (16258): #119    Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
I/flutter (16258): #120    ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4243:16)
I/flutter (16258): #121    Element.rebuild (package:flutter/src/widgets/framework.dart:3947:5)
I/flutter (16258): #122    StatelessElement.update (package:flutter/src/widgets/framework.dart:4298:5)
I/flutter (16258): #123    Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
I/flutter (16258): #124    SingleChildRenderObjectElement.update (package:flutter/src/widgets/framework.dart:5452:14)
I/flutter (16258): #125    Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
I/flutter (16258): #126    ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4243:16)
I/flutter (16258): #127    Element.rebuild (package:flutter/src/widgets/framework.dart:3947:5)
I/flutter (16258): #128    StatefulElement.update (package:flutter/src/widgets/framework.dart:4413:5)
I/flutter (16258): #129    Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
I/flutter (16258): #130    ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4243:16)
I/flutter (16258): #131    Element.rebuild (package:flutter/src/widgets/framework.dart:3947:5)
I/flutter (16258): #132    StatefulElement.update (package:flutter/src/widgets/framework.dart:4413:5)
I/flutter (16258): #133    Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
I/flutter (16258): #134    ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4243:16)
I/flutter (16258): #135    Element.rebuild (package:flutter/src/widgets/framework.dart:3947:5)
I/flutter (16258): #136    ProxyElement.update (package:flutter/src/widgets/framework.dart:4557:5)
I/flutter (16258): #137    Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
I/flutter (16258): #138    ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4243:16)
I/flutter (16258): #139    Element.rebuild (package:flutter/src/widgets/framework.dart:3947:5)
I/flutter (16258): #140    ProxyElement.update (package:flutter/src/widgets/framework.dart:4557:5)
I/flutter (16258): #141    Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
I/flutter (16258): #142    ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4243:16)
I/flutter (16258): #143    Element.rebuild (package:flutter/src/widgets/framework.dart:3947:5)
I/flutter (16258): #144    StatefulElement.update (package:flutter/src/widgets/framework.dart:4413:5)
I/flutter (16258): #145    Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
I/flutter (16258): #146    ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4243:16)
I/flutter (16258): #147    Element.rebuild (package:flutter/src/widgets/framework.dart:3947:5)
I/flutter (16258): #148    StatefulElement.update (package:flutter/src/widgets/framework.dart:4413:5)
I/flutter (16258): #149    Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
I/flutter (16258): #150    SingleChildRenderObjectElement.update (package:flutter/src/widgets/framework.dart:5452:14)
I/flutter (16258): #151    Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
I/flutter (16258): #152    ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4243:16)
I/flutter (16258): #153    Element.rebuild (package:flutter/src/widgets/framework.dart:3947:5)
I/flutter (16258): #154    StatelessElement.update (package:flutter/src/widgets/framework.dart:4298:5)
I/flutter (16258): #155    Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
I/flutter (16258): #156    SingleChildRenderObjectElement.update (package:flutter/src/widgets/framework.dart:5452:14)
I/flutter (16258): #157    Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
I/flutter (16258): #158    SingleChildRenderObjectElement.update (package:flutter/src/widgets/framework.dart:5452:14)
I/flutter (16258): #159    Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
I/flutter (16258): #160    ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4243:16)
I/flutter (16258): #161    Element.rebuild (package:flutter/src/widgets/framework.dart:3947:5)
I/flutter (16258): #162    StatefulElement.update (package:flutter/src/widgets/framework.dart:4413:5)
I/flutter (16258): #163    Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
I/flutter (16258): #164    SingleChildRenderObjectElement.update (package:flutter/src/widgets/framework.dart:5452:14)
I/flutter (16258): #165    Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
I/flutter (16258): #166    SingleChildRenderObjectElement.update (package:flutter/src/widgets/framework.dart:5452:14)
I/flutter (16258): #167    Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
I/flutter (16258): #168    ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4243:16)
I/flutter (16258): #169    Element.rebuild (package:flutter/src/widgets/framework.dart:3947:5)
I/flutter (16258): #170    StatefulElement.update (package:flutter/src/widgets/framework.dart:4413:5)
I/flutter (16258): #171    Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
I/flutter (16258): #172    ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4243:16)
I/flutter (16258): #173    Element.rebuild (package:flutter/src/widgets/framework.dart:3947:5)
I/flutter (16258): #174    StatelessElement.update (package:flutter/src/widgets/framework.dart:4298:5)
I/flutter (16258): #175    Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
I/flutter (16258): #176    ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4243:16)
I/flutter (16258): #177    Element.rebuild (package:flutter/src/widgets/framework.dart:3947:5)
I/flutter (16258): #178    StatefulElement.update (package:flutter/src/widgets/framework.dart:4413:5)
I/flutter (16258): #179    Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
I/flutter (16258): #180    SingleChildRenderObjectElement.update (package:flutter/src/widgets/framework.dart:5452:14)
I/flutter (16258): #181    Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
I/flutter (16258): #182    ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4243:16)
I/flutter (16258): #183    Element.rebuild (package:flutter/src/widgets/framework.dart:3947:5)
I/flutter (16258): #184    ProxyElement.update (package:flutter/src/widgets/framework.dart:4557:5)
I/flutter (16258): #185    _InheritedNotifierElement.update (package:flutter/src/widgets/inherited_notifier.dart:94:11)
I/flutter (16258): #186    Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
I/flutter (16258): #187    SingleChildRenderObjectElement.update (package:flutter/src/widgets/framework.dart:5452:14)
I/flutter (16258): #188    Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
I/flutter (16258): #189    ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4243:16)
I/flutter (16258): #190    Element.rebuild (package:flutter/src/widgets/framework.dart:3947:5)
I/flutter (16258): #191    StatefulElement.update (package:flutter/src/widgets/framework.dart:4413:5)
I/flutter (16258): #192    Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
I/flutter (16258): #193    ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4243:16)
I/flutter (16258): #194    Element.rebuild (package:flutter/src/widgets/framework.dart:3947:5)
I/flutter (16258): #195    StatelessElement.update (package:flutter/src/widgets/framework.dart:4298:5)
I/flutter (16258): #196    Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
I/flutter (16258): #197    SingleChildRenderObjectElement.update (package:flutter/src/widgets/framework.dart:5452:14)
I/flutter (16258): #198    Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
I/flutter (16258): #199    ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4243:16)
I/flutter (16258): #200    Element.rebuild (package:flutter/src/widgets/framework.dart:3947:5)
I/flutter (16258): #201    ProxyElement.update (package:flutter/src/widgets/framework.dart:4557:5)
I/flutter (16258): #202    Element.updateChild (package:flutter/src/widgets/framework.dart:2977:15)
I/flutter (16258): #203    ComponentElement.performRebuild (package:flutter/src/widgets/framework.dart:4243:16)
I/flutter (16258): #204    Element.rebuild (package:flutter/src/widgets/framework.dart:3947:5)
I/flutter (16258): #205    BuildOwner.buildScope (package:flutter/src/widgets/framework.dart:2432:33)
I/flutter (16258): #206    WidgetsBinding.drawFrame (package:flutter/src/widgets/binding.dart:773:20)
I/flutter (16258): #207    RendererBinding._handlePersistentFrameCallback (package:flutter/src/rendering/binding.dart:283:5)
I/flutter (16258): #208    SchedulerBinding._invokeFrameCallback (package:flutter/src/scheduler/binding.dart:1102:15)
I/flutter (16258): #209    SchedulerBinding.handleDrawFrame (package:flutter/src/scheduler/binding.dart:1041:9)
I/flutter (16258): #210    SchedulerBinding.scheduleWarmUpFrame.<anonymous closure> (package:flutter/src/scheduler/binding.dart:850:7)
I/flutter (16258): #212    _Timer._runTimers (dart:isolate-patch/timer_impl.dart:384:19)
I/flutter (16258): #213    _Timer._handleMessage (dart:isolate-patch/timer_impl.dart:418:5)
I/flutter (16258): #214    _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:174:12)
I/flutter (16258): (elided one frame from package dart:async-patch)
I/flutter (16258):
I/flutter (16258): ════════════════════════════════════════════════════════════════════════════════════════════════════

Flutter info:
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, v1.12.13+hotfix.8, on Linux, locale en_GB.UTF-8)

I can reproduce it on 3 devices (not emulators):
3 connected devices:
A   • XXXXX           • android-arm   • Android 4.4.2 (API 19)
B • YYYYY         • android-arm   • Android 7.1.1 (API 25)
C     • <IP_ADDRESS>:5555 • android-arm64 • Android 9 (API 28)

It always happens when list if empty, adding 1 element "fixes" the issue.

Channel master also affected [✓] Flutter (Channel master, v1.15.4-pre.82, on Linux, locale en_GB.UTF-8)

If this is still an issue, I had something similar: .firstWhere( (z) => z.id == value.issuer.id, orElse: () => null)
was missing orElse in my code.

If you are using a physical android device, then unplugging and plugging again the usb into cellphone fixed it for me.


Refactor port detection code

Current port detection code tries to be compact and simple. As a result - logic partially goes to shell, and becomes messy.

It's not evident when shell script failed (some commands not support use params in certain env).
Fixing complex command can break it for another env (shells can be different).

Ideas:

If anyone have time, it would be nice to split this logic into separate part.
If anybody wish, it would be nice to configure more test envs to make sure that port detection works.

update

2.0 should support port reporting. So, just drop that code when phantomjs 2.0 is available on npm.
Problems with bad -p key are related to docker busybox images. Can be solved by install full version of netstat/ss

A better option would be to get phantomjs to report the actual port used
when using port 0. That way we could just ask for it directly. I had hoped
they would fix this in phantomjs 2.0, but I guess not?
On Sat, Jan 16, 2016 at 8:28 AM, Vitaly Puzrin<EMAIL_ADDRESS>wrote:

Current port detection code tries to be compact and simple. As a result -
logic partially goes to shell, and becomes messy.

It's not evident when shell script failed (some commands not support
use params in certain env).
Fixing complex command can break it for another env (shells can be
different).

Ideas:

If anyone have time, it would be nice to split this logic into
separate part.
If anybody wish, it would be nice to configure more test envs to
make sure that port detection works.

—
Reply to this email directly or view it on GitHub
https://github.com/baudehlo/node-phantom-simple/issues/113.

Ah, you are right. Alternative is to completely drop this code, when 2.0 available. Forgot about it :)
Current situation is, that phantom 2.0 can not be installed on linux via npm. This problem is known, old, and nobody can say when it will be solved. So, i did not tried to investigate what's up with port in 2.0.

Just for records. Reports about bad -p key are related to docker busybox images. http://serverfault.com/questions/219984/busybox-netstat-no-p. Can be solved by install of full netstat/ss

https://github.com/Medium/phantomjs/releases/tag/v2.1.1
Holy shit! PhantomJS 2.1 finally available on npm for linux!

Update
2.1.2 works somehow, but:

Need to polish tests

one still broken here (onError)
one still broken in navit (after patches)

New version sends cache headers, and that can fuckup everything, because you can get 304 response (without body/headers) instead of expected 200 response.

solution can be to force cache reset on every request https://github.com/nodeca/navit/commit/1896bdee2e0c8bedfa32cafde34d4fbaea9f88b8.

Will continue tomorrow.

Nothing changed about port in 2.1. Created issue https://github.com/ariya/phantomjs/issues/13947

Good news - issue assigned for 2.2 release

Should this be targeting phantomjs-prebuilt?