PlaceOS/backoffice

Issue on page Repositories

Closed this issue · 2 comments

@Bogdan-Vizcom commented on Tue Nov 10 2020

Describe the bug
"Pull the latest commit for this repository" on Place OS Drivers repository fails and does not show a clear error or reason for the failure.

To Reproduce
Steps to reproduce the behaviour:

  1. Go to Repos
  2. Click on Place OS Drivers
  3. Click on Pull
  4. After a little while see error: "Error pulling latest commit. Error: {}"

Expected behaviour

  1. The repo is pulled successfully without error; or
  2. If there is an error in pulling the repo, display information about the error which can help the user identify and rectify the problem.

Screenshots
image
image
image

Desktop (please complete the following information):

  • OS: Windows 10
  • Browser Chrome Version 86.0.4240.183 (Official Build) (64-bit)

Additional context

Hash: b746e20
Built: 09 Nov 2020, 8:42 AM


@MrYuion commented on Tue Nov 10 2020

Hmm... I can't reproduce this locally. Are you able to grab the console error or network request error to help me diagnose the issue?


@Bogdan-Vizcom commented on Wed Nov 11 2020

Hi,

I just tried “Pull” again and got same behaviour.

Below logs, from Log streams in AWS. Please let me know if you need more info.

[30m]
CloudWatch -> CloudWatch Logs -> Log groups -> placeos-test-deploy-service-core -> core/core/960dca4096eb4559a1afd202edb97fff


message
level=INFO time=2020-11-10T23:55:05Z source=action-controller client_ip=10.192.21.183 request_id=df2e7985-b719-446d-b6a9-d38d053a6cb5 event=response method=GET path=/api/core/v1/drivers?repository=place+os status=200 duration=1.42ms
level=INFO time=2020-11-10T23:58:53Z source=action-controller client_ip=10.192.21.183 request_id=4b825a24-4538-4b51-aa69-13e1efaa49e4 event=response method=GET path=/api/core/v1/drivers?repository=place+os status=200 duration=1.46ms
level=INFO time=2020-11-10T23:59:17Z source=action-controller client_ip=10.192.21.183 request_id=64c17ea3-4cae-434d-821a-2ba8b6922aab event=response method=GET path=/api/core/v1/drivers?repository=place+os status=200 duration=1.43ms
level=INFO time=2020-11-10T23:59:33Z source=action-controller client_ip=10.192.21.183 request_id=588c3eed-5485-45b9-8dfe-617a7af8901d event=response method=GET path=/api/core/v1/drivers?repository=place+os status=200 duration=1.48ms
level=INFO time=2020-11-11T00:03:43Z source=action-controller client_ip=10.192.21.183 request_id=ef14e0a1-3544-4e30-995a-534cf6a776f3 event=response method=GET path=/api/core/v1/drivers?repository=place+os status=200 duration=1.42ms
level=INFO time=2020-11-11T00:03:48Z source=action-controller client_ip=10.192.21.183 request_id=be43ae95-87d6-4f0d-a26b-fbbe1c2b4e7c event=response method=GET path=/api/core/v1/drivers?repository=place+os status=200 duration=1.45ms
level=INFO time=2020-11-11T00:03:56Z source=action-controller client_ip=10.192.21.183 request_id=b6bbcc4d-9730-4eac-887d-7016f2fa67f9 event=response method=GET path=/api/core/v1/drivers?repository=place+os status=200 duration=1.43ms

[30m]
CloudWatch -> CloudWatch Logs -> Log groups -> placeos-test-deploy-service-frontends -> frontends/frontends/e7cd65aa22cb4554a8cb62d620e729f3


message
level=INFO time=2020-11-11T00:00:00Z source=place_os.resource type=PlaceOS::Model::Repository handler=PlaceOS::Frontends::Loader action=Created id=repo-G2Ygux_SuNJ message=processing skipped
level=INFO time=2020-11-11T00:00:00Z source=place_os.frontends.loader type=PlaceOS::Model::Repository handler=PlaceOS::Frontends::Loader action=Created id=repo-G2XPXaE8h4b repository=backoffice branch=build-alpha uri=https://github.com/placeos/backoffice message=cloning repository
level=INFO time=2020-11-11T00:00:00Z source=place_os.frontends.loader type=PlaceOS::Model::Repository handler=PlaceOS::Frontends::Loader action=Created id=repo-G2XPXaE8h4b repository=backoffice branch=build-alpha uri=https://github.com/placeos/backoffice message=pulling repository
level=INFO time=2020-11-11T00:00:10Z source=place_os.frontends.loader type=PlaceOS::Model::Repository handler=PlaceOS::Frontends::Loader action=Created id=repo-G2XPXaE8h4b commit=fd55611 branch=build-alpha repository=backoffice repository_commit=HEAD uri=https://github.com/placeos/backoffice message=loaded repository
level=INFO time=2020-11-11T00:00:10Z source=place_os.resource type=PlaceOS::Model::Repository handler=PlaceOS::Frontends::Loader action=Created id=repo-G2XPXaE8h4b message=processed event
level=INFO time=2020-11-11T00:00:10Z source=place_os.resource type=PlaceOS::Model::Repository handler=PlaceOS::Frontends::Loader message=loaded 2 PlaceOS::Model::Repository resources

[Vizcom Technologies]https://www.vizcom.com.au/
Bogdan Popescu​
|
Software Manager
10 Leeway Court, Osborne Park, Western Australia 6017
T
+61 8 9242 8442
M
+61 438 441 243
W
www.vizcom.com.auhttps://www.vizcom.com.au/
[cid:image005.jpg@01D6B803.AD6B2060]
This email and any files transmitted with it are confidential and intended for use by the Addressee only. The confidential nature of the information contained in the email and/or file is not waived, lost or destroyed if it is sent in error to other than the Addressee. Use or dissemination of the information contained in the email and/or files by a recipient other than the Addressee may cause commercial damage to both/either the Sender and/or Addressee. If you are not the Addressee of this email/files please immediately contact the Sender and delete this email/files.

From: Alex Sorafumo notifications@github.com
Sent: Tuesday, 10 November 2020 7:40 PM
To: PlaceOS/backoffice backoffice@noreply.github.com
Cc: Bogdan Popescu bogdan.popescu@vizcom.com.au; Author author@noreply.github.com
Subject: Re: [PlaceOS/backoffice] Issue on page Repositories (#117)

Hmm... I can't reproduce this locally. Are you able to grab the console error or network request error to help me diagnose the issue?


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/PlaceOS/backoffice/issues/117#issuecomment-724648214, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ARWKR5OHJAR7FL6WJMOEC5DSPERAZANCNFSM4TQIASTA.


@MrYuion commented on Wed Nov 11 2020

Sorry if I wasn't being clear but are you able to grab any errors from the browser dev tools. I'm looking in particular at the console tab and network tab.
Screen Shot 2020-11-11 at 11 29 25 am


@Bogdan-Vizcom commented on Wed Nov 11 2020

alb-placeos-test-deploy-2014533901.eu-west-2.elb.amazonaws.com.zip


@Bogdan-Vizcom commented on Wed Nov 11 2020

Sent you an e-mail at alex@yuion.net with credentials to login to this PlaceOS instance.


@MrYuion commented on Wed Nov 11 2020

Thanks. Looks like the pull request is timing out. @stakach, are you able to have a look?


@Bogdan-Vizcom commented on Tue Mar 09 2021

Hi. Was this fixed? If so, in which version?


@MrYuion commented on Wed Mar 10 2021

There was some fixes made related to pulling repositories but this is not an issue with backoffice.
@caspiano, are you able to give an update?


@caspiano commented on Wed Mar 10 2021

@Bogdan-Vizcom the error response should be more descriptive in the next platform version.
Some changes were made to the repository update process but I, unfortunately, cannot confirm whether this resolves your issue with the information you've provided.
The cause of this could be a number of things, such as attempting to use an old core against new versions of drivers. We're currently building an independent driver compilation process to ensure these types of errors do not occur.

Sorry for the closure of the issue, we're moving to consolidate our issues against our release repository by the end of this week. I'll reopen and move the issue there when we do!


@jeremyw24 commented on Fri Jun 04 2021

Detect 503 error and report please wait. Human readable status response.

I'm not sure this is an issue anymore.
@caspiano, are you able to reproduce it?

I believe the issue should be closed and reopened under another title.
The intent is to have clearer rendering of errors, instead of the object, i.e. render the status code in a human readable fashion and the response body. it would be incredible if the request itself could be introspected for easy issue creation (so user does not need to open dev tools)