QueuedExport doesn't allow softDeleted data

Versions

PHP version: 8.0
Laravel version: 8.73
Nova version: 3.29
Package version: 1.2.9

Description
After softDeleted data selected, QueuedExport doesn't get deleted ones. DownloadExcel class does that.
Additional Information
(new CustomExcelExport())->withDisk('media')->askForFilename(),
The implementations are WithMapping,WithHeadings
The traits are InteractsWithQueue, Queueable;

Hey @yahya077 can you share the query please

I'm not familiar with set('trashed').  The package that serializes the query has support for trashed/soft deleted: https://github.com/laravie/serialize-queries/blob/master/tests/Feature/EloquentTest.php#L87 I guess it would be best if you could try to create an easy to reproduce scenario, so I can share it with the package author

If you want to set only trashed you have to do it during or before __sleep(). I don't think this package interacts with request during __wakeup(), @patrickbrouwers may confirm this.
laravie/serialize-queries only handle query serialize and unserialize.

I think indeed the request won't be correctly searialized for the wakekup. Perhaps add some logging to check what the value is within that indexQuery at the moment it does the _wakeup

Alright, let me give you the sceneario.
My Nova Resource in actions
(new CustomExcelExport())->withDisk('media')->askForFilename(),
My CustomExcelExport class
`extends QueuedExport implements WithMapping,WithHeadings`
// functions that i included are
public function name()
public function headings(): array
public function map($model): array

// Those functions are not empty obviously, it stands for scenario purpose.

The problem
The data doesn't returns with deleted ones.
What I tried
note: these substances are tried separately.

In the nova resource i override indexQuery function to get delated ones. Which is writing queries to get with deleted.
In the nova resource i override indexQuery. With;

$request->merge(['trashed' => 'with']);
$request->query->set('trashed','with');
return $query;

In the nova resource i override initializeQuery. I just add it $withTrashed = 'with'; to the beginning of the function.
In the custom class i override __sleep(). I add it  $request->merge(['trashed' => 'with']); and $request->query->set('trashed','with'); to the beginning of the function.

As you are already using a custom export class, you can probably better just overwrite the query method there.

Well, I also tried that earlier but It also doesn't work. Why? Let me explain.
When I add a query like get data with deleted ones It doesnt work.
eq: $query->whereNotNull('deleted_at') // this will get all data with that query not the ones i selected from datatable
The query function is not doing its job. I check the all query after i queried. There is a 'where is null deleted_at' query. It seems like before the query function some query prepared already.
If you try it you will see that extra query will broke the code.

It would be a lot easier if you could give a full reproduction scenario, this is quite hard to puzzle together to what you are exactly trying. If you could make a reproduction repository with the most simple situation that will make it less time consuming to look into, without it I won't have time to look into it.


[FEATURE] Added Bypass Anticheat AAC

Add Speed For AAC And LongJump

And Bypass AACAP

What AAC new old latest?

Not needed

No anarchy servers use aac in any significant capacity


build: Downgrade the requirement for cryptography

Some customers want to use cryptography 2.8. We can relax the requirement since we don't use any of the new functionality later versions offer.

Setting on hold, FOSSA found a security issue after all.

Changing to 3.4 as it has the 2.8 vulnerability fixed. This is the lowest we can go according to the security scan.


config cleanup CH data; COUNTRY=rbd

remove unused data columns in CH data
This applies to RBD and Cameroon.
To do - further reduce Cameroon data with a country filter

Awesome, thanks @wadhwamatic !


websocket/upgrade path does not honor per_connection_buffer_limit_bytes ?

I send websocket data on port 443, and when I push a ton of tcp data, I can see envoy buffering up data and finally gets OOM killed. I am using istio 1.10.2, and I have applied the below EnvoyFilter
- applyTo: CLUSTER
  patch:
    operation: MERGE
    value:
      per_connection_buffer_limit_bytes: 65536

But inspite of that I can see that my inbound listener is queueing up more data than I configured for.
cluster.inbound|443||.upstream_cx_tx_bytes_buffered: 130832
cluster.inbound|443||.upstream_cx_tx_bytes_buffered: 103815
Note that the filter above seems to be applied just fine, the value 65536 is reflected below
Maybe I am misunderstanding the whole concept of flow control here - my expectation is that if the cluster tx buffers are backed up, it will basically stop the listener from reading further.  But I realize thats not possible if the listeneris doing http2  and multiplexing many streams - but what if the listener is doing http1.1 ? Can the cluster stop the listener from reading - I hope thats how envoy is designed ? That is primarily what I am expecting here
[
    {
        "name": "inbound|443||",
        "type": "ORIGINAL_DST",
        "connectTimeout": "10s",
        "perConnectionBufferLimitBytes": 65536,
        "lbPolicy": "CLUSTER_PROVIDED",
        "circuitBreakers": {
            "thresholds": [
                {
                    "maxConnections":<PHONE_NUMBER>,
                    "maxPendingRequests":<PHONE_NUMBER>,
                    "maxRequests":<PHONE_NUMBER>,
                    "maxRetries":<PHONE_NUMBER>,
                    "trackRemaining": true
                }
            ]
        },
        "cleanupInterval": "60s",
        "upstreamBindConfig": {
            "sourceAddress": {
                "address": "<IP_ADDRESS>",
                "portValue": 0

So is there something special in the upgrade path that makes it ignore these settings ? I read about the usage of buffer filter in the upgrade path in the envoy docs, but I dont have any buffer filter. All that it has is an http.router filter.
Any clues / pointers would be appreciated!

Some more trace logs if thats of any help
2021-07-09T18:31:45.221433Z	trace	envoy connection	[C2118] ssl read returns: -1
2021-07-09T18:31:45.221434Z	trace	envoy connection	[C2118] ssl error occurred while read: WANT_READ
2021-07-09T18:31:45.221437Z	trace	envoy connection	[C2118] ssl read 2854 bytes
2021-07-09T18:31:45.221441Z	trace	envoy filter	Alpn Protocol Not Found. Expected istio-peer-exchange, Got
2021-07-09T18:31:45.221455Z	trace	envoy http	[C2118] parsing 2854 bytes
2021-07-09T18:31:45.221458Z	trace	envoy http	[C2118] message begin
2021-07-09T18:31:45.221463Z	debug	envoy http	[C2118] new stream
2021-07-09T18:31:45.221474Z	trace	envoy http	[C2118] completed header: key=host value=gatewaytestc.nextensio.net:443
2021-07-09T18:31:45.221479Z	trace	envoy http	[C2118] completed header: key=upgrade value=websocket
2021-07-09T18:31:45.221481Z	trace	envoy http	[C2118] completed header: key=connection value=Upgrade
2021-07-09T18:31:45.221484Z	trace	envoy http	[C2118] completed header: key=sec-websocket-key value=dGhlIHNhbXBsZSBub25jZQ==
2021-07-09T18:31:45.221486Z	trace	envoy http	[C2118] completed header: key=sec-websocket-version value=13
2021-07-09T18:31:45.221488Z	trace	envoy http	[C2118] completed header: key=user-agent value=Go-http-client/1.1
2021-07-09T18:31:45.221491Z	trace	envoy http	[C2118] completed header: key=x-nextensio-connect value=nextensio-default-nextensio-net
2021-07-09T18:31:45.221493Z	trace	envoy http	[C2118] completed header: key=content-length value=0
2021-07-09T18:31:45.221495Z	trace	envoy http	[C2118] completed header: key=x-forwarded-for value=<IP_ADDRESS>
2021-07-09T18:31:45.221498Z	trace	envoy http	[C2118] completed header: key=x-forwarded-proto value=https
2021-07-09T18:31:45.221500Z	trace	envoy http	[C2118] completed header: key=x-envoy-internal value=true
2021-07-09T18:31:45.221503Z	trace	envoy http	[C2118] completed header: key=x-request-id value=c9b5c1ad-4418-9fc4-9707-a63d08d2fd51
2021-07-09T18:31:45.221505Z	trace	envoy http	[C2118] completed header: key=x-envoy-decorator-operation value=nextensio-default-nextensio-net-http-outside.nxt-nextensio.svc.cluster.local:443/*
2021-07-09T18:31:45.221511Z	trace	envoy http	[C2118] completed header: key=x-envoy-peer-metadata value=ChQKDkFQUF9DT05UQUlORVJTEgIaAAoaCgpDTFVTVEVSX0lEEgwaCkt1YmVybmV0ZXMKGQoNSVNUSU9fVkVSU0lPThIIGgYxLjEwLjIKvwMKBkxBQkVMUxK0AyqxAwodCgNhcHASFhoUaXN0aW8taW5ncmVzc2dhdGV3YXkKEwoFY2hhcnQSChoIZ2F0ZXdheXMKFAoIaGVyaXRhZ2USCBoGVGlsbGVyCjYKKWluc3RhbGwub3BlcmF0b3IuaXN0aW8uaW8vb3duaW5nLXJlc291cmNlEgkaB3Vua25vd24KGQoFaXN0aW8SEBoOaW5ncmVzc2dhdGV3YXkKGQoMaXN0aW8uaW8vcmV2EgkaB2RlZmF1bHQKMAobb3BlcmF0b3IuaXN0aW8uaW8vY29tcG9uZW50EhEaD0luZ3Jlc3NHYXRld2F5cwohChFwb2QtdGVtcGxhdGUtaGFzaBIMGgo1NjRkZjk1NDg1ChIKB3JlbGVhc2USBxoFaXN0aW8KOQofc2VydmljZS5pc3Rpby5pby9jYW5vbmljYWwtbmFtZRIWGhRpc3Rpby1pbmdyZXNzZ2F0ZXdheQovCiNzZXJ2aWNlLmlzdGlvLmlvL2Nhbm9uaWNhbC1yZXZpc2lvbhIIGgZsYXRlc3QKIgoXc2lkZWNhci5pc3Rpby5pby9pbmplY3QSBxoFZmFsc2UKGgoHTUVTSF9JRBIPGg1jbHVzdGVyLmxvY2FsCi8KBE5BTUUSJxolaXN0aW8taW5ncmVzc2dhdGV3YXktNTY0ZGY5NTQ4NS1ndms2NAobCglOQU1FU1BBQ0USDhoMaXN0aW8tc3lzdGVtCl0KBU9XTkVSElQaUmt1YmVybmV0ZXM6Ly9hcGlzL2FwcHMvdjEvbmFtZXNwYWNlcy9pc3Rpby1zeXN0ZW0vZGVwbG95bWVudHMvaXN0aW8taW5ncmVzc2dhdGV3YXkKFwoRUExBVEZPUk1fTUVUQURBVEESAioACicKDVdPUktMT0FEX05BTUUSFhoUaXN0aW8taW5ncmVzc2dhdGV3YXk=
2021-07-09T18:31:45.221514Z	trace	envoy http	[C2118] completed header: key=x-envoy-peer-metadata-id value=router~<IP_ADDRESS>~istio-ingressgateway-564df95485-gvk64.istio-system~istio-system.svc.cluster.local
2021-07-09T18:31:45.221516Z	trace	envoy http	[C2118] completed header: key=x-envoy-attempt-count value=1
2021-07-09T18:31:45.221518Z	trace	envoy http	[C2118] completed header: key=x-b3-traceid value=5fc2a3a4aa8ce39c49d1c38d60074db4
2021-07-09T18:31:45.221520Z	trace	envoy http	[C2118] completed header: key=x-b3-spanid value=49d1c38d60074db4
2021-07-09T18:31:45.221526Z	trace	envoy http	[C2118] onHeadersCompleteBase
2021-07-09T18:31:45.221527Z	trace	envoy http	[C2118] completed header: key=x-b3-sampled value=1
2021-07-09T18:31:45.221531Z	trace	envoy http	[C2118] codec entering upgrade mode.
2021-07-09T18:31:45.221533Z	trace	envoy http	[C2118] Server: onHeadersComplete size=19
2021-07-09T18:31:45.221547Z	debug	envoy http	[C2118][S18324486996342923096] request headers complete (end_stream=false):
':authority', 'gatewaytestc.nextensio.net:443'
':path', '/'
':method', 'GET'
'upgrade', 'websocket'
'connection', 'Upgrade'
'sec-websocket-key', 'dGhlIHNhbXBsZSBub25jZQ=='
'sec-websocket-version', '13'
'user-agent', 'Go-http-client/1.1'
'x-nextensio-connect', 'nextensio-default-nextensio-net'
'content-length', '0'
'x-forwarded-for', '<IP_ADDRESS>'
'x-forwarded-proto', 'https'
'x-envoy-internal', 'true'
'x-request-id', 'c9b5c1ad-4418-9fc4-9707-a63d08d2fd51'
'x-envoy-decorator-operation', 'nextensio-default-nextensio-net-http-outside.nxt-nextensio.svc.cluster.local:443/*'
'x-envoy-peer-metadata', 'ChQKDkFQUF9DT05UQUlORVJTEgIaAAoaCgpDTFVTVEVSX0lEEgwaCkt1YmVybmV0ZXMKGQoNSVNUSU9fVkVSU0lPThIIGgYxLjEwLjIKvwMKBkxBQkVMUxK0AyqxAwodCgNhcHASFhoUaXN0aW8taW5ncmVzc2dhdGV3YXkKEwoFY2hhcnQSChoIZ2F0ZXdheXMKFAoIaGVyaXRhZ2USCBoGVGlsbGVyCjYKKWluc3RhbGwub3BlcmF0b3IuaXN0aW8uaW8vb3duaW5nLXJlc291cmNlEgkaB3Vua25vd24KGQoFaXN0aW8SEBoOaW5ncmVzc2dhdGV3YXkKGQoMaXN0aW8uaW8vcmV2EgkaB2RlZmF1bHQKMAobb3BlcmF0b3IuaXN0aW8uaW8vY29tcG9uZW50EhEaD0luZ3Jlc3NHYXRld2F5cwohChFwb2QtdGVtcGxhdGUtaGFzaBIMGgo1NjRkZjk1NDg1ChIKB3JlbGVhc2USBxoFaXN0aW8KOQofc2VydmljZS5pc3Rpby5pby9jYW5vbmljYWwtbmFtZRIWGhRpc3Rpby1pbmdyZXNzZ2F0ZXdheQovCiNzZXJ2aWNlLmlzdGlvLmlvL2Nhbm9uaWNhbC1yZXZpc2lvbhIIGgZsYXRlc3QKIgoXc2lkZWNhci5pc3Rpby5pby9pbmplY3QSBxoFZmFsc2UKGgoHTUVTSF9JRBIPGg1jbHVzdGVyLmxvY2FsCi8KBE5BTUUSJxolaXN0aW8taW5ncmVzc2dhdGV3YXktNTY0ZGY5NTQ4NS1ndms2NAobCglOQU1FU1BBQ0USDhoMaXN0aW8tc3lzdGVtCl0KBU9XTkVSElQaUmt1YmVybmV0ZXM6Ly9hcGlzL2FwcHMvdjEvbmFtZXNwYWNlcy9pc3Rpby1zeXN0ZW0vZGVwbG95bWVudHMvaXN0aW8taW5ncmVzc2dhdGV3YXkKFwoRUExBVEZPUk1fTUVUQURBVEESAioACicKDVdPUktMT0FEX05BTUUSFhoUaXN0aW8taW5ncmVzc2dhdGV3YXk='
'x-envoy-peer-metadata-id', 'router~<IP_ADDRESS>~istio-ingressgateway-564df95485-gvk64.istio-system~istio-system.svc.cluster.local'
'x-envoy-attempt-count', '1'
'x-b3-traceid', '5fc2a3a4aa8ce39c49d1c38d60074db4'
'x-b3-spanid', '49d1c38d60074db4'
'x-b3-sampled', '1'

2021-07-09T18:31:45.221666Z	trace	envoy http	[C2118][S18324486996342923096] decode headers called: filter=0x5593d0f58fc0 status=0
2021-07-09T18:31:45.221686Z	debug	envoy filter	AuthenticationFilter::decodeHeaders with config
policy {
  peers {
    mtls {
      mode: PERMISSIVE
    }
  }
}
skip_validate_trust_domain: true

2021-07-09T18:31:45.221691Z	debug	envoy filter	[C2118] validateX509 mode PERMISSIVE: ssl=true, has_user=true
2021-07-09T18:31:45.221692Z	debug	envoy filter	[C2118] trust domain validation skipped
2021-07-09T18:31:45.221694Z	debug	envoy filter	Set peer from X509: cluster.local/ns/istio-system/sa/istio-ingressgateway-service-account
2021-07-09T18:31:45.221696Z	trace	envoy filter	Got request path /
2021-07-09T18:31:45.221698Z	debug	envoy filter	Set principal from peer: cluster.local/ns/istio-system/sa/istio-ingressgateway-service-account
2021-07-09T18:31:45.221699Z	debug	envoy filter	Origin authenticator succeeded
2021-07-09T18:31:45.221727Z	debug	envoy filter	Saved Dynamic Metadata:
fields {
  key: "request.auth.principal"
  value {
    string_value: "cluster.local/ns/istio-system/sa/istio-ingressgateway-service-account"
  }
}
fields {
  key: "source.namespace"
  value {
    string_value: "istio-system"
  }
}
fields {
  key: "source.principal"
  value {
    string_value: "cluster.local/ns/istio-system/sa/istio-ingressgateway-service-account"
  }
}
fields {
  key: "source.user"
  value {
    string_value: "cluster.local/ns/istio-system/sa/istio-ingressgateway-service-account"
  }
}

2021-07-09T18:31:45.221731Z	trace	envoy http	[C2118][S18324486996342923096] decode headers called: filter=0x5593d03b6a10 status=0
2021-07-09T18:31:45.221737Z	trace	envoy http	[C2118][S18324486996342923096] decode headers called: filter=0x5593d0f34fc0 status=0
2021-07-09T18:31:45.221741Z	trace	envoy http	[C2118][S18324486996342923096] decode headers called: filter=0x5593d0e60310 status=0
2021-07-09T18:31:45.221749Z	trace	envoy http	[C2118][S18324486996342923096] decode headers called: filter=0x5593d079ccb0 status=0
2021-07-09T18:31:45.221754Z	debug	envoy router	[C2118][S18324486996342923096] cluster 'inbound|443||' match for URL '/'
2021-07-09T18:31:45.221768Z	debug	envoy upstream	transport socket match, socket default selected for host with address <IP_ADDRESS>:443
2021-07-09T18:31:45.221771Z	debug	envoy upstream	Created host <IP_ADDRESS>:443.
2021-07-09T18:31:45.221801Z	debug	envoy upstream	addHost() adding <IP_ADDRESS>:443
2021-07-09T18:31:45.221806Z	debug	envoy router	[C2118][S18324486996342923096] router decoding headers:
':authority', 'gatewaytestc.nextensio.net:443'
':path', '/'
':method', 'GET'
':scheme', 'https'
'upgrade', 'websocket'
'connection', 'Upgrade'
'sec-websocket-key', 'dGhlIHNhbXBsZSBub25jZQ=='
'sec-websocket-version', '13'
'user-agent', 'Go-http-client/1.1'
'x-nextensio-connect', 'nextensio-default-nextensio-net'
'content-length', '0'
'x-forwarded-for', '<IP_ADDRESS>'
'x-forwarded-proto', 'https'
'x-request-id', 'c9b5c1ad-4418-9fc4-9707-a63d08d2fd51'
'x-envoy-attempt-count', '1'
'x-envoy-internal', 'true'
'x-forwarded-client-cert', 'By=spiffe://cluster.local/ns/nxt-nextensio/sa/default;Hash=9b3cdd9d344004b22a09d8010c4998f5fb27edecd90dd9856ef66b96de48650f;Subject="";URI=spiffe://cluster.local/ns/istio-system/sa/istio-ingressgateway-service-account'
'x-b3-traceid', '5fc2a3a4aa8ce39c49d1c38d60074db4'
'x-b3-spanid', 'dee418e272ee39b7'
'x-b3-parentspanid', '49d1c38d60074db4'
'x-b3-sampled', '1'

2021-07-09T18:31:45.221812Z	debug	envoy pool	queueing stream due to no available connections
2021-07-09T18:31:45.221814Z	debug	envoy pool	trying to create new connection
2021-07-09T18:31:45.221826Z	trace	envoy pool	ConnPoolImplBase 0x5593d0953980, ready_clients_.size(): 0, busy_clients_.size(): 0, connecting_clients_.size(): 0, connecting_stream_capacity_: 0, num_active_streams_: 0, pending_streams_.size(): 1 per upstream preconnect ratio: 1
2021-07-09T18:31:45.221828Z	debug	envoy pool	creating a new connection
2021-07-09T18:31:45.221861Z	debug	envoy client	[C2119] connecting
2021-07-09T18:31:45.221864Z	debug	envoy connection	[C2119] connecting to <IP_ADDRESS>:443
2021-07-09T18:31:45.221882Z	debug	envoy upstream	membership update for TLS cluster inbound|443|| added 1 removed 0
2021-07-09T18:31:45.221890Z	debug	envoy upstream	re-creating local LB for TLS cluster inbound|443||
2021-07-09T18:31:45.221908Z	debug	envoy upstream	membership update for TLS cluster inbound|443|| added 1 removed 0
2021-07-09T18:31:45.221917Z	debug	envoy upstream	re-creating local LB for TLS cluster inbound|443||
2021-07-09T18:31:45.222099Z	debug	envoy connection	[C2119] connection in progress
2021-07-09T18:31:45.222141Z	trace	envoy pool	not creating a new connection, shouldCreateNewConnection returned false.
2021-07-09T18:31:45.222148Z	trace	envoy http	[C2118][S18324486996342923096] decode headers called: filter=0x5593d03b7a40 status=1
2021-07-09T18:31:45.222152Z	trace	envoy http	[C2118] message complete
2021-07-09T18:31:45.222154Z	trace	envoy http	[C2118] Pausing parser due to upgrade.
2021-07-09T18:31:45.222157Z	trace	envoy http	[C2118] parsed 1852 bytes
2021-07-09T18:31:45.222158Z	trace	envoy http	[C2118] direct-dispatched 1002 bytes
2021-07-09T18:31:45.222160Z	trace	envoy http	[C2118] body size=1002
2021-07-09T18:31:45.222165Z	trace	envoy http	[C2118][S18324486996342923096] decode data called: filter=0x5593d0f58fc0 status=0
2021-07-09T18:31:45.222167Z	trace	envoy http	[C2118][S18324486996342923096] decode data called: filter=0x5593d03b6a10 status=0
2021-07-09T18:31:45.222168Z	trace	envoy http	[C2118][S18324486996342923096] decode data called: filter=0x5593d0f34fc0 status=0
2021-07-09T18:31:45.222170Z	trace	envoy http	[C2118][S18324486996342923096] decode data called: filter=0x5593d0e60310 status=0
2021-07-09T18:31:45.222172Z	trace	envoy http	[C2118][S18324486996342923096] decode data called: filter=0x5593d079ccb0 status=0
2021-07-09T18:31:45.222175Z	trace	envoy router	[C2118][S18324486996342923096] buffering 1002 bytes
2021-07-09T18:31:45.222178Z	trace	envoy http	[C2118][S18324486996342923096] decode data called: filter=0x5593d03b7a40 status=3
2021-07-09T18:31:45.222184Z	debug	envoy upstream	membership update for TLS cluster inbound|443|| added 1 removed 0
2021-07-09T18:31:45.222189Z	debug	envoy upstream	re-creating local LB for TLS cluster inbound|443||
2021-07-09T18:31:45.222233Z	trace	envoy connection	[C2119] socket event: 2
2021-07-09T18:31:45.222253Z	trace	envoy connection	[C2119] write ready
2021-07-09T18:31:45.222266Z	debug	envoy connection	[C2119] connected
2021-07-09T18:31:45.222277Z	trace	envoy connection	[C2119] raising connection event 2
2021-07-09T18:31:45.222289Z	debug	envoy client	[C2119] connected
2021-07-09T18:31:45.222316Z	debug	envoy pool	[C2119] attaching to next stream
2021-07-09T18:31:45.222338Z	debug	envoy pool	[C2119] creating stream
2021-07-09T18:31:45.222347Z	debug	envoy router	[C2118][S18324486996342923096] pool ready
2021-07-09T18:31:45.222363Z	trace	envoy connection	[C2119] writing 808 bytes, end_stream false
2021-07-09T18:31:45.222366Z	trace	envoy connection	[C2119] writing 1002 bytes, end_stream false
2021-07-09T18:31:45.222369Z	trace	envoy connection	[C2119] write ready
2021-07-09T18:31:45.222387Z	trace	envoy connection	[C2119] write returns: 1810
2021-07-09T18:31:45.222395Z	trace	envoy connection	[C2119] socket event: 2
2021-07-09T18:31:45.222396Z	trace	envoy connection	[C2119] write ready
2021-07-09T18:31:45.223481Z	trace	envoy connection	[C2119] socket event: 3
2021-07-09T18:31:45.223530Z	trace	envoy connection	[C2119] write ready
2021-07-09T18:31:45.223719Z	trace	envoy connection	[C2119] read ready. dispatch_buffered_data=false
2021-07-09T18:31:45.223778Z	trace	envoy connection	[C2119] read returns: 1131
2021-07-09T18:31:45.223788Z	trace	envoy connection	[C2119] read error: Resource temporarily unavailable
2021-07-09T18:32:14.549170Z	trace	envoy http	[C2119] parsing 215 bytes
2021-07-09T18:32:14.549172Z	trace	envoy http	[C2119] direct-dispatched 215 bytes
2021-07-09T18:32:14.549208Z	trace	envoy http	[C2118][S18324486996342923096] encode data called: filter=0x5593d03b7960 status=0
2021-07-09T18:32:14.549212Z	trace	envoy http	[C2118][S18324486996342923096] encode data called: filter=0x5593d03b69a0 status=0
2021-07-09T18:32:14.549214Z	trace	envoy http	[C2118][S18324486996342923096] encode data called: filter=0x5593d03b6380 status=0
2021-07-09T18:32:14.549217Z	trace	envoy http	[C2118][S18324486996342923096] encode data called: filter=0x5593d0e61420 status=0
2021-07-09T18:32:14.549219Z	trace	envoy http	[C2118][S18324486996342923096] encoding data via codec (size=215 end_stream=false)

cc @alyssawilk

I figured out the thing, it was my bad, the websocket buffering was getting flow controlled properly, I had not set the http2_protocol_options under "typed_extension_protocol_options" - so it was http2 that was buffering like crazy, I set that option and its fine for now. More details at https://github.com/istio/istio/issues/33416

phew!  thanks for the update :-)


Syntax error

I'm using your firetv server within a homeassistant addon vor hassio (https://github.com/mpneuried/hassio-custom-addons)
starting version 3.2.4
Traceback (most recent call last):
File "/usr/bin/firetv-server", line 11, in
load_entry_point('firetv==1.0.5', 'console_scripts', 'firetv-server')()
File "/usr/lib/python2.7/site-packages/pkg_resources/init.py", line 561, in load_entry_point
return get_distribution(dist).load_entry_point(group, name)
File "/usr/lib/python2.7/site-packages/pkg_resources/init.py", line 2631, in load_entry_point
return ep.load()
File "/usr/lib/python2.7/site-packages/pkg_resources/init.py", line 2291, in load
return self.resolve()
File "/usr/lib/python2.7/site-packages/pkg_resources/init.py", line 2297, in resolve
module = import(self.module_name, fromlist=['name'], level=0)
File "/usr/lib/python2.7/site-packages/firetv/main.py", line 36
def is_valid_host(host: str):
^
SyntaxError: invalid syntax

This project does not support python2 (type annotations for methods are not supported there). The setup.py could be updated to add python_requires='>=3.4' or similar.

This was a change some days ago:
https://github.com/happyleavesaoc/python-firetv/commit/5de43fc45c32245facb8d12121c11903bc19b421

Fixed in https://github.com/happyleavesaoc/python-firetv/commit/55406c66d13a83f4be1b07e5d001dbacba19149d


Fix disabled checked switches style

Proposed changes
There's a style problem when a switch disabled but checked, the background color should be disabled color, not enabled color. This is just a simple fix.
Codepen:
Problem example
Types of changes

[x] Bug fix (non-breaking change which fixes an issue).
[ ] New feature (non-breaking change which adds functionality).
[ ] Breaking change (fix or feature that would cause existing functionality to change).

Checklist:

[x] I have read the CONTRIBUTING document.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Oh btw, I forgot to include the reference design
Reference


GanttTimeline GanttBar GanttPopup

GanttTimeline GanttBar GanttPopup
How to use it?

Those are kind of lower level components used to abstract some of the complexity of GanttRow. There's a great example that shows how to use the react Gantt chart at the link below.
https://github.com/codejamninja/react-gantt/blob/master/demo/script.js

1、now，I need to modify these  kind of lower level components style，such as GanttTimeline scale，how to modify ？
2.You are a Seven  day scale. How do I scale every month?  I try set ’secondFormat="YYYY-MM" minuteFormat="YYYY-MM" hourFormat="YYYY-MM" dayFormat="YYYY-MM" weekFormat="YYYY-MM" monthFormat="YYYY-MM" yearFormat="YYYY-MM" ‘，but Four times in the same month

1、now，I need to modify these kind of lower level components style，such as GanttTimeline style，how to modify ？
2.You are a Seven day scale. How do I scale every month? I try set ’secondFormat="YYYY-MM" minuteFormat="YYYY-MM" hourFormat="YYYY-MM" dayFormat="YYYY-MM" weekFormat="YYYY-MM" monthFormat="YYYY-MM" yearFormat="YYYY-MM" ‘，but Four times in the same month

At the moment you can't modify it without forking the repo and making a pull request.
You could fork it and install it with npm the following way . . .
npm install --save react-gantt<EMAIL_ADDRESS>


fix subset doesn't return ImageGeometry

I don't think this will maintain the axis label order?

additionally a similar trick should be done for the AcquisitionData

I also was looking at AcquisitionGeometry. It seems to me that dimension parameter doesn't have sense
https://github.com/vais-ral/CCPi-Framework/blob/fix_subset/Wrappers/Python/ccpi/framework/framework.py#L251
One can write
sgeometry = AcquisitionGeometry(dimension=2, angles=numpy.linspace(0, 180, num=10),
                                        geom_type='parallel', pixel_num_v=3,
                                        pixel_num_h=5, channels=2)
print (sgeometry)

returns the following which is just storing the parameters without checks.
Number of dimensions: 2
angles: [  0.  20.  40.  60.  80. 100. 120. 140. 160. 180.]
voxel_num : h5,v3
voxel size: h1,v1
geometry type: parallel
distance source-detector: None
distance center-detector: None
number of channels: 2

If you actually allocate an AcquisitionData with that geometry you get a 4D not 2D. So why do we have dimensions?
vol = sgeometry.allocate()
print (vol.shape)

>>> (2, 10, 3, 5)

additionally a similar trick should be done for the AcquisitionData

@paskino ,technically, the user might want to create a subset of AcquisitionData with only one angle
Let's say something like this
ag = AcquisitionGeometry(geom_type = 'cone',
                         dimension = '3D',
                         angles = np.linspace(0,np.pi,180),
                         pixel_num_h = 100,
                         pixel_size_h = 2,
                         pixel_num_v = 200,
                         pixel_size_v = 3,
                         dist_source_center = 100,
                         dist_center_detector = 200,
                         channels = 10)
ad = ag.allocate()
sid = ad.subset(angle = 3)

Currently, this will fail, because `AcquisitionData' init requires angles.

Test of reader.py fail at this line in test.
Geometry should have the labels and output should be allocated with allocate method.

closes #312


Angular 13 & 14

If this repo upgrades to Angular 14, I would like to make a YouTube series where I refactor the state management into a more reactive pattern than standard NgRx, and then from that to StateAdapt. I might open a PR to compare, then close it.
If nobody else has the bandwidth, I might do this. But I'm not familiar with this codebase.

Thanks for reminding me to upgrade the repo for the latest version of Angular. I did that a few weeks ago, hope you enjoy it.
I'm not sure about the refactor you suggested being useful, but if it's a fun exercise for you, what could it hurt? The app is already pretty heavily performance optimized using NgRx and Immutable.js so that it runs well on mobile devices, so you'll want to do some analysis to make sure any refactor keeps the same performance.
If you wanted to refactor something that would be helpful to the project as it is right now, our use of NgRX and RXJS in angular components is outdated. Specifically, the @Effect decorator from ngrx/effects and the way we use combineLatest from rxjs are deprecated. A refactor to remove the use of those deprecated apis would be very helpful.
I'll close this for now since Angular was updated. Thanks again!


Enum type in Query annotation does not work in in clause

@Query(value = "select category, text, count(id) as count from table_name where from_type in (:fromTypes) group by text,category")
List<Stats> statsByFromType(Collection<FromType> fromTypes);

The FromType here is an enum type, but the in clause in the Query annotation cannot find the data.
The executed sql shows that FromType is converted to int type, but the actual string type is stored in the database

I also found that issue, but the problem is different. This problem occurs in the in clause, the parameter is a Collection.


Move more config to docker defaults

Motivation

Solution

PR Checklist

[ ] Added Tests
[ ] Added Documentation
[ ] Updated the changelog

Codecov Report

Merging #47 (62ece3e) into master (8912346) will not change coverage.
The diff coverage is n/a.

Additional details and impacted files

@@           Coverage Diff           @@
##           master      #47   +/-   ##
=======================================
  Coverage   41.88%   41.88%
=======================================
  Files          30       30
  Lines        6867     6867
=======================================
  Hits         2876     2876
  Misses       3991     3991

Flag
Coverage Δ

test
41.88% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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 8912346...62ece3e. Read the comment docs.


Define Enso epoch start as 15th October 1582.

Pull Request Description
Define start of Enso epoch as 15th of October 1582.
Important Notes

Some (Gregorian) calendar related functionalities within Date and Date_Time now fails with Time_Error if the receiving Date/Date_Time is before the epoch start, e.g., week_of_year.

Checklist
Please include the following checklist in your PR:

[x] The documentation has been updated if necessary.
[x] All code conforms to the
Scala,
Java,
and
Rust
style guides.
All code has been tested:

[x] Unit tests have been written where possible.
[x] If GUI codebase was changed: Enso GUI was tested when built using BOTH
./run ide build and ./run ide watch.

One last thing - from the earlier discussions I was not sure if we want to return the dataflow error for these operations. My initial understanding was that we allow to return a result, but attach a dataflow warning to such an operation saying that the result cannot be trusted. This is a bit more permissive as the user can still use the operations, they are just warned that results may be wrong. It is a bit more dangerous as it's easier to remove the warnings though. I have no opinion on this, @jdunkerley what was the idea here? Do we want dataflow errors or warnings?

The original idea was to use warnings. I will change the behavior so that the methods that fail with an exception in the underlying java methods will fail with an error, and all the other methods that now fail with error, will just attach a warning instead. So that, e.g., trying to get number of days for a Date_Time that is before the epoch will attach a warning and won't fail with an error.

One last thing - from the earlier discussions I was not sure if we want to return the dataflow error for these operations. My initial understanding was that we allow to return a result, but attach a dataflow warning to such an operation saying that the result cannot be trusted. This is a bit more permissive as the user can still use the operations, they are just warned that results may be wrong. It is a bit more dangerous as it's easier to remove the warnings though. I have no opinion on this, @jdunkerley what was the idea here? Do we want dataflow errors or warnings?

Yes the suggestion was to return the values with a warning attached. This would allow the users to perform the computation but warn that the values are possibly wrong.


Hex8

The ColorPicker parses 8-digits hex correclty, but onChange is always received the hex value in 6-digit format. How can I use the value in hex with opactiy?

+1 on hex8 support.
Apparently this block is to blame:
https://github.com/casesandberg/react-color/blob/master/src/helpers/color.js#L51

+1

+1

i find a way fix this, use patch-package to fix。
Apparently this block is to blame:
https://github.com/casesandberg/react-color/blob/master/src/helpers/color.js#L51

i find other way to fix this issues
 <div           onInput={(event) => {             const target = event?.target as HTMLInputElement;             const value = target?.value;             console.log(value)           }}         >           <SketchPicker             presetColors={[]}             onChange={(value) => {           />         </div>


Fix Indentation, Removed repetitive code

Indentation fix in Infobox.js
Added fall-through (i.e OR for key case, to avoid repetitive code) - For gradient navigation using left/right arrow keys

Yea kinda makes sense to move the dupe code in a function and calling it inside the switch statements.. no issues though! Glad to share something new with you ;)


PR: Add sqrtpi package

Resolves https://github.com/stdlib-js/todo/issues/1185
Description

What is the purpose of this pull request?

This pull request adds sqrtpi package
Related Issues

Does this pull request have any related issues?

This pull request:

resolves https://github.com/stdlib-js/todo/issues/1185

Questions

Any questions for reviewers of this pull request?

No.
Other

Any other information relevant to this pull request? This may include screenshots, references, and/or implementation notes.

No.
Checklist

Please ensure the following tasks are completed before submitting this pull request.

[x] Read, understood, and followed the contributing guidelines.

@stdlib-js/reviewers

@steff456 Went ahead and applied the requested changes. If you could do another review to ensure that I did not miss anything, that would be great!

I think the PR is ready! I don't see anymore changes that are needed from your review. Thanks a lot :)


How to catch events?

Is it possible to catch events for example when user selects something?

Ok in API I found setValue method: https://github.com/brianreavis/selectize.js/blob/master/docs/api.md


[API] About batch_normalization

AFAIK, batch normalization is a process should be done before activation happens for every layer except the last layer.
So I think, in the public api level, bn layer can be hidden. Rather, it can be property of either layer or Network
eg) if you want to make a bn layer.
current version requires to declare a layer.
# Network Section : Network
[Network]
Type = NeuralNetwork	# Network Type : Regression, KNN, NeuralNetwork
Layers = inputlayer \
         fc1layer \
         batchnormalization \
         fc2layer \
         batchnormalization2 \
	 outputlayer	#Layers of Neuralnetwork
# /** omitted **/

# Layer Section : Name
[inputlayer]
Type = InputLayer

[fc1layer]
Type = FullyConnectedLayer

[fc2layer]
Type = FullyConnectedLayer

[batchnormalization]
Type = BatchNormalizationLayer

[batchnormalization2]
Type = BatchNormalizationLayer

[outputlayer]
Type = OutputLayer

but this could be more concise if we put bn_layer as a properties like:
# Network Section : Network
[Network]
Type = NeuralNetwork	# Network Type : Regression, KNN, NeuralNetwork
Layers = inputlayer \
         fc1layer \
         fc2layer \
	 outputlayer	#Layers of Neuralnetwork
# /** omitted **/

# Layer Section : Name
[inputlayer]
Type = InputLayer

[fc1layer]
Type = FullyConnectedLayer
BatchNormalize = true

[fc2layer]
Type = FullyConnectedLayer
BatchNormalize = true

[outputlayer]
Type = OutputLayer

It would be more concise if we assume that bn follows just before every activation happens.
Since we can make it as a Network properties:
# Network Section : Network
[Network]
Type = NeuralNetwork	# Network Type : Regression, KNN, NeuralNetwork
Layers = inputlayer \
         fc1layer \
         fc2layer \
	 outputlayer	#Layers of Neuralnetwork
BatchNormalize = true
# /** omitted **/

# Layer Section : Name
[inputlayer]
Type = InputLayer

[fc1layer]
Type = FullyConnectedLayer

[fc2layer]
Type = FUllyConnectedLayer

[outputlayer]
Type = OutputLayer

So, I'd like to hear which one would be the best for us. @jijoongmoon  @kparichay

:octocat: cibot: Thank you for posting issue #209. The person in charge will reply soon.

@zhoonit Overall I agree to having batch normalization as a property for an individual layer (just like activation). Its more cleaner and inline with existing frameworks style.
However, the constraint bn follows just before every activation happens is not necessary. How about adding another ini config batch_normalize_after_activation which is false by default?

@zhoonit Overall I agree to having batch normalization as a property for an individual layer (just like activation). Its more cleaner and inline with existing frameworks style.
However, the constraint bn follows just before every activation happens is not necessary. How about adding another ini config batch_normalize_after_activation which is false by default?

Sounds good idea. I will work to make bn as a layer property first, and we could extend with batch_normalize_after_activation prop


Use two AZs

Right now the template is deploying an autoscaling group across every AZ in a region.  We probably want it to split an even number of nodes over two.
There's a wider question of how MDS impacts this that I don't know the answer to yet.

Not quite sure if this is the right approach.  Need more discussion with Karthik and Tony.  I'm going to continue using every available AZ until then.

I wonder what would happen if we had a replica count of 1 but a server group per AZ, which would mean 2 copies of the data are spread across 2, 3 or more server groups.

Perry confirmed this'll work well:
I’m debating adding some code to the various cloud templates where (let’s take AWS as an example) a node would call the metadata service on boot to check what AZ it’s in.  It would then assign itself to a server group with the name of that AZ.  Assuming our replica placement takes advantage of that, it would allow us to get the maximum spread across AZs in a region, rather than making use of only two as seems to be the recommendation from some conversations I’ve had.  An added benefit is that is way easier to code and maintain that restricting to two regions.

https://developer.couchbase.com/documentation/server/current/cli/cbcli/group-manage.html

This is a high priority.


Currently buildah run is not handling command options correctly

This patch will allow commands like
buildah run $ctr ls -lZ /
To work correctly.
Signed-off-by: Daniel J Walsh<EMAIL_ADDRESS>

LGTM

@rh-atomic-bot r=TomSweeneyRedHat

"Error determining manifest MIME type for docker://registry.fedoraproject.org/fedora-minimal:latest: unauthorized: authentication required" -  fedoraproject.org is down?

bot, retest this please

@rh-atomic-bot r+

FWIW I was previously doing:
buildah config ${container} --entrypoint blah etc., and that broke after this PR.
But eh, after reading now I understand why the change was made.

(It's tricky since the rest of my code is lots of buildah run ${container} arguments...)


Readme

Codecov Report

Merging #34 into dev will decrease coverage by 1.84%.
The diff coverage is 65.67%.

@@            Coverage Diff             @@
##              dev      #34      +/-   ##
==========================================
- Coverage   76.20%   74.35%   -1.85%
==========================================
  Files          11       11
  Lines         374      390      +16
==========================================
+ Hits          285      290       +5
- Misses         89      100      +11

Impacted Files
Coverage Δ

peon/src/comandline/comandline.py
0.00% <0.00%> (ø)

peon/src/lint/principles/links.py
100.00% <ø> (ø)

peon/src/lint/report/report.py
60.00% <ø> (ø)

peon/src/project/file/file.py
64.28% <ø> (ø)

...ject/file/function_def/expression/returned_expr.py
100.00% <ø> (ø)

peon/src/lint/principles/principles.py
50.84% <40.00%> (ø)

peon/src/lint/lint.py
31.57% <55.55%> (ø)

peon/src/comandline/project_tree.py
93.10% <93.10%> (ø)

peon/src/project/ast_analyze.py
58.82% <100.00%> (ø)

peon/src/project/file/class_def/classes.py
97.05% <100.00%> (ø)

... and 2 more

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 e2565a4...7f978d6. Read the comment docs.


"SetMeleeKill *" will now make everything a target

we could even make a Like regex here too, but that'd waste a lot more cpu and have a very limited use case, so i just suggest * for everything, for now :p

related: http://www.blackdtools.net/showthread.php?62650-Help-with-SetMeleekill-to-ANY-monster


Vagrant 1.8.1 asked for password

Using vagrant 1.8.1, and run vagrant up in Android directory has the following problem.
==> default: Preparing to edit /etc/exports. Administrator privileges will be required...
Password:
Sorry, try again.
Tried with password 'vagrant' but didn't work.

OK, it's asking for the host password.


Can CLIENT ID command on startup be skipped?

on startup fred will send a CLIENT ID command to the server.
I am wondering if that is a hard requirement of the way fred is implemented or if its just a nice to have and we could expose a config to the user allowing it to be disabled?

Hey @rukai, it's not a hard requirement for the client to function at all, but some things may not work. In 7.1.0 it was made optional (via https://github.com/aembke/fred.rs/issues/176), but I haven't fully tested the implications of that.
If I had to guess it likely only impacts the connection blocking interface (Blocking::Error or Blocking::interrupt), but I'm not entirely sure.

ah, funnily enough, I actually want the opposite of that PR.
My use case is that I have a redis proxy, and if the proxy is misconfigured then it will send an error response upon receiving its first request and then terminate the connection.
So if fred sends a message on connection init and then discards the result, the connection will be terminated with no error given to the user.
So I either want to:

wait_for_connect should return Err containing error response of CLIENT ID when it fails.
skip running CLIENT ID all together

Oh I see what you mean. If the first command was AUTH or HELLO would you see the error then?
I could also change the init logic to send PING first if no creds are provided. In that case the first command would always be PING, AUTH, or HELLO, and the client wouldn't ignore the result of any of those.

That would fix the issue yeah, but I imagine most people would prefer to avoid sending further unnecessary commands as that would delay start up of the application.

Oh wait, but as you said it already sends AUTH when using authentication right?
Then it would just be bringing it to the same level as an authenticated session which seems fine.

Sounds good. I added this in my working branch so it'll be included in 8.0.0.

Added in 8.0.0 (https://github.com/aembke/fred.rs/pull/199)


Support GatewayServerMiddleware and AddPassedHeader

WHY
WHAT
REF

Codecov Report

Merging #22 into master will increase coverage by 1.88%.
The diff coverage is 66.66%.

@@            Coverage Diff             @@
##           master      #22      +/-   ##
==========================================
+ Coverage   18.18%   20.06%   +1.88%
==========================================
  Files          33       33
  Lines         902      897       -5
==========================================
+ Hits          164      180      +16
+ Misses        730      709      -21
  Partials        8        8

Impacted Files
Coverage Δ

pkg/grapiserver/config.go
0% <ø> (ø)
:arrow_up:

pkg/grapiserver/builder.go
0% <0%> (ø)
:arrow_up:

pkg/grapiserver/gateway.go
0% <0%> (ø)
:arrow_up:

pkg/grapiserver/passing_header_middleware.go
100% <100%> (ø)

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 719aad9...60ca1ef. Read the comment docs.


Add key expiry timeouts

This adds an auth section to config/kansa.yaml, which now defines the validity time of keys as well as sessions. By default, sessions are valid for five days and keys for one year. For admins, however, keys are only valid for five days.
When attempting login with an expired key, the key is automatically reset and emailed, and the server responds to the request with a 403 HTTP status and a body with { "status": "expired" }.

I think you should look into an authentication middleware framework that can handle this end to end, with a redirection to a custom login form if you need it. Shared secret auth is a generally bad idea from a security POV and I'd rather see the effort in place to drop it completely.

Given that our starting point is shared-secret authentication for Hugo nominations and voting, are you proposing that we get rid of that, or that we have a completely separate authentication system for admin users?

The latter; a pre-shared key to have limited access to voting makes sense, but admin should not be behind that kind of low-tech barrier

I decided to merge this, as my dev branch is building on top of it so much. Next step for auth is to enable proper 2FA.


UX: Show range of records shown vs. pages in paginated tables

Description
Offer more clarity on the range of records the seller is looking at in their dashboard vs. pages, i.e requiring math operations to map to the range of orders, transactions etc.
Current Behavior

Expected Behavior
Change Page 1 of 12 to Viewing 1-100 of 1,200
Pages

[ ] Finance > Incoming
[ ] Finance > Outgoing
[ ] Sales > Orders
[ ] Sales > Subscriptions
[ ] Products > Discounts

Basically one component to tweak: https://github.com/polarsource/polar/blob/main/clients/packages/polarkit/src/components/ui/atoms/datatable/DataTablePagination.tsx

@birkjernstrom I am picking this. Can you please assign it to me?


Repo sync for protected CLA branch

The pull request is created from master637383787948926739 to master to fix git push error for protected CLA branch

@cmcclister : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Load access fault on C906 during boot

Board Ox64, used the c906.config defconfig, compiled and flashed according instructions, sadly, after few seconds, C906 crashes as follows (E907 is OK):
Due having limited time for this, I can't play with JTAG and getting more information right now.
Please, any suggestions where I might do a mistake?
dynamic memory init success,heap size = 26 Kbyte
C906 start...
mtimer clk:1000000
linux load start...
len:0x006df29f

Un-handled Exception on CPU 1:
mstatus = 0x, FS=8403200, MPP=1, MPIE=3
mcause: 5, mtval = 0x, mepc = 0x

Load access fault

ra = 0x  sp = 0x  gp = 0x  tp = 0x
t0 = 0x  t1 = 0x  t2 = 0x  t3 = 0x
t4 = 0x  t5 = 0x  t6 = 0x
a0 = 0x  a1 = 0x  a2 = 0x  a3 = 0x
a4 = 0x  a5 = 0x  a6 = 0x  a7 = 0x
s0 = 0x  s1 = 0x  s2 = 0x  s3 = 0x
s4 = 0x  s5 = 0x  s6 = 0x  s7 = 0x
s8 = 0x  s9 = 0x  s10 = 0x s11 = 0x

Fixed by https://github.com/bouffalolab/bl808_linux/commit/73a5e95b665ec90ace218ac388d2bc166e0f719c


Clarify what constitutes a "strong local machine"

I've got an RTX 2070 SUPER 8GB and 32GB of system RAM.
When running the backend, I run into
2022-06-04 13:02:17.271909: W external/org_tensorflow/tensorflow/core/common_runtime/bfc_allocator.cc:479] Allocator (GPU_0_bfc) ran out of memory trying to allocate 768.00MiB (rounded to 805306368)requested by op
2022-06-04 13:02:17.272293: W external/org_tensorflow/tensorflow/core/common_runtime/bfc_allocator.cc:491] *********************************************************************_****************************__
2022-06-04 13:02:17.273116: E external/org_tensorflow/tensorflow/compiler/xla/pjrt/pjrt_stream_executor_client.cc:2141] Execution of replica 0 failed: RESOURCE_EXHAUSTED: Out of memory while trying to allocate 805306368 bytes.
BufferAssignment OOM Debugging.
BufferAssignment stats:
             parameter allocation:    16.4KiB
              constant allocation:        64B
        maybe_live_out allocation:    5.25GiB
     preallocated temp allocation:  288.04MiB
  preallocated temp fragmentation:       496B (0.00%)
                 total allocation:    5.53GiB
              total fragmentation:     5.3KiB (0.00%)

But I'm not sure if it is due to a configuration error, or if my system simply cannot handle the Mega model. Does anyone know the minimum requirement for GPU RAM?
This sort of information should be added to the readme, if it is available.

I'm using a RTX2060, I'm also receiving errors related to out-of memory errors.

Are you trying to run the environment with DALL-E Mini or DALL-E Mega?

Hi Sahar, and thanks so much for this repo!
I am wondering how much improvement on the images the Pro+ or local GPU can make. Do you have a sense of that?
I started a question for Boris that references Eleutherai's "plans" to create a larger pretrained model (https://github.com/borisdayma/dalle-mini/issues/208).
I wish this were something that distributed computing (like BIONC) could help, but I've heard it said the large memory requirements make DC solutions difficult.

mega-1 uses (together with the few hundred MiB of the VQGAN) a little under 12 GiB of VRAM.
You can use mega-1-fp16, it's half as big and almost as good. Note the parameter type for this model is jnp.float16, not bfloat16 (which is a leftover from an earlier attempt, I believe).

That's strange as mega-1 consumes 24GB on my RTX3090.
I have built docker image and during build for dalle-backend I have a lot of info that it run out of memory.

It turns out that JAX try to allocate to itself 90% of the GPU VRAM by default https://jax.readthedocs.io/en/latest/gpu_memory_allocation.html wich could be a problem if your GPU is also used for display.
I got dalle-mini working by setting XLA_PYTHON_CLIENT_ALLOCATOR=platform
On my RTX 3070Ti 8GB, mini-1 + VQGAN use 5GB of VRAM.
I was no able to run mega-1-fp16, it try to allocate f32 buffers, so I'm not sure the fp16 is doing anything.

Thanks @Hugi-R unfortunately, even with such fix my RTX2060 cannot run mini-1.
So I had to change jax to use CPU instead.

Upstream's example notebook (current HEAD master@db1ed25) makes sure to only load the parameters onto your GPU(s) once, in float16, and with XLA's allocator adjusted, total VRAM use (including display) stays under 8GiB on my Windows system. Take a look at what's changed there vs. backend/app.py here (which is based on an older version of that code).
You should be able to run mini-1 with a 4GB GPU, mega-1-fp16 with an 8GB GPU and mega-1 with a 12GB GPU with the current reference notebook (but not what's in this repository right now).
Mini-1 likely even fits in 3GB, mega-1-fp16 in 6GB, if you move VQGAN to CPU and/or the card's not responsible for display.
@mikaczma As mentioned above, XLA by default assumes it's running on dedicated hardware and reserves 90% of VRAM as soon as you request any (which can already happen from import statements). One easy way to avoid this is to put import os; os.environ["XLA_PYTHON_CLIENT_ALLOCATOR"] = "platform" (or whatever behavior you want, see link above) at the top of your code.
Also, not all out-of-memory errors are fatal. JAX/XLA tries a couple times. I get OOMs every time I load the fp32 model, but also succeed every time, with plenty of space left.

Hi all, thanks a lot for these insights. Adding this environment variable to the docker composer file did the trick.
This is the following memory usage for RTX2060:

Hope this environment variable is added by default in this project

Hi, also there is a hint if you have two different cards in the machine ;)
Set CUDA_VISIBLE_DEVICES=(number of card/s which are one type) eg. CUDA_VISIBLE_DEVICES=0 as I see JAX has issues when compiled and then run on different cards.
dalle-mini consumes ~6.5GB on 3090,  mega takes all I have :) 23GB but works and 3 images query time is ~20s

Hi, also there is a hint if you have two different cards in the machine ;)
Set CUDA_VISIBLE_DEVICES=(number of card/s which are one type) eg. CUDA_VISIBLE_DEVICES=0 as I see JAX has issues when compiled and then run on different cards.
dalle-mini consumes ~6.5GB on 3090,  mega takes all I have :) 23GB but works and 3 images query time is ~20s

Hey there, how is the image quality using your 3090? Is it much different than the Spaces demo online or the mega1-fp16? Thanks

No image quality will not change - sometimes I have even worse results.
9 images query takes ~120-140s with 70ish% GPU load

No image quality will not change - sometimes I have even worse results.
9 images query takes ~120-140s with 70ish% GPU load

Thanks for the images, appreciate that. I find the smaller model struggles most with human faces. Could you share a couple of those if possible?
I'm assuming the bottleneck is ram size, not processing time. Either that or the gains from shuffling data in and out somehow to the training ram or not enough to warrant it. I wish someone like eleuthera would share a pre-trained model 👍,

I assume that this issue is not related to quality of the model, so this should be moved to another topic.
But in fact even dalle-mega image has issues with faces (and e.g. cats, dogs heads). They are blurred or deformed. According to this article  in April model was learned in 18%

I've just pushed some updates as part of a PR that should accelerate the inference using DALL-E Mega.
To run the playground with DALL-E Mega make sure to pass "mega" as another command line arg, i.e. !python dalle-playground/backend/app.py 8000 mega.


docs: define component states

Define/document available component states.
Checklist

[x] The added / edited code has been documented with JSDoc
[x] All changes are documented in the documentation app (folder apps/docs)
[x] If a new component is added, at least one Playwright screenshot test is added
[x] A changeset is added with npx changeset add if your changes should be released as npm package (because they affect the library usage)

I believe this information might be better suited for our wiki or maybe UX docs. Its geared towards developers and UX.

I believe this information might be better suited for our wiki or maybe UX docs. Its geared towards developers and UX.

It is already placed inside the UX docs :) Jannick already created a UX page for the component states. This PR just fills it with content accordingly.
But I can also move it to the Wiki and delete the UX page for component states

@larsrickert Nice, got it 👍 Then @jannick-ux should do the review please


Show unauthorized signals when connecting to bots with credentials

a regression was introduced that lost this signal. this brings it back.

Coverage decreased (-0.001%) to 57.2% when pulling 856d725879c13ccf0ac4ad96c120d99e61cce174 on cwhitten/show-unauthorized into 7b28956fe942957d012dca79fabbd68e5e37ac73 on master.


5372 add support for adding a batch of users to a group

This closes #5372. @rafatower CR this, please.  This depends on CartoDB/cartodb-postgresql#137

Wrong branch


Publish for scala.js

I'm using fs2-data-xml for library that I'd like to cross publish to scala.js.
It seems that it should be possible given the dependencies.
I may try myself but I don't know much about using mill.
Tests are problematic though as they use files and that would be harder on Scala.js

Hi @cquiroz
This is a good idea. Having experimenting various problems with mill I am thinking about moving back to sbt anyway, I can take the opportunity to add Scala.JS support when possible.
For the test cases, it's kind of usual that they only run on JVM, I've done this kind of things for another project in the past, so this wouldn't be a problem.

It would be great to have at least one js test, it could be done with plain strings instead of files.
The main reason for at least a test is to detect linking errors in case an unsupported call is used.

The tests depending on files need to be JVM specific, but the other ones can be shared. The tests relying on files are the compliance tests for all three supported formats, I guess it doesn't matter since we mainly want to check linking.


Make up/down ingress/egress less ambiguous for paths

Make up/down ingress/egress less ambiguous for paths, fixes #1479

up becomes !consDir (as the current "up" is the opposite of the construction direction)
ingress becomes consIngress
egress becomes consEgress

This change is

Reviewed 1 of 27 files at r1.
Review status: 1 of 27 files reviewed at latest revision, all discussions resolved.

go/lib/spath/info.go, line 48 at r1 (raw file):

	inf := &InfoField{}
	flags := b[0]
	inf.ConsDir = flags&0x1 == 0

My intention with this proposal was to change the concept, not just the name. Meaning, inf.ConsDir = flags&01 != 0.

Comments from Reviewable

Review status: 1 of 27 files reviewed at latest revision, 1 unresolved discussion.

go/lib/spath/info.go, line 48 at r1 (raw file):
Previously, kormat (Stephen Shirley) wrote…
My intention with this proposal was to change the concept, not just the name. Meaning, inf.ConsDir = flags&01 != 0.

(And yes, this is a breaking change)

Comments from Reviewable

Review status: 19 of 28 files reviewed at latest revision, 1 unresolved discussion, some commit checks failed.

python/lib/packet/path.py, line 198 at r3 (raw file):

            # interface, and another from the upstream interface, used for
            # verification only.
            ingress_up = {(True, False): +2, (True, True): +1,

The var needs to be renamed. The up refers to the old Up flag. Same below.

Comments from Reviewable

Review status: all files reviewed at latest revision, 2 unresolved discussions, some commit checks failed.

python/lib/packet/opaque_field.py, line 159 at r2 (raw file):
Previously, worxli (Lukas Bischofberger) wrote…
Integration tests fail, when it is set to True. Unfortunately I couldn't find the exact cause.

Ahh, i see it. False is correct. _parse_flags only sets it to True if CONS_DIR is set, so the default has to be the opposite.

Comments from Reviewable

Review status: all files reviewed at latest revision, 1 unresolved discussion, some commit checks failed.

python/lib/packet/path.py, line 198 at r3 (raw file):
Previously, kormat (Stephen Shirley) wrote…
The var needs to be renamed. The up refers to the old Up flag. Same below.

Done.

Comments from Reviewable

Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


Any chance for a v0.37.58 with 2020c in it?

I was wondering if anyone would be able to make a v0.37.58 that contained 2020b and 2020c? I'm sorry to ask, but I'm stuck on a super old release of Rails and we can't get off of it anytime soon.
If this is a reasonable thing for a new community member to try to take on, I'd be happy to give it a whirl and make a PR? But I completely recognize that often onboarding is harder than just doing the thing :)
Thank you for all your hard work!

At the moment the 0.3 branch is being updated soon after each time zone database release (the 2020c data update is in 15a5b27b5af65de9d37ded58151d9d841623247e).
0.3.x releases are made sporadically when there are significant changes. The Fiji change in 2020c probably qualifies, so you can likely expect a 0.3.58 release soon.
If you don't want to wait for a release, you can use the code from git directly, e.g. with the following in your Gemfile:
gem 'tzinfo', git: 'https://github.com/tzinfo/tzinfo.git', branch: '0.3'

Amazing! Thank you so, so much!


BUG: Send screen crashes when no balance present

Describe the bug
When entering send screen  and no balance is present it crashes on some chains like:
THORChain, Maya, DYDX, Gaia or Kujira.
When implementing a fix, please verify that all chains are free of error.
To Reproduce
Steps to reproduce the behavior:

Enter send screen with no balance present
See error

Expected behavior
Send view opens normally
-version 8

fixed by #514 #506


GraphQL: add a query to fetch specific pending snark work

This PR adds the possibility to fetch a specific range of work in the pending snark work list with GraphQL.

!ci-build-me

!ci-nightly-me

coverage: 61.0% (+0.01%) from 60.989%
when pulling d5882bafd6f3ca84b1b22264e2307ec3ef26c046 on al/snark-work-graphql
into 4f78a48d364f8cf3416d64615686606ba03adb37 on compatible.

!ci-build-me

!ci-build-me

!ci-build-me


Add support for NetworkPolicy

I'd like to use a NetworkPolicy to restrict access from the default namespace into my project's namespace.
I use the following policy to allow the Router to send traffic to a set of pods:
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
  name: openshift-router-nginx
spec:
  ingress:
  - from:
    - namespaceSelector:
        matchLabels:
          name: default
  podSelector:
    matchLabels:
      component: nginx
  policyTypes:
  - Ingress

Unfortunately the exposer pods in the projects namespace to not contain labels I can use to set up a NetworkPolicy. The only option I have is to allow traffic to all pods from the default namespace.
Labels:             app=exposer-6kro17vt8umfvlbh0huarjn5a5q341g2epo70mj4m6nh1oqtlh10

I would suggest to add a new label component=acme (or similar) to allow the definition of a NetworkPolicy like the following.
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
  name: openshift-router-acme
spec:
  ingress:
  - from:
    - namespaceSelector:
        matchLabels:
          name: default
  podSelector:
    matchLabels:
      component: acme
  policyTypes:
  - Ingress

@tnozicka

PR #125 would solve it as well, but unfortunately it has not been merged.

PR #125 would solve it as well, but unfortunately it has not been merged.

Yes, i've created this branch, with this little changes. I don't know why it has not been merged...

/reopen.


Users shows undefined Email of tracked user

On login, I have added the code for identifying the user like below
mixpanel.identify(phone);
Then I have registered some super properties like below
 mixpanel.registerSuperPropertiesOnce({
        email,
        phone,
        firstName,
        lastName
      });

Then I have set the User profile property by following the Setting Profile Property document as below
mixpanel.getPeople().set("Email", email);
In Mixpanel dashboard on Users module its shows undefined value of User profile like below Screenshot

Thanks in advance

hi @JigarAdesara1 , Sorry for the late response. I see you're currently tracking an "email" property but the "Email" column in the table is mapped to the Mixpanel managed "$email" property (with the $ in front). Since you're not tracking "$email" with the $, the "Email" column in the table is returning undefined. You can actually modify your table columns to show the "email" property you currently track(by clicking Edit Columns). Feel free to let me know if you have more questions.


drivers: sensor: add driver and example for DPS310

Add driver and example for Infineon DPS310 temperature and pressure sensor.
This is a rebased version of #20187, since that PR went stale.
Signed-off-by: Christoph Reiter<EMAIL_ADDRESS>

Applied the suggested fixes and rebased on latest master.

@galak Sorry, I seem to have accidentally undone your changes, can you please re-apply them again?

@galak Sorry, I seem to have accidentally undone your changes, can you please re-apply them again?

will do.

Redid my changes.  You might want to think about moving DPS310 temperature oversampling and DPS310 pressure oversampling from Kconfig into dts properties.  Since you support more than one instance of the sensor, I wonder if a user will always want those settings the same for both instances.

Rebased to fix conflicts.

Redid my changes. You might want to think about moving DPS310 temperature oversampling and DPS310 pressure oversampling from Kconfig into dts properties. Since you support more than one instance of the sensor, I wonder if a user will always want those settings the same for both instances.

If this is not a hard requirement, I would leave it as is, because the sensor is an environmental sensor and it there will be very few people actually using more than one instance, let alone with different settings.

@galak Is there anything else I need to do to get this merged?

@galak please revisit

@galak any update?

Hi all, Will this be available for 2.3? It has been a long journey and is almost there.
@creiter32 just curious, what shield do you recommend to test this Sensor?

@nandojve For development I used this one: https://www.infineon.com/cms/en/product/evaluation-boards/s2go-pressure-dps310/

@galak please take another look, I've been asked to consider this for 2.3

Do not merge yet until #25214 has been merged.

We need to update DT_HAS_NODE_STATUS_OKAY to DT_NODE_HAS_STATUS(..., okay)

@creiter32 would you mind applying the changes described above by @galak so we can merge this in time for 2.3?

Here's my diff for the change.:
diff --git a/drivers/sensor/dps310/dps310.c b/drivers/sensor/dps310/dps310.c
index d3a363db26..65c6d3a344 100644
--- a/drivers/sensor/dps310/dps310.c
+++ b/drivers/sensor/dps310/dps310.c
@@ -1,7 +1,5 @@
 /* Driver for Infineon DPS310 temperature and pressure sensor */

-#define DT_DRV_COMPAT infineon_dps310
-
 /*
  * Copyright (c) 2019 Infineon Technologies AG
  *
@@ -725,7 +723,7 @@ static const struct sensor_driver_api dps310_api_funcs = {

 /* support up to 2 instances */

-#if DT_HAS_NODE_STATUS_OKAY(DT_DRV_INST(0))
+#if DT_NODE_HAS_STATUS(DT_DRV_INST(0), okay)
 static struct dps310_data dps310_data_0;
 static const struct dps310_cfg dps310_cfg_0 = {
        .i2c_bus_name = DT_INST_BUS_LABEL(0),
@@ -737,7 +735,7 @@ DEVICE_AND_API_INIT(dps310, DT_INST_LABEL(0), dps310_init,
                    CONFIG_SENSOR_INIT_PRIORITY, &dps310_api_funcs);
 #endif

-#if DT_HAS_NODE_STATUS_OKAY(DT_DRV_INST(1))
+#if DT_NODE_HAS_STATUS(DT_DRV_INST(1), okay)
 static struct dps310_data dps310_data_1;
 static const struct dps310_cfg dps310_cfg_1 = {
        .i2c_bus_name = DT_INST_BUS_LABEL(1),

@galak @carlescufi Applied the requested changes and rebased. Allow edits by maintainers
is also enabled in case other small fixes are needed.

@galak @carlescufi Applied the requested changes and rebased. Allow edits by maintainers
is also enabled in case other small fixes are needed.

Thank you @creiter32. This is merged now.


[FEATURE] Make API mapping page left panel draggable

left panel should be in correct scrollable state when the panel is not showing the full endpoint

based on feedback from Emma, the left panel should be responsive within minimum width

pass


Emojis

where do these emojis fall?
0⃣1⃣2⃣3⃣4⃣5⃣6⃣7⃣8⃣9⃣🔟❎…and others?

Those all are valid.
For reference, there are Digits "1" [31], Digits w/emoji presentation "1" [31 FE0F], and Keycaps "1⃣" [31 FE0F 20E3].   Digits and Keycaps are valid.


How can I use the pretrain results?

https://www.robots.ox.ac.uk/~maxbain/frozen-in-time/models/cc-webvid2m-4f_stformer_b_16_224.pth.tar
This is the Pretrained Weights you listed in the website. But the checkpoint is .tar, and when I unzip it, it is a file, and I do not know how to use it as a normal .pth checkpoints?

It is what I just download, is that right?


Address occasional negative value in rate control calculation

There is still a bug in the algorithm. It seems that if a command/OutRep is received more-or-less at the same time a buffered OutRep is being sent than the received command will be inmediatly sent. The problem seems to occurs for some error in the timestamp calculation / buffer queue order that causes the time comparison between the new command and the last sent OutRep to result in a negative value.

Just so we have this as reference for the future, this edge case issue still has not been solved, but the current state of the fix is good enough to solve the problem most of the time
Originally posted by @Kanuan in https://github.com/ViGEm/DsHidMini/issues/20#issuecomment-817688698

To my observation this hasn't caused any problems in the field whatsoever and I wanna focus on other things, so, closed due to "don't care, next" 😉


Could Create 3 work together with Rasp. Pi 5?

Hi, Dear iRobot team,
I have an issue with the new Raspberry Pi 5, working with Rasp. CAM3 and Create 3. Since I find a connect guidance on Raspberry Pi 4 in Docs. Could Rasp. 5 also connect the adapter board with one USB-C cable, just like the Rasp. 4?
Best Regards

You may be the first user of the Create 3 robot who also has access to a Raspberry Pi 5. I don't know any reason why the new board shouldn't have an Ethernet gadget capability on its USB-C port, but I also don't have any data to know, or a device to test.

I did some light Internet searching and found https://forums.raspberrypi.com/viewtopic.php?p=2147672&hilit=gadget#p2147672 . Looks like you need to do a little extra work to enable the gadget mode in Bookworm. Perhaps that's the problem? If so, this problem should be reproducible on a Pi 4, as well. What version of the Pi OS are you using?

You may be the first user of the Create 3 robot who also has access to a Raspberry Pi 5. I don't know any reason why the new board shouldn't have an Ethernet gadget capability on its USB-C port, but I also don't have any data to know, or a device to test. If you give us some more information about what you've tried to do, we might be able to try to offer suggestions about how to help.

Thanks a lot for your answer.
We are trying to connect Pi 5 to Create 3 and run some object detection algorithms on it.  And send the information back to the server via WiFi.
For the OS, we plan to use Ubuntu Server 22.04, exactly as shown in the Tutorial.

Disclaimer:  I am a Create3 user.  No affiliation with iRobotEd
I have implemented the Pi5 as the compute board for the Create3 successfully.  It is not for the faint of heart, but doable.  Having to run ROS 2 Humble in a Docker container complicates everything, especially having to constantly add something to the docker file, delete the old images to save SDCard space, and then 15-25 minutes to rebuild Docker.
Getting the USB0 setup on Pi5 was not easy, but eventually figured it out, as well as setting up chrony  in PiOS outside docker and the discovery server inside the docker container.  Still not sure I have the super client xml file correct, but all parts (Create3, nodes inside Docker on Pi5, and rviz2 on desktop)  are communicating well.
Still testing the latest firmware H2.6 which allows turning off a lot of the functionality not needed and possibly causing issues trying to run RTABmap and the depthai_ros_driver.  Not encouraging but I’m really on the fringe of my knowledge at this point.
Suggest set up with Pi4 until the Create3 supports Jazzy which will run native over 23.04 on Pi5.

Is there any plan to support Jazzy in the near future?

I would like to revisit this.  Since the Raspberry Pi 5 has been out for sometime, is it supported with the Create 3 and ROS 2 Jazzy?
Are there any power issues by using a Raspberry Pi 5 vs 4?


[0.5/vk] fix handling of AMD viewport negation

Addresses https://github.com/gfx-rs/wgpu-rs/issues/227
We are now taking MAINTENANCE1 whenever it's supported. This code path is supposed to be unaffected. However, if it's not supported, and NDC_Y_FLIP is requested, and we end up using AMD_NEGATIVE_VIEWPORT_HEIGHT, then we don't shift the Y of the viewport.
PR checklist:

[ ] make succeeds (on *nix)
[ ] make reftests succeeds
[ ] tested examples with the following backends:
[ ] rustfmt run on changed code

bors r=wgpu


What does input label mean in code?

`input_points = torch.tensor([[[[580, 350], [650, 350]]]])
input_labels = torch.tensor([[[1, 1]]])
redicted_logits, predicted_iou = model(
sample_image_tensor[None, ...],
input_points,
input_labels,
)
`

I get it, the label represents foreground and background

I have a question to bother you! If i want to do salienct segmentation in a arbitrary image, how should i set this parameter to fit random images?


Fix lint errror in ExecuteButton.js

Travis is currently complaining about this (example build).

With that lint error fixed, it exposes another error further on down the build, which I'll look into now.


RFC: k8s storage

Rendered
This is meant for the next iteration of our Kubernetes runtime work. This has nothing to do with how the Concourse helm chart currently functions.

TODO: Add a section explaining the current storage mechanism and where it falls short

TODO - Document the permissions required to setup the baggageclaim CSI + Storage Class


Add MIT License

I'm adding the same license as in rescript-lang/rescript-sublime. A license is required for github/linguist since we're using this repository for the grammar.

Wouldn't it better to put grammer in a separate repo?


fix: allow clicking the canvas to drop a dragged component [ALT-283]

Changes

In coordination with UI changes that will allow clicking a new component from the UI sidebar to start the component Drag state, these changes will allow clicking inside the component to Drop the component being dragged
Removing unused mouseUp and mouseDown events
Removing unused Mouse Handlers and some related code from the SDK that migrated over to the Visual Editor

Thanks for the additional clean up here!


No registration exists matching provided key

Hi there,
I am trying to get your acme_client code to run. It works with the staging server, but when I try to use the real endpoint I get the error:
Acme::Client::Error::Unauthorized
---------------------------------
No registration exists matching provided key

My code is pretty much the same as yours, this are my attributes:
default['letsencrypt']['contact'] =<EMAIL_ADDRESS>default['letsencrypt']['endpoint'] = 'https://acme-v01.api.letsencrypt.org'
I am running Ubuntu 14.04. Do you have any idea why this could happen?
Thanks!

Sounds like you registered on the staging server, and are now using your staging key to authenticate to the real endpoint. Try to clear your node['letsencrypt']['private_key'] and try again.

Thanks, that was it. I deleted it with knife exec -E 'nodes.transform(:all) { |n| n.normal_attrs.delete("letsencrypt"); n.save() }'. Do you think that is a good way to solve this or is there a better way if I run into this problem again in the future?

Sure, looks fine, as long as it clears the attribute. I would probably have used knife node edit instead but this looks like it could also work :)

Alright, good to know. Thanks and good evening.


flake.nix: init

This is based almost entirely off the version in nixpkgs.
Enables:

nix run github:ast-grep/ast-grep
nix develop in the repository to get cargo/rust etc even if you don't have those in the environment.
Use of this flake in other flakes to get the most recent version of the code, even if it hasn't been packaged in nixpkgs.

Summary by CodeRabbit

New Features

Introduced package management capabilities and support for building the ast-grep Rust package using Nix.

Chores

Updated .gitignore to exclude specific temporary files related to Nix operations.

cc @cafkafk who did the last update to nixpkgs (https://github.com/NixOS/nixpkgs/pull/257385)

HI @philiptaron would you like to add more context for me? I'm not a Nix user personally but I'm open to support Nix package for ast-grep. That said, should the nix package information maintained in the nix repo? I believe other package managers (say brew, aur, suse) also have standalone repos.

@HerringtonDarkholme:

Would you like to add more context for me? I'm not a Nix user personally but I'm open to support Nix package for ast-grep.

I'd love to do so. Nix is famously confusing. Here's a diagram some joker made about how there are three things named "Nix" and how they're related and not related.

This PR adds a Nix flake to this repository. Flakes are a way of declaratively  sharing build procedures, development shell, applications and their variants, and metadata about the code. It allows both to consume the work of others (those are the inputs) and to be consumed by others (say, by a NixOS configuration like my flock.nix.)
Other than consuming nixpkgs as an input (in order to gain access to the Rust toolchain) this PR has nothing to do with nixpkgs.
To test out this PR for yourself, install Nix, then run

nix build github:philiptaron/ast-grep/flake.nix to build the project
nix run github:philiptaron/ast-grep/flake.nix to run the sg tool as built by Nix.
git clone https://github.com/philiptaron/ast-grep -b flake.nix, then run nix develop in that repository's root to access the Nix versions of cargo, rustc, etc.

That said, should the nix package information maintained in the nix repo? I believe other package managers (say brew, aur, suse) also have standalone repos.

I'm looking for these benefits that having Nix flake integration in this repository provides:

Declarative, reproducible development environments. No more "works on my machine." Nix flakes create environments that work seamlessly and are easily sharable across platforms.
Declarative, reproducible package builds. nix run and nix build in the repository and I know that the code builds and passes its unit tests.

As it happens, https://github.com/NixOS/nixpkgs/pull/231553 is where @montchr added ast-grep to nixpkgs; the most recent update to the package happened today when @r-ryantm (a bot) updated the version from 0.20.0 -> 0.20.2
That works really well for consuming the tool; it works less well for doing development on it. And I'd like to contribute a bit. 🙂

I really liked this talk from @grahamc at PackagingCon last year about flakes.

Thank you for your contribution! We appreciate your interest in improving the project. However, merging flake in nixpkg seems to be more appropriate:

Our team currently utilizes cargo and rustup for managing Rust projects, which aligns with our existing workflow and tooling preferences. As such, we recommend sticking with these tools for consistency and ease of use among all team members.
Regarding the inclusion of a flake in the nixpkgs repository, it’s a valid approach for Nix users. However, since our project does not use Nix, we believe it would be more appropriate for such configurations to be maintained separately within the Nix community’s repositories.

We’re open to future suggestions and contributions that align with our project’s tooling and practices. Thanks again for your understanding and support!

I'm sorry to hear that perspective. I believe that having a flake in this repository would enable contributors to agree on which version of cargo specifically they use, on which version of rustc specifically they use, and no longer have to remember when they last ran rustup... without disallowing or impeding the existing workflow. It's a net positive!
Flakes are about the code in this repository, not nixpkgs; as I tried to mention, the code that's in nixpkgs is about the released version of this tool, not the in-development version of this tool.
I respect your right as maintainer and author to control or direct which workflows you'd like to use in this repository, though I would ask that you try out this workflow and see it for yourself. 🙇🏻♂

Thanks for the contribution. But I prefer to minimize project dependency.

agree on which version of cargo specifically they use

This is already done by the rusttoolchain file. https://github.com/ast-grep/ast-grep/blob/main/rust-toolchain


Add real and fake listings for companies.

Add one Topic "Companies"
Add one real listing and one fake listing each for Starbucks, Netflix, Burlington, Pinterest, and BP.
Each company listing refers to the same topic "Companies"

This is an update to #20

Closed for fixup.


make define_reference optional (as documented)

(it used to raise an AttributeError if you didn't call define_reference)

Thanks for catching this @hroskes !


Zipkin

Codecov Report

Merging #14 (a532b72) into master (652b49a) will increase coverage by 0.00%.
The diff coverage is 95.93%.

@@           Coverage Diff            @@
##           master      #14    +/-   ##
========================================
  Coverage   94.21%   94.22%
========================================
  Files         182      185     +3
  Lines        7853     7961   +108
========================================
+ Hits         7399     7501   +102
- Misses        454      460     +6

Impacted Files
Coverage Δ

...nclude/opentelemetry/ext/http/client/http_client.h
90.90% <ø> (ø)

...include/opentelemetry/ext/http/common/url_parser.h
91.30% <91.30%> (ø)

...ntelemetry/ext/http/client/curl/http_client_curl.h
94.89% <95.23%> (-0.11%)
:arrow_down:

...lemetry/ext/http/client/curl/http_operation_curl.h
82.89% <100.00%> (+0.46%)
:arrow_up:

...pentelemetry/ext/http/client/http_client_factory.h
100.00% <100.00%> (ø)

ext/test/http/curl_http_test.cc
94.41% <100.00%> (+0.86%)
:arrow_up:

ext/test/http/url_parser_test.cc
100.00% <100.00%> (ø)

sdk/test/common/circular_buffer_test.cc
98.97% <0.00%> (-1.03%)
:arrow_down:

... and 1 more


loadview only restores visible folds

Neovim version (nvim -v | head -n1)
NVIM v0.7.2
Operating system/version
ArchLinux latest
How to reproduce the issue
cat mini.lua
local create_autocmd = vim.api.nvim_create_autocmd
local create_augroup = vim.api.nvim_create_augroup

vim.o.packpath = "~/.local/share/nvim/site"
vim.cmd("packadd promise-async")
vim.cmd("packadd nvim-ufo")

-- Setting
vim.o.foldcolumn = "1"
vim.o.foldlevel = 99
vim.o.foldlevelstart = -1
vim.o.foldenable = true

local ufo = require("ufo")
ufo.setup()
vim.keymap.set("n", "zR", ufo.openAllFolds)
vim.keymap.set("n", "zM", ufo.closeAllFolds)

local saveAndLoadViews = create_augroup("saveAndLoadViews", { clear = true })
create_autocmd("BufLeave", {
	pattern = "*.*",
	command = "mkview",
	group = saveAndLoadViews,
	desc = "Save view on leaving buffer",
})
create_autocmd("BufEnter", {
	pattern = "*.*",
	command = "silent! loadview",
	group = saveAndLoadViews,
	desc = "Load view on entering buffer",
})

nvim --clean -u mini.lua some-file.ext

open a file which contains a number of fold
close some folds
move the cursor so that some closed folds are off screen/invisible
close neovim
open file again
scroll to look at the (previously) closed folds off screen
...

(NOTE: the bug does not seem to happen when opening a file with :e from within neovim)
Expected behavior
I use some autocmds to save and restore views and in particular folds (see above mini.lua). I would like all folds to be restored when opening a file again.
Actual behavior
Only visible folds (that aren't off screen) are restored. All folds that are above or below what's currently visible on screen are fully opened.
Thanks for the great plugin! This has been something I've been missing for a while. I'm especially happy that it also gets rid of some annoying bugs in neovim's treesitter fold handling!

Reproduced. It's a tech limitation for ufo. ufo is based on extmarks to update the folds.
Unfortunately, mkview/loadview can't save/load any extmarks to/from script.
Must write pre/post script as a workaround.

Works perfectly, thanks for the super quick fix @kevinhwang91!

Hey @kevinhwang91, I'm still encountering this problem when trying to open files with Telescope's find_files.
Here's my minimal config to reproduce. I've added Telescope and some settings to get loadview to work with it. Note that there is a longstanding issue in Telescope where folds only work with fixes. In that issue there is a different method of getting it to work (with autocmd), and I've tried that as well with the same result.
local create_autocmd = vim.api.nvim_create_autocmd
local create_augroup = vim.api.nvim_create_augroup

vim.o.packpath = "~/.local/share/nvim/site"
vim.cmd("packadd promise-async")
vim.cmd("packadd nvim-ufo")
vim.cmd("packadd telescope.nvim")

-- Setting
vim.o.foldcolumn = "1"
vim.o.foldlevel = 99
vim.o.foldlevelstart = -1
vim.o.foldenable = true

local ufo = require("ufo")
ufo.setup()
vim.keymap.set("n", "zR", ufo.openAllFolds)
vim.keymap.set("n", "zM", ufo.closeAllFolds)

local saveAndLoadViews = create_augroup("saveAndLoadViews", { clear = true })
create_autocmd("BufLeave", {
	pattern = "*.*",
	command = "mkview",
	group = saveAndLoadViews,
	desc = "Save view on leaving buffer",
})
create_autocmd("BufEnter", {
	pattern = "*.*",
	command = "silent! loadview",
	group = saveAndLoadViews,
	desc = "Load view on entering buffer",
})

-- fix to get folds to work with telescope (see https://github.com/nvim-telescope/telescope.nvim/issues/559)
local action_set = require("telescope.actions.set")
local builtin = require("telescope.builtin")
local open_files_opts = {
	hidden = true,
	attach_mappings = function(_)
		action_set.select:enhance({
			post = function()
				vim.cmd([[:normal! zx]])
				vim.cmd([[:silent! loadview]])
			end,
		})
		return true
	end,
}
builtin.my_find_files = function(opts)
	opts = opts or {}
	return builtin.find_files(vim.tbl_extend("error", open_files_opts, opts))
end

The steps to reproduce are exactly the same as above, except now instead of point 5, the file is opened with Telescope find_files.
Let me know if you think this is a different issue, and I will open a new one.

				vim.cmd([[:normal! zx]])

Let me clarify maybe. When I use telescope, then with the above fix, folds are restored and everything works as expected. However, when I combine telescope with nvim-ufo, then only the folds that are visible are restored, which is the same problem as originally discussed in this issue. I thought maybe that's because ufo's conversion of the folds from the view file into extmarks (which is what your fix does if I understand it correctly) doesn't get triggered. Is there maybe some function I can call in action_set.select:enhance instead of loadview that triggers ufo fetching the folds correctly?
Just like with the telescope issue, reloading the file with :e fixes the folds. I guess I can use that for now, although it's very clunky. I totally agree that at the root this is telescope's issue; I guess I'm hoping for a workaround to get the workaround to work :sweat: :rofl: I don't have much hope on this getting properly fixed in telescope any time soon... But yeah, I do understand if you don't want spend any time on this!
In any case, thanks for the great plugin! :)

UFO_LOG=trace nvim
Log affter enter file:

You should add loadview between two BufEnter
 require('ufo.lib.log').trace('debug yourself')

If I have time I will do some research.

@kevinhwang91: I asked in the telescope issue thread, and someone posted a working workaround. :)

Should work now without any hack. please handle your comment in telescope issue thread.

Wow, thanks a lot for working on this when it wasn't even ufo's bug to begin with!


Set commit worker threads as daemons

Currently, CTRL-C does not exit the commit threads (unless with explicit termination signals). Explicitly set the commit threads as daemons to exit these as well when the main thread terminates.

The threads don't necessarily need to be made daemons.
You can just register an "atexit" function that shuts down the threads.
At this point, I think we need an "initialize_pdo" function in the client that we always call to init the modules. That function could start the replication threads and then register the atexit() function to shutdown the threads cleanly.

agreed, i dint know about atexit() until now. A cleaner solution than converting threads to daemons (i prefer non-daemon threads to enable completion of background tasks & a clean exit function rather than abruptly killing threads, especially when there is no error, and the main threads just wants to exit)

Done.


does't work on OS X 10.11.4 beta6 (15E61b)

there's no optional item for select in screen saver options

Hi @lorichueng could you give us more information on the problem you are seeing?

Just cannot work. I am 10.11.4 beta6 , too.

@leochenfc What do you mean cannot work? Do you get an error that says "You cannot use the Aerial screen saver with this version of OS X. Please contact the vendor to get a newer version of the screen saver."?
If so it's a bug in OS X. But it only affects the preview in System Preferences. The screensaver will actually work okay when it launches itself. If you see this error in System Preferences, select Aerial, close System Preferences and then reopen it. The preview will then work too.
You can read more here.
http://alistairmcmillan.github.io/2016/04/25/OSX-Swift-screensaver-bug.html

I redownload the stable version and reinstall. It works fine! Thanks.

If it was just that error then you should really use the latest beta. The error isn't caused by a bug in the screensaver. It's a bug in OS X. And the latest beta of the screensaver offers a number of fixes and features.

sorry for long time with no reply.
maybe it's just the bug on OSX . Now , I upgrade it to 10.11.6 Beta , Aerial works fine

Glad to hear it's working for both of you. Closing.


can't find cmd/gateway

When I follow the README instruction, and running make build-go, it raised:
go build -o bin/gateway cmd/gateway/*.go
malformed import path "cmd/gateway/*.go": invalid char '*'
make: *** [build-go] Error 1

Then I found that the cmd is not contained in the repo, so is there something wrong?

Thank you for flagging up this issue. The README (and make target) is out of date. This is a relic of much earlier in the development of Fabric Gateway when a stand-alone process was used to prototype the server-side Gateway gRPC service. Now this service is embedded directly in the v2.4 Fabric peer. The README and Makefile both need some clean-up so we can use this issue to drive that.
The README provides information for setting up a development environment in order to contribute to the Fabric Gateway client API codebase. For usage of the API in client application, refer to the user documentation:
https://hyperledger.github.io/fabric-gateway/
In particular, the samples provide examples and instructions for developing and running a client application using the Fabric Gateway API.


Update New-CsAutoAttendantMenuOption.md

Fixed Typo in Example 2: ApplicationEndpoint instead of AApplicationEndpoint

Docs Build status updates of commit 54d6460:
:clock10: Full build: the average full build time is 17 min(s) 31 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit 54d6460:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/New-CsAutoAttendantMenuOption.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

@Kateyanne Please merge this PR. Thanks.

Docs Build status updates of commit 1756009:
:clock10: Full build: the average full build time is 17 min(s) 31 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit 1756009:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/New-CsAutoAttendantMenuOption.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Implement stateful Zino reachability monitor

It seems the best way to approach building the state engine of Zino is to implement a minimal port of the reachability monitor, so there is actually some state to update.

#49 continues this


check correct extensionsUsed for serialization

Check the size of the correct extensionsUsed variable before serialization.

@Selmar Super awesome! Thanks!


loadjson: complex value was replaced by  its conjugate

example
>> dat=loadjson('{"array":[1,2,3-4i]}')
dat =
  array: [1.0000 + 0.0000i 2.0000 + 0.0000i 3.0000 + 4.0000i]

maybe caused by this code
loadjson.m, row 410
if(~iscell(object) && size(object,1)>1 && ndims(object)==2)
   object=object';
end

should be
object=object.';

interesting finding .. thanks, it is now fixed.
I want to mention that {"array":[1,2,3-4i]} is not a valid JSON string because JSON does not support complex numbers, but using the default FastArrayParser, this is acceptable to loadjson and can be parsed. Disabling it will give an error
loadjson('{"array":[1,2,3-4i]}','fastarrayparser',0)

A more unambiguous (and JSON compatible) way to handle complex number is to use the built-in JData annotation:
array=[1,2,3-4i];
savejson(array)
loadjson(savejson(array))


Typo

I don't think this is by IBM though...
http://www.ibm.com/developerworks/library/wa-watson-explorer-react-app/

Yes, it's: http://www.ibm.com/developerworks/library/wa-watson-explorer-react-app/index.html.

@mbrookes Thanks!

That's the same page I linked to, which is in a a community library. The developer is:
Sing Li
Consultant
Makawave

That's the same page I linked to

Indeed, sorry. Well, I must admit, I hadn't read the post yet.

Shame though! :disappointed:

Could this be him https://www.linkedin.com/in/singli :grin:

This guy is a project manager at IBM :see_no_evil:.

You know what, let's ask him @Sing-Li

Thanks for the alert!    :smile:
I'm with the open source GitHub project over at Rocket.Chat now.    It is an MIT licensed on-premise/cloud hosted web chat (collaboration) platform with features such as video chat and Livechat popup integration.  We have thousands of installations in 22 countries and counting :smile:
Please update info with a hyperlink if possible ...
Sing Li
Rocket.Chat
Visit us + chat with the core dev team at the clustered, 24 x 7, five nine, demo + support + dog-fooding sever at:
https://demo.rocket.chat/


Refactor population_ prefixed columns in Partner model

It would probably be worth considering a refactor at this point -- there are a TON of population_ prefixed columns and I suspect there will be more after these demographic categories are added.
Could these be condensed into a population_demographic (or similar) JSON column? Could probably do the same with the other N+1 column headers as well.

Originally posted by @armahillo in https://github.com/rubyforgood/human-essentials/issues/2550#issuecomment-940422095
Two approaches come to mind for this:

Extract this to a separate resource
Combine these into a single JSON field

I have not dove deep into how this data behaves (very fluent in Diaper side, less so on Partner side), but the cursory look I've had suggests to me that it's just a simple scalar with a multitude of related variants. Something like:
population: :json that stored a collection like:
{
   "united-states": 1234,
   "canada": 2345,
   "mexico": 3456,
}

would probably work.  PostgreSQL lets us query on JSON values natively, so we shouldn't take a performance hit if the app needs to query on those fields specifically (instead of only reporting them)
Nesting data, like:
{
   "united-states": {
      "region-1": 123,
      "northeast": 234,
      "south": 345,
      "some-other-region": 223,
   },
   "canada": {
     "quebec": 111,
     "ontario": {
         "toronto": 22222,
         "other": 111
     },
   }

would be possible though that feels a bit wibbly and loose with the strucure of the data, particularly regarding a key naming scheme.  I think doing a 1:1 migration of column names to keys would probably be sufficient and could be done with a lateral shift in behavior.
Alternately, were it to be done as an associative resource if we needed specific behaviors around it too -- this might be the way to go if there are a BUNCH of different demographic fields that need extraction like this, then they could fall under the same larger resource and subtype them via STI.

From:  https://www2.census.gov/programs-surveys/decennial/2020/technical-documentation/questionnaires-and-instructions/questionnaires/2020-informational-questionnaire-english_DI-Q1.pd
If I'm reading this correctly,  the 2020 census added several more-specific race categories that (I presume) would have been under the Asian or Pacific Islander umbrellas before.

f

From the partnerbase working group meeting 2022/07/13,

noting that the gov't is often a bit behind on preferred terminology
recommended:

Black/African-American
White/Caucasian
Hispanic/Latin
Native American/Alaskan Native

Closing due to lack of activity