Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Jan 27 14:36
    vascoguita closed #3633
  • Jan 27 14:19
    vascoguita synchronize #3633
  • Jan 27 14:01
    vascoguita ready_for_review #3633
  • Jan 27 14:00
    vascoguita synchronize #3633
  • Jan 27 14:00
    vascoguita edited #3633
  • Jan 27 13:39
    vascoguita synchronize #3633
  • Jan 27 10:58
    vascoguita synchronize #3633
  • Jan 27 10:50
    vascoguita synchronize #3633
  • Jan 27 10:44
    vascoguita synchronize #3633
  • Jan 27 10:39
    vascoguita edited #3633
  • Jan 27 10:39
    vascoguita converted_to_draft #3633
  • Jan 27 10:38
    vascoguita review_requested #3633
  • Jan 27 10:38
    vascoguita review_requested #3633
  • Jan 27 10:38
    vascoguita review_requested #3633
  • Jan 27 10:38
    vascoguita review_requested #3633
  • Jan 27 10:38
    vascoguita opened #3633
  • Jan 27 09:20
    vascoguita closed #3630
  • Jan 27 09:05
    vascoguita synchronize #3630
  • Jan 27 07:47
    glpatcern closed #3631
  • Jan 27 07:47
    glpatcern closed #3627
Samuel Alfageme
@SamuAlfageme
Hey @aduffeck, should be fixed now, thx for the tip :)
Andre Duffeck
@aduffeck
:thumbsup: thank you
Klaas Freitag
@dragotin
@labkode could you please add @fschade as a member of the CS3 org? He can not review in Reva currently which is not cool. For some reasons, I can not do it.
Hugo Labrador
@labkode
@dragotin I've bumped your permissions to have the same as me, you should be able to add people now
Antoon P.
@redblom

I suddenly can't seem to build. make imports gives lots of I/O, find dir errors errors while the dirs and objects are actually there.

# make imports
GOPROXY=off
echo BUILD_DATE=`date +%FT%T%z`
BUILD_DATE=2022-08-03T11:30:35+0000
echo GIT_COMMIT=`git rev-parse --short HEAD`
error: unable to open .git/objects/aa: I/O error
GIT_COMMIT=aab472df
echo GIT_DIRTY=`git diff-index --quiet HEAD -- || echo "dirty-"`
error: unable to open object pack directory: .git/objects/pack: I/O error
error: unable to open object pack directory: .git/objects/pack: I/O error
error: unable to open object pack directory: .git/objects/pack: I/O error
fatal: failed to read object aab472df17c5d73b2a5d312fc1aa8c1a53825255: I/O error
GIT_DIRTY=dirty-
echo VERSION=`git describe --always`
error: unable to open object pack directory: .git/objects/pack: I/O error
... etc.
fatal: Not a valid object name HEAD

Never seen this before. Anyone who can point me into the right direction?

Hugo Labrador
@labkode
@redblom that smells like your machine is screwed, nothing to do with Reva
disk full maybe?
Antoon P.
@redblom
Have checked that and no other issues currently, so had to check if it wasn't a reva issue. Thanks.
Gonna try a restart then, the ol' helpdesk solution ;)
Hugo Labrador
@labkode
Always reboot :)
butonic
@butonic:matrix.org
[m]
@labkode: cs3org/cs3apis#178 would be splendid!
butonic
@butonic:matrix.org
[m]
@glpatcern: is @labkode on vacation? could you merge cs3org/cs3apis#178
Giuseppe Lo Presti
@glpatcern
Hey @butonic:matrix.org I guess he is (and I am as well!), let me have a look this evening
Andre Duffeck
@aduffeck
@glpatcern thanks for merging :thumbsup: happy vacation!
Nyra Reddy
@nyrareddy
Are there any programs other than GSoC to support students. I see that CERN has this, anything specific to Reva for this Winter/Fall?
Klaas Freitag
@dragotin
@labkode hi Hugo, FYI, I (mis-) used my power to tweak the settings in codacy to not complain about missing "Package Comments" any more in Reva, that blocked PRs unexpectedly for us. I hope you did not enable it intentionally recently...
Hugo Labrador
@labkode
Hi Klaas, no I haven't changed that settings in long time.
Good it helped you
Antoon P.
@redblom
Can someone (@glpatcern, @labkode) review this: cs3org/reva#2979
Antoon P.
@redblom
Thank you @labkode
dragonchaser
@dragonchaser:matrix.datenschmutz.space
[m]
morning
@labkode / @glpatcern is the ci/network broken atm? reva ci is more then flaky for me today.
/cc @SamuAlfageme
there are lots of timeouts towards the registry for example
dragonchaser
@dragonchaser:matrix.datenschmutz.space
[m]
butonic
@butonic:matrix.org
[m]
@labkode @glpatcern @SamuAlfageme any insights on the CI status?
Giuseppe Lo Presti
@glpatcern
I understood from @SamuAlfageme that some interventions were going on in the image registry, or Sam did you find anything else?
butonic
@butonic:matrix.org
[m]
ok, latest runs seem to go smoother ...
Michael Barz
@micbar
@labkode @glpatcern Seems that the reva CI on edge and experimental is broken since cs3org/reva@636b2b6
I wonder what happened. Did you change the codacy secret?
Giuseppe Lo Presti
@glpatcern
@micbar there's some active ongoing work on that, yes, because we really have to get out of drone - our license expired long ago
The target is to move everything to GitHub workflows
Hugo Labrador
@labkode
I pinged the person working on that
Vasco Guita
@vascoguita
@micbar We are moving out from Drone. Drone was running the "coverage" job which was using the Codacy API but now we run the Codacy/GitHub integration so we don't need the API anymore.
Therefore I removed the API access token (maybe I shouldn't have done it yet). Anyway, rebasing on master should solve the problem.
Or just cherry-pick that commit
Michael Barz
@micbar

The target is to move everything to GitHub workflows

Seen that. I hope it doesn't break anyhthing during our planned code freeze.

Michael Barz
@micbar
@labkode I wrote you an email. We need to sync these changes. Today it cost us a 4h delay on the reva experimental branch.
Michael Barz
@micbar
@vascoguita where did the code coverage report go? IMO we need to send the coverage report to codacy. Can you do that with the Codacy/GitHub integration?
Michael Barz
@micbar
we have two test pipelines which create code coverage, unit tests and integration tests.
Both coverage reports should be sent to codacy and aggregated.
Vasco Guita
@vascoguita
@micbar they are still in the same place: https://app.codacy.com/gh/cs3org/reva/dashboard
But now, instead of being trigger for those 2 pipelines, codacy runs for every PR/push
Vasco Guita
@vascoguita
Have you found it?
This is the one for edge – https://app.codacy.com/gh/cs3org/reva/dashboard?branch=edge
And this is the one for experimental – https://app.codacy.com/gh/cs3org/reva/dashboard?branch=experimental
Michael Barz
@micbar
ok, found it.
Hugo Labrador
@labkode
We're having issues with the CI, its been not working since yesterday, looks like a kernel issue, we're debugging
butonic
@butonic:matrix.org
[m]
Thx!
Hugo Labrador
@labkode
The CI box has a faulty line card that will be replaced, we'll ping you back when the box is ready
That's why some jobs are not passing and timing out
Michael Barz
@micbar
@labkode Is there an ETA for the fix?
Hugo Labrador
@labkode
Hopefully today, linecard didn't help