dcos / dcos-ui Goto Github PK

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Error type: Preset name not found within published preset config (monorepo:babel6). Note: this is a nested preset so please contact the preset author if you are unable to fix it yourself.

Please refer to the ticket https://jira.mesosphere.com/browse/DCOS_OSS-2065

Possible solution https://jira.mesosphere.com/browse/DCOS_OSS-2065?focusedCommentId=176587&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-176587

https://jira.mesosphere.com/browse/DCOS_OSS-4270

It is impossible to restart Pods. We don't have this option on the services page but we still do on the detail page.

it doesn't exist on the Task detail table

But it is still there on the detail page

Everything around supporting this action should be removed

The DC/OS dashboard shows overall CPU and GPU allocation but uses the word "shares" when it's actually referring to the total number of "cores". This should just say "cores".

Hello,

I suddenly started receiving 'Access denied' when trying to log in to the Mesosphere DCOS gui, using Google-Github-Microsoft accounts, even though i know for a fact that the google and microsoft accounts are contained in the approved list.

When i curl -I dcos.auth0.com from one of the cluster nodes, it gives status 301 Moved Permanently to basically the auth0 product homepage.

Any ideas on how i can continue to log in without having to use auth0 authentication?

In the deployment Modal

https://github.com/dcos/dcos-ui/blob/master/plugins/services/src/js/components/DeploymentsModal.js#L232

On registry https://registry.npmjs.org/, the "latest" version (v1.0.0) of dependency conventional-changelog-lint-config-angular has the following deprecation notice:

renamed to commitlint: https://git.io/vQ1rU

Marking the latest version of an npm package as deprecated results in the entire package being considered deprecated, so contact the package author you think this is a mistake.

Affected package file(s): package.json

If you don't care about this, you can close this issue and not be warned about conventional-changelog-lint-config-angular's deprecation again. If you would like to completely disable all future deprecation warnings then add the following to your config:

"suppressNotifications": ["deprecationWarningIssues"]

🚨 The automated release from the pb/test-release branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the pb/test-release branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

A publish plugin returned an invalid value. It must return an Object.

The publish plugins must return an Object.

The publish function of the @semantic-release/exec returned 123 instead.

We recommend to report the issue to the @semantic-release/exec authors, providing the following informations:

• The semantic-release version: 16.0.2
• The semantic-release logs from your CI job
• The value returned by the plugin: 123
• A link to the semantic-release plugin developer guide: https://github.com/semantic-release/semantic-release/blob/master/docs/developer-guide/plugin.md

Good luck with your project ✨

Your semantic-release bot 📦🚀

On registry https://registry.npmjs.org/, the "latest" version (v6.24.1) of dependency babel-preset-es2015 has the following deprecation notice:

🙌 Thanks for using Babel: we recommend using babel-preset-env now: please read babeljs.io/env to update!

Marking the latest version of an npm package as deprecated results in the entire package being considered deprecated, so contact the package author you think this is a mistake.

Affected package file(s): package.json

If you don't care about this, you can close this issue and not be warned about babel-preset-es2015's deprecation again. If you would like to completely disable all future deprecation warnings then add the following to your config:

"suppressNotifications": ["deprecationWarningIssues"]

Please refer to the issue https://jira.mesosphere.com/browse/DCOS_OSS-4245

File to look:

On registry https://registry.npmjs.org/, the "latest" version (v2.1.1) of dependency conventional-changelog-lint has the following deprecation notice:

renamed to commitlint: https://git.io/vQ1rU

Marking the latest version of an npm package as deprecated results in the entire package being considered deprecated, so contact the package author you think this is a mistake.

Affected package file(s): package.json

If you don't care about this, you can close this issue and not be warned about conventional-changelog-lint's deprecation again. If you would like to completely disable all future deprecation warnings then add the following to your config:

"suppressNotifications": ["deprecationWarningIssues"]

🚨 The automated release from the 4.x branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the 4.x branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

No npm token specified.

An npm token must be created and set in the NPM_TOKEN environment variable on your CI environment.

Please make sure to create an npm token and to set it in the NPM_TOKEN environment variable on your CI environment. The token must allow to publish to the registry https://registry.npmjs.org/.

Good luck with your project ✨

Your semantic-release bot 📦🚀

On registry https://registry.npmjs.org/, the "latest" version (v1.0.0) of dependency conventional-changelog-lint-config-angular has the following deprecation notice:

renamed to commitlint: https://git.io/vQ1rU

Marking the latest version of an npm package as deprecated results in the entire package being considered deprecated, so contact the package author you think this is a mistake.

Affected package file(s): package.json

If you don't care about this, you can close this issue and not be warned about conventional-changelog-lint-config-angular's deprecation again. If you would like to completely disable all future deprecation warnings then add the following to your config:

"suppressNotifications": ["deprecationWarningIssues"]

Please refer to the ticket https://jira.mesosphere.com/browse/DCOS_OSS-1370

Needs to be added to: https://github.com/dcos/dcos-ui/blob/master/plugins/services/src/js/service-configuration/PodNetworkConfigSection.js

On registry https://registry.npmjs.org/, the "latest" version (v2.1.1) of dependency conventional-changelog-lint has the following deprecation notice:

renamed to commitlint: https://git.io/vQ1rU

Marking the latest version of an npm package as deprecated results in the entire package being considered deprecated, so contact the package author you think this is a mistake.

Affected package file(s): package.json

If you don't care about this, you can close this issue and not be warned about conventional-changelog-lint's deprecation again. If you would like to completely disable all future deprecation warnings then add the following to your config:

"suppressNotifications": ["deprecationWarningIssues"]