Persistent error messages and no volume control Sony HT-ZF9

Hello,
I installed the plugin and it shows a lot of errors and I can’t control volume with the remote or any other way.
I can add the device in home app and I can turn on, off and change the inputs, but these error is constant in homebridge.
It keeps appearing almost every second.
I have a Sony HT-ZF9
[14/02/2021, 21:19:46] [Sony Audio Platform] Adding new accessory: HT-ZF9
[14/02/2021, 21:19:46] [Sony Audio Platform] Compatible device found, added: HT-ZF9
[14/02/2021, 21:19:46] HT-ZF9 is running on port 52101.
[14/02/2021, 21:19:46] Please add [HT-ZF9] manually in Home app. Setup Code: 031-45-154
[14/02/2021, 21:19:47] [Sony Audio Platform] Device HT-ZF9 hasn't a notifier notifyExternalTerminalStatus in disabled [{"name":"notifyAvailablePlaybackFunction","version":"1.0"},{"name":"notifyPlayingContentInfo","version":"1.0"}]
[14/02/2021, 21:19:49] [Sony Audio Platform] Error: connect ECONNREFUSED <IP_ADDRESS>:1901
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1146:16) {
errno: -111,
code: 'ECONNREFUSED',
syscall: 'connect',
address: '<IP_ADDRESS>',
port: 1901,
config: {
url: 'http://<IP_ADDRESS>:1901/index.html',
method: 'get',
headers: {
Accept: 'application/json, text/plain, /',
'User-Agent': 'axios/0.21.1'
},
transformRequest: [ [Function: transformRequest] ],
transformResponse: [ [Function: transformResponse] ],
timeout: 0,
adapter: [Function: httpAdapter],
xsrfCookieName: 'XSRF-TOKEN',
xsrfHeaderName: 'X-XSRF-TOKEN',
maxContentLength: -1,
maxBodyLength: -1,
validateStatus: [Function: validateStatus],
data: undefined
},
request: <ref *1> Writable {
_writableState: WritableState {
objectMode: false,
highWaterMark: 16384,
finalCalled: false,
needDrain: false,
ending: false,
ended: false,
finished: false,
destroyed: false,
decodeStrings: true,
defaultEncoding: 'utf8',
length: 0,
writing: false,
corked: 0,
sync: true,
bufferProcessing: false,
onwrite: [Function: bound onwrite],
writecb: null,
writelen: 0,
afterWriteTickInfo: null,
buffered: [],
bufferedIndex: 0,
allBuffers: true,
allNoop: true,
pendingcb: 0,
prefinished: false,
errorEmitted: false,
emitClose: true,
autoDestroy: true,
errored: null,
closed: false
},
_events: [Object: null prototype] {
response: [Function: handleResponse],
error: [Function: handleRequestError]
},
_eventsCount: 2,
_maxListeners: undefined,
_options: {
maxRedirects: 21,
maxBodyLength: 10485760,
protocol: 'http:',
path: '/index.html',
method: 'GET',
headers: [Object],
agent: undefined,
agents: [Object],
auth: undefined,
hostname: '<IP_ADDRESS>',
port: '1901',
nativeProtocols: [Object],
pathname: '/index.html'
},
_ended: true,
_ending: true,
_redirectCount: 0,
_redirects: [],
_requestBodyLength: 0,
_requestBodyBuffers: [],
_onNativeResponse: [Function (anonymous)],
_currentRequest: ClientRequest {
_events: [Object: null prototype],
_eventsCount: 7,
_maxListeners: undefined,
outputData: [],
outputSize: 0,
writable: true,
destroyed: false,
_last: true,
chunkedEncoding: false,
shouldKeepAlive: false,
_defaultKeepAlive: true,
useChunkedEncodingByDefault: false,
sendDate: false,
_removedConnection: false,
_removedContLen: false,
_removedTE: false,
_contentLength: 0,
_hasBody: true,
_trailer: '',
finished: true,
_headerSent: true,
socket: [Socket],
_header: 'GET /index.html HTTP/1.1\r\n' +
'Accept: application/json, text/plain, /\r\n' +
'User-Agent: axios/0.21.1\r\n' +
'Host: <IP_ADDRESS>:1901\r\n' +
'Connection: close\r\n' +
'\r\n',
_keepAliveTimeout: 0,
_onPendingData: [Function: noopPendingOutput],
agent: [Agent],
socketPath: undefined,
method: 'GET',
maxHeaderSize: undefined,
insecureHTTPParser: undefined,
path: '/index.html',
_ended: false,
res: null,
aborted: false,
timeoutCb: null,
upgradeOrConnect: false,
parser: null,
maxHeadersCount: null,
reusedSocket: false,
host: '<IP_ADDRESS>',
protocol: 'http:',
_redirectable: [Circular *1],
[Symbol(kCapture)]: false,
[Symbol(kNeedDrain)]: false,
[Symbol(corked)]: 0,
[Symbol(kOutHeaders)]: [Object: null prototype]
},
_currentUrl: 'http://<IP_ADDRESS>:1901/index.html',
[Symbol(kCapture)]: false
},
response: undefined,
isAxiosError: true,
toJSON: [Function: toJSON]
}

Hi,
Can't localize the problem yet
Can you run the Homebridge in debug mode and drop the logs here again?

Ok here it is!
Another thing, every time Homebridge shuts down, the input names turn to, for example, "HDMI1" again, even when I named it "Apple TV" in the home app.
[15/02/2021, 11:24:40] [SonyAudio] Adding new accessory: HT-ZF9
[15/02/2021, 11:24:40] [SonyAudio] Compatible device found, added: HT-ZF9
[15/02/2021, 11:24:40] HT-ZF9 is running on port 52101.
[15/02/2021, 11:24:40] Please add [HT-ZF9] manually in Home app. Setup Code: 031-45-154
[15/02/2021, 11:24:40] [SonyAudio] Device HT-ZF9 opened a socked ws://<IP_ADDRESS>:10000/sony/system
[15/02/2021, 11:24:40] [SonyAudio] Device HT-ZF9 opened a socked ws://<IP_ADDRESS>:10000/sony/avContent
[15/02/2021, 11:24:40] [SonyAudio] Device HT-ZF9 opened a socked ws://<IP_ADDRESS>:10000/sony/audio
[15/02/2021, 11:24:40] [SonyAudio] Set Characteristic Active ->  true
[15/02/2021, 11:24:40] [SonyAudio] Device HT-ZF9 received initial message {"result":[{"enabled":[],"disabled":[{"name":"notifyAlexaRegistrationStatus","version":"1.0"},{"name":"notifyPowerStatus","version":"1.0"},{"name":"notifySWUpdateInfo","version":"1.0"},{"name":"notifySettingsUpdate","version":"1.1"},{"name":"notifyStorageStatus","version":"1.1"}]}],"id":1}
[15/02/2021, 11:24:40] [SonyAudio] Device HT-ZF9 sent subscribe message {"method":"switchNotifications","id":2,"params":[{"disabled":[{"name":"notifyAlexaRegistrationStatus","version":"1.0"},{"name":"notifySWUpdateInfo","version":"1.0"},{"name":"notifySettingsUpdate","version":"1.1"},{"name":"notifyStorageStatus","version":"1.1"}],"enabled":[{"name":"notifyPowerStatus","version":"1.0"}]}],"version":"1.0"}
[15/02/2021, 11:24:40] [SonyAudio] Device HT-ZF9 received initial message {"result":[{"enabled":[],"disabled":[{"name":"notifyVolumeInformation","version":"1.0"}]}],"id":1}
[15/02/2021, 11:24:40] [SonyAudio] Device HT-ZF9 sent subscribe message {"method":"switchNotifications","id":2,"params":[{"disabled":[],"enabled":[{"name":"notifyVolumeInformation","version":"1.0"}]}],"version":"1.0"}
[15/02/2021, 11:24:40] [SonyAudio] Device HT-ZF9 received initial message {"result":[{"enabled":[],"disabled":[{"name":"notifyAvailablePlaybackFunction","version":"1.0"},{"name":"notifyPlayingContentInfo","version":"1.0"}]}],"id":1}
[15/02/2021, 11:24:40] [SonyAudio] Device HT-ZF9 hasn't a notifier notifyExternalTerminalStatus in disabled [{"name":"notifyAvailablePlaybackFunction","version":"1.0"},{"name":"notifyPlayingContentInfo","version":"1.0"}]
[15/02/2021, 11:24:40] [SonyAudio] Device HT-ZF9 sent subscribe message {"method":"switchNotifications","id":2,"params":[{"disabled":[{"name":"notifyAvailablePlaybackFunction","version":"1.0"}],"enabled":[{"name":"notifyPlayingContentInfo","version":"1.0"}]}],"version":"1.0"}
[15/02/2021, 11:24:40] [SonyAudio] Device HT-ZF9 received subscription status {"result":[{"enabled":[{"name":"notifyPowerStatus","version":"1.0"}],"disabled":[{"name":"notifyAlexaRegistrationStatus","version":"1.0"},{"name":"notifySWUpdateInfo","version":"1.0"},{"name":"notifySettingsUpdate","version":"1.1"},{"name":"notifyStorageStatus","version":"1.1"}]}],"id":2}
[15/02/2021, 11:24:40] [SonyAudio] Device HT-ZF9 received subscription status {"result":[{"enabled":[{"name":"notifyPlayingContentInfo","version":"1.0"}],"disabled":[{"name":"notifyAvailablePlaybackFunction","version":"1.0"}]}],"id":2}
[15/02/2021, 11:24:40] [SonyAudio] Device HT-ZF9 received subscription status {"result":[{"enabled":[],"disabled":[{"name":"notifyVolumeInformation","version":"1.0"}]}],"id":2}
[15/02/2021, 11:24:40] [SonyAudio] Set Characteristic Mute ->  false
[15/02/2021, 11:24:40] [SonyAudio] Set Characteristic ActiveIdentifier ->  2
[15/02/2021, 11:24:42] [SonyAudio] Error: connect ECONNREFUSED <IP_ADDRESS>:1901
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1146:16) {
errno: -111,
code: 'ECONNREFUSED',
syscall: 'connect',
address: '<IP_ADDRESS>',
port: 1901,
config: {
url: 'http://<IP_ADDRESS>:1901/index.html',
method: 'get',
headers: {
Accept: 'application/json, text/plain, /',
'User-Agent': 'axios/0.21.1'
},
transformRequest: [ [Function: transformRequest] ],
transformResponse: [ [Function: transformResponse] ],
timeout: 0,
adapter: [Function: httpAdapter],
xsrfCookieName: 'XSRF-TOKEN',
xsrfHeaderName: 'X-XSRF-TOKEN',
maxContentLength: -1,
maxBodyLength: -1,
validateStatus: [Function: validateStatus],
data: undefined
},
request: <ref *1> Writable {
_writableState: WritableState {
objectMode: false,
highWaterMark: 16384,
finalCalled: false,
needDrain: false,
ending: false,
ended: false,
finished: false,
destroyed: false,
decodeStrings: true,
defaultEncoding: 'utf8',
length: 0,
writing: false,
corked: 0,
sync: true,
bufferProcessing: false,
onwrite: [Function: bound onwrite],
writecb: null,
writelen: 0,
afterWriteTickInfo: null,
buffered: [],
bufferedIndex: 0,
allBuffers: true,
allNoop: true,
pendingcb: 0,
prefinished: false,
errorEmitted: false,
emitClose: true,
autoDestroy: true,
errored: null,
closed: false
},
_events: [Object: null prototype] {
response: [Function: handleResponse],
error: [Function: handleRequestError]
},
_eventsCount: 2,
_maxListeners: undefined,
_options: {
maxRedirects: 21,
maxBodyLength: 10485760,
protocol: 'http:',
path: '/index.html',
method: 'GET',
headers: [Object],
agent: undefined,
agents: [Object],
auth: undefined,
hostname: '<IP_ADDRESS>',
port: '1901',
nativeProtocols: [Object],
pathname: '/index.html'
},
_ended: true,
_ending: true,
_redirectCount: 0,
_redirects: [],
_requestBodyLength: 0,
_requestBodyBuffers: [],
_onNativeResponse: [Function (anonymous)],
_currentRequest: ClientRequest {
_events: [Object: null prototype],
_eventsCount: 7,
_maxListeners: undefined,
outputData: [],
outputSize: 0,
writable: true,
destroyed: false,
_last: true,
chunkedEncoding: false,
shouldKeepAlive: false,
_defaultKeepAlive: true,
useChunkedEncodingByDefault: false,
sendDate: false,
_removedConnection: false,
_removedContLen: false,
_removedTE: false,
_contentLength: 0,
_hasBody: true,
_trailer: '',
finished: true,
_headerSent: true,
socket: [Socket],
_header: 'GET /index.html HTTP/1.1\r\n' +
'Accept: application/json, text/plain, /\r\n' +
'User-Agent: axios/0.21.1\r\n' +
'Host: <IP_ADDRESS>:1901\r\n' +
'Connection: close\r\n' +
'\r\n',
_keepAliveTimeout: 0,
_onPendingData: [Function: noopPendingOutput],
agent: [Agent],
socketPath: undefined,
method: 'GET',
maxHeaderSize: undefined,
insecureHTTPParser: undefined,
path: '/index.html',
_ended: false,
res: null,
aborted: false,
timeoutCb: null,
upgradeOrConnect: false,
parser: null,
maxHeadersCount: null,
reusedSocket: false,
host: '<IP_ADDRESS>',
protocol: 'http:',
_redirectable: [Circular *1],
[Symbol(kCapture)]: false,
[Symbol(kNeedDrain)]: false,
[Symbol(corked)]: 0,
[Symbol(kOutHeaders)]: [Object: null prototype]
},
_currentUrl: 'http://<IP_ADDRESS>:1901/index.html',
[Symbol(kCapture)]: false
},
response: undefined,
isAxiosError: true,
toJSON: [Function: toJSON]
}
And it keeps repeating this error:
[15/02/2021, 11:24:47] [SonyAudio] Error: connect ECONNREFUSED <IP_ADDRESS>:1901
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1146:16) {
errno: -111,
code: 'ECONNREFUSED',
syscall: 'connect',
address: '<IP_ADDRESS>',
port: 1901,
config: {
url: 'http://<IP_ADDRESS>:1901/index.html',
method: 'get',
headers: {
Accept: 'application/json, text/plain, /',
'User-Agent': 'axios/0.21.1'
},
transformRequest: [ [Function: transformRequest] ],
transformResponse: [ [Function: transformResponse] ],
timeout: 0,
adapter: [Function: httpAdapter],
xsrfCookieName: 'XSRF-TOKEN',
xsrfHeaderName: 'X-XSRF-TOKEN',
maxContentLength: -1,
maxBodyLength: -1,
validateStatus: [Function: validateStatus],
data: undefined
},
request: <ref *1> Writable {
_writableState: WritableState {
objectMode: false,
highWaterMark: 16384,
finalCalled: false,
needDrain: false,
ending: false,
ended: false,
finished: false,
destroyed: false,
decodeStrings: true,
defaultEncoding: 'utf8',
length: 0,
writing: false,
corked: 0,
sync: true,
bufferProcessing: false,
onwrite: [Function: bound onwrite],
writecb: null,
writelen: 0,
afterWriteTickInfo: null,
buffered: [],
bufferedIndex: 0,
allBuffers: true,
allNoop: true,
pendingcb: 0,
prefinished: false,
errorEmitted: false,
emitClose: true,
autoDestroy: true,
errored: null,
closed: false
},
_events: [Object: null prototype] {
response: [Function: handleResponse],
error: [Function: handleRequestError]
},
_eventsCount: 2,
_maxListeners: undefined,
_options: {
maxRedirects: 21,
maxBodyLength: 10485760,
protocol: 'http:',
path: '/index.html',
method: 'GET',
headers: [Object],
agent: undefined,
agents: [Object],
auth: undefined,
hostname: '<IP_ADDRESS>',
port: '1901',
nativeProtocols: [Object],
pathname: '/index.html'
},
_ended: true,
_ending: true,
_redirectCount: 0,
_redirects: [],
_requestBodyLength: 0,
_requestBodyBuffers: [],
_onNativeResponse: [Function (anonymous)],
_currentRequest: ClientRequest {
_events: [Object: null prototype],
_eventsCount: 7,
_maxListeners: undefined,
outputData: [],
outputSize: 0,
writable: true,
destroyed: false,
_last: true,
chunkedEncoding: false,
shouldKeepAlive: false,
_defaultKeepAlive: true,
useChunkedEncodingByDefault: false,
sendDate: false,
_removedConnection: false,
_removedContLen: false,
_removedTE: false,
_contentLength: 0,
_hasBody: true,
_trailer: '',
finished: true,
_headerSent: true,
socket: [Socket],
_header: 'GET /index.html HTTP/1.1\r\n' +
'Accept: application/json, text/plain, /\r\n' +
'User-Agent: axios/0.21.1\r\n' +
'Host: <IP_ADDRESS>:1901\r\n' +
'Connection: close\r\n' +
'\r\n',
_keepAliveTimeout: 0,
_onPendingData: [Function: noopPendingOutput],
agent: [Agent],
socketPath: undefined,
method: 'GET',
maxHeaderSize: undefined,
insecureHTTPParser: undefined,
path: '/index.html',
_ended: false,
res: null,
aborted: false,
timeoutCb: null,
upgradeOrConnect: false,
parser: null,
maxHeadersCount: null,
reusedSocket: false,
host: '<IP_ADDRESS>',
protocol: 'http:',
_redirectable: [Circular *1],
[Symbol(kCapture)]: false,
[Symbol(kNeedDrain)]: false,
[Symbol(corked)]: 0,
[Symbol(kOutHeaders)]: [Object: null prototype]
},
_currentUrl: 'http://<IP_ADDRESS>:1901/index.html',
[Symbol(kCapture)]: false
},
response: undefined,
isAxiosError: true,
toJSON: [Function: toJSON]
}

Can't find the problem yet.
I published a new release with additional debug logging.
Whenever there is an opportunity, update and send me fresh logs in debug mode.
As for other problems, I will answer after solving with a flood of errors
Thank you for your participation
P.S. What platform is homebridge running on?

Ok, homebridge is running on a Raspberry Pi.
Here are the logs with the new release:
[15/02/2021, 13:07:53] [SonyAudio] Start registering a new device from the description: http://<IP_ADDRESS>:54380/MediaRenderer_HT-ZF9.xml
[15/02/2021, 13:07:54] [SonyAudio] Adding new accessory: HT-ZF9
[15/02/2021, 13:07:54] [SonyAudio] Compatible device found, added: HT-ZF9
[15/02/2021, 13:07:54] HT-ZF9 is running on port 52101.
[15/02/2021, 13:07:54] Please add [HT-ZF9] manually in Home app. Setup Code: 031-45-154
[15/02/2021, 13:07:54] [SonyAudio] Device HT-ZF9 opened a socked ws://<IP_ADDRESS>:10000/sony/audio
[15/02/2021, 13:07:54] [SonyAudio] Device HT-ZF9 opened a socked ws://<IP_ADDRESS>:10000/sony/system
[15/02/2021, 13:07:54] [SonyAudio] Device HT-ZF9 opened a socked ws://<IP_ADDRESS>:10000/sony/avContent
[15/02/2021, 13:07:54] [SonyAudio] Set Characteristic Active ->  true
[15/02/2021, 13:07:54] [SonyAudio] Device HT-ZF9 received initial message {"result":[{"enabled":[],"disabled":[{"name":"notifyVolumeInformation","version":"1.0"}]}],"id":1}
[15/02/2021, 13:07:54] [SonyAudio] Device HT-ZF9 sent subscribe message {"method":"switchNotifications","id":2,"params":[{"disabled":[],"enabled":[{"name":"notifyVolumeInformation","version":"1.0"}]}],"version":"1.0"}
[15/02/2021, 13:07:54] [SonyAudio] Device HT-ZF9 received initial message {"result":[{"enabled":[],"disabled":[{"name":"notifyAlexaRegistrationStatus","version":"1.0"},{"name":"notifyPowerStatus","version":"1.0"},{"name":"notifySWUpdateInfo","version":"1.0"},{"name":"notifySettingsUpdate","version":"1.1"},{"name":"notifyStorageStatus","version":"1.1"}]}],"id":1}
[15/02/2021, 13:07:54] [SonyAudio] Device HT-ZF9 sent subscribe message {"method":"switchNotifications","id":2,"params":[{"disabled":[{"name":"notifyAlexaRegistrationStatus","version":"1.0"},{"name":"notifySWUpdateInfo","version":"1.0"},{"name":"notifySettingsUpdate","version":"1.1"},{"name":"notifyStorageStatus","version":"1.1"}],"enabled":[{"name":"notifyPowerStatus","version":"1.0"}]}],"version":"1.0"}
[15/02/2021, 13:07:54] [SonyAudio] Device HT-ZF9 received initial message {"result":[{"enabled":[],"disabled":[{"name":"notifyAvailablePlaybackFunction","version":"1.0"},{"name":"notifyPlayingContentInfo","version":"1.0"}]}],"id":1}
[15/02/2021, 13:07:54] [SonyAudio] Device HT-ZF9 hasn't a notifier notifyExternalTerminalStatus in disabled [{"name":"notifyAvailablePlaybackFunction","version":"1.0"},{"name":"notifyPlayingContentInfo","version":"1.0"}]
[15/02/2021, 13:07:54] [SonyAudio] Device HT-ZF9 sent subscribe message {"method":"switchNotifications","id":2,"params":[{"disabled":[{"name":"notifyAvailablePlaybackFunction","version":"1.0"}],"enabled":[{"name":"notifyPlayingContentInfo","version":"1.0"}]}],"version":"1.0"}
[15/02/2021, 13:07:54] [SonyAudio] Device HT-ZF9 received subscription status {"result":[{"enabled":[],"disabled":[{"name":"notifyVolumeInformation","version":"1.0"}]}],"id":2}
[15/02/2021, 13:07:54] [SonyAudio] Device HT-ZF9 received subscription status {"result":[{"enabled":[{"name":"notifyPowerStatus","version":"1.0"}],"disabled":[{"name":"notifyAlexaRegistrationStatus","version":"1.0"},{"name":"notifySWUpdateInfo","version":"1.0"},{"name":"notifySettingsUpdate","version":"1.1"},{"name":"notifyStorageStatus","version":"1.1"}]}],"id":2}
[15/02/2021, 13:07:54] [SonyAudio] Device HT-ZF9 received subscription status {"result":[{"enabled":[{"name":"notifyPlayingContentInfo","version":"1.0"}],"disabled":[{"name":"notifyAvailablePlaybackFunction","version":"1.0"}]}],"id":2}
[15/02/2021, 13:07:54] [SonyAudio] Set Characteristic Mute ->  false
[15/02/2021, 13:07:54] [SonyAudio] Set Characteristic ActiveIdentifier ->  2
[15/02/2021, 13:07:57] [SonyAudio] Start registering a new device from the description: http://<IP_ADDRESS>:1901/index.html
[15/02/2021, 13:07:57] [SonyAudio] Can't retrieve the device description at http://<IP_ADDRESS>:1901/index.html: Error: connect ECONNREFUSED <IP_ADDRESS>:1901
[15/02/2021, 13:08:02] [SonyAudio] Start registering a new device from the description: http://<IP_ADDRESS>:1901/index.html
[15/02/2021, 13:08:02] [SonyAudio] Can't retrieve the device description at http://<IP_ADDRESS>:1901/index.html: Error: connect ECONNREFUSED <IP_ADDRESS>:1901
When changing the volume with the control center remote, nothing happens with the sound bar volume - volume up logs this:
[15/02/2021, 13:11:41] [SonyAudio] Set Characteristic VolumeSelector ->  0
[15/02/2021, 13:11:42] [SonyAudio] Start registering a new device from the description: http://<IP_ADDRESS>:1901/index.html
[15/02/2021, 13:11:42] [SonyAudio] Can't retrieve the device description at http://<IP_ADDRESS>:1901/index.html: Error: connect ECONNREFUSED <IP_ADDRESS>:1901
Volume down:
[15/02/2021, 13:12:54] [SonyAudio] Set Characteristic VolumeSelector ->  1
[15/02/2021, 13:12:54] [SonyAudio] Set Characteristic Active ->  1
[15/02/2021, 13:12:54] [SonyAudio] Device HT-ZF9: Device API got an error: {"error":[40000,"Request Retry"],"id":55}
[15/02/2021, 13:12:54] [SonyAudio] Set Characteristic Active ->  true
[15/02/2021, 13:12:54] [SonyAudio] Set Characteristic Mute ->  false
[15/02/2021, 13:12:54] [SonyAudio] Set Characteristic ActiveIdentifier ->  2
[15/02/2021, 13:12:57] [SonyAudio] Start registering a new device from the description: http://<IP_ADDRESS>:1901/index.html
[15/02/2021, 13:12:57] [SonyAudio] Can't retrieve the device description at http://<IP_ADDRESS>:1901/index.html: Error: connect ECONNREFUSED <IP_ADDRESS>:1901
And it continuously show this error:
[15/02/2021, 13:13:02] [SonyAudio] Start registering a new device from the description: http://<IP_ADDRESS>:1901/index.html
[15/02/2021, 13:13:02] [SonyAudio] Can't retrieve the device description at http://<IP_ADDRESS>:1901/index.html: Error: connect ECONNREFUSED <IP_ADDRESS>:1901
[15/02/2021, 13:13:07] [SonyAudio] Start registering a new device from the description: http://<IP_ADDRESS>:1901/index.html
[15/02/2021, 13:13:07] [SonyAudio] Can't retrieve the device description at http://<IP_ADDRESS>:1901/index.html: Error: connect ECONNREFUSED <IP_ADDRESS>:1901
[15/02/2021, 13:13:12] [SonyAudio] Start registering a new device from the description: http://<IP_ADDRESS>:1901/index.html
[15/02/2021, 13:13:12] [SonyAudio] Can't retrieve the device description at http://<IP_ADDRESS>:1901/index.html: Error: connect ECONNREFUSED <IP_ADDRESS>:1901
[15/02/2021, 13:13:17] [SonyAudio] Start registering a new device from the description: http://<IP_ADDRESS>:1901/index.html
[15/02/2021, 13:13:17] [SonyAudio] Can't retrieve the device description at http://<IP_ADDRESS>:1901/index.html: Error: connect ECONNREFUSED <IP_ADDRESS>:1901
[15/02/2021, 13:13:22] [SonyAudio] Start registering a new device from the description: http://<IP_ADDRESS>:1901/index.html
[15/02/2021, 13:13:22] [SonyAudio] Can't retrieve the device description at http://<IP_ADDRESS>:1901/index.html: Error: connect ECONNREFUSED <IP_ADDRESS>:1901

Thx,
OK
What I see: your platform (Raspberry) has a process running that responds to discovery requests for SONY devices.
Each device class has a specific header that it responds to. For example, SONY responds to urn: schemas-sony-com: service: ScalarWebAPI: 1. For other devices, the header is different and other devices should not respond to requests for other devices.
But some process on your platform (at <IP_ADDRESS>:1901) is responding to this discovery request, which is a violation of the SSDP protocol.
I will make sure that this error does not appear more than once. I cannot completely hide that error, because this may prevent localizing the problems of other users (when, for example, the user has network problems), after all, the problem is in your network environment.

Hm I get it, I’ve used to use the homebridge-Sony-audio-control plugin, I’ve uninstalled it when I installed this plugin, but maybe something is still on the network. Do you have any idea what could be?
So, because of this, I can’t control volume through the control center remote?

Thank you for the plugin and for your help! :)
No problem and thanks for the help testing and catching bugs  )

After posting a new release of stopping the flood of errors, I close this issue.
Please create new separate tasks for each issue mentioned in the thread. Most likely these are errors on my side )

So, because of this, I can’t control volume through the control center remote?

No no. Volume is definitely my bug.
And I will need your help to solve it )

Ok! I can help of course!

I’ve uninstalled it when I installed this plugin, but maybe something is still on the network. Do you have any idea what could be?
I am not familiar with Raspberry but you can google 'how to find which process is using a port'

Look at here https://www.codegrepper.com/code-examples/fortran/kill+running+port+raspberry+pi
But you have to look for a process for port 1900

@ojoaosemtil
Error flooding was stopped at v1.0.5
For unanswered questions, create new issues, please

Hello!
I don’t know if you changed something but in this new release I keep seeing again a lot of messages about the error:
[SonyAudio] Can't retrieve the device description at http://<IP_ADDRESS>:1901/index.html: Error: connect ECONNREFUSED <IP_ADDRESS>:1901
Is it possible to keep it like before, warning just once?
Thank u!

Hi @ojoaosemtil
I fixed it in v1.0.9

Thank u!!

you can confirm that everything is ok?

I’ve just updated and everything seems to be fine! 😊


CPLAT-4335 Add deprecations in preparation for 5.0.0

As part of preparations for ReactJS 16 support coming in version 5.0.0, we need to alert consumers to some important deprecations by annotating those deprecated members, and providing comments about what to use instead (if applicable).
Deprecations:

Legacy context APIs
isMounted
react_test_utils.SimulateNative
String Component.refs
Component.replaceStates
All aspects of server-side rendering
Component.bind
Component.transferComponentState

@kealjones-wk @joebingham-wk @greglittlefield-wf

+1


Game Crashed with other Mods

Hello,
i just made a new Modpack for the Minecraft version 1.12.2 and addet a bunch of mod (list below)
and after I addet the Mod chiseled me the modpack wouldnt start anymore. I looked arround your Github and saw in one Post that you talked about a list of incompatible mods. I looked arround for that list but i couldnt find it. btw the modpack starts fine without the chiseled me mod.
Would be very happy if you could send me the list of incompatible mods or tell me where i can find it

Yeah, the list is not really a physical thing, because when I say 'list of mods' its more like 'I know there is a lot of mods who dont work, and there are issues with exact mods on the github, and when I get to fix all of that I will test for all of them'.
Most notable are OptiFine, iChulUtil (and thus all mods by iChun) and some others from the issues around here.
You have a lot of mods, usually I ask to do a binary search - remove half of the mods, check if it crashes, remove other half - if it crashes with one half and not the other, then the incompatible mod is in that half, repeat the process with only that half, do that until you find the incompatible mod.
This is not really easy to do, and I am sorry for the inconvenience, but yes, since so many mods are incompatible using this mod in modpacks is not really a thing so far.
Usually it is not compatible with so called coremods (it is one of them too) - the mods that change the game internals, for pretty obvious reason - they both tamper with something at the same time and everything breaks.
In earlier forge there was a whole separate 'coremods' folder, but now there isn't, so you can identify such mods by '-Core' suffixes, or by finding 'list of coremods' in logs.
Also yeah, please provide the crashlog, would help so very much.

A lot of mod compat issues are fixed in the current master (releasing it as the next version in about a week) so your issues may or may not be fixed, you may try again with the next release once it is out, but currently I cannot help you without an actual crash.

A crazy ton of mod compat and other issues were resolved in latest discord beta, the mod successfully worked when added to the Project Ozone 3 modpack.
Closing this as stale issue with no further input, feel free to open a new one if you need to.

A crazy ton of mod compat and other issues were resolved in latest discord beta, the mod successfully worked when added to the Project Ozone 3 modpack.
Closing this as stale issue with no further input, feel free to open a new one if you need to.


added greetings action

This PR Contains
Added Greetings GHA that welcomes and congratulate
opening your very first issue in keploy
opening your very first pull request in keploy

cc @nehagup

CC @nehagup


Media Library: Sorting and Pagination

Demo
https://github.com/BeaconCMS/beacon_live_admin/assets/13787741/e486caef-5b48-42d5-a411-0ba89263eccb

@leandrocp could you please review that one


Installing Superset via Docker-compose Up

I am on ubuntu. I am following the instructions to install Superset via docker via this link:
https://superset.incubator.apache.org/installation.html#start-with-docker
Expected results
I expect after these steps if I open http://localhost:8088, I see Superset UI
Actual results
I see a blank page at http://localhost:8088
Screenshots

How to reproduce the bug

Go to a computer with Ubuntu installed on it
Follow the exact instructions at https://superset.incubator.apache.org/installation.html#start-with-docker
You may get some error messages asking for installing docker and its dependencies and creating and running one. Please do those.
See error

Environment
(please complete the following information):

superset version: not-installed!!! [trying to install]
python version: Python 3.7.4
node.js version: v8.10.0
npm version: 3.5.2

Checklist
Make sure these boxes are checked before submitting your issue - thank you!

[X] I have checked the superset logs for python stacktraces and included it here as text if there are any.
[X] I have reproduced the issue with at least the latest released version of superset.
[X] I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context
Here is the full log:
'(base) smirs@emarats-brain:~/incubator-superset$ sudo docker-compose up
Starting superset_db    ... done
Starting superset_cache ... done
Starting superset_tests_worker ... done
Starting superset_worker       ... done
Starting superset_init         ... done
Starting superset_node         ... done
Starting superset_app          ... done
Attaching to superset_db, superset_cache, superset_tests_worker, superset_worker, superset_init, superset_node, superset_app
superset_db              |
superset_db              | PostgreSQL Database directory appears to contain a database; Skipping initialization
superset_db              |
superset_db              | 2020-05-21 19:17:21.482 UTC [1] LOG:  listening on IPv4 address "<IP_ADDRESS>", port 5432
superset_cache           | 1:C 21 May 19:17:22.498 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
superset_db              | 2020-05-21 19:17:21.482 UTC [1] LOG:  listening on IPv6 address "::", port 5432
superset_db              | 2020-05-21 19:17:21.484 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
superset_init            |
superset_init            | ######################################################################
superset_init            |
superset_init            |
superset_init            | Init Step 1/4 [Starting] -- Setting up admin user ( admin / admin )
superset_init            |
superset_init            |
superset_init            | ######################################################################
superset_init            |
superset_cache           | 1:M 21 May 19:17:22.499 # You requested maxclients of 10000 requiring at least 10032 max file descriptors.
superset_cache           | 1:M 21 May 19:17:22.499 # Server can't set maximum open files to 10032 because of OS error: Operation not permitted.
superset_cache           | 1:M 21 May 19:17:22.499 # Current maximum open files is 4096. maxclients has been reduced to 4064 to compensate for low ulimit. If you need higher maxclients increase 'ulimit -n'.
superset_db              | 2020-05-21 19:17:21.497 UTC [25] LOG:  database system was shut down at 2020-05-21 19:17:17 UTC
superset_cache           |                 _._
superset_cache           |            _.-``__ ''-._
superset_cache           |       _.-``    `.  `_.  ''-._           Redis 3.2.12 (00000000/0) 64 bit
superset_cache           |   .-`` .-```.  ```\/    _.,_ ''-._
superset_cache           |  (    '      ,       .-`  | `,    )     Running in standalone mode
superset_cache           |  |`-._`-...-` __...-.``-._|'` _.-'|     Port: 6379
superset_cache           |  |    `-._   `._    /     _.-'    |     PID: 1
superset_cache           |   `-._    `-._  `-./  _.-'    _.-'
superset_cache           |  |`-._`-._    `-.__.-'    _.-'_.-'|
superset_cache           |  |    `-._`-._        _.-'_.-'    |           http://redis.io
superset_cache           |   `-._    `-._`-.__.-'_.-'    _.-'
superset_cache           |  |`-._`-._    `-.__.-'    _.-'_.-'|
superset_cache           |  |    `-._`-._        _.-'_.-'    |
superset_cache           |   `-._    `-._`-.__.-'_.-'    _.-'
superset_cache           |       `-._    `-.__.-'    _.-'
superset_cache           |           `-._        _.-'
superset_cache           |               `-.__.-'
superset_cache           |
superset_cache           | 1:M 21 May 19:17:22.500 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128.
superset_db              | 2020-05-21 19:17:21.513 UTC [1] LOG:  database system is ready to accept connections
superset_cache           | 1:M 21 May 19:17:22.500 # Server started, Redis version 3.2.12
superset_cache           | 1:M 21 May 19:17:22.500 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
superset_cache           | 1:M 21 May 19:17:22.500 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command 'echo never > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled.
superset_cache           | 1:M 21 May 19:17:22.500 * DB loaded from disk: 0.000 seconds
superset_cache           | 1:M 21 May 19:17:22.500 * The server is now ready to accept connections on port 6379
superset_tests_worker    | INFO:superset.utils.logging_configurator:logging was configured successfully
superset_db              | 2020-05-21 19:17:24.857 UTC [32] FATAL:  database "test" does not exist
superset_tests_worker    | /usr/local/lib/python3.6/site-packages/flask_caching/__init__.py:189: UserWarning: Flask-Caching: CACHE_TYPE is set to null, caching is effectively disabled.
superset_tests_worker    |   "Flask-Caching: CACHE_TYPE is set to null, "
superset_tests_worker    | ERROR:flask_appbuilder.security.sqla.manager:DB Creation and initialization failed: (psycopg2.OperationalError) FATAL:  database "test" does not exist
superset_tests_worker    |
superset_tests_worker    | (Background on this error at: http://sqlalche.me/e/e3q8)
superset_tests_worker    | Loaded your LOCAL configuration at [/app/pythonpath/superset_config.py]
superset_worker          | INFO:superset.utils.logging_configurator:logging was configured successfully
superset_tests_worker exited with code 1
superset_init            | INFO:superset.utils.logging_configurator:logging was configured successfully
superset_app             |  * Serving Flask app "superset.app:create_app()" (lazy loading)
superset_app             |  * Environment: development
superset_app             |  * Debug mode: on
superset_app             |  * Running on http://<IP_ADDRESS>:8088/ (Press CTRL+C to quit)
superset_app             |  * Restarting with stat
superset_app             | INFO:superset.utils.logging_configurator:logging was configured successfully
superset_init            | Loaded your LOCAL configuration at [/app/pythonpath/superset_config.py]
superset_init            | Recognized Database Authentications.
superset_init            | Error! User already exists admin
superset_init            | /usr/local/lib/python3.6/site-packages/flask_caching/__init__.py:189: UserWarning: Flask-Caching: CACHE_TYPE is set to null, caching is effectively disabled.
superset_init            |   "Flask-Caching: CACHE_TYPE is set to null, "
superset_init            |
superset_init            | ######################################################################
superset_init            |
superset_init            |
superset_init            | Init Step 1/4 [Complete] -- Setting up admin user
superset_init            |
superset_init            |
superset_init            | ######################################################################
superset_init            |
superset_init            |
superset_init            | ######################################################################
superset_init            |
superset_init            |
superset_init            | Init Step 2/4 [Starting] -- Applying DB migrations
superset_init            |
superset_init            |
superset_init            | ######################################################################
superset_init            |
superset_worker          | /usr/local/lib/python3.6/site-packages/flask_caching/__init__.py:189: UserWarning: Flask-Caching: CACHE_TYPE is set to null, caching is effectively disabled.
superset_worker          |   "Flask-Caching: CACHE_TYPE is set to null, "
superset_worker          | [2020-05-21 19:17:27,512: INFO/MainProcess] Connected to redis://redis:6379/0
superset_worker          | [2020-05-21 19:17:27,524: INFO/MainProcess] mingle: searching for neighbors
superset_app             |  * Debugger is active!
superset_app             |  * Debugger PIN: 294-670-256
superset_worker          | [2020-05-21 19:17:28,544: INFO/MainProcess] mingle: all alone
superset_worker          | [2020-05-21 19:17:28,552: INFO/MainProcess] celery@6f1df210e742 ready.
superset_app             | INFO:superset.utils.logging_configurator:logging was configured successfully
superset_init            | INFO:superset.utils.logging_configurator:logging was configured successfully
superset_init            | /usr/local/lib/python3.6/site-packages/flask_caching/__init__.py:189: UserWarning: Flask-Caching: CACHE_TYPE is set to null, caching is effectively disabled.
superset_init            |   "Flask-Caching: CACHE_TYPE is set to null, "
superset_init            | INFO  [alembic.runtime.migration] Context impl PostgresqlImpl.
superset_init            | INFO  [alembic.runtime.migration] Will assume transactional DDL.
superset_init            | Loaded your LOCAL configuration at [/app/pythonpath/superset_config.py]
superset_init            |
superset_init            | ######################################################################
superset_init            |
superset_init            |
superset_init            | Init Step 2/4 [Complete] -- Applying DB migrations
superset_init            |
superset_init            |
superset_init            | ######################################################################
superset_init            |
superset_init            |
superset_init            | ######################################################################
superset_init            |
superset_init            |
superset_init            | Init Step 3/4 [Starting] -- Loading examples
superset_init            |
superset_init            |
superset_init            | ######################################################################
superset_init            |
superset_init            | INFO:superset.utils.logging_configurator:logging was configured successfully
superset_app             | /usr/local/lib/python3.6/site-packages/flask_caching/__init__.py:189: UserWarning: Flask-Caching: CACHE_TYPE is set to null, caching is effectively disabled.
superset_app             |   "Flask-Caching: CACHE_TYPE is set to null, "
superset_app             | <IP_ADDRESS> - - [21/May/2020 19:17:34] "GET / HTTP/1.1" 302 -
superset_app             | INFO:werkzeug:<IP_ADDRESS> - - [21/May/2020 19:17:34] "GET / HTTP/1.1" 302 -
superset_app             | <IP_ADDRESS> - - [21/May/2020 19:17:34] "GET /superset/welcome HTTP/1.1" 200 -
superset_app             | INFO:werkzeug:<IP_ADDRESS> - - [21/May/2020 19:17:34] "GET /superset/welcome HTTP/1.1" 200 -
superset_app             | <IP_ADDRESS> - - [21/May/2020 19:17:34] "GET /static/assets/images/loading.gif HTTP/1.1" 404 -
superset_app             | INFO:werkzeug:<IP_ADDRESS> - - [21/May/2020 19:17:34] "GET /static/assets/images/loading.gif HTTP/1.1" 404 -
superset_init            | /usr/local/lib/python3.6/site-packages/flask_caching/__init__.py:189: UserWarning: Flask-Caching: CACHE_TYPE is set to null, caching is effectively disabled.
superset_init            |   "Flask-Caching: CACHE_TYPE is set to null, "
superset_init            | DEBUG:superset.models.core:Database.get_sqla_engine(). Masked URL: postgresql://superset:XXXXXXXXXX@db:5432/superset
superset_init            | Loaded your LOCAL configuration at [/app/pythonpath/superset_config.py]
superset_init            | Loading examples metadata and related data into examples
superset_init            | Creating default CSS templates
superset_init            | Loading energy related dataset
superset_init            | Creating table [wb_health_population] reference
superset_init            | Loading [World Bank's Health Nutrition and Population Stats]
superset_init            | Creating table [wb_health_population] reference
superset_init            | Creating slices
superset_init            | Creating a World's Health Bank dashboard
superset_init            | Loading [Birth names]
superset_init            | Creating some slices
superset_init            | Creating a dashboard
superset_init            | Loading [Unicode test data]
superset_init            | Creating table [unicode_test] reference
superset_init            | Creating a slice
superset_init            | Creating a dashboard
superset_init            | Loading [Random time series data]
superset_init            | Creating table [random_time_series] reference
superset_init            | Creating a slice
superset_init            | Loading [Random long/lat data]
superset_init            | Creating table reference
superset_init            | Creating a slice
superset_init            | Loading [Country Map data]
superset_init            | Creating table reference
superset_init            | Creating a slice
superset_init            | Loading [Multiformat time series]
superset_init            | Creating table [multiformat_time_series] reference
superset_init            | Creating Heatmap charts
superset_init            | Loading [Paris GeoJson]
superset_init            | Creating table paris_iris_mapping reference
superset_init            | Loading [San Francisco population polygons]
superset_init            | Creating table sf_population_polygons reference
superset_init            | Loading [Flights data]
superset_init            | Done loading table!
superset_init            | Loading [BART lines]
superset_init            | Creating table bart_lines reference
superset_init            | Loading [Multi Line]
superset_init            | Creating table [wb_health_population] reference
superset_init            | Creating slices
superset_init            | Creating a World's Health Bank dashboard
superset_init            | Creating some slices
superset_init            | Creating a dashboard
superset_init            | Loading [Misc Charts] dashboard
superset_init            | Creating the dashboard
superset_init            | Loading DECK.gl demo
superset_init            | Loading deck.gl dashboard
superset_init            | Creating Scatterplot slice
superset_init            | Creating Screen Grid slice
superset_init            | Creating Hex slice
superset_init            | Creating Grid slice
superset_init            | Creating Polygon slice
superset_init            | Creating Arc slice
superset_init            | Creating Path slice
superset_init            | Creating a dashboard
superset_init            | Loading [Tabbed dashboard]
superset_init            | Creating a dashboard with nested tabs
superset_init            |
superset_init            | ######################################################################
superset_init            |
superset_init            |
superset_init            | Init Step 3/4 [Complete] -- Loading examples
superset_init            |
superset_init            |
superset_init            | ######################################################################
superset_init            |
superset_init            |
superset_init            | ######################################################################
superset_init            |
superset_init            |
superset_init            | Init Step 4/4 [Starting] -- Setting up roles and perms
superset_init            |
superset_init            |
superset_init            | ######################################################################
superset_init            |
superset_init            | INFO:superset.utils.logging_configurator:logging was configured successfully
superset_init            | /usr/local/lib/python3.6/site-packages/flask_caching/__init__.py:189: UserWarning: Flask-Caching: CACHE_TYPE is set to null, caching is effectively disabled.
superset_init            |   "Flask-Caching: CACHE_TYPE is set to null, "
superset_init            | INFO:superset.security.manager:Syncing role definition
superset_init            | INFO:superset.security.manager:Syncing Admin perms
superset_init            | INFO:superset.security.manager:Syncing Alpha perms
superset_init            | INFO:superset.security.manager:Syncing Gamma perms
superset_init            | INFO:superset.security.manager:Syncing granter perms
superset_init            | INFO:superset.security.manager:Syncing sql_lab perms
superset_init            | INFO:superset.security.manager:Fetching a set of all perms to lookup which ones are missing
superset_init            | INFO:superset.security.manager:Creating missing datasource permissions.
superset_init            | INFO:superset.security.manager:Creating missing database permissions.
superset_init            | INFO:superset.security.manager:Creating missing metrics permissions
superset_init            | INFO:superset.security.manager:Cleaning faulty perms
superset_init            | Loaded your LOCAL configuration at [/app/pythonpath/superset_config.py]
superset_init            |
superset_init            | ######################################################################
superset_init            |
superset_init            |
superset_init            | Init Step 4/4 [Complete] -- Setting up roles and perms
superset_init            |
superset_init            |
superset_init            | ######################################################################
superset_init            |
superset_init exited with code 0
superset_app             | <IP_ADDRESS> - - [21/May/2020 19:17:54] "GET /health HTTP/1.1" 200 -
superset_app             | INFO:werkzeug:<IP_ADDRESS> - - [21/May/2020 19:17:54] "GET /health HTTP/1.1" 200 -
superset_node            | npm WARN deprecated<EMAIL_ADDRESS>https://github.com/lydell/resolve-url#deprecated
superset_node            | npm WARN deprecated<EMAIL_ADDRESS>Please see https://github.com/lydell/urix#deprecated
superset_app             | <IP_ADDRESS> - - [21/May/2020 19:18:15] "GET / HTTP/1.1" 302 -
superset_app             | INFO:werkzeug:<IP_ADDRESS> - - [21/May/2020 19:18:15] "GET / HTTP/1.1" 302 -
superset_app             | <IP_ADDRESS> - - [21/May/2020 19:18:15] "GET /superset/welcome HTTP/1.1" 200 -
superset_app             | INFO:werkzeug:<IP_ADDRESS> - - [21/May/2020 19:18:15] "GET /superset/welcome HTTP/1.1" 200 -
superset_app             | <IP_ADDRESS> - - [21/May/2020 19:18:15] "GET /static/assets/images/loading.gif HTTP/1.1" 404 -
superset_app             | INFO:werkzeug:<IP_ADDRESS> - - [21/May/2020 19:18:15] "GET /static/assets/images/loading.gif HTTP/1.1" 404 -
superset_app             | <IP_ADDRESS> - - [21/May/2020 19:18:19] "GET /superset/welcome HTTP/1.1" 200 -
superset_app             | INFO:werkzeug:<IP_ADDRESS> - - [21/May/2020 19:18:19] "GET /superset/welcome HTTP/1.1" 200 -
superset_app             | <IP_ADDRESS> - - [21/May/2020 19:18:19] "GET /static/assets/images/loading.gif HTTP/1.1" 404 -
superset_app             | INFO:werkzeug:<IP_ADDRESS> - - [21/May/2020 19:18:19] "GET /static/assets/images/loading.gif HTTP/1.1" 404 -
superset_app             | <IP_ADDRESS> - - [21/May/2020 19:18:24] "GET /health HTTP/1.1" 200 -
superset_app             | INFO:werkzeug:<IP_ADDRESS> - - [21/May/2020 19:18:24] "GET /health HTTP/1.1" 200 -
superset_app             | <IP_ADDRESS> - - [21/May/2020 19:18:55] "GET /health HTTP/1.1" 200 -
superset_app             | INFO:werkzeug:<IP_ADDRESS> - - [21/May/2020 19:18:55] "GET /health HTTP/1.1" 200 -
superset_node            | npm WARN deprecated<EMAIL_ADDRESS>Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
superset_node            | npm WARN deprecated<EMAIL_ADDRESS>fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
superset_app             | <IP_ADDRESS> - - [21/May/2020 19:19:25] "GET /health HTTP/1.1" 200 -
superset_app             | INFO:werkzeug:<IP_ADDRESS> - - [21/May/2020 19:19:25] "GET /health HTTP/1.1" 200 -
superset_node            | /usr/local/bin/webpack -> /usr/local/lib/node_modules/webpack/bin/webpack.js
superset_node            | /usr/local/bin/webpack-cli -> /usr/local/lib/node_modules/webpack-cli/bin/cli.js
superset_node            | npm WARN notsup Unsupported engine for<EMAIL_ADDRESS>wanted: {"node":"<8.10.0"} (current: {"node":"10.20.1","npm":"6.14.4"})
superset_node            | npm WARN notsup Not compatible with your version of node/npm<EMAIL_ADDRESS>superset_node            | npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/webpack/node_modules/chokidar/node_modules/fsevents):
superset_node            | npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
superset_node            | npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/webpack/node_modules/watchpack-chokidar2/node_modules/chokidar/node_modules/fsevents):
superset_node            | npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
superset_node            |
superset_node            | +<EMAIL_ADDRESS>superset_node            | +<EMAIL_ADDRESS>superset_node            | updated 2 packages in 123.688s
superset_app             | <IP_ADDRESS> - - [21/May/2020 19:19:55] "GET /health HTTP/1.1" 200 -
superset_app             | INFO:werkzeug:<IP_ADDRESS> - - [21/May/2020 19:19:55] "GET /health HTTP/1.1" 200 -
superset_app             | <IP_ADDRESS> - - [21/May/2020 19:20:25] "GET /health HTTP/1.1" 200 -
superset_app             | INFO:werkzeug:<IP_ADDRESS> - - [21/May/2020 19:20:25] "GET /health HTTP/1.1" 200 -
superset_app             | <IP_ADDRESS> - - [21/May/2020 19:20:56] "GET /health HTTP/1.1" 200 -
superset_app             | INFO:werkzeug:<IP_ADDRESS> - - [21/May/2020 19:20:56] "GET /health HTTP/1.1" 200 -
superset_app             | <IP_ADDRESS> - - [21/May/2020 19:21:26] "GET /health HTTP/1.1" 200 -
superset_app             | INFO:werkzeug:<IP_ADDRESS> - - [21/May/2020 19:21:26] "GET /health HTTP/1.1" 200 -
superset_node            | npm WARN tarball tarball data for<EMAIL_ADDRESS>(sha512-hLWjpy7EnsDBb0p+Z3B7rPi3GDeRG5ZtiI33kJhTt+ORCd38AbAIjB/9zRIUoeTbE/AVX5ZkU7m6bznsvrf8eQ==) seems to be corrupted.  Trying one more time.
superset_app             | <IP_ADDRESS> - - [21/May/2020 19:22:22] "POST /login/ HTTP/1.1" 302 -
superset_app             | INFO:werkzeug:<IP_ADDRESS> - - [21/May/2020 19:22:22] "POST /login/ HTTP/1.1" 302 -
superset_app             | <IP_ADDRESS> - - [21/May/2020 19:22:22] "GET /login/ HTTP/1.1" 200 -
superset_app             | INFO:werkzeug:<IP_ADDRESS> - - [21/May/2020 19:22:22] "GET /login/ HTTP/1.1" 200 -
superset_app             | <IP_ADDRESS> - - [21/May/2020 19:22:22] "GET<EMAIL_ADDRESS>HTTP/1.1" 404 -
superset_app             | INFO:werkzeug:<IP_ADDRESS> - - [21/May/2020 19:22:22] "GET<EMAIL_ADDRESS>HTTP/1.1" 404 -
superset_app             | <IP_ADDRESS> - - [21/May/2020 19:22:26] "GET /health HTTP/1.1" 200 -
superset_app             | INFO:werkzeug:<IP_ADDRESS> - - [21/May/2020 19:22:26] "GET /health HTTP/1.1" 200 -
superset_node            | npm WARN tar ENOENT: no such file or directory, open '/app/superset-frontend/node_modules/.staging/brace-3d4c8edd/mode/perl.js'
superset_node            | npm WARN tarball tarball data for<EMAIL_ADDRESS>(sha512-YYVO8jUSf6+SakL4AJmx9Jc7zAZhkJQ+WhdtX3VQe5PJdCOX6/ybY4x1vk+h94ePnjRn6uml68+QxTAJneUpvA==) seems to be corrupted. Trying one more time.
superset_node            | npm WARN tar ENOENT: no such file or directory, open '/app/superset-frontend/node_modules/.staging/moment-c2e9eafd/min/moment-with-locales.min.js'
superset_node            | npm WARN The package @types/classnames is included as both a dev and production dependency.
superset_node            | npm WARN The package @types/react-json-tree is included as both a dev and production dependency.
superset_node            |
superset_node            | npm ERR! code EAI_AGAIN
superset_node            | npm ERR! errno EAI_AGAIN
superset_node            | npm ERR! request to https://registry.npmjs.org/h3-js/-/h3-js-3.6.3.tgz failed, reason: getaddrinfo EAI_AGAIN registry.npmjs.org registry.npmjs.org:443
superset_node            | npm WARN tar ENOENT: no such file or directory, open '/app/superset-frontend/node_modules/.staging/core-js-9ca519da/client/library.js'
superset_node            | npm WARN tar ENOENT: no such file or directory, open '/app/superset-frontend/node_modules/.staging/datamaps-264ee032/src/js/data/hrv.topo.json'
superset_node            | npm WARN tar ENOENT: no such file or directory, open '/app/superset-frontend/node_modules/.staging/core-js-pure-60e0faf5/proposals/using-statement.js'
superset_node            | npm WARN tar ENOENT: no such file or directory, open '/app/superset-frontend/node_modules/.staging/core-js-pure-60e0faf5/es/array/values.js'
superset_node            | npm WARN tar ENOENT: no such file or directory, open '/app/superset-frontend/node_modules/.staging/core-js-pure-60e0faf5/es/array/virtual/values.js'
superset_node            | npm WARN tar ENOENT: no such file or directory, open '/app/superset-frontend/node_modules/.staging/core-js-pure-60e0faf5/es/instance/values.js'
superset_node            | npm WARN tar ENOENT: no such file or directory, open '/app/superset-frontend/node_modules/.staging/core-js-pure-60e0faf5/es/object/values.js'
superset_node            | npm WARN tar ENOENT: no such file or directory, open '/app/superset-frontend/node_modules/.staging/core-js-pure-60e0faf5/es/typed-array/values.js'
superset_node            | npm WARN tar ENOENT: no such file or directory, open '/app/superset-frontend/node_modules/.staging/core-js-pure-60e0faf5/features/array/values.js'
superset_node            | npm WARN tar ENOENT: no such file or directory, open '/app/superset-frontend/node_modules/.staging/core-js-pure-60e0faf5/features/array/virtual/values.js'
superset_node            | npm WARN tar ENOENT: no such file or directory, open '/app/superset-frontend/node_modules/.staging/core-js-pure-60e0faf5/features/instance/values.js'
superset_node            | npm WARN tar ENOENT: no such file or directory, open '/app/superset-frontend/node_modules/.staging/core-js-pure-60e0faf5/features/object/values.js'
superset_node            | npm WARN tar ENOENT: no such file or directory, open '/app/superset-frontend/node_modules/.staging/core-js-pure-60e0faf5/features/typed-array/values.js'
superset_node            | npm WARN tar ENOENT: no such file or directory, open '/app/superset-frontend/node_modules/.staging/core-js-pure-60e0faf5/stable/array/values.js'
superset_node            | npm WARN tar ENOENT: no such file or directory, open '/app/superset-frontend/node_modules/.staging/core-js-pure-60e0faf5/stable/array/virtual/values.js'
superset_node            | npm WARN tar ENOENT: no such file or directory, open '/app/superset-frontend/node_modules/.staging/core-js-pure-60e0faf5/stable/instance/values.js'
superset_node            | npm WARN tar ENOENT: no such file or directory, open '/app/superset-frontend/node_modules/.staging/core-js-pure-60e0faf5/stable/object/values.js'
superset_node            | npm WARN tar ENOENT: no such file or directory, open '/app/superset-frontend/node_modules/.staging/core-js-pure-60e0faf5/stable/typed-array/values.js'
superset_node            | npm WARN tar ENOENT: no such file or directory, open '/app/superset-frontend/node_modules/.staging/core-js-pure-60e0faf5/modules/web.dom-collections.for-each.js'
superset_node            | npm WARN tar ENOENT: no such file or directory, open '/app/superset-frontend/node_modules/.staging/core-js-pure-60e0faf5/modules/web.dom-collections.iterator.js'
superset_node            | npm WARN tar ENOENT: no such file or directory, open '/app/superset-frontend/node_modules/.staging/core-js-pure-60e0faf5/modules/web.immediate.js'
superset_node            | npm WARN tar ENOENT: no such file or directory, open '/app/superset-frontend/node_modules/.staging/core-js-pure-60e0faf5/modules/web.queue-microtask.js'
superset_node            | npm WARN tar ENOENT: no such file or directory, open '/app/superset-frontend/node_modules/.staging/core-js-pure-60e0faf5/modules/web.timers.js'
superset_node            | npm WARN tar ENOENT: no such file or directory, open '/app/superset-frontend/node_modules/.staging/core-js-pure-60e0faf5/modules/web.url-search-params.js'
superset_node            | npm WARN tar ENOENT: no such file or directory, open '/app/superset-frontend/node_modules/.staging/core-js-pure-60e0faf5/modules/web.url.js'
superset_node            | npm WARN tar ENOENT: no such file or directory, open '/app/superset-frontend/node_modules/.staging/babel-polyfill-0be08a64/dist/polyfill.min.js'
superset_app             | <IP_ADDRESS> - - [21/May/2020 19:22:52] "POST /login/ HTTP/1.1" 302 -
superset_app             | INFO:werkzeug:<IP_ADDRESS> - - [21/May/2020 19:22:52] "POST /login/ HTTP/1.1" 302 -
superset_app             | <IP_ADDRESS> - - [21/May/2020 19:22:52] "GET /login/ HTTP/1.1" 200 -
superset_app             | INFO:werkzeug:<IP_ADDRESS> - - [21/May/2020 19:22:52] "GET /login/ HTTP/1.1" 200 -
superset_app             | <IP_ADDRESS> - - [21/May/2020 19:22:52] "GET<EMAIL_ADDRESS>HTTP/1.1" 404 -
superset_app             | INFO:werkzeug:<IP_ADDRESS> - - [21/May/2020 19:22:52] "GET<EMAIL_ADDRESS>HTTP/1.1" 404 -
superset_app             | <IP_ADDRESS> - - [21/May/2020 19:22:57] "GET /health HTTP/1.1" 200 -
superset_app             | INFO:werkzeug:<IP_ADDRESS> - - [21/May/2020 19:22:57] "GET /health HTTP/1.1" 200 -
superset_app             | <IP_ADDRESS> - - [21/May/2020 19:22:58] "POST /login/ HTTP/1.1" 302 -
superset_app             | INFO:werkzeug:<IP_ADDRESS> - - [21/May/2020 19:22:58] "POST /login/ HTTP/1.1" 302 -
superset_app             | <IP_ADDRESS> - - [21/May/2020 19:22:58] "GET /login/ HTTP/1.1" 200 -
superset_app             | INFO:werkzeug:<IP_ADDRESS> - - [21/May/2020 19:22:58] "GET /login/ HTTP/1.1" 200 -
superset_app             | <IP_ADDRESS> - - [21/May/2020 19:22:58] "GET<EMAIL_ADDRESS>HTTP/1.1" 404 -
superset_app             | INFO:werkzeug:<IP_ADDRESS> - - [21/May/2020 19:22:58] "GET<EMAIL_ADDRESS>HTTP/1.1" 404 -
superset_node            | npm WARN tar ENOENT: no such file or directory, open '/app/superset-frontend/node_modules/.staging/ansi-colors-2f753b4b/symbols.js'
superset_node            |
superset_node            | npm ERR!
Action item: in the installation guide page, it needs to be added to install these packages. Specially because it doesn't directly get displayed in logs when trying to follow the current version of documentation here: https://superset.incubator.apache.org/installation.html#start-with-docker

@smirs Hi, sorry how did you install node and vpm?..I'm having the same problem, I notice that there are several containers

in my case I'm getting several logs indicating an issue with some npm dependencies

Facing same issue with docker-compose up

@craig-rueda , who has most context on our docker / docker-compose

Could be related to the node modules volume? Try re-pulling master and re-up.

same problem +1

Try leaving it to run for about 5 - 10 minutes. I had the same issue but leaving it webpack started printing messages and eventually I was able to load it when webpack finished but took about 5 minutes locally

Thanks for reaching out, guys. We're aware of this lagginess when it comes
to the node container and are actively looking at it. Thanks again, and
stay tuned for updates!
-Craig
On Thu, Jul 16, 2020 at 8:03 AM Robert Brown<EMAIL_ADDRESS>wrote:

Try leaving it to run for about 5 - 10 minutes. I had the same issue but
leaving it webpack started printing messages and eventually I was able to
load it when webpack finished but took about 5 minutes locally
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/apache/incubator-superset/issues/9880#issuecomment-659471654,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AATZTWYWTHUEZJRPHMEVG5DR34JD7ANCNFSM4NHHRZUA
.

I'm having this issue as well.  This is my log.
superset_app             | INFO:werkzeug:<IP_ADDRESS> - - [12/Aug/2020 22:09:09] "GET / HTTP/1.1" 302 -
superset_app             | <IP_ADDRESS> - - [12/Aug/2020 22:09:09] "GET /superset/welcome HTTP/1.1" 200 -
superset_app             | INFO:werkzeug:<IP_ADDRESS> - - [12/Aug/2020 22:09:09] "GET /superset/welcome HTTP/1.1" 200 -
superset_app             | <IP_ADDRESS> - - [12/Aug/2020 22:09:09] "GET /static/assets/images/loading.gif HTTP/1.1" 404 -
superset_app             | INFO:werkzeug:<IP_ADDRESS> - - [12/Aug/2020 22:09:09] "GET /static/assets/images/loading.gif HTTP/1.1" 404 -
superset_app             | <IP_ADDRESS> - - [12/Aug/2020 22:09:20] "GET /health HTTP/1.1" 200 -
superset_app             | INFO:werkzeug:<IP_ADDRESS> - - [12/Aug/2020 22:09:20] "GET /health HTTP/1.1" 200 -

Same here!. The problem was the amount of memory allocated to Docker. I increased ram and cpu and solved.

Same here

I have experienced similar issue when trying to setup superset for the first time. Hopefully this could be resolved so we can lower the barrier for people who is excited about superset's potential

I also experienced the same issue when trying to deploy on my MacBook Pro. Tried a few things, no luck yet. Will keep trying. Any suggetions?

same on fresh install ubuntu 18.04 LTS vm. install via github.
 I see that all of the Flask-served requests are returning 200, whereas the static assets aren't built.

I have experienced similar issue when trying to setup superset for the first time. Hopefully this could be resolved so we can lower the barrier for people who is excited about superset's potential

May I ask how did you solve the problem?

same problem +1 again

same problem

I solved it by:

Bumping Docker memory to 16GB (not 100% sure if helped since I already had 8gb there)
Running docker-compose up and wait 10 minutes until Webpack kicked off the build

Worked for me now after reinstalling Docker, increasing Docker memory to 16GB, running "docker-compose up" and waiting for about 15 minutes after superset-frontend node_module build complete.

Thanks for the updates. I will bump up docker to 16GB and wait.

Wait around 5 minutes until you see this in terminal.
######################################################################

Init Step 4/4 [Complete] -- Loading examples

######################################################################

Then you're all set. But it may use large amount of ram so you might increase docker ram to 16GB like others said.

Facing similar issue on Ubuntu 20.04 LTS via WSL 2 on Docker for Windows with WSL 2 Integration

We've noticed in the past that building the javascript bundles is pretty io intensive and that docker in some context doesn't do io as well. OSx used to be pretty bad and things could degrade while in container-in-container mode. Unclear how Docker on Windows does with this. Unclear if that's the part of the issue or not, but something to keep in mind.

I experienced the same kind of behaviour, restarted my docker machine vbox image with 4Gb memory and 2 cpus and left it for an hour or so. The static assets now appear to be present.

I've got exactly same blank page. From my case, i've also seen following errors from stage superset_init:
superset_init            | urllib.error.URLError: <urlopen error [Errno 99] Cannot assign requested address>

Facing similar issue on Ubuntu 20.04 LTS via WSL 2 on Docker for Windows with WSL 2 Integration

and.... fixed itself after a few hours.. of idling

That is amazing, i followed you and it worked after one hour waiting for some web packages installations. I've also used WSL2.

I had the same issue, took around 7m for webpack to finish
superset_node            | <s> [webpack.Progress] 100%
superset_node            | No type errors found
superset_node            | Version: typescript 3.8.3
superset_node            | Time: 412075ms
superset_node            |
superset_node            |    8278 modules

My guess is that given that the build operation is super io-heavy and that virtualization, depending the platform you're on (say docker on windows, or docker-in-docker, or whatever) can make certain io operations sluggish, and really slow down the build process. Looks like the node_modules/ folder contains a quarter million files (!)
$ find superset-frontend/node_modules/ | wc -l
  240901

It would be good to have official docker images from the project that don't require you to compile. Any newcomer who wants to try superset has to do all this compilation process to run the project.
For anyone who wants to give it a try, here is a link to unofficial docker images:

https://github.com/amancevice/docker-superset
https://hub.docker.com/r/amancevice/superset/

It would be good to have official docker images from the project that don't require you to compile. Any newcomer who wants to try superset has to do all this compilation process to run the project.
For anyone who wants to give it a try, here is a link to unofficial docker images:

https://github.com/amancevice/docker-superset
https://hub.docker.com/r/amancevice/superset/

I concur. This should be table stakes IMO.

I think I have the same problem I also get ENOENT: no such file or directory, open '/app/superset-frontend/node_modules/.staging/... errors during the npm build.
I am using Docker Desktop <IP_ADDRESS> on Mac. I gave Docker 16GB RAM, 4GB Swap, 6 CPUs and more then enough disk space so I hope missing resources is not the problem.
This is the logfile:
superset.log

We have switched over to using prebuilt images hosted on docker hub, see https://github.com/apache/incubator-superset/pull/11707
@korridor can you try pulling the latest master and running docker-compose again?

@nytai Thanks now it's working! I was using the master instead of the master-dev tag for some reason.

I have run into this issue, and it worked after installing the latest NPM and node.js.

I found myself forced to enter to superset-frontend and run npm run build

After increasing Docker memory limits I recreated superset-node service via:
docker-compose kill superset-node
docker-compose rm superset-node
docker-compose up -d superset-node

superset-node was able to build assets in this case.

After increasing Docker memory limits I recreated superset-node service via:
docker-compose kill superset-node
docker-compose rm superset-node
docker-compose up -d superset-node

superset-node was able to build assets in this case.

Got the same issue here when I following the official installation guide https://superset.apache.org/docs/installation/installing-superset-using-docker-compose.
It's pretty disappointing that having this issue in release/stable versions (I've tried both 1.0.0 and 1.0.1).

I found running docker stats in a separate terminal window helpful for monitoring whether the superset_node image was "busy"

@wahyd4 docker-compose is a dev environment set up. If you'd like to run an official version you can use the pypi distribution, ie pip install apache-superset or you can use one of the official release docker images, https://hub.docker.com/layers/apache/superset/1.0.1/images/sha256-8accc0a4bc0af3293e64c6dfe78bec16de8525ebdc5d649eca21d77fa3e73da8?context=explore
This of course means you will have to provide your own metadata database, redis instance, and you will have to configure workers properly in another container. Up to you which set "issues" you're more comfortable dealing with

@nytai Thanks for the clarification and explanation. It does make sense to me. But I suspect many people didn't expect that we have to compile resources when running app via docker-compose.  It would be great if we can have some more detailed documentation about running production ready superset app via docker, docker-compose or Kubernetes.
I do acknowledge there is some doc from official website https://superset.apache.org/docs/installation/installing-superset-from-scratch about install superset via helm but it doesn't provide any introduction about helm variables and how to config them.

The published docker containers already include the compiled resources. docker-compose volume mounts the repo and sets things up for development purposes, hence why the compilation step is necessary. We could add a version of docker-compose without volume mounts for quickly testing the app out, however that should ideally not be used in prod. The helm chart is also a great way to set up the app quickly for testing but it’s also not ideal for large scale prod deployments as it relies on containerized instances of redis and Postgres. It also expects knowledge of helm charts (most config usually happens in values.yaml)
As far as prod deployments, there are so many ways to run a flask app, celery app, celery beat app, provide a database, redis instance, etc. that documenting each would be a huge task. We could point to other resources for deploying flask/celery apps though

@nytai I agree with you that docker-compose shouldn't be used for production ideally, and it provides a super fast way for user to test superset by 1 command.
But I wouldn't agree with your thoughts on Helm, we don't have to using the embedded Database and Redis to run the application, and I wouldn't think people do that way to setup production clusters. That's why we provide option to use external database and redis instances in Helm, isn't it? If a user don't know too much about helm then use the quick start command, otherwise check the README to customize. Definitely there are lots of ways to run superset, but given we have provided helm as an option, so hope we can provide some more information about it which is similar to the archived superset helm chart https://github.com/helm/charts/tree/master/stable/superset
Anyway, thanks for the explanation, I have tried the apache/superset docker image locally, it works great.

@wahyd4 Actually, that deperacted helm chart got moved into the superset repo, so all that documentation still applied. If you're up for it, you could open a PR to include that readme in thehelm/superset directory. Some changes will be required to reflect the new paths, but it should be fairly straight forward.
Additionally, you've inspired me to cook up a docker-compose file explicitly for testing out superset and not developing, https://github.com/apache/superset/pull/13143

Thanks for the updates. I will bump up docker to 16GB and wait.

Did this solved your issue? Because I am also facing this currently..

same problem +1 again
And I can not see the way to solve this issue in version 3.0.3


SDK7: Removing one UiEntity can damage other remaining UiEntities

Background is provided in a comment.
Scene demonstrating the fix is included.
Steps to reproduce

Clone the demo scene at Cloning the scene in https://gitlab.com/dcl-tech/demo-uis
Be sure that the useGeneralizedCompositing variable near the top of DemoUs.tsx is set to true
Run it in preview
If you don’t see the 2D Uis appear automatically, click on the green box to open them
.   // You may have to click a second time, see issue #936
// Note the placement of the white Ui_2 text inside the minimized Ui_2
Click the CLOSE button on Ui_1
// Expected: it closes, Ui_2 is unaffected
// Actual:  Ui_2 background turns white, and its “Ui_2” text moves down the screen.
// you can reset the scene by clicking on the black box if it is present
// Optionally before or after clicking the CLOSE button on Ui2,
// you can click the button on Ui_2 to maximize Ui_2 and see a second button.
// That button, when pressed, will present a temporary announcement
// for a few seconds.

This is ugly.  I request a fix soon.

Background: I needed a way to manage multiple unrelated 2D Uis being added and removed independently.
Why?

Because one can only call ReactEcsRenderer once in a scene,
Because my scenes sometimes need more than one 2D Ui
Because those Uis may be completely unrelated, in their own reusable modules, for example
a. BuilderHUD
b. CinemaControls
c. AdmissionTicket
d. Dance button
e. Stage Manager Controls
This scene demonstrates such a mechanism,
but also demonstrates some issues with SDK7 2D UIs, which I’ll report in decentraland/sdk,
including interfering with (cross-talking with) the properties of other UiEntities.

Details of this particular issue:
Removing one UiEntity and its children can affect the color and positions of another remaining UiEntity


Load network with from_mat then run PreComp

Not a but, need to run preprocess_transition_probs first. Maybe one thing to do is to automatically run this if not yet run?


[Automation] Generate Fluent Lite from azurelargeinstance#package-2023-07-20-preview

[Automation] Generate Fluent Lite from azurelargeinstance#package-2023-07-20-preview

/azp run prepare-pipelines

/azp run java - largeinstance - ci

API change check
APIView has identified API level changes in this PR and created following API reviews.
com.azure.resourcemanager:azure-resourcemanager-largeinstance


altair_admin_common.min.js:2 Uncaught TypeError: $(...).velocity is not a function

at Object.card_expand (altair_admin_common.min.js:2)
at Object.init (altair_admin_common.min.js:2)
at HTMLDocument. (altair_admin_common.min.js:2)
at c (common.min.js:2)
at Object.fireWith [as resolveWith] (common.min.js:2)
at Function.ready (common.min.js:2)
at HTMLDocument.s (common.min.js:1)

@ishaqshaik222 this looks like an invalid import of the MaterializeCSS library, which needs velocity as part of its dependencies. Usually it's a problem with jQuery imports. Please check that you've followed the installation instructions and that you have only a single dependency of jQuery.

No answer. Closing.


New LinearMouse update messed up my Mac trackpad

OS
macOS 14.5 (Build 23F79)
LinearMouse
v0.10.0
Describe the bug
After installing new LM update, my track pad operates opposite of the way it used to; if I click with 1 finger, it responds as if I used 2 fingers. And if I use 2 fingers, it responds as if I clicked with 1 finger. The settings are the same as they were before installing the update. It's basically acting like it the mouse buttons were reversed. I checked the mouse settings and they are not reversed.
To reproduce
Install LM and then the trackpad works like the buttons are opposite
Expected behavior
I would like the trackpad to work correctly. It worked fine with LM installed, until I did the latest update.
Anything else?
No response

Hey @cfd323, thanks for feedback!
Could you upload your configuration file?

Sorry, new to Macbook/Mac OS. How do i do that?
On Thu, Jul 4, 2024 at 9:55 AM Jiahao Lu @.***> wrote:

Hey @cfd323 https://github.com/cfd323, thanks for feedback!
Could you upload your configuration file?
—
Reply to this email directly, view it on GitHub
https://github.com/linearmouse/linearmouse/issues/760#issuecomment-2209059878,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BJUPQH2JBEM74U4Q5DHD7O3ZKVH6LAVCNFSM6AAAAABKKHJ5U6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBZGA2TSOBXHA
.
You are receiving this because you were mentioned.Message ID:
@.***>

No worries! You can find the configuration file by:

Click the LinearMouse icon on the menu bar.
Click Config -> Reveal in Finder

Also, please check if the "Switch primary and secondary buttons" option is enabled by mistake for trackpad:


Add missing rbac to access keystone CRs

Currently horizon operator requires access to keystone CRs to obtain url of keystone endpoint. This adds missing RBAC to allow that access.

Note to self: Because horizon does not require its own user it does not require access to keystoneservices CR.


Issue installing via go install.

go install github.com/atterpac/refresh/cmd/refesh@latest

go: downloading github.com/atterpac/refresh v0.1.0
go: github.com/atterpac/refresh/cmd/refesh@latest: module github.com/atterpac/refresh@latest found (v0.1.0), but does not contain package github.com/atterpac/refresh/cmd/refesh

fixed by docs typo.


Calling convention specifier incorrect for C#'s C data interface

Describe the bug, including details regarding any error messages, version, and platform.
We specify the calling convention with:
internal delegate* unmanaged
#if !NET5_0_OR_GREATER
            [Stdcall]
#endif
            <CArrowArrayStream*, CArrowSchema*, int> get_schema;

Here is my understanding:

These functions are implemented in Arrow-C++  When we build Arrow-C++ we do not specify any calling convention (e.g. /Gd, /Gr, /Gv, /Gz) and therefore the default (/Gd) will be used which maps to __cdecl.
In the above, if we are < .NET 5.0 then it specifies [Stdcall], which is wrong
In the above, if we are >= .NET 5.0 then it specifies the default, which will be [Stdcall] on Windows, which is wrong.

In practice, this doesn't affect us because this only matters on 32-bit machines
Component(s)
C#

CC @teo-tsirpanis @pitrou @CurtHagenlocher @eerhardt for second opinions.  I'm opening this issue so we can isolate this conversation (as it is not terribly important unless we know someone is using this kind of system) and proceed on the other PR (which has other, legitimate, fixes)

I can quickly change it to cdecl, before you merge the PR.


Offline Usage

Is there any planned release to allow offline usage? It would be a nice feature, e.g. for buildung a mart home application and I guess the most users don't want to allow continues voice recognition.

annyang relies on the browser's Speech Recognition engine. This engine does all of its work "in the cloud". So unfortunately, that would be quite impossible without replicating an entire speech recognition engine inside annyang.


VSBuild task ignores DacApplicationName and SqlTargetName properties

I have sqlproj with DacApplicationName and SqlTargetName set up to "CDB_Acquiring". But VSBuild task ignore it and use project name as output for .dacpac:
Project "D:\a\1\s\Acquiring\MySolution.sln" (1) is building "D:\a\1\s\Acquiring\MySolution.DB\MySolution.DB.sqlproj" (7) on node 1 (default targets).
PrepareForBuild:
  Creating directory "bin\Release\".
CoreCompile:
  C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\15.0\Bin\Roslyn\csc.exe /noconfig /nowarn:1701,1702 /nostdlib+ /errorreport:prompt /warn:4 /define:TRACE /highentropyva+ /reference:"C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5.2\mscorlib.dll" /debug:pdbonly /optimize+ /out:obj\Release\MySolution.DB.dll /ruleset:"C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Team Tools\Static Analysis Tools\\Rule Sets\MinimumRecommendedRules.ruleset" /subsystemversion:6.00 /target:library /warnaserror- /utf8output "C:\Users\VssAdministrator\AppData\Local\Temp\.NETFramework,Version=v4.5.2.SqlClrAttributes.cs"
  Using shared compilation with compiler from directory: C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\15.0\Bin\Roslyn
SqlBuild:
  Creating a model to represent the project...
  Loading project references...
  Loading project files...
  Building the project model and resolving object interdependencies...
  Validating the project model...
  Writing model to D:\a\1\s\Acquiring\MySolution.DB\obj\Release\Model.xml...
  Writing create script to MySolution.DB_Create.sql...
CopyFilesToOutputDirectory:
  Copying file from "obj\Release\MySolution.DB.dll" to "bin\Release\MySolution.DB.dll".
  MySolution.DB -> D:\a\1\s\Acquiring\MySolution.DB\bin\Release\MySolution.DB.dll
  Copying file from "obj\Release\MySolution.DB.pdb" to "bin\Release\MySolution.DB.pdb".
SqlPrepareForRun:
  MySolution.DB -> D:\a\1\s\Acquiring\MySolution.DB\bin\Release\MySolution.DB.dacpac

My task is:
- task: VSBuild@1
      inputs:
        msbuildArgs: '/p:IsPackaging=true'
        clean: true
        solution: '$(Build.Repository.Name)\**\*.sln'
        platform: ${{ variables.platform }}
        configuration: ${{ variables.configuration }}

As you can see there is clean: true, but even with clean this doesn't work. I spent huge amount of time for determine the reason, but without success.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 29f86c97-f534-50ad-bfb1-a2cf78c7af94
Version Independent ID: acea40e3-512b-4d9a-9389-71b8b24327be
Content: Visual Studio Build build and release task - Azure Pipelines
Content Source: docs/pipelines/tasks/build/visual-studio-build.md
Product: devops
Technology: devops-cicd-tasks
GitHub Login: @vijayma
Microsoft Alias: vijayma

Problem was with .sqlproj file that missed DacApplicationName and SqlTargetName properties for 'Release' configuration. I had to set up this manually for both configs.


Fix "InvalidBookmark" warning in v2 builds for successful migration to v3

This fix is for docfx v3 migration and it won't break any of your published content pages.
The reason why we do this change is, v2 builds should use '#top' for [Top of page] bookmark.

Docs Build status updates of commit 5a4820b:
:warning: Validation status: warnings

File
Status
Preview URL
Details

globalization/input/font-support.md
:warning:Warning
View
Details

globalization/input/font-support.md

[Warning] Missing attribute: author. Add the current author's GitHub ID.
[Warning] Missing attribute: title. Add a title string to show in search engine results.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

You could probably also delete these links (and the "On this Page" section) since the document platform already generates the table on the right hand side https://docs.microsoft.com/en-ca/globalization/input/font-support

Looks like this got replaced by #120

closing as fixed in #120


generate spreadsheets for datasets in "metadata valid"

We need to generate spreadsheets for datasets in "metadata valid".
Those are supposed to be the ones for which we bumped the schema version, which caused them to go back to Metadata valid state.
Suggested course of action:

verify that the dataset does not have any other change since its last export but the schema upgrade
re-run graph validation
re-export (which will generate the spreadsheet)

This command will find and export several graph valid submissions.
export INGEST_TOKEN=<get from browser>
export INGEST_API=https://api.ingest.archive.data.humancellatlas.org
export PAGE_SIZE=1
curl -s "$INGEST_API/submissionEnvelopes/search/findBySubmissionState?submissionState=GRAPH_VALID&size=$PAGE_SIZE" \
  | jq '._embedded.submissionEnvelopes[]._links.self.href+"/submissionEvent"' \
  | xargs -t curl -H "Authorization: Bearer $INGEST_TOKEN" -XPUT --data-raw '["Export_Metadata"]' -H 'Content-Type: application/json'

See #885 for info about the datasets and the spreadsheet generation task.

I created a spreadsheet to track the progress.

14 projects will make it into Release 30.

Summary of export problems:

graph validation failure

lookup submission uuid in monitoring dashboard
navigate to submission page in ui
read error
fix
reset status to GraphValid

file_descriptor schema validation error

change content type to application/gzip; dcp-type=data
update file size by reading from s3 url, or if the file is missing from azul
reset status to GraphValid

When looking for n2, I found out another issue that I think I can resolve quite easily: some datasets were exported with "export" rather than "export metadata" flags.
The spreadsheet was not working for me, so I decided to retrieve things through the API:
all_submissions = api.get_all('https://api.ingest.archive.data.humancellatlas.org/submissionEnvelopes/', 'submissionEnvelopes')
all_submissions = list(api.get_all('https://api.ingest.archive.data.humancellatlas.org/submissionEnvelopes/', 'submissionEnvelopes'))
submitted = [s for s in all_submissions if s['submissionState'] == 'Submitted']

From these, a list of all the files these submissions contain was obtained:
submission_to_files = {}
for i, s in enumerate(submitted):
    submission_to_files[s['uuid']['uuid']] = list(api.get_all(s['_links']['files']['href'], 'files'))
    print(f"Submission {i}")

These is the list of all the files associated with the submission UUID. However, we know this specific issue arises from files with no “fileContentType” filled, so with the next bit of code, I identified which submissions suffer from this issue.
submission_to_files_no_fileContentType = {}
for submission_uuid, files in submission_to_files.items():
    no_filetype_files = [file for file in files if not file['fileContentType']]
    submission_to_files_no_fileContentType[submission_uuid] = no_filetype_files

Only four submissions suffer from this issue:
'c81f7d54-a27f-4212-a6df-88dde947f7cc', 'fce97270-fce0-4744-8a4e-a93d95521852', 'bf3116e5-1af1-46c2-8bbd-44dac49d1e7f', 'dca729d5-e66c-476b-a646-632c4499820b’
It’s also the first ones in the list, so my best guess is all of these are DCP1 datasets since the API tends to order submissions by submissionDate
I think the rest of the submissions got stuck due to trying to export data, so I will take the rest of the submission uuids and try to export only metadata. I have subtracted the rest of the submissions by doing a simple set substraction:
print(set(submission_to_files.keys()) - set(submission_to_files_no_fileContentType.keys()))
{'5d0c7b2b-24d3-456f-9c13-e28c12029cae', '13ad7484-b2cb-4e4f-b276-38a4135516c6', '3864f954-4707-42d7-8782-735a8b6c83a4', 'cb156730-90b0-4b77-944c-bfc263204c61', '4310b292-921c-4e87-a74b-5b8e3ce48c3d', 'de0c62d7-bf76-4620-80e1-49ea5edd85f9', '737d0394-862b-4d9a-ad44-9e09cd82766f', 'a5a37ee0-b19b-4de5-9903-b731bb69c9cf', '8fdc1e36-31d7-4525-85b1-808ebd54e8c1', '96e500d8-11e9-4d25-a2e5-817e0628199f', 'ba4fbccf-455a-4ec9-ad46-e346bca7ba95', '0ddb157b-beab-4721-b8fe-53f04a2328ae', 'c1e4ba7a-b131-4c4c-9986-35b1eed5ad94', '4f40bcbf-6c56-422c-ac8a-3f162f818595', '51bc39b1-2347-4307-800e-85615b278314', 'cb989b6e-bab9-432c-895d-ea8d2aa1ebab', '378455be-3938-4713-abfa-7584e1f63942', '29829bc7-c156-4fd3-a3fc-466f4586019c', '007aa0ef-8642-4ff9-833d-ad23a4a6d194', 'a961c8aa-5d05-4519-8e40-a8f5a3f60435', 'b18808af-73ce-4275-b153-719b16ffe52d', '7f398780-f962-4adc-8fad-a5fcc68bd3f8', 'fe536fd5-3343-462a-8026-42b2fccb5367', 'e3569524-66b0-46e0-bbee-08e469d60fd4', 'd596ce16-39c1-40f9-83b1-2a00b8dd82eb'}

And I will use an adaptation of the script above to send these submissions to export, after setting up the submissions to graph valid:
submission_uuids_to_graphValid = {uuid: submission_to_files[uuid] for uuid in set(submission_to_files.keys()) - set(submission_to_files_no_fileContentType.keys())}
for submission_uuid in submission_uuids_to_graphValid:
    submission = api.get_submission_by_uuid(submission_uuid)
    url = api.get_link_from_resource(submission, 'commitGraphValid')
    r = api.put(url, json={})

Ingest api objects throw an error if the response is not ok, so if this succeeds we assume all submissions have been put to graph valid. However, we will check just in case with one submission: https://api.ingest.archive.data.humancellatlas.org/submissionEnvelopes/60d5c1ebd20b7e03a5b3807f
As we can see, it's in graph valid. I will now save the submissionEvent links and use a modified version of the script in the body of the ticket to push the submissions
all_submissionEvents = []
for submission_uuid in submission_uuids_to_graphValid.keys():
    submission = api.get_submission_by_uuid(submission_uuid)
    url = api.get_link_from_resource(submission, 'self')
    all_submissionEvents.append(f"{url}/submissionEvent")
with open('links_to_submit.txt', 'w') as f:
    f.write('\n'.join(all_submissionEvents))

And then, in bash:
export INGEST_TOKEN=<get from browser>
cat links_to_submit.txt | xargs -t curl -H "Authorization: Bearer $INGEST_TOKEN" -XPUT --data-raw '["Export_Metadata"]' -H 'Content-Type: application/json'

Tomorrow I'll check the 25 submissions I've been testing, but they should be ok

One submission was exported, another one from the 25 we decided to move to exported because it already had the spreadsheet.
For the other 23, I was going to take an approach of "chunk submit" them, but even with only 3 exports, I am still getting an error:
{"log":"sqlite3.OperationalError: no such table: responses\n","stream":"stderr","time":"2023-08-30T14:16:23.946541993Z"}
I am observing that that error happens to specific export jobs, and there is no recovery from there
I unfortunately don't have enough knowledge to fix this issue. All I can see is that it seems related to when the crawler tries to crawl the graph for some processes and then the ingest-api object is trying to get the entities. It seems there is some kind of issue with requests_cache
The 23 submissions are:
5d0c7b2b-24d3-456f-9c13-e28c12029cae
13ad7484-b2cb-4e4f-b276-38a4135516c6
cb156730-90b0-4b77-944c-bfc263204c61
4310b292-921c-4e87-a74b-5b8e3ce48c3d
de0c62d7-bf76-4620-80e1-49ea5edd85f9
737d0394-862b-4d9a-ad44-9e09cd82766f
a5a37ee0-b19b-4de5-9903-b731bb69c9cf
8fdc1e36-31d7-4525-85b1-808ebd54e8c1
96e500d8-11e9-4d25-a2e5-817e0628199f
ba4fbccf-455a-4ec9-ad46-e346bca7ba95
0ddb157b-beab-4721-b8fe-53f04a2328ae
c1e4ba7a-b131-4c4c-9986-35b1eed5ad94
4f40bcbf-6c56-422c-ac8a-3f162f818595
51bc39b1-2347-4307-800e-85615b278314
378455be-3938-4713-abfa-7584e1f63942
29829bc7-c156-4fd3-a3fc-466f4586019c
007aa0ef-8642-4ff9-833d-ad23a4a6d194
a961c8aa-5d05-4519-8e40-a8f5a3f60435
b18808af-73ce-4275-b153-719b16ffe52d
7f398780-f962-4adc-8fad-a5fcc68bd3f8
fe536fd5-3343-462a-8026-42b2fccb5367
e3569524-66b0-46e0-bbee-08e469d60fd4
d596ce16-39c1-40f9-83b1-2a00b8dd82eb

The other 4, I will fix the files with this script I worked on some time ago https://github.com/ebi-ait/hca-ebi-dev-team/blob/master/scripts/fill_dcp1_file_metadata/fill_dcp1_metadata.py and try to re-submit once the issue is fixed


The way we provide feedback to learners on quizzes: changing behaviour

Hi Michel,
The faculty members are suggesting for quizzes that in stead learners have to press a button to get feedbacks after they submitted a quiz, the feedback should show up automatically.
Basically, can we get rid of the button show feedbacks and learners should have access to the feedbacks automatically after they submitted.
Best,
Ella

Hi, as said during the meeting, this had just been done today!
Cheers


podman-compose error "pod already exists" after cold reboot

/kind bug
Description
Had been using podman-compose successfully for 1month when laptop froze and I had to cold reboot. After that no success initiating.
Exactly same configuration on desktop computer has no problems.
Have tried:

full reinstall of podman & podman-compose
rm -Rf ~/.local/share/container
podman rm -avf (needed manual input b/c there was a "infra container". After this checked if any instance of pods, volumes or images => none

Steps to reproduce the issue:

podman-compose up in directory having docker-compose.yml

Describe the results you received:
Traceback (most recent call last):
  File "/home/david/.local/bin/podman-compose", line 10, in <module>
    sys.exit(main())
  File "/home/david/.local/lib/python3.7/site-packages/podman_compose.py", line 1093, in main
    podman_compose.run()
  File "/home/david/.local/lib/python3.7/site-packages/podman_compose.py", line 625, in run
    cmd(self, args)
  File "/home/david/.local/lib/python3.7/site-packages/podman_compose.py", line 782, in wrapped
    return func(*args, **kw)
  File "/home/david/.local/lib/python3.7/site-packages/podman_compose.py", line 898, in compose_up
    detached=args.detach, podman_command=podman_command)
  File "/home/david/.local/lib/python3.7/site-packages/podman_compose.py", line 457, in container_to_args
    mount_args = mount_desc_to_args(compose, volume, cnt['_service'], cnt['name'])
  File "/home/david/.local/lib/python3.7/site-packages/podman_compose.py", line 386, in mount_desc_to_args
    mount_desc = mount_dict_vol_to_bind(compose, fix_mount_dict(mount_desc, proj_name, srv_name))
  File "/home/david/.local/lib/python3.7/site-packages/podman_compose.py", line 366, in mount_dict_vol_to_bind
    src = json.loads(out)[0]["mountPoint"]
KeyError: 'mountPoint'

Describe the results you expected:
working services
Additional information you deem important (e.g. issue happens only occasionally):
no
Output of podman version:
podman pod create --name=dev-database --share net
125
podman volume inspect dev-database_mysql || podman volume create dev-database_mysql
Version:            1.6.2
RemoteAPI Version:  1
Go Version:         go1.13.1
OS/Arch:            linux/amd64

Output of podman info --debug:
debug:
  compiler: gc
  git commit: ""
  go version: go1.13.1
  podman version: 1.6.2
host:
  BuildahVersion: 1.11.3
  CgroupVersion: v2
  Conmon:
    package: conmon-2.0.2-1.fc31.x86_64
    path: /usr/bin/conmon
    version: 'conmon version 2.0.2, commit: 186a550ba0866ce799d74006dab97969a2107979'
  Distribution:
    distribution: fedora
    version: "31"
  IDMappings:
    gidmap:
    - container_id: 0
      host_id: 1000
      size: 1
    - container_id: 1
      host_id: 100000
      size: 65536
    uidmap:
    - container_id: 0
      host_id: 1000
      size: 1
    - container_id: 1
      host_id: 100000
      size: 65536
  MemFree:<PHONE_NUMBER>
  MemTotal:<PHONE_NUMBER>8
  OCIRuntime:
    name: crun
    package: crun-0.10.6-1.fc31.x86_64
    path: /usr/bin/crun
    version: |-
      crun version 0.10.6
      spec: 1.0.0
      +SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +YAJL
  SwapFree:<PHONE_NUMBER>
  SwapTotal:<PHONE_NUMBER>
  arch: amd64
  cpus: 8
  eventlogger: journald
  hostname: localhost.localdomain
  kernel: 5.3.11-300.fc31.x86_64
  os: linux
  rootless: true
  slirp4netns:
    Executable: /usr/bin/slirp4netns
    Package: slirp4netns-0.4.0-20.1.dev.gitbbd6f25.fc31.x86_64
    Version: |-
      slirp4netns version 0.4.0-beta.3+dev
      commit: bbd6f25c70d5db2a1cd3bfb0416a8db99a75ed7e
  uptime: 20m 51.37s
registries:
  blocked: null
  insecure: null
  search:
  - docker.io
  - registry.fedoraproject.org
  - registry.access.redhat.com
  - registry.centos.org
  - quay.io
store:
  ConfigFile: /home/david/.config/containers/storage.conf
  ContainerStore:
    number: 3
  GraphDriverName: overlay
  GraphOptions:
    overlay.mount_program:
      Executable: /usr/bin/fuse-overlayfs
      Package: fuse-overlayfs-0.7-1.fc31.x86_64
      Version: |-
        fusermount3 version: 3.6.2
        fuse-overlayfs: version 0.7
        FUSE library version 3.6.2
        using FUSE kernel interface version 7.29
  GraphRoot: /home/david/.local/share/containers/storage
  GraphStatus:
    Backing Filesystem: extfs
    Native Overlay Diff: "false"
    Supports d_type: "true"
    Using metacopy: "false"
  ImageStore:
    number: 4
  RunRoot: /run/user/1000
  VolumePath: /home/david/.local/share/containers/storage/volumes

Package info (e.g. output of rpm -q podman or apt list podman):
podman-1.6.2-2.fc31.x86_64

Additional environment details (AWS, VirtualBox, physical, etc.):
Also notice

podman volume ls

DRIVER   VOLUME NAME
local    dev-database_mysql

podman volume prune

WARNING! This will remove all volumes not used by at least one container.
Are you sure you want to continue? [y/N] y
Error: error freeing lock for volume dev-database_mysql: no such file or directory

isnt this a podman-compose issue which is not part of this repo?

I honestly don't know... the errors come from the script yes but I'm guessing there's some locked entity in cache which libpod cannot modify.

Also notice

podman volume ls

DRIVER   VOLUME NAME
local    dev-database_mysql

podman volume prune

WARNING! This will remove all volumes not used by at least one container.
Are you sure you want to continue? [y/N] y
Error: error freeing lock for volume dev-database_mysql: no such file or directory

This is a podman-compose issue. I had the same problem. I fixed it with a newer version of podman-compose from devel branch of upstream project.
pip3 install https://github.com/containers/podman-compose/archive/devel.tar.gz

Can confirm that solves the error above!
Still some issues that weren't previously but I think config related.

Yes, definitely solved. THX!


Any method to search if an exploit exists for a specific vulnerability?

I tried searching for a specific CVE but shodan doesn't return any results


SIMD#83 - Allow conflicting entries on replay side

Problem
Currently self-conflicting batches are not allowed on the replay side whereas SIMD#83 requires this support.
Summary of Changes

Introduced a flag in every batch to distinguish between self-conflicting and disjoint batches
Bypass rebatching for self-conflicting batches

Related to:
#1025

This PR is currently WIP.
It's complete in terms of code changes but we are currently working on its testcases and benchmarking. Pushed in a little advance to get your feedback on it.

Incorporated unit tests for rebatching logic in rebatch_and_execute_batches to ensure self-conflicting batches are not rebatched. Also added a unit test for schedule_batches_for_execution (new flow) for self-conflicting batches and it seems to handle this case.
After SVM changes (to allow self-conflicting batches), further tests can be added to test execution of self-conflicting  batches in process_batches.