Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

more accurate error messages #1693

Closed
wants to merge 0 commits into from

Conversation

unglaublicherdude
Copy link

this just cost me some hours, searching for a malformed activity_id

Copy link
Collaborator

@artonge artonge left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks !

@artonge
Copy link
Collaborator

artonge commented May 28, 2024

@unglaublicherdude can you fix DCO, and also commit the result of npm run build?

@artonge
Copy link
Collaborator

artonge commented May 28, 2024

Not there yet @unglaublicherdude

@unglaublicherdude unglaublicherdude force-pushed the master branch 2 times, most recently from a507c70 to 4460703 Compare May 29, 2024 10:24
@unglaublicherdude
Copy link
Author

It is weird. When I run

npm ci
npm run build --if-present

I get this:

git diff -a
diff --git a/js/vendor.LICENSE.txt b/js/vendor.LICENSE.txt
index 338efa90..79e5b708 100644
--- a/js/vendor.LICENSE.txt
+++ b/js/vendor.LICENSE.txt
@@ -53,7 +53,7 @@ version: 2.1.0
 license: GPL-3.0-or-later
 
 @nextcloud/l10n
-version: 3.1.0
+version: 2.2.0
 license: GPL-3.0-or-later
 
 @nextcloud/logger

While its still this version:

  "dependencies": {
[...]
    "@nextcloud/l10n": "^3.1.0",

@artonge
Copy link
Collaborator

artonge commented May 29, 2024

Maybe a matter of npm or nodejs versions?

@unglaublicherdude
Copy link
Author

I added a devcontainer for that where I have those version.

vscode ➜ /workspaces/activity (master) $ node --version
v20.13.1
vscode ➜ /workspaces/activity (master) $ npm --version
10.5.2

They match, whats required in the packages.json

  "engines": {
    "node": "^20.0.0",
    "npm": "^10.0.0"
  },

@unglaublicherdude unglaublicherdude force-pushed the master branch 2 times, most recently from dabd7b2 to b8852b7 Compare May 29, 2024 15:35
@unglaublicherdude
Copy link
Author

unglaublicherdude commented May 29, 2024

I deleted my commit and made a new one. The npm run did not change the licence file. But I guess the pipeline will still fail, because with the npm run build in the pipeline it will again create it, right?

Like it did in my second try:
https://github.com/nextcloud/activity/actions/runs/9266274710/job/25490812190

@artonge
Copy link
Collaborator

artonge commented Jun 3, 2024

@unglaublicherdude I tried on my computer, and the LICENCE.txt is properly updated. Could you try again? Maybe you also need to delete your node_modules first.

Copy link
Contributor

Hello there,
Thank you so much for taking the time and effort to create a pull request to our Nextcloud project.

We hope that the review process is going smooth and is helpful for you. We want to ensure your pull request is reviewed to your satisfaction. If you have a moment, our community management team would very much appreciate your feedback on your experience with this PR review process.

Your feedback is valuable to us as we continuously strive to improve our community developer experience. Please take a moment to complete our short survey by clicking on the following link: https://cloud.nextcloud.com/apps/forms/s/i9Ago4EQRZ7TWxjfmeEpPkf6

Thank you for contributing to Nextcloud and we hope to hear from you soon!

(If you believe you should not receive this message, you can add yourself to the blocklist.)

@susnux
Copy link
Contributor

susnux commented Aug 25, 2024

Rebase gone wrong, sorry!
Copy can be found here: #1757

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants