ci: test Node.js v16

https://nodejs.org/en/about/releases/
v16 is LTS since 2021-10-26

It seems in the last run it failed because of cancellation after 20 minutes instead:
Error: The operation was canceled.

@janpio FWIW, I restarted the cancelled pipeline and now it crashed with OOM on Node.js 16 again.

Been a long time since I was happy about getting an OOM 🤣

Even 2 GB is not enough, it seems 😄

For what it's worth we're seeing a memory leak in Snaplet on Node16 as well.

@peterp With which version of Prisma?


Feature: Window status entities should be a sensor and not a switch on models that do not support remote windows control

I second this. Toggling switches gives error:
saic-mqtt-gateway    | Traceback (most recent call last):
saic-mqtt-gateway    |   File "/usr/src/app/./mqtt_gateway.py", line 391, in handle_mqtt_command
saic-mqtt-gateway    |     await self.vehicle_state.configure_by_message(topic=topic, payload=payload)
saic-mqtt-gateway    |   File "/usr/src/app/vehicle.py", line 579, in configure_by_message
saic-mqtt-gateway    |     raise MqttGatewayException(f'Unsupported topic {topic}')
saic-mqtt-gateway    | exceptions.MqttGatewayException: Unsupported topic windows/sunRoof


New Bernoulli get "Object reference not set to an instance of an object."

Python:
>>> from torch.distributions import Categorical
>>> import torch as th
>>> th.manual_seed(1)
>>> nSamples = int(5e6)
>>> actionLogits = th.rand(nSamples, 2)
>>> distribution = Bernoulli(logits=actionLogits)

C#
using TorchSharp;
using TorchSharp.Modules;
using static TorchSharp.torch;

int nSamples = Convert.ToInt32(5e6);
random.manual_seed(1);
Tensor actionLogits = rand(nSamples, 2);
Bernoulli distribution = new(l: actionLogits);
# System.NullReferenceException: 'Object reference not set to an instance of an object.'

@ChengYen-Tang -- thanks for your bug reports, and for the small repos you posted. That always helps me get to a resolution faster.

Hope this project is more perfect.

I have verified the bug. Unfortunately, it will need a version update on NuGet in order to be addressed. In the meantime, you can work around it by using probs instead of logits to create the distribution. Not sure that works for you, but that's the current workaround.

Thanks, I can develop other things first and wait for the package update


Can you add support of "i" tag?

For example, to show play icon (we can use spans though)
<i class="icon-play"></i>

This was fixed by https://github.com/kriszyp/alkali/commit/31245b5eb59e8c660c15cd8e3bf8bc39aa339f05 and is in v0.11.1.


Sorta off topic but...

How long have you been designing websites @mastercoms and did you make Circuitsoft one? and is that a registered non profit or business I think I saw it somewhere but im not 100% sure. I feel like I did.

I have been designing websites for 3 years and I did make the CircuitSoft one. We're registering as a non profit, but we have not yet. If you would like to continue with this discussion, I can be reached at circuitsoft @ openmailbox.org.


chore(papyrus_node): use get_packaget_dir instead of env var

Stack:

#2403
#2402
#2401
#2400 ⬅
#2399
#2398
#2395
#2394

⚠ Part of a stack created by spr. Do not merge manually using the UI - doing so may have unexpected results.

This change is


Intentions SPOA gives expected capabilities error

Currently, the SPOA that checks Intentions is giving me an error when a request is received:
echo_1           | time="2019-09-18T20:02:40Z" level=info msg="spoe: hello from @: map[capabilities:pipelining engine-id:54DB81E3-F4EA-4899-BE8D-5F6F1EC62A1A max-frame-size:16380 supported-versions:2.0]"
echo_1           | time="2019-09-18T20:02:40Z" level=error msg="spoe: error handling connection: hello: expected capabilities [async pipelining]"
echo_1           | <IP_ADDRESS>:52874 | GET /
echo_1           | time="2019-09-18T20:02:40Z" level=info msg="spoe: hello from @: map[capabilities:pipelining engine-id:54DB81E3-F4EA-4899-BE8D-5F6F1EC62A1A max-frame-size:16380 supported-versions:2.0]"

Hi Nick,
This looks like related to this: https://github.com/criteo/haproxy-spoe-go/issues/3
Please enforce nbthread to 1 for now

Okay, the connector is generating this in the haproxy configuration:
master-worker
  nbproc 1
  nbthread 4

Yes, setting nbthread to 1 fixes the error. To do that, I can set the environment variable GOMAXPROCS = 1 and it sets nbthread to 1.

Ok cool.
I know @Aestek is aware of the problem and will fix it ;)


@TODO Error: eth_newFilter is not an allowed method, code: -32601 leads to exceeding relayer quota

Task: Migration of ethersV5 -> ethersV6
Library versions:

"@openzeppelin/defender-sdk": "1.14.2",
"ethers": "6.13.1",

Token contract event https://sepolia.etherscan.io/address/0x2A85Be1391EA0AADA22582995Fa79D753657839e#events
Code:
import { Defender, DefenderOptions } from '@openzeppelin/defender-sdk'
import { Token__factory } from 'contracts-v5.0.1'
import { env } from 'env/server'

function getContractEvent() {
  const credentials: DefenderOptions = {
    relayerApiKey: env.DEFENDER_API_KEY,
    relayerApiSecret: env.DEFENDER_API_SECRET,
  }

  const client = new Defender(credentials)
  const provider = client.relaySigner.getProvider({ ethersVersion: 'v6' })

  const tokenContract = Token__factory.connect('0x2A85Be1391EA0AADA22582995Fa79D753657839e', provider)

  void tokenContract.once(tokenContract.getEvent('FeeSettingsChanged'), () => {
    console.log('FeeSettingsChanged event')
  })
}

Error:
@TODO DefenderApiResponseError: Request failed with status code 403
    at rejectWithDefenderApiError (/Users/xxx/Projects/project/node_modules/@openzeppelin/defender-sdk-base-client/lib/api/api.js:10:27)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async Axios.request (/Users/xxx/Projects/project/node_modules/axios/dist/node/axios.cjs:4219:14)
    at async /Users/xxx/Projects/project/node_modules/@openzeppelin/defender-sdk-relay-signer-client/lib/api/index.js:70:21
    at async RelaySignerClient.withRetry (/Users/xxx/Projects/project/node_modules/@openzeppelin/defender-sdk-base-client/lib/api/client.js:86:20)
    at async RelaySignerClient.withRetry (/Users/xxx/Projects/project/node_modules/@openzeppelin/defender-sdk-base-client/lib/api/client.js:111:17)
    at async RelaySignerClient.withRetry (/Users/xxx/Projects/project/node_modules/@openzeppelin/defender-sdk-base-client/lib/api/client.js:111:17)
    at async RelaySignerClient.withRetry (/Users/xxx/Projects/project/node_modules/@openzeppelin/defender-sdk-base-client/lib/api/client.js:111:17)
    at async DefenderRelayProvider.send (/Users/xxx/Projects/project/node_modules/@openzeppelin/defender-sdk-relay-signer-client/lib/ethers/provider.js:51:28)
    at async FilterIdEventSubscriber._subscribe (/Users/xxx/Projects/project/node_modules/@openzeppelin/defender-sdk-relay-signer-client/node_modules/ethers/lib.commonjs/providers/subscriber-filterid.js:154:26)
    at Axios.request (/Users/xxx/Projects/project/node_modules/axios/dist/node/axios.cjs:4224:41)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async /Users/xxx/Projects/project/node_modules/@openzeppelin/defender-sdk-relay-signer-client/lib/api/index.js:70:21
    at async RelaySignerClient.withRetry (/Users/xxx/Projects/project/node_modules/@openzeppelin/defender-sdk-base-client/lib/api/client.js:86:20)
    at async RelaySignerClient.withRetry (/Users/xxx/Projects/project/node_modules/@openzeppelin/defender-sdk-base-client/lib/api/client.js:111:17)
    at async RelaySignerClient.withRetry (/Users/xxx/Projects/project/node_modules/@openzeppelin/defender-sdk-base-client/lib/api/client.js:111:17)
    at async RelaySignerClient.withRetry (/Users/xxx/Projects/project/node_modules/@openzeppelin/defender-sdk-base-client/lib/api/client.js:111:17)
    at async DefenderRelayProvider.send (/Users/xxx/Projects/project/node_modules/@openzeppelin/defender-sdk-relay-signer-client/lib/ethers/provider.js:51:28)
    at async FilterIdEventSubscriber._subscribe (/Users/xxx/Projects/project/node_modules/@openzeppelin/defender-sdk-relay-signer-client/node_modules/ethers/lib.commonjs/providers/subscriber-filterid.js:154:26)
    at async #poll (/Users/xxx/Projects/project/node_modules/@openzeppelin/defender-sdk-relay-signer-client/node_modules/ethers/lib.commonjs/providers/subscriber-filterid.js:66:28) {
  request: { path: '/v2/relayers/self/jsonrpc', method: 'POST' },
  response: {
    status: 403,
    statusText: 'Forbidden',
    data: {
      message: "'eyJra...' not a valid key=value pair (missing equal-sign) in Authorization header: 'Bearer eyJra...'."
    }
  }
}

When using "@openzeppelin/defender-sdk-relay-signer-client": "1.14.1"
function getContractEvent() {
  const credentials: RelayerParams = {
    apiKey: env.DEFENDER_API_KEY,
    apiSecret: env.DEFENDER_API_SECRET,
    authConfig: { type: 'relay', useCredentialsCaching: false },
  }

  const provider = new DefenderRelayProvider(credentials)

  const tokenContract = Token__factory.connect('0x2A85Be1391EA0AADA22582995Fa79D753657839e', provider)

  void tokenContract.once(tokenContract.getEvent('FeeSettingsChanged'), () => {
    console.log('FeeSettingsChanged event')
  })
}

I'm getting a different version of the error:
@TODO Error: eth_newFilter is not an allowed method
    at DefenderRelayProvider.send (/Users/xxx/Projects/project/node_modules/@openzeppelin/defender-sdk-relay-signer-client/lib/ethers/provider.js:54:31)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async FilterIdEventSubscriber._subscribe (/Users/xxx/Projects/project/node_modules/@openzeppelin/defender-sdk-relay-signer-client/node_modules/ethers/lib.commonjs/providers/subscriber-filterid.js:154:26)
    at async #poll (/Users/xxx/Projects/project/node_modules/@openzeppelin/defender-sdk-relay-signer-client/node_modules/ethers/lib.commonjs/providers/subscriber-filterid.js:66:28) {
  code: -32601,
  data: undefined
}

The main problem is that the provider is trying to retry the call every few seconds (also querying eth_blockNumber multiple times), which leads to exceeding the Relayer query quota of 10 000 requests.
The reading of the event works if using the JsonRpcProvider.  (It also worked when using ethersV5 and DefenderRelayProviderV5)
function getContractEvent() {
  const provider = new ethers.JsonRpcProvider('https://rpc.sepolia.org', undefined, { staticNetwork: true })

  const tokenContract = Token__factory.connect('0x2A85Be1391EA0AADA22582995Fa79D753657839e', provider)

  void tokenContract.once(tokenContract.getEvent('FeeSettingsChanged'), () => {
    console.log('FeeSettingsChanged event')
  })
}

Hi @patriksulak - Apologies that you were seeing the issue. Thank you for reporting it. We had a bug in 1.14.2  version on calling specific endpoints, we deprecated it and pushed a fix with 1.14.3.
Regarding eth_newFilter is not an allowed method We blacklisted several filter methods couple years back mainly due to our third party json rpc providers not supporting it. We tested to see if all the providers support it now and removed the methods from blacklist and patched our backend.
Please use 1.14.3 and see if it resolves the issue for you. We will look into retry logic on quota consumption.

Thanks for the reply.
Using @openzeppelin/defender-sdk-relay-signer-client": "1.14.3", but I'm getting stuck on the other issue:
Following error:
@TODO Error: eth_getFilterChanges is not an allowed method
    at DefenderRelayProvider.send (/Users/xxx/Projects/project/node_modules/@openzeppelin/defender-sdk-relay-signer-client/lib/ethers/provider.js:54:31)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async #poll (/Users/xxx/Projects/project/node_modules/@openzeppelin/defender-sdk-relay-signer-client/node_modules/ethers/lib.commonjs/providers/subscriber-filterid.js:90:28) {
  code: -32601,
  data: undefined
}

Provider debug log:
{
  action: 'response',
  request: {
    method: 'eth_getFilterChanges',
    params: [ '0x4200000000000000f00ad60e4627c44e4a0c' ]
  },
  response: {
    id: 35,
    jsonrpc: '2.0',
    result: null,
    error: {
      code: -32601,
      message: 'eth_getFilterChanges is not an allowed method'
    }
  },
  provider: DefenderRelayProvider {
    credentials: {
      apiKey: 'zzz',
      apiSecret: 'xxx',
      authConfig: { type: 'relay', useCredentialsCaching: true }
    },
    pendingNetwork: null,
    relayer: Relayer {
      credentials: {
        apiKey: 'zzz',
        apiSecret: 'xxx',
        authConfig: { type: 'relay', useCredentialsCaching: true }
      },
      relayer: RelaySignerClient {
        apiKey: 'zzz',
        apiSecret: 'xxx',
        httpsAgent: undefined,
        retryConfig: { retries: 3, retryDelay: [Function: exponentialDelay] },
        authConfig: { type: 'relay', useCredentialsCaching: true },
        jsonRpcRequestNextId: 36,
        sessionV2: {
          apiKey: 'zzz',
          refreshToken: 'eyJjdxxx',
          accessToken: 'eyJraWxxx'
        },
        api: [Function: wrap] {
          constructor: [Function: wrap],
          request: [Function: wrap],
          _request: [Function: wrap],
          getUri: [Function: wrap],
          delete: [Function: wrap],
          get: [Function: wrap],
          head: [Function: wrap],
          options: [Function: wrap],
          post: [Function: wrap],
          postForm: [Function: wrap],
          put: [Function: wrap],
          putForm: [Function: wrap],
          patch: [Function: wrap],
          patchForm: [Function: wrap],
          defaults: {
            transitional: {
              silentJSONParsing: true,
              forcedJSONParsing: true,
              clarifyTimeoutError: false
            },
            adapter: [ 'xhr', 'http' ],
            transformRequest: [ [Function: transformRequest] ],
            transformResponse: [ [Function: transformResponse] ],
            timeout: 0,
            xsrfCookieName: 'XSRF-TOKEN',
            xsrfHeaderName: 'X-XSRF-TOKEN',
            maxContentLength: -1,
            maxBodyLength: -1,
            env: {
              FormData: [Function: FormData] {
                LINE_BREAK: '\r\n',
                DEFAULT_CONTENT_TYPE: 'application/octet-stream'
              },
              Blob: [class Blob]
            },
            validateStatus: [Function: validateStatus],
            headers: {
              common: {
                Accept: 'application/json, text/plain, */*',
                'Content-Type': undefined
              },
              delete: {},
              get: {},
              head: {},
              post: {},
              put: {},
              patch: {},
              'Content-Type': 'application/json',
              'X-Api-Key': 'zzz',
              Authorization: 'Bearer xxx'
            },
            baseURL: 'https://api.defender.openzeppelin.com/'
          },
          interceptors: {
            request: InterceptorManager { handlers: [] },
            response: InterceptorManager {
              handlers: [
                {
                  fulfilled: [Function (anonymous)],
                  rejected: [Function: rejectWithDefenderApiError],
                  synchronous: false,
                  runWhen: null
                }
              ]
            }
          },
          create: [Function: create]
        }
      }
    }
  }
}

Hi @patriksulak - We still have couple of blacklisted methods "eth_getFilterChanges" & "eth_uninstallFilter". Wondering if you will be using these frequently. We were planning on removing those based on the usage of these methods. If you will be using these we will look into whitelisting these as well and given these are supported by providers now it's fair to whitelist them as well.

Thanks for the reply.
Using @openzeppelin/defender-sdk-relay-signer-client": "1.14.3", but I'm getting stuck on the other issue:
Following error:
@TODO Error: eth_getFilterChanges is not an allowed method
    at DefenderRelayProvider.send (/Users/xxx/Projects/project/node_modules/@openzeppelin/defender-sdk-relay-signer-client/lib/ethers/provider.js:54:31)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async #poll (/Users/xxx/Projects/project/node_modules/@openzeppelin/defender-sdk-relay-signer-client/node_modules/ethers/lib.commonjs/providers/subscriber-filterid.js:90:28) {
  code: -32601,
  data: undefined
}

Hi @patriksulak - Could you please try one more time and see if it resolves the issue for you. Pushed a patch to remove all blacklisted methods in the backend.

Hi @patriksulak - Could you please try one more time and see if it resolves the issue for you. Pushed a patch to remove all blacklisted methods in the backend.

@tirumerla tried again, but got another error:
@TODO Error: network is not available yet (code=NETWORK_ERROR, version=6.13.1)
    at makeError (/Users/xxxxx/Projects/project/node_modules/@openzeppelin/defender-sdk-relay-signer-client/node_modules/ethers/lib.commonjs/utils/errors.js:129:21)
    at assert (/Users/xxxxx/Projects/project/node_modules/@openzeppelin/defender-sdk-relay-signer-client/node_modules/ethers/lib.commonjs/utils/errors.js:149:15)
    at get _network [as _network] (/Users/xxxxx/Projects/project/node_modules/@openzeppelin/defender-sdk-relay-signer-client/node_modules/ethers/lib.commonjs/providers/provider-jsonrpc.js:361:31)
    at FilterIdEventSubscriber._emitResults (/Users/xxxxx/Projects/project/node_modules/@openzeppelin/defender-sdk-relay-signer-client/node_modules/ethers/lib.commonjs/providers/subscriber-filterid.js:159:75)
    at #poll (/Users/xxxxx/Projects/project/node_modules/@openzeppelin/defender-sdk-relay-signer-client/node_modules/ethers/lib.commonjs/providers/subscriber-filterid.js:91:24)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
  code: 'NETWORK_ERROR',
  shortMessage: 'network is not available yet'
}

Hi @patriksulak - Could you please try one more time and see if it resolves the issue for you. Pushed a patch to remove all blacklisted methods in the backend.

@tirumerla tried again, but got another error:
@TODO Error: network is not available yet (code=NETWORK_ERROR, version=6.13.1)
    at makeError (/Users/xxxxx/Projects/project/node_modules/@openzeppelin/defender-sdk-relay-signer-client/node_modules/ethers/lib.commonjs/utils/errors.js:129:21)
    at assert (/Users/xxxxx/Projects/project/node_modules/@openzeppelin/defender-sdk-relay-signer-client/node_modules/ethers/lib.commonjs/utils/errors.js:149:15)
    at get _network [as _network] (/Users/xxxxx/Projects/project/node_modules/@openzeppelin/defender-sdk-relay-signer-client/node_modules/ethers/lib.commonjs/providers/provider-jsonrpc.js:361:31)
    at FilterIdEventSubscriber._emitResults (/Users/xxxxx/Projects/project/node_modules/@openzeppelin/defender-sdk-relay-signer-client/node_modules/ethers/lib.commonjs/providers/subscriber-filterid.js:159:75)
    at #poll (/Users/xxxxx/Projects/project/node_modules/@openzeppelin/defender-sdk-relay-signer-client/node_modules/ethers/lib.commonjs/providers/subscriber-filterid.js:91:24)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
  code: 'NETWORK_ERROR',
  shortMessage: 'network is not available yet'
}

Could you please send me the payload for the request and the network details. I tested using your previous payload ( eth_getFilterChanges ) that seemed to work fine/ got back the response ok. If you could share the request details will try to reproduce and check it out.

Could you please send me the payload for the request and the network details. I tested using your previous payload ( eth_getFilterChanges ) that seemed to work fine/ got back the response ok. If you could share the request details will try to reproduce and check it out.

The whole debug log from the provider:
{
  action: 'response',
  request: {
    method: 'eth_getCode',
    params: [ '0x70997970c51812dc3a010c7d01b50e0d17dc79c8', 'latest' ]
  },
  response: { id: 3, jsonrpc: '2.0', result: '0x' },
  provider: DefenderRelayProvider {
    credentials: {
      apiKey: 'xxx',
      apiSecret: 'zzz',
      authConfig: { type: 'relay', useCredentialsCaching: true }
    },
    pendingNetwork: null,
    relayer: Relayer {
      credentials: {
        apiKey: 'xxx',
        apiSecret: 'zzz',
        authConfig: { type: 'relay', useCredentialsCaching: true }
      },
      relayer: RelaySignerClient {
        apiKey: 'xxx',
        apiSecret: 'zzz',
        httpsAgent: undefined,
        retryConfig: { retries: 3, retryDelay: [Function: exponentialDelay] },
        authConfig: { type: 'relay', useCredentialsCaching: true },
        jsonRpcRequestNextId: 5,
        sessionV2: {
          apiKey: 'xxx',
          refreshToken: 'eyJ...',
          accessToken: 'eyJ...'
        },
        api: [Function: wrap] {
          constructor: [Function: wrap],
          request: [Function: wrap],
          _request: [Function: wrap],
          getUri: [Function: wrap],
          delete: [Function: wrap],
          get: [Function: wrap],
          head: [Function: wrap],
          options: [Function: wrap],
          post: [Function: wrap],
          postForm: [Function: wrap],
          put: [Function: wrap],
          putForm: [Function: wrap],
          patch: [Function: wrap],
          patchForm: [Function: wrap],
          defaults: {
            transitional: {
              silentJSONParsing: true,
              forcedJSONParsing: true,
              clarifyTimeoutError: false
            },
            adapter: [ 'xhr', 'http' ],
            transformRequest: [ [Function: transformRequest] ],
            transformResponse: [ [Function: transformResponse] ],
            timeout: 0,
            xsrfCookieName: 'XSRF-TOKEN',
            xsrfHeaderName: 'X-XSRF-TOKEN',
            maxContentLength: -1,
            maxBodyLength: -1,
            env: {
              FormData: [Function: FormData] {
                LINE_BREAK: '\r\n',
                DEFAULT_CONTENT_TYPE: 'application/octet-stream'
              },
              Blob: [class Blob]
            },
            validateStatus: [Function: validateStatus],
            headers: {
              common: {
                Accept: 'application/json, text/plain, */*',
                'Content-Type': undefined
              },
              delete: {},
              get: {},
              head: {},
              post: {},
              put: {},
              patch: {},
              'Content-Type': 'application/json',
              'X-Api-Key': 'xxx',
              Authorization: 'Bearer eyJr...'
            },
            baseURL: 'https://api.defender.openzeppelin.com/'
          },
          interceptors: {
            request: InterceptorManager { handlers: [] },
            response: InterceptorManager {
              handlers: [
                {
                  fulfilled: [Function (anonymous)],
                  rejected: [Function: rejectWithDefenderApiError],
                  synchronous: false,
                  runWhen: null
                }
              ]
            }
          },
          create: [Function: create]
        }
      }
    }
  }
}

The logs without provider:
{
  action: 'request',
  request: {
    method: 'eth_newFilter',
    params: [
      {
        topics: [
          '0xc6bb007d5073aca60e38964dbf6930bee55f9c8cacae4019360cadf88110a54f'
        ],
        address: [ '0xdfc0b38e30b62e345a30938c5266b52e51affabf' ]
      }
    ]
  },
}
{
  action: 'response',
  request: {
    method: 'eth_newFilter',
    params: [
      {
        topics: [
          '0xc6bb007d5073aca60e38964dbf6930bee55f9c8cacae4019360cadf88110a54f'
        ],
        address: [ '0xdfc0b38e30b62e345a30938c5266b52e51affabf' ]
      }
    ]
  },
  response: {
    id: 23,
    jsonrpc: '2.0',
    result: '0x2402000000000000984148e62ae2f998615d'
  },
}
{
  action: 'request',
  request: { method: 'eth_chainId', params: [] },
}
{
  action: 'response',
  request: { method: 'eth_chainId', params: [] },
  response: { id: 24, jsonrpc: '2.0', result: '0xaa36a7' },
}
{ action: 'receiveRpcResult', result: '0xaa36a7', provider: 'xxx' }
{
  action: 'request',
  request: {
    method: 'eth_getFilterChanges',
    params: [ '0x2402000000000000984148e62ae2f998615d' ]
  },
}
{
  action: 'response',
  request: {
    method: 'eth_getFilterChanges',
    params: [ '0x2402000000000000984148e62ae2f998615d' ]
  },
  response: { id: 25, jsonrpc: '2.0', result: [] },
}
{
  action: 'request',
  request: { method: 'eth_blockNumber', params: [] },
}
{
  action: 'response',
  request: { method: 'eth_blockNumber', params: [] },
  response: { id: 26, jsonrpc: '2.0', result: '0x613e26' },
}
{
  action: 'request',
  request: { method: 'eth_blockNumber', params: [] },
}
{
  action: 'response',
  request: { method: 'eth_blockNumber', params: [] },
  response: { id: 27, jsonrpc: '2.0', result: '0x613e26' },
}
{
  action: 'request',
  request: { method: 'eth_blockNumber', params: [] },
}
{
  action: 'response',
  request: { method: 'eth_blockNumber', params: [] },
  response: { id: 28, jsonrpc: '2.0', result: '0x613e27' },
}
{
  action: 'request',
  request: { method: 'eth_chainId', params: [] },
}
{
  action: 'response',
  request: { method: 'eth_chainId', params: [] },
  response: { id: 29, jsonrpc: '2.0', result: '0xaa36a7' },
}
{ action: 'receiveRpcResult', result: '0xaa36a7', provider: 'xxx' }
{
  action: 'request',
  request: {
    method: 'eth_getFilterChanges',
    params: [ '0x2402000000000000984148e62ae2f998615d' ]
  },
}
{
  action: 'response',
  request: {
    method: 'eth_getFilterChanges',
    params: [ '0x2402000000000000984148e62ae2f998615d' ]
  },
  response: {
    id: 30,
    jsonrpc: '2.0',
    result: [
      {
        address: '0xdfc0b38e30b62e345a30938c5266b52e51affabf',
        topics: [
          '0xc6bb007d5073aca60e38964dbf6930bee55f9c8cacae4019360cadf88110a54f',
          '0x000000000000000000000000f64bd9d1b65daf7a57bd1c2ab84acbcf3c6b5438'
        ],
        data: '0x',
        blockNumber: '0x613e27',
        transactionHash: '0x8e8cb6b14bf5cbcbf3cc2506fc649e9723a674df912a31970e9a6eecfca51706',
        transactionIndex: '0xc',
        blockHash: '0xbd58311e9c4376492ff37c14986c9f53f69d36a8d16c9e186491881f65419ae8',
        logIndex: '0x9',
        removed: false
      }
    ]
  },
}
@TODO Error: network is not available yet (code=NETWORK_ERROR, version=6.13.1)
    at makeError (/Users/xxx/Projects/project/node_modules/@openzeppelin/defender-sdk-relay-signer-client/node_modules/ethers/lib.commonjs/utils/errors.js:129:21)
    at assert (/Users/xxx/Projects/project/node_modules/@openzeppelin/defender-sdk-relay-signer-client/node_modules/ethers/lib.commonjs/utils/errors.js:149:15)
    at get _network [as _network] (/Users/xxx/Projects/project/node_modules/@openzeppelin/defender-sdk-relay-signer-client/node_modules/ethers/lib.commonjs/providers/provider-jsonrpc.js:361:31)
    at FilterIdEventSubscriber._emitResults (/Users/xxx/Projects/project/node_modules/@openzeppelin/defender-sdk-relay-signer-client/node_modules/ethers/lib.commonjs/providers/subscriber-filterid.js:159:75)
    at #poll (/Users/xxx/Projects/project/node_modules/@openzeppelin/defender-sdk-relay-signer-client/node_modules/ethers/lib.commonjs/providers/subscriber-filterid.js:91:24)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
  code: 'NETWORK_ERROR',
  shortMessage: 'network is not available yet'
}
{
  action: 'request',
  request: { method: 'eth_blockNumber', params: [] },
}
{
  action: 'response',
  request: { method: 'eth_blockNumber', params: [] },
  response: { id: 31, jsonrpc: '2.0', result: '0x613e27' },
}
{
  action: 'request',
  request: { method: 'eth_blockNumber', params: [] },
}
{
  action: 'response',
  request: { method: 'eth_blockNumber', params: [] },
  response: { id: 32, jsonrpc: '2.0', result: '0x613e27' },
}
{
  action: 'request',
  request: { method: 'eth_blockNumber', params: [] },
}
{
  action: 'response',
  request: { method: 'eth_blockNumber', params: [] },
  response: { id: 33, jsonrpc: '2.0', result: '0x613e28' },
}
{
  action: 'request',
  request: { method: 'eth_chainId', params: [] },
}

and the eth_blockNumber is requested every 2-3 seconds until closing the server or exceeding the Relayer query quota limits.

Hi @patriksulak this seems to be a race condition where the provider tries send some rpc call and the network is still not loaded, would you mind sharing a code snippet along with the dependencies versions you are using?
If its private code, please send it to our support email<EMAIL_ADDRESS>And we will investigate the bug, thanks!


make fastdp work with large MTUs on 4.3/4.4 kernels

To address the MTU problem listed in #1853 for 4.3 and 4.4 kernels we could allow a user to pass a netdev interface name. The interface would be used as a VTEP (lowerdev) for VXLAN netdev we create. The VXLAN netdev inherits a MTU of its lowerdev, thus the hard limit for 1500 MTU is no longer the issue.
A downside of such approach is that removal of lowerdev might cause deletion of vxlan device (https://github.com/torvalds/linux/blob/v4.4/drivers/net/vxlan.c#L3146)
To implement this, we need to change the way we create vxlan-vport in router/fastdp.go:

Create a VXLAN via netlink
Create a VPort on datapath
Assign VXLAN to the VPort

Considering that the 4.4 kernel is still actively being used, I'd keep it open.

modprobe: module br_netfilter not found in modules.dep
Ignore the error if "br_netfilter" is built-in in the kernel
DEBU: 2019/08/30 09:35:28.392840 [kube-peers] Checking peer "b6:fd:87:9b:de:11" against list &{[{da:9a:60:e7:ab:f9 k8s-master02} {42:25:fe:0d:8a:aa k8s-node01} {b6:fd:87:9b:de:11 k8s-master04} {36:ee:00:02:58:df k8s-master03} {56:26:ba:e4:b7:57 k8s-node07} {da:3b:12:d8:b8:52 k8s-master05} {9e:7a:5b:26:84:ea k8s-node03} {2a:3a:73:2c:76:28 k8s-node05} {26:d7:16:ce:05:1a k8s-master01} {72:e5:bc:30:94:62 k8s-node04} {42:cb:95:cd:02:1d k8s-node06} {1a:2c:7e:3d:f6:04 k8s-node02} {7a:4d:c6:35:91:0c k8s-ingress02} {16:c8:13:e7:77:6e k8s-ingress01}]}
INFO: 2019/08/30 09:35:28.507827 Command line options: map[datapath:datapath ipalloc-range:<IP_ADDRESS>/21 metrics-addr:<IP_ADDRESS>:6782 no-dns:true port:6783 docker-api: http-addr:<IP_ADDRESS>:6784 name:b6:fd:87:9b:de:11 nickname:k8s-master04 host-root:/host ipalloc-init:consensus=14 conn-limit:100 db-prefix:/weavedb/weave-net expect-npc:true]
INFO: 2019/08/30 09:35:28.507882 weave  2.5.2
INFO: 2019/08/30 09:35:28.580902 Bridge type is bridged_fastdp
INFO: 2019/08/30 09:35:28.580930 Communication between peers is unencrypted.
WARN: 2019/08/30 09:35:28.603825 Address already in use creating vxlan vport 6784 - retrying
WARN: 2019/08/30 09:35:28.637836 Address already in use creating vxlan vport 6784 - retrying
WARN: 2019/08/30 09:35:28.667726 Address already in use creating vxlan vport 6784 - retrying
WARN: 2019/08/30 09:35:28.697736 Address already in use creating vxlan vport 6784 - retrying
WARN: 2019/08/30 09:35:28.729766 Address already in use creating vxlan vport 6784 - retrying
FATA: 2019/08/30 09:35:28.739927 netlink error response: address already in use

hello, we run weave:2.5.2 in k8s:1.14.3,and want to use fastdp which what above happened.Is this same problem? wish your help,tks.


BRDF Explorer project

This issue is meant to discuss software functions of BRDF Explorer.
Rendering algorithms will be discussed in #276.

[x] ~Include script file to clone my CEGUI branch as git submodule~
[x] ~Apply @Florastamine's theme patch~
[x] Push submodules online
[x] Build CEGUI dependencies
[x] Build CEGUI
[x] Add new IrrlichtBAW example 13.BRDF_Explorer
[x] Write CEGUI management class in ext namespace to init/destroy/render GUI
[x] Install CEGUI headers to INSTALL_PATH/include/irr/ext/CEGUI
[x] Port MainWindow layout
[ ] Port ColorPicker
[ ] Implement IrrBAW CEGUI texture loader in ext namespace
[ ] Patch CEGUI to upload sRGB (issue #263)
[ ] Render a simple model
[ ] More rendering features based on #276
[ ] Refactor Helpers
[ ] Solve comment https://github.com/buildaworldnet/IrrlichtBAW/pull/291#discussion_r282012784, https://github.com/buildaworldnet/IrrlichtBAW/pull/291#discussion_r282012245
[ ] Relocate submodules into 3rdparty
[ ] Compile cegui ext as static lib
[ ] Build dependencies on Linux instead of requiring user to install via apt

Note: For cloning CEGUI on Windows, Python folder should be added into PATH environment variable. For example it's OK if you can call python from CMD. Python 2 is required for this script to treat Mercurial repo with Git.
Asking approval from @devshgraphicsprogramming and @Crisspl, or else we can download a latest, compressed CEGUI branch before building from these links, but that's a little hard for updating CEGUI.

Python 2 (I have 3 but cmake is not finding it) seems to be necessary for some of our SPIR-V dependencies to not create disturbing errors when building with MSVC ( #269 ).
I'm all for Python 2 being a dependency, but please please please make CMake on Windows find it if its installed.
If possible I'd use and require Python 3 instead of 2 and solve #269 with Python 2, not 3.
CEGUI submodule can be a 3rdpart module in ./ext/cegui/3rdparty/ that is conditionally updated by CMake script only if the option is specified that we build the examples (there should really be extra cmake option switches for certain examples that rely on big extensions with dependencies).

Write main code file to render the GUI, load a simple model

I don't know where you want to discuss the Functionality-but-not-strictly-Rendering aspects of the task, but generally I would expect this issue to cover the parts of the BRDF Explorer LaTeX specification that are functionality.
Speaking of which I would want the intial sample to handle model loading and have a "stub" graphics-pipline reconfiguration function which actually gets triggered (for cases when we change "heavy" material parameters, such as the parameter source [texture vs constant] and BRDF type ).

One more note, everything to do with the BRDFExplorer should be statically linked into the binary, we don't want a massive folder of dlls to be necessary.
You have my permission to make irr::ext::cegui as a static library with its own build target, if necessary.
Furthermore, if CEGUI needs some skin, font atlas, or other resource that comes from a file which is not "required for BRDFExplorer only". I think the defaults/built-ins should be "resource compiled". Here's a script that supposedly does so
https://github.com/vector-of-bool/cmrc
Again, the XML layout of the GUI specific to BRDFExplorer needs not be embedded in the executable, but the reusable parts I would resource compile into irr::ext::cegui.
https://github.com/vector-of-bool/cmrc

I will update my Windows environment (includes MSVC) and test if Python 3 can be used with the Mercurial script.
About the static linking, I've done it before in my engine so I can guarantee. But I suggest we do static linking for Windows only since it doesn't benefit Linux much.

About CEGUI resource, the reusable part will be stored on my CEGUI branch too so we don't need to duplicate those files in irrbaw.
Resource distribution can also be in a single .zip file (with/without password protection) like in @Florastamine's releases before. Do you really want to compile resources into exe?

After reviewing the CEGUI data, I see that there're data which isn't general enough to get accepted into CEGUI's original branch, so it won't stay in my branch too. I'll manage a separate Git repo of the CEGUI data instead since we'll both use them. Nice CMake to have CEGUI+Data in a build process will be provide.

Stuff like the skins (reusable part) etc can go into ./media/ I'm not completely 100% resource compiled ;)

OK, will have them here.
Update about Python and Mercurial bridge stuff. I will configure on my machine to push from my local cegui to a git repo. So I can have single local and 2 different remotes (bitbucket hg and git). It makes the submodule much easier since I realized that in order to clone from Mercurial:

Python must be installed
A script must be included in irrbaw repo
PATH environment variable (both Linux and Windows) must be modified for git to find that script

In short, these 2 submodules will be added:

CEGUI from our GitLab
CEGUI datafiles to be installed in irrbaw's media folder, maintained by us on GitLab

Wasted half a day to try Hg-Git. Met errors on both Windows & Linux. Tags failed = not pushed anything. Issue reported: https://bitbucket.org/durin42/hg-git/issues/276/failed-to-push-tags
Tried again with this: https://github.com/frej/fast-export. Now I have 2 separate cegui folders and have keep then in sync with single command.
Repos are online at: https://gitlab.com/InnerPieceOSS
Integrating submodules into example app.

CEGUI dependencies now can be downloaded, built and installed to CEGUI. Will write build script for CEGUI tomorrow.

Base project is created. I will spend the day mostly for studying GUI implementation by @Florastamine.

I ported the main window GUI, but fails to compile so I'm waiting for the fix.
Next is to port color picker and finalize UI then we can start rendering. Hopefully in this week.

I meet this on Windows, git doesn't recognize new submodule.

Thought it was a folder so I ignored submodule before. Solved that issue.

Install CEGUI headers to INSTALL_PATH/include/irr/ext/CEGUI

I thought you meant only the CEGUI extension's headers, i.e. the headers which are supposed to be public in irr/ext/cegui (required for compilation of binaries and libraries using it)

ext will only help you set up. In order to develop GUI, you'll have to use CEGUI API too.

ok, but then:
INSTALL_PATH/include/irr/ext/CEGUI is for your own headers
INSTALL_PATH/include/irr/ext/CEGUI/some/other/path` is for cegui's headers

Some initial render, still has layout bug of my port I guess. Will have more updates soon.

Ah the layout is fine, just lacking windows because those are still not ported.
Great!

This is a bug actually, I double-checked it in CEED.
It should be like this.

Fixed by @devshgraphicsprogramming 's suggestion on Discord. This is about OpenGL/Vulkan NDC.
Still need confirmation on its effect on 3D rendering though.
Mouse input works, will test key input too.

@manhnt9 does this help you with your Saga3D renderer?

Oooh, absolutely. Thanks for reminding me about that. I don't remember solving any NDC issue and also my GUI is disappearing somehow. Gonna revisit it soon.

Mouse and key are working fully.

All Sliders, Click to browse events and File Dialogs are working.

Dropdown works.

GUI is 99% done. Next step is to re-test as much as possible and do the rendering.
Then connect GUI data to graphics pipeline.

Current bug:
Having a crash and this error message when clicking to Choose color for testing color picker
15/05/2019 16:35:58 (Error)    CEGUI::UnknownObjectException in function 'CEGUI::NamedElement* CEGUI::NamedElement::getChildElement(const String&) const' (/home/manh/IrrlichtBAW/3rdparty/CEGUI/cegui/cegui/src/NamedElement.cpp:150) : The Element object referenced by 'auto_oldcolourrect' is not attached to Element at 'UIRoot/__cewin_uid_2'.

All GUI controls are tested, working well. Gonna test on Windows.

I'm gonna refactor the build process for CEGUI first then solve pending comments later.

We have perfect build now, Debug/Release works, CEGUI projects are built before building IrrExtCEGUI.
Also found a bug about disappearing cursor in file dialog and fixed it. App has 2 overlapping cursors, CEGUI cursor and native cursor. Native cursor is now only visible for file dialog.

Base project is considered done to me. From now we can add new code consistently.
CEGUI's dependencies will be upgraded later when the Ext is widely used in examples then I'll change it to submodule instead of download and build from .zip. Hope that by the time CEGUI is already moved to Git too.

so do we close this issue?

Still have sRGB tasks left.

Next week I'll merge the loaders, write the image codec for CEGUI, make CEGUI upload textures in SRGB format.

Maybe we should remove the following from the checklist

More rendering features based on #276

so at least we can close issues

if IrrBaW will provide texture loading abilities to CEGUI can we kick out STB, etc?

can you guys manage to fix the crash when the titlebar of the color picker is double-clicked?
(or at least disable any sort of reponse to a double click)

@Crisspl would it make sense to get around our texture flipping issues with:

[ ] Implement IrrBAW CEGUI texture loader in ext namespace
?

Then we kick out STB and not build the CEGUI texture loading lib.
@Crisspl and @Przemog1 at your leisure:

[ ] Patch CEGUI to upload/use sRGB textures (issue #263) right now its rendering with sRGB "reinterpret_cast'ed" as linear, outputting into an SRGB framebuffer . I don't know how much easier the above point would make that.
[ ] Patch the CEGUI color picker to not fucking crash when double clicked

The last two things would be modifcations of the CEGUI submodules which would have to be diff'ed (with your favourite diff tool) into a .patch file that we submit to @manhnt9's branch of CEGUI (since his git repo is kind-of a mirror of a mercurial repo, yes CEGUI people use Hg)

would it make sense to get around our texture flipping issues with:
Implement IrrBAW CEGUI texture loader in ext namespace

You'd have to elaborate.
The only solution im almost sure will work is to separate CEGUI textures and irrbaw textures on the level of GL objects. Still i can't be 100% sure because it also became apparent that this weird behavior affects also textures that cegui doesnt even know about (but simultaneusly there are some shared between irrbaw and cegui). However it worked (textures wasnt flipped) when there was only GUI - no irrbaw textures were shared with cegui nor created at all

To be fair I don't even know how on earth CEGUI could flip textures in the main render window.
It does make most sense for CEGUI textures and our own textures to be separate objects.
(Unless we provided our own GUI Renderer to replace OpenGL core one)


Asset Properties section keeps loading and doesn't display any data

Asset Properties section keeps loading and doesn't display any data
Occurred after adding a 3rd complex property with 3 items.

screen-recording.webm

Already fixed and will be available in the latest build.

Fix is available in the latest uploaded DTM version


add an option for setting a context for the resolver functions

Currently the resolver functions runs in the null context (this variable). Add an option (look for similar options in other libs) to set the context when running the resolver. It defaults to null rather than the context of the resolver class.

This feature is out of scope of this minimalistic library. If one really needs to bind the context, they can use bind() on it before passing it to the renderFn() or renderFnAsync().


Link in day 5 is broken

Hi, started the course a few days ago and I noticed that the link to PyBite 13 that appears in day 5 is broken. I get a 404 error.
Also, I think that the url given in the notebook to retrieve the data is not valid anymore.
Thanks Michael for all that you put out there for people to level up in Python 🙏
I'm a big fan of TalkPythonToMe

Thanks @bluthej, I fixed the link, this happened when we migrated the blog to Wordpress.
The data link works for me:
https://raw.githubusercontent.com/sundeepblue/movie_rating_prediction/master/movie_metadata.csv
This also became free Bite 30 as well, if you want to code it there:
https://codechalleng.es/bites/30/


Where is localPort defined

Hi! Where can I can change the receiving (local) port of the IP of my ESP8266 in UDPSingle example?

I have the same problem. My software server reply to my udp message using a fixed port. I cannot receive data cause esp8266 receive only on the local port that is automatic assigned and opened when udp connection is registered with registerUDP method.

Alternatively which AT commands can be used to manually define the UDP local port to listen to for incoming messages?
Regards


Improve matching query term policy

This improvement motivation is about letting the user customize the behavior of Meilisearch when retrieving documents according to the query words.
Related product discussion

https://github.com/meilisearch/product/discussions/255

Process
💫 This issue will be completed with links and all the necessary information all along the feature creation process

[x] Create PRD, see this file (sorry Meili internal only)
[x] Create a prototype by providing a docker image -> see this discussion
[ ] Apply changes according to feedback
[X] Create the corresponding specification and link it to this issue -> https://github.com/meilisearch/specifications/pull/162

One precision: if the discovery phase (prototype creation + user feedback) is not satisfying, we will postpone this feature addition

The prototype is now available, more details here, please, feel free to give your feedback

The spec is available here: https://github.com/meilisearch/specifications/pull/162

I've added the spec (https://github.com/meilisearch/specifications/pull/173) and the finally dediced API changes

Hello everyone watching this issue!
We have just released v0.29.0rc1, which is a release candidate of v0.29.0 🔥
It means you can test the just-introduced matchingStrategy parameter during the search! Binaries are attached to the release, or you can you the docker image:
docker run -it --rm \
    -p 7700:7700 \
    getmeili/meilisearch:v0.29.0rc0

Let us know about any bugs or feedback! 😄 It would be really helpful.
FYI, the official v0.29.0 release will be available on 3rd October.


enif_cond_wait loop

Awesome job!
Just a quick note to remember, from the docs:

erl_drv_cond_wait can return even if no one has signaled or broadcast on the condition variable. Code calling erl_drv_cond_wait is always to be prepared for erl_drv_cond_wait returning even if the condition that the thread was waiting for has not occurred. That is, when returning from erl_drv_cond_wait, always check if the condition has occurred, and if not call erl_drv_cond_wait again.

So it should be something like:
while (callback_res_result_not_set) {
  enif_cond_wait(callback_res->cond, callback_res->mtx);
}

Thanks @jonatanklosko! I didn't notice this one, I'll push a commit to fix it!


[Backport release-24.05] twitch-chat-downloader: 2.5.3 -> 2.5.4

Description of changes
Updated version since previous version no longer works.
master PR

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Tested on aarch64-linux.


I read most of issues topic about comment, but my comment still doesn't work

https://github.com/taojiangdt/taojiangdt.github.io
Now my comment in production only show a title "Leave a comment", there is an empty area under "Leave a comment" can not input comments. Now, I would like to fix below problems:

how to make comments work in both of 'development',and 'production'?

There is no Netlify file in the mmistakes template, so how to and where is set JEKYLL_ENV=production?
https://github.com/mmistakes/minimal-mistakes/blob/master/_layouts/single.html#L66

Which file to set up below code?
{% if jekyll.environment == "production" %}
{% include disqus.html %}
{% endif %}

I read ticket #1562, and follow below posts:
https://mmistakes.github.io/minimal-mistakes/docs/configuration/#comments
https://jekyllrb.com/docs/configuration/environments/
https://github.com/mmistakes/minimal-mistakes/blob/master/_layouts/single.html#L66
And I also know :
Therefore if you omit JEKYLL_ENV from the build arguments, the default value will be JEKYLL_ENV=development
Please help to work on it, thank you very much!

Netlify lets you set environmental fields. You can add JEKYLL_ENV and production values in either a Netlify config file or under your site dashboard:  Settings > Build & deploy > Environment > Environment variables
https://docs.netlify.com/configure-builds/environment-variables/#declare-variables

Sorry, what is my site dashboard: Settings ? where do I can find my site dashboard?

Log into your Netlify account. There's all sorts of configurations there.

Oh ,Thank you . I don't know should create connection between my site in github and Netlify.
There two questions:

Could you please teach me why do we need to create this connection between github and Netlify?
And I need to Create a new site in Netlify? because my site can't search in Netlify

Thank you

You don't have to create your site with Netlify. I assumed you were deploying that way since you mentioned Netlify above.
If you're using GitHub Pages to build and deploy your site you don't need to set a production environment variable as it does it for you.
I suggest you ask for help in Jekyll various forums. Your questions aren't theme specific and you'll have more success broadening your search.


Lock gems that fail to install on certain Ruby versions

Bundler fails to install several gems. It seems that Ruby version constraint is ignored.
E.g. Sprockets 4.0 depend on Ruby >= 2.5 https://rubygems.org/gems/sprockets/versions/4.0.0
This results in build failures (https://travis-ci.org/github/rspec/rspec-rails/jobs/713253057):
Installing sprockets 4.0.2
Gem::RuntimeRequirementNotMetError: sprockets requires Ruby version >= 2.5.0.
The current ruby version is <IP_ADDRESS>4.

Surprisingly, Ruby 2.3.8 and Ruby 2.2.10 builds don't fail, and install sprockets 3.7.2.
This is a forgotten forward-port from https://github.com/rspec/rspec-rails/pull/2360/files#diff-8c3955be04b733dbd31e54e50844fb84R31

It's like a house of cards.
Fetching capybara 3.33.0
Installing capybara 3.33.0

Gem::RuntimeRequirementNotMetError: capybara requires Ruby version >= 2.5.0. The current ruby version is <IP_ADDRESS>4.

An error occurred while installing capybara (3.33.0), and Bundler cannot continue.

Make sure that `gem install capybara -v '3.33.0' --source 'https://rubygems.org/'` succeeds before bundling.

It also happens quite randomly. This time Ruby 2.4 build broke, but not 2.3 nor 2.2.
Another thing that I've noticed is that Ruby version constraints for some gems differ when you check them on https://rubygems.org/gems//versions/ and then you check it with gem specification --remote <gem> --version <version>. Don't have any example handy, but pretty sure I can find it.
Any newly released gem with a Ruby version constraint can break our build. Do you think those problems are worth Bundler core team attention?

Builds are green. I'm going to delete all repository caches, squash the commits and see if the builds are still green.

👍  Merge on green.

Do you think those problems are worth Bundler core team attention?

Maybe @deivid-rodriguez have an idea? 🙂

This is green, but the question still remains.
@deivid-rodriguez can you suggest what we are doing wrong here?
We run several build jobs, each for a different Ruby/Rails combination. The Gemfile we provide, doesn't specify a version of e.g. i18n, rack, childprocess, capybara to use, it's what we rely on from Rails' Gemfile. On Ruby 2.4 and RAILS_VERSION='~> 5.0.0' (resolved to <IP_ADDRESS>), bundler attempts to install sprockets version 4.0.2 for some reason:
Installing sprockets 4.0.2

Gem::RuntimeRequirementNotMetError: sprockets requires Ruby version >= 2.5.0. The current ruby version is <IP_ADDRESS>4.
An error occurred while installing sprockets (4.0.2), and Bundler cannot continue.
Make sure that `gem install sprockets -v '4.0.2' --source 'https://rubygems.org/'` succeeds before bundling.

In Gemfile:

  rails was resolved to <IP_ADDRESS>, which depends on
    sprockets-rails was resolved to 3.2.1, which depends on
      sprockets

rake aborted!

sprocket-rails 3.2.1 depend on sprockets >= 3.0.0, and sprockets 3.7.2 depend on Ruby >= 1.9.3.
Question: Is it Bundler that is unable to reduce the dependency considering the Ruby version constraint? Or should we look into what Travis' intermediate gem server is providing us with broken gem metadata?
The following versions of RubyGems/Bundler are used:
Bundler 2.1.4 installed
RubyGems 3.1.4 installed

Hi! Thanks for letting me know.
This is indeed an issue with bundler. A long time ago, bundler used a dependency API that didn't have required_ruby_version information. These days bundler uses a better API that does provide required_ruby_version information. However, under some circumstances, specifically, when the client is rate limited by rubygems.org because of too many concurrent requests, we still end up falling back to using the old API, causing this kind of intermittent problems.
I think we had relaxed the limits on the server side to minimize these issues, but the right fix is that bundler completely stops using the old API and instead waits a bit before retrying the new API again when being rate limited. This fix is being tracked at https://github.com/rubygems/rubygems/issues/3594.

Thanks a lot @deivid-rodriguez, this makes total sense!

No problem, and apologies for the trouble. We'll try to fix this.

Ooooh good to know! Thank you very much!
On August 1, 2020 12:16:15 PM GMT+02:00, "David Rodríguez"<EMAIL_ADDRESS>wrote:

Hi! Thanks for letting me know.
This is indeed an issue with bundler. A long time ago, bundler used a
dependency API that didn't have required_ruby_version information.
These days bundler uses a better API that does provide
required_ruby_version information. However, under some circumstances,
specifically, when the client is rate limited by rubygems.org because
of too many concurrent requests, we still end up falling back to using
the old API, causing this kind of intermittent problems.
I think we had relaxed the limits on the server side to minimize these
issues, but the right fix is that bundler completely stops using the
old API and instead waits a bit before retrying the new API again when
being rate limited. This fix is being tracked at
https://github.com/rubygems/rubygems/issues/3594.
--
You are receiving this because your review was requested.
Reply to this email directly or view it on GitHub:
https://github.com/rspec/rspec-rails/pull/2366#issuecomment-667508360

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Hei! Discussing this internally, this might actually not be due to rate limiting but to a different error condition. Bundler should log the exception that's causing the fallback to the old API in --verbose mode here, I believe. If you could use the --verbose flag and report back when this happens again, that would give us more information about this.

@deivid-rodriguez Awesome!
Got some results (1, 2) already. Please let me know if this is sufficient to pinpoint the issue.
Just to confirm that we're still experiencing the issue there's a similar failure from another build for a branch where:
if RUBY_VERSION < "2.3.0"
    gem 'i18n', '< 1.5.2'

is supposedly set, and the failure is:
Gem::RuntimeRequirementNotMetError: i18n requires Ruby version >= 2.3.0. The current ruby version is 2.2.0.
An error occurred while installing i18n (1.8.5), and Bundler cannot continue.

@deivid-rodriguez Ping. Is this of any help?
No pressure, we're in pretty good shape in terms of build stability right now. At the cost, though.
For me, it will be good enough if you are aware of the problem, there's a ticket, and it will eventually be resolved so we can clean our build-related dependency declaration code.

@deivid-rodriguez Ping. Can I provide anything else to help to pinpoint the issue?

@deivid-rodriguez Ping.

Gem::RuntimeRequirementNotMetError: i18n requires Ruby version >= 2.3.0. The current ruby version is 2.2.0.
An error occurred while installing i18n (1.8.5), and Bundler cannot continue.

This should no longer be an issue. I ran build on the same commit and it is passing https://travis-ci.com/github/sonalkr132/rspec-rails/jobs/379918197

they show a Net::OpenTimeout error.

this was probably an intermittent error and bundler continued with retry.
we backfilled required_ruby_version on older versions (16-17 Aug) after you reported https://github.com/rubygems/rubygems/issues/3870 which would have fixed the mismatch in the required ruby version.

Oh, right! This was fixed by backfilling those, I forgot about it!


Ability to use Data Prepper expressions in the OpenSearch sink index and document_id_field

Is your feature request related to a problem? Please describe.
The OpenSearch sink currently supports using values from an Event in the index and document_id_field
index: "${key_one}-${key_two}-%{yyyy.mm.hh}
document_id_field: "/key_three"

As a user, I would like the ability to set the index and document_id_field from Data Prepper expressions, most notably the functions available. For example, I would like to use the getMetadata function to set these values without having to keep them in the Event.
Describe the solution you'd like
A way to use Data Prepper expressions along with formatting in these parameters. We should do this in a way that can be kept consistent in any location in the pipeline config that needs a value
For the add_entries processor, we created a new field for each of these options
add_entries:
   - entries:
         key: "/my_key"
         value: "static_value"
         format: "${key_one}-${key_two}"
         value_expression: "length(/message)"

Ideally, we would not repeat this pattern in every location, in this case that being
index: "my_index" # This currently supports format as well with ${}
index_expression: "getMetadata(\"metatdata_key\")"
document_id_field: "/my_field_from_event"
document_id_field_expression: "getMetadata(\"metadata_key_two\")"
document_id_field_format: "${key_one}-${key_two}"

Instead of this, we should try to consolidate as mentioned in #2719. So we should have only the index and document_id_field parameters, and they will support all of the above options
The best way to do this will be to use ${} syntax to escape both keys and expressions. For example,
index: "prefix-${/some/key}-${getMetadata(\"metadata_key\")}-%{yyyy.mm.hh}
document_id_field: "prefix-${/some/key}-${length(/message)}"

Alternatively, we could consider a different escape character between key values and expressions if we find it difficult to detect keys vs expressions
index: "prefix-${/some/key}-@{getMetadata(\"metadata_key\")}-%{yyyy.mm.hh}
document_id_field: "prefix-${/some/key}-@{length(/message)}"

Describe alternatives you've considered (Optional)
Additional context
Consolidating the expression use in parameters of Data Prepper pipeline configurations (https://github.com/opensearch-project/data-prepper/issues/2719)

@graytaylor0 , Isn't this a breaking change?
It seems that we should add a new document_id which has the behavior you specified and deprecate the document_id_field property. The _field suffix of document_id_field is indicating that the value comes from the specified field.
Now, the behavior is to set the document_id to some value, which can use an expression of the field.


Rolling back resteasy upgrade and removing default yaml files

The rest easy upgrade requires code changes to common. Future task.

Passed testing.


Get level of security as integer

Maybe Feature Request:
Is ist already possible to retrieve the security-level as integer, so I can forbid passwords with a lower security-level than "3" ?

Feature added in v1.2.2 (PR #23)


Test coverage improvement

updated tests for:

dropdown
nav
tab
tabs
taskbar
tabPanel
textArea
textField
timer

also added uppercase to filtered props on TextArea to avoid console error

apologies for all the separate commits, something went wrong on my first branch and the pre-commit hook was changing every single file, so I went back and did them one component at a time


Fix compose file v2 syntax compatibility

#514

Thanks @zsolt-keseru-epam. And thanks for adding the tests as well, much appreciated.


Learning Web dev

I love this great it has helped me alot.

Thank you. share this repo with your friends!


Add support for Phabricator

Phabricator is a free software that can be downloaded from phabricator.org or used at phacility.com

The pull request will be evaluated and merged after the end of the toggl developer challenge deadline (https://toggl.com/toggl-developer-challenge) on February 14th. Thank you for your contribution.

I've made some changes to project name and description fetching as it seemed to not work reliably.
Thank you for your contribution.


fscache: fix a bug introduced by commit eac959f

Fix a bug introduced by commit eac959f, which will cause data corruption under race conditions.
Fixes: https://github.com/dragonflyoss/image-service/issues/969
Signed-off-by: Jiang Liu<EMAIL_ADDRESS>

/retest


Data Source at Client Side

As easy as pasting comma separated values in an input/Text box while in DataView Mode and pressing the button "AnalyzeThis" to see the visualizations. All Client End.
Example:
http://davidguttman.github.io/react-pivot/
Client Side Data can also be achieved by github's new feature of Drag and Drop any file easily to your repo and BAM! , you can analyze your data with a click of button!
Checkout how easy it is now to upload a file. An amateur with little knowledge of github interface can do it:
https://github.com/blog/2105-upload-files-to-your-repositories

If we let the user select/paste CSV data on the frontend, we have no way of saving (committing) this to the underlying GitHub repository.


Not able to access kubeflow

I cant seem to be able to access mkubeflow through microk8. I followed this guide here https://iamageek.medium.com/install-kubeflow-in-10-steps-on-macos-96d7dda9612 and  here https://ubuntu.com/tutorials/deploy-kubeflow-ubuntu-windows-mac#5-access-the-kubeflow-dashboard and even on your docs: https://v0-6.kubeflow.org/docs/started/workstation/getting-started-macos/
I am using sudo snap install microk8s --classic --channel=1.18
After ensuring that the kubeflow is successfully installed, I did the below
ubuntu@kubeflow:~$ sudo -- sh -c "echo '<IP_ADDRESS>\t<IP_ADDRESS>.xip.io' >> /etc/hosts"
ubuntu@kubeflow:~$ sudo iptables -P FORWARD ACCEPT
ubuntu@kubeflow:~$ exit
ssh -i kubeflow -D9999<EMAIL_ADDRESS>
But I keep getting an access issue to <IP_ADDRESS>.xip.io was forbidden when I try to access via the browser ( I already set the SOCKS proxy) and I tried both chrome and firefox.  Really bad documentation as it doesn't tell us how to debug.

Can you try with a later microk8s like 1.21/stable? Also, we have moved from xip.io to nip.io as xip has been abandoned upstream.

Sorry i wrote it wrong. Im accessing nip.io. I will try with 1.21/stable. It would be good to update your documentation so people who are trying out don't waste time. I tried with 1.22 then wasn't supported. Then tried 1.18 didn't work. so now trying 1.21.

ok now it worked with 1.21. BUT another issue
When i tried accessing workbooks, I get a {
"log": "The requested URL was not found on the server. If you entered the URL manually please check your spelling and try again.",
"status": 404,
"success": false,
"user": "admin"

}

i also tried to run a pipeline but it shows This step is in Error state with this message: task 'file-passing-pipelines-ff5tb.repeat-line' errored: Internal error occurred: failed calling webhook "admission-webhook.kubeflow.org": Post "https://admission-webhook.kubeflow.svc:443/apply-poddefault?timeout=30s": x509: certificate signed by unknown authority.
Seems like this is very buggy.

Sorry there's some things mixed up with the current pipeline setup.  This should be resolved in ~2 weeks or so when we release a new bundle that supports Kubeflow 1.4

Hi! I have just tried the 2 tutorials that come with Kubeflow version: Charmed Kubeflow, from Canonical, version 1.4
The error seems to be the same that the one presented in the thread:   task 'file-passing-pipelines-wjvkq.write-numbers' errored: Internal error occurred: failed calling webhook "admission-webhook.kubeflow.org": Post "https://admission-webhook.kubeflow.svc:4443/apply-poddefault?timeout=10s": x509: certificate signed by unknown authority,

Is there any fix?
Thanks very much,
Ramón Girona


Value Remaining Time

Hi, since serial battery is getting a lot of new features we also have remaining time now. Would you please add this to aggregate batteries?

Hello, all versions of Serial Battery since Bluetooth added are unstable in my sxstem, I don't understand why. I use an old one. Please write all new dbus paths you would like to aggregate, I can add them.

I added to my code, after test it will be published with an update.


Support distribution data type

Graph as heatmap or using mean value or ...
https://cloud.google.com/monitoring/api/ref_v3/rest/v3/TimeSeries#Point

https://github.com/mtanda/grafana-google-stackdriver-datasource/pull/23


Have c_rehash.in create links in the current directory to all other files in the directory list.

"c_rehash" generates links in the same directory as the CRT and CRL files.
It would be convenient for c_rehash to generate the links in the current directory, linking to the files in each of the directories passed to it.
i.e. $ ls -l /etc/ssl/certs
lrwxr-xr-x  1 root  wheel  70 Jun 13 18:28 02265526.0 -> /usr/share/certs/trusted/Entrust_Root_Certification_Authority_-_G2.pem
lrwxr-xr-x  1 root  wheel  61 Jun 13 18:28 03179a64.0 -> /usr/share/certs/trusted/Staat_der_Nederlanden_EV_Root_CA.pem
... etc ...

I think c_rehash should be be deprecated and openssl rehash should be the preferred way.  Perhaps the script could even just call the program :)

openssl rehash seems to have the same limitation, or is there special option to create symlinks in current working directory ?

No, no such option there. But the comment means that the feature should be implemented in the openssl rehash and not in c_rehash.

I support this request, in fact what should be supported is to provide the current list of input directories and the target with a switch. Most will pass: "/etc/ssl/certs" for the default verify location.

@michael-o are you able to submit a PR for this?

@michael-o are you able to submit a PR for this?

Let me check how rehash currently works and what effort it would be to fix it. I'll get back to you in a couple of days.


June 2018 Code Review

This is a placeholder issue for a code review of the Asclepias broker code/repo. More details to follow.

@augustfly Let us know if you need a walkthrough of the repository (CC @ChiaraBi @lnielsen)

perhaps yes, but let's have @astrofrog take a look first.

I've done a first pass at reviewing this! https://github.com/asclepias/asclepias-broker/pull/56


*: fix the issue that loadcluster does not remove overlap regions(#2022)

Signed-off-by: nolouch<EMAIL_ADDRESS>
What problem does this PR solve?
cherry-pick #2022
What is changed and how it works?
cherry-pick.
Check List
Tests

Unit test

/run-all-tests

/run-all-tests

/run-all-tests

Codecov Report

:exclamation: No coverage uploaded for pull request base (release-3.1@58ed361). Click here to learn what that means.
The diff coverage is 91.17%.

@@              Coverage Diff               @@
##             release-3.1    #2039   +/-   ##
==============================================
  Coverage               ?   69.47%
==============================================
  Files                  ?      171
  Lines                  ?    16837
  Branches               ?        0
==============================================
  Hits                   ?    11698
  Misses                 ?     4157
  Partials               ?      982

Impacted Files
Coverage Δ

server/handler.go
51.98% <ø> (ø)

server/core/errors.go
62.5% <100%> (ø)

server/core/region_kv.go
82.95% <100%> (ø)

server/core/kv.go
76.08% <100%> (ø)

server/core/region.go
93.42% <100%> (ø)

server/core/basic_cluster.go
93.1% <83.33%> (ø)

server/cluster_info.go
88.07% <92.3%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 58ed361...83daf86. Read the comment docs.

/run-cherry-picker


Stone tag needs to be stone, not smooth stone.

Stone tag needs to be stone, not smooth stone.

resolved


package change in spotipy

Breaks on the many changes in spotipy authentication flow.

Thanks, the skill installs spotipy 2.17.1 so changes shouldn't affect it.
That said, we should try to keep up with spotipy so it might be a good time to update it!


a bit of intrinsics organization

@bors r+

:pushpin: Commit 10a829446d32deb9902212110090792120359d01 has been approved by RalfJung
It is now in the queue for this repository.

:hourglass: Testing commit 10a829446d32deb9902212110090792120359d01 with merge 65b1045b70c955e9b02261e5e6b133d9ed247ff1...

:sunny: Test successful - checks-actions
Approved by: RalfJung
Pushing 65b1045b70c955e9b02261e5e6b133d9ed247ff1 to master...


error: unexpected argument '--config_file' found

It seems something was missed when adding support for a config file. Using -c doesn't seem to work either, and --help doesn't seem to be updated.
soul@SilverMini stalker % leptosfmt --version
leptosfmt 0.1.5
soul@SilverMini stalker % leptosfmt --config_file rustfmt.toml src/main.rs
error: unexpected argument '--config_file' found

  tip: to pass '--config_file' as a value, use '-- --config_file'

Usage: leptosfmt [OPTIONS] <INPUT_PATTERN>

For more information, try '--help'.

That is odd, looks like something went wrong when publishing, thanks for letting me know :)


app UI: Scn switching menu should have a scroll option

Right now the scn switching menu doesn't have a scroll option, thus the scenes at the end are not accessible.

fixed


Label & MessageBox: Add Word Wrap

This PR adds word wrap to Label and MessageBox.
Closes #352

If a Label is a single line, word wrap is disabled and the view acts as it did previously.
Because MessageBox uses Label, it gets word wrap for free (with some minor tweaks also in this PR).

The wrapping code has some issues with unicode characters that will need to eventually be fixed.

I am late - but this is glorious!   Thank you Charlie!


Support download package on Alpine Linux

I use Docker with image from https://github.com/wjordan/dockerfile-libvips with
npm install sharp.
The build raise error:
LDD_VERSION musl libc (x86_64) requires manual installation - please see http://sharp.dimens.io/en/stable/install/
How can I use this library on Alpine ?
Here my Dockerfile:
Dockerfile.txt

Hello, you'll need to install vips-dev, see also #803

I've added a section to the docs about Alpine - see commit 29354ba


codegen: Generate u128 / i128 when available.

This is the first step to fix #1370 / #1338 / etc.
Fix for that will build up on this.

 Warning

These commits modify unsafe code. Please review it carefully!

I implemented the whole thing, but there's an autogenerated test failure that fails because of https://github.com/rust-lang/rust/issues/54341.
So i128 / u128 doesn't have the right alignment on Rust :(

Still I think it's an improvement over what we have... So if I were to land this I'd disable the autogenerated tests for that test.
r? @fitzgen

The blob bits unfortunately aren't an improvement over what we have because of that rust alignment issue, so I don't think we can land tests for them unless we have a way of expecting test failures, which I don't think I have the cycles for.
Thanks for the review!
@bors-servo r=fitzgen

:pushpin: Commit c09c74e has been approved by fitzgen

:hourglass: Testing commit c09c74e18b6ce8b69626a59737d8e82a3eb1d1b8 with merge 6fc0a31febb63d77da1a38aa2eea9d10fbea0d0d...

:sunny: Test successful - status-travis
Approved by: fitzgen
Pushing 6fc0a31febb63d77da1a38aa2eea9d10fbea0d0d to master...


Fix unused variable warnings

While using this package, I noticed that there were four warnings when I went to compile:
==> phoenix_api_docs
Compiling 7 files (.ex)
warning: variable path is unused
  lib/phoenix_api_docs/controller.ex:52

warning: variable docs is unused
  lib/phoenix_api_docs/blueprint_writer.ex:108

warning: function Phoenix.Naming.humanize/1 is undefined (module Phoenix.Naming is not available)
  lib/phoenix_api_docs/generator.ex:101

warning: function Phoenix.Naming.resource_name/2 is undefined (module Phoenix.Naming is not available)
  lib/phoenix_api_docs/generator.ex:101

Generated phoenix_api_docs app

I've taken the time to fix them all up. The path one was easy as it just needed to be prefixed with an underscore. The docs one was interesting as it was getting used. I decided to refactor some of the code and it looks like the compiler now recognizes that the docs variable is being used.
As for the functions from Phoenix.Naming, I tried importing them, but it didn't go so well. It looks like the compiled code has no notion of a Phoenix.Naming, even if you require it.

Hi @BenMorganIO, thanks a lot for your contribution :) Actually the _path that you fixed is not needed at all, it's a bug. If you have any ideas for the project feel free to discuss it and contribute. It was quickly written in just one evening but I will work on it more when I have more time.

@smoku excellent. I'll let you know if I have any ideas. I'm currently using it at https://docs.taiga.market for a new project.
Going to write a blog post on my implementation of the PhoenixAPIDocs in the future. Wondering if you'd like to review it and put it in the README if you like it?


Win key cannot be remapped to ALT GR (Ctrl + ALT)

Microsoft PowerToys version
0.57.2
Running as admin

[X] Yes

Area(s) with issue?
Keyboard Manager
Steps to reproduce
Try to remap (Remap a key OR Remap a shortcut) Win-key (Win, Win (Left) or Win (Right) doesn't matter) to CTRL + ALT (of any kind)
✔ Expected Behavior
Remap Win key to selected keys
❌ Actual Behavior
An error pop-up with "Some of the shortcuts could not be remapped. Do you want to continue anyway?"
Other Software
No response

What does the message say exactly?

What does the message say exactly?

That depends on which remap i try to use. Remap keys says "Some of the keys could not be remapped. Do you want to continue anyway?". Shortcuts gives the exact message written above in actual behavior

Oh okay. I was thinking of a possible other message, but that's not the case here.
I believe the message is valid compared against the "internal rules". Shortcuts must include at least one "modifier" key (like Win/Ctrl/Alt/Shift) with (at least) one other "normal" key. The latter one is missing.
So, technically not a bug, but I see that users want some explanation here. This is a (sub) item for #2027.

Oh okay. I was thinking of a possible other message, but that's not the case here. I believe the message is valid compared against the "internal rules". Shortcuts must include at least one "modifier" key (like Win/Ctrl/Alt/Shift) with (at least) one other "normal" key. The latter one is missing. So, technically not a bug, but I see that users want some explanation here. This is a (sub) item for #2027.

It seems you are ignoring the fact that remaping the key does not work either.

Actually, I didn't. You try to Remap a key Win --> Ctrl+Alt. Here my answer above applies. I can imagine you try to press the physical Alt Gr key, but (afaik.) this sends a Ctrl+Alt combo "in the background".
If you try to use Remap a hotkey, the input needs to be a combination of keys and that is not appropriate for what you want to do.

Actually, I didn't. You try to Remap a key to a shortcut: Win --> Ctrl+Alt. Here my answer above applies. I can imagine you try to press the physical Alt Gr key, but (afaik.) this sends a Ctrl+Alt combo "in the background".
If you try to use Remap a hotkey, the input needs to be a combination of keys and that is not appropriate for what you want to do.

Your answer never mentions Remap a key so i really don't see how it can. I also don't see how remap a key could require a normal key in the mapped to - especially as i have already remapped caps-lock to win.

Caps --> Win is a key-to key situation, so that's a different situation. The problem/message comes from the Ctrl+Alt situation: a shortcut that has no "normal" non-modifier keys.

So what you're saying is that the bug is that it is not possible to map anything to alt-gr? That still seems like a pretty obvious bug...

Unfortunately, that's what is is. The AltGr might be one key on a keyboard, but it sends Ctrl+Alt in the background. Some keyboards might have an Office key, for example. It sends Win+Ctrl+Shift+Alt, but that is caught and acted on by Windows itself.

And i just found the solution - remap the key to alt(Right) reproduces the result of pressing alt-gr


Refs are not handled in schema properties

What are the steps to reproduce this issue?

Run the command

yarn orval --input https://raw.githubusercontent.com/linode/linode-api-docs/development/openapi.yaml --output ./generated/linode.ts

Observe Typescript type-checking errors in the generated types

Spec that is causing issues
      requestBody:
        description: Updated information for the Managed MySQL Database.
        required: true
        content:
          application/json:
            schema:
              type: object
              description: Updated information for the Managed MySQL Database.
              properties:
                label:
                  $ref: '#/components/schemas/DatabaseMySQLRequest/properties/label'
                allow_list:
                  $ref: '#/components/schemas/DatabaseMySQLRequest/properties/allow_list'
                updates:
                  $ref: '#/components/schemas/DatabaseMySQL/properties/updates'

What happens?
Typescript types are used but the interface for them does not exist

What were you expecting to happen?
This package should recursively resolve refs used in schema properties

Any logs, error output, etc?
No errors occour
Any other comments?
I'm very unfamiliar with this codebase but it looks like references are not being handled here:
https://github.com/anymaniax/orval/blob/8f1682ce72d721d8992b4c613513191b31029c7c/packages/core/src/getters/object.ts#L60-L77
What versions are you using?
Operating System: Pop_OS!
Package Version: 6.19.0
Browser Version: Chrome

This may be a duplicate of https://github.com/anymaniax/orval/issues/811

Definitely looks like a duplicate to me


Birdseye and multiple frigate servers

HI,
I don't know if this is even possible but any suggestions are warm welcomed.
This is what I have as configuration at the moment. client_id is acceptable because I can see the birdseye from frigatenvr1.
I can't add the other servers in similar way because the camera name is always  birdseye
Any suggestions?
- type: custom:frigate-card
    cameras:
      - frigate:
          camera_name: birdseye
          client_id: frigatenvr1
        dependencies:
          all_cameras: true

Adding a separate card for every frigate servers is not helping - the first birdseye is visible, only
- type: custom:frigate-card
    cameras:
      - frigate:
          camera_name: birdseye
          client_id: frigatenvr1
  - type: custom:frigate-card
    cameras:
      - frigate:
          camera_name: birdseye
          client_id: frigatenvr2
  - type: custom:frigate-card
    cameras:
      - frigate:
          camera_name: birdseye
          client_id: frigatenvr3

I can't add the other servers in similar way because the camera name is always birdseye

What's the error you are shown exactly? Why does this not work?
If it's simply that the id of the cameras are clashing in the card since the camera names are the same, something like this might help (have not tested):
- type: custom:frigate-card
  cameras:
    - id: birdseye1
      frigate:
        camera_name: birdseye
        client_id: frigatenvr1
    - id: birdseye2
      frigate:
        camera_name: birdseye
        client_id: frigatenvr2

No errors. Birdseye from one frigate server is displayed, only.
Let me check the solution you proposed

This is working. Thank you.
Not the best way because the streams need to be switched.

This is working. Thank you.

Excellent. Will close this issue then.

No, as the birdseye view is composed by the Frigate server, not the card.
However, the next release will include a new grid mode that lets you display a grid of cameras at once, and those cameras can come from any server (or even non-Frigate cameras). Theoretically that could be expanded in future to support a "dynamic birdseye" (as that will really just be hiding cameras from the grid that have no activity).


How can i set the limit to sticker zoom

I have an that error "Font size too large to fit in cache" when I zoom in until a single letter appears. So i want to set limit for zoom. But how can i do, anybody have any idea? (setMaxTextSize is not working this situation)

if you got any solution then share with me.
Thank you.


Revert "perf(semantic): use Atom<'a> for References"

Reverts oxc-project/oxc#3972
@DonIsaac As it turns out we can't have lifetimes on these structures because semantic data is exposed to downstream users to use freely, detached from the ast and allocator.

Does adding lifetimes break downstream consumers?

Does adding lifetimes break downstream consumers?

Yes, I forgot to mention Rolldown. https://github.com/rolldown/rolldown/blob/87ec563e8bc1a2241d80a40452c8dc7c6c59ad06/crates/rolldown_common/src/module/normal_module.rs#L42


Intensity is flipped?

Win32 puts the intensity on the upper colors so that intense/bold/light are to the right here:

But concfg (at least for solarized) reverses that, so that apps that ask for intense or bold get the opposite. Is that an issue just with your solarized sample, or is it reversed in all of concfg?

There's nothing in concfg that requires the intensity to be reversed, but it looks like most of the themes are configured that way currently.
The reason for this is that most of the themes are ported from Unix where colors seem to be named with a "bright" variant, to Windows where the colors have a "dark" variant (at least they're named "dark" in PowerShell).
The names were taken to mean that bright should be lighter than dark. Now that you're pointing it out, it seems like it might have been better to treat both "bright" and "dark" as "bold".

Sorry, I got that backwards. I'd forgotten we went through this whole thing 3 years ago.
Originally we went with the convention that bright = dark (the way most themes are set up now).
We tried inverting it so bright > dark, like you're suggesting — that seemed to break at least NodeJS and Grunt which use the bright = dark convention. So we switched back to bright = dark.
It sounds like PowerShell has assumed the bright > dark convention, which conflicts with other well-known programs.
Confg's Solarized theme has now been mangled to kind of support both PowerShell and other programs.

Gotcha. OK, good to know. Thanks for the info! Not sure about node or powershell, but I can tell you that Windows itself is dark/bright per their APIs. I think @bitcrazed may have something to say about it.

Thanks Scott. I'd appreciate any suggestions or advice about the best way to do it.

I manually changed the solarized config file to the following to force the background color to match, and make it readable. Not ideal, but works for my use case.
Note I updated the size to be a little more useful for powershell output, and my personal font of choice Fira Code is here so replace with yours if you want.
 {
	"black":"#002b36",
	"dark_blue":"#268bd2",
	"dark_green":"#859900",
	"dark_cyan":"#002b36",
	"dark_red":"#dc322f",
	"dark_magenta":"#d33682",
	"dark_yellow":"#b58900",
	"gray":"#eee8d5",
	"dark_gray":"#839496",
	"blue":"#839496",
	"green":"#859900",
	"cyan":"#93a1a1",
	"red":"#cb4b16",
	"magenta":"#6c71c4",
	"yellow":"#859900",
	"white":"#fdf6e3",

	"screen_colors":"blue,black",
	"popup_colors":"yellow,white",

	"font_face":"Fira Code",
	"font_true_type":true,
	"font_size":"0x16",
	"font_weight":500,

	"cursor_size":"small",

	"window_size":"120x40",
	"screen_buffer_size":"80x3000",

	"command_history_length":200,
	"num_history_buffers":4,

	"quick_edit":true,
	"insert_mode":true,
	"fullscreen":false,

	"load_console_IME":true
}

@lukesampson I (re)did most of the mapping for cmd-colors-solarized. My ordering came from looking at different implementations for terminal applications such as PuTTY, and then working backwards from that. The implementation that we settled with was that br* = Dark*. This creates some interesting mapping problems when the Terminal has colors which don't match base01 for example. In the README.md and screenshots, you can see how these were mapped. Basically, blue, green, cyan, red, magenta, and yellow were mapped to their respective colors while orange was mapped to its closest match "dark red" and violet was mapped to its closest match "dark magenta". The grayscale was harder to map, but again I was mostly matching other configurations. There's some logic in that color table values 0, 7, 8, and F have some significance in their brightness, and 0, 1, 6, and F have some significance in console mapping. What was left fell out of that, but again it closely followed other implementations.

Thank you @sheldonhull and @rbeesley.
I like the thoroughness of cmd-colors-solarized, and how you use a script to get PSReadLine to work.
Maybe the thing to do to improve concfg is to set the PSReadLine settings in the user's $profile when running concfg import.


Karatsuba Algorithm

Is your feature request related to a problem? Please describe.
Multiplying two big numbers using traditional multiplication can take quadratic time complexity. Karatsuba's algorithm is a faster method of multiplying two big numbers that take n power 1.59 time complexity.
Describe the solution you'd like
I would like to implement this method in Java.
Additional context

Please can u assign this issue to me to implement in Java.

refer #71


upgrade ui lib version to 0.4.2

upgrade ui lib version to 0.4.2

Coverage decreased (-0.03%) to 54.366% when pulling 373c6a3783b4332d00ae73f4912fb88eeb1ea884 on steven-zou:master into a6dc3e549dac484d2b2858fd1a510b16bda6e8fa on vmware:master.


would like more examples

[Enter feedback here]

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

ID: 8ed471c1-18af-0266-74d3-98449465a17d
Version Independent ID: bb750d55-4be7-214d-dc30-ee10317e98f5
Content: PartitionReceiver Class (Microsoft.Azure.EventHubs) - Azure for .NET Developers
Content Source: xml/Microsoft.Azure.EventHubs/PartitionReceiver.xml
Service: event-hubs
GitHub Login: @rloutlaw
Microsoft Alias: routlaw

Thank you for your feedback.  Tagging and routing to the team best able to assist.

Samples can be found in https://github.com/Azure/azure-event-hubs/tree/master/samples/DotNet/Microsoft.Azure.EventHubs


Add typescript to toctree

See #3069 and #3036

Fixed merge conflict in change log. Docs build passes. Merging!


Wrapper: River cluster analyzers - Hyperparameters

The specific parameters of the wrapped River ca algorithms need to be registered as hyperparameters on the wrapper level. This is the prerequisite to be able to hp-tune the wrapped algos...
See also
fhswf/MLPro#731 fhswf/MLPro#735 fhswf/MLPro#732 fhswf/MLPro#733

As discussed hp tunig of cluster analyzers makes not really sense...


shell shows error and usage when given extra parameters

Fixes #8593
When try to launch the shell with arguments the shell won't launch, instead will show an error (with the unknown args) as well as the usage.
Required for all non-trivial PRs

[x] Rebased/mergable
[x] Tests pass
[ ] CHANGELOG.md updated
[x] Sign CLA (if not already signed)

@stop-start would you mind adding a line like
- [#9065](https://github.com/influxdata/influxdb/pull/9065): Refuse extra arguments to influx CLI

to the 1.5.0 / Bugfixes section of CHANGELOG.md?

@mark-rushakoff  Done

Thanks @stop-start!

Thanks @mark-rushakoff, it's my second pull request but first looked at and approved!

The PR number in CHANGELOG.md is the wrong one, though. 9065 instead of 9095.

Good catch @Luit, that was a typo on my part. Care to open a small PR to fix it?

I opened a PR to fix it in #9182.


how to get jsonString

graphql
query MyQuery {
  user {
    id // string
    phone // string
    position // jsonString like [{x:double,ydouble}]  and graphql type is Position
  }
}

i try use JsonSerializer or PrimitiveSerializer ,but can not work, who can help me!!!

fromJson of JsonSerializer need a Map, but i got a list<dynamic>,
deserialize of PrimitiveSerializer got a list<dynamic>,
and my PositionSerializer not only deserialize grqphql type Position, also deserialize another type (int, string,double... )

Seems like this is a question about how to create custom BuiltValue serializers and isn't necessarily related to ferry.
I'm closing for now. Please direct any general questions to Stack Overflow or the Discord channel.


Xamarin android sample

Can you provide any sample for getting started with the indoor mapping and navigation using Xamarin.forms for both android and iOS, preferably android?

At this time the application builds for Xamarin.iOS only. You can refer to the development instructions in the README to learn how to download and build this project for iOS.
With that said, I will note that the app is architected in such a way that the business logic is abstracted from the UI. As such, building Indoor Routing for Xamarin.Android would require building only a front-end rather than starting from scratch, substantially reducing the amount of development work required to get this application up and running on other supported Xamarin platforms.
We accept contributions from the community, I encourage you to fork the repo and see what you come up with!


Convert incoming TCP connections to UCP

Thank you for your issue! Would you be able to expand on why this would be useful, and what your use-case is?

Going to close this for inactivity, but feel free to re-open with more information.


[SMO] Generic DAO and its serving API

Summary
First PR of a series PRs to introduce Generic DAO and its corresponding service APIs.
There has been previous attempt to implement a generic interface https://github.com/linkedin/datahub-gma/pull/325. But this attempt only covers the rest APIs. Under the hood, it still requires user to create many type-bounded DAOs, which means we still needs code changes for new entity e.g. write DAO factory, register the DAO etc...
This PR attempts to have a grand rewrite starting from the very bottom layer, which remove all the type bounds. All the type-casting is left to client to perform. Metadata is ingested as "raw" and served as "raw" in terms of JSON serialized strings.
Testing Done
Unit tests
Checklist

[ ] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
[ ] Links to related issues (if applicable)
[ ] Docs related to the changes have been added/updated (if applicable)

Codecov Report
Attention: Patch coverage is 72.41379% with 32 lines in your changes missing coverage. Please review.

Project coverage is 58.43%. Comparing base (c79500a) to head (594950e).

Files
Patch %
Lines

...om/linkedin/metadata/dao/EbeanGenericLocalDAO.java
77.65%
13 Missing and 8 partials :warning:

...adata/restli/BaseEntityAgnosticAspectResource.java
61.11%
6 Missing and 1 partial :warning:

...ava/com/linkedin/metadata/dao/GenericLocalDAO.java
0.00%
3 Missing :warning:

...linkedin/metadata/dao/EbeanGenericLocalAccess.java
0.00%
1 Missing :warning:

Additional details and impacted files
@@             Coverage Diff              @@
##             master     #383      +/-   ##
============================================
- Coverage     67.74%   58.43%   -9.31%
+ Complexity     1343     1190     -153
============================================
  Files           132      136       +4
  Lines          5276     5409     +133
  Branches        546      565      +19
============================================
- Hits           3574     3161     -413
- Misses         1484     2015     +531
- Partials        218      233      +15

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

Can you elaborate what is the ending goal for this refactor? considering

MMG will still need strong typed APIs, however
Graph query, aspect query does require entity agnostic access

Is the goal to unify the bottle logic for the two cases above?

Hi @yangyangv2 ,
The immediate issue that this PR want to solve is aspect routing. Current aspect routing hooks too many dependencies on the aspect GMS e.g. ownership-gms. Just a few examples:

Even with code-gen, we still have to make code changes in other teams' MP. This makes the boundary unclear.
We have to make sure the aspect GMS is deployed first with new APIs. Otherwise, main GMS will throw errors.
We have to import new clients in the main GMS whenever there is a new entity.

With the generic DAO / APIs in this PR, the aspect GMS e.g. ownership-gms can host a set of generic APIs and require no code change for new entity / aspect. Regarding the type casting, this can happen in the BaseAspectRoutingResource class.
As for future use cases, I think the type-casting can be a dedicated layer in the mid-tier of MMG. When new entity onboarded, an entry can be added in this layer. But no other places require code change since they are all generic.  A entity-specific resource / DAO class can still be created in case users needs customized logic.

Can you elaborate what is the ending goal for this refactor? considering

MMG will still need strong typed APIs, however
Graph query, aspect query does require entity agnostic access

Is the goal to unify the bottle logic for the two cases above?

Hi @yangyangv2 ,
The immediate issue this PR want to solve is aspect routing. Current aspect routing hooks too many dependencies on the aspect GMS e.g. ownership-gms. Just a few examples:

Even with code-gen, we still have to make code changes in other teams' MP. This makes the boundary unclear.
We have to make sure the aspect GMS is deployed first with new APIs. Otherwise, main GMS will throw errors.
We have to import new clients in the main GMS whenever there is a new entity.

With the generic DAO / APIs in this PR, the aspect GMS e.g. ownership-gms can host a set of generic APIs and require no code change for new entity / aspect. Regarding the type casting, this can happen in the BaseAspectRoutingResource class.
As for future use cases, I think the type-casting can be a dedicated layer in the mid-tier of MMG. When new entity onboarded, an entry can be added in this layer. But no other places require code change since they are all generic. A entity-specific resource / DAO class can still be created in case users needs customized logic.

Synced offline. Generally aligned the GenericDAO will help with the status quo. Once moving to MMG, the future trend is still strongly-typed. GenericDAO may still have its place in the low-level logic. Just for wide-use and or extension of GenericDAO should  be well considered to avoid with the Code-Gens in MMG.


enhancement #LOG192. Impl Openshift Token Auth

Enhancement to add bearer token auth https://jira.coreos.com/browse/LOG-192
This PR additionally allows us to add static groups which should also satisfy the prometheus metrics usecase and removing the proxy for that use.

Would this PR also let us remove the oauth proxy container?

@ewolinetz I went ahead and removed the 'enabled' configs.

@jcantrill can you add to the README that we removed the flags to enable and disable functionality?
Otherwise lgtm

/hold

i dont think the bot is listening here...

yeah - I think Jeff will merge it manually if we approve - so just Request Changes for now

Merging as https://github.com/openshift/origin-aggregated-logging/pull/1363 finally passed its tests


Fix hexToRgbaCss when alpha is 0

Fix hetToRgaCss when passing an explicit alpha of 0. Avoids a fasly trap that enoneously passes undefined to rgbaToRgbaCss.

Thank you for this! Nice find.