Fail to fetch customer profile

Hi team,
I'm facing an interesting edge case while trying to retrieve Amazon Connect customer profiles in a React App. This only happens if I log-out and then log back in into my app. Worth mentioning that we're using Cognito as IDP service for Amazon Connect as described in the video call escalation repo.
We're logging out as instructed in the amazon connect docs.
 <button
          className={styles.logoutButton}
          onClick={() => {
            // First signout of Amazon Connect
            fetch(connectLogoutUrl, {
              credentials: "include",
              mode: "no-cors",
            })
              .then(() => {
                const eventBus = connect.core.getEventBus()
                eventBus.trigger(connect.EventType.TERMINATE)
              })
              .then(() => cognitoSignOut())
              .then(() => clearConnectTimestamp())
              .catch((err) => logError(err))
          }}
        >
        Log out
        </button>

It looks like there is an fac error around the time of my request to the customer profile API but the connect streams apparently treats this error as a normal occurrence.
This is how I instantiate the customer profile client:
const customerProfileInstance = `https://<connectInstanceAlias>.my.connect.aws`

useEffect(() => {
    const iframeContainer = ref.current
    setIsCustomerProfileLoading(true)

    const log = connect.getLog()
    log.setEchoLevel(connect.LogLevel.WARN)
    log.setLogLevel(connect.LogLevel.WARN)

    connect.core.initCCP(iframeContainer as HTMLElement, initCCPOptions)

    const customerProfileClient = new connect.CustomerProfilesClient(
      customerProfileInstance,
    )
    // store the customer profile client in state (jotai atom) to be reused across the app
    setCustomerProfileClient(customerProfileClient)

    connect.core.onInitialized(() => {
      setCCPMode({ current: "INITIALIZED" })
    })

   // agent and contact event handlers below
  // ...
  }, [<dependencies>])

This is the hook that I run to fetch the customer profile:
useEffect(() => {
    if (!customerProfileId) {
      return
    }

    const throwErrorOnDelay = new Promise((_resolve, reject) => {
      setTimeout(
        reject,
        10 * 1000,
        "Delayed response from customer profile API",
      )
    })

    const storeCustomerProfile = async (customerProfileId: string) => {
      try {
        console.log("1. fetching profiles --->")

        const profiles = await Promise.race([
          customerProfileClient.searchProfiles({
            DomainName: config.customerProfilesDomain,
            KeyName: "_profileId",
            Values: [customerProfileId],
            AdditionalSearchKeys: phoneNumber
              ? [
                  {
                    KeyName: "_phone",
                    Values: [phoneNumber],
                  },
                ]
              : undefined,
            LogicalOperator: "OR",
          }),
          throwErrorOnDelay,
        ])
        console.log("2. fetched profiles --->", profiles)

        const {
          data: { Items },
        } = profiles

       // store first profile in the array in state
      } catch (err) {
        console.log("3. error --->", err)
      }
    }

    storeCustomerProfile(customerProfileId)
  }, [
    customerProfileId,
    phoneNumber,
    customerProfileClient,
  ])

I've included a screencast of the exact edge case i'm facing. You can consult it here https://www.loom.com/share/0d236d17144e47e5b1cbb54824bac15f?sid=c58f4c50-76d5-4448-a9d0-7280c399efd0
Below i'll paste the export of my console window.  As you can see below the Promise.race ends with throwing an error 10 seconds after not receiving a response for the customer profile search request. Any ideas on how I could fix or mitigate this edge case? As mentioned, I only noticed it after logging out from Amazon connect and then logging back into Amazon Connect.
1.  Ignoring...
connect-streams-min.e0f9cd8f.js:1 [2023-11-22T07:09:40.464Z] [INFO] [c89a1e17-4aa6-4a1f-b731-a4a4bdbbbd69]: clientApp is detected ENABLED. Now trying Connecting to ClientApp...
connect-streams-min.e0f9cd8f.js:1 [2023-11-22T07:09:40.464Z] [INFO] [c89a1e17-4aa6-4a1f-b731-a4a4bdbbbd69]: Agent state has changed from oldState init to newState available
connect-streams-min.e0f9cd8f.js:1 [2023-11-22T07:09:40.466Z] [INFO] [c89a1e17-4aa6-4a1f-b731-a4a4bdbbbd69]: After INIT, agent has ["c8908bf7-17d8-4e48-95c4-611b729940e9"] in Snapshot, and [] contacts in IDB
connect-streams-min.e0f9cd8f.js:1 [2023-11-22T07:09:40.466Z] [INFO] [c89a1e17-4aa6-4a1f-b731-a4a4bdbbbd69]: No contact found to end after init
connect-streams-min.e0f9cd8f.js:1 [2023-11-22T07:09:40.482Z] [INFO] [c89a1e17-4aa6-4a1f-b731-a4a4bdbbbd69]: Ringtone is ready to play:
connect-streams-min.e0f9cd8f.js:1 [2023-11-22T07:09:40.483Z] [INFO] [c89a1e17-4aa6-4a1f-b731-a4a4bdbbbd69]: Ringtone is ready to play:
connect-streams-min.e0f9cd8f.js:1 [2023-11-22T07:09:40.485Z] [INFO] [c89a1e17-4aa6-4a1f-b731-a4a4bdbbbd69]: Ringtone is ready to play:
connect-streams-min.e0f9cd8f.js:1 [2023-11-22T07:09:40.568Z] [INFO] [c89a1e17-4aa6-4a1f-b731-a4a4bdbbbd69]: [Device Settings] Call updateDeviceList with getUserMedia
connect-streams-min.e0f9cd8f.js:1 [2023-11-22T07:09:40.656Z] [INFO] [c89a1e17-4aa6-4a1f-b731-a4a4bdbbbd69]: [Audio Device Settings] New Audio Input DeviceList is updated to [{"deviceId":"default","kind":"audioinput","label":"Default - MacBook Pro Microphone (Built-in)","groupId":"c76f3d08f0b92091b5c7e9d875c5c67ee38ae5d68b628972c043f34054ceb932"},{"deviceId":"048e85be582177ee28ee60309df262ba3252e5360d33d6b24dcd55c21fa4006b","kind":"audioinput","label":"MacBook Pro Microphone (Built-in)","groupId":"c76f3d08f0b92091b5c7e9d875c5c67ee38ae5d68b628972c043f34054ceb932"}]
connect-streams-min.e0f9cd8f.js:1 [2023-11-22T07:09:40.656Z] [INFO] [c89a1e17-4aa6-4a1f-b731-a4a4bdbbbd69]: [Audio Device Settings] New Audio Output DeviceList is updated to [{"deviceId":"default","kind":"audiooutput","label":"Default - MacBook Pro Speakers (Built-in)","groupId":"c76f3d08f0b92091b5c7e9d875c5c67ee38ae5d68b628972c043f34054ceb932"},{"deviceId":"babd4aff814220c54c3b86002ffac0113d9a9c53179bfb41744ab8d45d6dd9d5","kind":"audiooutput","label":"MacBook Pro Speakers (Built-in)","groupId":"c76f3d08f0b92091b5c7e9d875c5c67ee38ae5d68b628972c043f34054ceb932"}]
connect-streams-min.e0f9cd8f.js:1 [2023-11-22T07:09:40.656Z] [INFO] [c89a1e17-4aa6-4a1f-b731-a4a4bdbbbd69]: [Audio Device Settings] CCPUI calls Streams API setSpeakerDevice with default
connect-streams-min.e0f9cd8f.js:1 [2023-11-22T07:09:40.656Z] [INFO] [c89a1e17-4aa6-4a1f-b731-a4a4bdbbbd69]: [Audio Device Settings] CCPUI calls Streams API setRingerDevice with default
connect-streams-min.e0f9cd8f.js:1 [2023-11-22T07:09:40.657Z] [INFO] [c89a1e17-4aa6-4a1f-b731-a4a4bdbbbd69]: [Audio Device Settings] Attempting to set speaker device default
connect-streams-min.e0f9cd8f.js:1 [2023-11-22T07:09:40.657Z] [INFO] [c89a1e17-4aa6-4a1f-b731-a4a4bdbbbd69]: [Audio Device Settings] Attempting to set ringer device default
connect-streams-min.e0f9cd8f.js:1 [2023-11-22T07:09:40.658Z] [INFO] [c89a1e17-4aa6-4a1f-b731-a4a4bdbbbd69]: [Audio Device Settings] ringtoneType voice successfully set to deviceid default
connect-streams-min.e0f9cd8f.js:1 [2023-11-22T07:09:40.658Z] [INFO] [c89a1e17-4aa6-4a1f-b731-a4a4bdbbbd69]: [Audio Device Settings] ringtoneType chat successfully set to deviceid default
connect-streams-min.e0f9cd8f.js:1 [2023-11-22T07:09:40.658Z] [INFO] [c89a1e17-4aa6-4a1f-b731-a4a4bdbbbd69]: [Audio Device Settings] ringtoneType task successfully set to deviceid default
connect-streams-min.e0f9cd8f.js:1 [2023-11-22T07:09:40.658Z] [INFO] [c89a1e17-4aa6-4a1f-b731-a4a4bdbbbd69]: [Audio Device Settings] ringtoneType queue_callback successfully set to deviceid default
connect-streams-min.e0f9cd8f.js:1 [2023-11-22T07:09:40.658Z] [INFO] [c89a1e17-4aa6-4a1f-b731-a4a4bdbbbd69]: [Audio Device Settings] Speaker device default successfully set to speaker audio element
connect-streams-min.e0f9cd8f.js:1 [2023-11-22T07:09:39.688Z] [INFO] [c89a1e17-4aa6-4a1f-b731-a4a4bdbbbd69]: Creating a new Websocket connection for CCP
connect-streams-min.e0f9cd8f.js:1 [2023-11-22T07:09:39.689Z] [INFO] [c89a1e17-4aa6-4a1f-b731-a4a4bdbbbd69]: SharedWorker initializing with snapshot delay time of 0ms
connect-streams-min.e0f9cd8f.js:1 [2023-11-22T07:09:39.690Z] [INFO] [c89a1e17-4aa6-4a1f-b731-a4a4bdbbbd69]: ADVANCED_LOG AMZ_WEB_SOCKET_MANAGER::Initializing Websocket Manager Failure callback registered
connect-streams-min.e0f9cd8f.js:1 [2023-11-22T07:09:39.690Z] [INFO] [c89a1e17-4aa6-4a1f-b731-a4a4bdbbbd69]: ADVANCED_LOG AMZ_WEB_SOCKET_MANAGER::Websocket connection open callback registered
connect-streams-min.e0f9cd8f.js:1 [2023-11-22T07:09:39.690Z] [INFO] [c89a1e17-4aa6-4a1f-b731-a4a4bdbbbd69]: ADVANCED_LOG AMZ_WEB_SOCKET_MANAGER::Websocket connection close callback registered
connect-streams-min.e0f9cd8f.js:1 [2023-11-22T07:09:39.690Z] [INFO] [c89a1e17-4aa6-4a1f-b731-a4a4bdbbbd69]: ADVANCED_LOG AMZ_WEB_SOCKET_MANAGER::Websocket connection gain callback registered
connect-streams-min.e0f9cd8f.js:1 [2023-11-22T07:09:39.690Z] [INFO] [c89a1e17-4aa6-4a1f-b731-a4a4bdbbbd69]: ADVANCED_LOG AMZ_WEB_SOCKET_MANAGER::Websocket connection lost callback registered
connect-streams-min.e0f9cd8f.js:1 [2023-11-22T07:09:39.690Z] [INFO] [c89a1e17-4aa6-4a1f-b731-a4a4bdbbbd69]: ADVANCED_LOG AMZ_WEB_SOCKET_MANAGER::Websocket subscription failure callback registered
connect-streams-min.e0f9cd8f.js:1 [2023-11-22T07:09:39.691Z] [INFO] [c89a1e17-4aa6-4a1f-b731-a4a4bdbbbd69]: ADVANCED_LOG AMZ_WEB_SOCKET_MANAGER::Deep Heartbeat is successful. WebSocketManager has received 200 response from aws/ping
connect-streams-min.e0f9cd8f.js:1 [2023-11-22T07:09:39.691Z] [INFO] [c89a1e17-4aa6-4a1f-b731-a4a4bdbbbd69]: ADVANCED_LOG AMZ_WEB_SOCKET_MANAGER::Deep Heartbeat failed. WebSocketManager does not receive 200 response from aws/ping
connect-streams-min.e0f9cd8f.js:1 [2023-11-22T07:09:39.691Z] [INFO] [c89a1e17-4aa6-4a1f-b731-a4a4bdbbbd69]: ADVANCED_LOG AMZ_WEB_SOCKET_MANAGER::Generic topic failed.
connect-streams-min.e0f9cd8f.js:1 [2023-11-22T07:09:39.691Z] [INFO] [c89a1e17-4aa6-4a1f-b731-a4a4bdbbbd69]: ADVANCED_LOG AMZ_WEB_SOCKET_MANAGER::Reset Websocket state
connect-streams-min.e0f9cd8f.js:1 [2023-11-22T07:09:39.691Z] [INFO] [c89a1e17-4aa6-4a1f-b731-a4a4bdbbbd69]: ADVANCED_LOG AMZ_WEB_SOCKET_MANAGER::Fetching new WebSocket connection configuration
connect-streams-min.e0f9cd8f.js:1 [2023-11-22T07:09:39.874Z] [INFO] [c89a1e17-4aa6-4a1f-b731-a4a4bdbbbd69]: getWebSocketUrl succeeded
connect-streams-min.e0f9cd8f.js:1 [2023-11-22T07:09:39.874Z] [INFO] [c89a1e17-4aa6-4a1f-b731-a4a4bdbbbd69]: ADVANCED_LOG AMZ_WEB_SOCKET_MANAGER::Successfully fetched webSocket connection configuration
connect-streams-min.e0f9cd8f.js:1 [2023-11-22T07:09:39.875Z] [INFO] [c89a1e17-4aa6-4a1f-b731-a4a4bdbbbd69]: ADVANCED_LOG AMZ_WEB_SOCKET_MANAGER::Initializing Websocket Manager
connect-streams-min.e0f9cd8f.js:1 [2023-11-22T07:09:39.875Z] [INFO] [c89a1e17-4aa6-4a1f-b731-a4a4bdbbbd69]: Kicking off agent polling
connect-streams-min.e0f9cd8f.js:1 [2023-11-22T07:09:39.876Z] [INFO] [c89a1e17-4aa6-4a1f-b731-a4a4bdbbbd69]: Kicking off config polling
connect-streams-min.e0f9cd8f.js:1 [2023-11-22T07:09:39.876Z] [INFO] [c89a1e17-4aa6-4a1f-b731-a4a4bdbbbd69]: Kicking off auth token polling
connect-streams-min.e0f9cd8f.js:1 [2023-11-22T07:09:40.048Z] [INFO] [c89a1e17-4aa6-4a1f-b731-a4a4bdbbbd69]: ADVANCED_LOG AMZ_WEB_SOCKET_MANAGER::WebSocket connection established!
connect-streams-min.e0f9cd8f.js:1 [2023-11-22T07:09:40.048Z] [INFO] [c89a1e17-4aa6-4a1f-b731-a4a4bdbbbd69]: ADVANCED_LOG AMZ_WEB_SOCKET_MANAGER::Reset Websocket state
connect-streams-min.e0f9cd8f.js:1 [2023-11-22T07:09:39.688Z] [INFO] [c89a1e17-4aa6-4a1f-b731-a4a4bdbbbd69]: Creating a new Websocket connection for CCP
connect-streams-min.e0f9cd8f.js:1 [2023-11-22T07:09:39.689Z] [INFO] [c89a1e17-4aa6-4a1f-b731-a4a4bdbbbd69]: SharedWorker initializing with snapshot delay time of 0ms
connect-streams-min.e0f9cd8f.js:1 [2023-11-22T07:09:39.690Z] [INFO] [c89a1e17-4aa6-4a1f-b731-a4a4bdbbbd69]: ADVANCED_LOG AMZ_WEB_SOCKET_MANAGER::Initializing Websocket Manager Failure callback registered
connect-streams-min.e0f9cd8f.js:1 [2023-11-22T07:09:39.690Z] [INFO] [c89a1e17-4aa6-4a1f-b731-a4a4bdbbbd69]: ADVANCED_LOG AMZ_WEB_SOCKET_MANAGER::Websocket connection open callback registered
connect-streams-min.e0f9cd8f.js:1 [2023-11-22T07:09:39.690Z] [INFO] [c89a1e17-4aa6-4a1f-b731-a4a4bdbbbd69]: ADVANCED_LOG AMZ_WEB_SOCKET_MANAGER::Websocket connection close callback registered
connect-streams-min.e0f9cd8f.js:1 [2023-11-22T07:09:39.690Z] [INFO] [c89a1e17-4aa6-4a1f-b731-a4a4bdbbbd69]: ADVANCED_LOG AMZ_WEB_SOCKET_MANAGER::Websocket connection gain callback registered
connect-streams-min.e0f9cd8f.js:1 [2023-11-22T07:09:39.690Z] [INFO] [c89a1e17-4aa6-4a1f-b731-a4a4bdbbbd69]: ADVANCED_LOG AMZ_WEB_SOCKET_MANAGER::Websocket connection lost callback registered
connect-streams-min.e0f9cd8f.js:1 [2023-11-22T07:09:39.690Z] [INFO] [c89a1e17-4aa6-4a1f-b731-a4a4bdbbbd69]: ADVANCED_LOG AMZ_WEB_SOCKET_MANAGER::Websocket subscription failure callback registered
connect-streams-min.e0f9cd8f.js:1 [2023-11-22T07:09:39.691Z] [INFO] [c89a1e17-4aa6-4a1f-b731-a4a4bdbbbd69]: ADVANCED_LOG AMZ_WEB_SOCKET_MANAGER::Deep Heartbeat is successful. WebSocketManager has received 200 response from aws/ping
connect-streams-min.e0f9cd8f.js:1 [2023-11-22T07:09:39.691Z] [INFO] [c89a1e17-4aa6-4a1f-b731-a4a4bdbbbd69]: ADVANCED_LOG AMZ_WEB_SOCKET_MANAGER::Deep Heartbeat failed. WebSocketManager does not receive 200 response from aws/ping
connect-streams-min.e0f9cd8f.js:1 [2023-11-22T07:09:39.691Z] [INFO] [c89a1e17-4aa6-4a1f-b731-a4a4bdbbbd69]: ADVANCED_LOG AMZ_WEB_SOCKET_MANAGER::Generic topic failed.
connect-streams-min.e0f9cd8f.js:1 [2023-11-22T07:09:39.691Z] [INFO] [c89a1e17-4aa6-4a1f-b731-a4a4bdbbbd69]: ADVANCED_LOG AMZ_WEB_SOCKET_MANAGER::Reset Websocket state
connect-streams-min.e0f9cd8f.js:1 [2023-11-22T07:09:39.691Z] [INFO] [c89a1e17-4aa6-4a1f-b731-a4a4bdbbbd69]: ADVANCED_LOG AMZ_WEB_SOCKET_MANAGER::Fetching new WebSocket connection configuration
connect-streams-min.e0f9cd8f.js:1 [2023-11-22T07:09:39.874Z] [INFO] [c89a1e17-4aa6-4a1f-b731-a4a4bdbbbd69]: getWebSocketUrl succeeded
connect-streams-min.e0f9cd8f.js:1 [2023-11-22T07:09:39.874Z] [INFO] [c89a1e17-4aa6-4a1f-b731-a4a4bdbbbd69]: ADVANCED_LOG AMZ_WEB_SOCKET_MANAGER::Successfully fetched webSocket connection configuration
connect-streams-min.e0f9cd8f.js:1 [2023-11-22T07:09:39.875Z] [INFO] [c89a1e17-4aa6-4a1f-b731-a4a4bdbbbd69]: ADVANCED_LOG AMZ_WEB_SOCKET_MANAGER::Initializing Websocket Manager
connect-streams-min.e0f9cd8f.js:1 [2023-11-22T07:09:39.875Z] [INFO] [c89a1e17-4aa6-4a1f-b731-a4a4bdbbbd69]: Kicking off agent polling
connect-streams-min.e0f9cd8f.js:1 [2023-11-22T07:09:39.876Z] [INFO] [c89a1e17-4aa6-4a1f-b731-a4a4bdbbbd69]: Kicking off config polling
connect-streams-min.e0f9cd8f.js:1 [2023-11-22T07:09:39.876Z] [INFO] [c89a1e17-4aa6-4a1f-b731-a4a4bdbbbd69]: Kicking off auth token polling
connect-streams-min.e0f9cd8f.js:1 [2023-11-22T07:09:40.048Z] [INFO] [c89a1e17-4aa6-4a1f-b731-a4a4bdbbbd69]: ADVANCED_LOG AMZ_WEB_SOCKET_MANAGER::WebSocket connection established!
connect-streams-min.e0f9cd8f.js:1 [2023-11-22T07:09:40.048Z] [INFO] [c89a1e17-4aa6-4a1f-b731-a4a4bdbbbd69]: ADVANCED_LOG AMZ_WEB_SOCKET_MANAGER::Reset Websocket state
connect-streams-min.e0f9cd8f.js:1 [2023-11-22T07:09:40.806Z] [INFO] [c89a1e17-4aa6-4a1f-b731-a4a4bdbbbd69]: [Audio Device Settings] New Audio Input DeviceList is updated to [{"deviceId":"default","kind":"audioinput","label":"Default - MacBook Pro Microphone (Built-in)","groupId":"c76f3d08f0b92091b5c7e9d875c5c67ee38ae5d68b628972c043f34054ceb932"},{"deviceId":"048e85be582177ee28ee60309df262ba3252e5360d33d6b24dcd55c21fa4006b","kind":"audioinput","label":"MacBook Pro Microphone (Built-in)","groupId":"c76f3d08f0b92091b5c7e9d875c5c67ee38ae5d68b628972c043f34054ceb932"}]
connect-streams-min.e0f9cd8f.js:1 [2023-11-22T07:09:40.807Z] [INFO] [c89a1e17-4aa6-4a1f-b731-a4a4bdbbbd69]: [Audio Device Settings] New Audio Output DeviceList is updated to [{"deviceId":"default","kind":"audiooutput","label":"Default - MacBook Pro Speakers (Built-in)","groupId":"c76f3d08f0b92091b5c7e9d875c5c67ee38ae5d68b628972c043f34054ceb932"},{"deviceId":"babd4aff814220c54c3b86002ffac0113d9a9c53179bfb41744ab8d45d6dd9d5","kind":"audiooutput","label":"MacBook Pro Speakers (Built-in)","groupId":"c76f3d08f0b92091b5c7e9d875c5c67ee38ae5d68b628972c043f34054ceb932"}]
connect-streams-min.e0f9cd8f.js:1 [2023-11-22T07:09:40.807Z] [INFO] [c89a1e17-4aa6-4a1f-b731-a4a4bdbbbd69]: [Audio Device Settings] CCPUI calls Streams API setSpeakerDevice with default
connect-streams-min.e0f9cd8f.js:1 [2023-11-22T07:09:40.807Z] [INFO] [c89a1e17-4aa6-4a1f-b731-a4a4bdbbbd69]: [Audio Device Settings] CCPUI calls Streams API setRingerDevice with default
connect-streams-min.e0f9cd8f.js:1 [2023-11-22T07:09:40.807Z] [INFO] [c89a1e17-4aa6-4a1f-b731-a4a4bdbbbd69]: [Audio Device Settings] Attempting to set speaker device default
connect-streams-min.e0f9cd8f.js:1 [2023-11-22T07:09:40.808Z] [INFO] [c89a1e17-4aa6-4a1f-b731-a4a4bdbbbd69]: [Audio Device Settings] Speaker device default successfully set to speaker audio element
connect-streams-min.e0f9cd8f.js:1 [2023-11-22T07:09:40.808Z] [INFO] [c89a1e17-4aa6-4a1f-b731-a4a4bdbbbd69]: [Audio Device Settings] Attempting to set ringer device default
connect-streams-min.e0f9cd8f.js:1 [2023-11-22T07:09:40.808Z] [INFO] [c89a1e17-4aa6-4a1f-b731-a4a4bdbbbd69]: [Audio Device Settings] ringtoneType voice successfully set to deviceid default
connect-streams-min.e0f9cd8f.js:1 [2023-11-22T07:09:40.808Z] [INFO] [c89a1e17-4aa6-4a1f-b731-a4a4bdbbbd69]: [Audio Device Settings] ringtoneType chat successfully set to deviceid default
connect-streams-min.e0f9cd8f.js:1 [2023-11-22T07:09:40.808Z] [INFO] [c89a1e17-4aa6-4a1f-b731-a4a4bdbbbd69]: [Audio Device Settings] ringtoneType task successfully set to deviceid default
connect-streams-min.e0f9cd8f.js:1 [2023-11-22T07:09:40.808Z] [INFO] [c89a1e17-4aa6-4a1f-b731-a4a4bdbbbd69]: [Audio Device Settings] ringtoneType queue_callback successfully set to deviceid default
hook.ts:208 3. error ---> Delayed response from customer profile API
error.ts:20 Error: "Delayed response from customer profile API"
    at toError (error.ts:73:12)
    at logError (error.ts:19:23)
    at storeCustomerProfile (hook.ts:211:9)
overrideMethod @ console.js:213
logError @ error.ts:20
storeCustomerProfile @ hook.ts:211
await in storeCustomerProfile (async)
(anonymous) @ hook.ts:215
commitHookEffectListMount @ react-dom.development.js:23150
commitPassiveMountOnFiber @ react-dom.development.js:24926
commitPassiveMountEffects_complete @ react-dom.development.js:24891
commitPassiveMountEffects_begin @ react-dom.development.js:24878
commitPassiveMountEffects @ react-dom.development.js:24866
flushPassiveEffectsImpl @ react-dom.development.js:27039
flushPassiveEffects @ react-dom.development.js:26984
(anonymous) @ react-dom.development.js:26769
workLoop @ scheduler.development.js:266
flushWork @ scheduler.development.js:239
performWorkUntilDeadline @ scheduler.development.js:533
Show 12 more frames
Show less
connect-streams-min.e0f9cd8f.js:1 [2023-11-22T07:10:06.937Z] [INFO] [c89a1e17-4aa6-4a1f-b731-a4a4bdbbbd69]:  Sending check media stream event, is local media stream active: false

Hey @vtrofin could you send HAR file or some network information to help us debug this one. I'll try to replicate this issue locally on codesandbox.
If you get rid of the the race does the API ever return?
My one concern with the implementation is that you are mounting the connect client inside a hook and setting to a useState variable and that it is not fully mounted when the API is called.
You may want to immediately invoke the client setup and store it in the window or something. Trying to mount it in a useEffect may run into some issues.

@vtrofin  we worked on an example to help mitigate this here
For now, by using the onAgent callback, you can re-initialize the CustomerProfilesClient on login which should prevent this issue.
I will add a feature request to the amazon-connect-streams library to re-initailize the Customer Profiles ifame on log out and log in.

@greysonevins thank you very much for your response and for taking the time to investigate this. I'll point a few of the implementation decisions below, but it's probably that the client is not properly initialized in my implementation. I'll re-check the client initialization in my codebase.

Initializing the connect ccp client + customer profile client:
Our app has both private routes and public routes where the login page is obviously a public route.  I decided to initialize the ccp client in the private routes, after I retrieve the amazon connect credentials. As mentioned before, we have an auth flow based on the video-call-escalation example, where we use AWS Cognito as IDP and then use the Cognito access token to retrieve the connect credentials.

But the difference is that only after retrieving the Connect credentials I initialize the ccp client and the customer profile client, in the private route. The reason for this choice was that at the time I was unsure whether the ccp client can be properly initiated and refreshed without having the credentials first.

I noticed the edge case happens the first time I try to login (so basically at this point there is no ccp client instantiated because I have no cognito and connect credentials). I'll show this in a short screencast, where basically i refresh the browser login page just to make sure the ccp client is not initiated - in the public login route.
https://www.loom.com/share/6cdcd94c30ca49a8993441221a6acdff?sid=e013c5cf-03a6-4309-b85d-8f22a0aa4bd5

I'll provide a HAR file to the support team. I'm also wondering whether it's better to just instantiate the ccp client once for the entire app and let it manage the refresh once credentials are available.

The API never returns if i remove the race and I instantiate the customer profile like this

useEffect(() => {

 connect.core.initCCP(iframeContainer as HTMLElement, initCCPOptions)

    const customerProfileClient = new connect.CustomerProfilesClient(
      customerProfileInstance,
    )

    connect.core.onInitialized(() => {
      setCCPMode({ current: "INITIALIZED" })
    })

}, [<dependencies>])

However, if I try using the onInitialized event on the ccp client to instantiate the customer profile client, then I receive a meaningful error about the client not being ready when fetching the customer profile.
useEffect() => {
   connect.core.initCCP(iframeContainer as HTMLElement, initCCPOptions)

    connect.core.onInitialized(() => {
      setCCPMode({ current: "INITIALIZED" })

      // attempt to initiate the customer profile client
      const customerProfileClient = new connect.CustomerProfilesClient(
        customerProfileInstance,
      )

    })

}, [<dependencies>])

The error I receive when trying to fetch the customer profile is below

error.ts:20 Error: {"status":500,"statusText":"Client not ready","data":{}}
    at toError (error.ts:73:12)
    at logError (error.ts:19:23)
    at storeCustomerProfile (hook.ts:212:9)
overrideMethod @ console.js:213
logError @ error.ts:20
storeCustomerProfile @ hook.ts:212
await in storeCustomerProfile (async)
(anonymous) @ hook.ts:222
commitHookEffectListMount @ react-dom.development.js:23150
commitPassiveMountOnFiber @ react-dom.development.js:24926
commitPassiveMountEffects_complete @ react-dom.development.js:24891
commitPassiveMountEffects_begin @ react-dom.development.js:24878
commitPassiveMountEffects @ react-dom.development.js:24866
flushPassiveEffectsImpl @ react-dom.development.js:27039
flushPassiveEffects @ react-dom.development.js:26984
(anonymous) @ react-dom.development.js:26769
workLoop @ scheduler.development.js:266
flushWork @ scheduler.development.js:239
performWorkUntilDeadline @ scheduler.development.js:533
Show 12 more frames
Show less

Again, thank you very much for investigating this issue.

@greysonevins thank you for providing me with the example code.

For now, by using the onAgent callback, you can re-initialize the CustomerProfilesClient on login which should prevent this issue.

If I use your approach of searching customer profiles with a click event there is no problem, i get a proper response from the API even when I set the customer profile in state. But in my codebase i must fetch the customer profile with an useEffect hook, every time a new contact is pushed to the agent. This is the main reason i'm getting this error when i log-out and log-in again. And it only happens for that first contact, because the customer profile client is not yet ready.
Is there any way of knowing when the customer profile client is ready so I only attempt to query after that? I guess as an alternative I could make a loop and retry when I get this error.

I'll provide a HAR file to the support team.

I have just shared this on the associated AWS support case

In the end I've made my own check for the client to be ready and only make a query once it is ready.
If it helps anyone, here's my approach:
Initialize the customer profile client only after the ccp iframe is initialized
useEffect(() => {

  connect.core.initCCP(iframeContainer as HTMLElement, initCCPOptions)

  connect.core.onInitialized(() => {
    setCCPMode({ current: "INITIALIZED" })

    // Check whether client is ready and if not, initiate it
    isClientReady()
      .then((isReady) => {
        if (!isReady) {
          initiateCustomerProfileClient()
        }
      })
      .catch((err) => {
        logError(err)
      })
  })

}, [<dependencies>])

Set up the customer profiles client in Context. Below is the hook called in my Context Provider which retrieves the client and the helper methods to query the client
const useCustomerProfileClientHook = () => {

  const customerProfileInstance = `https://<connect-instance-alias>.my.connect.aws`
  const [client, setClient] = useState<unknown>(null)
  const isClientReadyRef = useRef<boolean>(false)

  const initiateClient = (): void => {
    const customerProfileClient = new connect.CustomerProfilesClient(
      customerProfileInstance,
    )

    setClient(() => customerProfileClient)
  }

  const sleep = (ms: number): Promise<void> =>
    new Promise((resolve) => setTimeout(resolve, ms))

  const throwErrorOnDelay = (delay: number) =>
    new Promise((_, reject) => {
      setTimeout(reject, delay, "delayed-api-response")
    })

  const isClientReady = async (): Promise<boolean> => {
    if (isNullish(client)) {
      return false
    }

    if (isClientReadyRef.current) {
      return true
    }

    try {
      const queryOptions = {
        DomainName: <customer-profiles-domain>,
        KeyName: "_phone",
        Values: ["1111"],
      }

      const response = await Promise.race([
        client.searchProfiles(queryOptions),
        throwErrorOnDelay(5 * 1000),
      ])

      if (response?.status === 200) {
        isClientReadyRef.current = true
        return true
      }

      return false
    } catch (err) {
      return false
    }
  }

  const searchProfiles = async (options: OptionsType): Promise<unknown> => {
    let i = 0
    const maxI = 4

    while (i < maxI) {
      if (!(await isClientReady())) {
        i++

        if (i === maxI) {
          break
        }

        await sleep(i + 1 * 1000)
        continue
      }

      const profiles = await client.searchProfiles(options)

      const {
        data: { Items },
      } = profiles

      return Items
    }

    throw new Error("client-not-ready")
  }

  return {
    client,
    initiateClient,
    isClientReady,
    searchProfiles,
  }
}

Query the client profile with useEffect on page render
useEffect(() => {
  const storeCustomerProfile = async () => {
    const queryOptions = {
      DomainName: config.customerProfilesDomain,
      KeyName: "_phone",
      Values: phoneNumber ? [phoneNumber] : undefined,
    }

    try {
      const profiles = await searchProfiles(queryOptions)

      // Set profile in state
      setCustomerProfile(() => profiles[0])

    } catch (err) {
      setCustomerProfile(() => null)

    }
  }

  storeCustomerProfile()
}, [<dependencies>])

Thank you very much @greysonevins for the help and for the code suggestions!


How to pick single date

Dear Volkan,
I can know use the "date range picker" to select two date values as date range(from/to) in sample "AdvancedElement".
But I don't know how to pick single date value, is there any sample to pick single date for reference or sample code?
Thanks,
Harry Zhang

'[DateEditor]' is what you're looking for

Thanks @wldkrd1.
[DateEditor] property just code in  ***Row.cs/Form.cs/.Columns.cs.
I want to code it in ****.cshtml. So can you have good idea to implement what I need(To pick a single Date)?
Thanks,
Harry

Why you want insert it in *.cshtml ?
Is not possible for you add a myDateField in your From.cs and add an [DateEditor] attribute over?

If you really need it only in cshtml for any other mvc templating, you can use bootstrap datepicker https://bootstrap-datepicker.readthedocs.io/en/latest/
or the already included http://jqueryui.com/datepicker/
For usage, see its docs.
Best Regards

I got that.
Thanks you edson.
Harry

<input id="SomeID" />
<script>
new Serenity.DateEditor($('#SomeID'));
</script>

Many Thanks Volkan.
Harry


WIP Use Pester v4 assertion operator syntax

PR Summary
Closes #890
Change assertion operators to Pester 4 syntax by pre-pending the dash (-) to Be, Not, Throw, and Match operators (by going through all operators in the documentation of Pester's Should documentation.
PR Checklist
Note: Tick the boxes below that apply to this pull request by putting an x between the square brackets. Please mark anything not applicable to this PR NA.

[x] PR has a meaningful title

[x] Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[ ] NA User facing documentation needed
[x] Change is not breaking
[ ] NA Make sure you've added a new test if existing tests do not effectively test the code changed
[ ] This PR is ready to merge and is not work in progress : Before this gets merged, we should first merge the other regression fix PR 891.

If the PR is work in progress, please add the prefix WIP: to the beginning of the title and remove the prefix when the PR is ready

@JamesWTruher The WMF4 build was fine (except for the currently known issues) but the Visual Studio 2017 has errors like RuntimeException: '-Be' is not a valid Should operator.
I saw that you changed the Pester v4 installation mechanism from cinst to nuget install in your PR. Is it possible that this actually does not work for the Visual Studio 2017 image?


Glide and support library versions updated

Thank you @Yellu . Could you PR into dev branch instead of master?

Thank you @cymcsg, updated PR to dev.

Thanks. If you have some free time, could you help fix the problem in travis-ci which alert this PR check error?

Sure, I will try it.
On Tue, Feb 27, 2018 at 1:30 PM, MarshalChen<EMAIL_ADDRESS>wrote:

Thanks. If you have some free time, could you help fix the problem in
travis-ci which alert this PR check error?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/cymcsg/UltimateRecyclerView/pull/485#issuecomment-368778964,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AL0AI0x0yqRn4nifeJQ_5rEIDZkwhaGvks5tY7YsgaJpZM4SUdAb
.


Remove warnings when an addon can't be registered

These warnings could not be removed, and there isn't really a point in having them.
This also removes the custom exceptions since they're no longer used.

Too bad you didn't wait for my response on this.
I already made changes that made this only show up while in debug mode.
There is a point in having these errors, if a user is has installed a custom addon, and didn't install the required dependency, an error should show up instead of a crash or other problem.
Please revert this change.

Debug mode does sound better than just removing them.


What do you think?
BTY, I really appreciate everything you've done. Thank you very much.

Sure, no problem :)


DSEGOG-137 data channel tree

Description
This PR adds the basic data channel dialogue & the tree view structure and removes the old channel list that was just for dev testing
Here's a gif demoing the new functionality

Testing instructions
Add a set up instructions describing how the reviewer should test the code

[ ] Review code
[ ] Check Actions build
[ ] Review changes to test coverage

Agile board tracking
Closes DSEGOG-137

@kennethnym There is actually a later issue to address this kinda: https://stfc.atlassian.net/browse/DSEGOG-140 - I didn't want to add more stuff to this PR as it's already quite big. That's the reason the checkboxes are rendered at all - I'll probably experiment with different ways of indicating when addressing the later issue - so I'd like this PR review to ignore the checkboxes for non-leaf nodes as this is something to be changed later


Move from Gulp to Webpack?

Still better to use gulp to build webpack components and move/copy and concat files as needed.


Drag slider speed varies based on range

All the sliders currently have a range of 0.0 to 1.0. I need to implement custom ranges for material parameters before I can properly review this.


Model Flags

We're enforcing certain ordering constraints using a single "world" token that gets assigned to a dummy register.  We should be modelling flags which get preassigned to the appropriate flag "registers" for the minizinc model.

Ok, hate is too strong. It is useful and appropriate sometimes. But not for modelling flags.

Yea it's bogus for flags, but I was lazy. And it's good for some other things.
Part of the issue was that we weren't modelling flags in the C semantics, so there was a slight mismatch.
But mostly the lazy.


Create newsletter

Description of the new feature
We want to add a newsletter so to update community members about new events and stuff.

Add a panel in the website 'Newsletter' which will ask the user for their email and register it to a 3rd party provider newsletter
We can use newsletter provider, such as Mailchimp, which has a free plan of 1K monthly emails (use Latina In Tech google account -> ask admin to sign up)

Tech Details

use the following regex for email: ^([a-z][a-z0-9]{1,13}[_.-]?[a-z0-9]{1,13})@((([0-9]{1,3})([.]{1})([0-9]{1,3})([.]{1})([0-9]{1,3})([.]{1})([0-9]{1,3}))|([a-z0-9]{1,10}[-]?[a-z0-9]{1,10}[.]?[a-z0-9-]{1,10}[.]{1}[a-z]{2,4}))$
which is safe as per regex DOS
Try to hide auth token in the source code, perhaps using github secrets

@coluzziandrea I'm playing with https://convertkit.com/
it seems to match our needs

I haven't done any tests yet but you should be able to design your form to allow users to sign up and then integrate into your website as an embedded element.
In this way, we don't need to write any code.
Thoughts? Could we have any block by adopting it?

We can give it a try, @Undermaken!

I'm just wondering if it exists some provider that will allow us to use our HTML, but I couldn't find any until now

I worked with https://github.com/Faire/mjml-react but I discovered that in email/html world there are no standards and a lot of edge cases.
Btw if we keep the email simple, that's a way

@Undermaken should we convert this issue to a discussion until we decide a way?

Absolutely, yes!
I'm not the maximum expert about that and any contribution, it is gold


Finetuning Callback crashes when using DeepSpeed

🐛 Bug
It seems the fine-tuning callback crashes when using DeepSpeed.
    trainer.fit(model, train_dataloaders=train_data, val_dataloaders=val_data)
  File "/usr/local/lib/python3.6/dist-packages/pytorch_lightning/trainer/trainer.py", line 553, in fit
    self._run(model)
  File "/usr/local/lib/python3.6/dist-packages/pytorch_lightning/trainer/trainer.py", line 918, in _run
    self._dispatch()
  File "/usr/local/lib/python3.6/dist-packages/pytorch_lightning/trainer/trainer.py", line 986, in _dispatch
    self.accelerator.start_training(self)
  File "/usr/local/lib/python3.6/dist-packages/pytorch_lightning/accelerators/accelerator.py", line 92, in start_training
    self.training_type_plugin.start_training(trainer)
  File "/usr/local/lib/python3.6/dist-packages/pytorch_lightning/plugins/training_type/training_type_plugin.py", line 161, in
start_training
    self._results = trainer.run_stage()
  File "/usr/local/lib/python3.6/dist-packages/pytorch_lightning/trainer/trainer.py", line 996, in run_stage
    return self._run_train()
  File "/usr/local/lib/python3.6/dist-packages/pytorch_lightning/trainer/trainer.py", line 1045, in _run_train
    self.fit_loop.run()
  File "/usr/local/lib/python3.6/dist-packages/pytorch_lightning/loops/base.py", line 111, in run
    self.advance(*args, **kwargs)
  File "/usr/local/lib/python3.6/dist-packages/pytorch_lightning/loops/fit_loop.py", line 200, in advance
    epoch_output = self.epoch_loop.run(train_dataloader)
  File "/usr/local/lib/python3.6/dist-packages/pytorch_lightning/loops/base.py", line 106, in run
    self.on_run_start(*args, **kwargs)
  File "/usr/local/lib/python3.6/dist-packages/pytorch_lightning/loops/epoch/training_epoch_loop.py", line 106, in on_run_sta$t
    self.trainer.call_hook("on_train_epoch_start")
  File "/usr/local/lib/python3.6/dist-packages/pytorch_lightning/trainer/trainer.py", line 1217, in call_hook
    trainer_hook(*args, **kwargs)
  File "/usr/local/lib/python3.6/dist-packages/pytorch_lightning/trainer/callback_hook.py", line 92, in on_train_epoch_start
    callback.on_train_epoch_start(self, self.lightning_module)
  File "/usr/local/lib/python3.6/dist-packages/pytorch_lightning/callbacks/finetuning.py", line 298, in on_train_epoch_start
    self._store(pl_module, opt_idx, num_param_groups, current_param_groups)
  File "/usr/local/lib/python3.6/dist-packages/pytorch_lightning/callbacks/finetuning.py", line 284, in _store
    current_param_groups, mapping
  File "/usr/local/lib/python3.6/dist-packages/pytorch_lightning/callbacks/finetuning.py", line 270, in __apply_mapping_to_par
am_groups
    group_state["params"] = [mapping[p] for p in g["params"]]
  File "/usr/local/lib/python3.6/dist-packages/pytorch_lightning/callbacks/finetuning.py", line 270, in <listcomp>
    group_state["params"] = [mapping[p] for p in g["params"]]

To Reproduce
import os

import torch
from torch.optim.optimizer import Optimizer
from torch.utils.data import DataLoader, Dataset

from pytorch_lightning import LightningModule, Trainer
from pytorch_lightning.callbacks import BaseFinetuning
from pytorch_lightning.plugins import DeepSpeedPlugin

class NoFreeze(BaseFinetuning):
    def freeze_before_training(self, pl_module: LightningModule) -> None:
        pass

    def finetune_function(
            self,
            pl_module: LightningModule,
            epoch: int,
            optimizer: Optimizer,
            opt_idx: int,
    ) -> None:
        pass

class RandomDataset(Dataset):
    def __init__(self, size, length):
        self.len = length
        self.data = torch.randn(length, size)

    def __getitem__(self, index):
        return self.data[index]

    def __len__(self):
        return self.len

class BoringModel(LightningModule):
    def __init__(self):
        super().__init__()
        self.layer = torch.nn.Linear(32, 2)

    def forward(self, x):
        return self.layer(x)

    def training_step(self, batch, batch_idx):
        loss = self(batch).sum()
        self.log("train_loss", loss)
        return {"loss": loss}

    def validation_step(self, batch, batch_idx):
        loss = self(batch).sum()
        self.log("valid_loss", loss)

    def test_step(self, batch, batch_idx):
        loss = self(batch).sum()
        self.log("test_loss", loss)

    def configure_optimizers(self):
        return torch.optim.SGD(self.layer.parameters(), lr=0.1)

def run():
    train_data = DataLoader(RandomDataset(32, 64), batch_size=2)
    val_data = DataLoader(RandomDataset(32, 64), batch_size=2)
    test_data = DataLoader(RandomDataset(32, 64), batch_size=2)

    model = BoringModel()
    trainer = Trainer(
        default_root_dir=os.getcwd(),
        fast_dev_run=True,
        plugins=DeepSpeedPlugin(stage=1),
        max_epochs=1,
        gpus=1,
        callbacks=[NoFreeze()]
    )
    trainer.fit(model, train_dataloaders=train_data, val_dataloaders=val_data)
    trainer.test(model, dataloaders=test_data)

if __name__ == "__main__":
    run()

Using lightning master.

From what I've seen, DeepSpeed has fused the parameters into a single param group:
Original PL module, showing one tensor for the boring model weight, and one for the bias:
tensor([[ 0.1513,  0.1053, -0.0563,  0.0805, -0.0555, -0.1556,  0.0337, -0.0581,
          0.0009,  0.0853,  0.0200,  0.1608, -0.1339,  0.1547, -0.0764,  0.1591,
         -0.0222,  0.1228, -0.0202,  0.1690, -0.1674, -0.0543, -0.0588,  0.1172,
          0.0959, -0.0224,  0.1467, -0.1188,  0.0766, -0.0192,  0.1700,  0.0861],
        [-0.0568,  0.0934, -0.1023,  0.0189,  0.0486, -0.1434, -0.0976,  0.1766,
         -0.1113,  0.0554,  0.1653,  0.1198, -0.1018, -0.0298,  0.1670,  0.1178,
         -0.1499, -0.0900, -0.0367, -0.0392, -0.0751,  0.1308, -0.1049,  0.0848,
          0.0134,  0.1708,  0.0882,  0.1684, -0.1443, -0.1318, -0.1007,  0.1382]],
       device='cuda:0', requires_grad=True), Parameter containing:
tensor([-0.0080,  0.1159], device='cuda:0', requires_grad=True)]

DeepSpeed optimizer showing both being fused into a single array:
(Pdb) pl_module.trainer.optimizers[0].param_groups
[{'params': [tensor([ 0.1513,  0.1053, -0.0563,  0.0805, -0.0555, -0.1556,  0.0337, -0.0581,
         0.0009,  0.0853,  0.0200,  0.1608, -0.1339,  0.1547, -0.0764,  0.1591,
        -0.0222,  0.1228, -0.0202,  0.1690, -0.1674, -0.0543, -0.0588,  0.1172,
         0.0959, -0.0224,  0.1467, -0.1188,  0.0766, -0.0192,  0.1700,  0.0861,
        -0.0568,  0.0934, -0.1023,  0.0189,  0.0486, -0.1434, -0.0976,  0.1766,
        -0.1113,  0.0554,  0.1653,  0.1198, -0.1018, -0.0298,  0.1670,  0.1178,
        -0.1499, -0.0900, -0.0367, -0.0392, -0.0751,  0.1308, -0.1049,  0.0848,
         0.0134,  0.1708,  0.0882,  0.1684, -0.1443, -0.1318, -0.1007,  0.1382,
        -0.0080,  0.1159], device='cuda:0', requires_grad=True)], 'lr': 0.1, 'momentum': 0, 'dampening': 0, 'weight_decay': 0, 'nesterov': False}]

This makes the below part of the code fail, where we assume that the optimizer param can be used to store some group_state which I'm unsure it's purpose: https://github.com/PyTorchLightning/pytorch-lightning/blob/master/pytorch_lightning/callbacks/finetuning.py#L270
We might be able to modify this piece of the code however unsure how to approach currently. @tchaton let me know if you have any thoughts!

Hey @SeanNaren.
Yes, I definitely didn't look into DeepSpeed support for this feature.
This piece of code is trying storing the params name in the checkpoint for each param groups and restoring them on reload.
I am not sure how we could apply this logic to DeepSpeed. I believe DeepSpeed isn't flexible enough yet for such feature. Ideally, it should virtually fused the tensors to enable flexibility on param groups manipulation.
Best,
T.C


Can't login as root / root as on Mac OS X Yosemite via a fresh brew install influxdb

I was trying to install InfluxDB 0.8.7 on my Mac OS X Yosemite machine via homebrew, as outlined in http://influxdb.com/docs/v0.8/introduction/installation.html

Step 1

brew install influxdb

Step 2

Run influxdb -config=/usr/local/etc/influxdb.conf
Issues:

Logging configuration

On startup, I get an error that the process can't write to the actual folder. After adding the /tmp path, the db starts up without having to use sudo.
I'm using file   = "/tmp/influxdb.log" instead of the standard file   = "influxdb.log" in the influxdb.conf.

Login into the web admin gui

I can't login using the specified root / root credentials (see http://influxdb.com/docs/v0.8/introduction/getting_started.html), I receive a Couldn't authenticate user: Invalid username/password error.

Iam getting in to this issue again. Please have a look at my /usr/local/var/influxdb/raft/ folder

ls -al /usr/local/var/influxdb/raft/
total 24
drwxr--r--  6 viswanath  admin  204 May 29 15:57 .
drwxrwxrwx  6 viswanath  admin  204 May 29 15:57 ..
-rw-------  1 viswanath  admin   28 May 29 15:57 conf
-rw-------  1 viswanath  admin  382 May 29 15:57 log
-rw-r--r--  1 viswanath  admin   15 May 29 15:57 name
drwx------  2 viswanath  admin   68 May 29 15:57 snapshot


Integrate node part of speech back into front end

Was integrated into the node label nodes tab and the node page.


Silo doesn't build with gcc version >= 13

Silo doesn't build with gcc version >= 13. Particularly problematic for MacOS builds but will soon be important on other clusters as gcc versions creep forward (gcc14 is already available).
I've tested with openmpi and mpich.
Fails like this:
 $ cmake --build /Users/spencer/Downloads/mfc/build/staging/silo --target silo --parallel 8 --config Release

[ 12%] Creating directories for 'silo'
[ 25%] Performing download step (git clone) for 'silo'
Cloning into 'silo'...
remote: Enumerating objects: 14264, done.
remote: Counting objects: 100% (2900/2900), done.
remote: Compressing objects: 100% (915/915), done.
remote: Total 14264 (delta 2028), reused 2714 (delta 1951), pack-reused 11364
Receiving objects: 100% (14264/14264), 118.40 MiB | 2.25 MiB/s, done.
Resolving deltas: 100% (11313/11313), done.
HEAD is now at 438477c macOS: Handle deprecated stat64
[ 37%] Performing update step for 'silo'
[ 50%] Performing patch step for 'silo'
No local changes to save
[ 62%] Performing configure step for 'silo'
CMake Warning:
  Ignoring empty string ("") provided on the command line.

-- The CXX compiler identification is GNU 14.1.0
-- The C compiler identification is GNU 14.1.0
-- Checking whether CXX compiler has -isysroot
-- Checking whether CXX compiler has -isysroot - yes
-- Checking whether CXX compiler supports OSX deployment target flag
-- Checking whether CXX compiler supports OSX deployment target flag - yes
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /opt/homebrew/bin/g++-14 - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Checking whether C compiler has -isysroot
-- Checking whether C compiler has -isysroot - yes
-- Checking whether C compiler supports OSX deployment target flag
-- Checking whether C compiler supports OSX deployment target flag - yes
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /opt/homebrew/bin/gcc-14 - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Found HDF5: hdf5-static (found version "1.12.2")
-- Looking for sys/types.h
-- Looking for sys/types.h - found
-- Looking for stdint.h
-- Looking for stdint.h - found
-- Looking for stddef.h
-- Looking for stddef.h - found
-- Check size of off64_t
-- Check size of off64_t - failed
-- Looking for dlfcn.h
-- Looking for dlfcn.h - found
-- Looking for fcntl.h
-- Looking for fcntl.h - found
-- Looking for fnmatch.h
-- Looking for fnmatch.h - found
-- Looking for history.h
-- Looking for history.h - not found
-- Looking for ieeefp.h
-- Looking for ieeefp.h - not found
-- Looking for inttypes.h
-- Looking for inttypes.h - found
-- Looking for memory.h
-- Looking for memory.h - found
-- Looking for readline.h
-- Looking for readline.h - not found
-- Looking for readline/history.h
-- Looking for readline/history.h - found
-- Looking for readline/readline.h
-- Looking for readline/readline.h - found
-- Looking for stdarg.h
-- Looking for stdarg.h - found
-- Looking for stdlib.h
-- Looking for stdlib.h - found
-- Looking for strings.h
-- Looking for strings.h - found
-- Looking for string.h
-- Looking for string.h - found
-- Looking for sys/fcntl.h
-- Looking for sys/fcntl.h - found
-- Looking for sys/stat.h
-- Looking for sys/stat.h - found
-- Looking for sys/time.h
-- Looking for sys/time.h - found
-- Looking for unistd.h
-- Looking for unistd.h - found
-- Looking for fclose
-- Looking for fclose - found
-- Looking for fflush
-- Looking for fflush - found
-- Looking for fnmatch
-- Looking for fnmatch - found
-- Looking for fopen
-- Looking for fopen - found
-- Looking for fpclass
-- Looking for fpclass - not found
-- Looking for fprintf
-- Looking for fprintf - found
-- Looking for fread
-- Looking for fread - found
-- Looking for fseek
-- Looking for fseek - found
-- Looking for ftell
-- Looking for ftell - found
-- Looking for fwrite
-- Looking for fwrite - found
-- Looking for setvbuf
-- Looking for setvbuf - found
-- Looking for strerror
-- Looking for strerror - found
-- Looking for isnan
-- Looking for isnan - found
-- Looking for memmove
-- Looking for memmove - found
-- Looking for add_history
-- Looking for add_history - not found
-- Looking for stat64
-- Looking for stat64 - not found
-- Looking for stat
-- Looking for stat - found
-- The Fortran compiler identification is GNU 14.1.0
-- Checking whether Fortran compiler has -isysroot
-- Checking whether Fortran compiler has -isysroot - yes
-- Checking whether Fortran compiler supports OSX deployment target flag
-- Checking whether Fortran compiler supports OSX deployment target flag - yes
-- Detecting Fortran compiler ABI info
-- Detecting Fortran compiler ABI info - done
-- Check for working Fortran compiler: /opt/homebrew/bin/gfortran-14 - skipped
-- Detecting Fortran/C Interface
-- Detecting Fortran/C Interface - Found GLOBAL and MODULE mangling
-- Configuring done (8.3s)
-- Generating done (0.0s)
-- Build files have been written to: /Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo-build
[ 75%] Performing build step for 'silo'
[  1%] Building C object CMakeFiles/pdb_detect.dir/src/pdb/detect.c.o
[  2%] Linking C executable bin/pdb_detect
Creating pdform.h using pdb_detect
Creating lite_pdb.h using mklite
Creating lite_score.h using mklite
[  2%] Built target pdb_detect
[  5%] Building C object CMakeFiles/silo.dir/src/netcdf/api.c.o
[  5%] Building C object CMakeFiles/silo.dir/src/debug/silo_debug.c.o
[  6%] Building C object CMakeFiles/silo.dir/src/netcdf/obj.c.o
[  8%] Building C object CMakeFiles/silo.dir/src/netcdf/silo_netcdf.c.o
[ 10%] Building C object CMakeFiles/silo.dir/src/filters/f_sample.c.o
[ 10%] Building C object CMakeFiles/silo.dir/src/netcdf/ent.c.o
[ 12%] Building C object CMakeFiles/silo.dir/src/netcdf/netcdf.c.o
[ 13%] Building C object CMakeFiles/silo.dir/src/filters/f_ale3d.c.o
[ 14%] Building C object CMakeFiles/silo.dir/src/netcdf/table.c.o
[ 16%] Building C object CMakeFiles/silo.dir/src/pdb/pdb.c.o
[ 17%] Building C object CMakeFiles/silo.dir/src/pdb/pdbdir.c.o
[ 18%] Building C object CMakeFiles/silo.dir/src/pdb/pdbio.c.o
[ 20%] Building C object CMakeFiles/silo.dir/src/pdb/pdbmm.c.o
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/pdb/pdb.c:1810:2: warning: #warning MOVE TO PDLOW.C [-Wcpp]
 1810 | #warning MOVE TO PDLOW.C
      |  ^~~~~~~
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/pdb/pdb.c:1818:2: warning: #warning MOVE TO PDMEMB.C [-Wcpp]
 1818 | #warning MOVE TO PDMEMB.C
      |  ^~~~~~~
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/pdb/pdb.c:1826:2: warning: #warning MOVE TO PDLOW.C [-Wcpp]
 1826 | #warning MOVE TO PDLOW.C
      |  ^~~~~~~
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/pdb/pdb.c:1877:2: warning: #warning MOVE TO PDLOW.C [-Wcpp]
 1877 | #warning MOVE TO PDLOW.C
      |  ^~~~~~~
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/pdb/pdb.c:1886:2: warning: #warning MOVE TO PDLOW.C [-Wcpp]
 1886 | #warning MOVE TO PDLOW.C
      |  ^~~~~~~
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/pdb/pdb.c:1896:2: warning: #warning MOVE TO PDBDIR.C [-Wcpp]
 1896 | #warning MOVE TO PDBDIR.C
      |  ^~~~~~~
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/pdb/pdb.c: In function 'lite_PD_ln':
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/pdb/pdb.c:1903:2: warning: #warning MAYBE INCREASE MAXLINE FOR LEOSPACT [-Wcpp]
 1903 | #warning MAYBE INCREASE MAXLINE FOR LEOSPACT
      |  ^~~~~~~
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/pdb/pdb.c: At top level:
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/pdb/pdb.c:1980:2: warning: #warning SHOULD GO IN PDBMM.c [-Wcpp]
 1980 | #warning SHOULD GO IN PDBMM.c
      |  ^~~~~~~
[ 21%] Building C object CMakeFiles/silo.dir/src/pdb/pdbx.c.o
[ 22%] Building C object CMakeFiles/silo.dir/src/pdb/pdconv.c.o
[ 24%] Building C object CMakeFiles/silo.dir/src/pdb/pdlow.c.o
[ 25%] Building C object CMakeFiles/silo.dir/src/pdb/pdmemb.c.o
[ 27%] Building C object CMakeFiles/silo.dir/src/pdb/pdpath.c.o
[ 28%] Building C object CMakeFiles/silo.dir/src/pdb/pdrdwr.c.o
[ 29%] Building C object CMakeFiles/silo.dir/src/pdb_drv/silo_pdb.c.o
[ 31%] Building C object CMakeFiles/silo.dir/src/score/memmove.c.o
[ 32%] Building C object CMakeFiles/silo.dir/src/score/scctl.c.o
[ 33%] Building C object CMakeFiles/silo.dir/src/score/scctla.c.o
[ 35%] Building C object CMakeFiles/silo.dir/src/score/schash.c.o
[ 36%] Building C object CMakeFiles/silo.dir/src/score/scstr.c.o
[ 37%] Building C object CMakeFiles/silo.dir/src/silo/alloc.c.o
[ 39%] Building C object CMakeFiles/silo.dir/src/silo/extface.c.o
[ 40%] Building C object CMakeFiles/silo.dir/src/silo/silo.c.o
[ 41%] Building C object CMakeFiles/silo.dir/src/silo/silo_ns.c.o
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/silo/alloc.c: In function 'DBIsEmptyQuadmesh':
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/silo/alloc.c:910:2: warning: #warning CHECK THIS LOGIC. IF ANY DIM>0, IT IS NOT EMPTY [-Wcpp]
  910 | #warning CHECK THIS LOGIC. IF ANY DIM>0, IT IS NOT EMPTY
      |  ^~~~~~~
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/silo/alloc.c: In function 'DBIsEmptyQuadvar':
[ 43%] Building C object CMakeFiles/silo.dir/src/silo/utils.c.o
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/silo/alloc.c:1357:2: warning: #warning CHECK THIS LOGIC [-Wcpp]
 1357 | #warning CHECK THIS LOGIC
      |  ^~~~~~~
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/silo/silo.c:75:2: warning: #warning SIMPLIFY HEADER INCLUSION LOGIC [-Wcpp]
   75 | #warning SIMPLIFY HEADER INCLUSION LOGIC
      |  ^~~~~~~
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/silo/silo.c:235:2: warning: #warning REDUCE USE OF THIS CONSTRUCT [-Wcpp]
  235 | #warning REDUCE USE OF THIS CONSTRUCT
      |  ^~~~~~~
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/silo/silo.c:295:2: warning: #warning FIX THIS [-Wcpp]
  295 | #warning FIX THIS
      |  ^~~~~~~
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/silo/silo.c: In function 'db_FreeToc':
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/silo/silo.c:1139:2: warning: #warning WE SHOULD PROBABLY JUST EITHER MAKE THIS CONSISTENT OR PERHAPS COPY ALL CHARS INTO LINK@TARGET format [-Wcpp]
 1139 | #warning WE SHOULD PROBABLY JUST EITHER MAKE THIS CONSISTENT OR PERHAPS COPY ALL CHARS INTO LINK@TARGET format
      |  ^~~~~~~
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/silo/silo.c: In function 'DBLs':
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/silo/silo.c:1746:2: warning: #warning CLEAN UP IS LOST IN ABOVE EARLY RETURNS [-Wcpp]
 1746 | #warning CLEAN UP IS LOST IN ABOVE EARLY RETURNS
      |  ^~~~~~~
[ 44%] Building C object CMakeFiles/silo.dir/src/taurus/silo_taurus.c.o
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/silo/silo.c: At top level:
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/silo/silo.c:2549:2: warning: #warning WHAT ABOUT FORCESINGLE SHOWERRORS [-Wcpp]
 2549 | #warning WHAT ABOUT FORCESINGLE SHOWERRORS
      |  ^~~~~~~
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/silo/silo.c: In function 'DBGrabDriver':
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/silo/silo.c:2860:2: warning: #warning FIX GLOBAL LOCK [-Wcpp]
 2860 | #warning FIX GLOBAL LOCK
      |  ^~~~~~~
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/silo/silo.c: At top level:
[ 45%] Building C object CMakeFiles/silo.dir/src/taurus/taurus.c.o
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/silo/silo.c:3603:2: warning: #warning ADD DBSHOWERRORSFILE [-Wcpp]
 3603 | #warning ADD DBSHOWERRORSFILE
      |  ^~~~~~~
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/silo/silo.c: In function 'DBShowErrors':
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/silo/silo.c:3620:2: warning: #warning GET RID OF SUSPEND/RESUME STUFF [-Wcpp]
 3620 | #warning GET RID OF SUSPEND/RESUME STUFF
      |  ^~~~~~~
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/silo/silo.c: In function 'db_InitFileGlobals':
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/silo/silo.c:3996:2: warning: #warning ADD compressionMinSize [-Wcpp]
 3996 | #warning ADD compressionMinSize
      |  ^~~~~~~
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/silo/silo.c:4000:2: warning: #warning CORRECT INITIALIZATION OF compressionErrmode [-Wcpp]
 4000 | #warning CORRECT INITIALIZATION OF compressionErrmode
      |  ^~~~~~~
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/silo/silo.c:4004:61: warning: assignment discards 'const' qualifier from pointer target type [-Wdiscarded-qualifiers]
 4004 |     dbfile->pub.file_scope_globals->compressionParams       = DB_CHAR_PTR_NOT_SET;
      |                                                             ^
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/silo/silo.c: In function 'DBClose':
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/silo/silo.c:4442:2: warning: #warning IS ORDER OF OPS CORRECT HERE [-Wcpp]
 4442 | #warning IS ORDER OF OPS CORRECT HERE
      |  ^~~~~~~
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/silo/silo.c: In function 'db_validate_copy_step':
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/silo/silo.c:5867:2: warning: #warning ONLY IF SRC SIZE SMALLER THAN DST SIZE [-Wcpp]
 5867 | #warning ONLY IF SRC SIZE SMALLER THAN DST SIZE
      |  ^~~~~~~
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/silo/silo.c: In function 'db_can_overwrite_dstobj_with_srcobj':
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/silo/silo.c:5964:2: warning: #warning SHOULDNT WE USE FILE LENGTH FUNCTIONS HERE [-Wcpp]
 5964 | #warning SHOULDNT WE USE FILE LENGTH FUNCTIONS HERE
      |  ^~~~~~~
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/silo/silo.c:5976:2: warning: #warning DISALLOW SIMLINKS FOR NOW [-Wcpp]
 5976 | #warning DISALLOW SIMLINKS FOR NOW
      |  ^~~~~~~
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/silo/silo.c: In function 'db_copy_single_object_abspath':
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/silo/silo.c:6044:2: warning: #warning CHECK ARGS HERE. ALLOW FOR NULL dstFile AND dstObjAbsName [-Wcpp]
 6044 | #warning CHECK ARGS HERE. ALLOW FOR NULL dstFile AND dstObjAbsName
      |  ^~~~~~~
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/silo/silo.c:6045:2: warning: #warning WHY CHECK dstType HERE [-Wcpp]
 6045 | #warning WHY CHECK dstType HERE
      |  ^~~~~~~
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/silo/silo.c:6074:2: warning: #warning USE FILE-BASED FUNCTION WHEN AVAILABLE [-Wcpp]
 6074 | #warning USE FILE-BASED FUNCTION WHEN AVAILABLE
      |  ^~~~~~~
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/silo/silo.c: In function 'DBCp':
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/silo/silo.c:6291:2: warning: #warning WHAT ABOUT API MACROS. MAYBE NOT NEEDED SINCE NOT CALLING DOWN INTO DRIVERS [-Wcpp]
 6291 | #warning WHAT ABOUT API MACROS. MAYBE NOT NEEDED SINCE NOT CALLING DOWN INTO DRIVERS
      |  ^~~~~~~
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/silo/silo.c:6292:2: warning: #warning WHAT ABOUT -f (force) OPTION [-Wcpp]
 6292 | #warning WHAT ABOUT -f (force) OPTION
      |  ^~~~~~~
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/silo/silo.c:6313:2: warning: #warning WARN ABOUT CERTAIN OPTIONS NOT YET SUPPORTED [-Wcpp]
 6313 | #warning WARN ABOUT CERTAIN OPTIONS NOT YET SUPPORTED
      |  ^~~~~~~
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/silo/silo.c:6401:2: warning: #warning FIX LEAKS WITH EARLY RETURN HERE [-Wcpp]
 6401 | #warning FIX LEAKS WITH EARLY RETURN HERE
      |  ^~~~~~~
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/silo/silo.c:6509:18: warning: passing argument 1 of 'free' discards 'const' qualifier from pointer target type [-Wdiscarded-qualifiers]
 6509 |             free(srcDirBaseName);
      |                  ^~~~~~~~~~~~~~
In file included from /Library/Developer/CommandLineTools/SDKs/MacOSX14.4.sdk/usr/include/stdlib.h:128,
                 from /Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/silo/silo.c:85:
/Library/Developer/CommandLineTools/SDKs/MacOSX14.4.sdk/usr/include/malloc/_malloc.h:56:12: note: expected 'void *' but argument is of type 'const char *'
   56 | void  free(void * __unsafe_indexable);
      |            ^~~~~~
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/silo/silo.c: In function 'DBGetPartialObject':
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/silo/silo.c:6688:2: warning: #warning FIX THIS METHOD [-Wcpp]
 6688 | #warning FIX THIS METHOD
      |  ^~~~~~~
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/silo/silo.c: At top level:
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/silo/silo.c:8210:2: warning: #warning DO WE NEED THIS METHOD [-Wcpp]
 8210 | #warning DO WE NEED THIS METHOD
      |  ^~~~~~~
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/silo/silo.c: In function 'DBPutMaterial':
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/silo/silo.c:8987:2: warning: #warning BETTER PLACE TO NULL THESE [-Wcpp]
 8987 | #warning BETTER PLACE TO NULL THESE
      |  ^~~~~~~
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/silo/silo.c: In function 'DBPutMultimat':
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/silo/silo.c:9388:2: warning: #warning BETTER PLACE TO NULL THESE [-Wcpp]
 9388 | #warning BETTER PLACE TO NULL THESE
      |  ^~~~~~~
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/silo/silo.c: In function 'DBPutZonelist2':
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/silo/silo.c:10381:2: warning: #warning HI AND LO OFFSET NOT VALID IN PRESENCE OF EXPLICIT GHOST LABELS [-Wcpp]
10381 | #warning HI AND LO OFFSET NOT VALID IN PRESENCE OF EXPLICIT GHOST LABELS
      |  ^~~~~~~
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/silo/silo.c: In function 'DBStringArrayToStringList':
[ 47%] Building C object CMakeFiles/silo.dir/src/unknown/silo_unknown.c.o
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/silo/silo.c:13364:2: warning: #warning TEST THIS LOGIC [-Wcpp]
13364 | #warning TEST THIS LOGIC
      |  ^~~~~~~
[ 48%] Building C object CMakeFiles/silo.dir/src/silo/silo_f.c.o
[ 50%] Building C object CMakeFiles/silo.dir/src/hdf5_drv/H5FDsilo.c.o
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/hdf5_drv/H5FDsilo.c:508:2: warning: #warning REMOVE ME [-Wcpp]
  508 | #warning REMOVE ME
      |  ^~~~~~~
[ 51%] Building C object CMakeFiles/silo.dir/src/hdf5_drv/silo_hdf5.c.o
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/hdf5_drv/H5FDsilo.c: In function 'H5FD_silo_get_eof':
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/hdf5_drv/H5FDsilo.c:2001:2: warning: #warning TAKE ADVANTAGE OF TYPE INFO HERE [-Wcpp]
 2001 | #warning TAKE ADVANTAGE OF TYPE INFO HERE
      |  ^~~~~~~
In file included from /Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/hdf5_drv/silo_hdf5.c:73:
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/hdf5_drv/silo_hdf5_private.h:111:2: warning: #warning REMOVE db_hdf5_CpListedObjects [-Wcpp]
  111 | #warning REMOVE db_hdf5_CpListedObjects
      |  ^~~~~~~
In file included from /Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/hdf5_drv/silo_hdf5_private.h:67:
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/hdf5_drv/silo_hdf5.c: In function 'db_hdf5_get_obj_dsnames':
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/hdf5_drv/silo_hdf5.c:1812:45: error: passing argument 1 of '_db_safe_strdup' makes pointer from integer without a cast [-Wint-conversion]
 1812 |             (*dsnames)[i] = strdup(m.MEMNAME[i]);                \
      |                                    ~~~~~~~~~^~~
      |                                             |
      |                                             char
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/silo/silo_private.h:939:35: note: in definition of macro 'strdup'
  939 | #define strdup(s) _db_safe_strdup(s)
      |                                   ^
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/hdf5_drv/silo_hdf5.c:1869:13: note: in expansion of macro 'DB_OBJ_CASE'
 1869 |             DB_OBJ_CASE(DB_CURVE, DBcurve_mt, npts?1:1, yvarname)
      |             ^~~~~~~~~~~
In file included from /Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/silo/silo_private.h:79:
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo-build/include/silo.h:2214:56: note: expected 'const char *' but argument is of type 'char'
 2214 | SILO_API extern char *                 _db_safe_strdup(const char *);
      |                                                        ^~~~~~~~~~~~
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/hdf5_drv/silo_hdf5.c: In function 'db_hdf5_InitCallbacks':
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/hdf5_drv/silo_hdf5.c:2802:2: warning: #warning GET RID OF CPLISTEDOBJECTS [-Wcpp]
 2802 | #warning GET RID OF CPLISTEDOBJECTS
      |  ^~~~~~~
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/hdf5_drv/silo_hdf5.c: In function 'db_hdf5_set_compression':
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/hdf5_drv/silo_hdf5.c:3354:2: warning: #warning WHAT ABOUT NULL RETURN FROM DBGETCOMPRESSION [-Wcpp]
 3354 | #warning WHAT ABOUT NULL RETURN FROM DBGETCOMPRESSION
      |  ^~~~~~~
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/hdf5_drv/silo_hdf5.c:3387:2: warning: #warning FIX MISSING .compressionMinsize member [-Wcpp]
 3387 | #warning FIX MISSING .compressionMinsize member
      |  ^~~~~~~
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/hdf5_drv/silo_hdf5.c:3407:2: warning: #warning QUERY FILE LEVEL COMPRESSION PARAMS HERE [-Wcpp]
 3407 | #warning QUERY FILE LEVEL COMPRESSION PARAMS HERE
      |  ^~~~~~~
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/hdf5_drv/silo_hdf5.c: In function 'load_toc':
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/hdf5_drv/silo_hdf5.c:4134:2: warning: #warning REVISIT THIS CODE BLOCK [-Wcpp]
 4134 | #warning REVISIT THIS CODE BLOCK
      |  ^~~~~~~
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/hdf5_drv/silo_hdf5.c: In function 'db_hdf5_resolvename':
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/hdf5_drv/silo_hdf5.c:4751:2: warning: #warning HARD CODED SIZE HERE [-Wcpp]
 4751 | #warning HARD CODED SIZE HERE
      |  ^~~~~~~
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/hdf5_drv/silo_hdf5.c: In function 'db_hdf5_process_file_options':
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/hdf5_drv/silo_hdf5.c:4977:2: warning: #warning FIX ME...THIS NEEDS TO BE CONDITION ON COMPAT MODE WORKS FOR 1.8.0 [-Wcpp]
 4977 | #warning FIX ME...THIS NEEDS TO BE CONDITION ON COMPAT MODE WORKS FOR 1.8.0
      |  ^~~~~~~
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/hdf5_drv/silo_hdf5.c:4986:2: warning: #warning SET FRIENDLY NAMES TO 2 but only at file level [-Wcpp]
 4986 | #warning SET FRIENDLY NAMES TO 2 but only at file level
      |  ^~~~~~~
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/hdf5_drv/silo_hdf5.c:5024:2: warning: #warning REMOVED WINDOWS SPECIFIC CHECK [-Wcpp]
 5024 | #warning REMOVED WINDOWS SPECIFIC CHECK
      |  ^~~~~~~
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/hdf5_drv/silo_hdf5.c:5115:2: warning: #warning DO WE STILL NEED THIS [-Wcpp]
 5115 | #warning DO WE STILL NEED THIS
      |  ^~~~~~~
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/hdf5_drv/silo_hdf5.c:5175:2: warning: #warning REMOVED WINDOWS SPECIFIC CHECK [-Wcpp]
 5175 | #warning REMOVED WINDOWS SPECIFIC CHECK
      |  ^~~~~~~
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/hdf5_drv/silo_hdf5.c:5295:2: warning: #warning PUT UDATA POINTER IN DBFILE pointer so it can be freed with file is closed. [-Wcpp]
 5295 | #warning PUT UDATA POINTER IN DBFILE pointer so it can be freed with file is closed.
      |  ^~~~~~~
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/hdf5_drv/silo_hdf5.c:5530:2: warning: #warning FIX THIS [-Wcpp]
 5530 | #warning FIX THIS
      |  ^~~~~~~
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/hdf5_drv/silo_hdf5.c: In function 'db_hdf5_Open':
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/hdf5_drv/silo_hdf5.c:5909:2: warning: #warning QUERY FILE IMAGE STUFF HERE TO GET UDATA PTR [-Wcpp]
 5909 | #warning QUERY FILE IMAGE STUFF HERE TO GET UDATA PTR
      |  ^~~~~~~
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/hdf5_drv/silo_hdf5.c: In function 'db_hdf5_Create':
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/hdf5_drv/silo_hdf5.c:5993:2: warning: #warning BACKWARD COMPAT ISSUE FOR HDF5 [-Wcpp]
 5993 | #warning BACKWARD COMPAT ISSUE FOR HDF5
      |  ^~~~~~~
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/hdf5_drv/silo_hdf5.c:6030:2: warning: #warning FIX FILE SCOPE GLOBAL INITIALIZATION [-Wcpp]
 6030 | #warning FIX FILE SCOPE GLOBAL INITIALIZATION
      |  ^~~~~~~
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/hdf5_drv/silo_hdf5.c: In function 'copy_obj':
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/hdf5_drv/silo_hdf5.c:6496:2: warning: #warning WHY THIS SIZE [-Wcpp]
 6496 | #warning WHY THIS SIZE
      |  ^~~~~~~
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/hdf5_drv/silo_hdf5.c: At top level:
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/hdf5_drv/silo_hdf5.c:6667:2: warning: #warning REMOVE THIS MAYBE [-Wcpp]
 6667 | #warning REMOVE THIS MAYBE
      |  ^~~~~~~
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/hdf5_drv/silo_hdf5.c: In function 'db_hdf5_WriteObject':
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/hdf5_drv/silo_hdf5.c:7406:2: warning: #warning COMPATABILITY ISSUE [-Wcpp]
 7406 | #warning COMPATABILITY ISSUE
      |  ^~~~~~~
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/hdf5_drv/silo_hdf5.c: In function 'db_hdf5_get_var_byte_length':
[ 52%] Building C object CMakeFiles/silo.dir/src/hdf5_drv/H5Zzfp.c.o
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/hdf5_drv/silo_hdf5.c:7781:2: warning: #warning REMOVED db_perror CALLS [-Wcpp]
 7781 | #warning REMOVED db_perror CALLS
      |  ^~~~~~~
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/hdf5_drv/silo_hdf5.c: In function 'db_hdf5_WriteCKZ':
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/hdf5_drv/silo_hdf5.c:8429:2: warning: #warning WHAT IF EXISTING DATASET WAS COMPRESSED [-Wcpp]
 8429 | #warning WHAT IF EXISTING DATASET WAS COMPRESSED
      |  ^~~~~~~
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/hdf5_drv/silo_hdf5.c:8473:2: warning: #warning COMPARE TO -1 OR TO NEGATIVE [-Wcpp]
 8473 | #warning COMPARE TO -1 OR TO NEGATIVE
      |  ^~~~~~~
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/hdf5_drv/silo_hdf5.c:8497:2: warning: #warning COMPARE TO -1 OR NEGATIVE [-Wcpp]
 8497 | #warning COMPARE TO -1 OR NEGATIVE
      |  ^~~~~~~
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/hdf5_drv/silo_hdf5.c: In function 'db_hdf5_GetObject':
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/hdf5_drv/silo_hdf5.c:8724:2: warning: #warning THIS IFDEFD CODE IS IN TRANSITION TO BETTER GENERIC OBJECTS [-Wcpp]
 8724 | #warning THIS IFDEFD CODE IS IN TRANSITION TO BETTER GENERIC OBJECTS
      |  ^~~~~~~
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/hdf5_drv/silo_hdf5.c:8823:2: warning: #warning REVISIT THIS CLEANUP CODE. IS THERE A BETTER SYMBOLIC VALUE THAN -1 [-Wcpp]
 8823 | #warning REVISIT THIS CLEANUP CODE. IS THERE A BETTER SYMBOLIC VALUE THAN -1
      |  ^~~~~~~
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/hdf5_drv/silo_hdf5.c:8830:2: warning: #warning USE FREE() MACRO HERE [-Wcpp]
 8830 | #warning USE FREE() MACRO HERE
      |  ^~~~~~~
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/hdf5_drv/silo_hdf5.c:8844:2: warning: #warning USE FREE() MACRO HERE [-Wcpp]
 8844 | #warning USE FREE() MACRO HERE
      |  ^~~~~~~
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/hdf5_drv/silo_hdf5.c: In function 'db_hdf5_PutMultimat':
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/hdf5_drv/silo_hdf5.c:14354:2: warning: #warning REPLACE WITH STRING UTILITIES [-Wcpp]
14354 | #warning REPLACE WITH STRING UTILITIES
      |  ^~~~~~~
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/hdf5_drv/silo_hdf5.c:14394:2: warning: #warning IS THIS TAKEN CARE OF ELSEWHERE [-Wcpp]
14394 | #warning IS THIS TAKEN CARE OF ELSEWHERE
      |  ^~~~~~~
/Users/spencer/Downloads/mfc/build/staging/silo/silo-prefix/src/silo/src/hdf5_drv/silo_hdf5.c:14406:2: warning: #warning IS THIS TAKEN CARE OF ELSEWHERE [-Wcpp]
14406 | #warning IS THIS TAKEN CARE OF ELSEWHERE
      |  ^~~~~~~
make[6]: *** [CMakeFiles/silo.dir/src/hdf5_drv/silo_hdf5.c.o] Error 1
make[6]: *** Waiting for unfinished jobs....
[ 54%] Building C object CMakeFiles/silo.dir/src/zfp-0.5.5/src/bitstream.c.o
make[5]: *** [CMakeFiles/silo.dir/all] Error 2
make[4]: *** [all] Error 2
make[3]: *** [silo-prefix/src/silo-stamp/silo-build] Error 2
make[2]: *** [CMakeFiles/silo.dir/all] Error 2
make[1]: *** [CMakeFiles/silo.dir/rule] Error 2
make: *** [silo] Error 2

Error: Failed to build the silo target.

./mfc.sh: line 49: 36670 Terminated: 15          python3 "$(pwd)/toolchain/main.py" "$@"

Relevant issue on the silo repository: https://github.com/LLNL/Silo/issues/375


Unity MJ Scene Import - geom mass and density values are lost

using 2.2.0 and Unity 2020.3
I built a single muscle mujoco model to use with ML Agents. However, I noticed that the model actuation behaves differently from the simulator, which bugged me for a while. It took a bit of tracing to figure out the problem, but I will state the issue first.
I started by importing the muscle model in Unity using "Import Mujoco Scene". singlemuscle.txt
I set the actuator to 0.445, the muscle pulls the arm all the way up in unity, but pulls it only moderately in the simulator.
sensordata in simulator shows a tendon length of 0.21, while in unity, the actuator debug value shows 0.07
I started by comparing the original xml to the xml saved by the unity script, I suspected the muscle parameters turned into general, but I was wrong.
I kept trying to get the 2 files close to each other (Original and Script generated), until I figured it has to do with the mass/density values, these values get completely lost in translation (pun intended)
The script generated xml ignores any mass/density values
The problem happens here:
public unsafe GameObject ImportFile(string filePath) {
    // If MuJoCo can't parse the mjcfString, we abort the entire process.
    // MjEngineTool.LoadModelFromString throws an exception when MuJoCo fails to parse the provided
    // mjcfString.
    var name = Path.GetFileNameWithoutExtension(filePath) + $"{UnityEngine.Random.Range(0,999)}";
    string newPath = Path.Combine(Application.temporaryCachePath, $"{name}.xml");
    _mjModel = MjEngineTool.LoadModelFromFile(filePath);
    MjEngineTool.SaveModelToFile(newPath, _mjModel);
    Debug.Log($"Imported MJCF loaded, saved to {newPath}");
    string mjcfString = File.ReadAllText(newPath);
    GameObject root = null;
    try {
      root = ImportString(mjcfString, name, filePath);
    } finally {
      MujocoLib.mj_deleteModel(_mjModel);
    }
    return root;
  }

Briefly, the original XML is loaded into mjModel, the mjModel is saved to new XML, the new XML is loaded into Unity.
The problem happens somewhere in the middle, probably when the mjModel is saved to XML?
If I knew how to read mass/density values from mjModel, probably I could trace this more, but I think that's the best I can do at the moment.
Actually, I changed the code above to ImportString directly from the original XML and all worked fine for me, so it's an acceptable workaround, knowing that I am skipping the failsafe XML Validation, but I know we should take advantage of chances in life sometimes.

Hi Michel, I have tested your model with the XML load/save and if I load it, save it, and load it again, then all internal MuJoCo data structure are exactly identical, so I am inclined to think that the issue is not coming from saving the XML, but rather from the Unity plugin. Can you reproduce the bug in any way if you load-save-load in MuJoCo rather than Unity? Thanks.

yes, it is indeed plugin related. I am comparing to the simulator, as my reference of confidence.
The code I am referring to, above, is an extract from the unity plugin code that I am suspecting.
this line:
MjEngineTool.SaveModelToFile(newPath, _mjModel);
saves the model back to xml, without the mass/density attributes.
If you'd like, I can show you how the xml looks like after that code saves it.
As I mentioned, skipping the xml load/save (for the purpose of format verification) fixes it, which confirms that the load model/save model step above is most probably the source of the problem.

Yes please I would like to look at the XML. AFAIK, the plugin is calling the same load/save XML functions that are used in MuJoCo, so I'm surprised that the issue shows up only in the plugin.

had to rename to text to be able to upload to github.
First one is the original xml file containing 2 nodes with mass=0
Second one is the file saved in temp folder by the plugin, mass value disappeared.
Same behavior happens for density as well, but I didn't include density in this test file.
I am using the "Import Mujoco Scene" from the Assets Menu, Unity 2020.3, Plugin 2.2.0 (2.2.1 currently crashes, so I am not usin g it and reported it separately)
I am surprised as well, however the scenario is straight forward. I reviewed the XML reference to make sure I am using the correct syntax for assigning mass/density in Mujoco.
Is it possible that the MjGeom Scripts are not picking up the values correctly, and they may be involved in the process of loading/saving?
singlemuscle-original.txt
singlemuscle-savedbyplugin.txt

Do you see the mass disappearing also in the inspector? For me it's there.

this screenshot is showing the xml file - which I assume is the file I uploaded.
Did you try loading the xml using MJ Import Scene and look at the geom nodes with zero mass?

I get a crash with both 2.2.1 and 2.2.0 with the latest Unity..

2.2.1 unity plugin seems corrupt, I already reported that in a separate issue, and this issue here is reported for 2.2.0.
2.2.0 plugin works fine, unless you accidentally let it pick up the 2,2.1 dll

I tried with Unity 2022.1 and whatever caused the plugin to crash is now fixed. I can import your files so I will take a look.

OK that's interesting because the XML in my temp folder does have mass="0 (see attachment) and I see mass 0 also in the properties of the geom in Unity (see screenshot). What is your version of the unity plugin? The zero mass issue was solved on May 25th: https://github.com/deepmind/mujoco/commit/223874c4cab35cd88332947e0d9b13d5ec3822e4

singlemuscle_temp.txt

You are actually showing the problem i reported. mass is zero but density is 1000. density shouldn't be 1000 when mass is zero.
If you try the steps I indicated in the main issue, the results are different between unity and simulator. did you try them?
The commit you are referring to is after 2.2.0 - so I cannot confirm it, until 2.2.1 crash is resolved - you mentioned you are using 2.2.0 as well. I'd be happy to test it if fixed.

it's interesting that the mass is zero in your temp folder, that's different from what I have, which unity plugin version are you using?

Closing because stale.


Any instructions on how to install in RHEL/Centos 7

Has anyone tried to install in RHEL 7? Any instructions or procedure to be followed?

unix instructions in doc folder

sonicdx10 thanks for letting me know. I try to install using that.
Appreciate it.

so there might be few deppendencies missing right?

I think so. But before knowing about the instructions I tried a few things myself and it didn't worked ; -) but let's see I'll try it again carefully in a fresh VM and test.  Will let u know how it goes.

So I just tried out the instruction and yes there were some dependencies missing which were causing issue for ./configure and make install commands. But one by one I searched for the packages and installed then ran make install ./configure with the arguments as shown in the instructions and finally with the command as below the final output I received:
./configure LDFLAGS="-L${BDB_PREFIX}/lib/" CPPFLAGS="-I${BDB_PREFIX}/include/"
.................
.................
configure: Using endomorphism optimizations: no
configure: Building ECDH module: no
configure: Building ECDSA pubkey recovery module: yes
configure: Using jni: no
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating libsecp256k1.pc
config.status: creating src/libsecp256k1-config.h
config.status: executing depfiles commands
config.status: executing libtool commands
Fixing libtool for -rpath problems.
Options used to compile and link:
with wallet   = yes
with gui / qt = yes
qt version  = 5
with qr     = yes
with zmq      = no
with test     = no
with bench    = no
with upnp     = yes
debug enabled = no
werror        = no
target os     = linux
build os      =
CC            = gcc
CFLAGS        = -g -O2
CPPFLAGS      = -I/root/Downloads/BitcoinDiamond-master/db4/include/ -DHAVE_BUILD_INFO -D__STDC_FORMAT_MACROS
CXX           = g++ -std=c++11
CXXFLAGS      = -g -O2 -Wall -Wextra -Wformat -Wvla -Wformat-security -Wno-unused-parameter
LDFLAGS       = -L/root/Downloads/BitcoinDiamond-master/db4/lib/
At this point I believe installation has gone successful but I dont know how to get to the mining part.


Postgres Loader Configuration modal has unreadable text on meltano.meltanodata.com

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/1576
Originally created by @dmor on 2020-01-16 16:38:25

Repro steps

Go to meltano.meltanodata.com
Go to https://meltano.meltanodata.com/pipeline/load/target-postgres
View the model and roll mouse over any of the fields, to observe that the tooltip text to the right of the end of the modal boundary is unreadable

Potential MVC solution: bump up the Z-index of the tooltip so that it displays in front of the modal

View 3 previous comments from the original issue on GitLab


Failing to compile on macOS/Ruby 2.7.1 but not sure why

This is what I have in my logs for installing unf_ext. I'm not sure why this isn't working, it seems to be pointing to a source-code issue only, not failing to find other files, etc
If I can provide any other information, please let me know.
Installing unf_ext <IP_ADDRESS> (was <IP_ADDRESS>) with native extensions
Gem::Ext::BuildError: ERROR: Failed to build gem native extension.

    current directory: /Users/Csuhta/.gem/ruby/2.7.1/gems/unf_ext-<IP_ADDRESS>/ext/unf_ext
/Users/Csuhta/.rubies/ruby-2.7.1/bin/ruby -I /Users/Csuhta/.rubies/ruby-2.7.1/lib/ruby/2.7.0 -r ./siteconf20200401-85002-qhwila.rb extconf.rb
checking for -lstdc++... yes
creating Makefile

current directory: /Users/Csuhta/.gem/ruby/2.7.1/gems/unf_ext-<IP_ADDRESS>/ext/unf_ext
make "DESTDIR=" clean

current directory: /Users/Csuhta/.gem/ruby/2.7.1/gems/unf_ext-<IP_ADDRESS>/ext/unf_ext
make "DESTDIR="
compiling unf.cc
In file included from unf.cc:3:
In file included from /Users/Csuhta/.rubies/ruby-2.7.1/include/ruby-2.7.0/ruby.h:33:
In file included from /Users/Csuhta/.rubies/ruby-2.7.1/include/ruby-2.7.0/ruby/ruby.h:29:
In file included from /Users/Csuhta/.rubies/ruby-2.7.1/include/ruby-2.7.0/ruby/defines.h:171:
In file included from /Users/Csuhta/.rubies/ruby-2.7.1/include/ruby-2.7.0/ruby/missing.h:25:
/usr/local/include/jemalloc/jemalloc.h:226:28: error: exception specification in declaration does not match previous declaration
    void JEMALLOC_NOTHROW       *je_malloc(size_t size)
                                 ^
/usr/local/include/jemalloc/jemalloc.h:69:21: note: expanded from macro 'je_malloc'
#  define je_malloc malloc
                    ^
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/malloc/_malloc.h:40:7: note: previous declaration is here
void    *malloc(size_t __size) __result_use_check __alloc_size(1);
         ^
In file included from unf.cc:3:
In file included from /Users/Csuhta/.rubies/ruby-2.7.1/include/ruby-2.7.0/ruby.h:33:
In file included from /Users/Csuhta/.rubies/ruby-2.7.1/include/ruby-2.7.0/ruby/ruby.h:29:
In file included from /Users/Csuhta/.rubies/ruby-2.7.1/include/ruby-2.7.0/ruby/defines.h:171:
In file included from /Users/Csuhta/.rubies/ruby-2.7.1/include/ruby-2.7.0/ruby/missing.h:25:
/usr/local/include/jemalloc/jemalloc.h:229:28: error: exception specification in declaration does not match previous declaration
    void JEMALLOC_NOTHROW       *je_calloc(size_t num, size_t size)
                                 ^
/usr/local/include/jemalloc/jemalloc.h:63:21: note: expanded from macro 'je_calloc'
#  define je_calloc calloc
                    ^
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/malloc/_malloc.h:41:7: note: previous declaration is here
void    *calloc(size_t __count, size_t __size) __result_use_check __alloc_size(1,2);
         ^
In file included from unf.cc:3:
In file included from /Users/Csuhta/.rubies/ruby-2.7.1/include/ruby-2.7.0/ruby.h:33:
In file included from /Users/Csuhta/.rubies/ruby-2.7.1/include/ruby-2.7.0/ruby/ruby.h:29:
In file included from /Users/Csuhta/.rubies/ruby-2.7.1/include/ruby-2.7.0/ruby/defines.h:171:
In file included from /Users/Csuhta/.rubies/ruby-2.7.1/include/ruby-2.7.0/ruby/missing.h:25:
/usr/local/include/jemalloc/jemalloc.h:231:38: error: exception specification in declaration does not match previous declaration
JEMALLOC_EXPORT int JEMALLOC_NOTHROW    je_posix_memalign(void **memptr,
                                        ^
/usr/local/include/jemalloc/jemalloc.h:77:29: note: expanded from macro 'je_posix_memalign'
#  define je_posix_memalign posix_memalign
                            ^
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/malloc/_malloc.h:52:7: note: previous declaration is here
int      posix_memalign(void **__memptr, size_t __alignment, size_t __size) __OSX_AVAILABLE_STARTING(__MAC_10_6, __IPHONE_3_0);
         ^
In file included from unf.cc:3:
In file included from /Users/Csuhta/.rubies/ruby-2.7.1/include/ruby-2.7.0/ruby.h:33:
In file included from /Users/Csuhta/.rubies/ruby-2.7.1/include/ruby-2.7.0/ruby/ruby.h:29:
In file included from /Users/Csuhta/.rubies/ruby-2.7.1/include/ruby-2.7.0/ruby/defines.h:171:
In file included from /Users/Csuhta/.rubies/ruby-2.7.1/include/ruby-2.7.0/ruby/missing.h:25:
/usr/local/include/jemalloc/jemalloc.h:238:28: error: exception specification in declaration does not match previous declaration
    void JEMALLOC_NOTHROW       *je_realloc(void *ptr, size_t size)
                                 ^
/usr/local/include/jemalloc/jemalloc.h:79:22: note: expanded from macro 'je_realloc'
#  define je_realloc realloc
                     ^
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/malloc/_malloc.h:43:7: note: previous declaration is here
void    *realloc(void *__ptr, size_t __size) __result_use_check __alloc_size(2);
         ^
In file included from unf.cc:3:
In file included from /Users/Csuhta/.rubies/ruby-2.7.1/include/ruby-2.7.0/ruby.h:33:
In file included from /Users/Csuhta/.rubies/ruby-2.7.1/include/ruby-2.7.0/ruby/ruby.h:29:
In file included from /Users/Csuhta/.rubies/ruby-2.7.1/include/ruby-2.7.0/ruby/defines.h:171:
In file included from /Users/Csuhta/.rubies/ruby-2.7.1/include/ruby-2.7.0/ruby/missing.h:25:
/usr/local/include/jemalloc/jemalloc.h:240:39: error: exception specification in declaration does not match previous declaration
JEMALLOC_EXPORT void JEMALLOC_NOTHROW   je_free(void *ptr)
                                        ^
/usr/local/include/jemalloc/jemalloc.h:65:19: note: expanded from macro 'je_free'
#  define je_free free
                  ^
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/malloc/_malloc.h:42:7: note: previous declaration is here
void     free(void *);
         ^
In file included from unf.cc:3:
In file included from /Users/Csuhta/.rubies/ruby-2.7.1/include/ruby-2.7.0/ruby.h:33:
In file included from /Users/Csuhta/.rubies/ruby-2.7.1/include/ruby-2.7.0/ruby/ruby.h:29:
In file included from /Users/Csuhta/.rubies/ruby-2.7.1/include/ruby-2.7.0/ruby/defines.h:171:
In file included from /Users/Csuhta/.rubies/ruby-2.7.1/include/ruby-2.7.0/ruby/missing.h:25:
/usr/local/include/jemalloc/jemalloc.h:279:28: error: exception specification in declaration does not match previous declaration
    void JEMALLOC_NOTHROW       *je_valloc(size_t size) JEMALLOC_CXX_THROW
                                 ^
/usr/local/include/jemalloc/jemalloc.h:83:21: note: expanded from macro 'je_valloc'
#  define je_valloc valloc
                    ^
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/unistd.h:735:7: note: previous declaration is here
void    *valloc(size_t);
         ^
6 errors generated.
make: *** [unf.o] Error 1

make failed, exit code 2

Gem files will remain installed in /Users/Csuhta/.gem/ruby/2.7.1/gems/unf_ext-<IP_ADDRESS> for inspection.
Results logged to /Users/Csuhta/.gem/ruby/2.7.1/extensions/x86_64-darwin-19/2.7.0-static/unf_ext-<IP_ADDRESS>/gem_make.out

An error occurred while installing unf_ext (<IP_ADDRESS>), and Bundler cannot continue.
Make sure that `gem install unf_ext -v '<IP_ADDRESS>' --source 'https://rubygems.org/'` succeeds before bundling.

In Gemfile:
  discordrb was resolved to 3.3.0, which depends on
    discordrb-webhooks was resolved to 3.3.0, which depends on
      rest-client was resolved to 2.1.0, which depends on
        http-cookie was resolved to 1.0.3, which depends on
          domain_name was resolved to 0.5.20190701, which depends on
            unf was resolved to 0.1.4, which depends on
              unf_ext

Seeing the same issue. No clue what this is about.

I was able to fix this on MacOS 10.15.4, but I'm not sure what did it:

Reinstall MacOS Developer Tools
Re-install Jemalloc and Ruby (using homebrew and ruby-install)
Gem bundled correctly after that

After reinstalling jemalloc gem installed:
▶ brew reinstall jemalloc
==> Reinstalling jemalloc
==> Downloading https://homebrew.bintray.com/bottles/jemalloc-5.2.1_1.catalina.bottle.tar.gz
==> Downloading from https://akamai.bintray.com/b1/b1b211e5bead798c236d478dd74310a97a7b59470f607b608c07222648b08bf5?__gda__=exp=1587473617~hmac=2fe57
######################################################################## 100.0%
==> Pouring jemalloc-5.2.1_1.catalina.bottle.tar.gz
🍺  /usr/local/Cellar/jemalloc/5.2.1_1: 16 files, 2MB

▶ gem install unf_ext -v '<IP_ADDRESS>'
Building native extensions. This could take a while...
Successfully installed unf_ext-<IP_ADDRESS>
Parsing documentation for unf_ext-<IP_ADDRESS>
Installing ri documentation for unf_ext-<IP_ADDRESS>
Done installing documentation for unf_ext after 1 seconds
1 gem installed

If anyone should have a similar problem:
I still got the same error despite these steps. It just didn't work when the Command Tools were installed - the following steps, one after the other, were a workaround for me:
sudo rm -rf /Library/Developer/CommandLineTools
gem install unf_ext -v <IP_ADDRESS>
sudo xcode-select --install

Is there a solution for Linux? I installed all development tools and c++ devel libs, build is failing with 2.7
Centos 7
error.txt

If you come here in 2023, DON'T UNINSTALL anything related to XCode. No need.
There are great chance it is because your system Ruby, which is old, is loaded before your Homebrew Ruby.
Just follow this guide to have a ruby command using your latest Ruby installation.


add cpuset cgroup on the host.

Description of problem
The cpuset cgroup(.linux.resources.cpu.cpus[1]) is not applied in the host. When this is used the runtime caller expect that workload only run on specific cpus on  the host. This is the case of kuberentes static cpu manager policy[2].
Additional information.
[1] https://github.com/opencontainers/runtime-spec/blob/master/config-linux.md#cpu
[2] https://github.com/kata-containers/runtime/issues/878.
Expected result
The cgroup is applied and qemu and shim only run on the provided cpus.
Example:
$docker run -tid --runtime runc  --cpuset-cpus 0-1  --net none --rm busybox
$cat /sys/fs/cgroup/cpuset/docker/CID/cpuset.cpus
0-1
$cat /sys/fs/cgroup/cpuset/docker/CID/cgroup.procs
4516 # sh pid
$ cat /sys/fs/cgroup/cpuset/docker/CID/cgroup.procs

Actual result
$docker run -tid --runtime runc  --cpuset-cpus 0-1  --net none --rm busybox
$cat /sys/fs/cgroup/cpuset/docker/CID/cpuset.cpus
0-1
$cat /sys/fs/cgroup/cpuset/docker/CID/cgroup.procs
4516 # shim pid
4518 # qemu pid
$ cat /sys/fs/cgroup/cpuset/docker/CID/cgroup.procs
4516 # shim pid
4518 # qemu pid

Note: Given that qemu is a share resource this it may be needed to add to a special cgroup were all the containers cgroup is merged in one. See #1125 , for short term this will be implemented as today cpu cgroup on host.

(replace this text with the output of the kata-collect-data.sh script, after
you have reviewed its content to ensure it does not contain any private
information).

fixed https://github.com/kata-containers/runtime/pull/1189


[Issue 246.2][Try #2] GUI: Added the Pop-up attribute box

Added attribute pop-up box
Edit / Delete Button
Confirm Changes / Cancel Button
All button functionalities

LGTM 👍


chore: 🤖 remove dist/ from repo

Remove dist/ from repo, this will generate by npm run build job.
And I replace prepublishOnly task with prepare, which will automatically run after npm ci/install, and run before npm pack/publish. See: https://docs.npmjs.com/cli/v8/using-npm/scripts#prepare-and-prepublish
So both npm publish and npm install "git://github.com/tokenScript/token-negotiator.git#staging" should work.
And I set "files": ["dist/"] in package.json, which will limit npm package only contains dist/ directory and package.json.
After all, this should fix CI https://github.com/TokenScript/token-negotiator-examples/pull/96

@abcfy2 thanks. Let's test this out 👍


Use Math.hypot + various fixes

All the changes:

Use Math.hypot
Fix context parameter name in isTextElement function
Remove unused code
Use block scope everywhere

Since ES2015 feature Math.imul is used in a code base already, it should be fine to use Math.hypot also.
Should the target in tsconfig be "es2015"?

Line break change in package.json is made by prettier

Actually, let me merge this, we can do the elements changes in another PR


refactor: fix missing abstract directive for date-selection-model

We recently fixed all missing abstract directive decorators in
the components repo. Unfortunately though, the PR was not based
on top of the datepicker that landed while the PR was waiting
for merge. This means that master currently fails, and this commit
fixes the lint failure.

Adding preserve commits so that we could potentially have this merged fast-forward. This would help us as the framework components repo job will just point to the SHA of this commit.


Scalars wiki page shows extension of NoopSchemaGeneratorHooks but NoopSchemaGeneratorHooks is internal

Should probably be extending SchemaGeneratorHooks?

Updated, Thank you! https://github.com/ExpediaDotCom/graphql-kotlin/wiki/Scalars


Respect @static prune in deploys

Architect allows for static asset pruning with the command arc deploy --static --prune (or @static prune) – this feature removes unused files from S3. We should support this in Begin!

/cc @andyweiss1982

@static prune is now live, and enabled by default! https://docs.begin.com/en/static-assets/working-with-static-assets#other-static-asset-options