Create an example with a VCDM

I found it hard to understand the relationship between VC's and the spec. Specifically, it's not clear to me how to go from VC (as in application/vc+ld+json) to SD-JWT VC, nor the other way.

The specification does not use the W3C VCDM. A note was added to the spec. We might add a transformation algorithm from SD-JWT VC to W3C VCDM in the future if needed. This also depends on the implementation of the Miami resolution.
I'll rename the issue to make it clear that this is about a transformation algorithm and we will revisit in the future.

Transforming syntax between w3c vcdm payload and sd-jwt vc payload is probably not too complicated. it is more about mapping between the claims (i.e. issuer -> iss; issuanceData -> iat, etc.) and handling when representation of a claim is different (i.e. when issuer is an object in vcdm but is a string in sd-jwt vc, etc.)
the bigger problem is semantics. sd-jwt vc -> vcdm might work by using default context thanks to the @vocab value there that will tell json-ld parser to treat all undefined terms as #issuerDefined. not sure how much vcdm -> sd-jwt vc is possible because sd-jwt vc does not have @context value by definition. so in any case, semantics ie meaning of varying claims will probably need to be agreed out of band.

Thoughts?

I really like the fact that SD JWT VC is not related to the W3C VC DM, or any other format.
This independence allows this specification to present SD JWT VC as a new clean format.
I really see no point in adding mapping rules or describing approaches to map between formats.

I think, we had a lot of discussions on this and nobody argued for having a transformation algorithm being defined in this specification. I suggest to close this issue after 1 week unless anybody feels very strongly.


refactor: guardIESVGBug function

What kind of change does this PR introduce? (check at least one)

[ ] Bugfix
[ ] Feature
[ ] Code style update
[x] Refactor
[ ] Build-related changes
[ ] Other, please describe:

Does this PR introduce a breaking change? (check one)

[x] Yes
[ ] No

If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:

[ ] It's submitted to the main branch for v2.x (or to a previous version branch)
[ ] When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)
[x] All tests are passing: https://github.com/vuejs/vue/blob/dev/.github/CONTRIBUTING.md#development-setup
[ ] New/updated tests are included

If adding a new feature, the PR's description includes:

[ ] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:

Thank you! I think the current code is readable enough that refactoring it into two loops (filter + map) doesn't seem to pay off.


Change backend from SEAL to Lattigo

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Closed this PR. These changes are now on the lattigo-backend branch.


nomad: 1.0.1 -> 1.0.2

Motivation for this change
Upgrade nomad to the latest release
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

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

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 109462 run on x86_64-darwin 1

1 package built:

nomad_1_0

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 109462 run on x86_64-darwin 1

1 package built:

nomad_1_0

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 109462 run on x86_64-linux 1

1 package built:

nomad_1_0

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 109462 run on x86_64-linux 1

1 package built:

nomad_1_0


Add Logging to all API requests

Description
Add Logging to all API requests
Todos

[ ] Fixing tornado IP issue with Nginx
[ ] Test on a real server with non localhost
[ ] decide on what to save from request.body
[ ] Add DB migrations

Status

[ ] Changelog updated
[ ] Ready to go

I added an issue in geoip2 to request adding it to conda-forge. Currently, it's available in activisiongamescience conda channel.

I don't feel too comfortable adding a 60MB file to Fractal. Can we make this an optional standalone dependance? I don't imagine too many people will want this kind of data if the IP is stored.

Yes, sure it can be optional.


sql: remove old database privilege inheritance

Exalate commented:
https://github.com/cockroachdb/cockroach/pull/79049 --- Release note (sql change): Previously, any privileges on a database that would be inherited (copied down) to tables/schemas if a table/schema is created in that database.  For example, GRANT ALL ON DATABASE TEST TO foo CREATE TABLE test.t() would result in foo having ALL on the table.  This is no longer the case as users should rely on default privileges instead. They can achieve the same behaviour by doing USE test; ALTER DEFAULT PRIVILEGES GRANT ALL ON TABLES TO foo;
Jira Issue: DOC-3192

I think changing the docs around this is pretty important; I just got bit by this and it seems a major change that happened in 22.2 I think.
https://www.cockroachlabs.com/docs/v22.2/grant incorrectly says

When a role or user is granted privileges for a database, new tables created in the database will inherit the privileges

There might be many other mentions of this inheritance; I'm not sure.


Issue with Gulp Nunjucks Renderer for Production

After adding markdown functionality, I’ve hit an issue when running the prod task.
This fails and as a result, static HTML is not being generated for production.

Fixed.


Disentangling events for multiple rendering backends

I recently tried to replace the vispy canvas with a pygfx canvas to see what breaks. I came to the conclusion that in order to move along with the project of having multiplke rendering backends, the big elephant in the room is the event system.
The main issue is that we depend on vispy to initially handle events on the canvas, and only after that we take care of them. To set ourselves up for success on integrating pygfx, we need to make sure that napari is in control of the events, and only later passes them to vispy/pygfx as needed. I think the best way to go about this is to replace the event system with psygnal.
We briefly talked about it at the community meeting, and concluded I should open this issue to see who's interested in working on this, and to gather some discussion on if/how to go about this!
cc @napari/core-devs.

Dropping this here to investigate later: https://github.com/glue-viz/glue-vispy-viewers

We currently depend on vispy to calculate most of the camera movements. Maybe such a change will require more of this type of calculation on our side.

Makes sense :/

Did you know how mouse and key events work in pygfx?

No, I got stopped by the above issue before diving deeper.

@brisvag I suggest to not try to replace vispy, but create own docked widget with pygfx. Then we could have two viewers at the same time and compare them.
Also, there will be not problem with reconnecting events. Only some shortcuts will not work.

Then we could have two viewers at the same time and compare them.

I love this idea!


feature(argus): New Failure Statuses

This commit adds two new failure statuses (to be set manually for now) -
FAILED-BUG and FAILED-INFRA. The old FAILED status is now considered a
run failure, while other two fill in when the job fails to either
infrastructure issues (e.g. spot instance not available) (FAILED-INFRA)
or when the job fails due to testing framework bug (FAILED BUG).
Fixes #316

Demo:

Thanks - this is what we need - we'll be able to sort out where we are with infra (test, framework, cloud env, Jenkins) issues vs real failures.

I don't want this status

I don't want this status

@roydahan - please provide constructive feedback. We have today a critical issue, where we can't easily understand if failures were caused by infra or real issues. This has two implications:

We don't know the version's quality
We don't know if we improve the infra

We need a good solution here. This was an easy one.

I already commented on the issue.
There is no such a thing infra issue, if there is one, we fix and/or rerun.
We didn't accept this status long ago because we didn't want people to dismiss runs as infra issue and leave them as such.
We leave them as failed "in progress", fix them and re run them.
If you care about the current status for statistics, you can ask to mark these as Abort for now.

I already commented on the issue. There is no such a thing infra issue, if there is one, we fix and/or rerun.
We didn't accept this status long ago because we didn't want people to dismiss runs as infra issue and leave them as such. We leave them as failed "in progress", fix them and re run them. If you care about the current status for statistics, you can ask to mark these as Abort for now.

So we'll abuse 'abort' for this? How would we know we've improved our infra (resiliency to failures, for example) over time?

So we'll abuse 'abort' for this? How would we know we've improved our infra (resiliency to failures, for example) over time?

Tell me what do you call infra failure and I'll tell you if we can improve that.

spot termination isn't infra failure, it's abort.
And we cannot improve that.

Jenkins failure isn't infra failure, it's abort and we improved that to the maximum.

What else failures do you see that you call them infra failures?

So we'll abuse 'abort' for this? How would we know we've improved our infra (resiliency to failures, for example) over time?

Tell me what do you call infra failure and I'll tell you if we can improve that.

spot termination isn't infra failure, it's abort.
And we cannot improve that.
Jenkins failure isn't infra failure, it's abort and we improved that to the maximum.

What else failures do you see that you call them infra failures?

SCT issue - random example from today - https://github.com/scylladb/scylla-cluster-tests/pull/6985 )
Another - dtest this time - https://github.com/scylladb/scylla-dtest/pull/3791
Any failure that is not either a new or a known bug, I classify as infra - cloud, test framework, tests themselves.

SCT issue - random example from today - scylladb/scylla-cluster-tests#6985 )

This is exactly the reason why we don't need "Failed - infra".
It's not an infra failure, it's a change in scylla that now doesn't support something, one should fix it and re-run.

Another - dtest this time - scylladb/scylla-dtest#3791
I don't see how this one is related to the discussion here.
This is an improvement to dtest hoping to workaround environmental issue we don't have control with.
It's not part of Argus anyway.

Any failure that is not either a new or a known bug, I classify as infra - cloud, test framework, tests themselves.
You cannot count all these as "Failed - Infra" and hope to get improve, since we expect everyone to contribute tests to SCT, and once we do it we may have more and more SCT issues, so you won't improve, you'll degrade.
Also, not every issue in SCT should mark the test as "Failed - Infra", some are just issue in one of the nemesis or something like that, but the test continues and should be investigated.
Hece, we use the "linked" issues, to specify also SCT issues. but the responsibility of the "job assignee" is to get the job to completion and  till then, it's "Failed" (In progress").

SCT issue - random example from today - scylladb/scylla-cluster-tests#6985 )

This is exactly the reason why we don't need "Failed - infra". It's not an infra failure, it's a change in scylla that now doesn't support something, one should fix it and re-run.

It's a change that literally took place months ago - and most tests were adjusted already.

Another - dtest this time - scylladb/scylla-dtest#3791

I don't see how this one is related to the discussion here. This is an improvement to dtest hoping to workaround environmental issue we don't have control with. It's not part of Argus anyway.

It's not part of argus, it's part of the infra we have to reliably run tests and get results for the quality of ScyllaDB.

Any failure that is not either a new or a known bug, I classify as infra - cloud, test framework, tests themselves.

You cannot count all these as "Failed - Infra" and hope to get improve, since we expect everyone to contribute tests to SCT, and once we do it we may have more and more SCT issues, so you won't improve, you'll degrade. Also, not every issue in SCT should mark the test as "Failed - Infra", some are just issue in one of the nemesis or something like that, but the test continues and should be investigated. Hece, we use the "linked" issues, to specify also SCT issues. but the responsibility of the "job assignee" is to get the job to completion and till then, it's "Failed" (In progress").

Linking SCT issues to test that we'll make as 'Fail-Infra' doesn't make anything go away - we would like to fix them just as much and reduce them. This is why they are marked as a failure, and we should have a GH issue for root cause and fix.

SCT issue - random example from today - scylladb/scylla-cluster-tests#6985 )

This is exactly the reason why we don't need "Failed - infra". It's not an infra failure, it's a change in scylla that now doesn't support something, one should fix it and re-run.

It's a change that literally took place months ago - and most tests were adjusted already.

Right, and these tests like many others haven't run since.
And once someone bump into it, he shouldn't mark it as "Fail - infra" which is an easy way out for him.
One should understand the failure, send the fix and re-run. till then, it's "Failed".
We as release maintainers shouldn't care why it failed until there is a scylla issue attached to it.
Hence, I insisted in the past and still insist to not allow "easy way out statuses" like "Failed - Infra".

Another - dtest this time - scylladb/scylla-dtest#3791

I don't see how this one is related to the discussion here. This is an improvement to dtest hoping to workaround environmental issue we don't have control with. It's not part of Argus anyway.

It's not part of argus, it's part of the infra we have to reliably run tests and get results for the quality of ScyllaDB.

Any failure that is not either a new or a known bug, I classify as infra - cloud, test framework, tests themselves.

You cannot count all these as "Failed - Infra" and hope to get improve, since we expect everyone to contribute tests to SCT, and once we do it we may have more and more SCT issues, so you won't improve, you'll degrade. Also, not every issue in SCT should mark the test as "Failed - Infra", some are just issue in one of the nemesis or something like that, but the test continues and should be investigated. Hece, we use the "linked" issues, to specify also SCT issues. but the responsibility of the "job assignee" is to get the job to completion and till then, it's "Failed" (In progress").

Linking SCT issues to test that we'll make as 'Fail-Infra' doesn't make anything go away - we would like to fix them just as much and reduce them. This is why they are marked as a failure, and we should have a GH issue for root cause and fix.

Right, it doesn't make things go away, hence we want it to be "Failed" and want people to still hold the responsiblity to make it "Pass" or have a known scylladb issue on it.

SCT issue - random example from today - scylladb/scylla-cluster-tests#6985 )

This is exactly the reason why we don't need "Failed - infra". It's not an infra failure, it's a change in scylla that now doesn't support something, one should fix it and re-run.

It's a change that literally took place months ago - and most tests were adjusted already.

Right, and these tests like many others haven't run since. And once someone bump into it, he shouldn't mark it as "Fail - infra" which is an easy way out for him. One should understand the failure, send the fix and re-run. till then, it's "Failed". We as release maintainers shouldn't care why it failed until there is a scylla issue attached to it. Hence, I insisted in the past and still insist to not allow "easy way out statuses" like "Failed - Infra".

Why is it any easier than marking it as failed as it is today? Why wouldn't the engineer file an issue, fix the issue, re-run the test?

Another - dtest this time - scylladb/scylla-dtest#3791

I don't see how this one is related to the discussion here. This is an improvement to dtest hoping to workaround environmental issue we don't have control with. It's not part of Argus anyway.

It's not part of argus, it's part of the infra we have to reliably run tests and get results for the quality of ScyllaDB.

Any failure that is not either a new or a known bug, I classify as infra - cloud, test framework, tests themselves.

You cannot count all these as "Failed - Infra" and hope to get improve, since we expect everyone to contribute tests to SCT, and once we do it we may have more and more SCT issues, so you won't improve, you'll degrade. Also, not every issue in SCT should mark the test as "Failed - Infra", some are just issue in one of the nemesis or something like that, but the test continues and should be investigated. Hece, we use the "linked" issues, to specify also SCT issues. but the responsibility of the "job assignee" is to get the job to completion and till then, it's "Failed" (In progress").

Linking SCT issues to test that we'll make as 'Fail-Infra' doesn't make anything go away - we would like to fix them just as much and reduce them. This is why they are marked as a failure, and we should have a GH issue for root cause and fix.

Right, it doesn't make things go away, hence we want it to be "Failed" and want people to still hold the responsiblity to make it "Pass" or have a known scylladb issue on it.

It completely hides the quality of Scylla. If those were rare issues - fine - but they aren't. The signal to noise in our tests isn't good.

SCT issue - random example from today - scylladb/scylla-cluster-tests#6985 )

This is exactly the reason why we don't need "Failed - infra". It's not an infra failure, it's a change in scylla that now doesn't support something, one should fix it and re-run.

It's a change that literally took place months ago - and most tests were adjusted already.

Right, and these tests like many others haven't run since. And once someone bump into it, he shouldn't mark it as "Fail - infra" which is an easy way out for him. One should understand the failure, send the fix and re-run. till then, it's "Failed". We as release maintainers shouldn't care why it failed until there is a scylla issue attached to it. Hence, I insisted in the past and still insist to not allow "easy way out statuses" like "Failed - Infra".

Why is it any easier than marking it as failed as it is today? Why wouldn't the engineer file an issue, fix the issue, re-run the test?

Because when doing so, it kinds of remove the responsibility from the "reporter" / the "assignee" which now thinks, it's an infra problem, not my problem.

This assumes we don't trust our engineers to do their job. It's just as re-triggering CI without looking at why it failed of filing an issue on the failure. It's something that should be handled elsewhere.

Another - dtest this time - scylladb/scylla-dtest#3791

I don't see how this one is related to the discussion here. This is an improvement to dtest hoping to workaround environmental issue we don't have control with. It's not part of Argus anyway.

It's not part of argus, it's part of the infra we have to reliably run tests and get results for the quality of ScyllaDB.

Any failure that is not either a new or a known bug, I classify as infra - cloud, test framework, tests themselves.

You cannot count all these as "Failed - Infra" and hope to get improve, since we expect everyone to contribute tests to SCT, and once we do it we may have more and more SCT issues, so you won't improve, you'll degrade. Also, not every issue in SCT should mark the test as "Failed - Infra", some are just issue in one of the nemesis or something like that, but the test continues and should be investigated. Hece, we use the "linked" issues, to specify also SCT issues. but the responsibility of the "job assignee" is to get the job to completion and till then, it's "Failed" (In progress").

Linking SCT issues to test that we'll make as 'Fail-Infra' doesn't make anything go away - we would like to fix them just as much and reduce them. This is why they are marked as a failure, and we should have a GH issue for root cause and fix.

Right, it doesn't make things go away, hence we want it to be "Failed" and want people to still hold the responsiblity to make it "Pass" or have a known scylladb issue on it.

It completely hides the quality of Scylla. If those were rare issues - fine - but they aren't. The signal to noise in our tests isn't good.

I disagree, I think that you misinterpret some of the failures considering them as "Infra" issue. For now in 2024.1, there are 7 failures that are marked with SCT issue. 3 of them are related to the kMS change one is (6982 & 6893 & 6959) 2 of either test issue (not infra) or not clear enough if it's a real scylla issue or not (6842 & 5825) 1 of them is people running a job without a scylla version or scylla image (6893) 1 is a bad configuration of monitor instance type that scylla stopped supporting.

There were many more in 5.4. We just did not investigate (yet) enough on 2024.1
Anyway, my experience so far has been that we simply have too many infra issues.
The example of running a job without a scylla version or image - the Jenkins job doesn't have the description that a field is mandatory, for example. Even the documentation of the variables could have helped here.
Not to mention we could have added a validator.

@mykaul @roydahan Reworked, now includes only one new status - Test Error
Demo:

Darker shade of red for it.

@roydahan

How about this one then?


Use into() instead of casting to c_ulong because of different types in some targets

For example, in x86_64-unknown-linux-musl, ioctl takes c_int. It is better to use into() to work around this issue than using as c_ulong.
https://rust-lang.github.io/libc/x86_64-unknown-linux-musl/libc/fn.ioctl.html
pub unsafe extern "C" fn ioctl(fd: c_int, request: c_int, ...) -> c_int

I was using into() but a warning was generated by clippy or/and rustc on macos and/or linux platform so I made this change:
https://github.com/kkawakam/rustyline/commit/cb056d3a344f5a5642c7fc3932abb65337db9368#diff-0655ced7de6892bafa1f0000619c718eR35
So I am not sure that

It is better to use into() to work around this issue than using as c_ulong
...

Currently, it fails to compile on musl. Therefore, at least it's better than warning because of a bug in libc.

Thanks.
I will fix the warning with an #[allow(???)]...


fix:Order blocks in sidebar doesn't respect layout restrictions: requ…

[x] I signed and returned the Plone Contributor Agreement, and received and accepted an invitation to join a team in the Plone GitHub organization.
[x] I verified there aren't other open pull requests for the same change.
[x] I followed the guidelines in Contributing to Volto.
[x] I succesfully ran code linting checks on my changes locally.
[x] I succesfully ran unit tests on my changes locally.
[x] I succesfully ran acceptance tests on my changes locally.
[x] If needed, I added new tests for my changes.
[x] If needed, I added documentation for my changes, either in the Storybook or narrative documentation.
[x] I included a change log entry in my commits.

fixed : Order blocks in sidebar doesn't respect layout restrictions: required and fixed position

I added the checks to display the delete block and drag block button according to values set like fixed and required.
After my change:
https://github.com/user-attachments/assets/d40e9138-c798-4ba9-ab1c-74b8e26599b8
Closes #6481

@plone/volto-team I have made the appropriate changes to fix the issue and It works as wanted please If you can review this PR.

@alihamza1221 We had the yearly Plone Conference Last week in Brasilia, BR, so most of our community members who are volunteers in this project were very busy with preparing, travelling and attending. It could therefore take a while before this is reviewed, but it will probably get on the next Volto Team meeting.
As @sneridagh loves the new sidebar ordering he'll want improvements for that added asap ;-)   (teasing him)


coverage3 is used but not required for dev build

In #297, coverage testing was introduced. In the cmake it uses "coverage3",
https://github.com/QISKit/qiskit-sdk-py/blob/cd1b1067deffe645323d6e4d89f1881e2f55cfce/cmake/code-qa.cmake#L34
but this is not part of the requirements:
https://github.com/QISKit/qiskit-sdk-py/blob/cd1b1067deffe645323d6e4d89f1881e2f55cfce/requirements-dev.txt#L6
Consequently, my build from source breaks.
Expected Behavior

Current Behavior

Possible Solution

Steps to Reproduce (for bugs)

Context

Your Environment

Version used:
Environment name and version (e.g. Python 3.6.1):
Operating System and version:

@ajavadia , can you elaborate a bit? Do you mean that coverage3 (the binary) is not provided when you pip install coverage (the package)? If so, can you provide more info about your installation - the wheels for Python 3 seem to have an alias for coverage3 in most cases:
[console_scripts]
coverage = coverage.cmdline:main
coverage-3.6 = coverage.cmdline:main
coverage3 = coverage.cmdline:main

And the docs seem to point in that direction as well:

When you install coverage.py, a command-line script simply called coverage is placed in your Python scripts directory. To help with multi-version installs, it will also create either a coverage2 or coverage3 alias, and a coverage-X.Y alias, depending on the version of Python you’re using. For example, when installing on Python 2.7, you will be able to use coverage, coverage2, or coverage-2.7 on the command line.

Hi @diego-plan9, thanks. I think the problem was with the pip version I was using on the new linux environment I was testing on. It is fixed now.


On "Press" Page, Add New GovTech Story at the Top

May 27, 2015 -- "Free Law Founders Make Strides for Open Government"
Link: http://www.govtech.com/data/Free-Law-Founders-Make-Strides-for-Open-Government.html

For things this small, feel free to make the changes yourself directly, it's just as quick as adding an issue ticket:
https://github.com/opengovfoundation/free-law-founders-site/edit/gh-pages/press.md
:+1:


Analytical_TTL Replace Functionality

Description
This PR is for the replace container functionality for the analytical storage ttl feature.

OH and please add relevant Changelog entry and remove the limitation from the README


1.9.0 Changelog

as title

I would suggest to add detail on the fact that docker tag 1 and 1.9 will not follow anymore latest commit from branch release/v1.9 but the latest tag 1.9.X (more stable)

@sapk maybe we put that in blog post?
Blocking this PR waiting for https://github.com/go-gitea/gitea/pull/7675 backport.

Well, now that #7675 is merged, let's restart the build?

@rakshith-ravi waiting back port https://github.com/go-gitea/gitea/pull/7682
@techknowlogick could you update the change log to add #7682

make LG-TM work


Fix Intel compile

Fixes Intel compile (closing #47). We don't have CI for Intel compiler set up, @NilsBForze can you please test?
How:

Renames all the .f95 files to .f90. Intel doesn't recognize .f95 extensions as Fortran code, although it can be made to do so with special platform-specific flags (/extfor:, -Tf), but I ran into problems with these. Renaming the files just worked.
Fixes some Intel-specific compiler errors and warnings.

My environment:

CMake 3.17.2
ifort (IFORT) 2021.3.0 20210609 (oneAPI)

Works for me.
Cmake: 3.17.1
ifort 2021.3.0


MultipleContainers jitter from inner item when dragging to bottom of new column

I have reconstructed the multiple containers example:
https://codesandbox.io/s/dndkit-ivpj4d
When moving an inner container to the bottom of a different column, I'm experiencing some jitter from an existing inner item at the bottom of the column just as the dragged item is carried to the new column.
Watch "C4" in this video:
https://user-images.githubusercontent.com/20871604/227420071-22394f93-86d4-45d0-8b90-198850516e71.mov

In a local project:
https://user-images.githubusercontent.com/20871604/227420320-4a7f096e-3731-4c87-ad1d-23e76bcb2f4d.mov

It appears subtle in this video, but it appears more pronounced in different examples. Does anyone know what might be causing this jitter?

I noticed the same behaviour when I've added more logic to my draggable items.
I did some debugging and I think what happens is that the vertical sorting strategy first adds the item as next to last, then quickly moves it to the last spot when the state updates with the item in new container. As of now, I have no solution except to try and simplify my draggable items when dragging something.
In this video, first I have the full item and you can see how it jitters when changing containers. Then, I comment out the menu code (button with 3 vertical dots, which contains plenty of logic) inside the draggable item and the jitter is gone.

I think you're right, it's probably related to the vertical sort or the collision strategy. I also noticed the keyboard's programmatic move will move the item to the next-to-last in the next column as well, and refuses to move it to the last item, even if it's lower on the previous column's list.


cant set session timeout, tried many permutations and asked in irc and stack. to no avail.

Hi, Im only posting my issue here as a last resort, I understand this is a bug tracker. But I think its fair to say that flask default session lasting 31 days is a bug and security flaw in itself, and havent found an easy way to change this.  Im simply trying to set a timeout of 15 minutes idle activity for my user sessions (site-wide but particularly for my @login_required '/dashboard/' area) I tried eliminating different variables to solve the problem but still the session lasts indefinitely.  Heres the post of my imports, config, dashboard, blueprint, register / login system in its entirety (dont worry its rather succinct).  Hopefully someone can see an error I overlooked.  Thank you.
https://dpaste.de/1pVD

The session cookie isn't permanent by default. If you make it permanent, you can set the lifetime with PERMANENT_SESSION_LIFETIME. Also, Flask-Login is not part of Flask.
Please use Stack Overflow for questions about your own code. This tracker is for issues with Flask's code. Be sure to include a Minimal, Complete, and Verifiable Example.

sorry but that didnt answer anything.  my code includes the line
permanent_session_lifetime = timedelta(minutes=2)
and i currently dont use Flask-Login, so that extension doesnt apply to my question.  guess ill jsut have to deal with session = INFINITY DURATION because no one on the internet can provide an answer...

PERMANENT_SESSION_LIFETIME, capitalized, just like every other setting in that call to update.


Loadbalancer member in error

With the Octavia load balancer there is always a member of the pool in error :

we have to find a way to fix this.

When there's 2 nodes, one of the https member is down. Both http members are up.

If the resource "openstack_lb_monitor_v2" "monitor" is removed, both members are up...


Fix linting errors and run ESLint on Travis

Makes npm test run both ESLint and Mocha - could fix it by adding npm run lint to travis.yml's script field too.

Coverage remained the same at 77.572% when pulling 60ca6692a2ae49337d6c0401294afeac924f6b82 on ekmartin:lint into b3d5f98cff5fb0f14ef9fcbf40494622b67f7a33 on slackhq:master.


Fix docker build

https://stackoverflow.com/questions/51023312/docker-having-issues-installing-apt-utils/56569081#56569081
Signed-off-by: Francesco Guardiani<EMAIL_ADDRESS>

Fixes https://github.com/knative-sandbox/eventing-kafka-broker/issues/274
I'll wait for the CI run to see if the error is gone.


Dtest.debug seems ignored

I couldn't find documentation stating this to be deprecated, rather, I found 5.0 documentation claiming both should work, so....
C:\GRADLE\gradle-5.0\bin\gradle :cleanTest :test --tests com.me.MyClass* -Dtest.debug
(above does not wait, runs test successfully, exits without attachment)
C:\GRADLE\gradle-5.0\bin\gradle :cleanTest :test --tests com.me.MyClass* --debug-jvm
(waits for debugger attachment, can be successfully attached)
Windows 10, JDK 1.8_181
Can repro?

Looks like you didn't search hard enough: There is a deprecation info at https://docs.gradle.org/5.0/userguide/upgrading_version_4.html#potential_breaking_changes

The -Dtest.debug command-line option has been removed — use the --debug-jvm option instead.

I found 5.0 documentation claiming both should work, so....
Maybe you can tell where you found the "-Dtest.debug" option - that would be a documention error then.

https://docs.gradle.org/current/userguide/java_testing.html#sec:debugging_java_tests
At end:
"You can either set the Test.getDebug() property to true or use the --debug-jvm command line option"
I guess now in hindsight I just assumed that meant the property was still "public" and could be set via command line.
At any rate, I was trying to figure out where I needed to submit a ticket.  I wasn't sure this was a bug, and had posted it to forums first, but got no traction.  I need to submit the issue to: https://github.com/kelemen/netbeans-gradle-project
...because that is how it is attempting to run debug-test.  There is a workaround to configure the plugin to make the process "attach" to the debugger, and those cmdline args/options still work fine.
Thanks for quick response!  Gradle is Great.  I'll see if I can get that IDE plugin back on track, and keep the House of Gradle clean ;)


Time Series Resource:  incorrect element labels in resourcemetadata.xml

Testing on dev.hydroshare.org.  See resource: http://dev.hydroshare.org/resource/f5e4c6083e8d4e91be216295f7b6282e/
There are a couple of issues in the resourcemetadata.xml created for a time series resource:

The "UnitsAbbreviation" element is incorrectly encoded as UnitsType.  The content of the element is correct, it is just the name of the element that is incorrect.
The "AggregationStatistics" element should singular - AggregationStatistic

@pkdash is this ready for 1.5.0 release.  If it would be a distraction from your current work please indicate whether (a) time series can be included as is without this fix in 1.5 or (b) whether we should withhold time series from 1.5 until this is fixes.  Change the milestone based on your choice.

@dtarb and @horsburgh I missed it as it was not in the 1.5 release check list. It is a small fix and I think I should fix it today so that time series resource can be included in release 1.5.

I would hate to put it off if it is something small.  Thanks Pabitra.

@horsburgh I have now fixed this. I think you should be able to test it on dev.hydroshare.org sometime tomorrow after tonight's build. Then you can close this if see it being fixed.


Documentation for using this library in a Jetpack Compose project for detecting iBeacons

Please add documentation for using this library in a Jetpack Compose project for detecting iBeacons

Thank you for the suggestion. We will improve the doc and look into iBeacons. Let's leave the issue open for a reminder.

is there a way to detect iBeacon ?


"Method does not override any method from its superclass" error thrown in Xcode

Cannot get the library installed on iOS:

using dev branch
RN version 0.52.0

Library works on android.

I can still reproduce this error on 0.2.4 react-native-track-player, rn 0.44.0


React-aria versions of react-spectrum Tray

🙋 Feature Request
The react-spectrum package has a feature not available if you are solely building on top of react-aria and react-stately; the mobile tray versions of the Picker and ComboBox.
🔦 Context
The trays used by these are very useful and have special logic and code inside the react-spectrum implementation. It is certainly possible to recreate a mobile tray, and copy implementation details from react-spectrum, but that is not an ideal solution.
We are currently building a component library on top of react-aria and react-stately, since our design team wants a lot of flexibility but we also care about a11y. The mobile trays have so far been complicated to implement, and we would rather not copy implementation examples from react-spectrum since it can easily get out of sync with bug fixes in the futrue.
There is a lot of code in the ComboBoxTray that basically looks like its own useMobileComboBox hook.

Definitely something we can consider doing, my only hesitation would be the divergences our MobileComboBox has from the    WAI-ARIA ComboBox pattern in general and where we would draw the line when deciding which of those divergences are Spectrum design specific.

Another very useful use-case for Tray from react-spectrum is Menu. The current version in RAC doesn't do that on mobile and so creates a usability issue.
react spectrum docs even call it out:

Trays
On mobile, Menus automatically display in a tray instead of a popover to improve usability.

We hope to bring Trays to RAC in the near future.

I don't think we need to do anything for them. You can already build a Tray with the Modal component and some custom styles. This example opens to the side but you could just as easily build a bottom tray. https://react-spectrum.adobe.com/react-aria/Modal.html#custom-overlay

Good to know, thanks for the links. In the Menu use-case there's however the complexity of sliding left and right with submenus. Is there some way how to achieve that with existing components/hooks?

I think you have a couple options. You could make a Popover which just renders into place, sibling to root Menu.
If it needs to be more complex. All the hooks and state for Popovers should be available via the context. You can reference our implementation. I also made a stripped down example the other day for another discussion.
https://github.com/adobe/react-spectrum/discussions/6258#discussioncomment-10027318
@devongovett am I missing an easier way to do this? Otherwise I imagine we'll add something (even just an example) in the near future.

Closing as this should be doable.

I don't think we need to do anything for them. You can already build a Tray with the Modal component and some custom styles. This example opens to the side but you could just as easily build a bottom tray. https://react-spectrum.adobe.com/react-aria/Modal.html#custom-overlay
And for a more fancy example here's one that you can swipe to close https://react-spectrum.adobe.com/react-aria/examples/framer-modal-sheet.html

@devongovett, it's really hard to find a modern website these days where the mobile menu doesn't slide out in a tray – it's kind of a standard. But you're suggesting adding a library and then writing custom CSS on top of it, which might not even work bug-free?
I've criticized Ant Design plenty of times for its performance, but every time I look for alternatives to Tabs, Drawer, Collapse, or Dropdown, I end up going back to it. Why? Because I don’t have to reinvent the wheel with custom components – most of the features I need are already built-in.

All of react aria components is style free so I'm not sure how this component is any different than our others?


add diagnostic collectors based on datacenter type

Issue #, if available:
Description of changes:
Add diagnostic collectors based on datacenter type, including the CAPV system namespace which was missing.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: danbudris, jaxesn
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [danbudris,jaxesn]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Add links to the original Python notebooks on Cookbook pages

Like a button Open in Github here.

Currently, added as a kink in the document


ValueError: For training, each question should have exactly 1 answer.

Please be sure that there's no other issue regarding the same bug by searching in older issues and that the bug is particular to cdQA (sometimes you can find a fix for the bug by doing a quick search on google).
Describe the bug
Im following your tutorial but when adding the SQuAD data base for fine tunning is giving me an error: ValueError: For training, each question should have exactly 1 answer.
Screenshots

I have fixed it, it looks like SQuAD v2 has 3 repetitive answers per questions and this model doesen't likes that


sunvox: 1.9.6c -> 2.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/SunVox/versions.
meta.description for sunvox is: "Small, fast and powerful modular synthesizer with pattern-based sequencer"
meta.homepage for sunvox is: "http://www.warmplace.ru/soft/sunvox/"
meta.changelog for sunvox is: ""
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
Warning: no invocation of /nix/store/877s69rxacj65rcp939db16n46784am3-SunVox-2.0/bin/sunvox had a zero exit code or showed the expected version
0 of 1 passed binary check by having a zero exit code.
0 of 1 passed binary check by having the new version present in output.
found 2.0 with grep in /nix/store/877s69rxacj65rcp939db16n46784am3-SunVox-2.0
found 2.0 in filename of file in /nix/store/877s69rxacj65rcp939db16n46784am3-SunVox-2.0

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
0 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
sunvox

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/877s69rxacj65rcp939db16n46784am3-SunVox-2.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A sunvox https://github.com/r-ryantm/nixpkgs/archive/f89e01891efd5e3f381d020893d1fb14b1f29dff.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/877s69rxacj65rcp939db16n46784am3-SunVox-2.0
ls -la /nix/store/877s69rxacj65rcp939db16n46784am3-SunVox-2.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

sunvox

Maintainer pings
cc @puffnfresh for testing.

@ofborg eval

Superseded by #158366


Casanovo predicts for invalid spectra

Invalid spectra after preprocessing are replaced by a dummy spectrum, but Casanovo still predicts a peptide for them. The resulting predictions are naturally incorrect, consisting of long peptide sequences with low(ish) scores (but not obviously wrong).
Instead invalid spectra should be filtered out or no prediction should be given. The former is probably better, because it might be a factor during training as well. I haven't fully been able to figure out how to skip items in the dataloader though.

One solution would be to move peak processing from Dataset to Parser in depthcharge. That way invalid spectra are encountered prior to being added to the index and can immediately be filtered out, rather than when being retrieved from the dataset. As an added advantage, spectrum processing only needs to be done once for each spectrum, when creating the index, rather than repeating it every time the same spectrum is retrieved.
A disadvantage, however, is that when spectrum processing options change, the index would have to be recreated. Nevertheless, I think our spectrum processing based on best practices and we don't really vary it, so for Casanovo at least it should be pretty fixed.
Additionally, it destroys the link between the indexes of the output PSMs and the input spectra. Although this is a broader issue (#70).
@wfondrie What do you think?

I'm open to this. I also think that the current way of tracking the spectrum index is pretty fragile and not ideal. Instead, that information should be saved in the index itself. Ayse started a PR in depthcharge to solve the spectrum tracking issue, but it was incomplete - I'll see if I can get it updated and integrated.

#105 will address spectrum index tracking once completed for future reference


[WIP] API Tweaks

New routes

/v2/assets/<asset>/dispenses
/v2/addresses/<address>/dispenses/sends
/v2/addresses/<address>/dispenses/receives
/v2/addresses/<address>/dispenses/sends/<asset>
/v2/addresses/<address>/dispenses/receives/<asset>
/v2/transactions/<int:tx_index>/events
/v2/transactions/<tx_hash>/events
/v2/transactions/<int:tx_index>/events/<event>
/v2/transactions/<tx_hash>/events/<event>
/v2/transactions/<int:tx_index>
/v2/blocks/<block_hash>
/v2/mempool/transactions/<tx_hash>/events
/v2/addresses/<address>/issuances

Pagination

Replace offset and last arguments by cursor
All responses contain a next_cursor field.
All queries that return lists from the database accept the "cursor" and "limit" arguments. To get the next page you must use "?cursor=<next_cursor>"

Miscellaneous

Documents the list of events with an example format for each of them.
Updated rowtracer so that apsw returns boolean instead of integer for BOOL type fields.
The asset, assets, give_asset and get_asset parameters are not case sensitive.

OP updated.


Updates: go version, and use dependabot

Fixed. Happy with this for review now.

Updated the branch protection rules to require the new checks and deleted the old versions.


Did not receive response to shouldStartLoad in time, defaulting to YES

Fix: Did not receive response to shouldStartLoad in time, defaulting to YES by increase check time to 5 seconds
https://github.com/react-native-webview/react-native-webview/issues/124#issuecomment-489677422

@hqdai please send pull request to the react-native-webview/react-native-webview

@hqdai please send pull request to the react-native-webview/react-native-webview


Add isDeveloperModeEnabled for android devices

With isDeveloperModeEnabled you can check if the device is in the
android developer mode.

Resolve merge conflict

Hi there!
I'm a new maintainer on this project and I'm trying to clear the PR queue.
Are you still available to bring this PR up to date with latest changes and discuss it?
Please let me know, thank you!

Hi great that the library has new maintenaner like you and gant. Will take a Look at this PR soonish :)

Great, happy to see that you're still on board! 🎉
Left you a change request, otherwise this looks good to me

Thank you :)

The branch was lost in my fork so I need to make a new PR https://github.com/rebeccahughes/react-native-device-info/pull/316


How to install without bower?

Hello,
How can i install chartist and plugins without bower?
Thanks in advance.

Using npm?
https://www.npmjs.com/search?q=chartist
Or simply from a CDN (https://gionkunz.github.io/chartist-js/getting-started.html#use-a-cdn-alternatively)

A quickstart guide can be found here.


[redfish] Change system action status code from 201 to 202

Resolves https://github.com/RackHD/RackHD/issues/383

*** BUILD #2228 ***
Test Name: Redfish Systems Root should perform the specified valid reset
Error Details: expected 201 "Created", got 202 "Accepted" Response body: {<EMAIL_ADDRESS>'/redfish/v1/TaskService/Tasks/abcdef' } Error: expected 201 "Created", got 202 "Accepted"     at Test._assertStatus (/home/jenkins/workspace/on-http/build/node_modules/supertest/lib/test.js:232:12)     at Test._assertFunction (/home/jenkins/workspace/on-http/build/node_modules/supertest/lib/test.js:247:11)     at Test.assert (/home/jenkins/workspace/on-http/build/node_modules/supertest/lib/test.js:148:18)     at assert (/home/jenkins/workspace/on-http/build/node_modules/supertest/lib/test.js:127:12)     at /home/jenkins/workspace/on-http/build/node_modules/supertest/lib/test.js:124:5     at Test.Request.callback (/home/jenkins/workspace/on-http/build/node_modules/supertest/node_modules/superagent/lib/node/index.js:691:12)     at IncomingMessage.<anonymous> (/home/jenkins/workspace/on-http/build/node_modules/supertest/node_modules/superagent/lib/node/index.js:922:12)     at IncomingMessage.EventEmitter.emit (events.js:117:20)     at _stream_readable.js:920:16     at process._tickDomainCallback (node.js:459:13)
Stack Trace: Error: expected 201 "Created", got 202 "Accepted"
    at Test._assertStatus (node_modules/supertest/lib/test.js:232:12)
    at Test._assertFunction (node_modules/supertest/lib/test.js:247:11)
    at Test.assert (node_modules/supertest/lib/test.js:148:18)
    at assert (node_modules/supertest/lib/test.js:127:12)
    at node_modules/supertest/lib/test.js:124:5
    at Test.Request.callback (node_modules/supertest/node_modules/superagent/lib/node/index.js:691:12)
    at IncomingMessage.<anonymous> (node_modules/supertest/node_modules/superagent/lib/node/index.js:922:12)
    at _stream_readable.js:920:16

Test Name: Redfish Systems Root should perform the specified boot image installation
Error Details: expected 201 "Created", got 202 "Accepted" Response body: {<EMAIL_ADDRESS>'/redfish/v1/TaskService/Tasks/abcdef' } Error: expected 201 "Created", got 202 "Accepted"     at Test._assertStatus (/home/jenkins/workspace/on-http/build/node_modules/supertest/lib/test.js:232:12)     at Test._assertFunction (/home/jenkins/workspace/on-http/build/node_modules/supertest/lib/test.js:247:11)     at Test.assert (/home/jenkins/workspace/on-http/build/node_modules/supertest/lib/test.js:148:18)     at assert (/home/jenkins/workspace/on-http/build/node_modules/supertest/lib/test.js:127:12)     at /home/jenkins/workspace/on-http/build/node_modules/supertest/lib/test.js:124:5     at Test.Request.callback (/home/jenkins/workspace/on-http/build/node_modules/supertest/node_modules/superagent/lib/node/index.js:691:12)     at IncomingMessage.<anonymous> (/home/jenkins/workspace/on-http/build/node_modules/supertest/node_modules/superagent/lib/node/index.js:922:12)     at IncomingMessage.EventEmitter.emit (events.js:117:20)     at _stream_readable.js:920:16     at process._tickDomainCallback (node.js:459:13)
Stack Trace: Error: expected 201 "Created", got 202 "Accepted"
    at Test._assertStatus (node_modules/supertest/lib/test.js:232:12)
    at Test._assertFunction (node_modules/supertest/lib/test.js:247:11)
    at Test.assert (node_modules/supertest/lib/test.js:148:18)
    at assert (node_modules/supertest/lib/test.js:127:12)
    at node_modules/supertest/lib/test.js:124:5
    at Test.Request.callback (node_modules/supertest/node_modules/superagent/lib/node/index.js:691:12)
    at IncomingMessage.<anonymous> (node_modules/supertest/node_modules/superagent/lib/node/index.js:922:12)
    at _stream_readable.js:920:16

Test Name: Http.Api.Notification "before all" hook: start HTTP server
Error Details: Attempted to wrap undefined property publishTaskNotification as function
Stack Trace: TypeError: Attempted to wrap undefined property publishTaskNotification as function
    at Object.wrapMethod (node_modules/sinon/lib/sinon/util/core.js:106:29)
    at Object.stub (node_modules/sinon/lib/sinon/stub.js:61:26)
    at Context.<anonymous> (spec/lib/services/notification-api-service-spec.js:27:15)

:+1:

:+1:

*** BUILD #2229 ***
Test Name: Http.Api.Notification "before all" hook: start HTTP server
Error Details: Attempted to wrap undefined property publishTaskNotification as function
Stack Trace: TypeError: Attempted to wrap undefined property publishTaskNotification as function
    at Object.wrapMethod (node_modules/sinon/lib/sinon/util/core.js:106:29)
    at Object.stub (node_modules/sinon/lib/sinon/stub.js:61:26)
    at Context.<anonymous> (spec/lib/services/notification-api-service-spec.js:27:15)

jenkins: test this please

@yyscamper fyi - I'm seeing a master regression of the same failure in the continuous unit-test job: http://rackhdci.lss.emc.com/job/Continuous-Test/job/Continuous-Unit-Test/buildTimeTrend

@jlongever : I have reverted the code (see https://github.com/RackHD/on-core/pull/194), so I think it's OK now.


Initial support for triggering and storing notifications

This pull request adds support for triggering and storing notifications.  The notificaton definition interface and specific notification definitions are in the notifications package.  The notification handler is in the middleware package.  Currently only the code-based notifications are supported: Inpatient Encounter, Re-Admission, and ER Visit.
This pull request depends on https://github.com/intervention-engine/fhir/pull/5.
This is my first attempt (ever) at writing Go, so I appreciate a full code-review (although this is mainly just following the same template as all the other resources).

I'm still not 100% sure on package notification.  I think there are actually three choices to consider here:
What I've submitted so far (split between notifications and middleware packages)
Moving notification interface and implementations to models
Moving notification handler to notifications so all things notification are together
I actually kind of like the last option, but it goes against the current structure of the project.  Still, I think it's worth considering if each type of middleware component should just have its own package that contains everything related to it (e.g., facts, notifications, etc) -- especially since most handlers are not actually related to each other.  Just something to think about...


Updated front-end dependencies

Coverage remained the same at 44.202% when pulling a849a8e3d2fea7f8168297a8ca0554a20c7fffb2 on dep_update into 2817c67c41127ee4c69e748883b7c7ac93da9578 on master.


(editor) Cursor should be moved to the Rename Symbol edit field

Issue Type: Feature Request
When using Rename Symbol in the editor the cursor stays on the code line instead of moving to the symbal rename field. Forces to click in that box to change the name, instead of typing right away which is the intuitive thing to do. And typing right away overwrites the initial name in the actual code line, messing everything up.
VS Code version: Code 1.64.2 (f80445acd5a3dadef24aa209168452a3d97cc326, 2022-02-09T22:02:28.252Z)
OS version: Windows_NT x64 10.0.19042
Restricted Mode: No

This doesn't reproduce for me... @RaphTronic How do you invoke rename, via the keybinding or via the context menu?

Via context menu.
This seems to be intermittent. Has been bugging me for the last 2weeks but impossible to repro this morning (normal editing, during a run pause, during a run error, etc).
Seems to be an intermittent issue, like the non alphanumeric keys not working anymore in the editor after a run error (clicking on any menu makes them work again).
Ok, let's close. I'll reopen if I stumble on a way to repro some day.
Thanks.


Consider MPL license

Hi all! Have you considered the MPLv2 license rather than the MIT license?

if you need to know what it's about theres a dicussion here btw https://github.com/SethBling/cbscript/issues/3

We'll share more info soon about this.

We'll share more info soon about this.

i see no reason not to go with MPLv2, in my eyes MIT serves no real purpose, it's outdated

We'll share more info soon about this.

any update?


how to customizing variables bootstrap4

https://v4-alpha.getbootstrap.com/getting-started/options/
nuxt.config.js
    css: [
      'bootstrap/scss/bootstrap.scss',
      '~/styles/index.scss',
      'bootstrap-vue/dist/bootstrap-vue.css',
    ],
    plugins: [
      '~/plugins/bootstrap-vue.js'
    ],

and how to add  bootstrap-loader?
require('bootstrap-loader?bootstrapPath=/path/to/bootstrap');

// or

entry: [ 'bootstrap-loader?bootstrapPath=/path/to/bootstrap', './app' ]

Tips: You can refer this doc bootstrap-vue to integrate bootstrap-vue.

Yes, I added it and it works. But I need customizing bootstrap variables.

Have a look at https://github.com/bootstrap-vue/bootstrap-vue/issues/690, hope it can help you 😸

it works. Thank you

Dear @dvgamer
Can you share your configuration based on bootstrap-vue/bootstrap-vue#690 to apply in Nuxt ?
Thanks

Sure, @duythang
Bootstrap-Vue Customizing variables for nuxtjs
npm i bootstrap@4 bootstrap-vue
npm i --save-dev node-sass sass-loader

nuxt.config.js
  css: [
    'styles/index.scss',
    'bootstrap-vue/dist/bootstrap-vue.css'
  ],
  plugins: [
    'plugins/bootstrap-vue.js'
  ],

styles/index.scss
@import 'bootstrap_variables.scss';
@import '~bootstrap/scss/bootstrap.scss';

styles/bootstrap_variables.scss
// https://v4-alpha.getbootstrap.com/getting-started/options/
$grid-columns:  12;

plugins/bootstrap-vue.js
import Vue from 'vue'
import BootstrapVue from 'bootstrap-vue'

Vue.use(BootstrapVue)

@dvgamer : Thank you so much ^^

@touno-project This doesn't seem to make Bootstrap variables available in components/layouts/pages. Is there a way to access things like theme-color('primary') in (for example) layouts/default.vue without importing bootstrap our my custom scss file into every location where I want to access scss variables/mixins?

@dagoss I think that would not be possible.

I didn't include it as a plugin (plugins/bootstrap-vue.js) and worked well


Fix DB migration error in postgresql 12.*

This happens in postgres 12.*
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123 HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123 The above exception was the direct cause of the following exception:
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123 Traceback (most recent call last):
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123   File "/app/.venv/bin/alembic", line 11, in <module>
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123     load_entry_point('alembic==1.4.0', 'console_scripts', 'alembic')()
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123   File "/app/.venv/lib/python3.8/site-packages/alembic/config.py", line 577, in main
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123     CommandLine(prog=prog).main(argv=argv)
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123   File "/app/.venv/lib/python3.8/site-packages/alembic/config.py", line 571, in main
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123     self.run_cmd(cfg, options)
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123   File "/app/.venv/lib/python3.8/site-packages/alembic/config.py", line 548, in run_cmd
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123     fn(
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123   File "/app/.venv/lib/python3.8/site-packages/alembic/command.py", line 298, in upgrade
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123     script.run_env()
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123   File "/app/.venv/lib/python3.8/site-packages/alembic/script/base.py", line 489, in run_env
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123     util.load_python_file(self.dir, "env.py")
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123   File "/app/.venv/lib/python3.8/site-packages/alembic/util/pyfiles.py", line 98, in load_python_file
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123     module = load_module_py(module_id, path)
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123   File "/app/.venv/lib/python3.8/site-packages/alembic/util/compat.py", line 173, in load_module_py
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123     spec.loader.exec_module(module)
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123   File "<frozen importlib._bootstrap_external>", line 783, in exec_module
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123   File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123   File "/app/src/conduit/migrations/env.py", line 62, in <module>
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123     run_migrations_online()
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123   File "/app/src/conduit/migrations/env.py", line 56, in run_migrations_online
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123     context.run_migrations()
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123   File "<string>", line 8, in run_migrations
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123   File "/app/.venv/lib/python3.8/site-packages/alembic/runtime/environment.py", line 846, in run_migrations
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123     self.get_context().run_migrations(**kw)
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123   File "/app/.venv/lib/python3.8/site-packages/alembic/runtime/migration.py", line 518, in run_migrations
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123     step.migration_fn(**kw)
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123   File "/app/src/conduit/migrations/versions/72a996e5a6ca_tags.py", line 21, in upgrade
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123     op.create_table(
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123   File "<string>", line 8, in create_table
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123   File "<string>", line 3, in create_table
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123   File "/app/.venv/lib/python3.8/site-packages/alembic/operations/ops.py", line 1250, in create_table
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123     return operations.invoke(op)
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123   File "/app/.venv/lib/python3.8/site-packages/alembic/operations/base.py", line 374, in invoke
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123     return fn(self, operation)
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123   File "/app/.venv/lib/python3.8/site-packages/alembic/operations/toimpl.py", line 101, in create_table
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123     operations.impl.create_table(table)
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123   File "/app/.venv/lib/python3.8/site-packages/alembic/ddl/impl.py", line 258, in create_table
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123     self._exec(schema.CreateTable(table))
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123   File "/app/.venv/lib/python3.8/site-packages/alembic/ddl/impl.py", line 140, in _exec
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123     return conn.execute(construct, *multiparams, **params)
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123   File "/app/.venv/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 982, in execute
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123     return meth(self, multiparams, params)
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123   File "/app/.venv/lib/python3.8/site-packages/sqlalchemy/sql/ddl.py", line 72, in _execute_on_connection
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123     return connection._execute_ddl(self, multiparams, params)
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123   File "/app/.venv/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1039, in _execute_ddl
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123     ret = self._execute_context(
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123   File "/app/.venv/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1249, in _execute_context
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123     self._handle_dbapi_exception(
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123   File "/app/.venv/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1476, in _handle_dbapi_exception
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123     util.raise_from_cause(sqlalchemy_exception, exc_info)
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123   File "/app/.venv/lib/python3.8/site-packages/sqlalchemy/util/compat.py", line 398, in raise_from_cause
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123     reraise(type(exception), exception, tb=exc_tb, cause=cause)
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123   File "/app/.venv/lib/python3.8/site-packages/sqlalchemy/util/compat.py", line 152, in reraise
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123     raise value.with_traceback(tb)
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123   File "/app/.venv/lib/python3.8/site-packages/sqlalchemy/engine/base.py", line 1245, in _execute_context
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123     self.dialect.do_execute(
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123   File "/app/.venv/lib/python3.8/site-packages/sqlalchemy/engine/default.py", line 588, in do_execute
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123     cursor.execute(statement, parameters)
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123 sqlalchemy.exc.ProgrammingError: (psycopg2.errors.UndefinedFunction) function gen_random_uuid() does not exist
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123 LINE 3:  id UUID DEFAULT gen_random_uuid() NOT NULL,
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123                          ^
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123 HINT:  No function matches the given name and argument types. You might need to add explicit type casts.
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123 [SQL:
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123 CREATE TABLE tags (
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123 	id UUID DEFAULT gen_random_uuid() NOT NULL,
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123 	name VARCHAR NOT NULL,
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123 	CONSTRAINT pk_tags PRIMARY KEY (id)
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123 )
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123 ]
Feb 27 06:02:12 pyramid-real-migrate-mi-vqtfe8 app/release.3123 (Background on this error at: http://sqlalche.me/e/f405)
Feb 27 06:02:13 pyramid-real-migrate-mi-vqtfe8 app/release.3123 Sentry is attempting to send 1 pending error messages
Feb 27 06:02:13 pyramid-real-migrate-mi-vqtfe8 app/release.3123 Waiting up to 10 seconds
Feb 27 06:02:13 pyramid-real-migrate-mi-vqtfe8 app/release.3123 Press Ctrl-C to quit
Feb 27 06:02:13 pyramid-real-migrate-mi-vqtfe8 app/release.3123 Database migrations failed!

Then upgrade postgres to the latest version (Available versions are 9.5, 9.6, 10, 11, 12 (the default is 12)).

[ ] Local development DB is upgraded
[ ] Review app DB is upgraded
[ ] Production DB is upgraded

Nope.. it's not postgres version related. Neither psycopg2-binary, pyramid-deferred-sqla
nor zope.sqlalchemy.

Nope.. it's not postgres version related. Neither psycopg2-binary, pyramid-deferred-sqla
nor zope.sqlalchemy.

Found ans in https://dba.stackexchange.com/questions/146135/psql-9-5-gen-random-uuid-not-working. Need to CREATE EXTENSION pgcrypto;

Fixed in https://github.com/niteoweb/pyramid-realworld-example-app/pull/84


Help: How to allow task overlap in JobShop like problem?

Hi,
I have a set of machines that can do tasks on parallel, how can I allow these tasks to overlap?
I tried this:

Applying this way the NoOverlap constraint only to the normal machines and ignoring the parallel ones. At first it seemed to work. But because some unkown reason some taks simply dissappear. Any Ideas?

Use a Cumulative constraint.
Laurent Perron | Operations Research |<EMAIL_ADDRESS>| (33) 1 42 68 53
00
Le mar. 25 juin 2019 à 20:06, gustavo-barros<EMAIL_ADDRESS>a
écrit :

Hi,
I have a set of machines that can do tasks on parallel, how can I allow
these tasks to overlap?
I tried this:
[image: image]
https://user-images.githubusercontent.com/36746102/60121925-87a37c80-975a-11e9-97e0-c6e45634dee5.png
Applying this way the NoOverlap constraint only to the normal machines and
ignoring the parallel ones. At first it seemed to work. But because some
unkown reason some taks simply dissappear. Any Ideas?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/google/or-tools/issues/1379?email_source=notifications&email_token=ACUPL3O4SE5WHZM3KSMZHFLP4JNBRA5CNFSM4H3K4DJKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4G3TVMSA,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACUPL3K3TKG6J3S6FBCIU6DP4JNBRANCNFSM4H3K4DJA
.

Can you start reading the doc ?
Le mar. 25 juin 2019 à 20:16, gustavo-barros<EMAIL_ADDRESS>a
écrit :

How I use that, you have an example?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/google/or-tools/issues/1379?email_source=notifications&email_token=ACUPL3LPUW7PWX33CI5NB3TP4JOGPA5CNFSM4H3K4DJKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYRECHY#issuecomment-505561375,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACUPL3OUNCIZR2UDUNEJQYLP4JOGPANCNFSM4H3K4DJA
.

http://google.github.io/or-tools/python/ortools/sat/python/cp_model.html#cp_model.CpModel.AddCumulative
I have no documentation for C# currently.

Thank you for the link Laurent.
The problem is I don't understand how that will help me to make the tasks overlap with each other in the chosen machine. Maybe I don't  have the knowledge required to understand what that function actually does, despite I understand the code it expresses.
I made some tests here, but I was not able to extract some sense of it.

All that I need is to tell the solver, "hey, in this machine the tasks can run free and wildly as they want to". My first idea was simply remove the NoOverlap constraint, but that seems not to work.

Here is another explanation on the cumulative constraint:
http://www.emn.fr/x-info/sdemasse/gccat/Ccumulative.html
Laurent Perron | Operations Research |<EMAIL_ADDRESS>| (33) 1 42 68 53
00
Le jeu. 27 juin 2019 à 16:36, gustavo-barros<EMAIL_ADDRESS>a
écrit :

All that I need is to tell the solver, "hey, in this machine the tasks can
run free and wildly as they want to". My first idea was simply remove the
NoOverlap constraint, but that seems not to work.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/google/or-tools/issues/1379?email_source=notifications&email_token=ACUPL3JSBSCYVFSUNN2CUMDP4TF6TA5CNFSM4H3K4DJKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYXKIFQ#issuecomment-506373142,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACUPL3KMQSMD7EVU635SL5DP4TF6TANCNFSM4H3K4DJA
.

I propose that for each interval 'i', you create an optional interval 'i_c' using the start, duration and end variable of the interval 'i', and an new Boolean variable 'p'.
Then you add all 'i_c' to the no_overlap.
Now to enforce the no_overlap, just set the 'p' variables to true.


Don't fear the reaper (part 4 of 4) bug

Don't know if anyone else has had this issue, but in Don't fear the reaper part 4, after I use the device on the mine cart and enter the fusion portal, the mission doesn't get past "defeat fusion grim" after I've defeated him. I've realoaded, refreshed, killed him and every single simian spawn about ten times now. Has anyone else had this issue? Pls help

I'm being told this is a known tabledata ID mismatch issue. This should be fixed soon. Thanks for the report.


Jerry

Hi @eaeao,
I assume you meant  to submit that to a different repository, but if you would like to create a PR to add Korean to Ardublockly it would be quite welcomed :)


No access to "Data and AI Demo Megamap"

I am not sure if this is the case, but while reading the article series from top to bottom, i've encountered the link to demo broken / incorrect.
See here:
https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/industry/retail/industry-priority-scenarios#see-intelligent-retail-hands-on-with-a-retail-industry-demo
I wanted to play around with the map, but got no access instead:

Is this expected?

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

ID: 902df803-acad-cc32-0018-4d83fd5039bf
Version Independent ID: 902df803-acad-cc32-0018-4d83fd5039bf
Content: Industry priority scenarios in the retail industry - Cloud Adoption Framework
Content Source: docs/industry/retail/industry-priority-scenarios.md
Service: caf
Sub-service: caf-scenario-retail
GitHub Login: @mpvenables
Microsoft Alias: jaalmond

The "Data & AI Dream Demo Hub" is supported through<EMAIL_ADDRESS>and<EMAIL_ADDRESS>not through the Cloud Adoption Framework for Azure content team.  We'll have to close the issue here, and request that you seek support from the team that can help you at those email addresses.
#please-close


Ensure canonical-data.json updates are propagated to all tracks

There's been a lot of great work done recently to add the extract/update/create canonical-data.json files for all of the exercises.
Currently, the updates don't create any corresponding link in the different language repositories to let the maintainers know that they should update their tests to correspond to the standard.
Is there some sort of way that we could automatically create an issue in all of the corresponding language tracks each time the canonical data changes for one of the exercises?
As a track maintainer that would let me track which exercises I need to update without having to try to keep my own todo list or manually open issues for each updated exercise.

I was thinking something like what was done with ensuring every track had a hello world exercise:
https://github.com/exercism/todo/issues/12

There was a bit of previous discussion on when we should emblazon tracks at https://github.com/exercism/discussions/issues/104#issuecomment-263109966. It would be useful to get clarity on the threshold at which we consider a change significant enough to warrant it. How worried are we about issue fatigue?
I imagine that we would consider a new canonical-data.json file to be significant enough to warrant emblazoning all the tracks, right?

The below is no solution, but at some point in the past I needed to check whether various tracks are up-to-date - https://github.com/exercism/x-common/compare/master...petertseng:up-to-date has scripts which compare the last modify time of select tracks' test files against the last modify time in x-common. I say this is no solution because the track maintainer still has to remember to run it from time to time.

I imagine that we would consider a new canonical-data.json file to be significant enough to warrant emblazoning all the tracks, right?

Potential counterpoints:

But if the canonical-data.json file matches all tracks' existing tests anyway, why bother?

But it's not always the case! Remember I said in https://github.com/exercism/x-common/pull/510#issuecomment-275205381 I think we want the canonical tests to represent what we want the tests to be, which is not necessairly what they already are
And if track maintainers don't get a notification on a new canonical-data.json file, how will I tell the difference between "there was no significant change" versus "somebody just forgot to emblazon"?

I'm still against bulk blazoning.

Actively maintained tracks can watch the progress of things through x-common.
Active tracks can create scripts to check for canonical data updates. (I'm sure someone could come up with a git one-liner for this.)
Inactive tracks will just have dozens(hundreds?) of issues piling up in them.

Track specific opt-in blazoning could be OK I guess, I don't want to stop tracks that want automatic issues created from getting them.

Except x-common can be overwhelming. I got about 50 emails from just 3 exercism repos today, mostly x-common. I'd rather have an issue show up in my track, where I'm far more likely to pay attention to it.

@ErikSchierboom and @IanWhitney I think that @Insti's suggestion of having an opt-in blazon could be a good compromise. It would have to be automated to ensure that checkins aren't missed though. In terms of minimizing the amount of issues that would get created, is there a way to programatically determine which changes are "important" vs description modifications?
@Insti if I play devil's advocate for a minute, what's the purpose of creating and maintaining the canonical data if we're not ensuring it gets integrated in the different tracks? My understanding was that this canonical data is used to ensure there's cross track consistency.

I do get an influx of e-mail (but I use the terminal, so it is a few keypresses to processes the hundreds of repository related email every day.  But to coordinate I use the web based notifications and zenhub's todo (That last link will work properly if you use zenhub, otherwise it is "ignored".)

... This is partially due to the fact that canonical data updates are mixed with other types of updates, like description modifications and such...

Semantic versioning of test data would be great, and could also be used in a track-specific solution to match its versions against x-common.

Semantic versioning of test data would be great, and could also be used in a track-specific solution to match its versions against x-common.

Absolutely! Great idea.

This does not solve the original problem (propagating changes), but I guess it may solve part of it (what changed?) #673


Serialize private keys (and encrypted private keys) with checksums

https://github.com/BitShares/bitshares/issues/1219#issuecomment-69399989

Just refer to #1219 instead.


argument of type 'Endpoint' is not iterable

poseidon/poseidonMonitor.py line 98, in schedule_job_reinvestigation
if 'state' in my_value:

Can you verify that this is still a problem.

fixed, thanks!


MMap::MapImage maps image twice on Win10x64

On Windows 10 x64, manually mapping a buffer into a remote process works, however the image is mapped twice (or two threads are created, not sure which). I have been using this on Windows 7 x64 for months without this double mapping.
The issue is easily reproduced by using 	TestMMapFromMem() in the TestApp executable. There, cmd is mapped into the current process. After 30s control is given back to the parent, and one can see "Successfully mapped image, unmapping", however at that point the image is mapped a second time. Here is the application trace:
Manual image mapping from buffer test
Trying to map C:\windows\system32\cmd.exe into current process
BlackBone: ManualMap: Mapping image 'MemoryImage_0x01020000' with flags 0x4042
BlackBone: ManualMap: Loading new image 'MemoryImage_0x01020000'
BlackBone: ManualMap: Image base allocated at 0x011C0000
BlackBone: ManualMap: Performing image copy
BlackBone: ManualMap: Relocating image 'MemoryImage_0x01020000'
BlackBone: ManualMap: Enabling exception support for image 'MemoryImage_0x01020000'
BlackBone: ManualMap: Performing security cookie initializtion for image 'MemoryImage_0x01020000'
BlackBone: ManualMap: Rebasing process to address 0x011C0000
BlackBone: ManualMap: Calling entry point for 'MemoryImage_0x01020000', Reason: 1
The system cannot find message text for message number 0x2350 in the message file for Application.

(c) 2015 Microsoft Corporation. All rights reserved.

C:\reversing\Blackbone\build\Win32\Debug>

Successfully mapped, unmapping
BlackBone: ManualMap: Unmapping image 'MemoryImage_0x01020000'
BlackBone: ManualMap: Calling entry point for 'MemoryImage_0x01020000', Reason: 0
The system cannot find message text for message number 0x2350 in the message file for Application.

(c) 2015 Microsoft Corporation. All rights reserved.

C:\reversing\Blackbone\build\Win32\Debug>

BlackBone: ManualMap: Disabling exception support for image 'MemoryImage_0x01020000'

C:\reversing\Blackbone\build\Win32\Debug>

I wanted to leave it out of the issue, but the comment section afford me a separate opportunity: This is a masterpiece of a library. Well done DarthTon! Many of the techniques you employ have been quite helpful in honing my abilities, and I am very thankful.

That's because it's an exe. Entry point is called upon unmapping with DLL_PROCESS_DETACH reason, but in exe there is no such thing as DLL_PROCESS_DETACH, and cmd just executes normally once more. Shouldn't be an issue when mapping dlls.

I agree that an exe will be called a second time from the DLL_PROCESS_DETACH call, however, the second mapping (or thread creation) is occurring on the call to DLL_PROCESS_ATTACH. You can reproduce this by removing all calls to DLL_PROCESS_DETACH (ie, remove calls to UnmapAllModules()). Still the exe is mapped twice.
The issue is coming from
            if (!RunModuleInitializers( img.get(), DLL_PROCESS_ATTACH ))
                return nullptr;

inside MMap::MapImageInternal. I see different behavior with this call in Win7 vs Win10. In windows 7, if I comment out this call, the exe is never mapped and the application closes. In windows 10, if I comment out this function call, the exe is this time mapped (presumably by FindOrMapModule), and only once! If I uncomment this line (how it is originally), the image is mapped a single time in Win7, and twice in Win10.

Here are the investigation results.
In win10 LdrShutdown process started to call module initializer upon process termination. Since image is mapped with 'CreateLdrRef' flag, its initializer gets called upon process termination.

Ah, I see. Tricky. Well, thank you for these results.


eliminate jQuery

There are security problems with jQuery 1.4.4, so it is time to get rid of it.

Thanks for the update, Bob! I pushed a couple very minor suggestions to a like-named branch.

Thanks for the suggestions, which I incorporated this morning!


fix(notify): 添加消息来源

What this PR does / why we need it:

Does this PR need to be backport to the previous release branch?:

/cc @ioito @swordqiu

/lgtm


karavictl list/get powermax

Description
This PR adds support for listing/getting PowerMax arrays, filtering the storage list output by storage type, and enforcing arguments when getting storage.
List all storage:
karavictl storage list
List powerflex storage:
karavictl storage list --type powerflex
List powermax storage:
karavictl storage list --type powermax
The karavictl storage get command now does not default to powerflex. You must supply a storage type and system-id. Otherwise, you will see errors such as error: system type not specified and error: system type not specified.
There is a new secret in cmd/karavictl/cmd/testdata called kubectl_get_secret_storage_powerflex_powermax.json with the following secret data in storage-systems.yaml. The powermax ID is quoted because otherwise the ID will show as "1.9790072e+08" in the JSON output.
storage:
  powermax:
    "000197900714":
      Endpoint: https://localhost
      Insecure: true
      Pass: Password123
      User: admin
  powerflex:
    542a2d5f5122210f:
      Endpoint: https://localhost
      Insecure: true
      Pass: Password123
      User: admin

Issues
List the issues impacted by this PR:

Issue ID

#72

Checklist:

[x] I have performed a self-review of my own changes.

go test -count=1 -cover -race -timeout 30s -short ./...
?       karavi-authorization/cmd/karavictl      [no test files]
ok      karavi-authorization/cmd/karavictl/cmd  4.301s  coverage: 57.6% of statements
ok      karavi-authorization/cmd/proxy-server   0.067s  coverage: 0.7% of statements
?       karavi-authorization/cmd/sidecar-proxy  [no test files]
?       karavi-authorization/cmd/tenant-service [no test files]
ok      karavi-authorization/deploy     0.095s  coverage: 84.6% of statements
?       karavi-authorization/internal/decision  [no test files]
ok      karavi-authorization/internal/powerflex 9.091s  coverage: 88.9% of statements
ok      karavi-authorization/internal/proxy     6.607s  coverage: 68.0% of statements
ok      karavi-authorization/internal/quota     0.369s  coverage: 92.6% of statements
ok      karavi-authorization/internal/roles     0.048s  coverage: 96.0% of statements
ok      karavi-authorization/internal/tenantsvc 1.805s  coverage: 82.9% of statements
ok      karavi-authorization/internal/token     0.041s  coverage: 90.0% of statements
ok      karavi-authorization/internal/web       0.047s  coverage: 24.1% of statements
?       karavi-authorization/pb [no test files]

@atye: Thank you for submitting your pull request!
Please make sure you have followed our contributing guidelines. We will review it as soon as possible.

We want your feedback! If you have any questions or suggestions regarding our contributing process/workflow, please reach out to us at<EMAIL_ADDRESS>

For consistency, can we quote all that storage system IDs instead of just the PowerMax ones?

For consistency, can we quote all that storage system IDs instead of just the PowerMax ones?

We hit this issue because the PowerMax system IDs appear to be all numbers which seem to get interpreted as numbers in the JSON output; thus we see the scientific notation.
If we quote all IDs when creating storage, we'll get escape characters in the JSON output which looks messy. I'll think about this.
{
  "storage": {
    "powerflex": {
      "\"09315f941b2a200f\"": {
        "Endpoint": "https://<IP_ADDRESS>",
        "Insecure": false,
        "Password": "(omitted)",
        "User": "admin"
      }
    }
  }
}

For consistency, can we quote all that storage system IDs instead of just the PowerMax ones?

We hit this issue because the PowerMax system IDs appear to be all numbers which seem to get interpreted as numbers when we save it in the k8s secret; thus we see the scientific notation when reading it because the IDs start with 000.
If we quote all IDs when creating storage, we'll get escape characters in the JSON output which looks messy. I'll think about this.
{
  "storage": {
    "powerflex": {
      "\"09315f941b2a200f\"": {
        "Endpoint": "https://<IP_ADDRESS>",
        "Insecure": false,
        "Password": "(omitted)",
        "User": "admin"
      }
    }
  }
}

This is resolved.