Not running in TFS

Hi, we are trying to get your add-in to run on our TFS env but we are getting a SCRIPT5: Access is denied. error in IE, Firefox and Chrome any suggestions would be greatly appreciated. Please note that we have successfully used other Market Place add-ins in this environment.

15.117.26615.0, yes here they are:
Failed to load resource: the server responded with a status of 404 (Not Found)
/tfs/DefaultCollection/_apis/ExtensionManagement/InstalledExtensions/ms-devlabs/workitem-feature-timeline-extension/Data/Scopes/User/Me/Collections/%24settings/Documents/594afd2f-f489-4975-ab48-4255b213bd2e_iterationDisplayOptions:1 Failed to load resource: the server responded with a status of 404 (Not Found)
/tfs/DefaultCollection/_apis/ExtensionManagement/InstalledExtensions/ms-devlabs/workitem-feature-timeline-extension/Data/Scopes/Default/Current/Collections/%24settings/Documents/overriddenWorkItemIterations:1 Failed to load resource: the server responded with a status of 404 (Not Found)
VM22 Content:5 GET /tfs/DefaultCollection/_apis/ExtensionManagement/InstalledExtensions/ms-devlabs/workitem-feature-timeline-extension/Data/Scopes/User/Me/Collections/%24settings/Documents/594afd2f-f489-4975-ab48-4255b213bd2e_settings 404 (Not Found)
send @ VM22 Content:5
ajax @ VM22 Content:5
(anonymous) @ VM26 Content:52
c @ VM26 Content:28
(anonymous) @ VM26 Content:28
u.promiseDispatch @ VM26 Content:28
(anonymous) @ VM26 Content:28
t @ VM26 Content:28
VM120 react-dom.js:62 TypeError: Cannot read property 'length' of null
    at u (VM118 bundle.js:1)
    at VM118 bundle.js:1
    at Array.map (<anonymous>)
    at c (VM118 bundle.js:1)
    at u (VM118 bundle.js:1)
    at VM118 bundle.js:1
    at Array.map (<anonymous>)
    at c (VM118 bundle.js:1)
    at l (VM118 bundle.js:1)
    at t.getEpicHierarchy (VM118 bundle.js:1)

We just released an update ... can you try again?

Closing as we did not hear back, please reopen if are still facing this issue.

Good morning Navneet, unfortunately we have having the same issue with the latest version, we get many 404 against the package. would you be available for a WebEx to look at what is going on?
Sent from my BlackBerry 10 smartphone on the Bell network.
From: NAVNEET GUPTA
Sent: Tuesday, July 31, 2018 2:28 AM
To: Microsoft/featuretimeline
Reply To: Microsoft/featuretimeline
Cc: Daniel Godard; Author
Subject: Re: [Microsoft/featuretimeline] Not running in TFS (#18)
Closing as we did not hear back, please reopen if are still facing this issue.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/featuretimeline/issues/18#issuecomment-409109831, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AFE66KVwXSWdiEVDbk-voqBshU9JcfZKks5uL_kdgaJpZM4VCyuQ.

Sure ... What time suits you today?
On Aug 2, 2018 03:26, Daniel Godard<EMAIL_ADDRESS>wrote:
Good morning Navneet, unfortunately we have having the same issue with the latest version, we get many 404 against the package. would you be available for a WebEx to look at what is going on?
Sent from my BlackBerry 10 smartphone on the Bell network.
From: NAVNEET GUPTA
Sent: Tuesday, July 31, 2018 2:28 AM
To: Microsoft/featuretimeline
Reply To: Microsoft/featuretimeline
Cc: Daniel Godard; Author
Subject: Re: [Microsoft/featuretimeline] Not running in TFS (#18)
Closing as we did not hear back, please reopen if are still facing this issue.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/featuretimeline/issues/18#issuecomment-409109831, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AFE66KVwXSWdiEVDbk-voqBshU9JcfZKks5uL_kdgaJpZM4VCyuQ.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/featuretimeline/issues/18#issuecomment-409881123, or mute the threadhttps://github.com/notifications/unsubscribe-auth/Aaf79vCLkisSgy0DkVinWZiqVxMpknl1ks5uMtPxgaJpZM4VCyuQ.

Sorry, my day got overrun by events, would you be available tomorrow morning around 10?
Sent from my BlackBerry 10 smartphone on the Bell network.
From: NAVNEET GUPTA
Sent: Thursday, August 2, 2018 9:06 AM
To: Microsoft/featuretimeline
Reply To: Microsoft/featuretimeline
Cc: Daniel Godard; Author
Subject: Re: [Microsoft/featuretimeline] Not running in TFS (#18)
Sure ... What time suits you today?
On Aug 2, 2018 03:26, Daniel Godard<EMAIL_ADDRESS>wrote:
Good morning Navneet, unfortunately we have having the same issue with the latest version, we get many 404 against the package. would you be available for a WebEx to look at what is going on?
Sent from my BlackBerry 10 smartphone on the Bell network.
From: NAVNEET GUPTA
Sent: Tuesday, July 31, 2018 2:28 AM
To: Microsoft/featuretimeline
Reply To: Microsoft/featuretimeline
Cc: Daniel Godard; Author
Subject: Re: [Microsoft/featuretimeline] Not running in TFS (#18)
Closing as we did not hear back, please reopen if are still facing this issue.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/featuretimeline/issues/18#issuecomment-409109831, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AFE66KVwXSWdiEVDbk-voqBshU9JcfZKks5uL_kdgaJpZM4VCyuQ.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/featuretimeline/issues/18#issuecomment-409881123, or mute the threadhttps://github.com/notifications/unsubscribe-auth/Aaf79vCLkisSgy0DkVinWZiqVxMpknl1ks5uMtPxgaJpZM4VCyuQ.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/featuretimeline/issues/18#issuecomment-409919342, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AFE66FSqD7n32ljoxI0udCiYsdxej28sks5uMvlZgaJpZM4VCyuQ.

10 am PST tomorrow morning is fine with me.
On Aug 2, 2018 12:19, Daniel Godard<EMAIL_ADDRESS>wrote:
Sorry, my day got overrun by events, would you be available tomorrow morning around 10?
Sent from my BlackBerry 10 smartphone on the Bell network.
From: NAVNEET GUPTA
Sent: Thursday, August 2, 2018 9:06 AM
To: Microsoft/featuretimeline
Reply To: Microsoft/featuretimeline
Cc: Daniel Godard; Author
Subject: Re: [Microsoft/featuretimeline] Not running in TFS (#18)
Sure ... What time suits you today?
On Aug 2, 2018 03:26, Daniel Godard<EMAIL_ADDRESS>wrote:
Good morning Navneet, unfortunately we have having the same issue with the latest version, we get many 404 against the package. would you be available for a WebEx to look at what is going on?
Sent from my BlackBerry 10 smartphone on the Bell network.
From: NAVNEET GUPTA
Sent: Tuesday, July 31, 2018 2:28 AM
To: Microsoft/featuretimeline
Reply To: Microsoft/featuretimeline
Cc: Daniel Godard; Author
Subject: Re: [Microsoft/featuretimeline] Not running in TFS (#18)
Closing as we did not hear back, please reopen if are still facing this issue.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/featuretimeline/issues/18#issuecomment-409109831, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AFE66KVwXSWdiEVDbk-voqBshU9JcfZKks5uL_kdgaJpZM4VCyuQ.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/featuretimeline/issues/18#issuecomment-409881123, or mute the threadhttps://github.com/notifications/unsubscribe-auth/Aaf79vCLkisSgy0DkVinWZiqVxMpknl1ks5uMtPxgaJpZM4VCyuQ.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/featuretimeline/issues/18#issuecomment-409919342, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AFE66FSqD7n32ljoxI0udCiYsdxej28sks5uMvlZgaJpZM4VCyuQ.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/featuretimeline/issues/18#issuecomment-410038283, or mute the threadhttps://github.com/notifications/unsubscribe-auth/Aaf79u-wvBZq9WWmFgKKqVZC6_e2vNteks5uM1DKgaJpZM4VCyuQ.

Ok will send you and invite, cheers !
Sent from my BlackBerry 10 smartphone on the Bell network.
From: NAVNEET GUPTA
Sent: Thursday, August 2, 2018 3:50 PM
To: Microsoft/featuretimeline
Reply To: Microsoft/featuretimeline
Cc: Daniel Godard; Author
Subject: Re: [Microsoft/featuretimeline] Not running in TFS (#18)
10 am PST tomorrow morning is fine with me.
On Aug 2, 2018 12:19, Daniel Godard<EMAIL_ADDRESS>wrote:
Sorry, my day got overrun by events, would you be available tomorrow morning around 10?
Sent from my BlackBerry 10 smartphone on the Bell network.
From: NAVNEET GUPTA
Sent: Thursday, August 2, 2018 9:06 AM
To: Microsoft/featuretimeline
Reply To: Microsoft/featuretimeline
Cc: Daniel Godard; Author
Subject: Re: [Microsoft/featuretimeline] Not running in TFS (#18)
Sure ... What time suits you today?
On Aug 2, 2018 03:26, Daniel Godard<EMAIL_ADDRESS>wrote:
Good morning Navneet, unfortunately we have having the same issue with the latest version, we get many 404 against the package. would you be available for a WebEx to look at what is going on?
Sent from my BlackBerry 10 smartphone on the Bell network.
From: NAVNEET GUPTA
Sent: Tuesday, July 31, 2018 2:28 AM
To: Microsoft/featuretimeline
Reply To: Microsoft/featuretimeline
Cc: Daniel Godard; Author
Subject: Re: [Microsoft/featuretimeline] Not running in TFS (#18)
Closing as we did not hear back, please reopen if are still facing this issue.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/featuretimeline/issues/18#issuecomment-409109831, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AFE66KVwXSWdiEVDbk-voqBshU9JcfZKks5uL_kdgaJpZM4VCyuQ.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/featuretimeline/issues/18#issuecomment-409881123, or mute the threadhttps://github.com/notifications/unsubscribe-auth/Aaf79vCLkisSgy0DkVinWZiqVxMpknl1ks5uMtPxgaJpZM4VCyuQ.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/featuretimeline/issues/18#issuecomment-409919342, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AFE66FSqD7n32ljoxI0udCiYsdxej28sks5uMvlZgaJpZM4VCyuQ.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/featuretimeline/issues/18#issuecomment-410038283, or mute the threadhttps://github.com/notifications/unsubscribe-auth/Aaf79u-wvBZq9WWmFgKKqVZC6_e2vNteks5uM1DKgaJpZM4VCyuQ.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/featuretimeline/issues/18#issuecomment-410046996, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AFE66GvxedHWfUZkZi35L9g8tCBsRduIks5uM1f_gaJpZM4VCyuQ.

Good morning, what email address should I use to send you the invite ?
Sent from my BlackBerry 10 smartphone on the Bell network.
From: NAVNEET GUPTA
Sent: Thursday, August 2, 2018 3:50 PM
To: Microsoft/featuretimeline
Reply To: Microsoft/featuretimeline
Cc: Daniel Godard; Author
Subject: Re: [Microsoft/featuretimeline] Not running in TFS (#18)
10 am PST tomorrow morning is fine with me.
On Aug 2, 2018 12:19, Daniel Godard<EMAIL_ADDRESS>wrote:
Sorry, my day got overrun by events, would you be available tomorrow morning around 10?
Sent from my BlackBerry 10 smartphone on the Bell network.
From: NAVNEET GUPTA
Sent: Thursday, August 2, 2018 9:06 AM
To: Microsoft/featuretimeline
Reply To: Microsoft/featuretimeline
Cc: Daniel Godard; Author
Subject: Re: [Microsoft/featuretimeline] Not running in TFS (#18)
Sure ... What time suits you today?
On Aug 2, 2018 03:26, Daniel Godard<EMAIL_ADDRESS>wrote:
Good morning Navneet, unfortunately we have having the same issue with the latest version, we get many 404 against the package. would you be available for a WebEx to look at what is going on?
Sent from my BlackBerry 10 smartphone on the Bell network.
From: NAVNEET GUPTA
Sent: Tuesday, July 31, 2018 2:28 AM
To: Microsoft/featuretimeline
Reply To: Microsoft/featuretimeline
Cc: Daniel Godard; Author
Subject: Re: [Microsoft/featuretimeline] Not running in TFS (#18)
Closing as we did not hear back, please reopen if are still facing this issue.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/featuretimeline/issues/18#issuecomment-409109831, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AFE66KVwXSWdiEVDbk-voqBshU9JcfZKks5uL_kdgaJpZM4VCyuQ.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/featuretimeline/issues/18#issuecomment-409881123, or mute the threadhttps://github.com/notifications/unsubscribe-auth/Aaf79vCLkisSgy0DkVinWZiqVxMpknl1ks5uMtPxgaJpZM4VCyuQ.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/featuretimeline/issues/18#issuecomment-409919342, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AFE66FSqD7n32ljoxI0udCiYsdxej28sks5uMvlZgaJpZM4VCyuQ.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/featuretimeline/issues/18#issuecomment-410038283, or mute the threadhttps://github.com/notifications/unsubscribe-auth/Aaf79u-wvBZq9WWmFgKKqVZC6_e2vNteks5uM1DKgaJpZM4VCyuQ.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/featuretimeline/issues/18#issuecomment-410046996, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AFE66GvxedHWfUZkZi35L9g8tCBsRduIks5uM1f_gaJpZM4VCyuQ.

<EMAIL_ADDRESS>Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10

From: Daniel Godard<EMAIL_ADDRESS>Sent: Friday, August 3, 2018 7:19:46 AM
To: Microsoft/featuretimeline
Cc: NAVNEET GUPTA; State change
Subject: Re: [Microsoft/featuretimeline] Not running in TFS (#18)
Good morning, what email address should I use to send you the invite ?
Sent from my BlackBerry 10 smartphone on the Bell network.
From: NAVNEET GUPTA
Sent: Thursday, August 2, 2018 3:50 PM
To: Microsoft/featuretimeline
Reply To: Microsoft/featuretimeline
Cc: Daniel Godard; Author
Subject: Re: [Microsoft/featuretimeline] Not running in TFS (#18)
10 am PST tomorrow morning is fine with me.
On Aug 2, 2018 12:19, Daniel Godard<EMAIL_ADDRESS>wrote:
Sorry, my day got overrun by events, would you be available tomorrow morning around 10?
Sent from my BlackBerry 10 smartphone on the Bell network.
From: NAVNEET GUPTA
Sent: Thursday, August 2, 2018 9:06 AM
To: Microsoft/featuretimeline
Reply To: Microsoft/featuretimeline
Cc: Daniel Godard; Author
Subject: Re: [Microsoft/featuretimeline] Not running in TFS (#18)
Sure ... What time suits you today?
On Aug 2, 2018 03:26, Daniel Godard<EMAIL_ADDRESS>wrote:
Good morning Navneet, unfortunately we have having the same issue with the latest version, we get many 404 against the package. would you be available for a WebEx to look at what is going on?
Sent from my BlackBerry 10 smartphone on the Bell network.
From: NAVNEET GUPTA
Sent: Tuesday, July 31, 2018 2:28 AM
To: Microsoft/featuretimeline
Reply To: Microsoft/featuretimeline
Cc: Daniel Godard; Author
Subject: Re: [Microsoft/featuretimeline] Not running in TFS (#18)
Closing as we did not hear back, please reopen if are still facing this issue.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/featuretimeline/issues/18#issuecomment-409109831, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AFE66KVwXSWdiEVDbk-voqBshU9JcfZKks5uL_kdgaJpZM4VCyuQ.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/featuretimeline/issues/18#issuecomment-409881123, or mute the threadhttps://github.com/notifications/unsubscribe-auth/Aaf79vCLkisSgy0DkVinWZiqVxMpknl1ks5uMtPxgaJpZM4VCyuQ.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/featuretimeline/issues/18#issuecomment-409919342, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AFE66FSqD7n32ljoxI0udCiYsdxej28sks5uMvlZgaJpZM4VCyuQ.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/featuretimeline/issues/18#issuecomment-410038283, or mute the threadhttps://github.com/notifications/unsubscribe-auth/Aaf79u-wvBZq9WWmFgKKqVZC6_e2vNteks5uM1DKgaJpZM4VCyuQ.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/featuretimeline/issues/18#issuecomment-410046996, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AFE66GvxedHWfUZkZi35L9g8tCBsRduIks5uM1f_gaJpZM4VCyuQ.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/featuretimeline/issues/18#issuecomment-410264913, or mute the threadhttps://github.com/notifications/unsubscribe-auth/Aaf79tvjmmg18OQMliD_scqG82PAjIVVks5uNFwCgaJpZM4VCyuQ.

I have not received the invite yet, are we meeting at 10:30?

From: Navneet Gupta<EMAIL_ADDRESS>Sent: Friday, August 3, 2018 7:20 AM
To: Microsoft/featuretimeline; Microsoft/featuretimeline
Cc: State change
Subject: RE: [Microsoft/featuretimeline] Not running in TFS (#18)
<EMAIL_ADDRESS>Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10

From: Daniel Godard<EMAIL_ADDRESS>Sent: Friday, August 3, 2018 7:19:46 AM
To: Microsoft/featuretimeline
Cc: NAVNEET GUPTA; State change
Subject: Re: [Microsoft/featuretimeline] Not running in TFS (#18)
Good morning, what email address should I use to send you the invite ?
Sent from my BlackBerry 10 smartphone on the Bell network.
From: NAVNEET GUPTA
Sent: Thursday, August 2, 2018 3:50 PM
To: Microsoft/featuretimeline
Reply To: Microsoft/featuretimeline
Cc: Daniel Godard; Author
Subject: Re: [Microsoft/featuretimeline] Not running in TFS (#18)
10 am PST tomorrow morning is fine with me.
On Aug 2, 2018 12:19, Daniel Godard<EMAIL_ADDRESS>wrote:
Sorry, my day got overrun by events, would you be available tomorrow morning around 10?
Sent from my BlackBerry 10 smartphone on the Bell network.
From: NAVNEET GUPTA
Sent: Thursday, August 2, 2018 9:06 AM
To: Microsoft/featuretimeline
Reply To: Microsoft/featuretimeline
Cc: Daniel Godard; Author
Subject: Re: [Microsoft/featuretimeline] Not running in TFS (#18)
Sure ... What time suits you today?
On Aug 2, 2018 03:26, Daniel Godard<EMAIL_ADDRESS>wrote:
Good morning Navneet, unfortunately we have having the same issue with the latest version, we get many 404 against the package. would you be available for a WebEx to look at what is going on?
Sent from my BlackBerry 10 smartphone on the Bell network.
From: NAVNEET GUPTA
Sent: Tuesday, July 31, 2018 2:28 AM
To: Microsoft/featuretimeline
Reply To: Microsoft/featuretimeline
Cc: Daniel Godard; Author
Subject: Re: [Microsoft/featuretimeline] Not running in TFS (#18)
Closing as we did not hear back, please reopen if are still facing this issue.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/featuretimeline/issues/18#issuecomment-409109831, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AFE66KVwXSWdiEVDbk-voqBshU9JcfZKks5uL_kdgaJpZM4VCyuQ.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/featuretimeline/issues/18#issuecomment-409881123, or mute the threadhttps://github.com/notifications/unsubscribe-auth/Aaf79vCLkisSgy0DkVinWZiqVxMpknl1ks5uMtPxgaJpZM4VCyuQ.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/featuretimeline/issues/18#issuecomment-409919342, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AFE66FSqD7n32ljoxI0udCiYsdxej28sks5uMvlZgaJpZM4VCyuQ.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/featuretimeline/issues/18#issuecomment-410038283, or mute the threadhttps://github.com/notifications/unsubscribe-auth/Aaf79u-wvBZq9WWmFgKKqVZC6_e2vNteks5uM1DKgaJpZM4VCyuQ.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/featuretimeline/issues/18#issuecomment-410046996, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AFE66GvxedHWfUZkZi35L9g8tCBsRduIks5uM1f_gaJpZM4VCyuQ.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/featuretimeline/issues/18#issuecomment-410264913, or mute the threadhttps://github.com/notifications/unsubscribe-auth/Aaf79tvjmmg18OQMliD_scqG82PAjIVVks5uNFwCgaJpZM4VCyuQ.


Bind address option not documented

Description
In order to allow  multiple instances or to make the port accessible from outside of the Docker container you have to bind cloud sql proxy to tcp:<IP_ADDRESS>:<PORT_NUMBER>, but this setting is not documented in the help of the script or in the documentation page.

❯ ./cloud_sql_proxy --version
Cloud SQL Proxy: version 1.16; sha e802c2cb94aec939bfe7497637c5685d3dddd6af built Wed Oct  9 22:22:13 UTC 2019
❯ ./cloud_sql_proxy --help
The Cloud SQL Proxy allows simple, secure connectivity to Google Cloud SQL. It
is a long-running process that opens local sockets (either TCP or Unix sockets)
according to the parameters passed to it. A local application connects to a
Cloud SQL instance by using the corresponding socket.
Connection:
-instances
To connect to a specific list of instances, set the instances parameter
to a comma-separated list of instance connection strings. For example:
       -instances=my-project:my-region:my-instance

For connectivity over TCP, you must specify a tcp port as part of the
instance string. For example, the following example opens a loopback TCP
socket on port 3306, which will be proxied to connect to the instance
'my-instance' in project 'my-project':

        -instances=my-project:my-region:my-instance=tcp:3306

 When connecting over TCP, the -instances parameter is required.

Solution
In this Google documentation page, there is an example1 which is exactly the use case that I'm describing,  this example should be taken as a reference and included in the documentation.
By default I'm assuming that the bind is done on <IP_ADDRESS> so the help section should be probably changed in something similar to this :

❯ ./cloud_sql_proxy --help
The Cloud SQL Proxy allows simple, secure connectivity to Google Cloud SQL. It
is a long-running process that opens local sockets (either TCP or Unix sockets)
according to the parameters passed to it. A local application connects to a
Cloud SQL instance by using the corresponding socket.
Connection:
-instances
To connect to a specific list of instances, set the instances parameter
to a comma-separated list of instance connection strings. For example:
       -instances=my-project:my-region:my-instance

For connectivity over TCP, you must specify a tcp port as part of the
instance string. For example, the following example opens a loopback TCP
socket on port 3306, which will be proxied to connect to the instance
'my-instance' in project 'my-project'. For scenarios where you have to make
the socket open from outside you can change the <custom_bind_address> to <IP_ADDRESS>

        -instances=my-project:my-region:my-instance=tcp:<custom_bind_address>:3306

 When connecting over TCP, the -instances parameter is required.

This is documented in our Authorization with the Cloud SQL Proxy page as well, but I agree it should be mentioned in the readme and help flag.

This is documented in our Authorization with the Cloud SQL Proxy page as well, but I agree it should be mentioned in the readme and help flag.

No it isn't. Please show where.

v1: https://github.com/GoogleCloudPlatform/cloud-sql-proxy/tree/v1#tcp-socket-example
v2: https://github.com/GoogleCloudPlatform/cloud-sql-proxy#configuring-listening-address


fix: patch /blueprints/:id wouldn't handle byte[]

Summary
PATCH /blueprints/:id was using mapstructure.Decode for blueprint partial update, which was unable to handle datatypes.JSON or json.RawMessage.
This fix enhanced the helper.DecodeMapStruct to handle the situation, and replaced mapstructure.Decode with it.
Does this close any open issues?
Closes #2658
Screenshots

LGTM, please cherry-pick this fix to v0.12-rc2 verson.


node join-request (OTTA) failed

I installed all momponents by following https://www.loraserver.io/install/quick-install/ and setup in Lora App Server WebUI interface (including nodes' DevEUI、AppKey)  . I can see Gateway activity but my nodes can not join in.
type mosquitto_sub -t "gateway/#" -u loraroot -P {XXXXXX} -v I can see Gateway stats package once a minute. After I start the power of nodes, Ican see join-request like:

gateway/0002e4956e4bb547/rx {"rxInfo":{"mac":"0002e4956e4bb547","time":"2018-05-21T14:11:24.408761Z","timeSinceGPSEpoch":"336374h11m43.408s","timestamp":1961806796,"frequency":481500000,"channel":0,"rfChain":0,"crcStatus":1,"codeRate":"4/5","rssi":-65,"loRaSNR":7,"size":23,"dataRate":{"modulation":"LORA","spreadFactor":9,"bandwidth":125},"board":0,"antenna":0},"phyPayload":"AAEAAAAAAAAA////EAAAEBNdRWs6u14="}

gateway/0002e4956e4bb547/rx {"rxInfo":{"mac":"0002e4956e4bb547","time":"2018-05-21T14:11:31.458314Z","timeSinceGPSEpoch":"336374h11m50.457s","timestamp":1968856340,"frequency":481900000,"channel":2,"rfChain":0,"crcStatus":1,"codeRate":"4/5","rssi":-63,"loRaSNR":8,"size":23,"dataRate":{"modulation":"LORA","spreadFactor":9,"bandwidth":125},"board":0,"antenna":0},"phyPayload":"AAEAAAAAAAAA////EAAAEBPBdC3K/ZI="}

So what's wrong with my configurations ? Is that because I run sudo systemctl start loraserver or something simply ?

Please see: https://forum.loraserver.io/t/node-activation-otaa-issues/474.


[Question] (jdk11+scala2.12.16) An error is reported when the Linkis project is fully compiled

Before asking

[X] I have read the How to ask for help (我已阅读如何寻求帮助指引文档).

Your environment

Linkis version used: 1.1.2
Environment name and version:

cdh-5.14.2
hdp-3.1.5
hive-2.1.1
spark-3.2.1
scala-2.12.2
jdk 1.8.0_121
....

Describe your questions
(jdk11+scala2.12.16) An error is reported when the Linkis project is fully compiled
mv n -N install
mvn clean install error

File-->Settings-->Build,Execution,Deployment-->Compiler-->scala compiler , modify the compiler order to Scala Then Java build project and report an error

Eureka service list

eg:
Some logs info or acctch file

linkis-xxx.log:

<!--日志文字贴到这里-->

log file:

linkis-xxx.log

specific code branch?
Compatibility issues with JDK11 The current compatibility issues with JDK11 are as follows
sun.misc.{Signal, SignalHandler}
import sun.misc.Unsafe;
Like hadoop, the requirements for the jdk version, hadoop2.7 does not support jdk11
There are already students in the community who are doing adaptation follow-up, you can pay attention to the corresponding feature progress, or temporarily use the JDK8 version
具体代码分支？
JDK11的兼容性问题 目前对于JDK11的兼容性问题如下
sun.misc.{Signal, SignalHandler}
import sun.misc.Unsafe;
像hadoop之类的，对jdk版本的要求，hadoop2.7都不支持jdk11
社区已经有同学在做适配跟进，可以关注对应的特性进展，或则暂时先使用JDK8版本


Remove preview docker images when closing PR

Closes #14
We're using GHCR - Github container registry which is currently in beta. I was planning to delete images using Github GraphQL API, but this is not supported yet by GHCR 😞
Delete container image (ghcr beta): https://docs.github.com/en/packages/guides/deleting-a-container-image
Quote:
You can remove an entire container image or a specific version on GitHub.
To delete a container image, you must use the UI. Using
GraphQL to delete a container image is not supported at this time.

To delete a container image, you must have admin permissions to the container image.

When deleting public packages, be aware that you may break projects that depend on your package.

No packages returned by Github API:

One last thing to try:
can we use standard docker commands to delete image?
=> nope...
Apparently this feature is coming soon, hopefully by the end of (last) month? 😉
https://github.community/t/are-there-plans-to-support-deletions-of-images-in-ghcr/153728
But we’re working on a delete API that could be used on PR merge. Hoping to have this out by end of month.
@ralftar :
I guess we'll just have to wait for this feature to be released? Or switch to another package registry? Or try to "hack it" using the same http requests as the Github UI (but I want to wait..)

We'll wait 👍

Update:
this is now released-ish..
See this action for deleting packages:
https://github.com/marketplace/actions/delete-package-versions
but that is marked as unmaintained..: https://github.com/actions/delete-package-versions/issues/36
Also it doesn't support deleting docker images:
https://github.com/actions/delete-package-versions/issues/35
Perhaps this one is worth checking out?:
https://github.com/SmartsquareGmbH/delete-old-packages/issues/5

https://github.com/marketplace/actions/delete-a-package

https://github.com/marketplace?type=actions&query=delete+package

I'm facing the same problem and I'l probably use this:
https://github.com/marketplace/actions/delete-untagged-containers
Found via:
https://github.com/marketplace?type=actions&query=delete+container

https://github.com/marketplace/actions/ghcr-delete-image
test this one?


fix: defineslots empty function error (#4091)

When using defineSlots without a function argument it would throw an error as paramType can be undefined in that case. By adding this check this can be prevented.
I used a getAnyType now in case of no types, but I'm not sure if that is the best approach. The equivelent using a template-slot will generate an empty object as type. I'm not sure why and how to replicate that in this code, feel free to improve.

@johnsoncodehk There are build errors introduced by the auto-fix workflow that you added. A heads up as you might want to know.

LGTM, thanks!


Restart operation stuck in executing

Describe the bug
We've installed thin-edge on a custom board with a custom package-manager.
We also had to relocate the tmp.path to a non-volatile path:
$ tedge config list
...
tmp.path=/mnt/data/tedge/download
...

When I trigger a restart from c8y the device restarts, but the agent does not set the operation to successful.
I checked the log, but I could find anything pointing me to the error.
Log:
$ cat /var/log/tedge-agent.err
2023-08-11T08:13:24.09699871Z  INFO flockfile::unix: Lockfile created "/run/lock/tedge-agent.lock"
2023-08-11T08:13:24.097237419Z  INFO tedge_agent::agent: tedge-agent starting
2023-08-11T08:13:24.097401085Z  INFO sm-agent: tedge_agent::agent: Starting tedge agent
2023-08-11T08:13:24.104584794Z  INFO Runtime: Started
2023-08-11T08:13:24.10618296Z  INFO Runtime: Running Signal-Handler-0
2023-08-11T08:13:24.109716335Z  INFO Runtime: Running HttpFileTransferServer-1
2023-08-11T08:13:24.122435544Z  INFO Runtime: Running MQTT-2
2023-08-11T08:13:24.14085996Z  INFO Runtime: Running RestartManagerActor-3
2023-08-11T08:13:24.140973794Z  INFO Runtime: Running SoftwareManagerActor-4
2023-08-11T08:13:24.141049127Z  INFO Runtime: Running TedgeOperationConverter-5
2023-08-11T08:13:24.141117002Z  INFO Runtime: Running HealthMonitorActor-6
2023-08-11T08:13:24.141268585Z  INFO tedge-agent: send Message { topic: Topic { name: "tedge/health/tedge-agent" }, payload: "{"pid":2838,"status":"up","time":1691741604}", qos: AtLeastOnce, retain: true }
2023-08-11T08:13:24.621208585Z  INFO plugin_sm::plugin_manager: Plugin activated: /mnt/data/tedge/sm-plugins/cds
2023-08-11T08:13:33.55458817Z  INFO plugin_sm::plugin_manager: Plugin activated: /mnt/data/tedge/sm-plugins/ap
2023-08-11T08:13:33.554966295Z  INFO plugin_sm::plugin_manager: Default plugin type: ap
2023-08-11T08:13:33.570519378Z ERROR mqtt_channel::connection: MQTT connection error: Timeout
2023-08-11T08:13:33.614210211Z  INFO mqtt_channel::connection: MQTT connection established
2023-08-11T08:13:33.619202461Z  INFO MQTT: recv Ok(Some(Message { topic: Topic { name: "tedge/health/tedge-agent" }, payload: "{"pid":2838,"status":"up","time":1691741604}", qos: AtLeastOnce, retain: true }))
2023-08-11T08:13:33.714825795Z  INFO MQTT: send Message { topic: Topic { name: "tedge/commands/req/software/list" }, payload: "{"id":"ZpDTcMeq4_HqEQ3S5Xe4P"}", qos: AtLeastOnce, retain: false }
2023-08-11T08:13:33.71507942Z  INFO Mqtt-Request-Converter: recv Some(MqttMessage(Message { topic: Topic { name: "tedge/commands/req/software/list" }, payload: "{"id":"ZpDTcMeq4_HqEQ3S5Xe4P"}", qos: AtLeastOnce, retain: false }))
2023-08-11T08:13:33.715203628Z  INFO SoftwareSender: send SoftwareListRequest(SoftwareListRequest { id: "ZpDTcMeq4_HqEQ3S5Xe4P" })

2023-08-11T08:13:33.715303753Z  INFO SoftwareManager: recv Some(SoftwareListRequest(SoftwareListRequest { id: "ZpDTcMeq4_HqEQ3S5Xe4P" }))
2023-08-11T08:13:33.723645586Z  INFO SoftwareManager: send SoftwareListResponse(SoftwareListResponse { response: SoftwareRequestResponse { id: "ZpDTcMeq4_HqEQ3S5Xe4P", status: Executing, reason: None, current_software_list: None, failures: [] } })
2023-08-11T08:13:33.737589878Z  INFO Mqtt-Request-Converter: recv Some(SoftwareResponse(SoftwareListResponse(SoftwareListResponse { response: SoftwareRequestResponse { id: "ZpDTcMeq4_HqEQ3S5Xe4P", status: Executing, reason: None, current_software_list: None, failures: [] } })))
2023-08-11T08:13:33.737821003Z  INFO MqttPublisher: send Message { topic: Topic { name: "tedge/commands/res/software/list" }, payload: "{"id":"ZpDTcMeq4_HqEQ3S5Xe4P","status":"executing"}", qos: AtLeastOnce, retain: false }
2023-08-11T08:13:33.738023628Z  INFO MQTT: recv Ok(Some(Message { topic: Topic { name: "tedge/commands/res/software/list" }, payload: "{"id":"ZpDTcMeq4_HqEQ3S5Xe4P","status":"executing"}", qos: AtLeastOnce, retain: false }))
2023-08-11T08:13:44.478300131Z  INFO SoftwareManager: send SoftwareListResponse(SoftwareListResponse { response: SoftwareRequestResponse { id: "ZpDTcMeq4_HqEQ3S5Xe4P", status: Successful, reason: None, current_software_list: Some([SoftwareRequestResponseSoftwareList { plugin_type: "ap", modules: [SoftwareModuleItem { name: "thin-edge", version: Some("0.12.0_0.8.4"), url: None, action: None, reason: None }, SoftwareModuleItem { name: "CODESYS", version: Some("<IP_ADDRESS>-38"), url: None, action: None, reason: None }] }, SoftwareRequestResponseSoftwareList { plugin_type: "cds", modules: [] }]), failures: [] } })
2023-08-11T08:13:44.484829667Z  INFO Mqtt-Request-Converter: recv Some(SoftwareResponse(SoftwareListResponse(SoftwareListResponse { response: SoftwareRequestResponse { id: "ZpDTcMeq4_HqEQ3S5Xe4P", status: Successful, reason: None, current_software_list: Some([SoftwareRequestResponseSoftwareList { plugin_type: "ap", modules: [SoftwareModuleItem { name: "thin-edge", version: Some("0.12.0_0.8.4"), url: None, action: None, reason: None }, SoftwareModuleItem { name: "CODESYS", version: Some("<IP_ADDRESS>-38"), url: None, action: None, reason: None }] }, SoftwareRequestResponseSoftwareList { plugin_type: "cds", modules: [] }]), failures: [] } })))
2023-08-11T08:13:44.485580115Z  INFO MqttPublisher: send Message { topic: Topic { name: "tedge/commands/res/software/list" }, payload: "{"id":"ZpDTcMeq4_HqEQ3S5Xe4P","status":"successful","currentSoftwareList":[{"type":"ap","modules":[{"name":"thin-edge","version":"0.12.0_0.8.4"},{"name":"CODESYS","version":"<IP_ADDRESS>-38"}]},{"type":"cds","modules":[]}]}", qos: AtLeastOnce, retain: false }

2023-08-11T08:13:44.485750933Z  INFO MQTT: recv Ok(Some(Message { topic: Topic { name: "tedge/commands/res/software/list" }, payload: "{"id":"ZpDTcMeq4_HqEQ3S5Xe4P","status":"successful","currentSoftwareList":[{"type":"ap","modules":[{"name":"thin-edge","version":"0.12.0_0.8.4"},{"name":"CODESYS","version":"<IP_ADDRESS>-38"}]},{"type":"cds","modules":[]}]}", qos: AtLeastOnce, retain: false }))

To Reproduce

Expected behavior

Screenshots

Environment (please complete the following information):

OS [incl. version]
Hardware [incl. revision]
System-Architecture [e.g. result of "uname -a"]
thin-edge.io version [e.g. 0.1.0]

Additional context

Hi,
I've used the on_shutdown.sh script as reboot action and added a sync before the final reboot -r now and know the operation changes to "successful".
Therefore I assume that the latest changes to /etc/tedge/.agent/restart-current-operation are not written to disc.

I get now sometimes (maybe every other time) a "restart failed" response, but I checked the log of the agent and could only see, that the agent reports "successful".
$ cat /var/log/tedge-agent.err
2023-08-11T10:49:46.290369242Z  INFO flockfile::unix: Lockfile created "/run/lock/tedge-agent.lock"
2023-08-11T10:49:46.291770919Z  INFO tedge_agent::agent: tedge-agent starting
2023-08-11T10:49:46.292975052Z  INFO sm-agent: tedge_agent::agent: Starting tedge agent
2023-08-11T10:49:46.304583842Z  INFO Runtime: Started
2023-08-11T10:49:46.308766247Z  INFO Runtime: Running Signal-Handler-0
2023-08-11T10:49:46.31036805Z  INFO Runtime: Running HttpFileTransferServer-1
2023-08-11T10:49:46.360520695Z  INFO Runtime: Running MQTT-2
2023-08-11T10:49:46.360976323Z  INFO Runtime: Running RestartManagerActor-3
2023-08-11T10:49:46.361081657Z  INFO Runtime: Running SoftwareManagerActor-4
2023-08-11T10:49:46.361147699Z  INFO Runtime: Running TedgeOperationConverter-5
2023-08-11T10:49:46.361222491Z  INFO Runtime: Running TedgetoTeConverter-6
2023-08-11T10:49:46.364335055Z  INFO Runtime: Running HealthMonitorActor-7
2023-08-11T10:49:46.365002726Z  INFO tedge-agent: send Message { topic: Topic { name: "tedge/health/tedge-agent" }, payload: "{"pid":3128,"status":"up","time":1691750986}", qos: AtLeastOnce, retain: true }
2023-08-11T10:49:46.984963759Z  INFO plugin_sm::plugin_manager: Plugin activated: /mnt/data/tedge/sm-plugins/cds
2023-08-11T10:50:00.213581631Z  INFO plugin_sm::plugin_manager: Plugin activated: /mnt/data/tedge/sm-plugins/ap
2023-08-11T10:50:00.214045521Z  INFO plugin_sm::plugin_manager: Default plugin type: ap
2023-08-11T10:50:00.243015949Z ERROR mqtt_channel::connection: MQTT connection error: Timeout
2023-08-11T10:50:00.266983051Z  INFO tedge_agent::restart_manager::actor: Device restart successful.
2023-08-11T10:50:00.267124139Z  INFO RestartManager: send RestartOperationResponse { id: "pMB1jOsD7mnzJqSZ1b1bw", status: Successful }
2023-08-11T10:50:00.267479483Z  INFO Mqtt-Request-Converter: recv Some(RestartOperationResponse(RestartOperationResponse { id: "pMB1jOsD7mnzJqSZ1b1bw", status: Successful }))
2023-08-11T10:50:00.267607946Z  INFO MqttPublisher: send Message { topic: Topic { name: "tedge/commands/res/control/restart" }, payload: "{"id":"pMB1jOsD7mnzJqSZ1b1bw","status":"successful"}", qos: AtLeastOnce, retain: false }
2023-08-11T10:50:00.341418811Z  INFO mqtt_channel::connection: MQTT connection established
2023-08-11T10:50:00.34510122Z  INFO MQTT: recv Ok(Some(Message { topic: Topic { name: "tedge/health/tedge-agent" }, payload: "{"pid":3128,"status":"up","time":1691750986}", qos: AtLeastOnce, retain: true }))

2023-08-11T10:50:00.345502567Z  INFO MQTT: recv Ok(Some(Message { topic: Topic { name: "tedge/commands/res/control/restart" }, payload: "{"id":"pMB1jOsD7mnzJqSZ1b1bw","status":"successful"}", qos: AtLeastOnce, retain: false }))

What could be gone wrong?

According to the Log the mapper seems also to send the successful message, but c8y shows "failed" 😲.
$ cat /var/log/tedge-mapper-c8y.err
...
2023-08-11T11:05:14.291180198Z  INFO MQTT: send Message { topic: Topic { name: "tedge/commands/res/control/restart" }, payload: "{"id":"snOEGykPCFTNfJFluVeIw","status":"successful"}", qos: AtLeastOnce, retain: false }
2023-08-11T11:05:14.29216276Z  INFO CumulocityMapper: recv Some(MqttMessage(Message { topic: Topic { name: "tedge/commands/res/control/restart" }, payload: "{"id":"snOEGykPCFTNfJFluVeIw","status":"successful"}", qos: AtLeastOnce, retain: false }))
2023-08-11T11:05:14.292383741Z  INFO C8yMapper => Mqtt: send Message { topic: Topic { name: "c8y/s/us" }, payload: "503,c8y_Restart,
", qos: AtLeastOnce, retain: false }
2023-08-11T11:05:14.292764406Z  INFO MQTT: recv Ok(Some(Message { topic: Topic { name: "c8y/s/us" }, payload: "503,c8y_Restart,
", qos: AtLeastOnce, retain: false }))
...

@toewsar Can you make sure all operations are cleared first before running the new test. It is best to clear all operations which are not already set to SUCCESSFUL or FAILED (just in case if there is a really old PENDING operation somewhere which is not visible in the UI.

@toewsar Can you test this PR with your setting?
This addresses the fact you noticed that the latest changes to /etc/tedge/.agent/restart-current-operation are not written to disc. Now the agent call fsync for all the files that required to resume the operation after the reboot.
About the other comments, I suspect that is might be caused by on old operation still PENDING (this confuses Cumulocity). However, this needs to be confirmed.

This PR has been merged.
@toewsar Can you please test the latest version of thin-edge with your settings?

@didier-wenzek My test failed. The changes seem to be not efficient for my device. I cannot say why.
It seems that I need some sleep time between the operation and the actual reboot.

@didier-wenzek My test failed. The changes seem to be not efficient for my device. I cannot say why. It seems that I need some sleep time between the operation and the actual reboot.

@toewsar  Just to eliminate any source of confusion, can you confirm which commit hash you re-built from?

$ git describe
0.12.0-96-gf8aef0e7f4

It would be nice to understand a bit more about why the sync/flush is not enough to wait for the information to be written to the persistent partition...If there is a standard linux command that makes sense to convert this then we can add it, however I suspect the required command sounds very device specific (so using a custom shutdown command will be the way to go for you).

I'm not a RUST specialist and also not fimilar with async/await.
Can you confirm that the write operation is finished when calling sync?

The restart-current-operation is cleared even if the mapper is not running on startup....

I'm not a RUST specialist and also not fimilar with async/await. Can you confirm that the write operation is finished when calling sync?

I confirm that a call to file.sync_all().await? returns only after the system call to fsync returns. The await just means that another thread can make progress meantime.
However, the behavior of fsync is not guaranteed and depends on the file system.

@toewsar Would you be able to test the sync; sync; method in a custom shutdown script on your device?
For example, go through the following steps (I know you know this already, but I'm just adding it for the history):

Create a custom reboot command which just calls a script
file: /etc/tedge/system.toml
[system]
reboot = ["/usr/bin/on_shutdown.sh"]

Create the script which will be called when tedge triggers a reboot;
file: /usr/bin/on_shutdown.sh
#!/bin/sh
set -e
sync; sync;

Make sure the script is executable,
chmod a+x /usr/bin/on_shutdown.sh

Ensure you have script and the underlying commands in your sudoers file (otherwise the reboot will fail):
file: /etc/sudoers.d/tedge
tedge ALL = (ALL) NOPASSWD: /usr/bin/tedge, /etc/tedge/sm-plugins/[a-zA-Z0-9]*, /bin/sync, /sbin/init, /sbin/shutdown, /usr/bin/on_shutdown.sh

Make sure you clear all of the existing PENDING and EXECUTING commands in Cumulocity

Trigger a restart operation via the UI
The expected outcome is that the operation is successful, though I would also recommend repeating the test multiple times.

@toewsar are you happy to close this ticket then? We have already merged the improvement which explicitly calls sync before calling reboot, and from your last comment it seems to be more related to a hardware specific behaviour.


Breakpoints in dart: libraries are not hit

This came up at https://github.com/Dart-Code/Dart-Code/issues/3551.
Given the following code:
main() {
  print('test');
}

There are two possible ways in VS Code to try and set a breakpoint inside the print function:

Invoke the analysis servers Go-to-Definition on print and then add the breakpoint in the file that opens
For a Dart app, the file that opens is {dart-sdk-path}/lib/core/print.dart
For a Flutter app, the file that opens is {flutter-sdk-path}/bin/cache/pkg/sky_engine/lib/core/print.dart
Add a breakpoint on the call to print, run the app, then Step Into print and add the breakpoint in the file that opens
For both Dart and Flutter apps, the file is downloaded from the VM and has the uri dart:core/print.dart

Setting the breakpoints either of these ways does not cause the debugger to pause when next calling print. Ideally, both would, since both of them are reasonable ways for the user to get to the code and assume this would work (and both should generally match the version of code that is running in the VM as I understand it).
Here's an example showing the script URI returned from the VM:
"script": {
	"type": "@Script",
	"fixedId": true,
	"id"<EMAIL_ADDRESS>	"uri": "dart:core/print.dart", // <------------------------------ see here
	"_kind": "kernel"
},

And here's an example of a call to setBreakpointWithScriptUri with the same URI that fails to set a working breakpoint:
{
	"id": "10",
	"jsonrpc": "2.0",
	"method": "addBreakpointWithScriptUri",
	"params": {
		"isolateId": "isolates/996847484333475",
		"scriptUri": "file:///Users/danny/Dev/Dart%20SDKs/v2.13.4/lib/core/print.dart",
		"line": 9
	}
}

@bleroux found that for the Flutter case, and when you set breakpoints after stepping into the code, replacing "dart:" with "/" in the addBreakpointWithScriptUri will work for Flutter apps (I think this forces it to partially-match the URI, although I'm not certain and not sure why). It still only fixes a subset of the problem though (and it may break things if this is fixed in the VM for users that upgrade). Implementing the workaround in the SDK DAP might be more reasonable (with a test that would fail if the issue is fixed in a way that breaks the workaround), although it would still be nice to have a solution that works for the other cases (Dart CLI, and if the user Go-to-Definition'd into the SDK library).
@bkonyi

This is probably related to the debuggable bit on libraries, which unfortunately exists. It controls whether breakpoints or stepping will stop in the library, and it is off by default for dart: libraries.
https://github.com/dart-lang/sdk/blob/main/runtime/vm/service/service.md#setlibrarydebuggable

As far as I can see, we're setting that as expected:
		"libraries": [
			{
				"type": "@Library",
				"fixedId": true,
				"id": "libraries/@0150898",
				"name": "dart.core",
				"uri": "dart:core"
			},

{
	"id": "12",
	"jsonrpc": "2.0",
	"method": "setLibraryDebuggable",
	"params": {
		"isolateId": "isolates/340950901623355",
		"libraryId": "libraries/@0150898",
		"isDebuggable": true
	}
}

I think we currently send it for all libraries always, because the default changed in the past and caused issues, so now we're quite explicit about it.
Here's a full log:
full_debug_log.txt
Line 34 calls setLibraryDebuggable for dart:core
Line 28 + 29 set the breakpoints (one using the analysis servers path, and the other using the URI we get while debugging)
I'll do some testing to ensure the order of the above doesn't matter, but I'm fairly sure it works fine for non-SDK libraries this way (I didn't realise until just now we were sending them this way around!).

The weird order was because VS Code sent us the breakpoints while we were starting up. I temporarily delayed setting the breakpoints for testing, but the behaviour is the same. Here's an updated log:
Dart-Code-Log-2021-08-02 12-36-25.txt
Line 121 calls setLibraryDebuggable for dart:core (response is line 123)
Line 162+163 set the breakpoints (line 165+167 are the responses)
Line 171 resume the app (it was started paused to avoid race conditions setting breakpoints)
Line 174 the isolate exits, having never hit the breakpoint

I think there are several issues to tackle there.
The first one is that addBreakpointWithScriptUri documentation doesn't explain what is expected  for scriptUri parameter.
Digging in the code and reading informative @bkonyi comments on this flutter issue, we can find what works or not :

dart:core/print.dart : failed  (as reported by @DanTup)
org-dartlang-sdk:///sdk/lib/core/print.dart : passed  (from @bkonyi comments)
/core/print.dart : passed (found reading this)

To get those results I wrote the following sdk test :
const int LINE_A = 10;
...
var printUri = 'dart:core/print.dart';

var tests = <IsolateTest>[
  hasStoppedAtBreakpoint,
  // Dart libraries are not debuggable by default
  markDartColonLibrariesDebuggable,
  // Add breakpoint in core lib
  (Isolate isolate) async {
    var bpt = await isolate.addBreakpointByScriptUri(printUri, LINE_A);
    expect(bpt is Breakpoint, isTrue);
  },
  resumeIsolate,
  hasStoppedAtBreakpoint,
  stoppedAtLine(LINE_A),
  resumeIsolate,
];

I have fun with this and would like to contribute.
@DanTup  @rmacnak-google @bkonyi Should I create several issues so we can make progress step by step ?
If yes, first one would be on addBreakpointWithScriptUri documentation, as it will define what is expected.

If yes, first one would be on addBreakpointWithScriptUri documentation, as it will define what is expected.

I think it would definitely be good to clearly document this. Issues have come up in the past where sometimes breakpoints would only be hit if using file:/// and sometimes only if package:foo/ depending on how the files were loaded, and that led to IDEs sending the same breakpoint in multiple formats to try and get one that worked. Unfortunately that caused other complications in VS Code (because we had to try and manage mappings of 1-to-n breakpoints), but changes were made in the VM to handle either.
I think the ideal solution would allow the editor to send any of file:/// URIs or the package:/dart: URIs, because generally the editor only knows file paths when not in a debug session, and only VM URIs when stepping through code. If the VM can't map these URIs, I'm not sure how an editor could (plus, anything done in the editor needs duplicating in them all, but anything in the VM is all just in the SDK).
Eg., it would be great if all of these worked:

file:///home/danny/project_foo/lib/foo.dart
package:project_foo/foo.dart
file:///home/danny/dart-sdk/lib/core/print.dart
file:///home/danny/flutter/bin/cache/pkg/sky_engine/lib/core/print.dart (I don't really understand why this file exists since it seems duplicated in file:///home/danny/flutter/bin/cache/dart-sdk/lib/core/print.dart, but the former is where the analysis server jumps to when using go-to-definition in a Flutter app)
dart:core/print.dart

Slightly related is https://github.com/dart-lang/sdk/issues/46631 which describes a way for the editor to change between these paths through the VM Service. Although for requests like addBreakpointWithScriptUri I don't think it makes sense for the editor to ask the VM to translate them to then immediately send them back - it seems like internally addBreakpointWithScriptUri should be able to use the same mapping to just do the right thing.
(I don't know how feasible this is though, I don't know much about the internals - @rmacnak-google @bkonyi likely have more informed opinions)

As a first step, I submitted a PR to fix a bug in scripts lookup : https://dart-review.googlesource.com/c/sdk/+/213766
@bkonyi @rmacnak-google Thank you to review it.


文档拆分功能是否有使用指导文档，貌似只能提取单页？

請問能詳細描述這個問題一下嗎？

I closed this issue because there's no information added to make the question clear. We can re-open this issue if necessary.


omxplayer patch fail on master branch

Description

Steps to reproduce the issue:

bitbake omxplayer

Describe the results you received:
omxplayer-git-r4 do_patch: Command Error: 'quilt --quiltrc /home/studio/build/YOCTO_MASTER/poky-thud/build/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/omxplayer/git-r4/recipe-sysroot-native/etc/quiltrc push' exited with 0  Output:
Applying patch 0001-Remove-Makefile.include-which-includes-hardcoded.patch
patching file Makefile
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- rejects in file Makefile
patching file Makefile.ffmpeg
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- rejects in file Makefile.ffmpeg
The next patch would delete the file Makefile.include,
which does not exist!  Applying it anyway.
patching file Makefile.include
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- rejects in file Makefile.include
Patch 0001-Remove-Makefile.include-which-includes-hardcoded.patch does not apply (enforce with -f)
ERROR: omxplayer-git-r4 do_patch: Function failed: patch_do_patch
ERROR: Logfile of failure stored in: /home/studio/build/YOCTO_MASTER/poky-thud/build/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/omxplayer/git-r4/temp/log.do_patch.17082
ERROR: Task (/home/studio/build/YOCTO_MASTER/poky-thud/meta-raspberrypi/recipes-multimedia/omxplayer/omxplayer_git.bb:do_patch) failed with exit code '1'
Describe the results you expected:
Additional information you deem important (e.g. issue happens only occasionally):
Additional details (revisions used, host distro, etc.):

In latest omxplayer repository file Makefile.include doesn't exist anymore. Does anybody have same problem?

This sounds strange. @kraj Could this be introduced by the last update? I haven't tried to reproduce.

havent seen this here. I will take a look

i just tried to build on clear system with minimal layers and still same problem, on SUMO its working ok.
bitbake omxplayer
WARNING: Host distribution "ubuntu-18.04" has not been validated with this version of the build system; you may possibly experience unexpected failures. It is recommended that you use a tested distribution.
Parsing recipes: 100% |################################################################################| Time: 0:00:18
Parsing of 1472 .bb files complete (0 cached, 1472 parsed). 2106 targets, 98 skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies
Build Configuration:
BB_VERSION           = "1.40.0"
BUILD_SYS            = "x86_64-linux"
NATIVELSBSTRING      = "universal"
TARGET_SYS           = "arm-poky-linux-gnueabi"
MACHINE              = "raspberrypi0-wifi"
DISTRO               = "poky"
DISTRO_VERSION       = "2.6"
TUNE_FEATURES        = "arm armv6 vfp arm1176jzfs callconvention-hard"
TARGET_FPU           = "hard"
meta
meta-poky
meta-yocto-bsp       = "master:411184bfaa6269bf2926bb2a576c0922958cbbb3"
meta-raspberrypi     = "master:0f14d185d387f59ff9f00365ff314cf51e46db58"
meta-oe              = "master:f1511d254632a34c1deb51f4bf8b8c21e7423f51"
Initialising tasks: 100% |#############################################################################| Time: 0:00:00
Sstate summary: Wanted 425 Found 0 Missed 425 Current 12 (0% match, 2% complete)
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: omxplayer-git-r4 do_patch: Command Error: 'quilt --quiltrc /home/studio/build/testing/rpi-build/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/omxplayer/git-r4/recipe-sysroot-native/etc/quiltrc push' exited with 0  Output:
Applying patch 0001-Remove-Makefile.include-which-includes-hardcoded.patch
patching file Makefile
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- rejects in file Makefile
patching file Makefile.ffmpeg
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- rejects in file Makefile.ffmpeg
The next patch would delete the file Makefile.include,
which does not exist!  Applying it anyway.
patching file Makefile.include
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- rejects in file Makefile.include
Patch 0001-Remove-Makefile.include-which-includes-hardcoded.patch does not apply (enforce with -f)
ERROR: omxplayer-git-r4 do_patch: Function failed: patch_do_patch
ERROR: Logfile of failure stored in: /home/studio/build/testing/rpi-build/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/omxplayer/git-r4/temp/log.do_patch.12819
ERROR: Task (/home/studio/build/testing/poky/meta-raspberrypi/recipes-multimedia/omxplayer/omxplayer_git.bb:do_patch) failed with exit code '1'
NOTE: Tasks Summary: Attempted 557 tasks of which 546 didn't need to be rerun and 1 failed.
Summary: 1 task failed:
/home/studio/build/testing/poky/meta-raspberrypi/recipes-multimedia/omxplayer/omxplayer_git.bb:do_patch
Summary: There was 1 WARNING message shown.
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.

This should be now fixed. Please reopen if needed.


No Sound from USB Soundcard

hey,
I have a shairpoint script running as well. Output is working with that. with spotify connect running the output is no longer working.
Any Ideas?
Setup:

Pi Zero
Rasbian Lite
External USB Sound Card C-Media USB Headphone Set

alpay -l output:
**** List of PLAYBACK Hardware Devices ****
card 0: ALSA [bcm2835 ALSA], device 0: bcm2835 ALSA [bcm2835 ALSA]
Subdevices: 7/8
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
Subdevice #2: subdevice #2
Subdevice #3: subdevice #3
Subdevice #4: subdevice #4
Subdevice #5: subdevice #5
Subdevice #6: subdevice #6
Subdevice #7: subdevice #7
card 0: ALSA [bcm2835 ALSA], device 1: bcm2835 ALSA [bcm2835 IEC958/HDMI]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: Set [C-Media USB Headphone Set], device 0: USB Audio [USB Audio]
Subdevices: 0/1
Subdevice #0: subdevice #0

I've got not identical but similar issue with my USB DAC, it partially works but there was terrible noise sound. I provide small change when i run spotifyconnect i use parameter --device plughw:1 instead of --device hw:0 and it works like a charm. Try it maybe it helps.

thanks!
it is working that way.


DVL message discussion

This is the place for discussion of DVL-specific message design choices.

Closing in favor of people making specific issues for more specific requested changes on the message.


How to use SocketIOClient.get() and SocketIOClient.set() ?

The doc from socket.io says as below:
The old io.set() and io.get() methods are deprecated and only supported for backwards compatibility. Here is a translation of an old authorization example into middleware-style.

The old io.set() and io.get() methods are deprecated and only supported for backwards compatibility

Now Socket.IO uses other nodejs libs for this. Prior 1.0 version nodejs socketio project was more standalone. Now it relies on some libs exposes by nodejs. After 1.0 version this feature was deprecated because other nodejs libs offers such function. As for netty-socketio this feature will not be depreacted, because it's a fully standalone project.

@mrniko
If client use 'socket.property=value' instead old io.set(), does any way to get the property by netty-socketio?


Update the build system to have a hook to check for validation errors in the MRTK build

Recently we hit an issue in the MRTK where we had duplicate GUIDs checked in for a few different assets:
#5431
The root issue here was that the meta files were copy pasted, instead of being regenerated at the new location. There was a warning in the console but it was ignored, and since Unity will non-deterministically choose one of them (i.e. either of the duplicate GUIDs could be right) - you end up with cases where you will get one or the other of the assets (and hopefully Unity choose correctly for you!)
I looked into doing a custom logger (i.e. catching LogWarning) but found that it doesn't run soon enough (i.e. warnings will show up, this code will get compiled) so this had to resort to editor-log parsing.
In theory this could be extended in the future to other issues that we hit that show up in the console as well.

Note for reviewers, the .meta file is for testing, I will revert that once I have verified that this is working as intended on mrtk_pr

/azp run

It works!
https://dev.azure.com/aipmr/MixedRealityToolkit-Unity-CI/_build/results?buildId=3945

/azp run


Why flow is not supported in the project?

I am a user of both flow and material-ui, loving both of them, but my current problem is that I can't use both at the full potential, because currently this project is not implemented.
I know that due to those things we have flow-typed, nevertheless currently the version of flow-typed is very outdated and does not fully support the current mui components.
I am thinking of implementing the remaining flow types so that other users may be able to use it. But I was asking myself if it would be the best to actually implemented here or in flow-typed.

The main reason is the community. Assuming we can trust the traffic on the documentation, they are at least two orders of magnitude in the popularity of TypeScript vs Flow: https://www.similarweb.com/en/website/flow.org/?competitors=typescriptlang.org. You will find the same two orders of magnitude looking at the downloads on npm: https://npm-stat.com/charts.html?package=typescript&package=flow-bin.


Microsoft Editor Integration.

Integrate Microsoft Editor to automatically check for spelling and error and fix them. There are some extensions for VS Code. But they aren't that good.

Duplicate of #122084 and few other.

Duplicate of #122084 and few other.

Those guy is asking for an extension. But I guess a built-in feature will be better.

Most of functionality is implemented as built-in extensions.
However linked issue states reason why it's a problem to implement it either way.

Most of functionality is implemented as built-in extensions.
However linked issue states reason why it's a problem to implement it either way.

Hmm. I don't understand the issue. Can you explain it to me?

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.
Happy Coding!


create a new page for travel method selection

Please view the base design for the travel method selection button. If you want to test this all you have to do is replace question 4 with this travel method component. It will work as it should be. Save button need to be change  . Main component that support this save button need editing.

trello link for this task : https://trello.com/c/z50v3GrA/297-dev-travel-method-selection-page


Further development

Update README
Add FluentValidation for configuration validation
Add CommandPostExecution handling
Remove string to enum conversion from commands and introduce TypeReaders instead
Postfix missing async methods with Async
Add BotAdmin permission requirement for certain commands
Restructure appsettings configuration

Bump Discord.NET version to 3.9.0

LGTM


Add arg key to inspect specific namespace in k8s cluster

In some cases, inspection of whole cluster might be forbidden and it is possible only to some namespaces. Those changes will help to make it happen.

Thanks!
https://github.com/flant/k8s-image-availability-exporter/releases/tag/v0.1.15


The difference between "Fail" and "Unfinished" in test log

Context
Hello Caliper team, after I ran a test, I discovered that in test log, there are two fields: Fail, Unfinished.

And in the generated report, only Fail is presented, while Unfinished is not presented.

I don't understand the difference between them. Could you please tell me? Thanks in advance.

Unfinished: the transaction is submitted and going through the life cycle. We don't know the result yet
Fail: we got the notification that the transaction failed.
Succ: we got the notification that the transaction was successful.
Submitted = succ + fail + unfinished

So can I understand it like this:
unfinished will becomes one of these:
1.fail or timeout
2.success


Add the "Characteristics of Intended Reader" section to Examples

As discussed in issue #228, GlassBR, SSP, and GamePhysics should add the "Characteristics of Intended Reader" section. As @smiths mentioned, we are to follow Section 2.3 of the SWHS example (https://github.com/smiths/swhs/blob/master/SRS/PCM_SRS.pdf).

[ ] @hmadej
[ ] @niazim3
[ ] @njericha

Thank you for coordinating th is Maryyam.

Where are we getting the information to fill in the first 4 parameters for the currently automatically generated section defined in OrganizationOfSRS.hs? @smiths
`--Characteristics of Intended Reader section
charIntRdrF :: Sentence -> Sentence -> Sentence -> Sentence -> Sentence -> Contents -> Section
charIntRdrF know c1 und c2 progName r =
SRS.charOfIR (intReaderIntro know c1 und c2 progName r) []
--paragraph called by charIntRdrF
intReaderIntro :: Sentence -> Sentence -> Sentence -> Sentence -> Sentence -> Contents -> [Contents]
intReaderIntro know c1 und c2 progName r = [Paragraph $ foldlSent [S "Reviewers of this", (phrase documentation),
S "should have a strong knowledge in" +:+. know, S "A", c1,
S "course on this topic is recommended. The reviewers should also have an understanding of",
und sC S "as typically covered in", c2 +:+. S "courses", S "The", (plural user), S "of",
progName, S "can have a lower level of expertise, as explained in", (makeRef r)]]`
SWHS would call this function using the following code:
s2_3 = charIntRdrF (plural $ CT.heat ^. term)   (S "third or fourth year Mechanical Engineering")   (S "differential" +:+ (plural $ equation ^. term))   (S "first and second year Calculus")   (s3_2)

I'm sorry @niazim3 ; I do not understand your question.  Maybe it is more appropriately directed to @szymczdm ?

Sorry @smiths, I meant to ask about where the content that should be added can be found?
Since user characteristics may refer to a different group of people than the intended readers, we're unsure of what Sentences we should input as parameters (i.e. what should they have "strong knowledge" of, which courses must they have taken, what should they have previous understanding of (and which course that's typically taught in), etc. ).

Okay, now I understand.  Please go ahead and make a best guess for the knowledge that users should have.  You can follow the examples where this information is filled in.  It doesn't matter if the filled in information is "perfect."  We just need an idea.  We can always iterate on the details in the future.  The knowledge is usually going to centre around mathematics and physics.  If you can characterize the knowledge in terms of a level of education, that is ideal.  For instance, first year calculus is a fairly precise statement.  The content of a first year calculus course is fairly standardized across institutions.
Let me know (via an issue) once you have a section filled in for review.  I'd be happy to look it over.

I think: "Reviewers of this documentation should have knowledge of _____." "The reader should also have an understanding of _____", "The users of ____" would probably make a good frame for this section.

I agree @hmadej, I'll update the current charIntRdrF to be more generalized.

See 9932829 for the most recent version of charIntRdrF.

Assuming this is done @hmadej


Provide a timeout option for Flush()

Provide a timeout option for Flush()
We'd like the ability to specify a timeout for Flush() which would cancel the operation and return if the timeout was exceeded.  Our scenario is a short running .NET Core application with telemetry being uploaded at the end of the app by calling Flush() before exiting.  In some cases, network latency is causing the app to hang before exiting.  We'd rather lose the telemetry data than delay the app.
Issue Details:
When running our app, we're seeing reasonable return times for the Flush() command in almost all cases, with the network connected and without.  The failing case for us is when we're running our app in a Docker container and the host's network is disconnected.  In this case, the app acts as if it's connected but cannot reach the network resource, resulting in a 40 second delay while the network call times out.

Thanks Dan! We'll collect feedback on how typical your case is to see if we need to make it part of the API. As a workaround would doing something like this help:
            Thread thread = new Thread(() =>
            {
              telemetryClient.Flush();
            });
            thread.Start();
            if (!thread.Join(1000*5)) // wait 5 seconds
            {
                thread.Abort();
            }

I'd give a +1 here. It's not a must-have-feature, but it is something that a) I expect any API to IO operations to provide and b) I have wished in the past, but then it was not important enough to put effort into (especially testing).

+1 for the feature since the .NET Core telemetry scenario is on a critical CLI tool where time lags are noticeable.


Python GAPIC: pubsub v1

This pull request was generated by artman. Please review it thoroughly before merging.

@ethanbao http://i.imgur.com/7drHiqr.gif

This is great!

Also, 0.15.4 is pushed to PyPI. (Manually, sadly. Soon...)


Remove all deprecation logic. Lol

This has all moved to rails-sunset and faraday-sunset, so nothing left here.
Good news, we don't need Rails for aaaanything.

Coverage increased (+3.2%) to 98.932% when pulling 104156c145650f913763f9d4b5482f55d3228e60 on feature/remove-deprecation into 09fcf3b0e6bb50b5c5e4856fe66e24e17bc49d46 on master.


Single out component installs with better role dependencies

Description
Using tags, you can now select which component to install. The common and kerberos roles were moved into role dependencies
Fixes # (issue)
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Ran the install, made sure the conditional around kerberos worked still. Also ran single components at a time with --tag=<component_name>
Checklist:

[ ] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] Any dependent changes have been merged and published in downstream modules

I moved the common role into each component's dependencies (which means those tasks will get run before the components tasks)
And kerberos role inside a task file with all kerberos related tasks, so all can be skipped as necessary. this speeds up the playbook (slightly).


Curators can upload a local dataset to a private Collection

All Curators MUST be able to use the Curator API to add new Datasets to the Collection via uploads of local files to S3
session policy passed inline when creating the token.
{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Sid": "testWriteOnlyPolicy2",
      "Effect": "Allow",
      "Action": [
        "s3:PutObject"
      ],
      "Resource": [
        "arn:aws:s3:::<fill_in_bucket>/<fill_in_collection_id/*"
      ]
    }
  ]
}

Serve Role to get generate credentials
{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": "sts:AssumeRole",
            "Resource": "arn:aws:iam::401986845158:role/<name_of_role_that_we_call_with_assume_role>"
        }
    ]
}

and finally the role that we call with the 'assume role' call from the server (to get the temp tokens), simply needs to have write access to the s3 bucket
So there's

the role of the server
the role that the server calls with 'assume role' to get tokens
the inline policy that the server passes with the 'assume role' call to restrict the write access down to one specific collection_id path

https://feeney.mba/refreshable-aws-boto-credentials.html

We ended up only being able to create a token with a max time of 1 hour. This does not work for our curator who often need to upload much larger files that cannot complete in that time. As a stop gap, we are providing a code snippet that will automatically refresh the user's AWS credentials. We are also in the process of implementing a more permanent solution that will allow the user to generate AWS crednetials that can live up to 12 hours. In the future the user will also be able to automatically refresh those crednetials all using AWS tools.


Remove sc-migration reconciler

followup to https://github.com/kyma-incubator/reconciler/pull/1153
requirement for https://github.com/kyma-project/control-plane/pull/1959

/retest


data set

Is the data set in Github consistent with the data set in the paper？

Yes, the data set in GitHub is consistent with the paper.
Thanks for your interest.

It appears that API is not used as the slicing criterion when performing program slicing.At the same time, we found that only the C codes were sliced in the SARD dataset.The data set processed in the project is also quite different from that in the paper. For example, the number with label 0 in the NVD data set is much larger than label 1  .Could you elaborate further on these questions?

The dataset has been uploaded for only the C language. Sorry for the confusion with the above answer.
In the case of a slicing criterion, we applied some heuristics points such as arithmetic, array, etc., in addition to the vulnerable API list.
The dataset has more benign data (label 0) than vulnerable data (label 1), so that we applied the oversampling technique such as SMOTEENN.
On the README page, we will specify the differences from the dataset of the paper. Thank you for your valuable advice.


[Feature Request]: Support HuggingFace self-hosted LLM endpoint

Feature Description
Some users may want to deploy their own LLM endpoint based on open source. Huggingface's infra for doing so may not be a bad choice. We can integrate with it. https://github.com/huggingface/text-generation-inference
Not sure if it can handle embedding inference too. (Guess not, but see: https://github.com/huggingface/text-generation-inference/issues/199). Hopefully it can extract good util from the device. For instance the right amount of concurrent embeddings to perform given the GPU memory.

We do technically support it since LangChain also supports it.
Are there any benefits to having a native integration for this, other than one less langchain dependency?


fix: wrong pipe diameter

Checks
Please check if the PR fulfills these requirements

[x] The commit message follows our guidelines

Changes
Fixes the wrong pipe value for poulakis.inp net.
Current Behavior
The current pipe diameter seems wrong.

https://www.sciencedirect.com/science/article/pii/S0266892003000456
Questions

Is it written somewhere that P-01 is 100 meters? For my model I assumed 1000 meters based on the other pipes, so I am simply curious.
The roughness values in INP files are given in meters, but Poulakis gave them as 0.26 mm which would equal to 0.00026 m. Am I misunderstanding the INP File format or is this also an error? (This would increase the pressure on node J-31 from 7.98m to 21.79m

Well, tbh I got this model years ago from @steffelbauer and now took it for testing without looking at it in detail. Maybe David can shed some light here.
Since this mainly affects the tests, I'm personally fine with any change as long as the corresponding tests are updated as well.


Add settings to talk to Alertmanager

What this PR does / why we need it:
This PR adds

Prometheus settings to talk to Alertmanager (it got missed when moving alerting_rules.yml to Configmap)
an alerting rule to alert when error rate gets higher

Which issue(s) this PR fixes:
Fixes #
Does this PR introduce a user-facing change?:

NONE

/lgtm


Certificate issue for code.cloudfoundry.org/clock

Downloading go module 'code.cloudfoundry.org/clock' directly failed due to certificate issue
Summary
Directly downloading the go module code.cloudfoundry.org/clock failed due to a certificate issue. This probably was not noticed because go usually downloads the module from the official golang proxy (https://proxy.golang.org/).
Steps to Reproduce
$ export GOPROXY=direct
$ go mod download -x -json code.cloudfoundry.org/clock
# get https://code.cloudfoundry.org/clock?go-get=1
# get https://code.cloudfoundry.org/clock?go-get=1: Get "[https://code.cloudfoundry.org/clock?go-get=1":](https://code.cloudfoundry.org/clock?go-get=1%22:) x509: certificate is valid for *.de.a9sapp.eu, de.a9sapp.eu, not code.cloudfoundry.org
{
        "Path": "code.cloudfoundry.org/clock",
        "Version": "v1.0.0",
        "Error": "unrecognized import path \"code.cloudfoundry.org/clock\": https fetch: Get \"[https://code.cloudfoundry.org/clock?go-get=1\":](https://code.cloudfoundry.org/clock?go-get=1\%22:) x509: certificate is valid for *.de.a9sapp.eu, de.a9sapp.eu, not code.cloudfoundry.org"
}

Diego repo
code.cloudfoundry.org/clock which should resolve to https://github.com/cloudfoundry/clock
Environment Details
go 1.17

邮件已收到，我会尽快阅读并回复，谢谢

There was an issue with certificate. I believe this issue has been resolved.


use UUIDS while configuring rgw as objectstore

This patch ensures to use UUIDs instead of names of user, service and project while configuring rgw as ceph object store.
As a pull request owner and reviewers, I checked that:

[x] Appropriate testing is done and actually running
[x] Appropriate documentation exists and/or is up-to-date:

[x] README in the role
[x] Content of the docs/source is reflecting the changes

Jira: https://issues.redhat.com/browse/OSPRH-7408
Jira: https://issues.redhat.com/browse/OSPRH-7245

Certificates to stat will be installed before ceph playbook is run provided we have https://github.com/openstack-k8s-operators/architecture/pull/286

Certificates to stat will be installed before ceph playbook is run provided we have openstack-k8s-operators/architecture#286

Even if PR286 above is not sufficient to provide the certificates I still agree with the plan to have this PR add code which choses HTTP or HTTPS for the URI scheme based on the result of a stat of those certificate files. This can merge and we can ensure the certificates are in place another way.

We should be able to use https://github.com/openstack-k8s-operators/ci-framework/pull/1865 to create the certificate. Next step is to test both of these PRs together.

Good news:

I ran a full deployment of ci-framework with -e cifmw_deploy_architecture=true with this patch (+ 1865) and it was green.
I saw the RGW endpoint was configured with HTTPS and the RGW spec had the certificates embedded

Bad news:

The sanity tempest passed but not the tempest object storage tests.

Next steps:

Modify this patch (cifmw_cephadm_certificate: "" and cifmw_cephadm_key: "") so that it doesn't configure HTTPS by default so we can safely merge it and start using a keystone configuration with UUIDs
I will follow up in 1865 to get the tempest object tests passing and then I'll change the cert and key defaults in that patch.

/approve


MB-9925 update appctx linter to match desired use

Description
Our first pass at the linter only set it up to look at struct types, but it was due to a misunderstanding on my part. This PR updates the linter to also look at func params to make sure those also don't use *pop.Connection unless it's one of the allowed packages (or the one exception in handlers.handlerContext).
This PR also expands the allowed packages since it's more needed now that we're also looking at functions. I've added several packages to the testdata dir to ensure the package allowlist is working.
Also fixed a small thing in both linters where we were declaring a var inspector but already had an import with the same name, hence the edit to pkg/ato-linter/ato.go
Reviewer Notes
I tried a decent amount to get this to cover subpackages of the allowed ones, but really couldn't figure it out. Thread in Truss slack. At this point I'm just cleaning up the subpackages that are getting errors because that's going faster than my progress in figuring out how to skip subpacakges.
Setup
To run the tests for the linter, run:
go test -v ./pkg/appcontext-linter/...

If you'd like to run the linter itself, run:
go run ./cmd/appcontext-linter/main.go -- ./...

Though you'll still see code that is being flagged, like this:

As I mentioned in an earlier section, I'm working on a separate branch to fix the remaining issues.
Code Review Verification Steps

[ ] Request review from a member of a different team.
[ ] Have the Jira acceptance criteria been met for this change?

References

Jira story for this change

Messages

:book:
:link: MB-9925

  Generated by :no_entry_sign: dangerJS against c7cf09cdb068cfdc16722880df1a94bf9c6d3bc6


Implemented strict boolean comparison

Implemented strict boolean comparison to files:
src/AppBundle/Controller/ArticleController.php
src/AppBundle/Controller/CategoryController.php

With booleans, this should to lower bug risks and improve performance.
Thank you.

Thank you for this. I agree with you it's a best practice ! :+1:

You're welcome, happy to assist. :+1:

Smart, nice help :+1:


[BUG] CPU spikes at consisten intervals

The bug
I am monitoring UpSnap resource usage. I've noticed that, despite it not being in use, and Lazy Ping enabled, that every, approximately 15 minutes, the CPU usage spikes a few percent.  I only have 2 hosts registered (if that maker a difference)
Here is just the last 3 hours alone

I'm not sure this is necessarily the fault of UpSnap, but perhaps an issue with the Go configuration / web server being used, as I've noticed a very similar issue with Homarr, and to a lesser extent Gotify.
The OS that UpSnap is running on
Unraid
Version of UpSnap
4.2.12
Your docker-compose.yml content
As noted, I'm using Unraid, and haven't gotten around to using Docker Compose for this app, instead utilising the built in Unraid CA app template. I've used Composerize, which I know is not perfect here, but should be sufficient for you.

name: <your project name>
services:
    upsnap:
        container_name: UpSnap
        network_mode: host
        environment:
            - TZ=Europe/London
            - HOST_OS=Unraid
            - HOST_HOSTNAME=Orilla
            - HOST_CONTAINERNAME=UpSnap
            - TZ'='Europe/London
        labels:
            - net.unraid.docker.managed=dockerman
            - net.unraid.docker.webui='http://[IP]:[PORT:8090]'
            - net.unraid.docker.icon='https://raw.githubusercontent.com/seriousm4x/unraid-community-apps/master/icons/upsnap.png'
        volumes:
            - /mnt/user/appdata/upsnap/':'/app/pb_data/':'rw
        image: "'ghcr.io/seriousm4x/upsnap:4'"
        command: --http <IP_ADDRESS>:8090

Reproduction steps
Just run UpSnap.

Additional information
No response

Spikes are below 2%, i wouldn't call that concerning. That might very well be go's garbage collector running every couple minutes.
This is the output of the go pprof running for 15 mins:
(pprof) top
Showing nodes accounting for 280ms, 52.83% of 530ms total
Showing top 10 nodes out of 243
      flat  flat%   sum%        cum   cum%
      60ms 11.32% 11.32%       60ms 11.32%  runtime.cgocall
      50ms  9.43% 20.75%       50ms  9.43%  internal/runtime/syscall.Syscall6
      30ms  5.66% 26.42%       30ms  5.66%  runtime.(*gcBits).bitp
      30ms  5.66% 32.08%       30ms  5.66%  runtime.(*mspan).writeHeapBitsSmall
      30ms  5.66% 37.74%       30ms  5.66%  runtime.futex
      20ms  3.77% 41.51%       30ms  5.66%  runtime.adjustframe
      20ms  3.77% 45.28%       90ms 16.98%  runtime.mallocgc
      20ms  3.77% 49.06%       30ms  5.66%  runtime.step
      10ms  1.89% 50.94%       10ms  1.89%  bytes.Index
      10ms  1.89% 52.83%       90ms 16.98%  encoding/json.(*decodeState).object

runtime.mallocgc is the garbage collector which is 17% of the cpu usage
encoding/json.(*decodeState).object is just encoding json objects from the database also at 17%. But this happens more frequently rather than every couple minutes.
runtime.cgocall is probably sqlite/database related with 11.3%

I honestly don't know if there is anything that I can do about this.

Sure, I agree, not something to be concerned about. Just wondered if there was a setting somewhere (in Go) that could be altered to make the behaviour less spiky.
Thanks for investigating.


Update index.md

👷 Deploy Preview for eesg processing.

Name
Link

🔨 Latest commit
5767582cbee5d6a549017dd11280cf79fb4268ce

🔍 Latest deploy log
https://app.netlify.com/sites/eesg/deploys/627aa92a907008000876fa90

closing since duplicate


[Request] Collectable rotation improvment.

Hey,
in AutoGather.Actions.cs, Scour is hardcoded between 800 and 1000 collectability. Can we change that, to use Meticulous when 1000>Collectability >=850?
Bonus points if you can change 850 for (1000-Meticulous increase)  (in case it's not doing 150).
If I knew C# a bit better i would propose change myself, but I'm kinda scared it would break sth somewhere else.

It seems to be no longer an issue. Meticulous has priority if it hits the target collectability score.


Consolidate provider code (project layout refactor)

There's currently provider.go, provider/, mvt/provider/.
These should be consolidated.

We're talking about removing the mvt.Provider interface and creating a FeatureProvider interface. Pushing the responsibility of encoding MVT layers onto the provider is an old decision we want to go away. Providers should only be responsible for returning geometries and their associated tags.

What are you thinking for communicating the relationship of layers to features in a FeatureProvider?

Quick design we're playing with. Still settling on the names but this is the main idea:
type tegola.Feature{
  geom geom.Geometry
  tags map[string]interface{}
}

type FeatureProvider interface {
  FeaturesByBounds(ctx context.Context, layerName string, bounds Bounds) []tegola.Feature
}

I guess I'm highjacking this issue and turing it into a quick discussion about the Feature Provider. I want to make sure we have a good design before we start work on this.
Two Points:

Should Tegola.Feature have an SRID field? Or should each feature return have a way to get the SRID? This is needed as I think the responsibility for converting to a desired srid should fall at the layer level. The other thing related to to this that I comes up is to have an field in the FeaturesByBounds that acts like a hint, for the srid.

Bounds here is not quite the same as a bounding box. We need the X,Y,Z values and the bounding box. Or At least the SRID that the bounding box being provided is in. Currently, because the providers are handling the mvt layer, they calculate the bound box from the X,Y,Z and a hard coded resolution conversion for the Z. However, there are some problems with this and so we need to rethink this a bit.

An additional point is that the feature providers should know what zoom they're dealing with as we have a !ZOOM! token to support.

@gdey, are there any examples of features within a layer being encoded with different srid's?  I haven't seen it in gpkg's but the srid of a feature's geometry is stored independently of the layer's claimed srid so the possibility is there at least for this provider.

I have not seen it. The main reason is that the SRID needs to be provided, currently we are returning at slice of features. The Alternative is to return an SRID a long with the slice.:
type FeatureProvider interface {
  FeaturesByBounds(ctx context.Context, layerName string, bounds Bounds) (features []tegola.Feature,srid int)
}

After thinking this over a bit more, I'm going to propose we name the method TileFeatures since the tile will come with the Z, X and Y values as well as helper methods BoundingBox and the upcoming BufferedBoundingBox which the provider should be using to address the issue described in #107 .
Updated proposed interface:
type FeatureProvider interface {
  TileFeatures(ctx context.Context, layerName string, tile tegola.Tile) ([]tegola.Feature, error)
}

Regarding the SRID, features from a query should all have the same SRID otherwise they would not match the BoundingBox query. Additionally, I believe @gdey is proposing that the geom.Geometry interface have an SRID() method so each feature would know it's own SRID. So it's technically possible for a slice of features to have different SRIDs, but highly unlikely.

POC at https://github.com/terranodo/tegola/tree/issue-182_new_provider_interface
Managed to implement FeatureProvider interface with minor changes to each of:

MVTLayer->TileFeatures
layerFromQuery->featuresFromQuery
NewProvider->NewFeatureProvider

and types/interfaces in provider/featureProvider.go
Not sure exactly how you guys would want to access NewFeatureProvider to try things out, since it returns a different type (FeatureProvider instead of mvt.Provider) I can't just drop it in for provider.Register()


etcd-backup-operator: add backup types and its auto generated files

[skip ci]

@hongchaodeng made the pr only contains backup types and its auto-gen files

close in favor https://github.com/coreos/etcd-operator/pull/1451


compile fails

Generated bench/data/block413567.raw.h
CXX      bench/bench_bench_exosis-checkblock.o
CXX      bench/bench_bench_exosis-checkqueue.o
CXX      bench/bench_bench_exosis-Examples.o
CXX      bench/bench_bench_exosis-rollingbloom.o
CXX      bench/bench_bench_exosis-crypto_hash.o
CXX      bench/bench_bench_exosis-ccoins_caching.o
CXX      bench/bench_bench_exosis-mempool_eviction.o
CXX      bench/bench_bench_exosis-verify_script.o
CXX      bench/bench_bench_exosis-base58.o
CXX      bench/bench_bench_exosis-lockedpool.o
CXX      bench/bench_bench_exosis-perf.o
CXX      bench/bench_bench_exosis-prevector_destructor.o
CXX      bench/bench_bench_exosis-coin_selection.o
CXXLD    bench/bench_exosis
CXX      qt/qt_exosis_qt-bitcoin.o
In file included from ./qt/paymentserver.h:35:0,
from qt/bitcoin.cpp:27:
./qt/paymentrequestplus.h:10:10: fatal error: qt/paymentrequest.pb.h: No such file or directory
#include "qt/paymentrequest.pb.h"
^~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
./configure --disable-tests --with-incompatible-bdb
all depends are met
ubuntu 8.04

Hi
qt/paymentrequest.pb.h is generated by protobuf at compile time. Please check your dependencies again
Are you using the depends system to build?

Hi,
I am aware that libprotobuf is used for qt, have compiled a number of qt wallets on this system and have not had this problem.
I tried purging the packages and reinstalling
sudo apt purge libprotbuf-dev protobuf-compiler && sudo apt install libprotbuf-dev protobuf-compiler
dpkg -L protobuf
output:
libprotobuf-dev_3.0.0-9.1ubuntu1_amd64.deb
protobuf-compiler_3.0.0-9.1ubuntu1_amd64.deb
pkg-config --list-all | grep protobuf
output:
protobuf-lite                  Protocol Buffers - Google's Data Interchange Format
protobuf                       Protocol Buffers - Google's Data Interchange Format
export PKG_CONFIG_LIBDIR=/usr/lib/pkgconfig
./autogen.sh && ./configure --disable-tests --with-incompatible-bdb && make
not using depends as not trying to build cross platform
it builds all depends for the wallet from sources and packages them in the main binary?
any pointers to what i'm missing would be appreciated


fix(NotificationPanel): option to remove dnd

Contributes to #2975
Option to remove 'Do not Disturb' label and toggle from the notification panel by removing onDoNotDisturbChange.
What did you change?
Checking if there is onDoNotDisturbChange func available or not to render 'Do not Disturb'
How did you test and verify your work?

Storybook
Comment out onDoNotDisturbChange: action('Toggled to do not disturb'), from NotificationsPanel.stories.js

Can we mark the proptype as optional and ensure storybook is capable of displaying this state.

Introduced an optional prop showDoNotDisturb

Hope this works.

Sorry @Ratheeshrajan I think the preferred solution is to do as you did initially and comment the propTypes as follows and not add the additional property.
  /**
   * Optional: function that returns the current selected value of the disable notification toggle
   */
  onDoNotDisturbChange: PropTypes.func,

You could also update the propTypes for the comments for any related properties doNotDisturbLabel and doNotDisturbDefaultToggled to state if/when they are required.

@lee-chase reverted back to the initial solution.


ARTEMIS-3599 Removing finalization calls

unfortunately my CI failed with lots of unopened files.
it's probably just a test issue. but we will need to fix it before we can merge these.

The 500 failures you saw on your first run look like they would be unrelated to this. That looked to be the same situation I saw once before, essentially a LibaioContext instance was not closed and caused all following test classes [that subclass ActiveMQTestBase] that verify a count during cleanup to be marked as failed after 30 seconds wait. https://issues.apache.org/jira/browse/ARTEMIS-3435 has some more details, I used it to make changes to have it fail the overall run several hours faster if it happened again, and give some pointers to help give an idea where it went pop, which might possibly allow isolating why it happened.
It failed again that way yesterday for the first time since that change, first in a run of mine, and then also in yours on the next run. In my case it appears it happened during ReplicatedPagedFailoverTest, whereas in yours it either happened in ClusteredGroupingTest or in another before that started (need to check the output to see).
Your second run did still have a few failures though in CloseConnectionOnGCTest which I expect are very much related to this change given the name of the test, which probably just needs deleting.

I removed the test that's invalid now.


SW-4731 Create missing permanent clusters

PlantingSiteStore.ensurePermanentClustersExist() will, as its name suggests,
ensure that the required number of permanent clusters exist in each of a site's
planting zones, creating new monitoring plots or adding existing temporary plots
to clusters as needed.
For existing planting sites, this is a no-op because a full set of permanent
clusters is created at shapefile import time and this function thus has no work
to do, but future updates will get rid of the import-time plot creation and will
require this logic to be in place.

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

Current dependencies on/for this PR:

main

PR #1642

PR #1644

PR #1645   👈

This stack of pull requests is managed by Graphite.

Merge activity

Jan 26, 1:17 PM: @sgrimm started a stack merge that includes this pull request via Graphite.


CompareExchangeHashes.ps1 - baseline_15.0.516.30.zip not found

Hi,
can you please provide the baseline for 15.0.516.30?
Thanks!

I see this is being tracked under #313


Update to use with AGP 7.2.0 with backwards compatibility

Tested with
Gradle: 6.8, 7.3.3, 7.4.2
AGP: 4.2.0, 4.2.2, 7.0.4, 7.2.0, 7.2.1

Ok, that sounds reasonable.  Should I close the pull request?

If that's easier, sure. Otherwise, I'm fine with a new commit that switches to using VariantSelector.

new commit that switches to using VariantSelector.

Did I understand correctly that I need to add a commit where some VariantSelector can be passed to onVariants()?

Actually wait looking at this further I'm confused. Is the goal of this PR to support AGP 4.2? Based on the title, I thought the goal was to support AGP 7.2 but the types in that codepath don't seem to have changed so I'm assuming AGP 7.2 is not broken. TL;DR: Are you using AGP 4.2 and want support for it?

I used for a while with agp 7.0.4, but with the upgrade to 7.2.0 the plugin stopped working. So I added support for 7.2.0 without affecting other older versions.

Here is error log with classpath 'com.android.tools.build:gradle:7.2.1' and classpath "com.supercilex.gradle:version-orchestrator:1.0.0-20211121.212215-8":
* What went wrong:
A problem occurred evaluating project ':app'.
> Failed to apply plugin 'com.supercilex.gradle.versions'.
   > Type com.android.build.api.extension.ApplicationAndroidComponentsExtension not present

Ohhh, the imports are different: com.android.build.api.extension.ApplicationAndroidComponentsExtension vs com.android.build.api.variant.ApplicationAndroidComponentsExtension.

Exactly

should just bump the AGP version to 7.0 and change the import.

but not backwards compatible with 4.x versions, right?
All right then, I'll change the title of the PR and remove the compat classes.

but not backwards compatible with 4.x versions, right?

Correct

Alrighty, thanks for the PR and apologies for all the confusion. :)


Question: where is 'devise-4.2.0/app/controllers' added to $LOAD_PATH

I can see when you require devise, the lib directory will be added into $LOAD_PATH. (most gems will do like this).
But I couldn't find where the code adds devise-4.2.0/app/controllers into $LOAD_PATH. (So the rails could find the devise built controllers)
Thanks in advanced.

@flanker we don't require or push anything to $LOAD_PATH manually, but defining the Devise::Engine class as a subclass of Rails::Engine makes Rails load controllers/models/assets/etc from gems as if they were in the application themselves. I can't pinpoint the exact code from Rails that does that but it's how it works :)

@lucasmazza Thanks a lot for your reply. I will check the relevant code then.


Can I directly train the policy without training the expert?

Thanks for your great repo.
I am wondering whether it is possible to train the policy directly without training the expert?
Thanks!

Our approach generates human-like navigation trajectories relying on knowledge distillation from the expert policy. Therefore, the expert policy is a necessary part to reproduce the results shown in our paper.
To train a normal multi-agent navigation policy without knowledge distillation, you have to modify the file train_poliy.py to initialize the training without loading the expert policy. For better training results, probably, you also have to change the reward function defined in models/env.py.