Record start time of last started tasks

The files used to compare to lastRun time might get updated during the execution of a task.
Instead of recording the stop time, Undertaker should record the start time, before something like gulp.src start to read the content of a file.

Looking at the integration test that fails on io.js:

my implementation wouldn't work with that use case
I don't know why they are not failing on nodejs too

@dinoboff looks like you got it fixed, what was the problem?

First I had to change the test. The original was testing that the file built by the task was older than the last task run time. With the pull request, the last task run time now is the start of the task, I didn't know why it was only failing on iojs.
I changed the test to check that if a source file changes, using the since option with lastRun, the unchanged source file would get filtered out. However the test needs to wait before modify a file to test it.
I think files' mtime and node time (or the time the extension before method records) are not consistent. On my laptop (os x 10.9, node 0.10) mtime seems to get round dow to the second:
task setup started at 2015-03-17T12:10:04.347Z
task build started at 2015-03-17T12:10:04.355Z
task userWait started at 2015-03-17T12:10:04.362Z
task userEdit started at 2015-03-17T12:10:05.484Z
task countEditedFiles started at 2015-03-17T12:10:05.486Z
counting /Users/dinoboff/dev/undertaker/test/fixtures/tmp/testMore.js
mtime 2015-03-17T12:10:05.000Z

Note that the file get modified after 12:10:05.484Z, but its mtime is 12:10:05.000Z. Might be the same for travis node 0.10
On travis nodejs 0.12, it's not as bad, but it's still inconsistent:
task setup started at 2015-03-17T12:14:23.087Z
task build started at 2015-03-17T12:14:23.101Z
task userWait started at 2015-03-17T12:14:23.108Z
task userEdit started at 2015-03-17T12:14:24.209Z
task countEditedFiles started at 2015-03-17T12:14:24.211Z
counting /home/travis/build/phated/undertaker/test/fixtures/tmp/testMore.js
mtime 2015-03-17T12:14:24.208Z

userEdit Task starts at 12:14:24.209Z but the file mtime is 12:14:24.208Z.
On Travis iojs the task start time and the file mtime are the same.

@phated
Reading around:

HFS time resolution is 1s.
node fs stat time resolution is 1s in Node 0.10
node fs stat time resolution is 1ms in Node 0.11+

I don't know if the the issue with node 0.12 (mtime < start task in that travis run) is due to a bug with node 0.12, with travis container or in the extension before method.
Should Undertaker round down the last run time to 1s for consistency?

@dinoboff this PR is awesome.  thanks for all the work and research put into this


[Q] Any plans to add support for pipenv's Pipfile?

Hi!
Do you have any plans to add support for pipenv's Pipfile?
Some projects store metadata only in those files.
Example: https://github.com/nats-io/nats.py

another example:
https://github.com/mapado/haversine
Makes sense, will take a look.

Spec:
https://pipenv.pypa.io/en/latest/pipfile.html


Remove pound keywords token kinds

These are no longer being used, so we can clean up the list of token kinds a little further.

@swift-ci Please test


AsyncWrite wrappers that consume self can fail because of WouldBlock

See https://github.com/gyscos/zstd-rs/issues/22 as an example. There's a method called finish() which consumes self but could potentially fail because of WouldBlock.
This can lead to writers being stuck in an unrecoverable state even though all they needed to do was retry on next poll().
Is there any way to handle this short of adding a non-consuming version of any methods that could consume self yet cause writes?

I guess shutdown() is meant to solve this sort of use case? But it would mean that we'd have to convince any third-party crates to (optionally?) depend on tokio-io and add shutdown methods of their own.

Ah yes the intention here is for AsyncWrite::shutdown to implement this logic. Presumably there's an impl AsyncWrite somewhere though for this type, right? Where's that located?

I implemented it locally in my crate. Here's what the source code looks like: https://gist.github.com/sid0/2afeda9cb29e7250acce9badcc9727eb

If you add:
try_nb!(self.flush())

to the shutdown function, would that work?

No, because finish() does a write at the end that cannot be done any other way.

For reference: https://docs.rs/zstd/0.4.6/src/zstd/stream/encoder.rs.html#188
The ZSTD_endStream writes out an end-of-stream marker.

Aha I see now, good point!
I think that this is a case where the upstream crate needs to have support in some form, although not necessarily with tokio-io itself. Presumably ZSTD_endStream is properly reentrant, right? In the sense that if it returns "would block" you can come back later and try again?

That's actually a good point. There are two spots where finish() can fail.

ZSTD_endStream -- this shouldn't happen in normal use.
self.writer.write_all -- this is what would likely fail with WouldBlock.

I don't actually know if the underlying C function ZSTD_endStream is re-entrant. I suspect not. But that can be handled in the wrapper by adding some state about whether the end-of-stream marker has been written.

Oh right sorry good point, the issue here looks to be with self.writer.write_all, not with ZSTD_endStream. In that sense yeah I think that there needs to be some kind of try_finish which doesn't return the inner writer, or does something like:
fn finish(self) -> Result<W, (Self, io::Error)>

BTW do your bzip2 and flate2 crates have the same problem?

Ayup, I believe so!

I've opened an issue for flate2

OK. This would be worth documenting somewhere in a general "notes" section so that people don't have to learn this the hard way :)

@sid0 We'd appreciate a PR offering documentation :)

Still working on internal legal approval, unfortunately :( will hopefully have it in a couple of weeks

@sid0 if you don't get around to it first I'll try to update the docs in this regard and I'll also try to tackle the flate2 issues soon.

Ok I'm going to close this in favor of the flate2 issue, as I think that this is solved now with updated docs? Otherwise pending work is in the various external crates.
Let me know if this is in error though!


Create a landing page

Is your feature request related to a problem? Please describe.
Create a landing page required to summarise/explain the app.
Describe the solution you'd like
A landing page

It will be great if @SiddharthSham create that with proper documentation.
Tools suggested- https://docusaurus.io/

Do we need a seperate documentation webpage? Shouldn't the UI be enough? Because there are only a bunch of sliders and explanations. 😅

Documentation should not be a problem for the demo.
We can always update after that.
On Thu 4 Jun, 2020, 5:23 PM Siddharth Sham<EMAIL_ADDRESS>wrote:

Do we need a seperate documentation webpage? Shouldn't the UI be enough?
Because there are only a bunch of sliders and explanations. 😅
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/SiddharthSham/cssify/issues/18#issuecomment-638800761,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHEOIBQGETZJQNX7KJJSEC3RU6DM7ANCNFSM4NSRLBFQ
.

I suggest we improve the README as much as we can, till then.

@ayushgupta9906, This project is no longer maintained. If still you want to give it a try please go ahead.


Animation.display Animation.none -> Animation.display Animation.block is not doing anything

I tried to have animation started with Animation.display Animation.none and transition it to Animation.display Animation.block (along with some translation). Translation works, but the display property never changes. Am I too slow with understanding something or is this as expected?

Try putting the Animation.display property inside an Animation.set after the Animation.to.

@mdgriffith Thanks for your help! It worked out just as I wanted it. I should have figured this out on my own :(

No worries.  If you're not on the elm slack, I recommend getting on there.  I regularly answer questions :)


Updated Diagnostics.Log

Shrunk to 3 log level (Debug, Warning, Error).
Fixed crash when the object which should be logged was null.
Moved project specific log level to Dir.Build.props

The constants per project files are being overwritten by the build.props instead of appended.
One has to tinker around with all project files to define a $(constants) to be able to append stuff like this: $(constants);PLATFORM_DESKTOP;TRACE ...

I'm no longer sure if we need all the compiler constants. In the end it comes down to is it a DEBUG build or not. So I think we could just as well use if (!)DEBUG.


Allow file changes at the root

I don't claim to understand why, but this seems to keep happening to me when I'm setting buck2 up in a private repo:
RUST_BACKTRACE=1 buck run ...
[2022-12-10T18:58:58.032-08:00] thread 'notify-rs fsevents loop' panicked at 'a file/dir in the repo must have a parent, but `root//` had none', buck2_common/src/dice/file_ops.rs:187:5
[2022-12-10T18:58:58.032-08:00] stack backtrace:
[2022-12-10T18:58:58.032-08:00]    0:        0x104b988c4 - std::backtrace_rs::backtrace::libunwind::trace::hece5cd97d7ff3f91
[2022-12-10T18:58:58.032-08:00]                                at /rustc/8b705839cd656d202e920efa8769cbe43a5ee269/library/std/src/../../backtrace/src/backtrace/mod.rs:66:5
[2022-12-10T18:58:58.032-08:00]    1:        0x104b988c4 - std::backtrace_rs::backtrace::trace_unsynchronized::h11e2344cfa8655d5
[2022-12-10T18:58:58.032-08:00]                                at /rustc/8b705839cd656d202e920efa8769cbe43a5ee269/library/std/src/../../backtrace/src/backtrace/mod.rs:66:5
[2022-12-10T18:58:58.032-08:00]    2:        0x104b988c4 - std::sys_common::backtrace::_print_fmt::h634b091d56b54f05
[2022-12-10T18:58:58.032-08:00]                                at /rustc/8b705839cd656d202e920efa8769cbe43a5ee269/library/std/src/sys_common/backtrace.rs:66:5
[2022-12-10T18:58:58.032-08:00]    3:        0x104b988c4 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::h81da8dd6c6b18539
[2022-12-10T18:58:58.032-08:00]                                at /rustc/8b705839cd656d202e920efa8769cbe43a5ee269/library/std/src/sys_common/backtrace.rs:45:22
[2022-12-10T18:58:58.032-08:00]    4:        0x104bb720c - core::fmt::write::ha734a2d93e3a9a62
[2022-12-10T18:58:58.032-08:00]                                at /rustc/8b705839cd656d202e920efa8769cbe43a5ee269/library/core/src/fmt/mod.rs:1202:17
[2022-12-10T18:58:58.032-08:00]    5:        0x104b91060 - std::io::Write::write_fmt::h8c69c70c7ecba05b
[2022-12-10T18:58:58.032-08:00]                                at /rustc/8b705839cd656d202e920efa8769cbe43a5ee269/library/std/src/io/mod.rs:1679:15
[2022-12-10T18:58:58.032-08:00]    6:        0x104b9a50c - std::sys_common::backtrace::_print::h6d2807747db383e7
[2022-12-10T18:58:58.032-08:00]                                at /rustc/8b705839cd656d202e920efa8769cbe43a5ee269/library/std/src/sys_common/backtrace.rs:48:5
[2022-12-10T18:58:58.032-08:00]    7:        0x104b9a50c - std::sys_common::backtrace::print::h07269e00f341ae20
[2022-12-10T18:58:58.032-08:00]                                at /rustc/8b705839cd656d202e920efa8769cbe43a5ee269/library/std/src/sys_common/backtrace.rs:35:9
[2022-12-10T18:58:58.032-08:00]    8:        0x104b9a50c - std::panicking::default_hook::{{closure}}::h1d2c0e05af7977f1
[2022-12-10T18:58:58.032-08:00]                                at /rustc/8b705839cd656d202e920efa8769cbe43a5ee269/library/std/src/panicking.rs:267:22
[2022-12-10T18:58:58.032-08:00]    9:        0x104b9a230 - std::panicking::default_hook::hf9193a1b36f532f9
[2022-12-10T18:58:58.032-08:00]                                at /rustc/8b705839cd656d202e920efa8769cbe43a5ee269/library/std/src/panicking.rs:286:9
[2022-12-10T18:58:58.032-08:00]   10:        0x102d5fb00 - cli::panic::initialize::{{closure}}::h17a22d7ec0bfa34a
BUILD FAILED
Command failed: Buck daemon event bus encountered an error

Caused by:
    0: status: Unknown, message: "error reading a body from connection: broken pipe", details: [], metadata: MetadataMap { headers: {} }
    1: error reading a body from connection: broken pipe
    2: broken pipe

Stack backtrace:
   0: std::backtrace_rs::backtrace::libunwind::trace
             at /rustc/8b705839cd656d202e920efa8769cbe43a5ee269/library/std/src/../../backtrace/src/backtrace/mod.rs:66:5
   1: std::backtrace_rs::backtrace::trace_unsynchronized
             at /rustc/8b705839cd656d202e920efa8769cbe43a5ee269/library/std/src/../../backtrace/src/backtrace/mod.rs:66:5
   2: std::backtrace::Backtrace::create
             at /rustc/8b705839cd656d202e920efa8769cbe43a5ee269/library/std/src/backtrace.rs:333:13
   3: anyhow::error::<impl core::convert::From<E> for anyhow::Error>::from

This change seems to fix it with no ill side-effects as far as I can see (though I don't have much experience with this codebase or as an user of buck2)
Refs: https://github.com/facebookincubator/buck2/issues/14

Thanks, I managed to reproduce this, your fix looks good!


[FEATURE] Pin all packages versions in requirements.txt and requirements-dev.txt

Is your feature request related to a problem?
Currently, multiple packages are missing pins. Hence, they will be installed differently based on the available latest versions of the individual packages. This is not a deterministic installation. Hence, we can add min and max version pins to avoid breaking changes.
What solution would you like?
Pin all packages

What if we have one file to export package versions, so requirements.txt and requirements-dev.txt, ci tests can import package versions from this file?

Closing this issue in respect of https://github.com/opensearch-project/opensearch-py-ml/pull/383


Extension issue

Issue Type: Bug
Extension Name: python
Extension Version: 2020.6.90262
OS Version: Windows_NT x64 10.0.18363
VSCode version: 1.46.1

:warning: We have written the needed data into your clipboard. Please paste! :warning:
{
	"messages": [],
	"activationTimes": {
		"codeLoadingTime": 1707,
		"activateCallTime": 1648,
		"activateResolvedTime": 143,
		"activationReason": {
			"startup": false,
			"extensionId": {
				"value": "ms-python.python",
				"_lower": "ms-python.python"
			},
			"activationEvent": "onLanguage:python"
		}
	},
	"runtimeErrors": []
}

Thanks for the bug report, but unfortunately we need some more information from you in order to triage this issue appropriately. Please edit your opening comment by providing a filled-in copy of our issue template. Once you are done please leave a comment to that effect.


Is it possible to export sql queries in JSON format in Dbeaver?

I am trying to figure out a way to get Dbeaver and matillion redshift in sync using github. Matillion doesn't accept sql files as input, so I want to convert my dbeaver queries into JSON format which is accepted by matillion.

Sorry for the long answer, Query cannot be exported in JSON format, but query result can (select in query context menu Execute>Export from query).
Please reopen the ticket or create a new one if you have any other questions.


List of selectors of icon font elements for blacklisting

Let's keep track of classnames we encounter in the wild:
Generic
Found on Icomoon, bbc.com, Twitter.
.icon
.Icon
.icon-*
Bootstrap
.glyphicon
Font Awesome
Take heed: .fa is such a short classname it might be used for other things as well.
.fa
.fas
.far
.fal
.fab
Fontello
.font-fontello

Classes have been updated, closing this issue for now. Let's open new issues for new classes!


Remove duplicate crate dependencies (e.g. multiple versions of nix)

v1.0.0-rc1 depends on three versions of the nix crate. I see that they are pulled in because of iptables, rtnetlink and zbus each require a different version of the crate. But is there any cargo magic to only pull in 1 (latest | compatible) version ?

My google search doesn't seem to find a solution for that other than patching the dependencies :/

Nope, there is no solution. That's what you get when you drop global dependency resolution. Each crate can depend on any version they want locally, and cargo will download and build that for them. If you want single nix you would have to either approach each crate maintainer and ask them to update their dependencies or, as @Luap99 mentioned, patch them yourself in a fork.


Gracefully pause queues before shutting down

This PR changes the way Verk will shutdown. It uses a GenStage consumer to watch for all the queues that should be paused. Waiting a max of shutdown_timeout
It fixes https://github.com/edgurgel/verk/issues/96
cc/ @krasio

Coverage decreased (-3.3%) to 84.549% when pulling 042e6344c2172fd7c7ab4b86dffe19ac7005064a on graceful-shutdown into 4dbc7290ad11ce046f345a6f9e1ef57f92988d9e on master.


Are u the backend or the frontend guy?

@mai-soup I had quick look in your portfolio and the other projects. From what I'm able to observe you apply a similiar UI style to your projects. It may serve as your digital finger print.
I personally like to taste different ice cone flavours to see what's out there and to be inspired by cool styled pages. I sometimes get hung upon these pages to figure out how the person did it. That maybe simply my personal preference on the frontend.
As developers, the more we've experienced, the better our gut feeling for estimations, technolgy choices etc.
How would u feel about changing your UI style and upgrading it with some nice shiny looking things?
In general: Are u the backend or the frontend guy?

Thought about this a bit. To me, being a frontend guy !== being a visual designer (which is something I know I am not good at, no matter how cool I think it is). Most of my projects, portfolio included, had a design made by someone else (or, in the case of YelpCamp, largely default Bootstrap components) that I attempted to replicate and make work as intended. I can appreciate a nice design, but I don't particularly enjoy trying to come up with them myself.
Though, in general, I suppose I enjoy backend more.


CSS in Hubzilla version 2.4

fwiw i noticed the sidebar menu on the settings page of the demo hub seems to be missing some CSS and isn't showing as a proper list menu.

s. Mike's commentar in Project hubs updated to 2.4 -thread from 05-31-2017 at 23:12

The active tab is now white.

s. Martin's commentar in the same thread at 23:19

This is probably due to some custom code at the demo hub.

@anaqreon can you please make the custom code changes undo?

It actually looks fine in my browser. @zotlabs do you still have an issue?

Unfortunately yes.

Hm... I managed to reproduce (allthough i don't know how)... Probably there was an issue with smarty chaches in the restored snapshot...
Please retry again!

Looks fine. I think we also got the white tab sorted so we can probably close this.


Support exclude_if callable at field level

Change Summary
This PR aims to add support for excluding field from serialization based on condition. As @davidhewitt suggested I added a new exclude_if argument at field level, which is callable that checks if the field value meets a condition. However, in this pydantic issue David suggested to use skip_serializing_if from Rust's serde, I could't find a way to use it due that serialization is being doing a loop for each field using serialize_map.
Related issue number
https://github.com/pydantic/pydantic/issues/10728

Checklist

[x] Unit tests for the changes exist
[x] Documentation reflects the changes where applicable
[x] Pydantic tests pass with this pydantic-core (except for expected changes)
[x] My PR is ready to review, please add a comment including the phrase "please review" to assign reviewers

Selected Reviewer: @sydney-runkle

please review

Super exciting! Will give this a thorough review soon. Working on getting v2.10 out, and this will be included in v2.11 :)

Would love to see an implementation on the pydantic side as well - you can point to this branch.
Looks like a great start. I'm impressed with how simple this is going to be!

Hello @sydney-runkle ! How do you do the implementation in pydantic when you need a pydantic-core feature? First create a release of pydantic-core and then use it in pydantic?  In this case are you requesting to create a PR in pydantic pointing to this branch to see what it looks like, right?

? In this case are you requesting to create a PR in pydantic pointing to this branch to see what it looks like, right?

Yes, exactly this! Once we merge, we'll include in a minor pydantic-core release, then we can bump the pydantic-core version officially on your pydantic PR and merge that one.
It's just helpful to see the implementation on both sides before we merge the pydantic-core one.

I'm curious how the callable should work in the model_dump, are you thinking in a callable with one argument Callable[[Any], bool] to be applied in all fields

Yes, exactly this. That being said, I chatted with the team, and we decided that introducing this at the field level first makes sense, and we can follow with other config / runtime specs later.

Alright, @sydney-runkle I created a PR pointing to this branch!


GradeSchoolTest not according to README

The Test: "Student_names_with_grades_are_displayed_in_the_same_sorted_roster" is not according to Readme-file.
See README.md lines 13ff: - Get a sorted list of all students in all grades.  Grades should sort as 1, 2, 3, etc., and students within a grade should be sorted alphabetically by name.
"students WITHIN a grade should be sorted alphabetically"
Proposed new Test:
    [Fact]
    public void Student_names_with_grades_are_displayed_in_the_same_sorted_roster()
    {
        var school = new School();
        school.Add("Peter", 2);
        school.Add("Anna", 1);
        school.Add("Barb", 1);
        school.Add("Zoe", 2);
        school.Add("Alex", 2);
        school.Add("Jim", 3);
        school.Add("Charlie", 1);

        var actual = school.Roster();

        var expected = new[] { "Anna", "Barb", "Charlie", "Alex", "Peter", "Zoe", "Jim" };
        Assert.Equal(expected, actual);
    }```

@MahrWe Ah, good catch! Perhaps what we actually should be returning is a dictionary, if I look at other tracks. Would you be interested in doing a PR for this?

I was going just about to respond @ErikSchierboom but you're too fast :) @MahrWe feel free to submit a PR and we can approve it.

Actually I am not sure how to do that, Pull the Repo, make changes and then.. Push to a new Branch, maybe?

@ErikSchierboom, @robkeim sorry I am new to github

There are some good tutorials out there:

https://www.digitalocean.com/community/tutorials/how-to-create-a-pull-request-on-github
https://yangsu.github.io/pull-request-tutorial/


Custom vocabulary to be transformed into SKOS

Hello @m1ci,
we would like to perform entity linking through the FREME CKEditor plugin on a custom dataset. I understand that we have to transform it into SKOS, with which I'm pretty much unfamiliar. Could you please help?
The dataset has been provided to us in CSV format and follows the following structure:
Term name; Term link; Term description;
Thank you very much in advance!
GWPP_Glossary.zip

@Katsivelisp can you send CSV which will include only the label and the link?
I tried to parse the CSV but I could not manage to parse it properly - there are new lines in the description field which makes the parsing difficult. I also could not manage to import it even in Excel.

@m1ci Here it is:
GWPP_Glossary.zip

Hello again @m1ci ,
any news on this?

Done, the dataset has been converted and integrated in the FREME NER (dev API) with ID gwpp-glossary
@Katsivelisp should I load it in the live API?
Here is a call example:
http://api-dev.freme-project.eu/current/e-entity/freme-ner/documents/?informat=text&input=A text with some glossary terms, such as Capsid proteins and Adenoviral keratoconjunctivitis.&outformat=turtle&language=en&dataset=gwpp-glossary

@m1ci I would say, let us try it first and we'll see.

Hello again @m1ci,
could you please load it in the live API? We need to run some tests with the CKEditor Plugin and it requires a stable version of the API.
Thank you very much!

done, see
http://api.freme-project.eu/current/e-entity/freme-ner/datasets/gwpp-glossary?outformat=json

Thanks @m1ci ! :)

Hello @m1ci,
could you please re-upload this dataset for us (newer version)?
GWPP-glossary.zip


Colab Model Problem

When i try to play Download models thing i get error.
If the script above fails, which is largely due to exceeding download quota, try run the script below.
!./scripts/download_checkpoints.sh
it doesn't work too..

When i try to play Download models thing i get error.
If the script above fails, which is largely due to exceeding download quota, try run the script below.
!./scripts/download_checkpoints.sh
it doesn't work too..

I have exactly the same issue and tried contacting Xuan but haven't heard back. I tried using a different gmail account to troubleshoot but the same error occurred. I think the colab demo is essentially not working anymore?


Illegal IDs may be entered via properties panel

Describe the Bug
Starting with v3.2.0 we enforce that XML IDs generated by the application are valid QNames. as https://github.com/camunda/camunda-modeler/issues/1622 indicates users are still able to input now illegal IDs, i.e. ${FOO}. Saving the diagram and re-opening it in the modeler fails the import.
Steps to Reproduce

open process
change ID to ${FOO}
save diagram
re-open diagram
see that import blows up

Expected Behavior

Valid IDs are enforced in all places where we allow users to edit IDs
Illegal IDs may not be saved by the user

Environment

OS: Any
Camunda Modeler Version: v3.2.0, ..., v3.5.0

Valid IDs are enforced in all places where we allow users to edit IDs

Does this concern the XML edit as well @nikku ?

You mean the XML editor? No. If people enter invalid IDs into the XML view the problem will be caught on import and properly indicated.
Adding validation on the XML view would be another related feature request.

For reference: The problem seems to be here as after this operation ${FOO} becomes FOO so it passes the QNames regex test.

Yes. This was intentional in the past but is not desired anymore.

Needs release of fixes in all libraries and integration into Camunda Modeler.

Closed via https://github.com/camunda/camunda-modeler/commit/f906e142f77c616f60435bf6b7e0a9abaedc9b05.


Detect region based on ~/.aws/config

When running local tests, or anytime running outside of an EC2 instance, it would be terrific if Spring Cloud AWS would detect that I'm not on an EC2 instance (because there is no instance metadata) and fall back to region selection based on  ~/.aws/config.  That way, I can manage my local region selection via the CLI / eclipse plugin and the setting is automatically respected by Spring Cloud AWS.

I think this is what @sethp-jive was looking for, too. Basically to inherit CLI env. right? https://github.com/openzipkin/zipkin/pull/1302#issuecomment-249084931

Indeed – the trouble is that there's an awful lot of behavior baked into the DefaultAwsRegionProviderChain (and far more baked into the DefaultAWSCredentialsProviderChain). I'm not an expert on how spring cloud likes to take its configuration, but in AWS-land a hard-coded access key and secret id are just the beginning.
The others allow dynamic role-switching based on some initial profile, which involves an online call to the STS service to get dynamic credentials. This flow is often required for certain organizations, as a common pattern is to partition AWS accounts and STS is the only way to get from the account where the user is provisioned to where the resources live. Unfortunately, as is the way of all things broadly consumed, everyone's got a slightly different way into the same broad idea – and while they're not perfect, the default provider chains do at least capture some of the more common behavior.

The AWS SDK for Java resolves region using a straightforward chain.  So does Spring Cloud AWS, but it's not the same chain.
See https://github.com/aws/aws-sdk-java/blob/master/aws-java-sdk-core/src/main/java/com/amazonaws/regions/DefaultAwsRegionProviderChain.java .  The order is 1) Environment variable 2) System Property 3) Profile (that's the .aws/config file), and 4) instance metadata.  This behavior is becoming consistent with the non-Java SDKs too.
But Spring's chain appears to ignore the environment variable, system property, and profile, charging straight to the instance metadata.  This causes a fatal error when running locally, which makes the entire framework hard to use: one must begin by hard-coding a region in a Spring-specific, non-AWS-native way (i.e. setting cloud.aws.region.static)

I agree with @kennyk65. Spring Cloud AWS should follow same chain as DefaultAwsRegionProviderChain for region resolution.
It's a breaking change so it will not end up in 2.2.x but rather 2.3.


fix: add enum support in parameters (fixes #4192)

Enhancement proposal - https://github.com/argoproj/argo/issues/4192
UI PR coming up next
Checklist:

[x] Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this is a chore.
[x] The title of the PR is (a) conventional, (b) states what changed, and (c) suffixes the related issues number. E.g. "fix(controller): Updates such and such. Fixes #1234".
[x] My organization is added to USERS.md.
[x] I've signed the CLA.
[x] I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
[x] My builds are green. Try syncing with master if they are not.

@alexec The Codegen (pull_request) is complaining about differences in

api/openapi-spec/swagger.json
docs/fields.md
openapi_generated.go
test/e2e/workflow_template_test.go

I haven't make changes in first 3.
And have added test in 4th.
How can I fix issues of codegen
Thanks

@alexec Have fixed issues, please let me know if any changes are required

How can I fix issues of codegen

make codegen

Thanks @alexec , the codegen issues are fixed and build is green,
How can we take this PR forward

@alexec I'll raise a UI PR after this gets merged. I actually have changes ready

@alexec Thanks for merging. Will let you know when the UI PR is ready


Rate throttling by ease

The problem
I am using your add-on and evcc (evcc.io) and easee is restricting access to the API with rate throttling. It might be a good idea to include the possibility in your add-on to limit access to the API, e.g. very 20 seconds. It is said that easee is fine with every 10 seconds but this applies to access from the same IP-address (and I have two chargers ...).
At the moment I ran into problems in a regular basis ... e.g.
Get "https://api.easee.cloud/api/chargers/EH####/site"
net/http: request canceled (Client.Timeout exceeded while awaiting headers)
Oliver
Version of Easee integration having the issue?
all
Version of Home Assistant Core having the issue?
all
Anything in the logs that might be useful for us?
No response
Additional information
No response

Let me start out by saying, this integration typically does not poll.
We use a SignalR connection to the server on which new states are pushed out.
With the exception of polling for schedules and cost sensors, which only happens when we have a reason to think it has changed (i.e. when a related change is pusfed out over the SignalR connection or after midnight).
In any case, the API you mention is not polled on a regular basis, but only once at startup.
If you have more than one site (that you have selected to monitor in the integration settings) it would poll that API once for each site. Do you have more than one site, and does that cause this issue for you?
If you enable debug logging for the Easee component, can you see anything more useful when you have issues?
(i.e. add this to your configuration.yaml):
logger:
  default: info
  logs:
    pyeasee: debug
    custom_components.easee: debug

Rate limiting in connection with EVCC has been discussed before also, see https://github.com/fondberg/easee_hass/issues/263
At that point in time we could not really figure out what we should change to make it better, since as I said, we are not polling...

Closing this since this is most likely a problem with evcc.io implementation.


Use the upstream repo by default and remove runit

Further simplify this cookbook by using the upstream repo to bring current packages to all users. Remove runit as this hasn't been a good idea since Chef was Opscode.

Nuking this for now. We'll just warn when users are on Runit instead.


Test: Fix PodCIDR issues on Kubernetes 1.7

On Kubernetes 1.7 PodSubnet was not correctly applied, because the
controller arguments had two times the parameters configured.
As seen in the code[0], if the PodSubnet is configured, all ExtraArgs
are created by Kubeadm.
[0] Kubernetes 1.7: https://github.com/kubernetes/kubernetes/blob/release-1.7/cmd/kubeadm/app/master/manifests.go#L450-L454
[0] Kubernetes master: https://github.com/kubernetes/kubernetes/blob/master/cmd/kubeadm/app/phases/controlplane/manifests.go#L304-L309
Fix #4338
Signed-off-by: Eloy Coto<EMAIL_ADDRESS>

This change is

test-me-please

test-me-please

https://jenkins.cilium.io/job/Cilium-PR-Ginkgo-Tests-Validated/3785/testReport/junit/k8s-1/7/K8sValidatedTunnelTest_VXLan_Check_VXLAN_mode/


I think this should fix the travis deploy.

Not 100% sure though so wouldn't mind someone with travis experience (@spikeheap) to take a look first.

cool!

:+1: https://travis-ci.org/jsoxford/jsoxford.github.com/builds/61216563

Awesome! So npm script/postinstall etc. have the node_modules/.bin on its path.


Diagnostic plots 📈📊📉

We should add some convenience functions that make plots similar to what is in the examples for "generic" problems to help people debug why things aren't converging or why they are converging to the value they are etc etc.
Maybe use something in the style of https://github.com/dfm/corner.py to show N>2 spaces, where the samples are, what the acquisition function looks like, ...

Duplicate of #67?

Yes


You told me to post on your github, then you delete what I wrote.

Give theboy181 his credit, sweetmini aka M&M cannot make exefs mods.

I have no idea who or what are you talking about, please give context next time. If there is missing the credit for some modder please open the config.yaml file for for the mod in question and point where is the mistake.


Non-revoked credential with status QR code shows as revoked

From Issue 10, Non-revoked credential with status QR code

Shows as revoked.

@dmitrizagidulin this shouldn't be happening, it was an issue, but I thought we fixed it.

Let's grab the json data to investigate

JSON might be:
{
"@context": [
"https://www.w3.org/2018/credentials/v1",
"https://w3id.org/security/suites/ed25519-2020/v1",
"https://w3id.org/dcc/v1",
"https://w3id.org/vc/status-list/2021/v1"
],
"type": [
"VerifiableCredential",
"Assertion"
],
"issuer": {
"id": "did:key:z6MkhVTX9BF3NGYX6cc7jWpbNnR7cAjH8LUffabZP8Qu4ysC",
"name": "Example University",
"url": "https://cs.example.edu",
"image": "https://user-images.githubusercontent.com/947005/133544904-29d6139d-2e7b-4fe2-b6e9-7d1022bb6a45.png"
},
"issuanceDate": "2020-08-16T12:00:00.000+00:00",
"credentialSubject": {
"id": "did:key:z6MkhVTX9BF3NGYX6cc7jWpbNnR7cAjH8LUffabZP8Qu4ysC",
"name": "Kayode Ezike",
"hasCredential": {
"type": [
"EducationalOccupationalCredential"
],
"name": "GT Guide",
"description": "The holder of this credential is qualified to lead new student orientations."
}
},
"expirationDate": "2025-08-16T12:00:00.000+00:00",
"credentialStatus": {
"id": "https://digitalcredentials.github.io/credential-status-playground/JWZM3H8WKU#3",
"type": "StatusList2021Entry",
"statusPurpose": "revocation",
"statusListIndex": 3,
"statusListCredential": "https://digitalcredentials.github.io/credential-status-playground/JWZM3H8WKU"
},
"proof": {
"type": "Ed25519Signature2020",
"created": "2022-08-19T06:58:29Z",
"verificationMethod": "did:key:z6MkhVTX9BF3NGYX6cc7jWpbNnR7cAjH8LUffabZP8Qu4ysC#z6MkhVTX9BF3NGYX6cc7jWpbNnR7cAjH8LUffabZP8Qu4ysC",
"proofPurpose": "assertionMethod",
"proofValue": "z33Wy3kvx8UEoPHdQWYHVCXAjW19AZpA88NnikwfJqcH9oNmHyqSkt6wiVS31ewytAX7m2vneVEm8Awo4xzqKHYUp"
}
}

This may have had something to do with the document loader being fixed. Assigned to Dmitri to retest.

@dmitrizagidulin - please retest and let us know if this is fixed.

I'm showing it as fixed, having tested it in latest build.


Specifiy The compatibe Telegram Bot API version

It would be nice if we have The Telegram Bot API version that is supported by yagop/node-telegram-bot-api  at  the top of the main readme file!

Done


Suggestion: No delay when using the snail mode if the display doesn't change

It would be better when using the snail mode, blocks that doesn't cause the display to change doesn't delay.
Even better, if running the move/turn block with snail mode, the turtle smoothly glides/change direction.
What do you think?

Snail mode is really for debugging so you want to step through all the blocks, not just the graphics blocks themselves.
Re gliding, that would be a nice enhancement.


Debian package

Prepare package for debian

See: https://github.com/PureHTML/csob/tree/debianized


fix onDestroy of undefined in react when accessing annotation

Hello!
I love your project, but I encountered an error TypeError: Cannot read property 'onDestroy' of undefined in my React project when added annotation in my chart state.
I solved it by simply checking if current chartInstance is exist, then it can pop it.
Btw this is my first pull request :D please go easy on me.
Thank you !

Thank you for fast response !
To be honest, I have no idea why. I only tried to make a horizontal line as explained here
In my code, I only use it once in my react state
import {annotation} from 'chartjs-plugin-annotation'

...
state:{

portofolioChartOptions: {
   responsive: true,
      maintainAspectRatio: false,
      annotation: { //draw horizontal line
        annotations: [{
          type: 'line',
          mode: 'horizontal',
          scaleID: 'y-axis-0',
          value: 105,
          borderColor: 'rgb(75, 192, 192)',
          borderWidth: 4,
          label: {
            enabled: false,
            content: 'Initial Portofolio'
          }
        }]
      },
      tooltips: {
        mode: 'index',
        intersect: true
      },
      scales: {
        xAxes: [
          {
            ticks: {
              autoSkip: true,
              maxTicksLimit: 10,
            },
          },
        ],
        yAxes: [{
          ticks: {
              beginAtZero: true
          }
        }]
      },
    }

I used it here
<Portofolio data={this.state.portofolioChartData} options={this.state.portofolioChartOptions} />

And here is my Portofolio component
import { Line } from 'react-chartjs-2';
export class Portofolio extends React.Component{
    constructor(props){
        super(props);
    }
    render(){
        return(
            <div>
                <Line data={this.props.data} options={this.props.options}/>
            </div>
        )
    }
}

Do you know the reason?

I think the problem lies in hot loading. I clearly saw TypeError: Cannot read property 'onDestroy' of undefined. But when I delete node_modules and run npm install again without changing anything in your package, it run smoothly.
Sorry for taking your time. Cheers!

@jonassunandar btw,  deleting node_modules and running npm install did not solve this exact issue for me. But I'm running on Angular though.


Chrome - onDrop not being called when dragging from downloads bar

I can reproduce this bug only when dragging for the downloads bar. I'm using Chrome 51.0.2704.106.
Is it a Chrome bug? any workarounds for this issue?

Duplicate of #191?

Possibly.  I wasn't sure if he was talking about the same drag scenario

I don't think this is necessarily related to #191, but I think it is definitely an issue. The standard Dropzone.js library works fine when dragging from the downloads bar, but react-dropzone doesn't work.
Chrome 52.0.2743.116 (64-bit), Mac 10.9.5

Yes. still reproducible with the latest version of Chrome 52.0.2743.116 (64-bit)

So apparently the weird fix in #74 solves this issue
adding this line:
e.dataTransfer.dropEffect = 'copy';

Great, just needs to be PRed then!

Should be fixed in https://github.com/okonet/react-dropzone/releases/tag/3.6.0


Removed fallback exception from version change logic.

Description
We added a new feature in 4.9 to automatically detect dialog changes. Some customers are complaining about the fallback logic we have to automatically throw an exception if the bot doesn't handle the new event we added.  We've decided to remove the fallback exception and make the feature entirely opt-in.

Pull Request Test Coverage Report for Build 134369

0 of 1 (0.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.07%) to 80.272%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

libraries/botbuilder-dialogs/src/dialogContainer.ts
0
1
0.0%

Totals

Change from base Build 133949:
0.07%

Covered Lines:
12652

Relevant Lines:
15048

💛  - Coveralls

The C# PR that matches this is here:
https://github.com/microsoft/botbuilder-dotnet/pull/4000


It is necessary to Install client on my workstation?

I'm very interested in your projet kubeinvader.  I have some questions about it. Can you help me , thank you very much.
Must i intall client on my workstation ? or can i install it on the openshift?

workstation is just one option.  You should be able to install it on openshift and visit the URL.
# Choose route host for your kubeinvaders instance.
ROUTE_HOST=kubeinvaders.org

workstation is just one option. You should be able to install it on openshift and visit the URL.
# Choose route host for your kubeinvaders instance.
ROUTE_HOST=kubeinvaders.org

Hello, thank you very much for your response. I have already succed to install  it in a cluster k8s using helm, now, i want Install KubeInvaders on Openshift https://github.com/lucky-sideburn/KubeInvaders#install-kubeinvaders-on-openshift .
But i have the problem to connnect the endpoint.   So in the openshift, is it necessary to create a router or ingress to make the route enable?

Thank @jbkc85


support for polylines on terrain via entity API

See https://github.com/AnalyticalGraphicsInc/cesium/pull/6615

@likangning93, thanks for the pull request! Maintainers, we have a signed CLA from @likangning93, so you can review this at any time.

I am a bot who helps you make Cesium awesome! Contributions to my configuration are welcome.
:earth_africa: :earth_americas: :earth_asia:

Should we automatically clamp to ground when all of the position heights are zero?

I was wondering if this would be kind of a breaking change, but I guess I can't see a use case where users would be counting on intentional heights of 0 behaving like they do now.
It does put additional onus on the Entity API layer to check position heights though, which seems like it could duplicate a lot of the cartesian-to-cartographic work in GroundPolylineGeometry.

I would recommend against this change.  There are certainly places in the world where the ground is below 0, so it's not even a guarantee on the ground is what is desired, plus there are performance issues to consider as well.  We might change our mind later (when terrain is on by default) but I wouldn't suggest it for this PR.

@bagnell updated!


Duplicated compile operation

I have now observed twice that starting a build (of client-samples projects) cause duplication of output:

> Task :nativeCompile
[Fri Mar 27 21:23:56 CET 2020][INFO] ==================== COMPILE TASK ====================
[Fri Mar 27 21:23:56 CET 2020][INFO] ==================== COMPILE TASK ====================
[Fri Mar 27 21:23:56 CET 2020][INFO] We will now compile your code for x86_64-linux-linux. This may take some time.
[Fri Mar 27 21:23:56 CET 2020][INFO] We will now compile your code for x86_64-linux-linux. This may take some time.

[Fri Mar 27 21:23:59 CET 2020][INFO] [SUB] [com.gluonhq.hello.hellogluon:16441]    classlist:   2,949.85 ms
[Fri Mar 27 21:23:59 CET 2020][INFO] [SUB] [com.gluonhq.hello.hellogluon:16441]    classlist:   2,949.85 ms
[Fri Mar 27 21:24:00 CET 2020][INFO] [SUB] [com.gluonhq.hello.hellogluon:16441]        (cap):     633.47 ms
[Fri Mar 27 21:24:00 CET 2020][INFO] [SUB] [com.gluonhq.hello.hellogluon:16441]        (cap):     633.47 ms
[Fri Mar 27 21:24:01 CET 2020][INFO] [SUB] [com.gluonhq.hello.hellogluon:16441]        setup:   1,929.38 ms
[Fri Mar 27 21:24:01 CET 2020][INFO] [SUB] [com.gluonhq.hello.hellogluon:16441]        setup:   1,929.38 ms

This is using Gradle 6.3 and the daemon.
Maybe something static in the plugin somewhere, which survives individual invocations due to the daemon.

This happens when I publish a new substrate artifact to localMaven.
Substrate keeps a static logger instance.
For some reason, when executing under gradlew, the logging gets replicated for however many Logger instances have been created.
Printing a stacktrace with Info shows there is still only one process running. So this is an issue created inside Gradle wrapper.
And I think it only happens when building with a new substrate snapshot - so regular users will probably not see this.
In any event, it is harmless (albeit annoying).


FOURTH QUESTION: How do we specify which parts of the memory/cache  hierarchy are affected by CMOs ?

This fourth question is just to complete the set of questions in rough priority order: (1) address range vs per-cache-block-address? (2) microarchitecture cache index like (set,way) vs ???; (3) what CMO operations (CLEAN! EVICT! DISCARD! ZALLOC? ...); and now this issue: which caches are affected?  Or other parts of the memory subsystem?
E.g. do we flush/evict/clean data from the L1 D$? The L2 D$, Shared L3$? L4$ ...
To what level...  all the way to DRAM?  To NVRAM?  To Iron Mountain?
Do we prefetch into L1 D$, filling up all other caches alomg the way from DRAM?  Can we prefect into L2$ but not L1$, to avoid thrashing?  Some architectures have a small prefetch cache (e.g. HP Assist Cache) that exists to reduce thrashing.  Can we prefetch into L1$ without putting it into L2$?  Exactly what does "non-temporal prefetch" mean, anyway?
Can we prefetch into other processor caches?
How can any of this be portable code?    Iff you say L1$, I (as a microarchitect in a former life) will propose an L0$, or an L0.5$, or an L1.5$ between L1$ and L2$.

While it is fun to write these questions with lots of ? and !, I don't mean to imply that this is a hard problem.
Cache microarchitectures changhe all of the time.  Any notion of cache level is quickly obsolete.
But we can enumerate use cases, and for any particular use case, on any given implementation, we can describe what caches need to be invalidated.
E.g. for non-coherent DMA I/O, that writes into DRAM without changuing the cacghes, we will need (a) EVICT operations to flush dirty data to DRAM before the DMA, or maybe DISCARD operations for some embedded systems like network devices; and (b) and some sort of operation to flush stale data out of the caches after the DMA (whether that operation is another DISCARD, or EVICT, or possibly a new operation that I realized was better than EVICT but safer than DISCARD, which I don't have a name for yet.)
But forget about the EVICT/DISCARD/CLEAN/... operations - that is the earlier issue, THIRD PRIORITY question.
For non-coherent DMA I/O that Updates memory without updating cache, the CMOs  take data out  of any parts of the cache hierarchy, and flush it to DRAM.
But some I/O devices can inject data directly into the cache.  If they do that coherently, great, However, this may be happening in a system where processors have L1$ than are not coherent with the L2$.  In which case the CMOs operate FROM caches that are closer than the L2$, and TO the L2$.  (Although there is no harm in flushing all the way to DRAM, except for for performance).
E.g. some systems do software managed coherency.   I am most used to nodes that might have CPUs, each with coherent D1$ and I1$, coherent L2$, and possibly an L3$ that is coherent amongst the 4 to 8 CPUs in  in a node.  However, there are many such nodes in a system, sharing DRAM; and often the DRAM has its own caches on the other side of the interconnect.   In such a system you can used  coherent shared memory techniques  between processors in the same note, without requiring CMOs, but between the non-coherent notes you will require CMOs.
E.g. I was recently educated about embedded systems, where CPUs have private I$ and D$, and share an L2$   incoherently.   but there may be multiple such nodes that have L2$,  which are themselves  incoherent. So producer/consumer  between processors sharing the same L2 need to flush to the L2; but producer/consumer  between processors that do not share the same L2 need to flush to whatever is beyond the L2, like DRAM.
Lots of people will jump up and down this and say "to the point of coherence" ...   all that I wish to point out  is that there are  different points of  coherence for processors within the same node and between nodes.  I.e. the point of consistency is a function of the processors and caches involved.
E.g. hot unplug and  sending a processor to sleep requires CMOs that flush all caches on that processor to whatever maintains state - e.g. battery powered laptiop DRAM.  You may not need to flush caches on processors that are not being sent to sleep or  unplugged.  But for  noncoherent I/O  or software managed  coherence you may need to flush all caches  to which data may have migrated,  or between which processors might have migrated.  i.e. sometimes CMOs need to be a local, sometimes  global,  sometimes of intermediate scope.
E.g.  flushing to non-volatile storage  or persistence, so that even a battery can be removed. Versus flushing to all RAID copies of non-volatile storage, or even to remote systems, like Tandem Non-stop.
I.e.   how far  you need to flush to or beyond DRAM may depend on whether you want to survive (a) removing power to a single CPU, (b) removing power to an entire system, (c) loss of one of the NVRAM units, or (d) loss of redundant systems on an entire continent (thermonuclear war, or perhaps just a sub-oceanic cable).
E.g. in security, for timing channels, you typically need to flush all of whatever cache levels you need -  both data you have modified and data that might belong to others - either all the way to whatever level you have partitioned storage/caches/memory, or all the way to whatever level you think the timing channels will be low enough bandwidth that you can tolerate. (Gernot Heiser implemented SeL4 which required full L1$ EVICT, but where the L2$ was  partitioned by page coloring,  so these security flushes only needed to go to the L2.   however, many systems do not know how to partitioned the L2, so they would need to flush all the way to DRAM.)
But  main channel security differs from most of the other forms of CMOs and that timing channels security requires not just the caches to be EVICTed and left invalid, but also  any branch predictors, prefetchers, etc.  I.e, the domain of security related flushes increases.  There will be seaparte issues as to  whether this should be included in CMOs or not.
E.g. for security, for remanence (preventing physical attacks on storage, like freezing DRAM with  liquid nitrogen  and a cell phone that you have acquired) ...
OK, enough... I am getting punchy.  I just wanted to  provide examples.

One more example:   PERFORMANCE  PROGRAMMERS, people that are doing low-level performance tuning,  on systems that range from  embedded IoT to HPC,  may want  extremely precise control.  They will argue that they would like to be able to prefetch into or flush data out of any micro architectural cache.
All of the other usage models are more abstract.  PERFORMANCE  PROGRAMMERS  often want to bypass  such abstractions.
Now,   there is some possibility of abstraction  even for performance programmers.  E.g. the performance programmer may want to flush to the points of coherence  between producer/consumer; or to flush to the first cache bigger than a particular data structure.
It is TBD whether we, the RISC-V  CMOs task group, will want to provide all of the control that  performance programmers would like. (GLEW OPINION: no, except via OS and tech-config discovedry interaction, and a level of indirtection in the CMOs.)
many people argue that performance programmers usually fail;  that they think they can do a better job than hardware, but they often waste time and don't achieve much performance. . While this may be true, there are counterexamples.  . For a small company, a big customer when that is achieved only by a little bit of performance programming may mean the difference between success or bankruptcy.
===
APOLOGIES: I thought this was going to be a short issue, instead I  wrote more than I did in the important issues.
Anyway, I expect that people will talk in terms of things like ARM's Points of Coherence and Points of Persistence:

Point of Coherence (for a single layer  of incoherent processors)

Point of  Inner/Outer Coherence

Point of I/O Coherence (DRAM for  some noncoherent DMA, sometimes...)

Point of Inner Persistence (Battery backed up DRAM or power management)

Point of Outer Persustence (NVRAM... but whether thaat is first NVRAM copy or all NVRAM copy depends)

While these are great for simplifications,  as I have several times tried to point out they are not a complete set.   there are systems that may have different or multiple layers of points of coherence. The question is, what is a sufficiently good set for RISC-V's markets.
Some people say that we are creating an abstract  memory/cache hierarchy. I think this is bogus: we are creating a simplified or restricted abstract memory/cache hierarchy. What good is an abstraction if it fails the moment you become the moment you start doing anything new and interesting?   However, such a simple or restricted abstract model is good enough for many systems. I think that it is possible to create a truly abstract model, but that it would require interaction between operating system and configuration/discovery, and a level of indirection in specifying the scope of CMOs that many people are reluctant to provide.
--
OK, I have finally finished the first draft of this issue.
I just wanted to provide a placeholder for how we specify the scope of CMOs,  to complete the quad-fecta  of what I see as the most important top-level issues for CMO instruction set design.
I apologize for this verbal diarrhea and getting carried away. I apologize to anybody that I have insulted by saying that their abstract model is bogus.
Much of the text written above exists in other places, and probably shouldn't be in this issue; and I will probably remove it and provide references.
The verbosity in part is due to not very good terminology with this issue, and due to my rejection of the common terminology (e.g. Intel, ARM) of one or a few points of coherence  as being simplistic and unsatisfactory.   Although undoubtedly good enough for many systems.

I propose devising an abstract cache model on which the CMOs operate. Without such, it's harder to come up with a consistent set of definitions.
The abstract model can be as simple or as complex as we want, with the corresponding complexity and expressibility in the instructions.
A super simple model compresses all the hierarchy into a single cache level, basically hart -> cache -> memory, where each hart has a cache and every hart shares memory. This captures the notion that we are working with copies of data distinct from the actual memory location. A related set of instructions operates on the "copies" in the caches, e.g. EVICT moves all copies from the cache to memory. I don't pretend this is a complete model, but hopefully it illustrates what I mean.

@AndyGlew re: abstract models.... Not offended. Still going to push for one... :)
re: points of coherence.... There are "points of serialization" where request streams from different harts merge. I think this is the fundamental definition of levels, whether a cache exists there or not. In ARM's terminology, the PoC is the ultimate point of serialization. But even if we agree on definitions, discovering them and expressing them generically is challenging.
(FWIW, my super simple model consists of a single PoS/PoC at memory.)


Subscription: apply IoTConsensusV2 as cluster mode for integration test

follow up #13481

What a spetacular work💪🏻YOU MAKE SUBSCRIPTION GREEEEEEEEEAT AGAIN!!!🔥⚡


⚠ Avatar API Endpoint has degraded performance

In 8fb131e, Avatar API Endpoint (https://avatar.roblox.com/v1/avatar-rules) experienced degraded performance:

HTTP code: 200
Response time: 1760 ms

Resolved: Avatar API Endpoint performance has improved in f309644.


added new functionality to respondents tab

edit  contact details, resend verification email, enable/disable enrolment)
Motivation and Context
Business requested ability to make these changes from a respondents page
What has changed
Buttons added for edit contact details, resend verification email and enable/disable enrolment added and appropriate changes made to enable that.
How to test?
run tests on view_edit_respondents_tab branch
alternatively can manual test by clicking through from the respondents tab.
Links
https://trello.com/c/JOPM1IFq/394-us216-view-respondent-details-m
https://github.com/ONSdigital/rasrm-acceptance-tests/pull/258

you should definitely be using the Flash pattern if you're not using it, to display feedback messages to users as @insacuri indicates. There should be examples in the codebase you can copy.

There's no option to resend a verification email if the account has a pending enrolment (i.e. an account has been created but not yet verified).

added 'created' to the check of when to show the button

Changes that I asked for are now done.
@insacuri, @ryangrundy7 , and @gavinleeedwards happy with your requested changes?

There's no option to resend a verification email if the account has a pending enrolment (i.e. an account has been created but not yet verified).

added 'created' to the check of when to show the button

This isn't quite right.  Adding the 'resend' link for all created accounts will mean the 'resend verification' link is still shown for accounts that have been fully verified.  It needs to be there for accounts that are in 'Created' state but have a pending enrolment against them.

All works fine for me now 👍


DoSyncV2: response returned 524

Hello,
I have the problem that the initial sync fails with Error 524. I don't exactly know what the problem is.
Log is attached below.
Sync v3 [0.5.2] ()
15:47:16 INF creating handler
15:47:16 INF retrieved global snapshot from database
15:47:16 INF listening on <IP_ADDRESS>:8009
15:47:16 INF StartV2Pollers num_devices=1
15:47:16 INF EnsurePolling lock acquired device=c6748e448689802d182990e29db1ddb1814374c4a71aaab5b32ddbade5b451f3 user_id=@lucas:neuber-it.de
15:47:16 INF Poller: v2 poll loop started since= user_id=@lucas:neuber-it.de
15:47:20 INF EnsurePolling: new request user=@lucas:neuber-it.de
15:47:20 INF EnsurePolling: request finished user=@lucas:neuber-it.de
15:47:20 INF EnsurePolling lock acquired device=c6748e448689802d182990e29db1ddb1814374c4a71aaab5b32ddbade5b451f3 user_id=@lucas:neuber-it.de
15:48:55 WRN Poller: sync v2 poll returned temporary error error="DoSyncV2: response returned 524 " code=524 user_id=@lucas:neuber-it.de
15:48:55 WRN Poller: waiting before next poll duration=3s fail-count=1 user_id=@lucas:neuber-it.de
15:50:37 WRN Poller: sync v2 poll returned temporary error error="DoSyncV2: response returned 524 " code=524 user_id=@lucas:neuber-it.de
15:50:37 WRN Poller: waiting before next poll duration=3s fail-count=2 user_id=@lucas:neuber-it.de
15:52:19 WRN Poller: sync v2 poll returned temporary error error="DoSyncV2: response returned 524 " code=524 user_id=@lucas:neuber-it.de
15:52:19 WRN Poller: waiting before next poll duration=3s fail-count=3 user_id=@lucas:neuber-it.de

EDIT: Since 524 is a Cloudflare Timeout code, I temporarily disabled the Cloudflare Proxy. After that, I instead got Error 504 - Gateway Timed Out, which was caused by nginx. After I set the proxy_read_time to 600s (10min), I got a timeout error by synapse itself.

UPDATE: I did some testing and apparently I was "half joined" in a room. I did a purge using synapse's manhole and now it works.


Updates for 1.16.0 release.

 Is that expected?

Yeah, most of them are known failures.

When will this version be available on Cocoapods? 😮


Test results don't match the web page

From the browser http://www.speedtest.net/result/2604953153.png (66.2 d, 9.7 u)
cli: (same server)
./speedtest-cli-3
Retrieving speedtest.net configuration...
Retrieving speedtest.net server list...
Testing from Comcast Cable (<IP_ADDRESS>)...
Selecting best server based on ping...
Hosted by Grande Communications (San Marcos, TX) [204, .03 km]: 67.949 ms
Testing download speed........................................
Download: 32.75 Mbit/s
Testing upload speed..................................................
Upload: 8.04 Mbit/s
OS: ArchLinux 64-bit, git version 11fb59d6aeed4ae6d781cc27282300ea1ca8afe1
Python 2.7.3

Likewise : web site is giving me 90Mbit/s, speedtest-cli more like 65Mbit/s
Tests like downloading Ubuntu ISOs from three concurrent mirrors are giving me around 70Mbit/s - so I'm wondering what the website is doing different.


Port Mail as s-c-s source

As a developer, I'd like to move mail module from XD to s-c-s repo, so I can use it as source to build streaming pipeline.
Acceptance:

mail as source module is available in spring-cloud-stream-modules repo
maven repo includes mail module with respective group/artifact/version detail

There's a PR for this already.


Update requirements

composer require cuyz/valinor problem:
Your requirements could not be resolved to an installable set of packages.
- cuyz/valinor 0.17.0 requires psr/simple-cache ^1.0 || ^2.0 -> found psr/simple-cache[1.0.0, 1.0.1, 2.0.0, 2.x-dev] but the package is fixed to 3.0.0 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.

Already released psr/simple-cache 3.0.0:
https://packagist.org/packages/psr/simple-cache

Hi @nd2021, sorry for the inconvenience; the first major release of this library will be published at the beginning of next week, it will update the requirements and allow psr/simple-cache:^3.0.
May I ask which PHP version your application is running on?

Great! PHP 8.1

Hi @nd2021, version 1.0.0 has been released and should fix your issue.
Closing the issue. 😉


Capacity > 127 causes compile failure.

//! examples/capacity.rs

#![deny(unsafe_code)]
#![deny(warnings)]
#![no_main]
#![no_std]

use cortex_m_semihosting::{debug, hprintln};
use lm3s6965::Interrupt;
use panic_semihosting as _;

#[rtic::app(device = lm3s6965)]
const APP: () = {
    #[init]
    fn init(_: init::Context) {
        rtic::pend(Interrupt::UART0);
    }

    #[task(binds = UART0, spawn = [foo, bar])]
    fn uart0(c: uart0::Context) {
        c.spawn.foo(0).unwrap();
        c.spawn.foo(1).unwrap();
        c.spawn.foo(2).unwrap();
        c.spawn.foo(3).unwrap();

        c.spawn.bar().unwrap();
    }

    #[task(capacity = 128)] // <- here
    fn foo(_: foo::Context, x: u32) {
        hprintln!("foo({})", x).unwrap();
    }

    #[task]
    fn bar(_: bar::Context) {
        hprintln!("bar").unwrap();

        debug::exit(debug::EXIT_SUCCESS);
    }

    // RTIC requires that unused interrupts are declared in an extern block when
    // using software tasks; these free interrupts will be used to dispatch the
    // software tasks.
    extern "C" {
        fn SSI0();
    }
};

gives:
cargo run --example capacity --target thumbv7m-none-eabi
   Compiling cortex-m-rtic v0.5.3 (/home/pln/rust/rtic/cortex-m-rtic)
error: custom attribute panicked
  --> examples/capacity.rs:12:1
   |
12 | #[rtic::app(device = lm3s6965)]
   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   |
   = help: message: UNREACHABLE

error: unused imports: `debug`, `hprintln`
 --> examples/capacity.rs:8:28
  |
8 | use cortex_m_semihosting::{debug, hprintln};
  |                            ^^^^^  ^^^^^^^^
  |
note: the lint level is defined here
 --> examples/capacity.rs:4:9
  |
4 | #![deny(warnings)]
  |         ^^^^^^^^
  = note: `#[deny(unused_imports)]` implied by `#[deny(warnings)]`

error: unused import: `lm3s6965::Interrupt`
 --> examples/capacity.rs:9:5
  |
9 | use lm3s6965::Interrupt;
  |     ^^^^^^^^^^^^^^^^^^^

error: aborting due to 3 previous errors

error: could not compile `cortex-m-rtic`.

To learn more, run the command again with --verbose.:

Problem related to the queue length for associated to a priority level. The accumulated queue size of all tasks spawned at a certain priority. Likely related to U8 sized queue.

The cause of this has been identified, but currently a fix has not been decided on.
It comes from an internal queue which has the sum of all other queues in size which overflows (after rounding up to a power of 2).

This has now happened to a user on 0.6
Time to fix

Fixed


AddMemoryPressure causes Garbage Collection to run for over a minute

Describe the bug
I have an intermittent bug in my application that is causing our UWP app to hang for large periods of time.
The bug is currently blocking us from our next release.
The issue is that occasionally when we unload one of our UserControls, the entire application freezes.
The issue reproduces sporadically.
When the issue reproduces I cannot pause inside visual studio debugger, as the debugger hangs and I have to kill the app.
I have been able to pause inside of WinDBG however.
From the callstack inside windbg, it looks like the xaml engine gets stuck trying to run a GC collection pass.
The problematic part of the call stack starts with a call to GC.AddMemoryPressure().
76 000000be`9bffddc0 00007ff8`5e697ba4     SharedLibrary!System::GC.AddMemoryPressure+0x18e [f:\dd\ndp\fxcore\CoreRT\src\System.Private.CoreLib\src\System\GC.cs @ 572]

When the app starts reproducing this issue, the CPU starts spiking, and the memory consumption of the application starts to go up until the framework figures itself out. This can take upwards of a minute, and I have seen my memory consumption go from 600MB to 1.2GB in this time.
I have spent some time profiling this issue under both visual studio profiler and jet brains dot memory profiler.
The memory that is increasing in this time is all within the native/unmanaged space and I believe this is completely within the xaml framework increasing the memory.
I have been able to put breakpoints through windbg on the xaml parts of the call stack, and these will keep hitting, which told me that parts of xaml are still running here and we are not deadlocked.
While this seems like a bug in the engine, it would be good to know what we have done within our code that is exasperating this issue, and if there is a way that we can work around the issue.
The control that we are unloading is around 4000 elements in the xaml tree. The user control itself we keep in memory to improve performance when the user wants to bring the view back onto screen. The control that we believe is causing the problem is backed by a listview. In my repro the list view contains 6000 items, but virtualization is working, and obviously not all of those items are in the tree.
Steps to reproduce the bug
I currently don't have a consistent way to reproduce this, and this release of the app hasn't made it's way into production yet.
If it's valuable i should be able to collect a time travel trace of the application and attach that.
Otherwise, if we can't get a solution, we may be shipping this feature soon with a feature flag that will turn it off, and I can send instructions to enable the feature flag along with repro steps.
Expected behavior
GC should not be taking upwards of a minute and hanging the app completely.
Screenshots

I have attached a screenshot of a dot memory profiler trace. The yellow line indicates time spent in GC, usually time in gc is a very small yellow dash, however here the line goes for a minute and a half. Another line shortly after goes for about 15 seconds, which is also unacceptable.
You can see the increase of unmanaged memory when the gc starts happening as well.
AddMemoryPressureCallStack.txt
I have attached a copy of the stack track that i broke into while the app was in this state.
NuGet package version
WinUI 2 - Microsoft.UI.Xaml 2.8.2
Windows version
Windows 11 (22H2): Build 22621
Additional context
No response

76 000000be`9bffddc0 00007ff8`5e697ba4     SharedLibrary!System::GC.AddMemoryPressure+0x18e [f:\dd\ndp\fxcore\CoreRT\src\System.Private.CoreLib\src\System\GC.cs @ 572]
77 000000be`9bffde20 00007ff8`5e694274     SharedLibrary!$8_System::__ComObject.AddGCMemoryPressure+0x44 [f:\dd\ndp\fxcore\CoreRT\src\System.Private.Interop\src\Shared\__ComObject.cs @ 439]
78 000000be`9bffde50 00007ff8`5e694220     SharedLibrary!$8_System::__ComObject.__Attach+0x44 [f:\dd\ndp\fxcore\CoreRT\src\System.Private.Interop\src\Shared\__ComObject.cs @ 573]
79 000000be`9bffdee0 00007ff8`5e6941c5     SharedLibrary!$8_System::__ComObject.__AttachingCtor+0x50 [f:\dd\ndp\fxcore\CoreRT\src\System.Private.Interop\src\Shared\__ComObject.cs @ 406]
7a 000000be`9bffdf20 00007ff8`5e694181     SharedLibrary!$8_System::__ComObject.AttachingCtor+0x35 [f:\dd\ndp\fxcore\CoreRT\src\System.Private.Interop\src\Shared\__ComObject.cs @ 393]

https://github.com/dotnet/corert/blob/a8830fe5158c499a75b19239524a6d1092a679fe/src/System.Private.Interop/src/Shared/__ComObject.cs#L558
Following the breadcrumbs from there, I think it has something to do with the GCPressureAttribute. Are you using types with [GCPressure] applied in your controls?

Agreed, the issue seems to coming in from GCPressure, however we don't have this attribute anywhere in our callstack.
I'm assuming that some of the xaml controls we are using has this attribute.
a 90 second GC walk seems like something has gone completely out of whack though, and the fact that it doesn't reproduce consistently seems to imply to me that there is some sort of race going on.

closing since we are not planning to do any work in WinUI2. See here for more details - https://github.com/microsoft/microsoft-ui-xaml/blob/main/docs/contribution_handling.md#winui-2


Acceptance test fix for resetting the volume

Upon rejection of an NCMC proposal, all variables must be reset to their initial values. This PR fixes the fact that, previously, the periodic box vectors were not reset after rejection.
@bas-rustenburg, this fix should also work for #protons.

I noticed one minor opportunity for optimization. If you use asNumpy=True for your positions, velocities and box vectors, you save a few operations that add and strip units.

So the positions were being reset, but not the box vectors? I wonder why this didn't lead to insanely large energies.


Fix issues related time based output rate limiting

This PR contains fixes for below cases.

Support to use plural time scale in output rate limiting
Fix for time based output rate limiting

Fix for https://github.com/ballerina-platform/ballerina-lang/issues/8441.


iOS seems to load the images every time whereas Android caches them as expected

Hello,
Great component! It is working fine on Android when I do a native build however when I do a native build on iOS the images load every time. When I go back to the page the images reload - ie. it does not seem to cache the images on IOS (iPhone 6S+ and iOS 10.3).
Has anyone else had this problem?

Hi, so it's not working on IOS?

Yes, it does not work as expected - ie. it is not caching the images like it does on Android


Refactor CaseConverter

Refactor case converter in a full OOP way. This will ease later changes.

Changes should pass phing qa


[breaking change] load_dotenv should default to False

For Django and Flask load_dotenv currently defaults to True
In production environments this lead to unpredictable environment, so the extensions should load it only if user explicit set to True.

load_dotenv={"when": {"env": {"is_in": ["development"]}}}

@rochacbruno Are either of these supposed to work in v3.1.7? I cannot get either of them to work. the load_dotenv={"when"... notation is also in the learndynaconf repo example, but I am not finding anything like it in the documentation


pytest-related test failures on main

We're seeing failures like
 INTERNALERROR> Traceback (most recent call last):
INTERNALERROR>   File "/usr/share/miniconda3/envs/test-environment/lib/python3.10/site-packages/_pytest/main.py", line 266, in wrap_session
INTERNALERROR>     config._do_configure()
INTERNALERROR>   File "/usr/share/miniconda3/envs/test-environment/lib/python3.10/site-packages/_pytest/config/__init__.py", line 1037, in _do_configure
INTERNALERROR>     self.hook.pytest_configure.call_historic(kwargs=dict(config=self))
INTERNALERROR>   File "/usr/share/miniconda3/envs/test-environment/lib/python3.10/site-packages/pluggy/_hooks.py", line 277, in call_historic
INTERNALERROR>     res = self._hookexec(self.name, self.get_hookimpls(), kwargs, False)
INTERNALERROR>   File "/usr/share/miniconda3/envs/test-environment/lib/python3.10/site-packages/pluggy/_manager.py", line 80, in _hookexec
INTERNALERROR>     return self._inner_hookexec(hook_name, methods, kwargs, firstresult)
INTERNALERROR>   File "/usr/share/miniconda3/envs/test-environment/lib/python3.10/site-packages/pluggy/_callers.py", line 60, in _multicall
INTERNALERROR>     return outcome.get_result()
INTERNALERROR>   File "/usr/share/miniconda3/envs/test-environment/lib/python3.10/site-packages/pluggy/_result.py", line 60, in get_result
INTERNALERROR>     raise ex[1].with_traceback(ex[2])
INTERNALERROR>   File "/usr/share/miniconda3/envs/test-environment/lib/python3.10/site-packages/pluggy/_callers.py", line 39, in _multicall
INTERNALERROR>     res = hook_impl.function(*args)
INTERNALERROR>   File "/usr/share/miniconda3/envs/test-environment/lib/python3.10/site-packages/xdist/plugin.py", line 192, in pytest_configure
INTERNALERROR>     from xdist.dsession import DSession
INTERNALERROR>   File "/usr/share/miniconda3/envs/test-environment/lib/python3.10/site-packages/_pytest/assertion/rewrite.py", line 168, in exec_module
INTERNALERROR>     exec(co, module.__dict__)
INTERNALERROR>   File "/usr/share/miniconda3/envs/test-environment/lib/python3.10/site-packages/xdist/dsession.py", line 5, in <module>
INTERNALERROR>     from xdist.scheduler import (
INTERNALERROR>   File "/usr/share/miniconda3/envs/test-environment/lib/python3.10/site-packages/_pytest/assertion/rewrite.py", line 168, in exec_module
INTERNALERROR>     exec(co, module.__dict__)
INTERNALERROR>   File "/usr/share/miniconda3/envs/test-environment/lib/python3.10/site-packages/xdist/scheduler/__init__.py", line 1, in <module>
INTERNALERROR>     from xdist.scheduler.each import EachScheduling  # noqa
INTERNALERROR>   File "/usr/share/miniconda3/envs/test-environment/lib/python3.10/site-packages/_pytest/assertion/rewrite.py", line 168, in exec_module
INTERNALERROR>     exec(co, module.__dict__)
INTERNALERROR>   File "/usr/share/miniconda3/envs/test-environment/lib/python3.10/site-packages/xdist/scheduler/each.py", line 1, in <module>
INTERNALERROR>     from py.log import Producer
INTERNALERROR> ModuleNotFoundError: No module named 'py.log'; 'py' is not a package

on main. For an example of this in action see this CI build

Copying my comment ( https://github.com/dask/dask/pull/9596#issuecomment-1291045452 ) here:

Maybe this is related to the recent pytest upgrade ( https://github.com/conda-forge/pytest-feedstock/pull/153 )? Perhaps we can raise a reproducer on that feedstock

Here's the upstream issue in pytest https://github.com/pytest-dev/pytest/issues/10422 / https://github.com/pytest-dev/pytest/issues/10420. Looks like this is related to pytest-benchmark not declaring a dependency (xref https://github.com/ionelmc/pytest-benchmark/pull/227) -- though I don't think we have pytest-benchmark installed in our CI environments. Folks upstream in pytest are pointing to this pytest-benchmark fix https://github.com/ionelmc/pytest-benchmark/pull/227. I'll try pinning pytest in CI to see if that works as a temporary fix.

Ah, it looks like various pytest-* packages are impacted by an upstream pytest change. In our case, I think it's pytest-xdist (xref https://github.com/pytest-dev/pytest-xdist/issues/832)

We can just install py on our CI while they work through these issues (which probably will take some time)

Yeah, I was just coming around to that. Do you think it's worth add py upstream in the pytest conda-forge recipe?

We could raise that in a feedstock issue and see what the maintainers say

Closing as fixed (xref https://github.com/dask/dask/pull/9596#issuecomment-1291094796)

With my pytest maintainer hat on: Please don't add py as hard dependency to pytest itself - the whole point of the change in pytest is to get rid of the dependency where it's not actually needed. That various plugins use py without directly declaring it as a dependency is unfortunate, but that should be fixed in those plugins (or in their package, if necessary as a workaround), and not by installing py in all pytest installs.


Added new query and criteria for correct removing of older backups

Issue #63

@bastien70
FYI according to the contributing guidelines, I'm supposed to ran the CI/test jobs locally. CI was fine, but the tests failed due to "Too Many Connections" related to the database.
<!-- An exception occurred in the driver: SQLSTATE[08004] [1040] Too many connections (500 Internal Server Error) -->'
    'version' => '1.1'
    'statusCode' => 500
    'statusText' => 'Internal Server Error'
    'charset' => 'UTF-8'
) is redirected and has header "Location" with value "/login".

/app/vendor/symfony/framework-bundle/Test/BrowserKitAssertionsTrait.php:142
/app/vendor/symfony/framework-bundle/Test/BrowserKitAssertionsTrait.php:56
/app/tests/Controller/SecurityControllerTest.php:33
/app/tests/Controller/SecurityControllerTest.php:15

Caused by
ErrorException: An exception occurred in the driver: SQLSTATE[08004] [1040] Too many connections in /app/vendor/doctrine/dbal/src/Driver/API/MySQL/ExceptionConverter.php:119
Stack trace:
#0 /app/vendor/symfony/framework-bundle/Test/BrowserKitAssertionsTrait.php(56): Symfony\Bundle\FrameworkBundle\Test\WebTestCase::assertThatForResponse(Object(PHPUnit\Framework\Constraint\LogicalAnd), '')
#1 /app/tests/Controller/SecurityControllerTest.php(33): Symfony\Bundle\FrameworkBundle\Test\WebTestCase::assertResponseRedirects('/login')#2 /app/tests/Controller/SecurityControllerTest.php(15<EMAIL_ADDRESS>'test')
#3 /app/vendor/phpunit/phpunit/src/Framework/TestCase.php(1545): App\Tests\Controller\SecurityControllerTest->testLogin()
#4 /app/vendor/phpunit/phpunit/src/Framework/TestCase.php(1151): PHPUnit\Framework\TestCase->runTest()
#5 /app/vendor/phpunit/phpunit/src/Framework/TestResult.php(726): PHPUnit\Framework\TestCase->runBare()
#6 /app/vendor/phpunit/phpunit/src/Framework/TestCase.php(903): PHPUnit\Framework\TestResult->run(Object(App\Tests\Controller\SecurityControllerTest))
#7 /app/vendor/phpunit/phpunit/src/Framework/TestSuite.php(677): PHPUnit\Framework\TestCase->run(Object(PHPUnit\Framework\TestResult))
#8 /app/vendor/phpunit/phpunit/src/Framework/TestSuite.php(677): PHPUnit\Framework\TestSuite->run(Object(PHPUnit\Framework\TestResult))
#9 /app/vendor/phpunit/phpunit/src/Framework/TestSuite.php(677): PHPUnit\Framework\TestSuite->run(Object(PHPUnit\Framework\TestResult))
#10 /app/vendor/phpunit/phpunit/src/TextUI/TestRunner.php(673): PHPUnit\Framework\TestSuite->run(Object(PHPUnit\Framework\TestResult))
#11 /app/vendor/phpunit/phpunit/src/TextUI/Command.php(143): PHPUnit\TextUI\TestRunner->run(Object(PHPUnit\Framework\TestSuite), Array, Array, true)
#12 /app/vendor/phpunit/phpunit/src/TextUI/Command.php(96): PHPUnit\TextUI\Command->run(Array, true)
#13 /app/vendor/phpunit/phpunit/phpunit(98): PHPUnit\TextUI\Command::main()
#14 /app/vendor/bin/phpunit(123): include('/app/vendor/php...')
#15 {main}
ERRORS!

While this particular issue will probably not occur in the CI (for now), I think this has to do with the fact that I dockerized the app and added the image to another app already (connect to same MySQL service with max 5 active connections, of which only 2 were active without running tests).
So after some searching, I've found that if I added processIsolation = "true" to the phpunit.xml.dist, it stopped giving these errors (it now just fails on 1 test case unrelated to this change). I'm definitely not that familiar with unit testing, so I have no idea what the impact of processIsolation is, but apparently setting it to true works. Is this something that could be changed?

Oh sorry I didn't see your comment.
Well I guess that shouldn't be a problem. @jmsche  ?

Codecov Report

Merging #66 (09ae1ab) into main (0183053) will increase coverage by 0.31%.
The diff coverage is 89.28%.

@@             Coverage Diff              @@
##               main      #66      +/-   ##
============================================
+ Coverage     85.24%   85.56%   +0.31%
- Complexity      278      280       +2
============================================
  Files            43       43
  Lines           949      970      +21
============================================
+ Hits            809      830      +21
  Misses          140      140

Impacted Files
Coverage Δ

src/Entity/Database.php
100.00% <ø> (ø)

src/Repository/BackupRepository.php
88.23% <86.66%> (-11.77%)
:arrow_down:

src/Service/BackupService.php
62.50% <92.30%> (+7.32%)
: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 0183053...09ae1ab. Read the comment docs.

Okay for me for the query. For last changes, I let jmsche take care of it


Large POST requests (e.g. KML data) are being sent via query string (via Hurley)

I'm using the client to fire off SQL clients to the Fusion Tables API.  Although the client does a POST via hurley, the entire query goes through the query string in the URL, rather than a POST body.
As the SQL query can get rather long (i'm inserting KML data), the URL limit of 2K is reached and a bad request occurs.
This is a bit of an ugly patch I quickly made that ensures this request uses a body rather than query string, within lib/google/apis/core/http_command.rb
Hope it makes sense and is helpful.
Since Hurley will likely be dropped - worth checking on native HTTP client too.  Plus I'm not sure if other Google APIs require perhaps a split of query string and body params, so this could be expanded further.
`def execute_once(client)
body.rewind if body.respond_to?(:rewind)
begin
logger.debug { sprintf('Sending HTTP %s %s', method, url) }
        response = nil
        if method.to_s == 'post'
          uri = URI.parse(url)
          # get the url without the query string
          new_url = uri.to_s.split("?")[0]
          # query string to be used as POST body
          new_body = uri.query
          # set the content-type to ensure valid form post
          form_content_type = 'application/x-www-form-urlencoded; charset=UTF-8'
          # send the data
          response = client.post(new_url, new_body, form_content_type) do |req|
            apply_request_options(req)
          end
        else
          response = client.send(method, url, body) do |req|
            # Temporary workaround for Hurley bug where the connection preference
            # is ignored and it uses nested anyway
            req.url.query_class = Hurley::Query::Flat
            query.each do | k, v|
              req.url.query[k] = normalize_query_value(v)
            end
            # End workaround
            apply_request_options(req)
          end
        end

        logger.debug { response.status_code }
        logger.debug { response.inspect }
        response = process_response(response.status_code, response.header, response.body)
        success(response)
      rescue => e
        logger.debug { sprintf('Caught error %s', e) }
        error(e, rethrow: true)
      end
    end`

Have to think about how to do this in a way that is safe for all APIs.
I think it is OK to do iff:

The method is PUT/POST and
There is no other body type specified (e.g. no JSON payload)

Will take a look.


Nested routes

Just wanted to say it's a nice little library you have here, very well written.
Wondered if you've got any plans for allowing nested routes to be defined in different files? E.g if you had a route of GET /user it'd be nice if you could define that in the parent router, and instead of running the function to handle that route, it instead points it to a router in another file. Then in that file you could define child routes, E.g GET :id. This would then get setup as GET /users/:id

Hey,
This is definitely something I've been meaning to add but haven't gotten around to yet.
Thanks for letting me know that you're interested in this feature, I'll make sure to prioritize it :)

reminder for later but this is getting close I think it can be a bit more elegant

function getRouteMatcher(path) {
  const segments = path.split('/');
  const regexSegments = segments.map(segment => (segment.startsWith(':') ? '([^/]+)' : segment));
  const regexString = `^${regexSegments.join('\\/')}$`;
  return new RegExp(regexString);
}

function matchRoute(uri, path) {
  const routeMatcher = getRouteMatcher(path);
  const match = uri.match(routeMatcher);

  if (!match) return { matched: false };

  const params = {};
  path.split('/').forEach((segment, i) => {
    if (segment.startsWith(':'))
    console.log(segment, match, i)
    //thre is a bug here with /:param1/:param2
    params[segment.slice(1)] = match[i-1];
  });

  return { matched: true, params };
}

//https://codesandbox.io/s/stoic-austin-sx84zx?file=/src/index.mjs

https://codesandbox.io/s/stoic-austin-sx84zx?file=/src/index.mjs


bugfix: remove search app go button

Coverage decreased (-0.06%) to 48.465% when pulling 1b628e19afb2135e9cb9981f9dd5b2c65a8f2ccc on lepdou:bugfix_search into 9a22de999f5c00838357e2ad7e562e5bd9932f1c on ctripcorp:master.

Current coverage is 45.37% (diff: 100%)

Merging #447 into master will decrease coverage by 0.03%

@@             master       #447   diff @@
==========================================
  Files           257        257
  Lines          6188       6188
  Methods           0          0
  Messages          0          0
  Branches        709        709
==========================================
- Hits           2810       2808     -2
- Misses         3186       3190     +4
+ Partials        192        190     -2

Powered by Codecov. Last update 9a22de9...1b628e1


Multisignature support for bitcoin cash

Creating new wallet and import from backup/seed.

Hey Quark-Fusion,
First off, I want to apologize for the lack of communication on this, I am currently working through all of our GitHub issues. We have added Multisignature support in one of the Bitcoin.com Wallet releases.
You can find more information here: https://www.bitcoin.com/guides/how-to-create-a-shared-bitcoin-wallet
I appreciate you submitting this issue and if you experience any others, feel free to reach out.
Regards,
Ornn.


How to extract a graph_def from TFHub saved_model (e.g. mobilenet_v2/feature_vector)

There are several TFHub models, in saved_model format,  that would be useful to convert into a graph_def using standard TF2 API.
For example, the model here: https://tfhub.dev/google/tf2-preview/mobilenet_v2/feature_vector/4
The snippet below should be able to extract out concrete function into a graph_def, convert it into a graph, and then print out all the node names. However, it looks tricky to get extract out the concrete function (because there is no signature of serving_default in the serve tag).
What's the best way to get the graph_def from this saved_model?
import tensorflow as tf
from tensorflow.python.framework.convert_to_constants import convert_variables_to_constants_v2

model_path = r'd:\models_tfhub\tf2-preview_mobilenet_v2_feature_vector'

imported = tf.saved_model.load(model_path, tags=[['serve']])  # pylint: disable=no-value-for-parameter
concrete_func = imported.signatures['serving_default']
#concrete_func = imported.signatures['__saved_model_init_op']
frozen_func = convert_variables_to_constants_v2(concrete_func, lower_control_flow=False)
graph_def = frozen_func.graph.as_graph_def(add_shapes=True)
with tf.Graph().as_default() as inferred_graph:
    tf.import_graph_def(graph_def, name="")

nodes = inferred_graph.get_operations()
for n in nodes:
    print (n.name)

Hi @jignparm,
one way to get a concrete_function out of tf.saved_model.load would be:
concrete_func = imported.call.get_concrete_function(...)
https://tfhub.dev/google/tf2-preview/mobilenet_v2/feature_vector/4 specifically has 4 concrete functions - you can use imported.__call__.concrete_functions to inspect them.
The rest of the sample code that you provided should work. Let me know if you run into any problems.

@maringeo, thanks for the valuable insight! I am able to make the code snippet above work using
concrete_func = imported.__call__.get_concrete_function(tensor_spec.TensorSpec([None, None, None, 3]))
A couple of other questions I had were:

If a saved_model contains  signature_def['serving_default'] (from which we can extract a concrete function ) as well as some additional concrete functions under  imported.__call__.concrete_functions ,  is there any preference regarding which concrete function is the best one to use for inference purposes?

I noticed there are usually 4 functions under  imported.__call__.concrete_functions. Is there way to know which one is  the best one inference purposes?

It'd be great if there's a typical pattern to extract the inference graphs (don't care too much about training/fine-tuning).

Sorry for the delayed response.
All concrete functions are derived (traced) from the same tf.function - see Tensorflow concrete function guide.
So in the example of https://tfhub.dev/google/tf2-preview/mobilenet_v2/feature_vector/4 with tags=[['serve']], the 4 concrete functions are:
call_fn(inputs, training = True, return_endpoints = True, batch_norm_momentum)
call_fn(inputs, training = True, return_endpoints = False, batch_norm_momentum)
call_fn(inputs, training = False, return_endpoints = True, batch_norm_momentum)
call_fn(inputs, training = False, return_endpoints = False, batch_norm_momentum)

and they were traced from a function like:
@tf.function
def call_fn(inputs, training, return_endpoints, batch_norm_momentum):
  # actual code

From Tensorflow 2.3 onward there is a convenient way to inspect the signatures of concrete functions - guide.
In general, you don't need to explicitly call a given concrete function - you just need to call the callable with the correct parameters for you use-case (for example with training=False during inference and training=True during training). See the TF Hub SavedModelV2 guide for more details on how to call the TF 2 SavedModels.


implement grouping sets, cubes, and rollups

Is your feature request related to a problem or challenge? Please describe what you are trying to do.
a challenge to design and implement grouping sets, cubes, and rollups.
Describe the solution you'd like
similar to https://www.postgresql.org/docs/current/queries-table-expressions.html#QUERIES-GROUPING-SETS
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
this would be a rather large piece of work so ideally can be split up into three subsets:

[x] update sqlparser https://github.com/sqlparser-rs/sqlparser-rs/pull/366
[x] grouping sets
[x] cubes
[x] rollups

I guess a modification to sqlparser is also needed?

FYI @thinkharderdev  bashed this out in https://github.com/apache/arrow-datafusion/pull/2716 🥇


[SPARK-7741] [STREAMING] Added sparkContext.clean at missing places

These missing cleaners lead to capturing unnecessary objects in closures, especially when using a spark streaming in spark-shell.

@andrewor14 Could you please take a look?

Merged build triggered.

Merged build started.

Test build #33096 has started for   PR 6268 at commit c1dc4cf.

@tdas Most of the changes are actually not required, because they eventually get cleaned later through other methods. We established this rule in #5787.
So the only places that are actually required are: filter, combineByKey, mapValues and flatMapValues.
Additionally there are a few calls in updateStateByKey that need to be cleaned. In general, the following pattern needs cleaning:
def somePublicMethod(func: () => Int): Unit = {
  val cleanedF = sc.clean(func)
  new SomeRDD(this, (unused: Int) => cleanedF())
}

Test build #33096 has finished for   PR 6268 at commit c1dc4cf.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33096/
Test PASSed.

@andrewor14  I am closing this PR, yours is far better :)


returns null for http://vikram_tiwari.com

similar to https://github.com/oncletom/tld.js/issues/117

Hi @VikramTiwari,
Thank you for your feedback!
In this case, this is because currently the _ is not considered valid when found inside a domain. Related work: #122
Hopefully we will soon have a better behavior and a way to customize it.

@remusao You are not merging #122 into master for now?

PR #128 Looks great.


Change IP

The IP address of one of my TV's has changed how can I update it in the configuration?

If you configure new device (with new ip) for same TV it will automatically update ip of existing one and abort the flow.

Ah perfect good to know


feat: Deprecate Indy credentials and add support for Anoncreds

Currently, we have Indy based credentials that are made default for issuance and verification.
To do:

[x] Improve DTO level formating by leveraging APIExtraModels

[̶ ]̶ C̶h̶e̶c̶k̶ i̶f̶ w̶e̶ c̶a̶n̶ m̶i̶g̶r̶a̶t̶e̶ f̶r̶o̶m̶ I̶n̶d̶y̶ c̶r̶e̶d̶e̶n̶t̶i̶a̶l̶s̶ t̶o̶ A̶n̶o̶n̶c̶r̶e̶d̶s̶

[x] Issuance

[x] Add Anoncreds as an additional type
[x] Remove credentialType from Query param and make it required in Body
[x] Update credentialFormats in Interface
[x] Update the default credential type from Indy to Anoncreds

[x] Issuance with connection
[x] OOB Issuance
[x] OOB Issuance with email
[x] Bulk issuance change, if any

[x] Change in IssuanceDTO to accept a universal 'credentialFormats' instead of previous components required for issuing different types of credentials

[x] Issuance with connection
[x] OOB Issuance
[x] OOB Issuance with email
[x] Bulk issuance change, if any

[x] Verification

[x] Add Anoncreds as an additional type.
[x] Add Indy 'CredentialFormats' type
[x] Remove presentationType from Query param and make it required in Body
[x] Update credentialFormats in Interface
[x] Update the default presentation type from Indy to Anoncreds

[x] Verification with connection
[x] Verification OOB

[x] Change in VerificationDTO to accept a universal 'credentialFormats' instead of previous components required for issuing different types of credentials.

[x] Verification with connection
[x] Verification OOB

Breaking change

Can have an impact on required attributes for issuance and verification. The impact will be on backend considering the change in credentialFormats.

Solution

Have validations on attributes on DTO level for credentialFormats to not allow issuance in case of no attributes.
Can pass an optional array of required attributes, to validate.

Check if we can migrate from Indy credentials to Anoncreds

The task is done, but was not merged as it breaked other flows.
We need to create a separate task for integrating this


x/sys/unix: TIPC_WAIT_FOREVER isn't usable in TIPCSubscr.Timeout

What version of Go are you using (go version)?

$ go version
go version go1.13rc2 linux/amd64

Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/mischief/.cache/go-build"
GOENV="/home/mischief/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/mischief/code/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/home/mischief/src/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/home/mischief/src/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build480716661=/tmp/go-build -gno-record-gcc-switches"

What did you do?
package main

import (
	"fmt"

	"golang.org/x/sys/unix"
)

func main() {
	seq := unix.TIPCServiceRange{
		Type:  999,
		Lower: 0,
		Upper: ^uint32(0),
	}
	sub := &unix.TIPCSubscr{
		Seq:     seq,
		Timeout: unix.TIPC_WAIT_FOREVER,
		Filter:  unix.TIPC_SUB_PORTS,
	}
	fmt.Println(sub)
}

What did you expect to see?
the subscription is printed.
What did you see instead?
./f.go:17:3: constant -1 overflows uint32

TIPC_WAIT_FOREVER is a sentinel value to make a subscription never time out (see here).
its value is currently const TIPC_WAIT_FOREVER = -0x1. the kernel headers define it as a macro ((~0)). however, the TIPCSubscr.Timeout field is a uint32, so assignment doesn't work.

cc @mdlayher


[APPLE] Implement Apple Maps Support

[x] Implement Authentication
[x] Add Pano URL
[x] Implement into CLI
[ ] Convert Coordinates to Panorama ID
[ ] Stitch Panorama correctly
[ ] Obtain metadata
[ ] Figure out the first five paths

Panoramas aren't stitching correctly, so that's another one for the list

Finally managed to stitch the (first four) tiles correctly

Now that there's an online tool to preview Look Around Panoramas with their respectful Panorama ID & Regional ID, I'm gonna add the option to download the panorama with its respectful ID
and also credit skzk because he's the one whos done all of this work lol - i just made it compatible w my program


Add support for listening to parent el scroll for grids

Dear past self, is this not why you added this method?

I'd say this ones done already. That method makes it pretty straight forward to add a parent listener. :shipit:

It's weird because I opened this after the latest releases, which also include this method. Ah well, gonna close for now.