ErrorEvent

Steps to reproduce
import { Pool, neonConfig } from '@neondatabase/serverless';

...
const pool = new Pool({ connectionString: 'postgresql://postgres:password@localhost:54320/postgres' });
const result = await pool.query('SELECT id, name FROM sauna_location LIMIT 1');

Expected result
Returns rows from the database
Actual result
Throws ErrorEvent
Environment
Running in locally in MacOS, M2
ghcr.io/neondatabase/wsproxy:latest in Docker
"@neondatabase/serverless": "^0.10.4",
next.js 14.2.19
Vercel Edge runtime, servlerless function
Logs, links
ErrorEvent {
  [Symbol(type)]: 'error',
  [Symbol(kTarget)]: WebSocket {
  [Symbol(kEvents)]: SafeMap(4) {
  'error' => <ref *1> {
  size: 1,
  next: Listener {
  next: undefined,
  previous: [Circular *1],
  listener: [Function],
  flags: 0,
  callback: [Function]
},
  resistStopPropagation: false
},
  'message' => <ref *2> {
  size: 1,
  next: Listener {
  next: undefined,
  previous: [Circular *2],
  listener: [Function],
  flags: 0,
  callback: [Function]
},
  resistStopPropagation: false
},
  'close' => <ref *3> {
  size: 1,
  next: Listener {
  next: undefined,
  previous: [Circular *3],
  listener: [Function],
  flags: 0,
  callback: [Function]
},
  resistStopPropagation: false
},
  'open' => <ref *4> {
  size: 1,
  next: Listener {
  next: undefined,
  previous: [Circular *4],
  listener: [Function: handleWebSocketOpen],
  flags: 0,
  callback: [Function: handleWebSocketOpen]
},
  resistStopPropagation: false
}
},
  [Symbol(events.maxEventTargetListeners)]: 10,
  [Symbol(events.maxEventTargetListenersWarned)]: false,
  [Symbol(kHandlers)]: SafeMap(0) {},
  [Symbol(url)]: URL {  },
  [Symbol(controller)]: Fetch {
  _events: [Object: null prototype] {},
  _eventsCount: 0,
  _maxListeners: 21,
  dispatcher: Agent {
  _events: [Object: null prototype] {},
  _eventsCount: 0,
  _maxListeners: undefined,
  [Symbol(shapeMode)]: false,
  [Symbol(kCapture)]: false,
  [Symbol(destroyed)]: false,
  [Symbol(onDestroyed)]: null,
  [Symbol(closed)]: false,
  [Symbol(onClosed)]: [],
  [Symbol(dispatch interceptors)]: [ [Function] ],
  [Symbol(options)]: { connect: undefined, interceptors: undefined },
  [Symbol(maxRedirections)]: 0,
  [Symbol(factory)]: [Function: defaultFactory],
  [Symbol(clients)]: Map(1) { 'https://localhost' => WeakRef {  } },
  [Symbol(finalizer)]: { register: [Function: register] },
  [Symbol(onDrain)]: [Function],
  [Symbol(onConnect)]: [Function],
  [Symbol(onDisconnect)]: [Function],
  [Symbol(onConnectionError)]: [Function],
  [Symbol(Intercepted Dispatch)]: [Function: Intercept]
},
  connection: { abort: null, destroyed: true, destroy: [Function: destroy] },
  dump: false,
  state: 'terminated',
  [Symbol(shapeMode)]: false,
  [Symbol(kCapture)]: false
},
  [Symbol(ready state)]: 0,
  [Symbol(binary type)]: 'arraybuffer'
},
  [Symbol(kIsBeingDispatched)]: false
}

I would like to use Neon with HTTP only. But cannot find any option to disable websockets. Also, would like to use it without a pool with multiple queries, but again only the one shot query function.

Thanks. Is this issue superseded by #127?
WebSockets shouldn't need to be disabled: simply don't use the Pool or Client objects and WebSockets will not be used.
IIUC the wsproxy Docker image can forward WebSocket traffic but does not offer an http API, so http queries (via import { neon }) are not available in a local development environment.


Code reformat.  No functional changes.  Typically items such as:

Code reformat.  No functional changes. Typically items such as:

blank lines added to JavaDoc (between description and parameters)
multiple-blank lines in classes reduced from >2 blank lines to =2 blank lines
blank lines within JavaDoc descriptions replaced with <p>
superfluous blank lines removed from JavaDoc
static fields defined before non-static fields
blank lines removed from between field definitions (in the absence of JavaDoc at field level)
} else { on same line
} catch { on same line
class... no spurious newline before {
method()... no spurious newline before {

Style is subjective; there is no right-and-wrong, and these settings are configurable.  For now just having a deterministic style applied makes it much easier to address other refactorings.

PR build is green.

: - )


Rewrite logic in vlen to drop NumPy build dependency

As noted in issue ( https://github.com/zarr-developers/numcodecs ), vlen had problems with read-only data
Internally this occurred because we assigned the input array to object[:], which expects mutability. Ideally we would just replace this with const object[:]. However Cython does not support this ( https://github.com/cython/cython/issues/2485 ). Over time various blockers have been resolved on that front, but it is not yet fixed
Fortunately an astute SciPy developer noted that const <fused_type>[:] is allowed ( https://github.com/scipy/scipy/pull/18192#pullrequestreview-1359581611 ). We use that same trick here
This in turn should allow us to continue to accept read-only arrays. Though this does so without a NumPy build dependency, which can introduce more complexity to the build process

TODO:

[ ] Unit tests and/or doctests in docstrings
[ ] Tests pass locally
[ ] Docstrings and API docs for any new/modified user-facing classes and functions
[ ] Changes documented in docs/release.rst
[ ] Docs build locally
[ ] GitHub Actions CI passes
[ ] Test coverage to 100% (Codecov passes)

As per comments on https://github.com/conda-forge/numcodecs-feedstock/pull/108, I don't think we need this any more


[DDW-914] DDW-914 Implement 'Unmoderated stake pool data warning' notification

This PR implements the 'Unmoderated stake pool data warning' notification
Motivation
As a user, I would like to see a notification about "Unmoderated stake pool data" which I have to accept first in order to see any real data on the screen.
Description
Stake pool data is unmoderated and thus it might contain some offensive content. So, as a way to handle this, we need to have a special notification where users are informed of this and they need to accept to see the unmoderated data before we show it to them.
Once the user accepts this we won't show the notification in the next 24 hours.

QA thread

@daniloprates on the PR description the button is pink

and on Storybook it has blue color, this is fine?

@daniloprates on the PR description the button is pink
and on Storybook it has blue color, this is fine?

Yes. It's loading the wrong SASS variables, not related to this PR. But thanks for noticing, I'll fix it anyway.

Good job 👍
Please merge latest develop.

@yakovkaravelov latest develop merged. Could you approve it again?


Add ability to take license key from package.json

This is my initial idea to solve #23
How do you feel about this @runk?

Also, it'd be great to add a line to README explaining this alternative option for providing the licence key

Can you please rebase your branch with master? There were some issues with the env var

Merging this one into my branch so I can finish this work off

:tada: This PR is included in version 3.1.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

Sorry @runk - i didn't see your messages yesterday but that's brilliant, thanks so much, this really helps me a out a lot!


Wise Data Recovery v6.1.3

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

[x] Does your manifest conform to the 1.2 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

You don't need to change the ManifestVersion to 1.1.0 anymore; it can be left at 1.2.0

@russellbanks thanks.


Unexpected response when targeting localhost

use ekko::Ekko;

fn main() {
    let mut e = Ekko::with_target([127, 0, 0, 1]).unwrap();
    println!("{:?}", e.send(1).unwrap());
}

Unexpected((EkkoData { timepoint: Instant { tv_sec: 101850, tv_nsec: 776870355 }, elapsed: 62.953µs, address: Some(<IP_ADDRESS>), identifier: 56444, sequence: 0, hops: 1 }, (8, 0)))

Looks like it is receiving its own request packet. Perhaps those could be filtered?

Thank you! There will be a version bump over the weekend with a fix.

Solved in new version, closing issue.


Support For Extended TLS Settings

Describe the feature request
We are looking into configuring additional TLS settings in ingress and egress (currently we use basically the defaults).
As per the analysis, it would have been nice if Istio allows configuring more attributes beyond the cipher suite list.
For eg., we must be able to configure elliptic curves (ECDH parameters).  Fortunately, Envoy has support for this, but in Istio it is not exposed yet(so there is a way to do this currently with EnvoyFilter). We will also need to configure the signature schemes (e.g.  rsa_pkcs1_sha256, rsa_pss_rsae_sha256, ecdsa_secp256r1_sha256, ecdsa_secp384r1_sha384). Unfortunately, signature scheme is not configurable in Envoy either, and will initiate a separate request for the same in Envoy.
There have been different efforts/discussions in Istio in similar lines. Please see below:

Initial discussion of adding TLS params to mesh-config
add cipher suite to DR - API changes
add ecdh curves defaults PR

So, the requirements:

Support ‘ecdh_curves’ at the Gateway: https://istio.io/latest/docs/reference/config/networking/gateway/#ServerTLSSettings
Support ‘ecdh_curves’ in DestinationRule: https://istio.io/latest/docs/reference/config/networking/destination-rule/#ClientTLSSettings.
ClientTLSSettings currenlty miss the ability to configure TLS versions, and cipher suites (needs EnvoyFilters). It would be a good opportunity to add them too. (This PR seems to be addressing cipher suites part.)
Should we also support it for the Sidecar (Ingress Listener) ?https://istio.io/latest/docs/reference/config/networking/sidecar/#IstioIngressListener ==> This is just for completeness, and currently cannot find a requirement for this.

Describe alternatives you've considered
As Envoy supports some of these params already, we can configure the same using EnvoyFilters. However, it would be nice to have these supported using Istio standard APIs
apiVersion: networking.istio.io/v1alpha3
kind: EnvoyFilter
metadata:
name: gateway-tls-curves
namespace: istio-system
spec:
workloadSelector:
labels:
istio: ingressgateway
configPatches:

applyTo: FILTER_CHAIN
match:
context: GATEWAY
listener:
name: "<IP_ADDRESS>_8443"
patch:
operation: MERGE
value:
transport_socket:
name: envoy.transport_sockets.tls
typed_config:
"@type": type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.DownstreamTlsContext
common_tls_context:
tls_params:
ecdh_curves:
- P-256
- X25519

Affected product area (please put an X in all that apply)
[ ] Ambient
[ ] Docs
[ ] Installation
[X] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[X] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

cc @howardjohn @ramaraochavali

This requirement makes me think about should we introduce extensions API in istio, these APIs can iterate quickly and we do not need to guarantee their compatibility.   Like ratelimit, it is long there, but without much progress

How is extension API different from Envoy filters?

one case for RateLimit is apply to a specify route, simply refer to an VS will not be right.
it's avaliable for kubernetes Gateway API, as HTTPRoute is first class.

How is extension API different from Envoy filters?
It is user faced API, then we can translate it to xds, but not guarantee it could not change in the future, just like k8s deployment once resides in extensions API group, now they are migrated to apps group.

As per offline discussion with @howardjohn the API PR(https://github.com/istio/api/pull/2014) can be rebased and taken forward.

Just an update that finally the proposal that was accepted and the implementation that got merged - is to have a global MeshConfig for ecdh curves settings for all non ISTIO_MUTUAL tls traffic.

@kfaseela we are running with istio version 1.13.2. i tried envoyfilter with ecdh curves which did not work for me. Is there any limitations in envoyfilter as well?

@kfaseela we are running with istio version 1.13.2. i tried envoyfilter with ecdh curves which did not work for me. Is there any limitations in envoyfilter as well?

We have not faced any problems using the EnvoyFilter. Istio support for ecdhCurves in MeshConfig is already merged, just in case you want to try

Yes. We do have a plan to upgrade soon .  Timeebeing would like unblock the issue, Do you see any issue in Envoyfilter ?
apiVersion: networking.istio.io/v1alpha3
kind: EnvoyFilter
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"networking.istio.io/v1alpha3","kind":"EnvoyFilter","metadata":{"annotations":{},"name":"gateway-tls-curves","namespace":"istio-system"},"spec":{"configPatches":[{"applyTo":"FILTER_CHAIN","match":{"context":"GATEWAY","listener":{"name":"<IP_ADDRESS>_8443"}},"patch":{"operation":"MERGE","value":{"transport_socket":{"name":"envoy.transport_sockets.tls","typed_config":{"@type":"type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.DownstreamTlsContext","common_tls_context":{"tls_params":{"ecdh_curves":["P-256","X25519","secp384r1","secp256r1"]}}}}}}}],"workloadSelector":{"labels":{"istio":"ingressgateway"}}}}
  creationTimestamp: "2023-04-21T11:18:29Z"
  generation: 3
  name: gateway-tls-curves
  namespace: istio-system
  resourceVersion: "475778794"
  uid: 1c0c0e24-9326-431c-b6f7-a267de249d37
spec:
  configPatches:
  - applyTo: FILTER_CHAIN
    match:
      context: GATEWAY
      listener:
        name: <IP_ADDRESS>_8443
    patch:
      operation: MERGE
      value:
        transport_socket:
          name: envoy.transport_sockets.tls
          typed_config:
            '@type': type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.DownstreamTlsContext
            common_tls_context:
              tls_params:
                ecdh_curves:
                - P-256
                - X25519
                - secp384r1
                - secp256r1
  workloadSelector:
    labels:
      istio: ingressgateway

At a high level, the filter looks good. Make sure the label used in workloadselector matches with the gateway label.(might be different based on the Istio installation method)

P-256 and X25519 works, Rest all fails in handshake
/usr/bin/curl -vvv  --curves secp384r1  https://xxxx.xom
*   Trying <IP_ADDRESS>:443...
* Connected to xxxxx.com (<IP_ADDRESS>) port 443 (#0)
* ALPN: offers h2
* ALPN: offers http/1.1
*  CAfile: /etc/ssl/cert.pem
*  CApath: none
* (304) (OUT), TLS handshake, Client hello (1):
* error:1404B410:SSL routines:ST_CONNECT:sslv3 alert handshake failure
* Closing connection 0
curl: (35) error:1404B410:SSL routines:ST_CONNECT:sslv3 alert handshake failure
(base) kubernetes ananayak(k8s: qaus1-ai-eks) $

P-256 and X25519 works, Rest all fails in handshake
/usr/bin/curl -vvv  --curves secp384r1  https://xxxx.xom
*   Trying <IP_ADDRESS>:443...
* Connected to xxxxx.com (<IP_ADDRESS>) port 443 (#0)
* ALPN: offers h2
* ALPN: offers http/1.1
*  CAfile: /etc/ssl/cert.pem
*  CApath: none
* (304) (OUT), TLS handshake, Client hello (1):
* error:1404B410:SSL routines:ST_CONNECT:sslv3 alert handshake failure
* Closing connection 0
curl: (35) error:1404B410:SSL routines:ST_CONNECT:sslv3 alert handshake failure
(base) kubernetes ananayak(k8s: qaus1-ai-eks) $

Those are the default curves on envoy, did u check if the filter is really applied? What are the labels present on your gateway?

Yes. I see this error in ingress pods when i enable the debug , Does istio 1.13.2 envoy version supports ecdh configuration ?
{"level":"warning","time":"2023-04-21T11:45:36.557704Z","scope":"envoy config","msg":"gRPC config for type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.Secret rejected: Failed to initialize ECDH curves P-256:X25519:secp384r1:secp256r1"}

Yes. I see this error in ingress pods when i enable the debug , Anything extra configuration required in  istio 1.13.2 to support ecdh configuration ?
{"level":"warning","time":"2023-04-21T11:45:36.557704Z","scope":"envoy config","msg":"gRPC config for type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.Secret rejected: Failed to initialize ECDH curves P-256:X25519:secp384r1:secp256r1"}

I have not used the config with 1.13 before. Tried only with 1.16 I guess

We do use extra ciphersuits at the gateway would that be causing any issue here ?
  - hosts:
    - '*'
    port:
      name: https-default
      number: 443
      protocol: HTTPS
    tls:
      cipherSuites:
      - ECDHE-ECDSA-AES256-GCM-SHA384
      - ECDHE-RSA-AES256-GCM-SHA384
      - ECDHE-ECDSA-CHACHA20-POLY1305
      - ECDHE-RSA-CHACHA20-POLY1305
      - ECDHE-ECDSA-AES128-GCM-SHA256
      - ECDHE-RSA-AES128-GCM-SHA256
      credentialName: star-ciscoccservice-com-certs
      minProtocolVersion: TLSV1_2
      mode: SIMPLE

Yes. I see this error in ingress pods when i enable the debug , Anything extra configuration required in  istio 1.13.2 to support ecdh configuration ?
{"level":"warning","time":"2023-04-21T11:45:36.557704Z","scope":"envoy config","msg":"gRPC config for type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.Secret rejected: Failed to initialize ECDH curves P-256:X25519:secp384r1:secp256r1"}

Right now not with my laptop, but I think the name recognized by envoy is P-384 instead of secp384r1. I would have to check in detail tomorrow.

I just see the set of supported ECDH curves in envoy as
"P-224",
"P-256",
"P-521",
"P-384",
"X25519",
"CECPQ2",

@kfaseela  Yes working now. Thank you so much for help.

@kfaseela  Need one more help, With TLS1.3 works and 1.2 fails with ECDH cipher ? Is there any configuration we need here .
/usr/bin/curl -vvv --ciphers  ECDHE-ECDSA-AES256-GCM-SHA384   --curves secp384r1  https://MASKED
*   Trying <IP_ADDRESS>:443...
* Connected to MASKED (cc) port 443 (#0)
* ALPN: offers h2
* ALPN: offers http/1.1
* Cipher selection: ECDHE-ECDSA-AES256-GCM-SHA384
*  CAfile: /etc/ssl/cert.pem
*  CApath: none
* (304) (OUT), TLS handshake, Client hello (1):
* (304) (IN), TLS handshake, Server hello (2):
* (304) (IN), TLS handshake, Unknown (8):
* (304) (IN), TLS handshake, Certificate (11):
* (304) (IN), TLS handshake, CERT verify (15):
* (304) (IN), TLS handshake, Finished (20):
* (304) (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / AEAD-CHACHA20-POLY1305-SHA256
* ALPN: server accepted h2
* Server certificate:
*  subject: C=US; ST=California; L=San Jose; O=Cisco Systems, Inc.; CN=*.MASKED
*  start date: Jan  9 00:00:00 2023 GMT
*  expire date: Jan 31 23:59:59 2024 GMT
*  subjectAltName: host "MASKED" matched cert's "*.MASKED
*  issuer: C=US; O=DigiCert Inc; CN=DigiCert TLS RSA SHA256 2020 CA1
*  SSL certificate verify ok.
* Using HTTP2, server supports multiplexing

/usr/bin/curl -vvv --ciphers  ECDHE-ECDSA-AES256-GCM-SHA384   --tlsv1.2 --tls-max 1.2  --curves secp384r1  https://MASKED
*   Trying <IP_ADDRESS>:443...
* Connected to MASKED (<IP_ADDRESS>) port 443 (#0)
* ALPN: offers h2
* ALPN: offers http/1.1
* Cipher selection: ECDHE-ECDSA-AES256-GCM-SHA384
*  CAfile: /etc/ssl/cert.pem
*  CApath: none
* (304) (OUT), TLS handshake, Client hello (1):
* error:1404B410:SSL routines:ST_CONNECT:sslv3 alert handshake failure
* Closing connection 0
curl: (35) error:1404B410:SSL routines:ST_CONNECT:sslv3 alert handshake failure

@kfaseela Need one more help, With TLS1.3 works and 1.2 fails with ECDH cipher ? Is there any configuration we need here .
/usr/bin/curl -vvv --ciphers  ECDHE-ECDSA-AES256-GCM-SHA384   --curves secp384r1  https://MASKED
*   Trying <IP_ADDRESS>:443...
* Connected to MASKED (cc) port 443 (#0)
* ALPN: offers h2
* ALPN: offers http/1.1
* Cipher selection: ECDHE-ECDSA-AES256-GCM-SHA384
*  CAfile: /etc/ssl/cert.pem
*  CApath: none
* (304) (OUT), TLS handshake, Client hello (1):
* (304) (IN), TLS handshake, Server hello (2):
* (304) (IN), TLS handshake, Unknown (8):
* (304) (IN), TLS handshake, Certificate (11):
* (304) (IN), TLS handshake, CERT verify (15):
* (304) (IN), TLS handshake, Finished (20):
* (304) (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / AEAD-CHACHA20-POLY1305-SHA256
* ALPN: server accepted h2
* Server certificate:
*  subject: C=US; ST=California; L=San Jose; O=Cisco Systems, Inc.; CN=*.MASKED
*  start date: Jan  9 00:00:00 2023 GMT
*  expire date: Jan 31 23:59:59 2024 GMT
*  subjectAltName: host "MASKED" matched cert's "*.MASKED
*  issuer: C=US; O=DigiCert Inc; CN=DigiCert TLS RSA SHA256 2020 CA1
*  SSL certificate verify ok.
* Using HTTP2, server supports multiplexing

/usr/bin/curl -vvv --ciphers  ECDHE-ECDSA-AES256-GCM-SHA384   --tlsv1.2 --tls-max 1.2  --curves secp384r1  https://MASKED
*   Trying <IP_ADDRESS>:443...
* Connected to MASKED (<IP_ADDRESS>) port 443 (#0)
* ALPN: offers h2
* ALPN: offers http/1.1
* Cipher selection: ECDHE-ECDSA-AES256-GCM-SHA384
*  CAfile: /etc/ssl/cert.pem
*  CApath: none
* (304) (OUT), TLS handshake, Client hello (1):
* error:1404B410:SSL routines:ST_CONNECT:sslv3 alert handshake failure
* Closing connection 0
curl: (35) error:1404B410:SSL routines:ST_CONNECT:sslv3 alert handshake failure

is TLS 1.2 working for you without ecdh curves?

yes. it works . I am suspecting it is something to do with external digicert cerificate which we have at ingress layer created using RSA.  https://github.com/envoyproxy/envoy/issues/8983??
/usr/bin/curl -vvv --ciphers  ECDHE-RSA-AES256-GCM-SHA384  --tlsv1.2 --tls-max 1.2   https://MASKED
*   Trying <IP_ADDRESS>:443...
* Connected to MASKED (<IP_ADDRESS>) port 443 (#0)
* ALPN: offers h2
* ALPN: offers http/1.1
* Cipher selection: ECDHE-RSA-AES256-GCM-SHA384
*  CAfile: /etc/ssl/cert.pem
*  CApath: none
* (304) (OUT), TLS handshake, Client hello (1):
* (304) (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
* ALPN: server accepted h2
* Server certificate:
*  subject: C=US; ST=California; L=San Jose; O=Cisco Systems, Inc.; CN=*.MASKED
*  start date: Jan  9 00:00:00 2023 GMT
*  expire date: Jan 31 23:59:59 2024 GMT
*  subjectAltName: host "MASKED" matched cert's "*.MASKED"
*  issuer: C=US; O=DigiCert Inc; CN=DigiCert TLS RSA SHA256 2020 CA1
*  SSL certificate verify ok.


Add Allspot BEP20 token

Official Allspot [ALT] BEP20 token logo SVG file uploaded
Official project website
On the website you can find project`s legal certificates, whitepaper and info about the founder.
Token address on BscScan
As you can see on the block explorer, $ALT is traded on PancakeSwap DEX and has locked liquidity on Unicrypt
Allspot BEP20 Token Smart Contract source code
Allspot`s social media presence:
Instagram
Twitter
Facebook
Telegram official channel
Linkedin
Reddit

@xrn Hello,
please review this pool request.
While this PR is awaiting your review Allspot token is being listed on few more centralised exchanges

Hello,
@davidwgrossman
@xrn
while waiting your approval Allspot token got listed on few more exchanges and crypto indexes
Exchange:
https://tokpie.com/dashboard/make_request/alt-usdt/
https://www.mintme.com/token/Allspot/trade
Index:
https://www.coingecko.com/en/coins/allspot
https://coinpaprika.com/coin/alt-allspot/
https://nomics.com/assets/alt7-allspot
https://www.livecoinwatch.com/price/Allspot-___ALT


IAmazonS3 missing HeadBucket

It appears that the IAmazonS3 interface is missing calls for HeadBucket, but if you look at the implementation classes AmazonS3Client, it exists.  Any reason it's in the implementation but not the interface?

Actually, looking closer, the HeadBucket in AmazonS3Client is marked internal as well, so it's not available to developers.

It's been a while, but I think we decided to exclude this operation from the public SDK because AmazonS3Util.DoesS3BucketExist performs a similar check and we wanted to avoid confusion. Will DoesS3BucketExist work for your use-case?

Hmm... strange placement, but yes that meets our needs.


Faq fast follow work

Work done

Animation  on toggle

allow only one section to be open at a time

Reinstitute spanish page to look like old page until we have new translations

There is some wonkiness around the animation and autoclosing sections as pictured below. I will remove the logic to autoclose sections logic so we can keep the animation looking smooth.


Support pcm format

Has been the gem supporting pcm format?
audio = FFMPEG::Movie.new('spec/files/speech_-1.pcm')
=> #<FFMPEG::Movie:0x000000070e7700 @path="spec/files/speech_-1.pcm", @metadata={:error=>{:code=>-541478725, :string=>"End of file"}}, @duration=0, @invalid=true>
But ffmpeg in console work fine.

I figured out when I have a problem. I need to pass '-f s16le' param for new because it needs for ffprobe.


Upate to ngrx ^14.x pls

can you update your package to ngrx ^14.x pls?

How about:
 "peerDependencies": {
    "@ngrx/effects": ">=13.2.0",
    "@ngrx/store": ">=13.2.0",
}

Fixed: https://www.npmjs.com/package/ngrx-loading-state/v/1.0.13

@Trebor2022 Consider giving it a star?


BOTS installation script fixes

commit looks like nothing is changed. However, these scripts utilize Windows CR LF line endings that cause errors:

I think this is fixed now


chore(releasePlease): release functions-framework-api 2.0.0

:robot: I have created a release beep boop
2.0.0 (2022-09-02)
Bug Fixes

remove warnings from mvn install (#66) (270f4ec)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/anniefu/functions-framework-java/releases/tag/functions-framework-api-v2.0.0 :sunflower:


How can I call _DSM  method in a UMDF USB driver?

I want to call _DSM method in a USB driver(UMDF driver),  but I set  UMDFDispatcher = WinUSB in inf file, when I call _DSM method, the program crashed.   If I delete UMDFDispatcher = WinUSB,  call _DSM method is successful.   Is there a way call _DSM method in a USB driver with UMDFDispatcher = WinUSB ???

文档详细信息
⚠ 请勿编辑此部分。 docs.microsoft.com ➟ GitHub 问题链接必须具有此部分。

ID: 8c3650d3-b014-9dfa-9cd9-431829f63a44
Version Independent ID: 7878124f-5c3e-0f43-12f1-33964b2f5e93
Content: USB Device-Specific Method (_DSM) - Windows drivers
Content Source: windows-driver-docs-pr/bringup/usb-device-specific-method---dsm-.md
Product: windows-hardware
GitHub Login: @barrygolden
Microsoft Alias: bagold

Thanks for reaching out to the Windows Driver Developer Documentation team. Unfortunately, we don’t have the resources to offer individual technical advice to the broad array of customers who use the driver documentation.
You may have success posting your question in the following forums, where other driver developers and Microsoft engineers can be found. The community there is quite responsive.
MSDN Windows Hardware WDK and Driver Development forum
NTDEV forum at OSR Online


Fix traffic lights position for command center

Relating to issue: 157895
While window.commandCenter is enabled on MacOS, the traffic lights are centered vertically but the left position looks off.
This commit should keep the x position the same as the y position as described in the issue.

Thanks @stephen-ullom


Add support for threading conversations in group chats (a la Flowdock)

This is an immensely useful feature for group chats where more than one conversation might be happening in a chat. We've already run into examples of conversation where a feature like this could prevent significant confusion.

+1. Also note that the implementation of threaded conversations in Mattermost is very usable, imho. Slack's implementation seems less usable, to me.

+1. Also note that the implementation of threaded conversations in Mattermost is very usable, imho. Slack's implementation seems less usable, to me.

Giant +1 on this. Threaded conversations are super powerful for low/medium volume groups.

Here is an animation I created presenting the flowdock threading feature:

The lack of this feature is making me avoid Keybase. The non-threaded conversations are so difficult to follow.

Mattermost also has similar threading as Flowdock, but without drag-n-drop between threads.

If I would design something for everybody, I would perhaps go with something like Flowdock/Mattermost, with everything visible by default, but where individuals could toggle the visibility of the replies in individual threads, and perhaps also a setting to allow hiding new threads by default (slack-like). But imho the default should be to show everything to everybody, and more advanced users could customize thread behaviour to their liking.


compress() exceeds recursion limit (jupyter exit code<PHONE_NUMBER>) when the number of rows in X is not a power of 4

Hi, thanks for the great algorithms!
I think compress() does not stop when the number of rows in X is not a power of 2.
How to reproduce: Run compress() on data with 442 rows:
from sklearn.datasets import load_diabetes
import numpy as np
X, _ = load_diabetes(return_X_y=True)
print(X.shape)
# X = X[0:64, :] #:# this will work fine
# print(X.shape)
from goodpoints import kt, compress
def kernel_gaussian(y, X, gamma=1):
    k_vals = np.sum((X-y)**2, axis=1)
    return(np.exp(-gamma*k_vals/2))
f_halve = lambda x: kt.thin(X=x, m=1, split_kernel=kernel_gaussian, swap_kernel=kernel_gaussian)
id_compressed = compress.compress(X, halve=f_halve, g=0)
print(id_compressed)

I guess that all experiments in the Compress++ paper are on datasets of size 2**n.
What does<PHONE_NUMBER> (0xc00000fd) exit code means?
Edit:
Apparently, 128 does not work also:
from sklearn.datasets import load_diabetes
import numpy as np
X, _ = load_diabetes(return_X_y=True)
print(X.shape)
X = X[0:128, :]
print(X.shape)
from goodpoints import kt, compress
def kernel_gaussian(y, X, gamma=1):
    k_vals = np.sum((X-y)**2, axis=1)
    return(np.exp(-gamma*k_vals/2))
f_halve = lambda x: kt.thin(X=x, m=1, split_kernel=kernel_gaussian, swap_kernel=kernel_gaussian)
id_compressed = compress.compress(X, halve=f_halve, g=0)
print(id_compressed)

Thank you for bringing this to our attention @hbaniecki.  The latest commit ensures appropriate behavior for any number of rows.


WriteResult.nextExpectedRevision.valueUnsigned no longer exits in v4.0.0

It looks line WriteResult.nextExpectedRevision.valueUnsigned was removed in v4.0.0. What is the alternative?

Hey @oexza , hard to answer you question without context. What were you doing with that value before? A snippet would help too.


Search Bar dosen't Work

Can't search for anything as well as awkward sprite element appears when you type [Probaply use to clear? but it's useless with it's size]

Fixed search with index.html update commit


install ToolTip

Install ToolTip on Buttons
Added option to show ToolTip immediately on the buttons mouse over
event.

Thanks, looks good :)


Add organization administrator button is not working in the console

Describe the issue:
Add organization administrator button is not working in the console
How to reproduce:
Go to Administrators tab in the console and try to add an admin.

Didn't released with alpha. Hence moving the milestone.

This is a regression due to an improvement in Add User Wizard.

Fixed with: https://github.com/wso2/identity-apps/pull/4454


Example "window" compilation error on Qubes OS

Bevy version
commit/3e285d5c0bd49cf1aff11cf3848270bafdd48646
Operating system & version
Qubes OS R4.0 with template Debian 11
What you did
A compilation error occurred when trying to compile the "ui" example on Qubes OS (Xen virtualization based) on the Debian 11 template. It probably appeared because Qubes OS does not provide information about the existence of a physical monitor through virtualization.

Install Qubes OS on home PC
Upgrade default template Debian 10 to Debian 11
Try compile Bevy example "ui"

Logs
WARNING: lavapipe is not a conformant vulkan implementation, testing use only.
vulkan: No DRI3 support detected - required for presentation
Note: you can probably enable DRI3 in your Xorg config
thread 'main' panicked at 'Error in Device::create_swap_chain: surface does not support the adapter's queue family', /home/user/.cargo/registry/src/github.com-1ecc6299db9ec823/wgpu-0.7.0/src/backend/direct.rs:129:9
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace
Apr 06 09:30:48.696 ERROR gpu_descriptor::allocator: DescriptorAllocator is dropped while some descriptor sets were not deallocated
Apr 06 09:30:48.697 ERROR gpu_alloc::block: Memory block wasn't deallocated
Apr 06 09:30:48.697 ERROR gpu_alloc::block: Memory block wasn't deallocated
Segmentation fault
Source:
https://pastebin.com/VSaTmkjV
Additional information
It is understandable that the Bevy engine has problems with Qubes OS as it is a very specific home system that relies on virtualization for security reasons.

QubesOS doesn't allow VM's to use the GPU unless you setup GPU passthrough for the VM. This requires a separate GPU for this VM. Without GPU passthrough the only options are to use virtio-gpu (currently no vulkan support in mesa: https://www.phoronix.com/scan.php?page=news_item&px=VirtIO-GPU-Vulkan-Mesa-RFC) or to use software rendering. For vulkan this requires lavapipe, which is still experimental.

WARNING: lavapipe is not a conformant vulkan implementation, testing use only.

The actual problem here is

vulkan: No DRI3 support detected - required for presentation
Note: you can probably enable DRI3 in your Xorg config

Which makes it impossible to actually show something on the screen, hence the

thread 'main' panicked at 'Error in Device::create_swap_chain: surface does not support the adapter's queue family', /home/user/.cargo/registry/src/github.com-1ecc6299db9ec823/wgpu-0.7.0/src/backend/direct.rs:129:9

I am not sure if DRI3 can be enabled at all without either a real or virtio gpu being used.

@bjorn3
Of course, I know that Qubes OS does not allow easy access to the GPU due to the problem with secure virtualization of this object, but then how to force software rendering? It would be nice to add detection to Bevy in such a case that would atumatically force software rendering.

Mesa tried to use lavapipe for software rendering automatically. It is currently experimental. The problem you have may be one of the reasons.

Bevy works with lavapipe, it is used in CI. Not sure we can do much more for Qubes OS, please reopen if you have an actionable issue


Updates for Mobile Apps

Fixed /UserSites endpoint to only return camera sites with photos and added api method to allow creation of a new site.

@zmchristensen, I deployed this into production. You should be able update the mobile apps to use the new endpoints.


Sleep while lock setting ignored

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
With the "vehicle must be locked" setting enabled, the car is still sleeping.
Expected Behavior
The car would not attempt to sleep or actually fall asleep while unlocked.
Steps To Reproduce

Enable the requirement to be locked to sleep
Let the car reset
Notice the sleep pattern

Relevant log output
teslamate_1  | 2021-12-02 10:00:32.067 car_id=1 [warn] Unlocked ...
teslamate_1  | 2021-12-02 10:01:02.393 car_id=1 [warn] Unlocked ...
teslamate_1  | 2021-12-02 10:01:32.909 car_id=1 [warn] Unlocked ...
teslamate_1  | 2021-12-02 10:01:42.400 [info]     :alarm_handler: {:clear, TeslaMate.Vehicles.Vehicle_1_api_error}
teslamate_1  | 2021-12-02 10:02:03.485 car_id=1 [warn] Unlocked ...
teslamate_1  | 2021-12-02 10:02:33.583 [info] GET https://owner-api.teslamotors.com/api/1/vehicles/REDACTED/vehicle_data -> 408 (96.174 ms)
teslamate_1  | 2021-12-02 10:02:43.862 car_id=1 [info] Start / :asleep
teslamate_1  | 2021-12-02 10:02:43.889 car_id=1 [info] Disconnecting ...

Screenshots

Additional data
No response
Type of installation
Docker
Version
1.25

Discovered this was related to the missing Model in the cars table. See here #2193 .
Manually inserted the Model S into the cars table and now it will not go to sleep while unlocked.


youtube-dl-GUI for Python 3 using PyQt5

Addd ThreadPool
More stable

I have invited you as a collaborator. I did a cursory review of the PR and it looks good but you can go ahead and finish it up if it looks good to you. You should have access to merge it now. I don't have enough bandwidth to explore it in detail.
I hope the project grows under your guidance :)

I am going to join this PR which is the version compatible with PyQt5 in Python3. I am going to review the Conversion part and update youtube-dl. Thanks for adding me to the project!


Add a util function for web testing

What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Does this PR introduce a user-facing change?:

NONE

@cakecatz Test failed.

@cakecatz Test failed.

@nghialv I fixed failed code.

@nghialv I fixed failed code.

/approve

/approve


Easiest way to port MuJoCo to Brax?

The code just relies on dm_control and dm_env packages. Are there any analogous Brax packages that I can use to port the code?

We currently support conversion of (a small subset) of MuJoCo xml into brax configs via our converter tool here: https://github.com/google/brax/blob/main/brax/tools/mujoco_converter.py
You will have to manually tune some constants that don't have a good representation on the MuJoCo side, but are required on the brax side (like spring stiffnesses and damping parameters).  Let me know if you run into any trouble with the converter---it can be a little tricky to tune things correctly.

Closing this as I think it's addressed, but please do re-open if you have any other questions.

@erikfrey in case we would like to get more people to migrate from mujoco to brax, we should more openly document this somewhere I think. I found out about the mujoco_converter through discussions with the team and through this issue. If necessary, I can even provide a notebook in colab that helps with the migration of mujoco envs right in there.

@benelot good call, opened an issue to track this.


Distinguish bot when emitSelf (explicitly true/false)

When the option "emitSelf" is true, there's no clear way to distinguish the bot from otherwise. (Say the account runs on the same account as the owner of the bot or as another bot) Simply passing a fourth argument to the event listeners as "from self" should be enough (with explicit true or false).
client.addListener('chat', function(channel, user, text, fromSelf) {
    console.log('This message was ' + (fromSelf ? '' : 'not ') + 'from me.');
    /* fromSelf === false
     *      "This message was not from me."
     * fromSelf === true
     *      "This message was from me."
     */
});

I'm not very good at GitHub yet :sob: Not sure how to update a pull


[debugserver] Fix the G packet handling.

Of course r331004 needed a counterpart on the write side.
git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@331073 91177308-0d34-0410-b5e6-96231b3b80d8

@swift-ci test and merge


Fix up README.md wrt kernel documentation link

The link to the kernel documentation was malformed.

not lgtm sorry, this documentation is auto generated.

Is godoc2md already patched for the bug, then?

Probably not, do you want to take a look >
On Mon, Aug 24, 2015 at 10:00 AM, Christopher Harrington <
<EMAIL_ADDRESS>wrote:

Is godoc2md already patched for the bug, then?
—
Reply to this email directly or view it on GitHub
https://github.com/pkg/taptun/pull/5#issuecomment-133966877.

Actually looks like it is fixed in this merge. Although for what it's worth it still doesn't make sense to wrap a bare URL in an <a> tag with itself as the href in markdown; the markdown parser is already doing that. I would suggest regenerating README.md with the patched godoc2md.


[Question] Which Kernel Capabilities does k3s need?

Hi there,
While developing k3d, I often hit that one stone which is having to run the k3s containers in privileged mode.
This blocks us from e.g. making use of resource limits set on node level (privileged mode renders cgroup limits useless).
Did anyone maybe do an analysis and some point on which capabilities k3s actually needs to run?
I guess most things would be requested by containerd, right?
I'm pretty sure that we can't get to this point where we'll be able to use memory limits in k3d, but still it would be very interesting to know, if we could limit the set of capabilities given to the k3s containers for running in security sensitive environments.

Hello @dweomer ,
I have made some tests and for using rootless with k3s you still need to run a priviledge docker container.
Without this you have this error failed to start the child: fork/exec /proc/self/exe: operation not permitted.
I'm starting to add some capabilities but I'm afraid it's going to be like working with --privileged.
If you want to test it I have a docker image for k3s v1.17.0 with uidmap and a user. I will put the Dockerfile at the end of this message.
For tests :
OK (with privileged)
docker run --rm -it --privileged -p 6443:6443 -p 10080:10080  louiznk/k3s:rootless server --rootless
... normal trace and no crash ...

KO (without privileged)
docker run --rm -it -p 6443:6443 -p 10080:10080  louiznk/k3s:rootless server --rootless
... failed to start the child: fork/exec /proc/self/exe: operation not permitted

KO (with capas)
docker run --rm -it -p 6443:6443 -p 10080:10080 --security-opt seccomp=unconfined --security-opt apparmor=unconfined --security-opt systempaths=unconfined  louiznk/k3s:rootless server --rootless
... failed to setup UID/GID map: newuidmap 23 [0 1001 1 1<PHONE_NUMBER>6] failed: newuidmap: write to uid_map failed: Operation not permitted

KO (with more capas)
docker run --rm -it -p 6443:6443 -p 10080:10080 --security-opt seccomp=unconfined --security-opt apparmor=unconfined --security-opt systempaths=unconfined  --cap-add SYS_ADMIN  louiznk/k3s:rootless server --rootless
open: No such file or directory
... failed to setup network &{binary:slirp4netns mtu:65520 ipnet:0xc000e370b0 disableHostLoopback:true apiSocketPath:}: setting up tap tap0: executing [[nsenter -t 24 -n -m -U --preserve-credentials ip tuntap add name tap0 mode tap] [nsenter -t 24 -n -m -U --preserve-credentials ip link set tap0 up]]: exit status 1

The Dockerfile for buiilding the test image louiznk/k3s:rootless
FROM alpine:3.12 AS uidmap
RUN apk -u --no-cache add shadow-uidmap

## k3s with uidmap binaries
FROM rancher/k3s:v1.17.0-k3s.1 AS assembly

COPY --from=uidmap /etc/passwd /etc/group /etc/shadow /etc/subgid /etc/subuid /etc/
COPY --from=uidmap /usr/bin/newgidmap /usr/bin/newuidmap /usr/bin/
COPY --from=uidmap /lib/ld-musl-x86_64.so.1 /lib/
RUN mkdir -p /var/lib/rancher/k3s
RUN mkdir -p /output

## dest with k3s user
FROM scratch

COPY --from=assembly / /

RUN adduser -h /var/lib/rancher/k3s -g k3s -s /bin/false -D -u 1001 -G root k3s \
        && chown k3s:root /var/lib/rancher -Rv \
        && chown k3s:root /output -Rv \
        && echo k3s:200000:65536 >> /etc/subuid \
        && echo k3s:200000:65536 >> /etc/subgid

USER k3s:root

VOLUME /var/lib/kubelet
VOLUME /var/lib/rancher/k3s
VOLUME /var/lib/cni
VOLUME /var/log

ENV PATH="$PATH:/bin/aux"

ENTRYPOINT ["/bin/k3s"]
CMD ["agent"]

Hello @iwilltry42
Finally it's start with this capabilities and this devices access right (in rw and mknod)
docker run --device=/dev/net/tun --device=/dev/kmsg --rm -it -p 6443:6443 -p 10080:10080  --security-opt seccomp=unconfined --security-opt apparmor=unconfined --security-opt systempaths=unconfined  --cap-add SYS_ADMIN  louiznk/k3s:rootless server --rootless

Capabilities :
--security-opt seccomp=unconfined --security-opt apparmor=unconfined --security-opt systempaths=unconfined  --cap-add SYS_ADMIN
Devices : (note sure it's portable on every system)
--device=/dev/net/tun --device=/dev/kmsg
If I well understand

/dev/net/tun for tap0 using by slirp4netns
/dev/kmsg using by OOM watcher

I will continue to investigate to see if k3s is working (curl on API server & Traefik are ok)

--security-opt systempaths=unconfined --cap-add SYS_ADMIN

These are equivalents of --privileged. I'd rather suggest just setting --privileged for simplicity.

--security-opt systempaths=unconfined --cap-add SYS_ADMIN

These are equivalents of --privileged. I'd rather suggest just setting --privileged for simplicity.
Thanks a lot for your help @AkihiroSuda, unfortunately, I would prefer to run without privileged (Apparently when you run with privileged the memory constraint you apply to the docker container are ignored by k3s).

So I need to use some restrictive capabilities, I have tried to replace SYS_ADMIN capability by SETUID + SETGID but with this, I still have the error on uidmap
failed to setup UID/GID map: newuidmap 22 [0 1001 1 1<PHONE_NUMBER>6] failed: newuidmap: write to uid_map failed: Operation not permitted
Have you got an idea or a suggestion?

The newuidmap error can be probably avoided by compiling newuidmap with libcap https://github.com/moby/buildkit/blob/7f42dbf9b41c0de89c744823054ab8e7c4020c68/Dockerfile#L26
But anyway I don't see much benefit in choosing systempaths=unconfined instead of --privileged.
A process running as the root in a container with systempaths=unconfined can easily break the container via procfs and sysfs.

The newuidmap error can be probably avoided by compiling newuidmap with libcap https://github.com/moby/buildkit/blob/7f42dbf9b41c0de89c744823054ab8e7c4020c68/Dockerfile#L26

Thanks, I will try to build shadowuid with libcap.

But anyway I don't see much benefit in choosing systempaths=unconfined instead of --privileged.
A process running as the root in a container with systempaths=unconfined can easily break the container via procfs and sysfs.

It could sound strange but my aim is not to make a more secure container, I want to limit the "view of the resources available" for k3s to the container resources. Perhaps I take this in the wrong way.
Let me try to explain " limit the view of the resources available":
I want the limit (cpu & memory) that is on the container running k3s (with the flag --memory ...) is the reference for k3s, but the reference for k3s is the system (not the container). So if I run a cluster for k3s in docker (with k3d) I have a wrong view of the resources available (for every container we have the system resources, if you have a cluster with 1 server and 2 agents your cluster things he has 3 more time cpu and memory that he have).
Maybe an example is more clear than my explanation: A cluster with 1 server and 2 agents, on 3 containers limit at 512MiB
$ docker stats --no-stream
CONTAINER ID        NAME                       CPU %               MEM USAGE / LIMIT     MEM %               NET I/O             BLOCK I/O           PIDS
8b8ccc4e7383        k3d-memlimit-agent-1       4.07%               155MiB / 512MiB       30.27%              29.2MB / 453kB      299kB / 14.1MB      158
60be6633c344        k3d-memlimit-agent-0       9.33%               119.5MiB / 512MiB     23.34%              16.1MB / 424kB      528kB / 21.1MB      113
8979c47c1293        k3d-memlimit-server-0      21.92%              510.1MiB / 512MiB     99.63%              75.1MB / 2.09MB     16MB / 54.1MB       130
...

But for kubernetes the total memory available is the system memory * 3
$ kubectl top node
NAME                    CPU(cores)   CPU%   MEMORY(bytes)   MEMORY%
k3d-memlimit-agent-0    39m          0%     124Mi           0%
k3d-memlimit-agent-1    43m          0%     150Mi           0%
k3d-memlimit-server-0   148m         1%     474Mi           1%

$ kubectl describe node k3d-memlimit-server-0
....
Capacity:
...
  memory:             32493528Ki
...

This is with a standard k3s. So I try with to run it as rootless with the same result (directly run with docker without k3d and for this try only 1 server with 1024 MiB)
$ docker run --device=/dev/net/tun --device=/dev/kmsg --rm -it -p 6443:6443 -p 10080:10080  --security-opt seccomp=unconfined --security-opt apparmor=unconfined --security-opt systempaths=unconfined  --cap-add SYS_ADMIN -m 1024m louiznk/k3s:rootless server --rootless
....
$ docker stats --no-stream
CONTAINER ID        NAME                  CPU %               MEM USAGE / LIMIT   MEM %               NET I/O             BLOCK I/O           PIDS
3ba626186bf2        xenodochial_khayyam   65.03%              387.3MiB / 1GiB     37.82%              23.2kB / 4.2kB      0B / 1.57MB         114

# into the docker image (docker exec ...)
$ kubectl get node ...
....
Capacity:
....
  memory:             32486464Ki
....
...

Perhaps for my need it's a wrong way:
It's look like the memory contraint isn't know by k3s because it doesn't know it is in container and it use something like /proc/meminfo instead of /sys/fs/cgroup/memory/memory.limit_in_bytes (which as I just read and test is used by docker with cgroup to limit the memory)
I hope you doesn't lost you time on this, thanks for your help.
PS: Just for information I try to run the container using shadowuid build with libcap with the same result (error failed to setup UID/GID map:...)

Perhaps for my need it's a wrong way:
It's look like the memory contraint isn't know by k3s because it doesn't know it is in container and it use something like /proc/meminfo instead of /sys/fs/cgroup/memory/memory.limit_in_bytes (which as I just read and test is used by docker with cgroup to limit the memory)

That look to be that: https://github.com/rancher/k3s/blob/master/vendor/github.com/google/cadvisor/machine/machine.go#L128
Cadvisor is used by kubelet to get resources (for the node and the containers) see https://github.com/rancher/k3s/blob/master/vendor/k8s.io/kubernetes/pkg/kubelet/kubelet.go#L917 (and more much time in the code)

I hope you doesn't lost you time on this, thanks for your help.
PS: Just for information I try to run the container using shadowuid build with libcap with the same result (error failed to setup UID/GID map:...)

Hi @louiznk & @AkihiroSuda thanks for looking into this and going down this rabbit hole! :)
However, it seems that even though rootless mode in k3s is maturing, we won't be able to get rid of privileged mode in k3d...
@louiznk I like your approach though to make cAdvisor aware of it's containerized environment and I see, that even if they don't accept your PR, you can make it work with a k3s fork that includes the customized cAdvisor. Wish you the best of luck and success with this :+1:
Unfortunately, it seems that we have to close this issue as unsolvable though :confused:
Thanks again!

Hi @louiznk & @AkihiroSuda thanks for looking into this and going down this rabbit hole! :)
However, it seems that even though rootless mode in k3s is maturing, we won't be able to get rid of privileged mode in k3d...
@louiznk I like your approach though to make cAdvisor aware of it's containerized environment and I see, that even if they don't accept your PR, you can make it work with a k3s fork that includes the customized cAdvisor. Wish you the best of luck and success with this
Unfortunately, it seems that we have to close this issue as unsolvable though
Thanks again!

Thanks @iwilltry42 and @AkihiroSuda for your time and explanation, I learn a lot 🙏


[bugfix] Respect cli modulepaths during module restore

Fixes #1631

@jgphpc can you check if this works for you?

Codecov Report

Merging #1656 (e9426c9) into master (4bf3156) will decrease coverage by 0.11%.
The diff coverage is 10.00%.

@@            Coverage Diff             @@
##           master    #1656      +/-   ##
==========================================
- Coverage   87.72%   87.60%   -0.12%
==========================================
  Files          45       45
  Lines        7477     7487      +10
==========================================
  Hits         6559     6559
- Misses        918      928      +10

Impacted Files
Coverage Δ

reframe/core/modules.py
58.24% <10.00%> (-1.22%)
:arrow_down:

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 4bf3156...e9426c9. Read the comment docs.


Updated to support new config model

Codecov Report

Merging #109 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master   #109   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          32     32
  Lines         662    665    +3
  Branches       79     82    +3
=====================================
+ Hits          662    665    +3

Flag
Coverage Δ

#builder
100% <100%> (ø)
:arrow_up:

#runtime
100% <ø> (ø)
:arrow_up:

Impacted Files
Coverage Δ

loader/sky-processor/index.js
100% <100%> (ø)
:arrow_up:

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 ce21363...17ac974. Read the comment docs.


Update page.js

This is a set of JavaScript functions that are used for expanding and collapsing content in a web page. The toggleChildren function toggles the visibility of the child elements of the given element, while the showChildren function shows the child elements. The toggleNext function toggles the visibility of the next sibling element of the given element. The toggleId function toggles the visibility of the child elements of the element with the given ID. The jumpToId function scrolls the page to the element with the given ID and shows its child elements. The jumpToCall function scrolls the page to the element with the given ID. The jumpToTop function scrolls the page to the top.

Changes not needed.  Please don't spam us with PRs


Better not change the Stream ctx.body

Desc
I did something like this:
app.use(koaLogger).use(async ctx => {
  ctx.type = 'html'
  ctx.set('Content-Encoding', 'gzip')

  ctx.body = zlib.createGzip({
    flush: zlib.constants.Z_FULL_FLUSH,
  })
  ctx.body.write(Buffer.from('before'))
  setTimeout(() => {
    ctx.body.write(Buffer.from('after some async operation'))
    ctx.body.end()
  }, 1000)
})

However, koa-logger changes ctx.body to ctx.body.pipe(counter = Counter()):
https://github.com/koajs/logger/blob/7daa5f401644a7ae396de70874dfa8328e9202d6/index.js#L81-L83
which makes the second write() and end buggy...
Workaround
Write into the original stream, instead of ctx.body
app.use(koaLogger).use(async ctx => {
  ctx.type = 'html'
  ctx.set('Content-Encoding', 'gzip')

  const gzip = zlib.createGzip({
    flush: zlib.constants.Z_FULL_FLUSH,
  })
  ctx.body = gzip
  gzip.write(Buffer.from('before'))
  setTimeout(() => {
    gzip.write(Buffer.from('after some async operation'))
    gzip.end()
  }, 1000)
})

Conclusion
The workaround is simple, but that did make me confused before I read the source code of koa-logger.
I would suggest not to modify the ctx.body itself.

Isn't that expected? You should return promise from your middleware and once that promise is resolved, Koa thinks your middleware did its work. I think correct way to structure your code is:
app.use(koaLogger).use(async ctx => {
  ctx.type = 'html'
  ctx.set('Content-Encoding', 'gzip')

  ctx.body = zlib.createGzip({
    flush: zlib.constants.Z_FULL_FLUSH,
  })
  ctx.body.write(Buffer.from('before'))
  return new Promise(resolve => {
    setTimeout(() => {
      ctx.body.write(Buffer.from('after some async operation'))
      ctx.body.end()
      resolve();
    }, 1000)
  });
})

See https://cabinjs.com and its middleware


Questions

I have two questions:

Is it possible to create two or more types of events with different styles?
Is it possible to display the selected day?

Thank You

For events with different styles, see #6. I am not sure what you mean when you say "display the selected day", but #59 might be helpful.


Fixed #31039 -- Added support __contained_by lookup for AutoFields and BigAutoFields.

Ticket 31039.

Might want to throw support for SmallAutoField in there as well since it was added by #11611.

So probably also for a SmallIntegerField.

Might want to throw support for SmallAutoField in there as well since it was added by #11611.

So probably also for a SmallIntegerField.

And probably also DecimalField, so all of those extras would be:
...
    type_mapping = {
        ...
        'smallserial': 'int4range',
        'smallint': 'int4range',
        'numeric': 'numrange',
        ...
    }
...
models.SmallAutoField.register_lookup(RangeContainedBy)
models.SmallIntegerField.register_lookup(RangeContainedBy)
models.DecimalField.register_lookup(RangeContainedBy)

@felixxm, @charettes, @pope1ni Thanks for the review and suggestions.
Requested fields added.

@charettes Thanks again for the review.
The requested changes are ready now.
Unfortunately, I didn't get you completely about splitting the commits. :thinking:

@felixxm I think this path is complete now. the only remaining thing is splitting the commits as @charettes comment.
Could you please give me more detail about how to split them?

To clarify the commit splitting part, I wrongly assumed that this happened to be fixed for AutoField and BigAutoField by accident when we made them subclass IntegerField 21e559495b8255bba1e8a4429cd083246ab90457 but it's not the case because we were missing the RangedContainedBy.type_mapping for them as well.
I guess we could still remove the superflous BigIntegerField.register_lookup in a first commit if we wanted to.

@charettes Thanks again for the explanation.
I split the commits.

Thanks, I pushed minor edits.


security: extend overview to cover secure boot

Signed-off-by: Ricardo Salveti<EMAIL_ADDRESS>

Docs for 2a9dd2fc3d80c87cddcce63c26d11e60c313a521 are browesable at: https://ci.foundries.io/projects/fio-docs/builds/1276/docs/artifacts/html/index.html

Docs for 9bfd9b30bae6ea7490a758f43fcffe90a838f3f4 are browesable at: https://ci.foundries.io/projects/fio-docs/builds/1279/docs/artifacts/html/index.html

@vanmaegima updated.

Docs for e03d2a45eacb9c475319de778c37526975a90021 are browesable at: https://ci.foundries.io/projects/fio-docs/builds/1280/docs/artifacts/html/index.html


fix: retry issue in Prepare the enviroment step

Closes #298
Signed-off-by: Hai He<EMAIL_ADDRESS>

/test

Tests looking good, no failures out of Postgres 1

/ok-to-merge


cmd/go2go: improve error messages for missing or superfluous type constraints

What version of Go are you using (go version)?
go2go playground
Does this issue reproduce with the latest release?
N/A
What operating system and processor architecture are you using (go env)?
N/A
What did you do?

https://go2goplay.golang.org/p/m9YUDBTWwpA
func (m *MyMap[KT,VT comparable]) set(k KT, v VT) { ...

https://go2goplay.golang.org/p/GDxiXiIIti7
func blah[T1, T2](x T1) T2 { ...

What did you expect to see?

error to the effect that a constraint was used in a place where it's not allowed
error to the effect that a type constraint is missing

What did you see instead?

"missing ',' in type argument list"
"all type parameters must be named" (even though they were named!)

CC @griesemer

CC @griesemer

The first error is fixed in the latest (internal, not deployed version). The 2nd error is correct but misleading: Since the type parameter list is [T1, T2] and since type parameter lists are syntactically like regular parameter lists (but for the []'s), it looks like a parameter list with two constraints T1 and T2 and without explicitly named type parameters. For comparison, note that func f(int, int){} is a valid function declaration with unnamed value parameters.
Anyway, agreed that the error message should be better.

The first error is fixed in the latest (internal, not deployed version). The 2nd error is correct but misleading: Since the type parameter list is [T1, T2] and since type parameter lists are syntactically like regular parameter lists (but for the []'s), it looks like a parameter list with two constraints T1 and T2 and without explicitly named type parameters. For comparison, note that func f(int, int){} is a valid function declaration with unnamed value parameters.
Anyway, agreed that the error message should be better.

A similar case occurs when defining generic types if you omit the constraint on the type parameter, e.g.
https://go2goplay.golang.org/p/GqCc1gE36NL
That is, if you write
type slot[T] ...

instead of
type slot[T any] ...

In the go2go playground, the error currently says "undeclared name: T", rather than "type parameter T is missing type constraint"

For comparison, note that func f(int, int){} is a valid function declaration with unnamed value parameters.

Ugh, I didn't realise that was allowed.  If you want to discard arguments, you can also write func f(_, _ int){}, and to me that makes the intention clearer.

"type slot[T]  some_type" defines slot as an array of length T of element type some_type.  If T is not defined anywhere, then undeclared name: T is a correct error message.
That said, we might want to tweak the compiler error message here to make clear that the type is being interpreted as an array type.

"type slot[T]  some_type" defines slot as an array of length T of element type some_type.  If T is not defined anywhere, then undeclared name: T is a correct error message.
That said, we might want to tweak the compiler error message here to make clear that the type is being interpreted as an array type.


Game crashed and it seems the .json is corrupt?

Hi!
I'm following you since you took on the task to fork AMECS, which I'm very grateful for.
We have a server running on 1.21.1 and since you launched the fork, I'm using the too-many-shortcuts mod without any problems.
Today I had a client crash and since then I'm unable to start the game. See the error.log here: https://mclo.gs/y4y1qQj
Disabling the mod lets the game restart, although all the resource packs were disabled and other settings were reset (monochrome Mojang logo).
Looking into 'too-many-shortcuts.json' shows me 'null' values over and over:

I had to delete this file to reinstall the mod and start the game.
I'm not sure what happened here but I wanted to let you know.

That is interesting.

So the game crashed randomly? After that the mod wouldn't load?
If so is that the crash log from the original crash?

Hi!
Yes, the game crashed / froze the computer and I had to restart.  After that the game would exit with the problems I sent you, so no, that log is not the original crash log, it is the subsequent log trying to restart the game.
I'm not sure that there is a crash log for the moment the game froze, as it couldn't shut down gracefully.  I'll have to look later when I'm back home but I doubt that there is something.


Handle large a/v offset in first segment of recordings.

transcode: drop first segment if a/v tracks have a large offset

For HLS input (recordings), sometimes the first segment can experience a
large delta between the audio and video track's start time (in seconds).
This is mainly because when a streamer begins the stream, the user's
hardware config and OBS settings might cause the video track to start
later than the audio (or vice versa). These segments can be transcoded
but muxing them into an MP4 will fail. For these cases, the first segment
should be dropped from the transcode payload.

If it works then LGTM, but do we have any sense why this offset would cause problems when muxing to MP4?
Also it looks like the Cucumber tests are failing

Because MP4s need a/v starting PTS to be very close to one another otherwise the headers cannot be generated correctly. The 1s is arbitrary and we may update in the future. The offending recordings typically have 8s+ offsets between a/v tracks and the video typically starts later.


⚠ Jenkins Plugins Artifactory has degraded performance

In 406fa3d, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1351 ms

Resolved: Jenkins Plugins Artifactory performance has improved in f5ee9a9 after 13 minutes.


Add FTPS Functionality

This PR adds FTPS functionality to the app.

@jsavage7 - Just FYI, I migrated your commits to a new branch (feature/ftps) so we don't need to merge master back in to InboundOptimization.


CPS tag for Dialogic

Many dialogue systems include ways to change the text speed in the middle of a dialogue, which allows the text to have more versatile expression. Dialogic, despite its complexity, seems to lack this feature.
Describe the solution you'd like
A special BBCODE tag which could be something to the effect of {cps=10}, or setting the text speed to 10 characters per second.
Additional context
Ren'py does this quite elegantly, and is documented here, if example is needed

There already is a [speed=2] tag, that will change the text speed for the current text event. With 1.4, it will also be possible to change the speed mid sentence with this tag. If you download the WIP version (main branch on github) you can already try it out.


Improve mechanism to download complete message

When the user clicks the "Download complete message" button we (try to) download the message in a background thread and notify the caller via a callback.
This has a couple of drawbacks:

when there's a network error or no connectivity there's no automatic retry, i.e. the user has to press the button again
the callback leaks a reference to the activity (see #690)
on orientation change the callback references the old activity, i.e. the new activity isn't notified
there's no guarantee that a service is running, i.e. the app might be killed sooner than necessary when it is moved to the background
we're not holding a wake lock while downloading the message, i.e. the device could go to sleep during download

Anyway to make this an option?  In other words, I never had an issue viewing the complete message before, but now, I have to press the button, wait a while, then the message loads.  This feature is a real annoyance.  Please remove or include it as an option (or maybe it is and I don't know about it yet).

Is this still an issue?

Hello Felix,
I don't think so.  Thank you very much for all the efforts you guys put into this.
Best regards,
Rick
On October 7, 2024 11:53:04 AM CDT, Felix Baumann @.***> wrote:

Is this still an issue?
--
Reply to this email directly or view it on GitHub:
https://github.com/thunderbird/thunderbird-android/issues/782#issuecomment-2397433382
You are receiving this because you commented.
Message ID:
@.***>

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


Ionic - Cordova application

Core Library
MSAL.js v2 (@azure/msal-browser)
Wrapper Library
MSAL Angular (@azure/msal-angular)
Public or Confidential Client?
Public
Description
Allow to use msal-angular using ionic-cordova based application
->
https://github.com/AzureAD/microsoft-authentication-library-for-js/issues/5052
https://github.com/AzureAD/microsoft-authentication-library-for-js/issues/4290
Source
External (Customer)

@phyr0s We do not currently support Cordova, Capacitor or any hybrid framework. We do have this on our backlog for future consideration but unfortunately do not have an ETA at this time. You can track updates to that feature request in #4290. Closing this as duplicate for now.


Added support for rabbitmq vhosts

Added new config option to provide rabbitmq vhost.

Thanks :+1:

Are you going to release new version in future?

Tagged version 1.0.2


Chrome Extension Windows 7: Pagination is not correct, according to spec

Spec:
When a Reading System renders a Synthetic Spread, the default behavior is to populate the spread by rendering the next EPUB Content Document in the next available unpopulated viewport, where the next available viewport is determined by the given page progression direction or by local declarations within Content Documents.
I created a very simple reflowable book using all property defaults. The result is that the first XHTML file (which is short) is rendered on a left-hand page and is followed by a blank right-had page. The first Chapter (second XHTML file) begins on the next left-hand page. Seems that each XHTML file is starting on a left-hand page, rather that the next available slot, as the spec says it will.

That's correct, the reflowable viewport spans the entire available width, even if (visually) only the left hand side "column" of the synthetic spread is populated by content (are you aware of other reading systems implementing this correctly?). I am pretty confident that this restriction will remain for a long time in Readium, as fixing this would require very significant changes in how the reflowable view functions.
Note that as a byproduct of this limitation, Readium currently does not support mixing reflowable and fixed-layout viewports within the same visual space (I am not aware of any reading system that does though).

Here are JPGs which illustrate this issue.

XHTML File 1

XHTML File 2
According to the spec, File 2 should start on the right hand slot next to File 1 Page Description. But, Chrome is inserting a blank right and forcing Chapter 1 to start on the next left.

Closing as duplicate: https://github.com/readium/readium-js-viewer/issues/256


Add set ViewControllers function

It would be great if a setViewControllers function for the NavigationCoordinator would be added to the Toolbox .

@draskovits


Update ECS documentation for latest improvements

Update https://aws-otel.github.io/docs/setup/ecs for both ECS on EC2 and ECS on Fargate.
Add more info about infrastructure, container and appl metrics and traces
Review and improve related pages -
https://aws-otel.github.io/docs/components/ecs-metrics-receiver
Add more screenshots for user to understand what to expect for each step in setup.

@rltoSD Can you take a look - imo the content needs to be updated.

Will take a look at this @alolita

New additions - https://aws-otel.github.io/docs/getting-started/using-ecs-console-for-ecs-adot-observability and https://aws-otel.github.io/docs/getting-started/ecs-configurations/ecs-console-setup


feat: move theme data to config

Description

also solve BDU-601 & BDU-602
blocked by #1007
Checklist

[ ] Ran Linting
[ ] Targeted PR against correct branch.
[ ] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[ ] Wrote unit tests.
[ ] Added an entry to the CHANGELOG.md file.
[ ] Re-reviewed Files changed in the Github PR explorer.

@huichiaotsou Can you solve the conflicts please?


powerplatform_environment - update domain issue

environment domain validation send incorrect payload during environment update operation

Thanks for looking into this and responding quickly!


Setting default row_limit to null for timeseries charts

This PR sets default row_limit to null for line chart, bar chart, compare chart, and area chart. Because row_limit is a new field on timeseries charts, existing charts may be affected if they have over 10,000 rows.
@mistercrunch what do you think about setting the row_limit default to null? We could also set the default to 50,000 instead, it seems less likely that a chart with 50,000 rows would render very well anyways.

I think we should put some upper limit as people can crash their browser if they don't. The upper limit should be lower than the number at which we know the browser will crash for sure. This may vary quite a bit based on the viz type, number of series, ...
I also think we should allow users to crash their browsers if they want to clear or bump up the limit.
Notice that the label that shows the number or rows in the explore view should turn yellow and warn "you've reached the limit" to make sure users knows that data is missing. We may want to bring more attention to this and have a clear tooltip that explains the tradeoffs.

Here, I've been meaning to do this for a while https://github.com/apache/incubator-superset/pull/6252

Codecov Report

Merging #6244 into master will decrease coverage by 0.1%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #6244      +/-   ##
==========================================
- Coverage   76.85%   76.74%   -0.11%
==========================================
  Files          47       47
  Lines        9393     9393
==========================================
- Hits         7219     7209      -10
- Misses       2174     2184      +10

Impacted Files
Coverage Δ

superset/db_engine_specs.py
54.91% <0%> (-0.85%)
:arrow_down:

superset/connectors/sqla/models.py
80% <0%> (-0.75%)
:arrow_down:

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 af38d25...fd2fcd5. Read the comment docs.

Sounds good thanks Max. I did some testing on what the upper limit should be for different viz types, I think the only one we should increase is the line chart, I set it to 50000. This is still pretty slow but usable. The bar chart and area chart get pretty slow at 10K, they could be a little larger but this seems fine. The compare chart doesn't have a way of hiding the legend so there's no chance anyone is using it even at 10K currently.

+1


Minor UI fixes in back button in new group page

Fixes #
Describe the changes you have made in this PR -
In New Group Page :

Adds text-success to back button.
Shifts Back button to right.

Screenshots of the changes (If any) -
BEFORE

AFTER

@Ananthavijay does that work ??

Coverage remained the same at 84.266% when pulling a1a2adedb56aded14b616b1f0a5bc8449f516d83 on Nitish145:new-group-back-button-issue into 1145c3acff926c1f7f309f6a581c18bac0e3c070 on CircuitVerse:master.


Make it possible to boot from loop-mounted ISO using the FreeBSD boot loader

It would be very useful (not just for helloSystem but in general) if one could boot into ISO files from the FreeBSD boot loader.
https://reviews.freebsd.org/D19733 seems to implement at least the first half of it:

By mapping file, we create vdiskX device,  the device will be listed by lsdev [-v]
and can be accessed directly as ls vdisk0p1:/path or can be used as value for currdev variable.

map-vdisk can be used to loop-mount an ISO and to boot the kernel from it. I tested it and it works great:
map-vdisk aaa.iso # vdisk0 gets created
lsdev -v # shows vdisk0
set currdev=vdisk0:
unset vfs.root.mountfrom
boot -v

starts the kernel that is stored inside the ISO.
This is the first half of the needed functionality.
But then the kernel does not see the vdisk when trying to mount rootfs... is this functionality not implemented yet?
For this, we need the second half of the functionality.
Could it be ported from the ventoy kernel module?
This is what Ventoy seems to be doing in GRUB; can we achieve the same effect using the FreeBSD bootloader? If yes, then the existing Ventoy FreeBSD kernel module could possibly do the rest of the work?
    vtoy_ssprintf(buf, pos, "hint.ventoy.0.disksize=%llu\n", (ulonglong)(disk->total_sectors * (1 << disk->log_sector_size)));
    vtoy_ssprintf(buf, pos, "hint.ventoy.0.diskuuid=\"%s\"\n", uuid);
    vtoy_ssprintf(buf, pos, "hint.ventoy.0.disksignature=%02x%02x%02x%02x\n", disk_sig[0], disk_sig[1], disk_sig[2], disk_sig[3]);
    vtoy_ssprintf(buf, pos, "hint.ventoy.0.segnum=%u\n", g_img_chunk_list.cur_chunk);

    for (i = 0; i < g_img_chunk_list.cur_chunk; i++)
    {
        chunk = g_img_chunk_list.chunk + i;
        vtoy_ssprintf(buf, pos, "hint.ventoy.%u.seg=\"0x%llx@0x%llx\"\n",
            i, (ulonglong)(chunk->disk_start_sector * 512),
            (ulonglong)((chunk->disk_end_sector + 1) * 512));
    }

https://github.com/ventoy/Ventoy/blob/a4200ed99eaae5ec2b3034077d9a5ff461d5e8e8/GRUB2/MOD_SRC/grub-2.04/grub-core/ventoy/ventoy_unix.c#L313

Also @trasz.
I suspect this isn't really feasible with reroot - as I understand it, essentially we need to:

mount a filesystem on the physical device (probably FAT or ISO9660)
create a vnode md from a file in that filesystem
use that md as the root mount

Let's look into how Ventoy is doing it. I think they export certain information in GRUB to well-known memory locations, load the kernel, and then let the Ventoy kernel module pick up the information previously exported. From there on, the Ventoy kernel module does the rest of the work. So it is simply(?) a matter of exporting the same data that Ventoy exports using GRUB. Or so I imagine is how it works, as Ventoy unfortunately seems to be sparsely documented.

Huh, from g_ventoy.h:
#define VENTOY_UNIX_MAX_SEGNUM   40960
struct g_ventoy_seg {
    uint64_t seg_start_bytes;
    uint64_t seg_end_bytes;
};

struct g_ventoy_map{
    uint32_t magic1[4];
    uint32_t magic2[4];
    uint64_t segnum;
    uint64_t disksize;
    uint8_t diskuuid[16];
    struct g_ventoy_seg seglist[VENTOY_UNIX_MAX_SEGNUM];
    uint32_t magic3[4];

so it looks like the Ventoy geom makes use of a map of (up to 40960) byte ranges to translate between image file offsets and offsets in the underlying device -- clever, but it means that some Ventoy component needs to generate those maps (either after the image file is copied to the device, or as part of the boot process prior to FreeBSD starting). AFAICT this won't work with only the loader's vdisk support, without involvement of Ventoy.

That's what I mean - some code would probably have to be added to the bootloader. Not sure whether it could be done by Lua scripting alone.

We do not need UEFI vars or "well known" memory areas - we do have loader environment passed to kernel and we can use that mechanism just fine. The variables can be populated/removed with map/unmap commands, and all the kernel module needs to do, is to pick up the values (just like many other kernel modules are already doing). grub has no mechanism to pass data to loaded kernel, thats why they need alternate mechanisms.
The problem with memory area is, we can not be sure it is actually free and usable. And the problem with UEFI variables is, the variable storage can get fragmented (we need to add, then remove related vars and data) and this can lead to issues with system firmware.

Great. So one would need to:

Write code to compute and export the needed loader variables (can this be done in lua or is this only/better done in C?)
Augment the Ventoy kernel module to (preferably) read and act upon those loader variables

Correct?

I don't object to Ventoy, but would like to see if there's a way we can handle the kernel's side of map-vdisk without relying on Ventoy. (@tsoome I'm curious if you can explain how Illumos made use of this.)
(I'm still unsure if Ventoy generates the offset mapping info on each boot, or it's done as some sort of post-processing step after copying the ISO to the USB stick.)

Great. So one would need to:

Write code to compute and export the needed loader variables (can this be done in lua or is this only/better done in C?)

That depends on what exactly we would need from kernel [module] point of view. By naive approach, I'd guess, the file name could be just enough and if so, it could be done by script which does create mapping.

Augment the Ventoy kernel module to (preferably) read and act upon those loader variables

Correct?

Yes.

I don't object to Ventoy, but would like to see if there's a way we can handle the kernel's side of map-vdisk without relying on Ventoy. (@tsoome I'm curious if you can explain how Illumos made use of this.)
(I'm still unsure if Ventoy generates the offset mapping info on each boot, or it's done as some sort of post-processing step after copying the ISO to the USB stick.)

I am not aware if any illumos distribution is actually using it. Someone was complaining that there is no way to use mapped file, so I did add the feature and did test it is possible to boot from it. However, there is one important difference compared to FreeBSD - in case of illumos, we load kernel and boot archive (as ramdisk), and in case of iso, the boot archive is actually miniroot with set of tools - so all we need to do really in illumos, is to pass mapped file name and device ID, and script the file mapping to disk in userland...

in case of illumos, we load kernel and boot archive (as ramdisk)

Ah, ok - it is possible (but atypical) to do the same in FreeBSD. I just wanted to make sure I wasn't missing something.

I'm still unsure if Ventoy generates the offset mapping info on each boot, or it's done as some sort of post-processing step after copying the ISO to the USB stick.

Presumably a GRUB plugin.
There is no extra step (like running a script) for the user - just copy an ISO onto the Ventoy volume, reboot.


[IPCT1-95] refactor ci

on the last commit "Merge" I've realized that a new type was created in https://github.com/impactMarket/mobile-app/pull/132
nice, but we need something more generic and reusable. I've chosen the more reusable here. Will do another PR to replace the other later.

there are only two things

CI
types fixed

types were fixed because a type check was added and there were errors. To avoid merging with errors (besides tests) I just fixed them. Again, just type changes, no code refactoring anywhere.


Copy Encoding and Decoding library

[x] This contribution adheres to CONTRIBUTING.md.

What does this Pull Request accomplish?
Copies the Encoding and Decoding library from the Ballard ARINC 429 custom device repo.
Why should this Pull Request be merged?
Allows other custom devices to use library.
What testing has been done?
Build locally and verify that library is moved to common output directory for all components within repo. All unit tests run and pass (17/17).

Note to reviewers:
This source was copied from the Ballard ARINC 429 custom device. LabVIEW files were saved for previous (LabVIEW 2018). Tests were run in 2018 and in 2020 and all passed. A build spec was added to the lvproj to create a source distribution and then move it to the common output directory.
Build.toml and Jenkinsfile were modified to add the encoding library to the repo build. Issue #42 was created to capture work to fully integrate error file.


rpc_support: Remove old host packages from containers

Closes-Bug: #845

:+1:

-1 this type of cleanup action has the potential to cause issues. This task is one of the last to run and so has the potential to impact on services by removing packages that are required. While I agree with the intent of this commit the action is too far removed from the playbooks that are written to configure those containers. I think it would be safer to replace the containers than have a separate task blindly modifying them. This task creates an ongoing risk because if any of those containers have one of the listed packages introduced, the rpc-support role will remove them.

have you tested this (just by running though an ansible shell manually)?

yes it removes the packages just fine. Now I have to look why we install lxc, lxc-dev inside containers with https://github.com/openstack/openstack-ansible-repo_server/blob/master/defaults/main.yml#L74

After talking to Kevin, removing debootstrap for now since repo_server was intended to build lxc images but never did

this does need a better commit message, preferably mentioning the manual testing that took place along with proof (of some sort) that each of the removed packages won't be installed again like de-bootstrap would have been.

@prometheanfire This is overkill since we put test protocols in the commit message. It's not worth the effort here, closing it.


Feature Request: Custom Boards

Just to be able to define custom columns, templates. Could be a list of columns with comma separated and create a board based on that.

I've done a lot of work this, it's not live at retro.tools yet, but you can try it out here.
You can click the column icon to open a settings drawer where you can change the name, colour and icon.

You can also delete the column with the trash can icon to the right of the card input box.
To add a column, use the drop down on the top right.

You can have up to 6 columns.
I'm just writting tests and tweaking now, so hopefully it'll be deployed within a few days.
Let me know if you have any feedback!

Deployed :tada:


Add leetcode solution 60 to make this website one stop solution enhancement

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
Add leetcode solution 60 to make this website one stop solution enhancement
Use Case
Add leetcode solution 60 to make this website one stop solution enhancement
Benefits
No response
Add ScreenShots
No response
Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository

@Utsavladia only open 4 issue not large


Support modifying the name of every terminal

VSCode Version: 1.19.0
OS Version: windows 10.0.162299   version 16299

Steps to Reproduce:
Can't modify the name of every terminal

Reproduces without extensions: Yes

@jianzhou520
If I understand your request, rename any terminal to any name,  there is already a command for that:
Terminal: Rename
I don't think there is a default key binding so if you press F1 for the command pallet
then type Terminal and you will see all the terminal commands including rename terminal for the currently active terminal.  You can rename every terminal that way.

That helps. Thanks!


Bring back the 'copy all' from test results panel

Description
VS2017 had a quick link to 'Copy All' from the test results panel, in addition to an 'Output' link which opened the output text in a new tab.
VS2019 instead only has a link to 'Open additional output for this result', and a right-click context option from the test-hierarchy listing to "Copy Details" which only copies the truncated details, necessitating opening the test output in a new tab > right-click > Copy All
Steps to reproduce
Run a test
Expected behavior
Easily-accessible "Copy All" feature.
Actual behavior
Feature no longer obvious, buried behind a context menu, which then doesn't actually do the same thing, thus requiring additional steps anyway.
Environment
Visual Studio 2019
Apologies if this isn't the right place for this 'feature request', I arrived from this VS2019 Test Explorer documentation which suggested this repo for sorting requests.

It is not related to vstest. Please provide your suggestion here : https://developercommunity.visualstudio.com/


Update README: correct reference to circe-scalajs

I believe the parser subproject does not exist (anymore)?

[Current coverage][cc-pull] is 80.49%
[][cc-pull]

No coverage report found for master at c934acf.

Powered by Codecov. Last updated by [c934acf...39ab336][cc-compare]
[cc-base-branch]: https://codecov.io/gh/travisbrown/circe/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/travisbrown/circe/compare/c934acf6bf63db1b3db9ad5d9490d2298af6c938...39ab336dbd0fb8c6b26aa4124a1ad55f4af511ce?src=pr
[cc-pull]: https://codecov.io/gh/travisbrown/circe/pull/328?src=pr

circe-parser is still available—if you check Maven Central you'll find 0.5.0-M2 releases for both the JVM and Scala.js. In many cases you'll want to use circe-jawn or circe-scalajs directly, but if you want 100% shared code and only need the lowest common denominator of the two, circe-parser works.

Ah okay, clear, thanks!


Build customized country group

Hi,
Thanks for the awesome library! Was looking at implementing the phone number formatting and wanted to limit what countries was included in my bundle since I don't need them all.
Following the link below though you seem to be lacking documentation for this.
https://github.com/nosir/libphonenumber-country-metadata#build-phone-type-formatterjs-for-cleavejs
Will be adding more and more countries in the future so would need to do this every now and then and if it can be explained here I would be more than happy to create a PR for updated documentation :)

Hi @perrosen
Seems I didn't add that feature before :p
It's updated now, and the doc is updated with a demo:
https://github.com/nosir/cleave.js/blob/master/doc/phone-lib-addon.md#customize-building

Closing this, feel free to open if you have any problem in generating.


Add --no-auto-update while run scripts/build to disable autoupdate

Add --no-auto-update to script/build as an option to disable Atom autoupdate.
This PR create a new grunt task that set _enableAutoUpdate to Atom's package.json while building. And in AutoupdateManager, it loads package.json and check if _enableAutoupdate is set.
I verified that script/build --no-auto-update will set "_enableAutoUpdate" : false in Atom's package.json whereas script/build will  set "_enableAutoUpdate" : true.
However, it seems that the build generated by script/build won't trigger autoupdate even if I made the the version to be 1.0.9 instead of 1.0.9-somehash.
Any thought on how to verify the autoupdate feature using script/build?
cc @bolinfest  @maxbrunsfeld  @kevinsawicki

I noticed that there is no way to just check the update but not update it without touching electron code.  So I instead disable the periodically check if no-autoupdate is set, whereas user could still click the check update button to trigger autoupdate manually.
Also, do you have any suggestions on how to test that? I tried to hardcode the version number as 1.0.3 instead of something like 1.0.12-hash before building, but the autoupdate just doesn’t do anything.

I tried to hardcode the version number as 1.0.3 instead of something like 1.0.12-hash before building, but the autoupdate just doesn’t do anything.

If the app's version is just 1.x.y, the auto-update should run. What is the output of this command from your built version of Atom?
remote.require("app").getVersion()

What you've done looks good so far. There are a couple of changes I'd like you to make:

[ ] Rather than passing the @resourcePath into the AutoUpdateManager, so that it can read the package.json and possibly disable itself, I would rather pass a boolean disabled flag into the AutoUpdateManager if auto update has been disabled in the package.json, or the version string has a SHA in it.
[ ] When Atom has been built with --no-auto-update, the 'Atom' application menu should not have a Check for Update option. You could add an isDisabled method to AutoUpdateManager that can be checked in ApplicationMenu::getDefaultTemplate.

@maxbrunsfeld  ready for review again.
I still can't trigger autoupdate, here is what I did:

I checkout tag v1.0.13
I apply this patch to v1.0.13 https://github.com/scv119/atom/commit/e9e46f9fbf6c958eaf768ba65f3899651b9d9769
run pkill Atom && rm -rf /Applications/Atom.app
run ./script/build to get Atom.app
open /Applications/Atom.app

Here I verified the version is 1.0.1, but the Check for Update doesn't do anything if I click it.

Here is how I tested:

apply this patch (https://github.com/scv119/atom/commit/32c758b0fafc6a2631e3c609c9b894bcda7b70cd) to the commit.
run ./script/build to get Atom.app
verified that 2015-09-22 11:05:05.692 Atom[93618:5819640] called showed up while starting Atom using atom -f, and this log also showed up when Check for Update is clicked.

However, this didn't actually autoupdate Atom, which I suspect something related to this error Error Downloading Update: Could not get code signature for running application.

run ./script/build --no-auto-update to get Atom.app without autoupdater.
verified that .... called didn't show up while starting Atom using atom -f
verified that Check for Update didn't show up in Atom menu.

Here is how I tested

@scv119 :+1: Ok, that sounds good to me.
We can merge this as soon as you resolve the conflicts.

@maxbrunsfeld  rebased :)

Thanks @scv119!


docs: add simple example for document homepage

Resolve #6854

thanks. can you please resolve the formatting issues ?


Favorite styles for a given page to reference them easily

Until today, I used the "Enable styling..." option to temporarily disable my Stylebot style. This option perhaps had a confusing name, but it was very useful and I made use of it daily.
Now, it seems I must reset the page to see the original. But this is a permanent change. To 'revert' to the styled element, I need to hunt through "Install from social.." to find the original (thankfully I saved my style here, otherwise I believe it would be gone forever?).
It would be nice (a) to have a way to toggle Stylebot on/off for a given page, and/or (b) save 'favorite' styles for a given page to reference them easily. (unless I am missing something?)

there is now an easy way to enable/disable styles for a page from the popup menu


Heroku Slow And Unstable

Hi,
I deployed my dashboard to a Heroku free dyno. I am pinging it every few minutes to make sure it is always alive. My dashboard has 9 jobs, 10 widgets, and runs using Passenger, and seems to be slow to start up on Heroku. About once per day, I get an "Application Error" and need to go back and reload it a few times from my computer, then reset my Chromecast(running via https://github.com/dryan/geckocast). Is this normal? How about OpenShift? I get three free "small gears", would a 2 or 3 gear system be better for Dashing?
Thanks,
ahanmal

Heroku free dynos will spin down if not in use and are generally unreliable. It looks like OpenShift doesn't idle as frequently: http://stackoverflow.com/questions/23795884/how-long-with-no-traffic-before-an-openshift-gear-goes-idle
You may have better luck with some gears... Alternatively, you could run it locally. It doesn't need much processing power, a Raspberry Pi would be lots.


bug: logout button in portal does not work

When clicking the logout button at /auth/portal, I'm getting a 302 redirect back to /auth/portal with /auth?logout=true as initiator. The access token is still present and valid after that.
I think this is because /auth redirects back to /auth/portal when there is a valid token present, regardless of the ?logout=true parameter.

(just blacked out some private urls)

I think this is because /auth redirects back to /auth/portal when there is a valid token present, regardless of the ?logout=true parameter.

@MexHigh , this is a but ... The logout url is "/auth/logout". Previously, I had it ?logout=true.
Are you using the latest template?
https://github.com/greenpau/caddy-auth-portal/blob/main/assets/templates/forms_portal.template
By the way, did you create your own template or do you use default?

By the way, did you create your own template or do you use default?

By default I mean "not specifying template at all". This way it pick one up from memory.

I'm using a slightly modified version of yours. But it may be some versions behind. I'm trying again with newer ones.

Token is still valid. I'm just getting a drifferent redirect chain. Haven't set the template at all in the ui subdirective.

Token is still valid.

@MexHigh, do you still have access_token in your cookies? or do you expect the invalidation of the token previously granted to you?

I actually have two cookies named access_token, one with the correct JWT value and one with delete as content after logging out.
I expect that the logout removes the access_token cookie so that I need to re-authenticate when accessing a ressource secured with jwt.

@MexHigh , I suspect it is because the delete cookie parameters do not match ... I need to refactor the delete.
Could you please show all the fields of the two "access_token"? I think due to the use of domain, they do not clear out.
Will fix that shortly.

@MexHigh , I still need to see the values ... have you tried to clear the tokens completely? Are you using firefox?

@MexHigh , I am pretty sure that the delete token does not have domain included.

I'm using Chrome, because Firefox does not display the delete tokens I'm seeing in Chrome. But I tried both browsers, even the mobile versions of them. I'm using a fresh browser instances every time when testing this (setting a new temporary data directory for chrome using the --user-data-dir flag). I've tried deleting cookies by hand as well.

@MexHigh , I am pretty sure that the delete token does not have domain included.

Chrome displays .example.com on the cookie containing the JWT and example.com (note the missing dot in front) on the delete cookie. So maybe Chrome just displays the affiliation of the cookie.
In Firefox, I don't see any change on the cookies when pressing the logout button.
After clicking the logout button and then accessing a different ressource secured with jwt, I'm only seeing the access_token with the correct JWT value.

I just discovered that the delete token expires at January 1st, 1970. Maybe this could be a problem.

@MexHigh , I just pushed v1.1.1 https://github.com/greenpau/caddy-auth-portal/releases/tag/v1.1.1
When specifying cookie_domain, please put a leading dot ,
cookie_domain .example.com

additional reference: https://stackoverflow.com/questions/9618217/what-does-the-dot-prefix-in-the-cookie-domain-mean#:~:text=The leading dot means that,implementing the deprecated RFC 2109.

Works perfecty now. Even without the leading dot. Thank you.

Works perfecty now. Even without the leading dot. Thank you.

@MexHigh , thank you for testing! 👍
On a separate note, I am planning adding MFA with App/Yubikey/Hardware tokens.
https://github.com/greenpau/caddy-auth-portal#add-mfa-authenticator-application
Would you be interested in testing this feature?

Would you be interested in testing this feature?

Yes, of course. Sounds good.


Revert "New: Tag component"

Reverts Adslot/alexandria#243

[Current coverage][cc-pull] is 100% (diff: 100%)

Merging [#247][cc-pull] into [master][cc-base-branch] will not change coverage

@@           master   #247   diff @@
====================================
  Files          25     24     -1
  Lines         292    273    -19
  Methods        46     43     -3
  Messages        0      0
  Branches       38     34     -4
====================================
- Hits          292    273    -19
  Misses          0      0
  Partials        0      0

[][cc-pull]

Powered by Codecov. Last update [aa3f7aa...ce1e407][cc-compare]
[cc-base-branch]: https://codecov.io/gh/Adslot/alexandria/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/Adslot/alexandria/compare/aa3f7aa4231be4e9a424001ff499e9bea1c0841e...ce1e4074e42a6f797cdae7eca150077296c72141?src=pr
[cc-pull]: https://codecov.io/gh/Adslot/alexandria/pull/247?src=pr