OnDelete: 'cascade' is not applied during CLI schema update

Describe the bug
I added an onDelete: 'cascade' property to a @ManyToOne relationship, but when I ran mikro-orm schema:update -r, the foreign key relationship was not updated.
This is on PostgreSQL.
Example Entities:
@Entity()
export class SignUp extends BaseModel {

    @ManyToOne()
    user: User;

    @ManyToOne({onDelete: 'cascade'}) // This was empty before the update command
    event: Event;
}

@Entity()
export class Event extends BaseModel{

    @Property()
    title: string;

    @Property()
    startDate: number;

    @Property({nullable: true})
    endDate?: number;
}

@Entity({abstract: true})
export abstract class BaseModel {
    @PrimaryKey()
    public id: string = v4();
}

Stack trace
[query] delete from "event" where "id" in ('eb47e4bc-4fa3-4b74-bc15-f87ca7b58921') [took 7 ms]
[query] rollback
[2021-10-30T18:23:59.856Z] ERROR: ForeignKeyConstraintViolationException: delete from "event" where "id" in ('eb47e4bc-4fa3-4b74-bc15-f87ca7b58921') - update or delete on table "event" violates foreign key constraint "sign_up_ev
ent_id_foreign" on table "sign_up"
    at PostgreSqlExceptionConverter.convertException (C:\Workspace\volunteerbackend\node_modules\@mikro-orm\postgresql\PostgreSqlExceptionConverter.js:26:24)
    at PostgreSqlDriver.convertException (C:\Workspace\volunteerbackend\node_modules\@mikro-orm\core\drivers\DatabaseDriver.js:202:54)
    at C:\Workspace\volunteerbackend\node_modules\@mikro-orm\core\drivers\DatabaseDriver.js:206:24
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
    at async ChangeSetPersister.executeDeletes (C:\Workspace\volunteerbackend\node_modules\@mikro-orm\core\unit-of-work\ChangeSetPersister.js:44:13)
    at async UnitOfWork.commitDeleteChangeSets (C:\Workspace\volunteerbackend\node_modules\@mikro-orm\core\unit-of-work\UnitOfWork.js:558:9)
    at async UnitOfWork.persistToDatabase (C:\Workspace\volunteerbackend\node_modules\@mikro-orm\core\unit-of-work\UnitOfWork.js:501:13)
    at async PostgreSqlConnection.transactional (C:\Workspace\volunteerbackend\node_modules\@mikro-orm\knex\AbstractSqlConnection.js:53:25)
    at async UnitOfWork.commit (C:\Workspace\volunteerbackend\node_modules\@mikro-orm\core\unit-of-work\UnitOfWork.js:184:17)
    at async SqlEntityManager.flush (C:\Workspace\volunteerbackend\node_modules\@mikro-orm\core\EntityManager.js:497:9)

previous error: delete from "event" where "id" in ('eb47e4bc-4fa3-4b74-bc15-f87ca7b58921') - update or delete on table "event" violates foreign key constraint "sign_up_event_id_foreign" on table "sign_up"
    at Parser.parseErrorMessage (C:\Workspace\volunteerbackend\node_modules\pg-protocol\src\parser.ts:369:69)
    at Parser.handlePacket (C:\Workspace\volunteerbackend\node_modules\pg-protocol\src\parser.ts:188:21)
    at Parser.parse (C:\Workspace\volunteerbackend\node_modules\pg-protocol\src\parser.ts:103:30)
    at Socket.<anonymous> (C:\Workspace\volunteerbackend\node_modules\pg-protocol\src\index.ts:7:48)
    at Socket.emit (events.js:315:20)
    at Socket.EventEmitter.emit (domain.js:467:12)
    at addChunk (internal/streams/readable.js:309:12)
    at readableAddChunk (internal/streams/readable.js:284:9)
    at Socket.Readable.push (internal/streams/readable.js:223:10)
    at TCP.onStreamRead (internal/stream_base_commons.js:188:23) {
  length: 314,
  severity: 'ERROR',
  code: '23503',
  detail: 'Key (id)=(eb47e4bc-4fa3-4b74-bc15-f87ca7b58921) is still referenced from table "sign_up".',
  hint: undefined,
  position: undefined,
  internalPosition: undefined,
  internalQuery: undefined,
  where: undefined,
  schema: 'public',
  table: 'sign_up',
  column: undefined,
  dataType: undefined,
  constraint: 'sign_up_event_id_foreign',
  file: 'ri_triggers.c',
  line: '2490',
  routine: 'ri_ReportViolation'
}

To Reproduce
Steps to reproduce the behavior:

Create two entities, one with a @ManyToOne relationship to the other
Create the schema via CLI
Add a onDelete: 'cascade' property to the @ManyToOne definition
Run the CLI update command mikro-orm schema:update -r

Expected behavior
The foreign key relationship was updated to use an ON DELETE CASCADE method.
Additional context
If the table is dropped and recreated with the same mikro-orm schema:update -r command, the ON CASCADE DELETE exists.
Versions

Dependency
Version

node
14.15.4

typescript
4.4.4

mikro-orm
4.5.9

your-driver
4.5.9

Fixed in v5, no plans to backport schema related fixes as the changes are too incompatible.


JBPM-5336 - Support for rolling updates in kie server

@cristianonicolai could you please have a look?
description and use case can be found in this article

can anyone have a look at this?

@mswiderski Sorry I missed the first comment, I'll take a look on this.


Error: [Reanimated] valueUnpacker is not a worklet, js engine: hermes

Is there anyone knowns how to resovle this error ?
I had to use<EMAIL_ADDRESS>,maybe that is the problem ?

Hi @sunzhaoyang<EMAIL_ADDRESS>is unstable, please try again when this PR is released: https://github.com/software-mansion/react-native-reanimated/pull/5087

hey @sunzhaoyang<EMAIL_ADDRESS>is out, please install it and try again

@efstathiosntonas I got the same error message with<EMAIL_ADDRESS>"@georstat/react-native-image-cache": "^3.1.0",
"react-native-file-access": "^3.0.4",
"react-native-reanimated": "^3.5.2",

"react": "18.2.0",
"react-native": "0.72.4",

@tab can you try yarn start —reset-cache?
Unfortunately this was a reanimated issue that is fixed on 3.5.2, on our apps we do not get this bug.

I am having the same error using reanimated ^3.5.2 , still no clue how to solve it

@Salmahana have you tried yarn start —reset-cache?

Hello, I have the same issue.I installed the latest version by npm install react-native-reanimated@latest  and added ```
module.exports = function (api) {
api.cache(true);
return {
presets: ['babel-preset-expo'],
plugins: ['react-native-reanimated/plugin'],
};
};
in  babel.config.js and clear cache also but the same issue is there. Any help?

Hey folks, please create an issue on the reanimated repo, this is not an issue with this lib, we don’t use something weird or complex on our code with reanimated, if there’s a bug it’s on their side, not ours.

Had the same issue while upgrading RN app. I found this solution on stackoveflow to be working.

I had the same issue and I fixed it with a version downgrade:
npm install<EMAIL_ADDRESS><EMAIL_ADDRESS>And editing the bebel.config.js file:
  presets: ['module:metro-react-native-babel-preset'],
  plugins: ['react-native-reanimated/plugin'],
}; ```

How i can get back my console?

@shamaskaramat Hi,  what do you mean by getting back your console?

Solutions:
add to babel.config.js
module.exports = {
presets: ['module:metro-react-native-babel-preset'],
plugins: [
'react-native-reanimated/plugin',
],
};
and
npx react-native start --reset-cache
👍

What fixed it for me was:

npx expo install react-native-gesture-handler react-native-reanimated
Adding the before mentioned line plugins: ['react-native-reanimated/plugin'], to the Babel.config.js file.
Then clearing the Metro Bundler cache with yarn start --reset-cache

it's working! BTW i am using "react": "18.2.0", "react-native-router-flux": "^4.3.1", "react-native-reanimated": "^3.5.4", "react-native-gesture-handler": "^2.13.1",

Modifique mi archivo babel.config.js
module.exports = function (api) {
api.cache(true);
return {
presets: ['babel-preset-expo'],
plugins: ['react-native-reanimated/plugin'],
};
};

I had the same issue and I fixed it with a version downgrade:
npm install<EMAIL_ADDRESS><EMAIL_ADDRESS>And editing the babel.config.js file:
module.exports = {
  presets: ['module:metro-react-native-babel-preset'],
  plugins: ['react-native-reanimated/plugin'],
};

This solution worked for me. Thanks

2. plugins: ['react-native-reanimated/plugin']

Thank you
It works for expo

I had the same issue and I fixed it with a version downgrade:
npm install<EMAIL_ADDRESS><EMAIL_ADDRESS>And editing the babel.config.js file:
module.exports = {
  presets: ['module:metro-react-native-babel-preset'],
  plugins: ['react-native-reanimated/plugin'],
};

it works for me


A possible enhancement in code samples

Is there an existing issue for this?

[X] I have searched the existing issues

Is your feature request related to a problem? Please describe the problem.
As a user of a component set, I pay attention to the demos first and then to the code samples. Usually, my starting point is to use a ready-made sample component. And I expect the provided code to work with minimal changes.
In this regard, it seems that the code example for "Basic List with custom role and class"(or probably many other samples) can be improved. it has a build error.

In the first place, I couldn't run this code sample on my page because :

there is no "People" array object defined in the code sample so I had a build error.
Peope[1] is used in another demo and it made me confused at first glance.
it needs some styles to make the output of code like the real demo.
PS
At the moment I have no problems using it and I am sharing this feedback only to improve the documentation.

Describe the solution you'd like
I prefer to have something like this:
<BitBasicList Items="People"
              Virtualize="true"
              Role="list"
              class="p-10 grid grid-cols-1 sm:grid-cols-1 md:grid-cols-3 lg:grid-cols-3 xl:grid-cols-3 gap-5">
    <RowTemplate Context="person">

            Id<EMAIL_ADDRESS>            Full Name<EMAIL_ADDRESS>            Job<EMAIL_ADDRESS>

    </RowTemplate>
</BitBasicList>

@code {
    List<Person> People = new();
    protected override void OnInitialized()
    {
        Person person = new();

        People = person.GetPeople(8000);

        base.OnInitialized();
    }

    public class Person
    {
        public int Id { get; set; }
        public string FirstName { get; set; }
        public string LastName { get; set; }
        public string Job { get; set; }

        public List<Person> GetPeople(int itemCount)
        {
            List<Person> people = new();

            for (int i = 0; i < itemCount; i++)
            {
                people.Add(new Person
                    {
                        Id = i + 1,
                        FirstName = $"Person {i + 1}",
                        LastName = $"Person Family {i + 1}",
                        Job = $"Programmer {i + 1}"
                    });
            }

            return people;
        }
    }
}

Additional context
No response

Thanks for sharing your feedback
Is it possible for you to submit a PR for this?

Thanks for sharing your feedback Is it possible for you to submit a PR for this?

Let me check the code, if modifying it does not affect other codes, I will be happy to do so


[SPARK-31642] Add Pagination Support for Structured Streaming Page

What changes were proposed in this pull request?
Add Pagination Support for structured streaming page. Now both tables Active Queries and Completed Queries will have pagination.
To implement pagination, pagination framework from #7399  is used.

Also tables will only be shown if there is at least one entry in the table.

Why are the changes needed?

This will help users in analysing their structured streaming queries in much better way.
Other Web UI pages support pagination in their table. So this will make web UI more consistent across pages.
This can prevent potential OOM errors.

Does this PR introduce any user-facing change?
Yes. Both tables will support pagination.

How was this patch tested?
Manually. I will add snapshots soon.

cc @srowen @zsxwing @sarutak @uncleGen Kindly Review

Can one of the admins verify this patch?

Can one of the admins verify this patch?

ok to test

cc @gengliangwang as well

Test build #122469 has started for PR 28485 at commit df61b7c.

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-K8s/27130/
Test PASSed.

Test build #122469 has finished for PR 28485 at commit df61b7c.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class StreamingQueryPagedTable(
case class StructuredStreamingRow(
class StreamingQueryDataSource(uiData: Seq[StreamingQueryUIData], sortColumn: String, desc: Boolean,

Merged build finished. Test FAILed.

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

retest this please

Jenkins retest this please

Test build #122479 has started for PR 28485 at commit df61b7c.

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-K8s/27140/
Test PASSed.

Test build #122479 has finished for PR 28485 at commit df61b7c.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class StreamingQueryPagedTable(
case class StructuredStreamingRow(
class StreamingQueryDataSource(uiData: Seq[StreamingQueryUIData], sortColumn: String, desc: Boolean,

Merged build finished. Test FAILed.

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

Retest this please. Seems like an unrelated failure and will fixed in #28391

Jenkins retest this please

Test build #122485 has started for PR 28485 at commit df61b7c.

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-K8s/27146/
Test PASSed.

Test build #122485 has finished for PR 28485 at commit df61b7c.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class StreamingQueryPagedTable(
case class StructuredStreamingRow(
class StreamingQueryDataSource(uiData: Seq[StreamingQueryUIData], sortColumn: String, desc: Boolean,

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/122485/
Test PASSed.

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-K8s/27154/
Test PASSed.

Test build #122493 has started for PR 28485 at commit 2486177.

Test build #122493 has finished for PR 28485 at commit 2486177.

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/122493/
Test PASSed.

LGTM. Pending on #28512 accepted and then update this PR.

@srowen @sarutak @uncleGen This PR has been updated.

Test build #122941 has started for PR 28485 at commit 088c551.

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-K8s/27583/
Test PASSed.

Test build #122941 has finished for PR 28485 at commit 088c551.

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/122941/
Test PASSed.

Jenkins retest this please

Test build #123008 has started for PR 28485 at commit 088c551.

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-K8s/27651/
Test PASSed.

Test build #123008 has finished for PR 28485 at commit 088c551.

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/123008/
Test PASSed.

I've merged to master.
Thanks @iRakson !

Thank You 😊 @sarutak @srowen @uncleGen

. I will add snapshots soon.

@iRakson could you update the PR description with the screenshot.

@iRakson could you update the PR description with the screenshot.

Updated.


invalid java runtime configuration

youve definitly gotten questions about this before but im having trouble finding actual answers just through watching other peoples question about it or googling it so i thought i might send my own version of the question. i try to run the game with the mods required for better nether and better end: fabric and BCLib (sometimes plus mod menu) but without BCLib it says i require it and with it the game crashes and gives me the whole "invalid java runtime configuration" message and i dont know what to do to fix it.
2022-03-03-7.log.gz

You are loading Minecraft 1.18.2, with mods for 1.17, with java 16. As a result it doesn't work. Use mods versions only with correct MC version and correct Java version (for 1.18 it will be java 17)

thanks :)


D435I IMU Calibration Not Accurate

Required Info

Camera Model
D435I

Firmware Version
5.11.11

Operating System & Version
Win10

Kernel Version (Linux Only)

Platform
PC

SDK Version
stable 2.21.0

Language
python

Segment
Robot

Issue Description
I have attempted to calibrate the D435I IMU using the rs_imu_calib.py script. In order to ensure that the camera is held stationary and level, a tripod with bubble levels was used to orient the camera during the calibration process. After calibration, the acceleration reported in the Y direction is different depending on the orientation of the camera. The acceleration reads 9.4 m/s^2 along the +Y axis, and flipping it around gives a reading of 10.4 m/s^2 on the -Y axis. Additionally, the normalized acceleration from the RealSense Viewer is reported as 9.6 m/s^2, which is not close to 9.80 m/s^2.
Here is the output from the rs_imu_calib.py script post-calibration:

The calibration script states that the norm fixed data is very close to gravity, but it does not appear that way in the RealSense Viewer. I have a feeling that the calibration procedure was carried out properly, and some sort of issue is stemming from the RealSense Viewer or our camera hardware.
Thank you for your time.

If you are trying to calibrate the camera in a downward-facing position, Alexandra from the Intel Support forum had this to say to another user attempting to calibrate the D435i in a downward-looking orientation:
"Calibrating the IMU for a downward facing position will not be possible ... our calibration for the IMU will calibrate it upright, that’s our configuration or expected configuration.  You would have to do some compensations in SW on your own to translate the data into downward facing looking camera".

Thank you for your reply, Marty.
I think I may not have described the issue properly.
When held in position 5 (these images were taken from the IMU calibration whitepaper) we get a reading of 9.4 m/s^2.

When held in position 6 we get a reading of 10.4 m/s^2.

We are confused on why this is occurring post-calibration. We have only followed the instructions of the rs_calib.py, and it reports that the data has been fixed properly, but that is not the case when viewing the accel/gyro streams in the RealSense Viewer.
Thank you for your time.

Thank you very much for the clarification.
Are you able to achieve more consistent results if you test the IMU with the rs-motion demo, please?
https://github.com/IntelRealSense/librealsense/issues/4391#issuecomment-509921061

The rs-motion demo seems to behave reasonably. I am not sure how such a discrepancy between the reported acceleration in the RealSense Viewer and the rs-motion demo can exist.
I wrote a program to poll my D435i for motion frames and print out the normalized magnitude of the acceleration, and it matches up with what the RealSense viewer reports for Position 5 and 6 above.
Do you have any inkling on what the issue could be?
Thank you for your time MartyG!

The rs-motion documentation suggests that it uses something called a Complementary Filter to stabilize the data.  To quote:

We use an approximate version of Complementary Filter to balance gyroscope and accelerometer results. Gyroscope gives generally accurate motion data, but it tends to drift, not returning to zero when the system goes back to its original position. Accelerometer, on the other hand, doesn't have this problem, but its signals are not as smooth and are easily affected by noises and disturbances. We use alpha to aggregate the data. New theta is the combination of the previous angle adjusted by difference computed from gyroscope data, and the angle calculated from accelerometer data. Note that this calculation does not apply to the Y component of theta, since it is measured by gyroscope only.

@gorshborsh, can you share the IMU intrinsic calibration ?

rs-enumerate-devices -c

When the IMU calibration is performed and flushed to D435i's memory a new "Motion Correction" option would appear in realsense-viewer under the "Motion Module" branch.
Toggling this will change the IMU values, and in case of a properly performed IMU-calibration should  bring the accelerometer's norm close to the expected 9.8.
In the attached screenshot I manage to get a reasonable 9.65 with self-calibration on my desk.

The code that controls this is rs:options API RS2_OPTION_ENABLE_MOTION_CORRECTION

@gorshborsh , did you manage to verify the IMU calibration as specified ?
Please update


Improvements on React-App UI

Dashboards for Submitter and Validator
Mongo Connections for interacting with the smart contract

pls assign this issue to me


replace hash routine md5 with sha256

swapping out the md5 hash routine with sha256 (truncated to 32 chars)
and base64url encoded.
this allows jest to run on a system where openssl is in a fips enabled
mode.
Summary
https://github.com/facebook/jest/issues/10726
Test plan
ran e2e tests.

I'm unable to find any way of actually testing this (and not even any eslint rule to ban md5), so this is a best effort thing that will probably break. However, can land for now to hopefully unblock folks

If you have redhat 8 running in a VM or something, enabling fips mode is pretty easy:
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/security_hardening/using-the-system-wide-cryptographic-policies_security-hardening#switching-the-system-to-fips-mode_using-the-system-wide-cryptographic-policies
Its a bit trickier in a docker image, because there is a kernel boot flag involved, which you can't set independently for a docker container.
The reason we actually got his by this, is because the host running our jenkins / kubernetes build cluster is in fips mode - and when we deployed a redhat 8 image into it as a builder, the 'fips=1' flag from the kernel would be seen in the container, and that was enough to trigger openssl to go into fips mode inside the container.
I couldn't find any way to get openssl to come back out of fips mode when it saw that kernel flag.

If we could get something running on GH Actions, that'd be awesome. Or some other CI provider I guess


Relative image/attachement links

Hey,
Otterwiki seems like a great project and we want to switch to it from our old wiki.
During the switch I noticed something:
In the preview, relative links to images worked, i.e. if I upload an image as an attachement for a page and add a relative image-link, the image is displayed correctly. On the finished page, the image is not displayed. To be displayed on the finished page, an absolute link is required.
So the question: Are relative links to attachements supposed to work?

Ok, after thinking about it a bit here is what I think happens:
Otterwiki just pastes the link form the image link into an image tag. So we get
<img src="relative-path.jpg" />

This assumes it is in the same directory, so if this is on page www.my-otterwiki.com/chapter/page it tries to load www.my-otterwiki.com/chapter/relative-path.jpg. When editing, the link changes to www.my-otterwiki.com/chapter/page/edit, which leads the relative img-tag to search in www.my-otterwiki.com/chapter/page; which is coincidentally correct.
This probably means it is not supposed to work in either. And while a relative link pagename/relative-path.jpg would work, it would break in preview. So relative paths are just not supported properly.

Hey @Kilidsch, thank you for bringing this up.
It would be nice to be able to reference attachments not with the full path,
e.g.
![](/Example/a/example.png)

but relative:
![](example.png)

or
![](./example.png)

Currently the renderer knows nothing about the path of the page it's rendering, will have to look into it to find a nice solution.


new to OSX, tell EA to open on current space?

Hi again! been using EA for months on linux and lovin' it :)
Now at work have to use OSX and it works well. only issue is that emacs is always on space #1 and chrome on space #2. when i launch EA it takes me automatically to space #1 where EA opens.
Anyway to define the EA frame to open on the current space where it was launched from?
thx!!
Z

Hey buddy 👋 it’s been a while.
I’m aware of this issue. I have yet to look into a solution to this problem. If you look at the source code for this tool you will see that it’s a tower of dirty hacks and the solution to this issue, if it exists, will be another dirty hack. If it is possible to get the workspace number of the active window from System Events via AppleScript and if it’s possible to tell emacsclient to launch the new frame in a particular workspace, then I think we can resolve this issue.
I’m currently very busy on other projects at this time, but if someone else looks into the two requisites I mentioned and report back, it’d be a big help. Otherwise, it will be a few weeks before I have the time to look into this.
@zeltak, you’re awesome! Thank you for your continued involvement and your contributions to the project. You’re an official EA superstar! 💫

I know this answer is a bit late, but this sounds like a similar problem I was having. This might not be an EA issue. I assigned Emacs to this desktop (through the options menu from the dock in Mac OS) so I would have windows in the right place at startup. So anytime Emacs launched a new frame (like EA), the frame would pop up on the assigned desktop instead of where it was called from. I just unassigned Emacs and EA worked perfectly.


URL Shortner: Bug

URL Shortner is not working properly. Its not showing short URL .
See the screenshot below:

@urvashi-code1255 I would love to solve this bug. Could you plz assign this issue to me as a part of Gssoc'21?

Sure go for it @kunal299 :)

@urvashi-code1255 But our coding period will start on 8th march.

@urvashi-code1255 will it be fine?

Yes you can send a PR and I will review and merge it after 8!

Yes you can send a PR and I will review and merge it after 8!

ok

@urvashi-code1255 I've solved the bug, can you please assign me the issue so that I can me my first PR.


Script for releasing game (initial addition)

A script should be created to facilitate providing a released or releasable version of the game.
It should use the copy script (and not use its renaming parameters).
The script should be called release.py.
Parameters:

Optionally, it should take a source path as the first parameter.

If a source path is provided, it will instruct the copy script to use the provided path. If the root directory of the provided path does not exist, it should create it.
By default, if no source path is provided, a root level subdirectory called "build" should be used. The build directory should be deleted if it already exists.
The copy script will function as it normally does. However, immediately after copying, the copied project's "tools" directory should be deleted. All references to such tool scripts used within the release.py script should come from the originating / working project.
In the future, this script will have other parameters which will indicate how the game project is to be released. For example,

Whether / how to minify the project.
Provide a release target type, which may affect how the released version is packaged (eg zipped, etc.).

@thrabchak, I just moved the contents of www back into root directory (5c6594f4e73118cf976b0154355e516bc80e864b). All is well with building cordova android and browser from root directory, provided the following files are copied to a subdirectory called www:

assets
src
index.html
style.css
package.json

This same set of files is what would be needed for a NW JS based build.
Feel free to update this enhancement's description as necessary to fit the grunt approach.

Closing enhancement.
The status of this project's build and release system is in an early preliminary stage and the technology it is using is shifting from relying on Python and BASH scripts.
A decision needs to be made on where builds are stored and where releases are stored, as well as in what form.
The "release" aspect for this project needs to be rethought and a new enhancement should be filed.


ng update @angular/cli installs angular 8.2.0-next.0

🐞 Bug report
Command (mark with an x)

- [ ] new
- [ ] build
- [ ] serve
- [ ] test
- [ ] e2e
- [ ] generate
- [ ] add
- [x] update
- [ ] lint
- [ ] xi18n
- [ ] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc

Is this a regression?

 Yes, the previous version in which this bug was not present was: ....
Updating angular cli from 8.0.6 to 8.1.0 also updates other angular packages to 8.2.0-next.0 (nextnpm tag)
Description
 A clear and concise description of the problem...
The cli should update to latest instead of next npm tag.
🔬 Minimal Reproduction

create a angular workspace with angular 8.0.6 and upgrade to 8.1.0
npx -p<EMAIL_ADDRESS>ng new bug
cd bug
npx -p<EMAIL_ADDRESS>ng update @angular/cli

🔥 Exception or Error

Using package manager: 'yarn'
Collecting installed dependencies...
Found 81 dependencies.
Fetching dependency metadata from registry...
  Package "ng-packagr" has an incompatible peer dependency to "@angular/compiler-cli" (requires "^6.0.0 || ^7.0.0 || ^8.0.0-beta.0 || ^8.1.0-beta.0" (extended), would install "8.2.0-next.0").
  Package "@angular/cdk" has an incompatible peer dependency to "@angular/common" (requires "^8.0.0 || ^9.0.0-0" (extended), would install "8.2.0-next.0").
  Package "jest-preset-angular" has an incompatible peer dependency to "@angular/core" (requires ">=2.0.0", would install "8.2.0-next.0").
  Package "ng-packagr" has an incompatible peer dependency to "@angular/compiler" (requires "^6.0.0 || ^7.0.0 || ^8.0.0-beta.0 || ^8.1.0-beta.0" (extended), would install "8.2.0-next.0").
  Package "jest-preset-angular" has an incompatible peer dependency to "@angular/platform-browser-dynamic" (requires ">=2.0.0", would install "8.2.0-next.0").
Incompatible peer dependencies found.
Peer dependency warnings when installing dependencies means that those dependencies might not work correctly together.
You can use the '--force' option to ignore incompatible peer dependencies and instead address these warnings later.

🌍 Your Environment

Angular CLI: 8.0.6
Node: 10.15.0
OS: win32 x64
Angular: 8.1.0
... animations, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router

Package                            Version
------------------------------------------------------------
@angular-devkit/architect          0.800.6
@angular-devkit/build-angular      0.800.6
@angular-devkit/build-ng-packagr   0.800.6
@angular-devkit/build-optimizer    0.800.6
@angular-devkit/build-webpack      0.800.6
@angular-devkit/core               8.0.6
@angular-devkit/schematics         8.0.1
@angular/cdk                       8.0.2
@angular/cli                       8.0.6
@ngtools/json-schema               1.2.0
@ngtools/webpack                   8.0.6
@schematics/angular                8.0.1
@schematics/update                 0.800.6
ng-packagr                         5.3.0
rxjs                               6.5.2
typescript                         3.4.5
webpack                            4.30.0

Anything else relevant?

Same error.

I had the exact same issue, but resolved now .
My environment was:
Angular CLI: 7.3.9
Node: 9.11.1
OS: linux x64
Angular: 8.1.0
... animations, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.13.9
@angular-devkit/build-angular     0.801.0
@angular-devkit/build-optimizer   0.801.0
@angular-devkit/build-webpack     0.801.0
@angular-devkit/core              7.3.9
@angular-devkit/schematics        7.3.9
@angular/cli                      7.3.9
@ngtools/webpack                  8.1.0
@schematics/angular               7.3.9
@schematics/update                0.13.9
rxjs                              6.5.2
typescript                        3.4.5
webpack                           4.35.2

ng update  showed me 1 package to update:
      Name                               Version                  Command to update
     --------------------------------------------------------------------------------
      @angular/cli                       7.3.9 -> 8.1.0           ng update @angular/cli

Running  ng update @angular/cli I would get this every time:
Package "ag-grid-angular" has an incompatible peer dependency to "@angular/compiler" (requires ">=2.1.x" (extended), would install "8.2.0-next.0").
Package "ag-grid-angular" has an incompatible peer dependency to "@angular/core" (requires ">=2.1.x" (extended), would install "8.2.0-next.0").

However when I ran ng update @angular/cli @angular/core, it did the trick, and updated the package.
My environment now is:
Angular CLI: 8.1.0
Node: 9.11.1
OS: linux x64
Angular: 8.1.0
... animations, cli, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.801.0
@angular-devkit/build-angular     0.801.0
@angular-devkit/build-optimizer   0.801.0
@angular-devkit/build-webpack     0.801.0
@angular-devkit/core              8.1.0
@angular-devkit/schematics        8.1.0
@ngtools/webpack                  8.1.0
@schematics/angular               8.1.0
@schematics/update                0.801.0
rxjs                              6.5.2
typescript                        3.4.5
webpack                           4.35.2

Could you provide the dependency sections of the project's package.json?

@clydin - sure, here they are:
"dependencies": {
   "@angular/animations": "~8.1.0",
   "@angular/common": "~8.1.0",
   "@angular/compiler": "~8.1.0",
   "@angular/core": "~8.1.0",
   "@angular/forms": "~8.1.0",
   "@angular/platform-browser": "~8.1.0",
   "@angular/platform-browser-dynamic": "~8.1.0",
   "@angular/router": "~8.1.0",
   "ag-grid-angular": "^21.0.1",
   "ag-grid-community": "^21.0.1",
   "ag-grid-enterprise": "^21.0.1",
   "core-js": "^2.6.9",
   "rxjs": "~6.5.2",
   "tslib": "^1.10.0",
   "zone.js": "~0.9.1"
 },
 "devDependencies": {
   "@angular-devkit/build-angular": "~0.801.0",
   "@angular/cli": "^8.1.0",
   "@angular/compiler-cli": "~8.1.0",
   "@angular/language-service": "~8.1.0",
   "@types/jasmine": "^3.3.13",
   "@types/jasminewd2": "~2.0.6",
   "@types/node": "^11.13.15",
   "codelyzer": "^5.0.1",
   "jasmine-core": "~3.3.0",
   "jasmine-spec-reporter": "~4.2.1",
   "karma": "~4.0.1",
   "karma-chrome-launcher": "~2.2.0",
   "karma-coverage-istanbul-reporter": "~2.0.5",
   "karma-jasmine": "~2.0.1",
   "karma-jasmine-html-reporter": "^1.4.2",
   "protractor": "~5.4.2",
   "ts-node": "~8.0.3",
   "tslint": "~5.14.0",
   "typescript": "~3.4.5"
 }

I have a similar issue. I installed @angular/cli 8.1.0 globally yesterday. Updated a project today using ng update @angular/cli, and it installed Angular 8.2.0-next.0 for all my dependencies.
"dependencies": {
    "@angular/animations": "8.2.0-next.0",
    "@angular/common": "8.2.0-next.0",
    "@angular/compiler": "8.2.0-next.0",
    "@angular/core": "8.2.0-next.0",
    "@angular/forms": "8.2.0-next.0",
    "@angular/platform-browser": "8.2.0-next.0",
    "@angular/platform-browser-dynamic": "8.2.0-next.0",
    "@angular/router": "8.2.0-next.0",
    "core-js": "^2.6.5",
    "rxjs": "^6.5.2",
    "tslib": "^1.9.3",
    "zone.js": "~0.9.1"
},
"devDependencies": {
    "@angular-devkit/build-angular": "~0.801.0",
    "@angular/cli": "8.1.0",
    "@angular/compiler-cli": "8.2.0-next.0",
    "@angular/language-service": "8.2.0-next.0",
    ...

My Angular versions were 8.0.3, the CLI version was 8.0.4.
The application built, and the unit tests passed, so I am not too worried. But, it is odd.

I had the same issue when updating from 7.2.14 to 8.1.0
Removing the @angular/http package fixed this for me (allowing me to run the ng update command)

npm un @angular/http

Removing @angular/http didn't work for me. Same with ng update @angular/cli @angular/core

Ive seen the same issue with my projects.

Same issue here...

Also happening here and I couldn't find a way to make ng update uninstall 8.2.0-next and install 8.1.0 instead. I had to manually change in package.json.

Same issue here, ng update cli and core didn't worked, don't want to remove @angulat/http

@krischan1410 you may update it to @angular/common/http as the v8 Upgrade Guideline says.
In the other hand, I'm seeing this error for every new minor release since some time ago, the CLI must discard the next releases :-?

Issue had fix when i use the following command with --force flag..
ng update @angular/cli @angular/core --force

@matheo Thanks for the hint: Now I see that I don't use @angular/http at all. So removing it is not a bug fix for my environment :-)

Same issue here:
Angular CLI: 8.0.6
Node: 10.16.0
OS: darwin x64
Angular: 8.1.0
... animations, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... platform-server, router

Package                            Version
------------------------------------------------------------
@angular-devkit/architect          0.800.6
@angular-devkit/build-angular      0.800.6
@angular-devkit/build-optimizer    0.800.6
@angular-devkit/build-webpack      0.800.6
@angular-devkit/core               8.0.6
@angular-devkit/schematics         8.0.6
@angular/cdk                       8.0.2
@angular/cli                       8.0.6
@angular/material                  8.0.2
@angular/material-moment-adapter   8.0.2
@ngtools/webpack                   8.0.6
@schematics/angular                8.0.6
@schematics/update                 0.800.6
rxjs                               6.5.2
typescript                         3.4.5
webpack                            4.30.0

Error when running ng update @angular/cli :
Using package manager: 'npm'
Collecting installed dependencies...
Found 55 dependencies.
Fetching dependency metadata from registry...
                  Package "@angular/material" has an incompatible peer dependency to "@angular/animations" (requires "^8.0.0 || ^9.0.0-0" (extended), would install "8.2.0-next.0").
                  Package "@angular/cdk" has an incompatible peer dependency to "@angular/core" (requires "^8.0.0 || ^9.0.0-0" (extended), would install "8.2.0-next.0").
                  Package "@angular/cdk" has an incompatible peer dependency to "@angular/common" (requires "^8.0.0 || ^9.0.0-0" (extended), would install "8.2.0-next.0").
                  Package "@angular/material" has an incompatible peer dependency to "@angular/forms" (requires "^8.0.0 || ^9.0.0-0" (extended), would install "8.2.0-next.0").
Incompatible peer dependencies found.
Peer dependency warnings when installing dependencies means that those dependencies might not work correctly together.
You can use the '--force' option to ignore incompatible peer dependencies and instead address these warnings later.

The following worked for me:

remove node_modules/ folder
remove package-lock.json
Edit the package.json file and set @angular/core to the latest patch version. I had version 8.1.1 installed so I set it to 8.1.0.
Call npm install
Then execute ng udate exactly like this: ng update @angular/cli @angular/core

I hope it works for you also.

@clydin @alan-agius4 Same issue with cli 8.1.1
OP sent a repro of the issue, were you able to reproduce it on your end ?
Found 43 dependencies.
    We analyzed your package.json, there are some packages to update:

      Name                               Version                  Command to update
     --------------------------------------------------------------------------------
      @angular/cli                       8.0.6 -> 8.1.1           ng update @angular/cli
      @angular/core                      8.1.0 -> 8.1.1           ng update @angular/core
      @ngrx/store                        8.0.1 -> 8.1.0           ng update @ngrx/store
🦁 ~/src/squid-web-app (upgrades)
$ ng update @angular/cli
Your global Angular CLI version (8.1.0) is greater than your local
version (8.0.6). The local Angular CLI version is used.

To disable this warning use "ng config -g cli.warnings.versionMismatch false".
Using package manager: 'npm'
Collecting installed dependencies...
Found 43 dependencies.
Fetching dependency metadata from registry...
                  Package "@angular/cdk" has an incompatible peer dependency to "@angular/common" (requires "^8.0.0 || ^9.0.0-0" (extended), would install "8.2.0-next.1").
                  Package "@angular/material" has an incompatible peer dependency to "@angular/animations" (requires "^8.0.0 || ^9.0.0-0" (extended), would install "8.2.0-next.1").
                  Package "@angular/material" has an incompatible peer dependency to "@angular/forms" (requires "^8.0.0 || ^9.0.0-0" (extended), would install "8.2.0-next.1").
                  Package "@angular/cdk" has an incompatible peer dependency to "@angular/core" (requires "^8.0.0 || ^9.0.0-0" (extended), would install "8.2.0-next.1").
Incompatible peer dependencies found.
Peer dependency warnings when installing dependencies means that those dependencies might not work correctly together.
You can use the '--force' option to ignore incompatible peer dependencies and instead address these warnings later.

@hugodes just one clarification, on 8.1.1 the message now shows that 8.2.0-next.1 would be installed instead of -next.0
Whatever the issue is, it's being dragged along with new versions.

Same issue here, please fix

Using package manager: 'npm'
Collecting installed dependencies...
Found 42 dependencies.
Fetching dependency metadata from registry...
                  Package "codelyzer" has an incompatible peer dependency to "@angular/core" (requires ">=2.3.1 <9.0.0 || >8.0.0-beta <9.0.0" (extended), would install "8.2.0-next.1").
                  Package "@angular/material" has an incompatible peer dependency to "@angular/animations" (requires "^8.0.0 || ^9.0.0-0" (extended), would install "8.2.0-next.1").
                  Package "@angular/material" has an incompatible peer dependency to "@angular/common" (requires "^8.0.0 || ^9.0.0-0" (extended), would install "8.2.0-next.1").
                  Package "@angular/material" has an incompatible peer dependency to "@angular/forms" (requires "^8.0.0 || ^9.0.0-0" (extended), would install "8.2.0-next.1").
                  Package "ng-packagr" has an incompatible peer dependency to "@angular/compiler-cli" (requires "^6.0.0 || ^7.0.0 || ^8.0.0-beta.0 || ^8.1.0-beta.0" (extended), would install "8.2.0-next.1").
                  Package "codelyzer" has an incompatible peer dependency to "@angular/compiler" (requires ">=2.3.1 <9.0.0 || >8.0.0-beta <9.0.0" (extended), would install "8.2.0-next.1").
Incompatible peer dependencies found.
Peer dependency warnings when installing dependencies means that those dependencies might not work correctly together.
You can use the '--force' option to ignore incompatible peer dependencies and instead address these warnings later.

Same issue

with 8.1.2 version have the same issue.

For me the error appeared using @angular/cli installed globally. Installing locally solved my problem

npm install<EMAIL_ADDRESS>npx ng update @angular/cdk

Workaround is just installing the cli directly through npm

This combination doesn't make sense.
npm install does a local installation of @angular/cli.
npx ng creates a temporary, global "installation" of @angular/cli, executes the command and removes the temporary files again.

@db6edr That's just how I'm using the angular-cli, without a global installation. You might as well use it without npx but the issue was updating the @angular/cli package through the cli itself and that's what the first command is for. I've had no issue installing other @angular packages, thus the follow-up command to install other packages via the cli.

Running ng update @angular/cli @angular/cdk @angular/core @angular/material worked for us..

Package "@angular/material" has an incompatible peer dependency to "@angular/common" (requires "^8.0.0 || ^9.0.0-0" (extended), would install "8.2.0-rc.0").
Package "@angular/material" has an incompatible peer dependency to "@angular/animations" (requires "^8.0.0 || ^9.0.0-0" (extended), would install "8.2.0-rc.0").
Package "@angular/material" has an incompatible peer dependency to "@angular/forms" (requires "^8.0.0 || ^9.0.0-0" (extended), would install "8.2.0-rc.0").
Package "@angular/material" has an incompatible peer dependency to "@angular/core" (requires "^8.0.0 || ^9.0.0-0" (extended), would install "8.2.0-rc.0").
Incompatible peer dependencies found. See above.

Facing the above issue when trying to update cli using ng update @angular/cli. All of the other dependencies updated properly using ng update list, except @angular/cli.

ng update

Found 56 dependencies.
We analyzed your package.json, there are some packages to update:
  Name                                      Version                  Command to update
 ---------------------------------------------------------------------------------------
  @angular/cli                              8.1.2 -> 8.1.3           ng update @angular/cli

ng update @angular/cli

              Package "@angular/flex-layout" has an incompatible peer dependency to "@angular/common" (requires ">=8.0.0-rc.5", would install "8.2.0-rc.0").
              Package "@angular/flex-layout" has an incompatible peer dependency to "@angular/core" (requires ">=8.0.0-rc.5", would install "8.2.0-rc.0").
              Package "@angular/material" has an incompatible peer dependency to "@angular/animations" (requires "^8.0.0 || ^9.0.0-0" (extended), would install "8.2.0-rc.0").
              Package "@angular/flex-layout" has an incompatible peer dependency to "@angular/platform-browser" (requires ">=8.0.0-rc.5", would install "8.2.0-rc.0").
              Package "@nguniversal/module-map-ngfactory-loader" has an incompatible peer dependency to "@angular/platform-server" (requires "^8.0.0" (extended), would install "8.2.0-rc.0").
              Package "@angular/material" has an incompatible peer dependency to "@angular/forms" (requires "^8.0.0 || ^9.0.0-0" (extended), would install "8.2.0-rc.0").
              Package "@swimlane/ngx-charts" has an incompatible peer dependency to "@angular/platform-browser-dynamic" (requires "7.x || 8.x" (extended), would install "8.2.0-rc.0").

Using the --force flag worked for me.

Using the --force flag now will install Angular 9.0.0.next 😱

It seems
ng update @angular/cli - will update package.json to 9.0.0.next
ng update @angular/cli @angular/core - will update package.json to 8.2.0

With<EMAIL_ADDRESS>installed globally
A local ng update @angular/cli installs<EMAIL_ADDRESS>but also installs @angular/core, etc. to "9.0.0-next.0" without doing ng update @angular/core
Using package manager: 'npm'
Collecting installed dependencies...
Found 44 dependencies.
Fetching dependency metadata from registry...
    Updating package.json with dependency @angular/cli @ "8.2.0" (was "8.1.1")...
    Updating package.json with dependency @angular/compiler-cli @ "9.0.0-next.0" (was "8.1.3")...
    Updating package.json with dependency @angular/language-service @ "9.0.0-next.0" (was "8.1.3")...
    Updating package.json with dependency @angular/animations @ "9.0.0-next.0" (was "8.1.3")...
    Updating package.json with dependency @angular-devkit/build-angular @ "0.802.0" (was "0.801.1")...
    Updating package.json with dependency @angular/common @ "9.0.0-next.0" (was "8.1.3")...
    Updating package.json with dependency @angular/core @ "9.0.0-next.0" (was "8.1.3")...
    Updating package.json with dependency @angular/compiler @ "9.0.0-next.0" (was "8.1.3")...
    Updating package.json with dependency @angular/forms @ "9.0.0-next.0" (was "8.1.3")...
    Updating package.json with dependency @angular/platform-browser @ "9.0.0-next.0" (was "8.1.3")...
    Updating package.json with dependency @angular/platform-browser-dynamic @ "9.0.0-next.0" (was "8.1.3")...
    Updating package.json with dependency @angular/router @ "9.0.0-next.0" (was "8.1.3")...
    Updating package.json with dependency typescript @ "3.5.3" (was "3.4.5")...
UPDATE package.json (1795 bytes)

@ilianiv ng update @angular/cli @angular/core actually installed "@angular/cli": "8.2.0-next.1"

I have the same issue but with the new 8.2.0 release it now installs 9.0.0-next.0
Updating package.json with dependency @angular/animations @ "9.0.0-next.0" (was "8.1.3")...
Updating package.json with dependency @angular/compiler @ "9.0.0-next.0" (was "8.1.3")...
Updating package.json with dependency @angular/common @ "9.0.0-next.0" (was "8.1.3")...
Updating package.json with dependency @angular/forms @ "9.0.0-next.0" (was "8.1.3")...
Updating package.json with dependency @angular/core @ "9.0.0-next.0" (was "8.1.3")...
Updating package.json with dependency @angular/platform-browser-dynamic @ "9.0.0-next.0" (was "8.1.3")...
Updating package.json with dependency @angular/router @ "9.0.0-next.0" (was "8.1.3")...

Here's the log. (in order)
PS > ng update
Your global Angular CLI version (8.1.3) is greater than your local
version (8.1.2). The local Angular CLI version is used.

To disable this warning use "ng config -g cli.warnings.versionMismatch false".
Using package manager: 'npm'
Found 63 dependencies.
    We analyzed your package.json, there are some packages to update:

      Name                                Version                  Command to update
     ---------------------------------------------------------------------------------
      @angular/cdk                        8.1.1 -> 8.1.2           ng update @angular/cdk
      @angular/cli                        8.1.2 -> 8.2.0           ng update @angular/cli
      @angular/core                       8.1.3 -> 8.2.0           ng update @angular/core

Updating the global CLI
PS > npm -g install<EMAIL_ADDRESS>omitted\AppData\Roaming\npm\ng -> omitted\AppData\Roaming\npm\node_modules\@angular\cli\bin\ng

><EMAIL_ADDRESS>postinstall omitted\AppData\Roaming\npm\node_modules\@angular\cli
> node ./bin/postinstall/script.js

+<EMAIL_ADDRESS>added 1 package from 1 contributor and updated 16 packages in 15.545s

Updating angular
PS > ng update @angular/cli --force
Your global Angular CLI version (8.2.0) is greater than your local
version (8.1.2). The local Angular CLI version is used.

To disable this warning use "ng config -g cli.warnings.versionMismatch false".
Using package manager: 'npm'
Collecting installed dependencies...
Found 63 dependencies.
Fetching dependency metadata from registry...
                  Package "@angular/flex-layout" has an incompatible peer dependency to "@angular/platform-browser" (requires ">=8.0.0-rc.5", would install "9.0.0-next.0").
                  Package "@angular/flex-layout" has an incompatible peer dependency to "@angular/common" (requires ">=8.0.0-rc.5", would install "9.0.0-next.0").
                  Package "jest-preset-angular" has an incompatible peer dependency to "@angular/core" (requires ">=2.0.0", would install "9.0.0-next.0").
                  Package "jest-preset-angular" has an incompatible peer dependency to "@angular/platform-browser-dynamic" (requires ">=2.0.0", would install "9.0.0-next.0").
    Updating package.json with dependency @angular/cli @ "8.2.0" (was "8.1.2")...
    Updating package.json with dependency @angular/compiler-cli @ "9.0.0-next.0" (was "8.1.3")...
    Updating package.json with dependency @angular/language-service @ "9.0.0-next.0" (was "8.1.3")...
    Updating package.json with dependency @angular/platform-browser @ "9.0.0-next.0" (was "8.1.3")...
    Updating package.json with dependency @angular-devkit/build-angular @ "0.802.0" (was "0.801.2")...
    Updating package.json with dependency @angular/animations @ "9.0.0-next.0" (was "8.1.3")...
    Updating package.json with dependency @angular/compiler @ "9.0.0-next.0" (was "8.1.3")...
    Updating package.json with dependency @angular/common @ "9.0.0-next.0" (was "8.1.3")...
    Updating package.json with dependency @angular/forms @ "9.0.0-next.0" (was "8.1.3")...
    Updating package.json with dependency @angular/core @ "9.0.0-next.0" (was "8.1.3")...
    Updating package.json with dependency @angular/platform-browser-dynamic @ "9.0.0-next.0" (was "8.1.3")...
    Updating package.json with dependency @angular/router @ "9.0.0-next.0" (was "8.1.3")...
    Updating package.json with dependency typescript @ "3.5.3" (was "3.4.5")...
UPDATE package.json (2989 bytes)

npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS><9.0.0 || >8.0.0-beta <9.0.0 || >8.1.0-beta <9.0.0 || >8.2.0-beta <9.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS><9.0.0 || >8.0.0-beta <9.0.0 || >8.1.0-beta <9.0.0 || >8.2.0-beta <9.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS><=8.x but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS><=8.x but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS><=8.x but none is installed. You must install peer dependencies yourself.
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})

added 18 packages from 9 contributors, removed 1 package, updated 46 packages and audited 913394 packages in 49.043s
found 0 vulnerabilities

I have the same issue.  I managed to update @angular/cli and @angular/core by updating them together, but I can't update @angular/cdk as I get the "would install "9.0.0-next.0" error.

Issue had fix when i use the following command with --force flag..
ng update @angular/cli @angular/core --force

ng update with --force option will update angular irrespective of version conflicts dependencies

ng update @angular/cli @angular/core worked for me.
I was getting the following error before.

ng update @angular/cli @angular/core @angular/material @angular/cdk @angular/pwa @angular-devkit/build-angular
Using package manager: 'npm'
Collecting installed dependencies...
Found 50 dependencies.
Fetching dependency metadata from registry...
Package "@angular/common" has an incompatible peer dependency to "@angular/core" (requires "9.0.0-next.0" (extended), would install "8.2.0").
Package "@angular/compiler-cli" has an incompatible peer dependency to "@angular/compiler" (requires "9.0.0-next.0", would install "8.2.0")
Package "@angular/common" has an incompatible peer dependency to "@angular/core" (requires "9.0.0-next.0", would install "8.2.0")
Package "ngx-mask" has an incompatible peer dependency to "@angular/common" (requires ">=6.0.0", would install "9.0.0-next.0").
Package "@angular/forms" has an incompatible peer dependency to "@angular/common" (requires "8.2.0", would install "9.0.0-next.0")
Package "@angular/compiler-cli" has an incompatible peer dependency to "@angular/compiler" (requires "9.0.0-next.0" (extended), would install "8.2.0").
Package "@angular/platform-browser-dynamic" has an incompatible peer dependency to "@angular/common" (requires "8.2.0", would install "9.0.0-next.0")
Package "@angular/platform-browser" has an incompatible peer dependency to "@angular/common" (requires "8.2.0", would install "9.0.0-next.0")
Package "@angular/service-worker" has an incompatible peer dependency to "@angular/common" (requires "8.2.0", would install "9.0.0-next.0")
Package "@angular/router" has an incompatible peer dependency to "@angular/common" (requires "8.2.0", would install "9.0.0-next.0")
Incompatible peer dependencies found.
Peer dependency warnings when installing dependencies means that those dependencies might not work correctly together.
You can use the '--force' option to ignore incompatible peer dependencies and instead address these warnings later.

Cli team blames material, material team blames cli... angular/components/issues/16596

I'm not using material and still seeing this issue.

I was able to get around these issues via manually updating my package.json to latest angular/angular material versions.
Then running:
ng update @angular/cli  @angular/core  --from 7 --to 8 --migrate-only
ng update @angular/material --from 7 --to 8 --migrate-only

Similar problem here - updating from 8.1.1 -> 8.2.0.
A combined ng update @angular/cli @angular/core updates both to 8.2.0.
But when running ng update @angular/material afterwards, all angular dependencies (except for material, cdk and cli) are updated to 9.0.0-next.0

Similar problem here - updating from 8.1.1 -> 8.2.0.
A combined ng update @angular/cli @angular/core updates both to 8.2.0.
But when running ng update @angular/material afterwards, all angular dependencies (except for material, cdk and cli) are updated to 9.0.0-next.0

I have the exact same issue!

Bottom line, ng update doesn't work.
It get the following errors when attempting to upgrade from Angular 7.
Package "@angular/compiler-cli" has an incompatible peer dependency to "@angular/compiler" (requires "9.0.0-next.0", would install "8.2.0")
Package "codelyzer" has an incompatible peer dependency to "@angular/compiler" (requires ">=2.3.1 <7.0.0 || >6.0.0-beta <7.0.0" (extended), would install "8.2.0").                  Package "codelyzer" has an incompatible peer dependency to "@angular/core" (requires ">=2.3.1 <7.0.0 || >6.0.0-beta <7.0.0" (extended), would install "8.2.0").

ng update definitely has some problems... material as well. On my end, that's when I try to upgrade @angular/material that it tries to install 9.0.0-next.0. I'm upgrading from 7.1.2. Everything went perfectly until I tried to upgrade @angular/material and @angular/cdk. This is a real PITA...

Similar problem here - updating from 8.1.1 -> 8.2.0.
A combined ng update @angular/cli @angular/core updates both to 8.2.0.
But when running ng update @angular/material afterwards, all angular dependencies (except for material, cdk and cli) are updated to 9.0.0-next.0

I have the exact same issue!

These steps helped me resolved the problem:

Manually edit the version numbers of the depencies which changed to ~9.0.0-next.0" in package.json. Example: "@angular/common": "~9.0.0-next.0" to "@angular/common": "^8.1.2",
Remove node_modules folder
Run npm install

Similar problem here - updating from 8.1.1 -> 8.2.0.
A combined ng update @angular/cli @angular/core updates both to 8.2.0.
But when running ng update @angular/material afterwards, all angular dependencies (except for material, cdk and cli) are updated to 9.0.0-next.0

I have the exact same issue!

These steps helped me resolved the problem:

Manually edit the version numbers of the depencies which changed to ~9.0.0-next.0" in package.json. Example: "@angular/common": "~9.0.0-next.0" to "@angular/common": "^8.1.2",
Remove node_modules folder
Run npm install

I've gone kinda the same way to resolve the issue. I manually upgrade material and cdk manually with npm and then ran the migration command manually from the schematics of angular CLI. Works perfectly the first time.

I don't even have Angular Material in my project.
Just Angular and Bootstrap, that's all and it doesn't work.

In a project with "@angular/core": "~8.1.2", I ran ng update @angular/cli and I got "@angular/cli": "~8.2.0" along with "@angular/core": "~9.0.0-next.0". This seems unexpected to me if I don’t specify --next.
I was expecting to go to "@angular/core": "~8.2.0".
It seems quite surprising to go from a stable to a preview release.
You can use this repo and commit to reproduce/debug: https://github.com/angular-hispano/angular-hispano/commit/7375b34f6e3f2b1158f7430230d2087e1b18d3a6.

I was able to get around these issues via manually updating my package.json to latest angular/angular material versions.
Then running:
ng update @angular/cli @angular/core --from 7 --to 8 --migrate-only
ng update @angular/material --from 7 --to 8 --migrate-only

Run that without the --migrate-only.
Finally installed 8.2.1 and NOT 9.0.0.next... (or whatever)
Also uninstall all other packages that throw that incompatible peer-dependency Error and reinstall them afterwards. In my case it was angularx-social-login.

I am having the same issue
running this command
ng update @angular/cdk @angular/material @angular/material-moment-adapter
and getting this error -
Package "ag-grid-angular" has an incompatible peer dependency to "@angular/core" (requires ">=2.1.x" (extended),
would install "9.0.0-next.2").
                  Package "ag-grid-angular" has an incompatible peer dependency to "@angular/compiler" (requires ">=2.1.x" (extended), would install "9.0.0-next.2").
Incompatible peer dependencies found.
Peer dependency warnings when installing dependencies means that those dependencies might not work correctly together.
You can use the '--force' option to ignore incompatible peer dependencies and instead address these warnings later.

Do not want to use force option but why i am getting this error.

@ErVishalM: you are getting this error, because somehow angular cli thinks, that 9.0.0-next.2 is the latest version. You can combine your update command with cli and core (as @heapifyman suggested):
ng update @angular/core @angular/cli @angular/cdk @angular/material @angular/material-moment-adapter.
Than somehow the correct version is used for peer dependency check (8.2.x).

It is now having the same problem with the 9.0.0-next.2!
Running ng update:
 Name                               Version                  Command to update
     --------------------------------------------------------------------------------
      @angular/cdk                       8.0.2 -> 8.1.2           ng update @angular/cdk
      @angular/material                  8.0.2 -> 8.1.2           ng update @angular/material

Running ng update @angular/material
Updating package.json with dependency @angular/material @ "8.1.2" (was "8.0.2")...
    Updating package.json with dependency @angular/language-service @ "9.0.0-next.2" (was "8.2.2")...
    Updating package.json with dependency @angular/compiler-cli @ "9.0.0-next.2" (was "8.2.2")...
    Updating package.json with dependency @angular/cdk @ "8.1.2" (was "8.0.2")...
    Updating package.json with dependency @angular/core @ "9.0.0-next.2" (was "8.2.2")...
    Updating package.json with dependency @angular/animations @ "9.0.0-next.2" (was "8.2.2")...
    Updating package.json with dependency @angular/common @ "9.0.0-next.2" (was "8.2.2")...
    Updating package.json with dependency @angular/forms @ "9.0.0-next.2" (was "8.2.2")...
    Updating package.json with dependency @angular/platform-browser @ "9.0.0-next.2" (was "8.2.2")...
    Updating package.json with dependency @angular/router @ "9.0.0-next.2" (was "8.2.2")...
    Updating package.json with dependency @angular/compiler @ "9.0.0-next.2" (was "8.2.2")...
    Updating package.json with dependency @angular/platform-browser-dynamic @ "9.0.0-next.2" (was "8.2.2")...

@hpawe01 well not solved from this command also. see run this command -
ng update @angular/core @angular/cli @angular/cdk @angular/material @angular/material-moment-adapter Using package manager: 'npm' Collecting installed dependencies... Found 43 dependencies. Fetching dependency metadata from registry... Package '@angular/core' is already up to date. Package '@angular/cli' is already up to date.                   Package "ag-grid-angular" has an incompatible peer dependency to "@angular/core" (requires ">=2.1.x" (extended),  would install "9.0.0-next.2").                   Package "ag-grid-angular" has an incompatible peer dependency to "@angular/compiler" (requires ">=2.1.x" (extended), would install "9.0.0-next.2"). Incompatible peer dependencies found. Peer dependency warnings when installing dependencies means that those dependencies might not work correctly together. You can use the '--force' option to ignore incompatible peer dependencies and instead address these warnings later.

I had the exact same issue, but resolved now .
following command worked.
ng update<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>

I hate ng update...

I have the same issue when update @angular/cli 8.1.3 -> 8.2.2

@nzbin I'm pretty sure this would skip any automatic code migration that would be done by the ng update command. I highly recommend you not to do this, unless someone who knows more about it than me can clear things up.

I can confirm @nzbin case, same here from @angular/cli 8.1.3 -> 8.2.2
In my case it want to install @angular/common 9.0.0.next, also when only updating @angular/core
The only way around ist manual update.

@JohnnyDevNull I am getting this error via this command - ng update<EMAIL_ADDRESS><EMAIL_ADDRESS>Collecting installed dependencies...
Found 43 dependencies.
Package '@angular/core' is already at '8.2.2'.
Fetching dependency metadata from registry...
                  Package "ag-grid-angular" has an incompatible peer dependency to "@angular/core" (requires ">=2.1.x" (extended),
would install "9.0.0-next.2").
                  Package "ag-grid-angular" has an incompatible peer dependency to "@angular/compiler" (requires ">=2.1.x" (extended), would install "9.0.0-next.2").
Incompatible peer dependencies found.
Peer dependency warnings when installing dependencies means that those dependencies might not work correctly together.
You can use the '--force' option to ignore incompatible peer dependencies and instead address these warnings later

Same issue from 7.2.14 to 8.2.2
this worked for me -
ng update<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>

Still does not work. How are we supposed to update?
Setting the versions by hand does not work either:
ng update<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Using package manager: 'npm'
Collecting installed dependencies...
Found 51 dependencies.
Fetching dependency metadata from registry...
                  Package "@angular/common" has an incompatible peer dependency to "@angular/core" (requires "9.0.0-next.2" (extended), would install "8.2.2").
                  Package "@angular/platform-browser-dynamic" has an incompatible peer dependency to "@angular/common" (requires "8.2.2", would install "9.0.0-next.2")
                  Package "@angular/platform-browser" has an incompatible peer dependency to "@angular/common" (requires "8.2.2", would install "9.0.0-next.2")
                  Package "@angular/common" has an incompatible peer dependency to "@angular/core" (requires "9.0.0-next.2", would install "8.2.2")
                  Package "@angular/flex-layout" has an incompatible peer dependency to "@angular/common" (requires ">=8.0.0-rc.5", would install "9.0.0-next.2").
                  Package "@angular/router" has an incompatible peer dependency to "@angular/common" (requires "8.2.2", would install "9.0.0-next.2")
                  Package "@angular/forms" has an incompatible peer dependency to "@angular/common" (requires "8.2.2", would install "9.0.0-next.2")
Incompatible peer dependencies found.
Peer dependency warnings when installing dependencies means that those dependencies might not work correctly together.
You can use the '--force' option to ignore incompatible peer dependencies and instead address these warnings later.

Guys, this is a showstopper. If this was a commercial release it would be withdrawn until this issue was resolved. As things stand, following the update instructions results in unreleased beta software being installed. You have to resolve this or pull the update instructions.

@colmben A showstopper? Please! This is an inconvenience, at worst. The issue was reported over a month ago, and it hasn’t kept me from getting the proper version of Angular installed in my applications. Don’t be so dramatic.

@rdrrichards Ah great, can you expand on how you safely update all angular package?
In good faith, I'm stuck with this ng update fail. I am not familiar enough with the inner workings of angular-cli to feel safe with just bypassing that through npm or packages.json and pray for dependencies to fall in order afterwards.

Nothing magical, really. After seeing this issue come up, all I do is edit the packages.json file, and change all occurrences of 9.0.0-next.2 to 8.2.2, then run npm install.
If you're not comfortable with editing the packages.json, try to get some level of comfortable with it. Obviously, relying on the tools 100% of the time can be disappointing.
If this issue were a real show showstopper, the Angular CLI team would have had it fixed by now. Working around this is quite easy.

I don't know how you get to the point where you have 9.0.0-next.2 in packages.json, it doesn't happen to me :( (see error above)
Bypassing https://github.com/angular/angular-cli/blob/master/packages/angular/cli/commands/update-impl.ts and the rest doesn't seem trivial to me - at least I cannot safely envision the consequences.
IMO, relying on a toolchain is not a weakness but rather the basis for successful devops: having those shortcuts and not caring about the gory details is part of why I chose Angular in the first place :)
I hope a safe workaround can be found until it's fully fixed in a future release.

Same thing just happened to me. Updated from 8.0.0 to what I thought would be 8.2.2, updated all the way to ~9.0.0-next.2. Bit of a surprise...

Nothing magical, really. After seeing this issue come up, all I do is edit the packages.json file, and change all occurrences of 9.0.0-next.2 to 8.2.2, then run npm install.
If you're not comfortable with editing the packages.json, try to get some level of comfortable with it. Obviously, relying on the tools 100% of the time can be disappointing.
If this issue were a real show showstopper, the Angular CLI team would have had it fixed by now. Working around this is quite easy.

Doing that you're asking for trouble. Let me explain it a little here. When you ran ng update @angular/core and end up with the 9.0.0-next.Y versions, the CLI also ran the migration for Angular 9 on your project unless you added the flag to skip these which doesn't seem to be the case here. It's working because you got lucky. The migration didn't transition some code to something that is new in Angular 9 and not supported by 8. Otherwise, it wouldn't have worked. This is a reckless way of going around the problem that can results in much bigger problem IMO...

Nothing magical, really. After seeing this issue come up, all I do is edit the packages.json file, and change all occurrences of 9.0.0-next.2 to 8.2.2, then run npm install.
If you're not comfortable with editing the packages.json, try to get some level of comfortable with it. Obviously, relying on the tools 100% of the time can be disappointing.
If this issue were a real show showstopper, the Angular CLI team would have had it fixed by now. Working around this is quite easy.

Doing that you're asking for trouble. Let me explain it a little here. When you ran ng update @angular/core and end up with the 9.0.0-next.Y versions, the CLI also ran the migration for Angular 9 on your project unless you added the flag to skip these which doesn't seem to be the case here. It's working because you got lucky. The migration didn't transition some code to something that is new in Angular 9 and not supported by 8. Otherwise, it wouldn't have worked. This is a reckless way of going around the problem that can results in much bigger problem IMO...

This is exactly what happened to me, it updated 30+ source files beyond the 3 that actually needed updating for 8. All quite scary and time consuming for what should be a simple enough framework update. I did exactly what rdrrichards  suggests and so now I have an app that is using 8 but migrated to 9. It seems to be working, but I haven't diff'ed all 30+ files yet to understand what the implications are. For a commercial developer this is all time wasted that could have been spent writing code - the exact point of using a framework like Angular in the first place. Obviously we all have different definitions of what is a showstopper, but releasing an update procedure that causes unreleased beta code to be loaded onto your client severs and all your client's code go through an unreleased migration process seems to me to fall within that category.

Hey folks, we're aware of this problem and @clydin is looking into it. Since the discussion is getting a bit heated, I'll lock the issue temporarily until we have some progress. Excuse us for the inconvenience and thank you for your patience!
Side note: if you're already on version 8.x, updating your package.json to the latest Angular version should be fine. We haven't shipped any changes that require automatic migration (codemods).

This should be resolved now in latest 8.3.x builds.


PROV: use EVP_CIPHER_CTX_set_params() rather than EVP_CIPHER_CTX_ctrl()

This is in gmac_final(), where the cipher is known to be fetched.
It's more suitable to use OSSL_PARAMs than _ctrl functions, as the
latter are expected to become obsolete.
Fixes #14359

This pull request is ready to merge

Merged
c9d01f4186817612e8afa401951e0968aed83b2e PROV: use EVP_CIPHER_CTX_set_params() rather than EVP_CIPHER_CTX_ctrl()
92e9359b24660228fa8fbf9129837ce5ab287715 TEST: Stop the cleanup in test/recipes/20-test_mac.t


Do you consider this module production ready?

In the readme I've found that you call this implementation a prototype. And since I'd be interested in using it, I'd like to know if the maintainers consider it production-ready. Before attempting using this one in prod.
Thanks!

@renannprado
As you mentioned, this project is merely a prototype. I think keycloak's maintainer does NOT consider it production-ready.
I've been trying to implement webauthn's support onto keycloak but I have not used this protype's codes directly.
FYI, the first phase of the webauth's support based on this repository has been merged into keycloak master. Therefore, this project will not be actively maintained basically.

@tnorimat Ah, I see. Thanks for the information!
Now I have two questions:

Is there anywhere a documentation about features that were merged so far?
Do you have information about the target version when they expect webauthn (full-featured) to be available? Sorry if I'm asking the wrong person.

@renannprado Hello.

Is there anywhere a documentation about features that were merged so far?

Please refer to https://github.com/keycloak/keycloak-documentation/blob/master/server_admin/topics/authentication/webauthn.adoc
This is the manual for the webauthn feature that has already been mereged in to the current master branch.
Also this merged webauthn feature has been developed along with the design document. Please look at https://github.com/keycloak/keycloak-community/blob/master/design/web-authn-authenticator.md .

Do you have information about the target version when they expect webauthn (full-featured) to be available? Sorry if I'm asking the wrong person.

I'm sorry I don't know it. I am merely a contributor of this webauthn feature. It might be better to ask this question to the keycloak maintainers. Keycloak project has the mailing list.


Add Indonesia Language

Hello,
I really like this module in Transformice. When i see the list of languages, i didn't see my country language. So, I created this one.

Thank you! Will be added in V3.2.0

Whats your nickname in Transformice? I need it to give credits

My nickname is Ppabcd#0000


Network drive Unavailable Windows

Issue Type: Bug
I'm using a Windows 10 PC and opening files from Networkshares.
If I'm working from home via VPN the drives are marked in the explorer with a red x as they are not available after the login. But they are after the VPN connection is running.
if you now try to click on an open file it will show the error "Unable to open '': File not found (file:///:/.../) and close the file.
I need to click on the drive in the Explorer first so it will mark the drive as available first than I can click on the open file.
VS Code version: Code 1.31.1 (1b8e8302e405050205e69b59abb3559592bb9e60, 2019-02-12T02:20:54.427Z)
OS version: Windows_NT x64 10.0.17134

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz (8 x 2592)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: enabledsurface_synchronization: enabled_onvideo_decode: enabledwebgl: enabledwebgl2: enabled

Memory (System)
31.86GB (25.02GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (8)

Extension
Author (truncated)
Version

perl-toolbox
d97
1.3.0

gitlens
eam
9.5.1

gc-excelviewer
Gra
2.1.29

todo-tree
Gru
0.0.121

compareit
in4
0.0.2

cisco
jam
1.3.0

PowerShell
ms-
1.11.0

html-css-class-completion
Zig
1.18.0

This seems to be a Windows issue, not a VS Code one.

with any other app I can access the files without the need to use the explorer first.
I can't even reopen the file from recent files. If I do this it will be removed from the recent files.
So I think it's an issue with checking if the file/drive is available.


ThemeProvider Rapid UI error on expo start

This is the error I am getting :
node_modules/react-native-rapi-ui/provider/ThemeProvider.tsx: Property body[12] of BlockStatement expected node to be of a type ["Statement"] but instead got "AssignmentExpression"
Thanks for your help

can you give me more details, what template are you using? btw check this https://stackoverflow.com/questions/68659516/react-native-property-body41-of-blockstatement-expected-node-to-be-of-a-type

@adnaneghalem


docs: DOC-46: Simplify Connecting AWS S3 with IAM Role Access

@lawesworks this PR is ready for your review/approval. Thank you!


Wrong keywords in forwardingList

I noticed that in the forwarding list there are keywords "server-name" and "service-name".
In the template from the ApplicationPattern I only see "server-name", so I guess this might be wrong as I would expect this should be "server-name" everywhere...
Example:
  - forwarding-name: ServiceRequestCausesLtpUpdateRequest
    uuid: ol-2-0-1-op-fc-bm-006
    forwarding-type: InvariantProcessSnippet
    management-requests:
      operation-client-update:
        - server-name: /v1/redirect-topology-change-information
          uuid: ol-2-0-1-op-s-bm-009
      fc-port-update:
        - server-name: /v1/redirect-topology-change-information
          uuid: ol-2-0-1-op-s-bm-009
      fc-port-deletion:
      operation-client-deletion:
    initiating-requests:
      - server-name: /v1/register-yourself
        uuid: ol-2-0-1-op-s-bm-000
      - server-name: /v1/embed-yourself
        uuid: ol-2-0-1-op-s-bm-001
      - server-name: /v1/redirect-service-request-information
        uuid: ol-2-0-1-op-s-bm-002
      - server-name: /v1/redirect-oam-request-information
        uuid: ol-2-0-1-op-s-bm-003
      - server-name: /v1/inquire-oam-request-approvals
        uuid: ol-2-0-1-op-s-bm-005
      - server-name: /v1/update-client
        uuid: ol-2-0-1-op-s-bm-007
      - server-name: /v1/redirect-topology-change-information
        uuid: ol-2-0-1-op-s-bm-009
      - server-name: /v1/update-operation-client
        uuid: ol-2-0-1-op-s-bm-011
      - server-name: /v1/bequeath-your-data-and-die
        uuid: ol-2-0-1-op-s-im-000
      - service-name: /v1/regard-application
        uuid: ol-2-0-1-op-s-is-001
    consequent-requests:
      - client-name: ApplicationLayerTopology://v1/update-ltp
        uuid: ol-2-0-1-op-c-bm-alt-1-0-0-001

Changed as proposed.


Run getComputedStyle in the same context as the target element

I work on an embedded JavaScript app. We inject an iframe into the page that we're embedded on and the JavaScript is inserted and run in the context of that iframe so we can run in isolation from the parent page.
This works well, but there's an issue in Firefox, specifically with getComputedStyle(), where, if you try to run this method in the context of an iframe, it always returns null.
I'm looking to introduce Popper into my embedded app, but because of the bug above, Popper can't position my elements because getComputedStyle returns null. Unfortunately, this issue has been open for almost a decade and is unlikely to be fixed any time soon.
Because the elements themselves live on the parent page, we can work around this by getting the window of the document that the element is embedded in, and run getComputedStyle() in that context.
This PR solves our specific use case, and should work exactly as before for any other supported browser.
Let me know what you think.

Thank you @mckenna!
@ryanseddon sorry to bother you, but since you worked on (#607) which is pretty similar, may you review this PR and let me know if anything looks off?

You would not believe this but we had this issue yesterday and tracked it down to this same function and I was about to do a similar PR. So approved!

Nice one on merging this 👍 — any idea when you plan to do another release?


Updates v1.28 hugo.toml for v1.30 release

Updating hugo.toml for release v1.30.
/hold until v1.30 release day.

/remove-hold


#16 Linear search code added

Added linear search program in c++ language

Added linear_search.cpp file to find an element by linear search algorithm

LGTM! Merging it into master


Add bulk file download

A quick implementation of bulk download to support the download of files returned from search.
When a user searches files, they get a list of files that could be attached to many different containers (projects, sessions, acquisitions). This change allows a user to send a list of unique file references (container name, container id, and filename) and receive a download ticket for a tar of those files.
Of Note:

Files on analyses are currently not searchable so they are not included in this first pass.
Permissions are checked by adding the requesting user id to the DB query
Will silently skip a requested file when the file is not found or the user does not have access to the file (this can be easily changed, mimicking existing api/download functionality)

To make a download ticket request:
POST /api/download?bulk=true HTTP/1.1
Content-Type: application/json
{
    "files": [
        {
            "container_name": "acquisition",
            "container_id": "5769a9051a86148932be9af1",
            "filename": "149_2_1_t1_dicom.zip"
        },
        {
            "container_name": "acquisition",
            "container_id": "5769a8c21a86148932be9ae4",
            "filename": "8403_6_1_fmri_dicom.zip"
        }
    ]
}

Which will receive a response similar to:
{
  "ticket": "<ticket_id>",
  "file_cnt": 2,
  "size": 25394268
}

Then, request the download by using the ticket id:
POST /api/download?ticket=<ticket_id> HTTP/1.1

LGTM

Changed file naming structure, added ability for a super user request that ignores permissions

Will merge after CI hits green


Save study

for some reason now the following errors appear:
/volatile/salome/jenkins/workspace/Salome9_UB18/SALOME-9.4.0-UB18.04/SOURCES/medfile/src/ci/MEDstructElementGeotype.c [60] : Erreur à l'ouverture du groupe
/volatile/salome/jenkins/workspace/Salome9_UB18/SALOME-9.4.0-UB18.04/SOURCES/medfile/src/ci/MEDstructElementGeotype.c [60] : /STRUCT/MED_BALL

not sure why/how it is related
this is also the reason to switch from ascii to utf-8 for encoding


NullPointerException in client during broker restart

On restarting the broker a NPE was thrown by the client.  Once the service was restarted the client seemed to be blocked draining.  Restarting the broker a second time doesn't seem to help.  I was not able to reproduce this failure so hopefully the exception gives some indication of what may have gone wrong.
06/16 01:19:00.482 INFO [oopGroup-1024-8] c.g.o.s.StateMachine - Firing NETWORK_ERROR
06/16 01:19:00.486 INFO [oopGroup-1024-7] c.g.o.s.StateMachine - Firing NETWORK_ERROR
06/16 01:19:00.495 INFO [oopGroup-1024-7] c.g.o.s.StateMachine - Firing EP_RESP_OK
06/16 01:19:00.496 DEBUG[lt-dispatcher-4] c.m.m.m.p.a.i.IbmAsyncConsumer - Consumer lost connection to broker, retrying
06/16 01:19:00.497 INFO [oopGroup-1024-8] c.g.o.s.StateMachine - Firing EP_RESP_OK
06/16 01:19:00.506 DEBUG[lt-dispatcher-4] c.m.m.m.p.a.i.IbmAsyncProducer - Producer lost connection to broker, retrying
06/16 01:19:00.536 WARN [oopGroup-1024-6] i.n.u.c.DefaultPromise - An exception was thrown by com.ibm.mqlight.api.impl.network.NettyNetworkService$ConnectListener.operationComplete()
java.lang.NullPointerException: null
at com.ibm.mqlight.api.impl.network.NettyNetworkService$ConnectListener.operationComplete(NettyNetworkService.java:340) ~[mqlight-api-1.0.2015060300.jar:1.0.2015060300]
at com.ibm.mqlight.api.impl.network.NettyNetworkService$ConnectListener.operationComplete(NettyNetworkService.java:316) ~[mqlight-api-1.0.2015060300.jar:1.0.2015060300]
at io.netty.util.concurrent.DefaultPromise.notifyListener0(DefaultPromise.java:679) ~[netty-all-4.0.21.Final.jar:4.0.21.Final]
at io.netty.util.concurrent.DefaultPromise$LateListeners.run(DefaultPromise.java:844) [netty-all-4.0.21.Final.jar:4.0.21.Final]
at io.netty.util.concurrent.DefaultPromise$LateListenerNotifier.run(DefaultPromise.java:872) [netty-all-4.0.21.Final.jar:4.0.21.Final]
at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:370) [netty-all-4.0.21.Final.jar:4.0.21.Final]
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:357) [netty-all-4.0.21.Final.jar:4.0.21.Final]
at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:116) [netty-all-4.0.21.Final.jar:4.0.21.Final]
at io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:137) [netty-all-4.0.21.Final.jar:4.0.21.Final]
at java.lang.Thread.null(Unknown Source) [na:1.8.0_40]

Hi Bernard
Thanks for the information.  I've managed to recreate the problem in a debugger.
The issue seems to be a small window in that during channel initialization should a network error occur the ConnectListener.operationComplete() method can be called with a success status, even though the channel has been torn down. This could be deemed as a bug in Netty, but I think the problem is really related to the way we are using Netty.
I have managed to the fix the issue and we should hopefully upload the code changes to github tomorrow, once we've passed it though our FV test automation.


add is quadratic test

bors r+
🤖

bors r-

bors try

changelog internal: use liner regression to catch "accidentally quadratic" performance regressions.

bors try+

bors try

bors try+

bors try

bors r+

cc @SomeoneToIgnore this is one of the reasons want to try using generated code as much as possible. With generation, it's easy to vary n and to check big-O


Add dependencyTree to preserve tree structure for other tools

@ennru   - maybe an entry in the Readme for how to use it?


Add AWS Service Discovery provider

Hi guys,
AWS engineer here. First of all thank you for the successful integration with Route 53 API. Good job!
I would like to propose an alternative AWS provider to current one. It uses the recently published Amazon Auto Naming API that is more suitable for service discovery use case. You can read more about the service discovery in the Amazon API Reference
I would like to emphasize a few important features of the provider:

It natively supports recent addition of multiple targets per endpoint - in Auto Naming API terms you can have multiple instances per service.
It is more safe to use compared to managing DNS records in hosted zone. All services are isolated in separate namespaces. In case there is a bug in ExternalDNS code there is no risk of taking the whole domain (with possibly all DNS records) down.

Please let me know what you think.

Any update on this? Is there any way how I could help with the review? I am ready to answer your questions. Just want to know there is a chance this contribution to be accepted.

@vanekjar I think your feature generally looks interesting, also for us (Zalando). Apparently nobody had time to review yet, sorry for that.

@ideahitme What do you think can we merge it? I think all questions and concerns have been answered.

Unfortunately not yet, I will answer all comment later this week

@ideahitme any update?

@hjacobs still need to put a bit of work, I will try to help out with adding missing parts

Suggested additions: https://github.com/vanekjar/external-dns/pull/1

@ideahitme Thank you again for the proposed idea. Based on your code I finalized the story of AWS-SD registry. The ownership information (labels) is stored in service description instead of creatorRequestId, because this one is limited to length of 64 characters.
Please have a look at the latest commit if it is implemented correctly. If I get a green from you I would squash all the commits to fix the problem with CLA validation.

/lgtm

/lgtm

@njuettner, when do you plan to merge it?

@linki @njuettner can we just merge it? (we have two LGTMs)

@njuettner @linki this new provider probably deserves a new External DNS release?


fix: modify jupyter's authority from hash password to token string

Signed-off-by: zhenguo.li<EMAIL_ADDRESS>

The jupyter password must be hase string, so i think we can set string token for jupyter authority

Close https://github.com/tensorchord/envd/issues/760


a page to show the open source projects

Fixes Issue

Closes #33
Changes proposed

Adds Project element in the sidebar and navbar
Adds Projects component in the homepage.jsx
Adds routes for the invidual projects
Screenshots

Note to reviewers

It would be great to hear your comments on this pull request. I hope to improve myself through the comments. And, the sidebar seems to use styled.div instead of styled(LinkScroll). I didn't change it. Left it to your wisdom.

Code of Conduct

[x] By submitting this pull request, I confirm I've read and complied with the CoC 🖖

Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[ ] My change requires changes to the documentation.
[ ] I have updated the documentation accordingly.
[ ] All new and existing tests passed.
[x] This PR does not contain plagiarized content.
[x] The title of my pull request is a short description of the requested changes.

You can also join our Discord community.
Feel free to check out other cool repositories of the Cryptoverse Web3.
Join the Cryptoverse Web3 GitHub Organisation by raising an issue (you will be sent an invitation).

Can you fetch the new code into your repo, and in your branch?

hey, I am having difficulty resolving the conflicts. It says my branch is 3 commits ahead and 2 commits behind, how do I fix this?


[e2e]: go push main config-noldflags slsa3

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/3318292897
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.go.push.main.config-noldflags.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.go.push.main.config-noldflags.slsa3.yml
Trigger: push
Branch: main
Date: Tue Oct 25 05:09:24 UTC 2022

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/3326132555
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.go.push.main.config-noldflags.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.go.push.main.config-noldflags.slsa3.yml
Trigger: push
Branch: main
Date: Wed Oct 26 04:15:25 UTC 2022

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/3334429604
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.go.push.main.config-noldflags.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.go.push.main.config-noldflags.slsa3.yml
Trigger: push
Branch: main
Date: Thu Oct 27 04:15:49 UTC 2022

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/3364395553
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.go.push.main.config-noldflags.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.go.push.main.config-noldflags.slsa3.yml
Trigger: push
Branch: main
Date: Mon Oct 31 20:17:17 UTC 2022
Tests are passing now. Closing this issue.


jordan did u fork ur engine to my repository bc i didnt use github for long

What is your question?
u just fork ur engine to my repository did u do that or no or does someone has the same like me?

you're on the repositories tab

What is your question?
u just fork ur engine to my repository did u do that or no or does someone has the same like me?

dude that’s your fork, that you made

oh wait
you did fork it

Not related to js engine so first ever off topic issue in this repo?

Not related to js engine so first ever off topic issue in this repo?

yep


Unable to configure PostgreSQL dialer as a 'companion process'

https://cloud.google.com/sql/docs/postgres/connect-external-app#go
Google's documentation incorrectly duplicates the MySQL configuration for the instructions on using PostgreSQL dialer as a 'companion process'.
When this issue is resolved, I'll file a bug against the Google documentation :-)
The PostgreSQL dialer works as a library referenced within code:
	dsn := fmt.Sprintf("host=%s user=%s dbname=%s password=%s sslmode=disable",
		instanceConnection,
		user,
		databaseName,
		password)
	db, err := sql.Open("cloudsqlpostgres", dsn)

It's unclear to me how this should be configured as a companion process.
I've tried Unix|TCP sockets:
./cloud_sql_proxy -instances=$INSTANCE -dir=/cloudsql
./cloud_sql_proxy -instances=$INSTANCE=tcp:5432
./cloud_sql_proxy -instances=$INSTANCE=tcp:<IP_ADDRESS>:5432

And:
	dsn := fmt.Sprintf("%s:%s@unix(/cloudsql/%s)/%s",
		user,
		password,
		instanceConnection,
		databaseName)

But I get:
2017/08/18 16:21:51 missing "=" after "$USER:$PASS@unix(/cloudsql/$INSTANCE)/$DATABASE" in connection info string"

And, if I just add "=" after the connection string:
2017/08/18 16:24:38 failed to parse addr: "localhost:5432". It should conform to the regular expression "^\\[(.+)\\]:[0-9]+$"

And, the same error if I add something that conforms to the source's (!?) actual RegEx == ^\[(.+)\]:[0-9]+$ specifically just duplicate the $INSTANCE (project:region:instance):
Stumped.
https://github.com/GoogleCloudPlatform/cloudsql-proxy/blob/master/proxy/dialers/postgres/hook.go

Your dsn looks like the dsn for the MySQL driver used in Go examples. Every
driver has different dsn formats. What postgres driver are you using?
Please check the documentation for that driver for the dsn format.
I'd appreciate any updates of documentation that is not correct.

I'm trying to connect to a Cloud SQL PostreSQL instance using the Google-provided Cloud SQL Proxy.
Google's documentation for PostgreSQL incorrectly duplicates the MySQL instructions:
https://cloud.google.com/sql/docs/postgres/connect-external-app#go
The first dsn I provided is for when the cloudsql-proxy is used as a library in Go code. This works.
The second dsn I provided is the only example I have (from the Google documentation) for using the cloudsql-proxy as a "companion process" (sidecar-like). Because I don't have any other documentation to use, I'm stumped as to whether:
-- I can use the cloudsql-proxy as a companion process for PostreSQL as I can for MySQL
-- how to configure the dsn in this case

Sorry! I got it (finally). This is not proxy-specific, I just need to craft the dsn to use localhost and the examples I have look generic but must be MySQL-specific. Apologies!

Solution: The dialer is not needed for companion use of the Cloud SQL Proxy.
Will have the documentation folks update Google's documentation to make this use clearer:
import (
	_ "github.com/lib/pq"
)

And then:
UNIX sockets -- NB host value is prefixed with "/" to indicate UNIX socket:
	dsn := fmt.Sprintf("host=/%s user=%s dbname=%s password=%s sslmode=disable",
		instanceConnection,
		user,
		databaseName,
		password)

TCP sockets -- host defaults to localhost and port defaults to 5432 so not specified:
	dsn := fmt.Sprintf("user=%s dbname=%s password=%s sslmode=disable",
		user,
		databaseName,
		password)