php8 for Debian 11

PHP8 repository for Debian 11 with distribution check.
Solves #174

@staticdev please review

It works now for
Debian 11: https://github.com/aalaesar/install_nextcloud/actions/runs/3796702674/jobs/6457031424#step:7:172
and
Debian 10: https://github.com/aalaesar/install_nextcloud/actions/runs/3796702674/jobs/6457031455#step:7:175

@wiktor2200 if you can also add this change from https://github.com/aalaesar/install_nextcloud/pull/176/files we can close both issues in one merge.

@staticdev I've merged your branch (https://github.com/aalaesar/install_nextcloud/pull/176/files) into this one.

@staticdev I've merged your branch (https://github.com/aalaesar/install_nextcloud/pull/176/files) into this one.

Ah sorry, I just merged it at the same time =/

No problem, I merged your branch into mine, so commits are the same so there will be no conflicts :)


vcpkg install fails to parse CONTROL files (need vcpkg version bumb)

Problem
On systems running an older build of vcpkg vcpkg install throws warnings for any port control file containing the new 'Homepage` field (https://github.com/microsoft/vcpkg/pull/2933) and fails to build those:
vcpkg install ms-gsl:%PLATFORM%-windows
Warning: an error occurred while parsing 'alembic'
...
Warning: an error occurred while parsing 'ms-gsl'
...
Error: Cannot find definition for package `ms-gsl`.

Both on Windows and Linux builds:
TravisCI - Linux
Appveyor - Windows
The problem is that vcpkg v2018.11.23 as build in November 2018 is not compatible with the updated format for the control files used with vcpkg v2018.11.23 build in June 2019.
Without a version bump there is no warning, users have to figure for themselves out that a rebuild is necessary.
As also noted with one of the PR's: https://github.com/microsoft/vcpkg/pull/6844#issuecomment-501625789
Workaround
Rebuild vcpkg: ./bootstrap-vcpkg.bat
Or for CI systems (travis) remove the cache.
Solution
Vcpkg needs a version increase.
To warn users and to get CI systems, that contain an older build (Appveyor) or cache vcpkg, to rebuild vcpkg.

@vicroms Why would you label this as a feature?
The current version is 2018.11.23 and the associated update behaviour* has always been a part of vcpkg.
* When the version is changed users receive a warning message with instructions to rebuild vcpkg.
It used to be that @alexkaratarakis regularly updated the version number and changelog.
Solving the issue by creating a PR for toolsrc/VERSION.txt is easy, but updating CHANGELOG.md with all the changes in the past 7 months ...

Thanks for pointing out this issue!
We do recommend that users always re-run ./bootstrap whenever they change the vcpkg commit. However, for certain changes that we know will cause problems, we do have the warning mechanism that you've mentioned. In this case, we should definitely be using that warning mechanism!
We are currently considering alternative approaches to the CHANGELOG.md file than directly tying it to the version in toolsrc/VERSION.txt; due to that, we would be more than happy to accept a PR just bumping the VERSION.txt :)


stages/oci-archive: write history entries

According to the OCI Image Format Specification history entries for layers in the container are optional; but when trying to push a container quay.io via skopeo (copy oci-archive:… docker://quay) it will fail with "Cannot convert an image with 0 history entries". This seems to come from the containers/image library when the container is converted back from the docker distribution format to oci-archive on quay.io. Thus it seems that when skopeo converts the image to the docker format for the distribution it does not fill any the history entries, which are then assumed and required to be there when converting back.
To fix this, insert history entries for each layer that is created.

@teg @gicmo This PR fixed quay.io uploading issue. And it works with docker.io as well.
Verified on:
osbuild-selinux-27-1.20210329gita96eaf1.20210329gita96eaf1.el8.noarch
python3-osbuild-27-1.20210329gita96eaf1.20210329gita96eaf1.el8.noarch
osbuild-27-1.20210329gita96eaf1.20210329gita96eaf1.el8.noarch
osbuild-composer-core-28.3-1.el8.x86_64
osbuild-composer-28.3-1.el8.x86_64
osbuild-ostree-27-1.20210329gita96eaf1.20210329gita96eaf1.el8.noarch
osbuild-composer-worker-28.3-1.el8.x86_64

Upload to quay.io:
[cloud-user@new-rhel-8-4 ~]$ skopeo copy oci-archive:e4fa3a99-11f4-4035-971c-fbc58c49725c-rhel84-container.tar docker://quay.io/xiaofwan/rhel-edge:latest
Getting image source signatures
Copying blob c00a33b1e994 done
Copying config f4f290da2e done
Writing manifest to image destination
Copying config f4f290da2e [======================================] 471.0b / 471.0b
Writing manifest to image destination
Storing signatures

[cloud-user@new-rhel-8-4 ~]$ sudo podman pull quay.io/xiaofwan/rhel-edge:latest
Trying to pull quay.io/xiaofwan/rhel-edge:latest...
Getting image source signatures
Copying blob c00a33b1e994 done
Copying config f4f290da2e done
Writing manifest to image destination
Storing signatures
f4f290da2ecc190609189ea43003ba32d0f740f4a8e10219d5fa3c252481bd40

[cloud-user@new-rhel-8-4 ~]$ sudo podman images
REPOSITORY                                   TAG     IMAGE ID      CREATED         SIZE
quay.io/xiaofwan/rhel-edge                   latest  f4f290da2ecc  11 minutes ago  1.25 GB

Upload to docker.io
[cloud-user@new-rhel-8-4 ~]$ skopeo copy --dest-creds henrywangxf:hello112233 oci-archive:e4fa3a99-11f4-4035-971c-fbc58c49725c-rhel84-container.tar docker://docker.io/henrywangxf/rhel-edge:latest
Getting image source signatures
Copying blob c00a33b1e994 done
Copying config f4f290da2e done
Writing manifest to image destination
Storing signatures

[cloud-user@new-rhel-8-4 ~]$ sudo podman pull docker.io/henrywangxf/rhel-edge:latest
Trying to pull docker.io/henrywangxf/rhel-edge:latest...
Getting image source signatures
Copying blob c00a33b1e994 [--------------------------------------] 0.0b / 0.0b
Copying config f4f290da2e done
Writing manifest to image destination
Storing signatures
f4f290da2ecc190609189ea43003ba32d0f740f4a8e10219d5fa3c252481bd40

[cloud-user@new-rhel-8-4 ~]$ sudo podman images
REPOSITORY                                   TAG     IMAGE ID      CREATED         SIZE
docker.io/henrywangxf/rhel-edge              latest  f4f290da2ecc  16 minutes ago  1.25 GB
quay.io/xiaofwan/rhel-edge                   latest  f4f290da2ecc  16 minutes ago  1.25 GB

OpenStack broken again. All else is good.


Can't compile on WASM.

My project fails to get compiled at some point.
Clearly, the issue was regarding the mio, which is not supported on web assembly.
so I have checked the dependency tree with cargo tree --target wasm32-unknown-unknown.
├── reqwest-websocket v0.4.4
│   ├── futures-util v0.3.31 (*)
│   ├── reqwest v0.12.9 (*)
│   ├── thiserror v2.0.9
│   │   └── thiserror-impl v2.0.9 (proc-macro)
│   │       ├── proc-macro2 v1.0.92 (*)
│   │       ├── quote v1.0.37 (*)
│   │       └── syn v2.0.90 (*)
│   ├── tokio v1.42.0
│   │   ├── bytes v1.9.0
│   │   ├── mio v1.0.2
│   │   ├── pin-project-lite v0.2.14
│   │   └── tokio-macros v2.4.0 (proc-macro)
│   │       ├── proc-macro2 v1.0.92 (*)
│   │       ├── quote v1.0.37 (*)
│   │       └── syn v2.0.90 (*)
│   ├── tracing v0.1.40 (*)
│   └── web-sys v0.3.76 (*)

It turns out that reqwest-websocket  is the only library try to get mio involved in the dependency tree.
So I would like to know if any one compiles this without error for wasm32 target, is there any thing I should try.

What is the exact error message when compiling? Or is there a way I could reproduce this?
reqwest-websocket for wasm32-unknown-unknown depends on tokio for the queues (mpsc and oneshot) and the tokio::select! macro. The dependency only enables features required for this.
When I run cargo tree I get no mio.
$ cargo tree --target wasm32-unknown-unknown

[...]
├── tokio v1.42.0
│   ├── pin-project-lite v0.2.15
│   └── tokio-macros v2.4.0 (proc-macro)
│       ├── proc-macro2 v1.0.92 (*)
│       ├── quote v1.0.37 (*)
│       └── syn v2.0.90 (*)
[...]

Do you have any other dependencies that might enable a feature with tokio that requires mio? Looks like the features net, process and signal pull in mio.

Thank you for the swift reply.
Here is the error message.
   Compiling wasm-bindgen-backend v0.2.99
   Compiling futures-util v0.3.31
   Compiling futures-channel v0.3.31
   Compiling serde_json v1.0.128
   Compiling memchr v2.7.4
   Compiling bitflags v2.6.0
   Compiling mio v1.0.2
error[E0432]: unresolved import `crate::sys::IoSourceState`
  --> /Users/chanwooahn/.cargo/registry/src/index.crates.io-6f17d22bba15001f/mio-1.0.2/src/io_source.rs:14:5
   |
14 | use crate::sys::IoSourceState;
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^ no `IoSourceState` in `sys`

error[E0432]: unresolved import `crate::sys::tcp`
  --> /Users/chanwooahn/.cargo/registry/src/index.crates.io-6f17d22bba15001f/mio-1.0.2/src/net/tcp/listener.rs:17:17
   |
17 | use crate::sys::tcp::{bind, listen, new_for_addr};
   |                 ^^^ could not find `tcp` in `sys`

error[E0432]: unresolved import `crate::sys::tcp`
  --> /Users/chanwooahn/.cargo/registry/src/index.crates.io-6f17d22bba15001f/mio-1.0.2/src/net/tcp/stream.rs:15:17
   |
15 | use crate::sys::tcp::{connect, new_for_addr};
   |                 ^^^ could not find `tcp` in `sys`

error[E0433]: failed to resolve: could not find `Selector` in `sys`
   --> /Users/chanwooahn/.cargo/registry/src/index.crates.io-6f17d22bba15001f/mio-1.0.2/src/poll.rs:321:18
    |
321 |             sys::Selector::new().map(|selector| Poll {
    |                  ^^^^^^^^ could not find `Selector` in `sys`

error[E0433]: failed to resolve: could not find `event` in `sys`
  --> /Users/chanwooahn/.cargo/registry/src/index.crates.io-6f17d22bba15001f/mio-1.0.2/src/event/event.rs:24:14
   |
24 |         sys::event::token(&self.inner)
   |              ^^^^^ could not find `event` in `sys`

error[E0433]: failed to resolve: could not find `event` in `sys`
  --> /Users/chanwooahn/.cargo/registry/src/index.crates.io-6f17d22bba15001f/mio-1.0.2/src/event/event.rs:38:14
   |
38 |         sys::event::is_readable(&self.inner)
   |              ^^^^^ could not find `event` in `sys`

error[E0433]: failed to resolve: could not find `event` in `sys`
  --> /Users/chanwooahn/.cargo/registry/src/index.crates.io-6f17d22bba15001f/mio-1.0.2/src/event/event.rs:43:14
   |
43 |         sys::event::is_writable(&self.inner)
   |              ^^^^^ could not find `event` in `sys`

error[E0433]: failed to resolve: could not find `event` in `sys`
  --> /Users/chanwooahn/.cargo/registry/src/index.crates.io-6f17d22bba15001f/mio-1.0.2/src/event/event.rs:68:14
   |
68 |         sys::event::is_error(&self.inner)
   |              ^^^^^ could not find `event` in `sys`

error[E0433]: failed to resolve: could not find `event` in `sys`
  --> /Users/chanwooahn/.cargo/registry/src/index.crates.io-6f17d22bba15001f/mio-1.0.2/src/event/event.rs:99:14
   |
99 |         sys::event::is_read_closed(&self.inner)
   |              ^^^^^ could not find `event` in `sys`

error[E0433]: failed to resolve: could not find `event` in `sys`
   --> /Users/chanwooahn/.cargo/registry/src/index.crates.io-6f17d22bba15001f/mio-1.0.2/src/event/event.rs:129:14
    |
129 |         sys::event::is_write_closed(&self.inner)
    |              ^^^^^ could not find `event` in `sys`

error[E0433]: failed to resolve: could not find `event` in `sys`
   --> /Users/chanwooahn/.cargo/registry/src/index.crates.io-6f17d22bba15001f/mio-1.0.2/src/event/event.rs:151:14
    |
151 |         sys::event::is_priority(&self.inner)
    |              ^^^^^ could not find `event` in `sys`

error[E0433]: failed to resolve: could not find `event` in `sys`
   --> /Users/chanwooahn/.cargo/registry/src/index.crates.io-6f17d22bba15001f/mio-1.0.2/src/event/event.rs:173:14
    |
173 |         sys::event::is_aio(&self.inner)
    |              ^^^^^ could not find `event` in `sys`

error[E0433]: failed to resolve: could not find `event` in `sys`
   --> /Users/chanwooahn/.cargo/registry/src/index.crates.io-6f17d22bba15001f/mio-1.0.2/src/event/event.rs:183:14
    |
183 |         sys::event::is_lio(&self.inner)
    |              ^^^^^ could not find `event` in `sys`

error[E0433]: failed to resolve: could not find `event` in `sys`
   --> /Users/chanwooahn/.cargo/registry/src/index.crates.io-6f17d22bba15001f/mio-1.0.2/src/event/event.rs:221:26
    |
221 |                     sys::event::debug_details(f, self.0)
    |                          ^^^^^ could not find `event` in `sys`

error[E0433]: failed to resolve: could not find `tcp` in `sys`
   --> /Users/chanwooahn/.cargo/registry/src/index.crates.io-6f17d22bba15001f/mio-1.0.2/src/net/tcp/listener.rs:105:18
    |
105 |             sys::tcp::accept(inner).map(|(stream, addr)| (TcpStream::from_std(stream), addr))
    |                  ^^^ could not find `tcp` in `sys`

error[E0433]: failed to resolve: could not find `udp` in `sys`
   --> /Users/chanwooahn/.cargo/registry/src/index.crates.io-6f17d22bba15001f/mio-1.0.2/src/net/udp.rs:124:14
    |
124 |         sys::udp::bind(addr).map(UdpSocket::from_std)
    |              ^^^ could not find `udp` in `sys`

error[E0433]: failed to resolve: could not find `udp` in `sys`
   --> /Users/chanwooahn/.cargo/registry/src/index.crates.io-6f17d22bba15001f/mio-1.0.2/src/net/udp.rs:546:14
    |
546 |         sys::udp::only_v6(&self.inner)
    |              ^^^ could not find `udp` in `sys`

error[E0412]: cannot find type `Selector` in module `sys`
   --> /Users/chanwooahn/.cargo/registry/src/index.crates.io-6f17d22bba15001f/mio-1.0.2/src/poll.rs:272:20
    |
272 |     selector: sys::Selector,
    |                    ^^^^^^^^ not found in `sys`

error[E0412]: cannot find type `Selector` in module `sys`
   --> /Users/chanwooahn/.cargo/registry/src/index.crates.io-6f17d22bba15001f/mio-1.0.2/src/poll.rs:728:44
    |
728 |     pub(crate) fn selector(&self) -> &sys::Selector {
    |                                            ^^^^^^^^ not found in `sys`

error[E0412]: cannot find type `Waker` in module `sys`
  --> /Users/chanwooahn/.cargo/registry/src/index.crates.io-6f17d22bba15001f/mio-1.0.2/src/waker.rs:79:17
   |
79 |     inner: sys::Waker,
   |                 ^^^^^ not found in `sys`
   |
help: consider importing one of these structs
   |
1  + use crate::Waker;
   |
1  + use std::task::Waker;
   |
help: if you import `Waker`, refer to it directly
   |
79 -     inner: sys::Waker,
79 +     inner: Waker,
   |

error[E0433]: failed to resolve: could not find `Waker` in `sys`
  --> /Users/chanwooahn/.cargo/registry/src/index.crates.io-6f17d22bba15001f/mio-1.0.2/src/waker.rs:87:14
   |
87 |         sys::Waker::new(registry.selector(), token).map(|inner| Waker { inner })
   |              ^^^^^ could not find `Waker` in `sys`
   |
help: consider importing one of these structs
   |
1  + use crate::Waker;
   |
1  + use std::task::Waker;
   |
help: if you import `Waker`, refer to it directly
   |
87 -         sys::Waker::new(registry.selector(), token).map(|inner| Waker { inner })
87 +         Waker::new(registry.selector(), token).map(|inner| Waker { inner })
   |

error[E0412]: cannot find type `Event` in module `sys`
  --> /Users/chanwooahn/.cargo/registry/src/index.crates.io-6f17d22bba15001f/mio-1.0.2/src/event/event.rs:18:17
   |
18 |     inner: sys::Event,
   |                 ^^^^^ not found in `sys`
   |
help: consider importing this struct through its public re-export
   |
1  + use crate::event::Event;
   |
help: if you import `Event`, refer to it directly
   |
18 -     inner: sys::Event,
18 +     inner: Event,
   |

error[E0412]: cannot find type `Event` in module `sys`
   --> /Users/chanwooahn/.cargo/registry/src/index.crates.io-6f17d22bba15001f/mio-1.0.2/src/event/event.rs:187:55
    |
187 |     pub(crate) fn from_sys_event_ref(sys_event: &sys::Event) -> &Event {
    |                                                       ^^^^^ not found in `sys`
    |
help: consider importing this struct through its public re-export
    |
1   + use crate::event::Event;
    |
help: if you import `Event`, refer to it directly
    |
187 -     pub(crate) fn from_sys_event_ref(sys_event: &sys::Event) -> &Event {
187 +     pub(crate) fn from_sys_event_ref(sys_event: &Event) -> &Event {
    |

error[E0412]: cannot find type `Event` in module `sys`
   --> /Users/chanwooahn/.cargo/registry/src/index.crates.io-6f17d22bba15001f/mio-1.0.2/src/event/event.rs:191:41
    |
191 |             &*(sys_event as *const sys::Event as *const Event)
    |                                         ^^^^^ not found in `sys`
    |
help: consider importing this struct through its public re-export
    |
1   + use crate::event::Event;
    |
help: if you import `Event`, refer to it directly
    |
191 -             &*(sys_event as *const sys::Event as *const Event)
191 +             &*(sys_event as *const Event as *const Event)
    |

error[E0412]: cannot find type `Event` in module `sys`
   --> /Users/chanwooahn/.cargo/registry/src/index.crates.io-6f17d22bba15001f/mio-1.0.2/src/event/event.rs:217:46
    |
217 |             struct EventDetails<'a>(&'a sys::Event);
    |                                              ^^^^^ not found in `sys`
    |
help: consider importing this struct through its public re-export
    |
1   + use crate::event::Event;
    |
help: if you import `Event`, refer to it directly
    |
217 -             struct EventDetails<'a>(&'a sys::Event);
217 +             struct EventDetails<'a>(&'a Event);
    |

error[E0412]: cannot find type `Events` in module `sys`
  --> /Users/chanwooahn/.cargo/registry/src/index.crates.io-6f17d22bba15001f/mio-1.0.2/src/event/events.rs:43:17
   |
43 |     inner: sys::Events,
   |                 ^^^^^^ not found in `sys`
   |
help: consider importing this struct through its public re-export
   |
1  + use crate::Events;
   |
help: if you import `Events`, refer to it directly
   |
43 -     inner: sys::Events,
43 +     inner: Events,
   |

error[E0433]: failed to resolve: could not find `Events` in `sys`
  --> /Users/chanwooahn/.cargo/registry/src/index.crates.io-6f17d22bba15001f/mio-1.0.2/src/event/events.rs:94:25
   |
94 |             inner: sys::Events::with_capacity(capacity),
   |                         ^^^^^^ could not find `Events` in `sys`
   |
help: consider importing this struct through its public re-export
   |
1  + use crate::Events;
   |
help: if you import `Events`, refer to it directly
   |
94 -             inner: sys::Events::with_capacity(capacity),
94 +             inner: Events::with_capacity(capacity),
   |

error[E0412]: cannot find type `Events` in module `sys`
   --> /Users/chanwooahn/.cargo/registry/src/index.crates.io-6f17d22bba15001f/mio-1.0.2/src/event/events.rs:189:47
    |
189 |     pub(crate) fn sys(&mut self) -> &mut sys::Events {
    |                                               ^^^^^^ not found in `sys`
    |
help: consider importing this struct through its public re-export
    |
1   + use crate::Events;
    |
help: if you import `Events`, refer to it directly
    |
189 -     pub(crate) fn sys(&mut self) -> &mut sys::Events {
189 +     pub(crate) fn sys(&mut self) -> &mut Events {
    |

error[E0425]: cannot find value `listener` in this scope
  --> /Users/chanwooahn/.cargo/registry/src/index.crates.io-6f17d22bba15001f/mio-1.0.2/src/net/tcp/listener.rs:76:24
   |
76 |         set_reuseaddr(&listener.inner, true)?;
   |                        ^^^^^^^^ not found in this scope

error[E0425]: cannot find value `listener` in this scope
  --> /Users/chanwooahn/.cargo/registry/src/index.crates.io-6f17d22bba15001f/mio-1.0.2/src/net/tcp/listener.rs:78:15
   |
78 |         bind(&listener.inner, addr)?;
   |               ^^^^^^^^ not found in this scope

error[E0425]: cannot find value `listener` in this scope
  --> /Users/chanwooahn/.cargo/registry/src/index.crates.io-6f17d22bba15001f/mio-1.0.2/src/net/tcp/listener.rs:79:17
   |
79 |         listen(&listener.inner, 1024)?;
   |                 ^^^^^^^^ not found in this scope

error[E0425]: cannot find value `listener` in this scope
  --> /Users/chanwooahn/.cargo/registry/src/index.crates.io-6f17d22bba15001f/mio-1.0.2/src/net/tcp/listener.rs:80:12
   |
80 |         Ok(listener)
   |            ^^^^^^^^ not found in this scope

error[E0425]: cannot find value `stream` in this scope
  --> /Users/chanwooahn/.cargo/registry/src/index.crates.io-6f17d22bba15001f/mio-1.0.2/src/net/tcp/stream.rs:95:18
   |
95 |         connect(&stream.inner, addr)?;
   |                  ^^^^^^ not found in this scope

error[E0425]: cannot find value `stream` in this scope
  --> /Users/chanwooahn/.cargo/registry/src/index.crates.io-6f17d22bba15001f/mio-1.0.2/src/net/tcp/stream.rs:96:12
   |
96 |         Ok(stream)
   |            ^^^^^^ not found in this scope

error[E0425]: cannot find function `set_reuseaddr` in this scope
  --> /Users/chanwooahn/.cargo/registry/src/index.crates.io-6f17d22bba15001f/mio-1.0.2/src/net/tcp/listener.rs:76:9
   |
76 |         set_reuseaddr(&listener.inner, true)?;
   |         ^^^^^^^^^^^^^ not found in this scope

error[E0599]: no method named `register` found for struct `IoSource<std::net::TcpListener>` in the current scope
   --> /Users/chanwooahn/.cargo/registry/src/index.crates.io-6f17d22bba15001f/mio-1.0.2/src/net/tcp/listener.rs:148:20
    |
148 |         self.inner.register(registry, token, interests)
    |                    ^^^^^^^^ method not found in `IoSource<TcpListener>`
    |
   ::: /Users/chanwooahn/.cargo/registry/src/index.crates.io-6f17d22bba15001f/mio-1.0.2/src/io_source.rs:37:1
    |
37  | pub struct IoSource<T> {
    | ---------------------- method `register` not found for this struct
    |
    = help: items from traits can only be used if the trait is implemented and in scope
note: `Source` defines an item `register`, perhaps you need to implement it
   --> /Users/chanwooahn/.cargo/registry/src/index.crates.io-6f17d22bba15001f/mio-1.0.2/src/event/source.rs:75:1
    |
75  | pub trait Source {
    | ^^^^^^^^^^^^^^^^

error[E0599]: no method named `reregister` found for struct `IoSource<std::net::TcpListener>` in the current scope
   --> /Users/chanwooahn/.cargo/registry/src/index.crates.io-6f17d22bba15001f/mio-1.0.2/src/net/tcp/listener.rs:157:20
    |
157 |         self.inner.reregister(registry, token, interests)
    |                    ^^^^^^^^^^ method not found in `IoSource<TcpListener>`
    |
   ::: /Users/chanwooahn/.cargo/registry/src/index.crates.io-6f17d22bba15001f/mio-1.0.2/src/io_source.rs:37:1
    |
37  | pub struct IoSource<T> {
    | ---------------------- method `reregister` not found for this struct
    |
    = help: items from traits can only be used if the trait is implemented and in scope
note: `Source` defines an item `reregister`, perhaps you need to implement it
   --> /Users/chanwooahn/.cargo/registry/src/index.crates.io-6f17d22bba15001f/mio-1.0.2/src/event/source.rs:75:1
    |
75  | pub trait Source {
    | ^^^^^^^^^^^^^^^^

error[E0599]: no method named `deregister` found for struct `IoSource<std::net::TcpListener>` in the current scope
   --> /Users/chanwooahn/.cargo/registry/src/index.crates.io-6f17d22bba15001f/mio-1.0.2/src/net/tcp/listener.rs:161:20
    |
161 |         self.inner.deregister(registry)
    |                    ^^^^^^^^^^ method not found in `IoSource<TcpListener>`
    |
   ::: /Users/chanwooahn/.cargo/registry/src/index.crates.io-6f17d22bba15001f/mio-1.0.2/src/io_source.rs:37:1
    |
37  | pub struct IoSource<T> {
    | ---------------------- method `deregister` not found for this struct
    |
    = help: items from traits can only be used if the trait is implemented and in scope
note: `Source` defines an item `deregister`, perhaps you need to implement it
   --> /Users/chanwooahn/.cargo/registry/src/index.crates.io-6f17d22bba15001f/mio-1.0.2/src/event/source.rs:75:1
    |
75  | pub trait Source {
    | ^^^^^^^^^^^^^^^^

   Compiling keyboard-types v0.7.0
error[E0308]: mismatched types
   --> /Users/chanwooahn/.cargo/registry/src/index.crates.io-6f17d22bba15001f/mio-1.0.2/src/net/tcp/listener.rs:237:9
    |
237 | /         unsafe {
238 | |             #[cfg(any(unix, target_os = "hermit", target_os = "wasi"))]
239 | |             {
240 | |                 net::TcpListener::from_raw_fd(listener.into_raw_fd())
...   |
245 | |             }
246 | |         }
    | |_________^ expected `TcpListener`, found `()`

error[E0599]: no method named `register` found for struct `IoSource<std::net::TcpStream>` in the current scope
   --> /Users/chanwooahn/.cargo/registry/src/index.crates.io-6f17d22bba15001f/mio-1.0.2/src/net/tcp/stream.rs:330:20
    |
330 |         self.inner.register(registry, token, interests)
    |                    ^^^^^^^^ method not found in `IoSource<TcpStream>`
    |
   ::: /Users/chanwooahn/.cargo/registry/src/index.crates.io-6f17d22bba15001f/mio-1.0.2/src/io_source.rs:37:1
    |
37  | pub struct IoSource<T> {
    | ---------------------- method `register` not found for this struct
    |
    = help: items from traits can only be used if the trait is implemented and in scope
note: `Source` defines an item `register`, perhaps you need to implement it
   --> /Users/chanwooahn/.cargo/registry/src/index.crates.io-6f17d22bba15001f/mio-1.0.2/src/event/source.rs:75:1
    |
75  | pub trait Source {
    | ^^^^^^^^^^^^^^^^

error[E0599]: no method named `reregister` found for struct `IoSource<std::net::TcpStream>` in the current scope
   --> /Users/chanwooahn/.cargo/registry/src/index.crates.io-6f17d22bba15001f/mio-1.0.2/src/net/tcp/stream.rs:339:20
    |
339 |         self.inner.reregister(registry, token, interests)
    |                    ^^^^^^^^^^ method not found in `IoSource<TcpStream>`
    |
   ::: /Users/chanwooahn/.cargo/registry/src/index.crates.io-6f17d22bba15001f/mio-1.0.2/src/io_source.rs:37:1
    |
37  | pub struct IoSource<T> {
    | ---------------------- method `reregister` not found for this struct
    |
    = help: items from traits can only be used if the trait is implemented and in scope
note: `Source` defines an item `reregister`, perhaps you need to implement it
   --> /Users/chanwooahn/.cargo/registry/src/index.crates.io-6f17d22bba15001f/mio-1.0.2/src/event/source.rs:75:1
    |
75  | pub trait Source {
    | ^^^^^^^^^^^^^^^^

error[E0599]: no method named `deregister` found for struct `IoSource<std::net::TcpStream>` in the current scope
   --> /Users/chanwooahn/.cargo/registry/src/index.crates.io-6f17d22bba15001f/mio-1.0.2/src/net/tcp/stream.rs:343:20
    |
343 |         self.inner.deregister(registry)
    |                    ^^^^^^^^^^ method not found in `IoSource<TcpStream>`
    |
   ::: /Users/chanwooahn/.cargo/registry/src/index.crates.io-6f17d22bba15001f/mio-1.0.2/src/io_source.rs:37:1
    |
37  | pub struct IoSource<T> {
    | ---------------------- method `deregister` not found for this struct
    |
    = help: items from traits can only be used if the trait is implemented and in scope
note: `Source` defines an item `deregister`, perhaps you need to implement it
   --> /Users/chanwooahn/.cargo/registry/src/index.crates.io-6f17d22bba15001f/mio-1.0.2/src/event/source.rs:75:1
    |
75  | pub trait Source {
    | ^^^^^^^^^^^^^^^^

error[E0308]: mismatched types
   --> /Users/chanwooahn/.cargo/registry/src/index.crates.io-6f17d22bba15001f/mio-1.0.2/src/net/tcp/stream.rs:419:9
    |
419 | /         unsafe {
420 | |             #[cfg(any(unix, target_os = "hermit", target_os = "wasi"))]
421 | |             {
422 | |                 net::TcpStream::from_raw_fd(stream.into_raw_fd())
...   |
427 | |             }
428 | |         }
    | |_________^ expected `TcpStream`, found `()`

error[E0599]: no method named `register` found for struct `IoSource<std::net::UdpSocket>` in the current scope
   --> /Users/chanwooahn/.cargo/registry/src/index.crates.io-6f17d22bba15001f/mio-1.0.2/src/net/udp.rs:624:20
    |
624 |         self.inner.register(registry, token, interests)
    |                    ^^^^^^^^ method not found in `IoSource<UdpSocket>`
    |
   ::: /Users/chanwooahn/.cargo/registry/src/index.crates.io-6f17d22bba15001f/mio-1.0.2/src/io_source.rs:37:1
    |
37  | pub struct IoSource<T> {
    | ---------------------- method `register` not found for this struct
    |
    = help: items from traits can only be used if the trait is implemented and in scope
note: `Source` defines an item `register`, perhaps you need to implement it
   --> /Users/chanwooahn/.cargo/registry/src/index.crates.io-6f17d22bba15001f/mio-1.0.2/src/event/source.rs:75:1
    |
75  | pub trait Source {
    | ^^^^^^^^^^^^^^^^

error[E0599]: no method named `reregister` found for struct `IoSource<std::net::UdpSocket>` in the current scope
   --> /Users/chanwooahn/.cargo/registry/src/index.crates.io-6f17d22bba15001f/mio-1.0.2/src/net/udp.rs:633:20
    |
633 |         self.inner.reregister(registry, token, interests)
    |                    ^^^^^^^^^^ method not found in `IoSource<UdpSocket>`
    |
   ::: /Users/chanwooahn/.cargo/registry/src/index.crates.io-6f17d22bba15001f/mio-1.0.2/src/io_source.rs:37:1
    |
37  | pub struct IoSource<T> {
    | ---------------------- method `reregister` not found for this struct
    |
    = help: items from traits can only be used if the trait is implemented and in scope
note: `Source` defines an item `reregister`, perhaps you need to implement it
   --> /Users/chanwooahn/.cargo/registry/src/index.crates.io-6f17d22bba15001f/mio-1.0.2/src/event/source.rs:75:1
    |
75  | pub trait Source {
    | ^^^^^^^^^^^^^^^^

error[E0599]: no method named `deregister` found for struct `IoSource<std::net::UdpSocket>` in the current scope
   --> /Users/chanwooahn/.cargo/registry/src/index.crates.io-6f17d22bba15001f/mio-1.0.2/src/net/udp.rs:637:20
    |
637 |         self.inner.deregister(registry)
    |                    ^^^^^^^^^^ method not found in `IoSource<UdpSocket>`
    |
   ::: /Users/chanwooahn/.cargo/registry/src/index.crates.io-6f17d22bba15001f/mio-1.0.2/src/io_source.rs:37:1
    |
37  | pub struct IoSource<T> {
    | ---------------------- method `deregister` not found for this struct
    |
    = help: items from traits can only be used if the trait is implemented and in scope
note: `Source` defines an item `deregister`, perhaps you need to implement it
   --> /Users/chanwooahn/.cargo/registry/src/index.crates.io-6f17d22bba15001f/mio-1.0.2/src/event/source.rs:75:1
    |
75  | pub trait Source {
    | ^^^^^^^^^^^^^^^^

error[E0308]: mismatched types
   --> /Users/chanwooahn/.cargo/registry/src/index.crates.io-6f17d22bba15001f/mio-1.0.2/src/net/udp.rs:713:9
    |
713 | /         unsafe {
714 | |             #[cfg(any(unix, target_os = "hermit", target_os = "wasi"))]
715 | |             {
716 | |                 net::UdpSocket::from_raw_fd(socket.into_raw_fd())
...   |
721 | |             }
722 | |         }
    | |_________^ expected `UdpSocket`, found `()`

Some errors have detailed explanations: E0308, E0412, E0425, E0432, E0433, E0599.
For more information about an error, try `rustc --explain E0308`.
error: could not compile `mio` (lib) due to 47 previous errors
warning: build failed, waiting for other jobs to finish...

I haven't went through a couple more test.
It seems like it's not in single library introducing mio into the dependency graph.
Rather, it is combination of couple libraries
[dependencies]
...
dioxus = { version = "0.6.0", features = ["router"] }
reqwest = { version = "0.12", default-features = false }
reqwest-websocket = "0.4.4"
# ! Only macros and sync are supported in WASM
tokio = { version = "1.16.1", features = ["macros", "sync"] }
...

Here are some of the relevant dependencies.
reqwest or reqwest-websocket alone does not introduce mio in to the dependency graph, but it seems having both does.
It is the same for tokio and request as well.
Can you reproduce this? or is this just on me?

What does cargo tree --target wasm32-unknown-unknown -i -p mio say?

mio v1.0.2
└── tokio v1.42.0
    └── reqwest-websocket v0.4.4
        └── merc-client v0.1.0 (/Users/chanwooahn/Documents/dev/rust/merc/merc-client)

Here it goes!

Hmm, I really don't understand why it's pulling in mio. But I noticed that your crate doesn't appear in that dependency tree, even though it depends on tokio. You're using tokio 1.16. Have you tried using a newer version? This should not be an issue, but I'm honestly out of ideas.

I understand.
This looks weird for me as well. I am trying to make a new crate and find the exact condition of issue.
Will let you know if I find any :)

It seems like workspace does have effect between crates.
I have manage to build working crate on bare-bone project.
However, when I copy and paste all into the problematic workspace, it failed.
So it seems nothing wrong with you crate.
I appreciate your rapid response though. :)

A bit off topic, but unfortunately I change the web sockets crate to ws_stream_wasm because it support Stream with Sync. If there is any way to make your implementation support Sync it would be awesome.

All dependencies are shared in a workspace, so if another crate in your workspace enables a mio-related feature for tokio that would affect your client crate as well. Although the dependencies are separate per target.
I started a PR a while ago that would make the wasm websocket Send + Sync, but I never got around finishing it. I appreciate the feedback.


Ignore updates from all Wikidata domains

In production there are www.wikidata.org and test.wikidata.org. We want
to ignore both of them when it comes to updates.
Bug: T149114

cc @wikimedia/services

Coverage remained the same at 93.117% when pulling 979e86b2b37bfff6272df514af7fcf40452cf61b on d00rman:remove-wikidata into d75a478bfc6914b38e060ec55828f94f17ab7336 on wikimedia:master.

Self-merging to deploy right now.


Security Groups should not be enabled when creating an Open vSwitch network

Author Name: Jaime Melis (@jmelis)
Original Redmine Issue: 5561, https://dev.opennebula.org/issues/5561
Original Date: 2017-11-17

Currently the Security Groups tab is disabled when the user selects a vCenter network. The same thing should happen with Open vSwitch.

master + one-5.4. 5.4.6 release notes updated


[Question] Pre-computed unconditional embeddings

I noticed that the assets folder contains some pre-computed embeddings that function as the unconditional input. Were these computed similarly to how the graido app uses black images to provide the unconditional embedding?

Although we provide assets/clip_ug.pth, we didn't actually use that. The UG for prompt-free diffusion is all zeros vectors.
But prompt-free is totally fine with traditional UG (i.e. negative prompts), you may try use it. Our experience shows little improvement.
The anime app, however, assets/anime_ug.pth provided improvement in results, so we apply that in the app.


You should explain...

There are several "random word" packages on npm that randomly choose a word from a dictionary.  You should explain better that your package is different -- that it makes up new words that don't exist -- because it's not obvious right away.  Specifically when you say that it "returns a random word" -- that does not make it obvious -- it sounds like you are doing what the others do.  Also, give more than one example output in your description -- a single made-up word is not immediately distinguishable from a randomly chosen dictionary word ( it might be a real word that I just don't know ) -- but a whole list of them would give a more correct impression.   Anyway, thanks for the package -- cool stuff.

Thanks, I've added some docs to the README.md for this in #8 .


Set instance name while starting

Running limactl start foo.yml automatically sets the instance name to foo. It would be nice to be able to set a name different than the file name. Ex. running limactl start foo.yml --name bar would create an instance named bar.

Probably one of the other KEY to override when using the same YAML to spin other VM would be SSH port, I know that muddles the context of this issue but this name override feature won't be usable till that is addressed too IMO

I still feel very strongly that the instance name does not belong in lima.yaml, and is different from all the other settings. It serves no purpose in there, as you can only access it if you already know the instance name. Just like you don't store the name of the file inside the file, or the name of a database table inside the table. It would just be redundant information that can get out of sync with reality.
That said, I am very interested in having --set supported, especially if it can be used to change settings on an existing instance (like the cpu and memory settings). We discussed some of this before in #131.  I was planning to look into the helm code that implements their --set command, but I think it was not a good fit, as their values.yaml doesn't have any kind of schema.

We can have --name NAME and revisit --set KEY=VAL later.

Also, while we should deprecate limactl start NEW_INSTANCE_NAME, we should keep limactl start EXISTING_INSTANCE_NAME permanently.

Yes, that's essentially what I suggested, except I want limactl start NEW_INSTANCE_NAME to throw an error, so I can recall the command and append --from-default or --from URL.
I have further suggestions to refine the --from argument, but I don't want to complicate the discussion about the basic syntax just yet. 😄

Maybe --set-name to clarify that this flag is only for new instances?

I find it inconsistent that for new instances the URL is the required argument, but for existing ones it is the NAME. I think it should always be the same. Otherwise it should be a different command limactl create URL --set-name NAME. But I still prefer limactl start NAME --from URL|FILE.
Of course --from (and --from-default) will throw an error if the instance already exists.
Again, if --from doesn't work for you, then maybe --template or --config is better, although personally I've now grown fond of --from.

Ok, I'm still going to mention it: there are 2 additional template locations I would like to see supported:

lima.yaml of existing instances
examples stored in /usr/local/share/doc/lima/examples

So I think limactl start foo --from bar should use $LIMA_HOME/bar/lima.yaml as the template.
I don't have a suggestion yet how to create a shortcut syntax for the examples folder that is not ambiguous with any of our existing URL/file schemes. We could invent a fake URL prefix, but I don't like that either.

I find it inconsistent that for new instances the URL is the required argument, but for existing ones it is the NAME. I think it should always be the same. Otherwise it should be a different command limactl create URL --set-name NAME. But I still prefer limactl start NAME --from URL|FILE.

We already limactl start FILE and I assume we want to keep it, so I think we can just extend it to support limactl start URL

So I think limactl start foo --from bar should use $LIMA_HOME/bar/lima.yaml as the template.

I'd prefer to have "copy-instance" command for that.
limactl copy-instance --refresh-disk=(true|false) PARENT CHILD

Renaming existing machines would also be useful. As far as I can tell, there currently is no way to do that (not even mv ~/.lima/machine1 ~/.lima/machine2, that breaks the machine). Should renaming be tracked in a separate ticket?

Yes, renaming is a separate feature

Implemented in https://github.com/lima-vm/lima/pull/674


Permission::groupList is never cached

Affected Version
4.13+
Description
Permission::groupList use under the hood $member->Groups(). It's not very efficient, as the code comment said itself, but it's supposed to be cached per session. But the cache is only read when you don't pass an argument... which don't seem to be the case.
and caching itself is only done IF there are no argument passed
(and as a side note, it's using the raw $_SESSION global var which is not ideal)
Calls to groupList
https://github.com/silverstripe/silverstripe-framework/blob/0c40cc9b3d9658ad868c560059c88255d2ee0674/src/Security/Permission.php#L211
https://github.com/silverstripe/silverstripe-framework/blob/0c40cc9b3d9658ad868c560059c88255d2ee0674/src/Security/Permission.php#L287
groupList itself
https://github.com/silverstripe/silverstripe-framework/blob/0c40cc9b3d9658ad868c560059c88255d2ee0674/src/Security/Permission.php#L330-L347
Steps to Reproduce
Check the queries. In happens on each request.
PRs

https://github.com/silverstripe/silverstripe-framework/pull/10836

Have closed PR on this one, want be proceeding sorry

@emteknetnz @GuySartorelli
no issue at not using cache, but then i think the comment in the code should be updated somehow
// NOTE: This isn't efficient; but it's called once per session so
// it's a low priority to fix.
=> which is not true, because the method is never called by the framework without argument


[Bug] Mobile tag query with wildcard displays no results

On the iOS app, When I query for a tag using wildcards (say tag:#victuals/food* for example) in the interactive map, no results are displayed on the map.
The query works as expected on desktop.

Hi, I can't recreate this, but I'm using Android and don't have any iOS devices :-/
Can you try to investigate a little further and see if there are specific combinations that work or don't work, e.g. does it work without the slash, or do wildcards work in marker icon rules set by the configuration?


Repo tool continues when log in is declined.

Dev Home version
No response
Windows build number
No response
Other software
No response
Steps to reproduce the bug

Go to repo tool
Click account
Open up oauth prompt
decline log in

Dev home continues to the "Add via account" page.
Putting something in the filter text box crashes the app.
Expected result
Dialog does not move forward.
Actual result
Went to "Add via account" screen with no repos to select.
Included System Information
No response
Included Extensions Information
No response

Fixed in PR #2641


Looping over all district teams is really slow

It'd be way more efficient to either just get the matches for each division, or only use the teams that are actually at worlds.  😅

Closed by 5a5274d66f16be3b5df016d15afa4621e4cf8d6f


Camera.ImageArray Base64 Handoff Mode

First off, thank you so much for your work on this library! It is MUCH MUCH better than writing all the puts and gets out for a telescope control system.
I have one question about the camera module. Has the Base64 handoff mode been implemented when getting image arrays? I'm using this library with the Remote Server, and I believe this would make a difference in my overheads.
Thank you!
-Carson

Hi Carson -- My apologies for not replying sooner. Base64 Handoff was one of the schemes that was being tried back in 2019, see Alpaca ImageArray Performance Over Loopback. This was eventually replaced with Peter Simpson's ImageBytes High Speed Image Transfer Protocol. See the latest Alpaca API Reference V9 (May 2023 - PDF) available at the ASCOM Web Site Documentation Center..  Alpyca handles this transparently, via detecting the HTTP content-type in the camera's image data that comes into Alpyca.  ASCOM Remote automatically converts the ASCOM COM ImageData to ImageBytes so a camera on a Windows system with a Windows ASCOM COM driver will automatically  benefit from ImageBytes. A native Alpaca camera driver would want to provide ImageBytes  not a JSON based blob. Alpyca will accept the JSON as well (again by content-type).  You can see this in action by looking in Camera.py, line 1569 or so, _get_imagedata().


[LORO-303] Allow users to control the timestamp interval to merge change automatically

null
LORO-303

Done


jetson-xavier-nx-devkit: Add PNG images for this device type

Images are the only part that is missing for this
device type, let's add them.
Change-type: patch
Signed-off-by: Alexandru Costache<EMAIL_ADDRESS>Connects to:

https://github.com/balena-io/docs/issues/1624
https://github.com/balena-io/docs/pull/1825#issuecomment-822486220

@balena-ci rebase

@vipulgupta2048 this logo has Xavier on it, the other has Nano..

🤦🏼 Couldn't see it because of dark mode ...


v3 droplet copy acceptance test failing for NFS fog

Issue
Running cf-release acceptance tests while upgrading to release 278 I noticed that the v3 droplet copy integration test was failing.
Context
Here is the error output from the test:
[v3] droplet features copying a droplet [It] can copy a droplet
/var/vcap/packages/acceptance-tests/src/github.com/cloudfoundry/cf-acceptance-tests/v3/droplet.go:86

  Saw:
      {
         "guid": "bb2aee32-30ae-4655-bc2d-2ab25429ffb9",
         "state": "FAILED",
         "error": "failed to copy - Permission denied @ rb_sysopen - /var/vcap/nfs/shared/cc-droplets/bb/2a/bb2aee32-30ae-4655-bc2d-2ab25429ffb9/e1ad2fb40551aad403289e11cddb9f310830364a",
         "lifecycle": {
            "type": "buildpack",
            "data": {}
         },
         "checksum": null,
         "buildpacks": [
            {
               "name": "ruby_buildpack",
               "detect_output": null
            }
         ],
         "stack": "cflinuxfs2",
         "image": null,
         "execution_metadata": "",
         "process_types": {
            "console": "bundle exec irb",
            "rake": "bundle exec rake",
            "web": "bundle exec rackup config.ru -p $PORT",
            "worker": "bundle exec rackup config.ru -p $PORT"
         },
         "created_at": "2017-10-20T20:09:14Z",
         "updated_at": "2017-10-20T20:09:15Z",
         "links": {
            "self": {
               "href": "https://cf.domain/v3/droplets/bb2aee32-30ae-4655-bc2d-2ab25429ffb9"
            },
            "package": null,
            "app": {
               "href": "https://cf.domain/v3/apps/42c742ba-ac85-4c27-872e-26f216923b8a"
            },
            "assign_current_droplet": {
               "href": "https://cf.domain/v3/apps/42c742ba-ac85-4c27-872e-26f216923b8a/relationships/current_droplet",
               "method": "PATCH"
            }
         }
      }

  Which matches the unexpected:
      FAILED

  /var/vcap/packages/acceptance-tests/src/github.com/cloudfoundry/cf-acceptance-tests/helpers/v3_helpers/v3.go:389

Checking in my CC the destination droplet is read only.
Steps to Reproduce
Try to run the v3 droplet copy test against NFS blobstore in cf-release 278
Expected result
Tests should pass
Current result
Tests Fail
Possible Fix
Perhaps droplets need to be made rw similar to the recent staging buildpack fix?
If you cannot duplicate LMK and I'll dig deeper.

@youngm We've had a couple reported NFS issues come up recently. We've got a story coming up to get a CI env setup with NFS: https://www.pivotaltracker.com/story/show/150375975. Once that's done we can dig a little deeper into this issue.

We've been working on getting our permanent CI-ed NFS test environment set up in #150375975. While doing that we saw several CATS failures around them and didn't realize that this issue had already been submitted here at the time.
Anyways, we've been working on this particular issue in #153418863 and commit https://github.com/cloudfoundry/cloud_controller_ng/commit/dc3ef641964f6488062141d5191440bbdb69cffc should address it. In the case of copying a droplet, having them be read only on the mounted NFS volume is okay because we're just reading an existing droplet and copying it over to create a brand new droplet. The reason why this endpoint was failing was due to the save in these lines. Setting public on a fog-local File doesn't actually do anything so we could safely omit it and the call to save.
Just as a heads up, we've also got another story around NFS CATS failures in flight and a PR to the CATS themselves https://github.com/cloudfoundry/cf-acceptance-tests/pull/257.
Thanks for reporting this @youngm!

Thanks @tcdowney I'm really excited you now how a CIed NFS test environment.  This is great.


Is it possible to create a master-detail form?

Let's say, like a user form as main form and addresses as a detail form allowing more than one address for each user.

If I understand well, your need is to create users, and associate multiple addresses to each user ?
I added an example to this repo: https://github.com/lovasoa/SQLpage/tree/main/examples/nested-forms
Does this solve your problem ?
How do you think the documentation could be improved to make this easier to discover ?

I will move this to the discussions forum, where it is easier to discuss ideas around the project then in issues.


security/acme-client Add Ability to Retrieve SSL Certificates via REST API

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:
[x] I have read the contributing guide lines at https://github.com/opnsense/plugins/blob/master/CONTRIBUTING.md
[x] I have searched the existing issues and I'm convinced that mine is new.
[x] When the request is meant for an existing plugin, I've added its name to the title.
Describe the solution you'd like
I would find it extremely useful to be able to extract both the private key and the actual certificate via the REST API that currently exists.
One option could be that on this endpoint that currently exists:
/acmeclient/certificates/get/:id
We get the cert/key content included in the response. Or if we don't want that too cluttered, we could do something like:
/acmeclient/certificates/get/:id/key
/acmeclient/certificates/get/:id/cert
And the response contains this specific information.
To me this provides greater flexibility vs the SFTP option that's currently available for when a certificate is renewed. It makes it so I only have to worry about looking in one place that's more dependably online that other hosts.
Describe alternatives you've considered
I know some alternatives that more or less already exist are:

SFTP via Automation Actions post-renewal
Straight up pulling the cert off the OpnSense host via SSH/SFTP myself.

@Shackelford-Arden Thanks for the detailed description. I agree that it would be useful to retrieve certs/keys via API. However, I don't think this should be added to the ACME plugin (or any other OPNsense plugin).
The ACME plugin uses the OPNsense cert manager to expose certs/keys for use in other applications. So I think the correct way to implement this would be to add API support to the OPNsense cert manager instead.
That being said, the OPNsense cert manager is still legacy code and I think it would first need a rewrite to convert it to OPNsense's MVC framework. AFAIK, there's currently nobody working on this.
I'll close this issue, because it is pretty unlikely that this will be implemented in the near future. However, I'll add the "help wanted" label, because code contributions could of course make a huge difference and probably change priorities too. :)


Feature/dot 303 make profile view responsive

Closes: #...
Checklist

[x] I have made the ProfileLayout responsive
[x] I have made the ProfileLanding responsive

Changelog

Changed ProfileLayout to display navbar in dropdown on smaller screens
Made ProfileLayout and ProfileLanding responsive
Changed StudentProgress to resize when on smaller screens

How to test

Run monoweb
Navigate to /profile
Resize the window

cursed conflicts. thats a lot


Update service-embed-report-microsoft-teams.md

Removed a typo. There is not such thing as Power BI BOT service.  @LukaszPawlowski-MS

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

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

@LukaszPawlowski-MS - Could you review this pull request? Thanks.

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

#sign-off


fixes travis config node versions

I mean, maybe. Just checking to see if quotes make a difference.
Going from the logs, Travis seems to be using node 0.10.33 right
now.

Travis?


Push / native / system notifications

The topic "native Android push notifications" popped up in several issues in the last few days: e.g. #870, #865, #725, #7, #858, #79, #259.
I posted my thoughts in several of them, but as this tends to hijack the actual feature discussion, I wanted to centralize that information in one place:
Native push notifications would certainly be a nice technical feature and could greatly enhance some functionality. But they pose some very serious challanges:

Server Side Component
Unfortunately, native notifications require a server side component that a) either polls for new "messages" on Mediawiki or b) is informed about new "messages" by MediaWiki. It also requires a "database" of "push tokens" that are connected to user accounts (unless this can somehow be added to the mediawiki user account) and are used by the serer component to send the notification to the actual device. (It gets more complicated when a user has multiple devices.)

Google Play Services
As far as I know the only battery friendly way to support push notifications on Android is using GCM/FCM which is implemented via Google Play Services on the device. From what I read in the past, this might be a problem for the project because of licence / Open Source rules reasons.

Does one of the official Wikipedia apps have push notifications? I would like to look into how they implemented this...
Alternatives to proper push notifications include a) local notifications (where the app or a service trigger a notification to be generated themselves, looks identical to push but happens all on the device) or a b) "pull notification" system which works similar to e.g. the Facebook feed where you have to refresh a list of messages to get new messages (or which gets refreshed automatically when the app is started or running).

Thanks for creating this thread, @janpio - definitely useful to have a centralized issue for discussing this.

We recently moved away from FCM for a small set of push "notifications" at my workplace. For this we used Socket.IO to maintain an active socket connection in the background between the client and the server. And while the system works just fine we haven't really been able to match the delivery success rate that we get on FCM, primarily cause keeping the background service running all the time to maintain the socket connection active is a major problem in itself.
That said, I just learned that the Wikipedia Android app is open source as well! I just had a quick look into their repository and it looks like they are using some kind of polling mechanism, although I haven't made enough sense of it yet. We could get some learnings from that and use them here.

Does one of the official Wikipedia apps have push notifications? I would like to look into how they implemented this..

I guess you missed my comment on #725.

Actually the Wikipedia android app uses notifications to notify the user about a reverted edit (sounds similar to "proposed deletion", doesn't it?). So I thought you could do something similar.

This seems like quite a well documented request; do we know whether it was implemented?
Chris.


Compile where fails

I need to fix query because where was compiled as:
DELETE FROM `usuario_observadores` WHERE `id_usuario` = '1' AND id_observador `NOT` IN('3')

Compile put bracket on NOT and not in id_observador field
I'm using grocery_crud, relating fields with relation_n_n.
My fix:
https://github.com/avdata99/medusapp/commit/495364bce3e96e8fb3dab04791b3549a09c11587

What's the QB code that resulted in this query?

Some example:
  [0] => Array ( [condition] => id_usuario = '5' [escape] => 1 )
  [1] => Array ( [condition] => AND id_observador NOT IN('4') [escape] => 1 ) )

Just FYI, that was not what I asked for and barely helped ... I have to know how the query builder methods are called, not what they result in.


Section 5 What can be expected from alchemical simulations

@davidlmobley I think it would be great if Huafeng could write part of this section. I will email him separately, but just putting it here so that I remember.

Took a pass at this in Overleaf. I'll also e-mail Huafeng.

Thank you!

Is more needed on this @ppxasjsm or are we in OK shape here? LMK if you need me to either nag Huafeng or take another pass.

Will let you know if more is required here.


yabridge, yabridgectl: 3.1.0 → 3.2.0

Motivation for this change
Update to the latest version: https://github.com/robbert-vdh/yabridge/releases/tag/3.2.0
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 121715 run on x86_64-linux 1

2 packages built:

yabridge
yabridgectl

Result of nixpkgs-review pr 121715 at 01ec0514 run on x86_64-linux 1

2 packages built successfully:

yabridge
yabridgectl

1 suggestion:

warning: missing-phase-hooks
installPhase should probably contain runHook preInstall and runHook postInstall.
Near pkgs/tools/audio/yabridge/default.nix:121:3:
    |
121 |   installPhase = ''
    |   ^


Increased testing ability

Added some grunt tasks for testing, mainly to check coverage (with karma:coverage) and to run the tests continuously during development (with karma:dev).
Also added a jshint task and fixed a few small styling issues that were raised.
Finally I checked the coverage which is currently on 28.5%

side note: in the future I am planning to build on the current test suite with the aim to have 100% code coverage. In the mean time I wanted to submit this pull request so that if it is merged then it is easier for others to contribute to the test suite as well.


[#1068]: Remove backstopjs

Preview environment images deployed!
The preview environment has been updated:
client image tag: preview-1906-84107248a0f0c1ba2087e5628d786a97501b0b65-20240510.1123
storybook image tag: preview-1906-84107248a0f0c1ba2087e5628d786a97501b0b65-20240510.1123
Client URL: https://pr-1906--epp.elifesciences.org
Storybook URL: https://pr-1906--epp-storybook.elifesciences.org
Note: Updated images can take a few minutes to roll out.

Preview environment created!
The preview environment has been deployed to the cluster.
Client URL: https://pr-1906--epp.elifesciences.org
Storybook URL: https://pr-1906--epp-storybook.elifesciences.org
Note: If this is a new environment, it can take a few minutes for DNS to update.


Monocular UI pod fails to launch

I'm using master and helm to install monocular. The monocular-ui pod fails to launch.
Readiness probe failed: Get http://<IP_ADDRESS>:80/: dial tcp <IP_ADDRESS>:80: getsockopt: connection refused
Back-off restarting failed docker container
Error syncing pod, skipping: failed to "StartContainer" for "monocular" with CrashLoopBackOff: "Back-off 10s restarting failed container=monocular pod=terrifying-ocelot-monocular-ui-551467507-7q2lr_default(0fcaebd6-422a-11e7-b52f-d2987996dc93)"

@dcberg sorry, missed this. What are the logs from the failed container?

ping @dcberg any more info on this?

I have seen this as well. What I did to work around this was to continue to delete the failing POD until eventually the two instances both came up and were running.  Looks like it is attempting to load a large set of resources when starting up.

time="2017-06-16T19:19:34Z" level=info msg="Processing icon" dest="/root/monocular/repo-data/stable/gitlab-ce/0.1.8/logo-160x160-fit.png" source="/root/monocular/repo-data/stable/gitlab-ce/0.1.8/logo-original.png"
time="2017-06-16T19:19:34Z" level=info msg="Local cache missing" name=magento version=0.4.3
time="2017-06-16T19:19:34Z" level=info msg="Downloading metadata" dest="/root/monocular/repo-data/stable/magento/0.4.3/chart.tgz" source="https://kubernetes-charts.storage.googleapis.com/magento-0.4.3.tgz"
time="2017-06-16T19:19:34Z" level=info msg="Local cache missing" name=magento version=0.4.2
time="2017-06-16T19:19:34Z" level=info msg="Downloading metadata" dest="/root/monocular/repo-data/stable/magento/0.4.2/chart.tgz" source="https://kubernetes-charts.storage.googleapis.com/magento-0.4.2.tgz"
time="2017-06-16T19:19:34Z" level=info msg="Storing in cache" path="/root/monocular/repo-data/stable/testlink/0.4.3/README.md"
time="2017-06-16T19:19:34Z" level=info msg="Local cache missing" name=magento version=0.4.1
time="2017-06-16T19:19:34Z" level=info msg="Downloading metadata" dest="/root/monocular/repo-data/stable/magento/0.4.1/chart.tgz" source="https://kubernetes-charts.storage.googleapis.com/magento-0.4.1.tgz"
time="2017-06-16T19:19:34Z" level=info msg="Downloading icon" dest="/root/monocular/repo-data/stable/testlink/0.4.7/logo-original.png" source="https://bitnami.com/assets/stacks/testlink/img/testlink-stack-220x234.png"
time="2017-06-16T19:19:34Z" level=info msg="Processing icon" dest="/root/monocular/repo-data/stable/spark/0.1.3/logo-160x160-fit.png" source="/root/monocular/repo-data/stable/spark/0.1.3/logo-original.png"
time="2017-06-16T19:19:34Z" level=info msg="Processing icon" dest="/root/monocular/repo-data/stable/gitlab-ce/0.1.7/logo-160x160-fit.png" source="/root/monocular/repo-data/stable/gitlab-ce/0.1.7/logo-original.png"
time="2017-06-16T19:19:34Z" level=info msg="Local cache missing" name=magento version=0.4.0
time="2017-06-16T19:19:34Z" level=info msg="Downloading metadata" dest="/root/monocular/repo-data/stable/magento/0.4.0/chart.tgz" source="https://kubernetes-charts.storage.googleapis.com/magento-0.4.0.tgz"

@todkap indeed, you may need to increase the initial delay for the liveness probe: https://github.com/kubernetes-helm/monocular/blob/master/deployment/monocular/values.yaml#L23


Remove kvdb WAL

Development Task
TiKV essentially have two WAL, one as raft log stored in raftdb, one as rocksdb WAL. Theoretically we can get rid of the rocksdb WAL, but we currently make use of  it to store states like region split/merge, and issue fsync to make sure the state is persisted. The biggest benefit of removing rocksdb WAL is not to reduce IO, but to decouple apply thread from IO tasks.
While there's not immediate plan to remove the WAL, this issue keep track of discussions around the task.

cc @Little-Wallace @BusyJay feel free to fill in more details of current discussion result here. Thanks.

If WAL is removed, does rocksdb still provide atomicity and order? For example, a write batch should not only lose some keys while save others. A write batch written after a lost one should also be lost.

If WAL is removed, does rocksdb still provide atomicity and order? For example, a write batch should not only lose some keys while save others. A write batch written after a lost one should also be lost.

Yes, but we need to enable the atomic flush feature, which may need some testing.

The major problems need to be solved are admin commands.
For admin changes that modify epoch like conf change/split/merge, a solution is recording the epoch of the region and its dependency in raft db. For example, if region a is split into several regions (b, c, a) at index i, then a record like (b, init epoch) -> (a, i) is recorded. If region b is merged into a at index j, then a record like (a, merged eoch) -> (b, j) should be recorded. In such way, when a region is recovered, it should not be started until its dependency has applied to the given index.
For log compaction, log should not be removed until flushed apply index is beyond the compact index.
For ingesting sst files, we need to wait until the apply index is flushed before deleting those files. Perhaps, we need to manually flush to avoid running out of space.
This should probably be proposed as an RFC.

If rocksdb still provide atomicity and order, we can still rely on apply index to tell if all previous logs are applied. Because order is guaranteed, so the following situations should not exist:

region a is revert back before splitting and the split region b's apply index is larger than initial index.
region b is revert back before merging and the target region a's apply index is larger than commit merge index.

/cc @solotzg TiFlash should probably also consider what could go wrong.

Data in raft engine is actually the WAL of apply processes. For tiflash, normal write raft cmd will be recorded in memory until admin cmd(like split/merge/compactlog) occurs. Then fsync memory cache of region into column storage engine and write region state and apply state to kv engine of proxy(a dynamic c lib extended from TiKV). When restarted, apply process could replay raft log from last applied index. Atomicity and idempotency of tiflash really depend on atomicity and order of storage engine of TiKV.

The major problems need to be solved are admin commands.
For admin changes that modify epoch like conf change/split/merge, a solution is recording the epoch of the region and its dependency in raft db. For example, if region a is split into several regions (b, c, a) at index i, then a record like (b, init epoch) -> (a, i) is recorded. If region b is merged into a at index j, then a record like (a, merged eoch) -> (b, j) should be recorded. In such way, when a region is recovered, it should not be started until its dependency has applied to the given index.
For log compaction, log should not be removed until flushed apply index is beyond the compact index.
For ingesting sst files, we need to wait until the apply index is flushed before deleting those files. Perhaps, we need to manually flush to avoid running out of space.
This should probably be proposed as an RFC.

For log compaction and file ingestion, we can probably make use of RocksDB's flush complete callback and the ReadTier::read_tier to advance the flushed apply index.

Data in raft engine is actually the WAL of apply processes. For tiflash, normal write raft cmd will be recorded in memory until admin cmd(like split/merge/compactlog) occurs. Then fsync memory cache of region into column storage engine and write region state and apply state to kv engine of proxy(a dynamic c lib extended from TiKV). When restarted, apply process could replay raft log from last applied index. Atomicity and idempotency of tiflash really depend on atomicity and order of storage engine of TiKV.

@solotzg thanks for chime in. Does TiFlash assume data is persisted once the apply state is written to kv engine?

Data in raft engine is actually the WAL of apply processes. For tiflash, normal write raft cmd will be recorded in memory until admin cmd(like split/merge/compactlog) occurs. Then fsync memory cache of region into column storage engine and write region state and apply state to kv engine of proxy(a dynamic c lib extended from TiKV). When restarted, apply process could replay raft log from last applied index. Atomicity and idempotency of tiflash really depend on atomicity and order of storage engine of TiKV.

@solotzg thanks for chime in. Does TiFlash assume data is persisted once the apply state is written to kv engine?

@yiwu-arbug Yes. But not like TiKV, TiFlash only writes apply state to kv engine when applying admin command. Actually, for TiFlash, there is no data in write/default/lock cf in kv engine. Just like: https://github.com/solotzg/tikv/blob/tiflash-proxy-master/components/raftstore/src/store/fsm/apply.rs#L1375 https://github.com/solotzg/tikv/blob/tiflash-proxy-master/components/raftstore/src/store/fsm/apply.rs#L1183, we only put region meta and state info to write batch.


Add 'release/trigger_all_tests.json' to trigger path of mass comment PR

This replaces the mass comment workflow for release verification. Currently add all precommit to it.

Create GItHub Action PreCommit

Create missing Google-ads IO PreCommit

Create missing RequestResponse IO PreCommit

Please add a meaningful description for your change here

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

R: @damccorm

R: @volatilemolotov

Code looks good.
With this trigger it will get added to PR so the status will show

Code looks good. With this trigger it will get added to PR so the status will show

Yeah that's the main benefits

the down side is that we need to make sure this path is included in every test, so I added another precommit (PreCommit GHA) to guard this.


boards: intel_adsp_cavs18: add test coverage

Increase the test coverage for intel_adsp_cavs18. To keep its
test coverage as the same as cavs15 and cavs25.
Currently only one test sutite failed , See #42157.
with #42158 expend the time of ringbuffer testing, it can reach
100% pass rate.
Signed-off-by: Enjia Mai<EMAIL_ADDRESS>

Test result of  commit: 0c830822aee87b350025de35c3ba631ad834059d
(the timeout of tests/lib/ringbuffer/ is 90sec)
INFO    - 133 of 133 test configurations passed (100.00%), 0 failed, 855 skipped with 0 warnings in 2494.38 seconds
INFO    - In total 1151 test cases were executed, 18150 skipped on 1 out of total 426 platforms (0.23%)
INFO    - 133 test configurations executed on platforms, 0 test configurations were only built.
Hardware distribution summary:

Board
ID
Counter

intel_adsp_cavs18

133

INFO    - Saving reports...

INFO    - Writing xunit report /home/mm/zephyrproject/zephyr/twister-out/twister.xml...

INFO    - Writing xunit report /home/mm/zephyrproject/zephyr/twister-out/twister_report.xml...

INFO    - Run completed

We need to discuss if we need to enable this at this moment. So marked it as DNM.

Codecov Report

Merging #42196 (0c83082) into main (e12d938) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 0c83082 differs from pull request most recent head 996683e. Consider uploading reports for the commit 996683e to get more accurate results

@@           Coverage Diff           @@
##             main   #42196   +/-   ##
=======================================
  Coverage   51.65%   51.65%
=======================================
  Files         616      616
  Lines       72528    72528
  Branches    16676    16676
=======================================
  Hits        37463    37463
  Misses      28960    28960
  Partials     6105     6105

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 e12d938...996683e. Read the comment docs.


[Question] Is there any plan to support Google Hangouts as a channel in Bot Framework?

If no, is there please suggest recommended workaround. I read through related issues which were closed since V4 came out. However, I don't see any recommended solution which can work at scale.

Our client also want the feature of Google Hangouts channel, Is there any plan I can expect in V4?

Hi, I'm Jim from the Bot Service team.  Hangouts is not on our short term roadmap for Bot Service; we're continually evaluating our backlog and I'll note your interest to be considered in the next round of planning.


H265 on RTMP - no video, only sound

Which version are you using?
v0.21.4
Which operating system are you using?

Windows 10 22H2
Describe the issue
OBS with H265(NVIDIA NVENC HEVC) on RTMP give me only sound without video, with RTSP all working correct.
Describe how to replicate the issue
OBS stream with NVIDIA NVENC HEVC

start the server
publish with OBS v29.0.2 (64bit)
stream settings:
Encoder: NVIDIA NVENC HEVC
Rate Control: CBR
Bitrate: 2500
Keyframe interval: 2
Preset : P5 Slow (Good Quality)
Tuning: Low Latency
Multipass Mode: Single Pass
Profile: Main
Max B-frames: 0
VLC v3.0.18

Did you attach the server logs?
with publishing:
[RTMP] [conn <IP_ADDRESS>:11594] is publishing to path 'Tengu', 2 tracks (H265, MPEG4-audio)
on RTMP read:
[RTMP] [conn <IP_ADDRESS>:11772] is reading from path 'Tengu', 1 track (MPEG4-audio)
on RTSP read:
[RTSP] [session 92155e59] is reading from path 'Tengu', with UDP, 2 tracks (H265, MPEG4-audio)

Did you attach a network dump?

no

Use RTSP to read the stream:
rtsp://localhost:8554/Tengu
Nor VLC nor the server support reading H265 with RTMP, as explicitly written in the README.


Ping to rspec < 3.8 to prevent failures

Signed-off-by: Tim Smith<EMAIL_ADDRESS>

smells like ruby 2.5 has a real failure?

I'm open to ideas

Closing this out as it's not the real fix


Integration test for regression with parallel docker run when specifying a port

Implement integration test for #1314
ping @chanwit @aluzzardi @vieux
Tested before (failure with the nil pointer panic) and after the patch (test succeeded). This integration test should ensure that we don't see a regression in the future for this specific issue.
Not sure if the best way so let me know if I can improve it (parallel command is not available in the swarm test image). Also don't know where to put the test so it ended up in port.bats :smile:
Signed-off-by: Alexandre Beslic<EMAIL_ADDRESS>

ouch golint :facepunch: (will fix)

LGTM
This is awesome @abronan. I think it's OK to merge right away.

You might want to use the parallel command instead. That would require updating the testing image test/integration/Dockerfile

@aluzzardi not sure if really necessary to have parallel on this one, but your call :)
@vieux WDYT?

LGTM

Let's update to parallel in another PR


Questions about the way of handling webhook event

Since I'm making some changes,  I'm confused by the code which handles webhook event. For me, cla.check() is able to handle a webhook event. The function handleWebhook() first get commits(but don't use the commits) and then call cla.check(). I feel it's really redundant. Could anyone give me some guidance?

@KharitonOff would be the right one to help out here 😃

The main reason of getting commits first and calling cla.check() afterwards is the problem with GitHub API we faced lately: sometimes the PR API (https://developer.github.com/v3/pulls/#list-commits-on-a-pull-request) didn't respond with appropriate data straight after the PR was created, it took a bit of time until the API responded as expected.
So, in order to handle this latency I added this api-call before check() and the timeout function for the case the GitHub API response has no data yet.


CreationDate problem with use Ngpsql.EntityFrameworkCore.PostgreSQL > 6.0

More details: https://www.roji.org/postgresql-dotnet-timestamp-mapping
Details of problem:
From what I understand, basically the problem happens when you have a date with Kind other than UTC, to get around the problem a flag must be changed globally, but it is not a good practice, the best is to use the concept of "UTC Everywhere".
Checking the source code on line 14 of the KeyMaterial file, the Data value starts with Now, this causes the error because of Kind=Local.
Likely correction:
KeyMaterial line 14: DateTime.UtcNow
KeyMaterial line 37: DateTime.UtcNow
This will make Npgsql not throw excpetion on account of Kind other than UTC and also the dates will be bought in UTC ignoring infra setting.
Imagem do erro em um projeto .NET6 com PostgreSQL:

Conclusion
If these changes make sense for the project proposal, I can be making and submitting the pull request.
I used google translate to create the text, in case something was confused in the translation I can send it in pt-br.

In my project I resolved the problem adding one interceptor for transform dates to utc dates, but it would be nice to have the fix in the package.

Hi @eliezeralmeida ,
It makes sense, go ahead and make a pr!
Thx


Support password grant type

Hello,
I tried to add AuthorizationGrantType.PASSWORD while building the RegisteredClient object, like this:
RegisteredClient registeredClient = RegisteredClient.withId(UUID.randomUUID().toString())
				...
				.authorizationGrantType(AuthorizationGrantType.AUTHORIZATION_CODE)
				.authorizationGrantType(AuthorizationGrantType.REFRESH_TOKEN)
				.authorizationGrantType(AuthorizationGrantType.CLIENT_CREDENTIALS)
				.authorizationGrantType(AuthorizationGrantType.PASSWORD)
				...
				.build();

Using Postman, the error I get is:
{
    "error_description": "OAuth 2.0 Parameter: grant_type",
    "error": "unsupported_grant_type",
    "error_uri": "https://datatracker.ietf.org/doc/html/rfc6749#section-5.2"
}

Any plans for future baselines to support this grant type?
Thank you!

See #466

I see, thank you. So it would be nice to remove the constant AuthorizationGrantType.PASSWORD to avoid misunderstanding. Thanks!

Closing as duplicate of gh-343


Installing the VST in Mac?

Hi,
how do install the VST plugin on my Mac? I did a cargo build in the example from the README, and it generated a .dylib file, but my DAW isn't able to find it.
Thanks!

I believe you'll need to bundle the .dylib file as a loadable bundle. There might be a way to do this through XCode but at the bare minimum you need a directory structure that looks like:
chorus.vst/
    Contents/
        MacOS/
            chorus
        Info.plist

The MacOS/chorus file should be the .dylib that you get when you compile but without the .dylib extension, e.g. chorus.dylib becomes chorus. Here's a sample Info.plist:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>CFBundleName</key>
	<string>ODP Chorus</string>
</dict>
</plist>

This works! Thanks! :+1:

It would be worth adding this information to the README or some other form of documentation. I had the same question and just happened to come by this closed issue. It would be more helpful if the information was in the forefront.

It seems to be a general problem with the way that OSX dynamic libraries/bundles work. It's not necessarily specific to VST plugins, so there might be a better solution elsewhere. I could link this issue in the README if you think it would help?

I think it could be helpful, the main issue is that people who may be new to vst dev on OS X may not realize that an extra step is required to package a working vst. I could work up a shell script or something that could be included with the lib that would generate a working bundle

I wrote a small bash script that will create a vst bundle given a package name and a library filepath.
#!/bin/bash
# did the user provide a package name and a library path
if [[ $1 != "" && $2 != "" ]]; then

  #make the bundle folder
  mkdir "$1.vst"
  cd "$1.vst"
  mkdir "Contents"
  cd "Contents"

  #create the PkgInfo
  touch "PkgInfo"
  echo "BNDL????">"PkgInfo"

  #build the Info.Plist
  touch "Info.Plist"
  echo "<?xml version="1.0" encoding="UTF-8"?>
  <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
  <plist version="1.0">
  <dict>
  	<key>CFBundleDevelopmentRegion</key>
  	<string>English</string>

  	<key>CFBundleExecutable</key>
  	<string>vst</string>

    <key>CFBundleGetInfoString</key>
    <string>vst</string>

    <key>CFBundleIconFile</key>
    <string></string>

    <key>CFBundleIdentifier</key>
  	<string>com.rust-vst2.$1</string>

  	<key>CFBundleInfoDictionaryVersion</key>
  	<string>6.0</string>

  	<key>CFBundleName</key>
  	<string>$1</string>

  	<key>CFBundlePackageType</key>
  	<string>BNDL</string>

  	<key>CFBundleVersion</key>
  	<string>1.0</string>

  	<key>CFBundleSignature</key>
  	<string>$((RANDOM % 9999))</string>

    <key>CSResourcesFileMapped</key>
  	<string></string>

  </dict>
  </plist>" > "Info.Plist"

  #move the provided library to the correct location
  mkdir "MacOS"
  cd "MacOS"
  cp -r "$2" "$1"

else
  if [[ $1 == "" ]]; then
    echo "Package name not provided!"
  fi
  if [[ $2 == "" ]]; then
    echo "Library Path not provided!"
  fi
fi

It can be used as such: vst_bundler.sh pkgname /path/to.dylib
It will output a bundle that contains the provided library as well as the needed support files.
vst_bundler.sh.zip
I will need someone to verify that this script works though. I currently do not have the proper setup on my machine to test that the generated bundle works.

@zyvitski I've cleaned up and fixed some small issues with the script. If you want to make a pull request with some sort of section in the README I'll merge it in.
#!/bin/bash

# Make sure we have the arguments we need
if [[ -z $1 || -z $2 ]]; then
    echo "Generates a macOS bundle from a compiled dylib file"
    echo "Example:"
    echo -e "\t$0 Plugin target/release/plugin.dylib"
    echo -e "\tCreates a Plugin.vst bundle"
else
    # Make the bundle folder
    mkdir -p "$1.vst/Contents/MacOS"

    # Create the PkgInfo
    echo "BNDL????" > "$1.vst/Contents/PkgInfo"

    #build the Info.Plist
    echo "<?xml version=\"1.0\" encoding=\"UTF-8\"?>
<!DOCTYPE plist PUBLIC \"-//Apple//DTD PLIST 1.0//EN\" \"http://www.apple.com/DTDs/PropertyList-1.0.dtd\">
<plist version=\"1.0\">
<dict>
    <key>CFBundleDevelopmentRegion</key>
    <string>English</string>

    <key>CFBundleExecutable</key>
    <string>vst</string>

    <key>CFBundleGetInfoString</key>
    <string>vst</string>

    <key>CFBundleIconFile</key>
    <string></string>

    <key>CFBundleIdentifier</key>
    <string>com.rust-vst2.$1</string>

    <key>CFBundleInfoDictionaryVersion</key>
    <string>6.0</string>

    <key>CFBundleName</key>
    <string>$1</string>

    <key>CFBundlePackageType</key>
    <string>BNDL</string>

    <key>CFBundleVersion</key>
    <string>1.0</string>

    <key>CFBundleSignature</key>
    <string>$((RANDOM % 999999))</string>

    <key>CSResourcesFileMapped</key>
    <string></string>

</dict>
</plist>" > "$1.vst/Contents/Info.plist"

    # move the provided library to the correct location
    cp "$2" "$1.vst/Contents/MacOS/$1"

    echo "Created bundle $1.vst"
fi

Pull request issued


Not working on manjaro (arch)

This script doesn't update the now playing status on discord when running it on manjaro (based off arch)
This is the error that gets outputted
[12:00:58 PM] [/]] Opening Discord IPC Pipe
[12:00:58 PM] [/] onPlexServerAlert Error: There is no current event loop in thread 'Thread-5'.

Are you using the latest version of Python?

Sorry this took so long. Another user had the same issue (#7) and the latest update of the script fixed it for them. Update your copy and let me know if it's fixed for you as well.


DataStore Speed/Latency -> Library Version

Hi,
Question/technical problem regarding DataStore:
I was reading the documentation on Datastore, and it seems there were revisions to increase the speed of latency. I could not find confirmation if the PHP Client Library is on V1Beta3, which is supposed to be the core release with fixes for DataStore latency on the client side.
The reason I ask is because I am experiencing some latency with the PHP library for datastore, and I am trying to find the source. I am not on app engine. I have tested this on Compute Instance as well as my local machine.
<?php

// getting list by type
function list_items_of_type($type)
{
	global $datastore;
    $query = $datastore->query()
        ->kind($type);
    $result = $datastore->runQuery($query);
    return $result;
}

// getting an entity
function get_item($id,$type){
    global $datastore;
    # get item object from the database
    $itemKey = $datastore->key($type, $id);
    $transaction = $datastore->transaction();
    return $transaction->lookup($itemKey);
}

Either of these operations takes .7 to 1 second to complete (just a single query or say 30 serialized calls each call takes 1 second). I was running it on a DataStore with 1 and then 3 entities and was a bit surprised to see the query take that long.
Same setup, python:
from google.cloud import datastore
import time
client = datastore.Client()
# Then query for entities
t = time.time()
query = client.query(kind=entity_type)
query.fetch()
print(time.time() -t )

0.05 - 0.11 seconds on my local connection for serialized calls.. I am certain its not the speed of the network as a full network loop is pretty normal for what I would expect from a Instance and from my connection, that latency is in the 10s of ms or so, and even then there is still a pretty big discrepancy between the two libraries, but I might be totally running queries the wrong way was just following whats on the GCP main site.
To be clear, I am measuring this using microtime in php, although sometimes this provides values greater than the system clock gives for real world execution of the entire script which is rather quirky, but in other words I have made sure its not PHP  overhead, these operations are slow no matter how many times the program executes them.
I also read an explanation about the system ops that allow DataStore to scale automatically unlike the manual process with Dynamo, that automation can hamper the speed sometimes on intermittent reads, so I did run a bunch of reads and it hovers around but is pretty tightly bound around 1 second.
I am running "google/cloud-datastore": "^1.3".
Hoping someone might know what could be causing this, was not sure if its the underlying auth strategy causing overhead but did not dig deep enough yet to find out, would have to be pretty different from python lib.
Thanks!

The latency you describe is a bit high, but not completely outside of what could be expected depending on your connection speed. In my tests, I saw results of roughly 0.3s to 0.5s.
We recommend storing access tokens in a cache. This should show marked improvements after the first request. symfony/cache is a good option.
Create your client like this:
use Google\Cloud\Datastore\DatastoreClient;
use Symfony\Component\Cache\Adapter\FilesystemAdapter;

$datastore = new DatastoreClient([
  'authCache' => new FilesystemAdapter
]);

After setting up a cache, you should see latency on requests after the first request drop considerably.

@jdpedrie  Thanks for the tip. Much faster!

One last question about the datastore client. Is there an easy way to iterate over the elements. I basically need to iterate over the structure and then build an array to json encode. Normal ArrayAccess foreach is not working as I'd expect. Am looking now, but figured I would ask.

I'm not sure what you are referring to by "elements". Do you mean fields in an entity? You can use Entity::get() to fetch all the fields in an entity as an array, which can then be iterated.

@1tron1 did you figure out what you needed for your followup question?

@jdpedrie  yes my apologies, thanks for the help.


Add ZIO Bson Docs to The zio.dev Website

Now that the documentation project has been published to the npm registry, we can integrate it into the zio.dev website.

It is now on zio.dev: https://zio.dev/zio-bson/


Implement remote branch deletion

Jgit isn't doing what it's supposed to do on this, backlogging until jgit people respond to forum post

Also fix branch creation updating branches

Branches deleted/created locally are now updated correclty

Try filing as a bug with JGit team.

Turns out this is actually possible! Poorly documented though...

NIce! Did they answer you, or did you find it yourself?

I found some syntax in a bug report from 2012, then trial and errored the particular branch name syntax until I got it right...


Add a Desktop Version

I am wondering if there ever will be a desktop version of K-9 Mail. I really enjoy the program on my phone and have yet to find a program on desktop (Windows 10 specifically) that works with all of my several emails (or even allows the customizability that this program allows). I do understand it will take a while to implement in full, but I am willing to test it out 👍 .

consider Thunderbird for desktop
It is open source, customizable and works with quite everything I know of...

I acutally just uninstalled that one, it didn't have Google as the default search engine and many of the plugins are old and no longer supported


 produces an error in TypeScript despite having an effect

Description
Passing aspectRatio prop to Image component works, but produces an error in TypeScript:
error TS2769: No overload matches this call.
  Overload 1 of 2, '(props: ImageProps | Readonly<ImageProps>): Image', gave the following error.
    Type '{ aspectRatio: number; height: number | undefined; resizeMode: "contain"; source: { uri: string; }; style: any; width: number | undefined; accessibilityLabel: string | undefined; }' is not assignable to type 'IntrinsicAttributes & IntrinsicClassAttributes<Image> & Readonly<ImageProps>'.
      Property 'aspectRatio' does not exist on type 'IntrinsicAttributes & IntrinsicClassAttributes<Image> & Readonly<ImageProps>'.
  Overload 2 of 2, '(props: ImageProps, context: any): Image', gave the following error.
    Type '{ aspectRatio: number; height: number | undefined; resizeMode: "contain"; source: { uri: string; }; style: any; width: number | undefined; accessibilityLabel: string | undefined; }' is not assignable to type 'IntrinsicAttributes & IntrinsicClassAttributes<Image> & Readonly<ImageProps>'.
      Property 'aspectRatio' does not exist on type 'IntrinsicAttributes & IntrinsicClassAttributes<Image> & Readonly<ImageProps>'.

35       aspectRatio={4 / 3}

React Native Version
0.72.3
Output of npx react-native info
System:
OS: macOS 13.5
CPU: (8) arm64 Apple M2
Memory: 37.58 MB / 16.00 GB
Shell:
version: "5.9"
path: /bin/zsh
Binaries:
Node:
version: 18.17.0
path: /private/var/folders/3y/swkjq1x101b76mzjgt4pm2d80000gp/T/xfs-ac03ab9d/node
Yarn:
version: 3.5.1
path: /private/var/folders/3y/swkjq1x101b76mzjgt4pm2d80000gp/T/xfs-ac03ab9d/yarn
npm:
version: 9.8.1
path: /usr/local/bin/npm
Watchman: Not Found
Managers:
CocoaPods:
version: 1.12.1
path: /opt/homebrew/bin/pod
SDKs:
iOS SDK:
Platforms:
- DriverKit 22.4
- iOS 16.4
- macOS 13.3
- tvOS 16.4
- watchOS 9.4
Android SDK: Not Found
IDEs:
Android Studio: Not Found
Xcode:
version: 14.3.1/14E300c
path: /usr/bin/xcodebuild
Languages:
Java: Not Found
Ruby:
version: 2.6.10
path: /usr/bin/ruby
npmPackages:
"@react-native-community/cli": Not Found
react:
installed: 18.2.0
wanted: 18.2.0
react-native:
installed: 0.72.3
wanted: ^0.72.3
react-native-macos: Not Found
npmGlobalPackages:
"react-native": Not Found
Android:
hermesEnabled: true
newArchEnabled: false
iOS:
hermesEnabled: true
newArchEnabled: false
Steps to reproduce
<Image
  // …
  aspectRatio={4 / 3}
/>

Snack, screenshot, or link to a repository
https://snack.expo.dev/eHW3LA8QD

This is also the case for other Layout Props (I tested height, margin/padding and borderWidth/borderColor using the example provided).
Are these props supposed to work like that? They are labeled "props", but they are used via style prop in the documentation.

Style props are flattened when passed to native components for historical reasons. I would recommend not relying on it, and keeping style props on style. I.e. we would like to fix this in the future, but it’s scary to because existing untyped code may be using these as top level props with everything working.


feat: add voice search component

Closes #
📑 Description

add voice search component and doc

✅ Checks

[x] My pull request adheres to the code style of this project
[x] My code requires changes to the documentation
[x] I have updated the documentation as required
[x] All the tests have passed
[x] My pull request is based on the latest version

ℹ Additional Information

If your branch is behind the upstream master, I will have difficulties to merge the request. Please fetch the latest version of the branch:
git checkout your-branch
git pull upstream master

or
git checkout your-branch
git pull --rebase upstream master

Thanks for your PR. It has been merged.

@oune Please join the Discord Flowbite channel, if you are interested.

We have Flowbite-Svelte channel.
I will request to invite you to an internal svelte-library channel.

Let me know your Discord user name.

My discord name is oune#6436 thank you

Thanks. Did you join to the Flowbite channel?

I tried join the channel few minuets ago but i had error message

Can you try this one?
Join the Flowbite Discord Server

sucess! thank you


BUG: stats: fix skewnorm pdf when a=0

Reference issue
Fixes #16038
What does this implement/fix?
Fix the skewnorm PDF when a=0. As described in #16038, skewnorm limits to norm when a=0. All the methods except PDF matched norm's methods. This PR fixes this and adds appropriate tests.

Added the example from the issue, thanks!

Thanks @tirthasheshpatel!


Docker Pulling exact version still seems to pull wrong version

I pull down the exact version:

0.16.47: Pulling from dtandersen/factorio
Digest: sha256:50d24d718e46e51a9d0ba9edaa5eb09ec11f2e0488adca22e7bfb6a351e6e916
Status: Image is up to date for dtandersen/factorio:0.16.47

But when this container fires up, and I try to connect it still says it is running 0.16.46.
At first I thought it was that latest wasn't pointing to 0.16.47...
(similar to this: https://github.com/dtandersen/docker_factorio_server/issues/166)
But, even pulling the specific image seems to still be starting a 0.16.46 server.
:/
Not sure what is up.
(but I have had this similar mismatch issue a few times for other versions as well in the past month or so)

Ill validate this.

$ docker run --rm -it dtandersen/factorio:0.16.47
Unable to find image 'dtandersen/factorio:0.16.47' locally
0.16.47: Pulling from dtandersen/factorio
ff3a5c916c92: Already exists
c4f576d46465: Pull complete
edebedd9043d: Pull complete
fbc80f8f72f4: Pull complete
Digest: sha256:50d24d718e46e51a9d0ba9edaa5eb09ec11f2e0488adca22e7bfb6a351e6e916
Status: Downloaded newer image for dtandersen/factorio:0.16.47

...
+ /opt/factorio/bin/x64/factorio --create /factorio/saves/_autosave1.zip --map-gen-settings /factorio/config/map-gen-settings.json --map-settings /factorio/config/map-settings.json
   0.000 2018-06-04 13:56:45; Factorio 0.16.47 (build 36587, linux64, headless)
   0.000 Operating system: Linux

could you post your log?

just poking around now, I'll let you know what I turn up. :)

Alright, I got it figured out.
It was related to the other issue about "latest" not being latest.
I have two scripts one for update.sh and one start.sh, the last few times I ran them I had forgotten to update the version they were referencing in start.sh (so it was still trying to load up :latest)
*Fixed it so start just takes the tag in as an argument now
And so, yes .47 behaves as expected. :)


Users/yacao/m105 fixantoptions

Looks good.  Thanks, Yang.

Maven and Gradle changes look good too.

Change to using tl.line() instead of tl.arg() and don't use getDelimitedInput() as we talked about offline.
Thanks,
Madhuri


Can add Metal 2 support?

needs new MacOS 10.13 and Xcode 9..

Yes, I'm already looking into this.

Only one question.. do you plan to support it in the beta period or will have support once MacOS/IOS and Xcode 9 have stable releases?
thanks

Yes, I'm planning to support it. I'm working on it, it's pretty big change.


[material-ui][Transitions] External ownerState is incorrectly forwarded to inner components

Description
Fix forwarded ownerState from Transition component overriding component own's ownerState
https://www.loom.com/share/96131abf63ba48878bf3e8d02856cce3
closes https://github.com/mui/material-ui/issues/40653

[x] I have followed (at least) the PR section of the contributing guide.

This code was written and reviewed by GitStart Community. Growing great engineers, one PR at a time.

@DiegoAndai This PR is ready for review