dbus: 1.12.6 -> 1.12.8

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/dbus/versions.
These checks were done:

built on NixOS
ran ‘/nix/store/q2p724wzbngs5qrv96s2mny5bhsnm3jk-dbus-1.12.8/bin/dbus-monitor --help’ got 0 exit code
ran ‘/nix/store/q2p724wzbngs5qrv96s2mny5bhsnm3jk-dbus-1.12.8/bin/dbus-update-activation-environment help’ got 0 exit code
ran ‘/nix/store/q2p724wzbngs5qrv96s2mny5bhsnm3jk-dbus-1.12.8/bin/dbus-cleanup-sockets -h’ got 0 exit code
ran ‘/nix/store/q2p724wzbngs5qrv96s2mny5bhsnm3jk-dbus-1.12.8/bin/dbus-cleanup-sockets --help’ got 0 exit code
ran ‘/nix/store/q2p724wzbngs5qrv96s2mny5bhsnm3jk-dbus-1.12.8/bin/dbus-cleanup-sockets help’ got 0 exit code
ran ‘/nix/store/q2p724wzbngs5qrv96s2mny5bhsnm3jk-dbus-1.12.8/bin/dbus-run-session -h’ got 0 exit code
ran ‘/nix/store/q2p724wzbngs5qrv96s2mny5bhsnm3jk-dbus-1.12.8/bin/dbus-run-session --help’ got 0 exit code
ran ‘/nix/store/q2p724wzbngs5qrv96s2mny5bhsnm3jk-dbus-1.12.8/bin/dbus-uuidgen --help’ got 0 exit code
ran ‘/nix/store/q2p724wzbngs5qrv96s2mny5bhsnm3jk-dbus-1.12.8/bin/dbus-launch -h’ got 0 exit code
ran ‘/nix/store/q2p724wzbngs5qrv96s2mny5bhsnm3jk-dbus-1.12.8/bin/dbus-launch --help’ got 0 exit code
found 1.12.8 with grep in /nix/store/q2p724wzbngs5qrv96s2mny5bhsnm3jk-dbus-1.12.8
directory tree listing: https://gist.github.com/598fa486a7a2da2a0887e0899dd2ed27

Success on x86_64-linux (full log)
Attempted: dbus
Partial log (click to expand)
stripping (with command strip and flags -S) in /nix/store/1x2jqbsksiix0iw0rz4wlnggz64ly9lp-dbus-1.12.8-lib/lib
patching script interpreter paths in /nix/store/1x2jqbsksiix0iw0rz4wlnggz64ly9lp-dbus-1.12.8-lib
checking for references to /build in /nix/store/1x2jqbsksiix0iw0rz4wlnggz64ly9lp-dbus-1.12.8-lib...
shrinking RPATHs of ELF executables and libraries in /nix/store/nipfi4d0365k8vk4f1awv94m8l897rh4-dbus-1.12.8-doc
strip is /nix/store/j75dgadrff2d1fyc4fczmcgqkid2imdx-binutils-2.30/bin/strip
patching script interpreter paths in /nix/store/nipfi4d0365k8vk4f1awv94m8l897rh4-dbus-1.12.8-doc
checking for references to /build in /nix/store/nipfi4d0365k8vk4f1awv94m8l897rh4-dbus-1.12.8-doc...
Moving /nix/store/q2p724wzbngs5qrv96s2mny5bhsnm3jk-dbus-1.12.8/bin/dbus-launch to /nix/store/1x2jqbsksiix0iw0rz4wlnggz64ly9lp-dbus-1.12.8-lib/bin/dbus-launch
rmdir: failed to remove '/nix/store/q2p724wzbngs5qrv96s2mny5bhsnm3jk-dbus-1.12.8/bin': Directory not empty
/nix/store/q2p724wzbngs5qrv96s2mny5bhsnm3jk-dbus-1.12.8

Success on aarch64-linux (full log)
Attempted: dbus
Partial log (click to expand)
stripping (with command strip and flags -S) in /nix/store/9yryd78fbdci7wmlm7l4a3aj1bjql4hf-dbus-1.12.8-lib/lib
patching script interpreter paths in /nix/store/9yryd78fbdci7wmlm7l4a3aj1bjql4hf-dbus-1.12.8-lib
checking for references to /build in /nix/store/9yryd78fbdci7wmlm7l4a3aj1bjql4hf-dbus-1.12.8-lib...
shrinking RPATHs of ELF executables and libraries in /nix/store/icd0z99fjns69rr2i92v9lc5arshj75g-dbus-1.12.8-doc
strip is /nix/store/gp7fylxwn18b7pl2c18ks89hsiaxyfvf-binutils-2.30/bin/strip
patching script interpreter paths in /nix/store/icd0z99fjns69rr2i92v9lc5arshj75g-dbus-1.12.8-doc
checking for references to /build in /nix/store/icd0z99fjns69rr2i92v9lc5arshj75g-dbus-1.12.8-doc...
Moving /nix/store/3197rjclvqcm7x2crwbv874g3xv1r3dx-dbus-1.12.8/bin/dbus-launch to /nix/store/9yryd78fbdci7wmlm7l4a3aj1bjql4hf-dbus-1.12.8-lib/bin/dbus-launch
rmdir: failed to remove '/nix/store/3197rjclvqcm7x2crwbv874g3xv1r3dx-dbus-1.12.8/bin': Directory not empty
/nix/store/3197rjclvqcm7x2crwbv874g3xv1r3dx-dbus-1.12.8

Failure on x86_64-linux (full log)
Attempted: dbus
Partial log (click to expand)
cannot build derivation '/nix/store/87893l5c88n5wysfr0a7l9drh6sr5440-gnu-efi-3.0.8.drv': 3 dependencies couldn't be built
cannot build derivation '/nix/store/3mgymcp2cdgz6dna49a0szi6pjck29s7-intltool-0.51.0.drv': 5 dependencies couldn't be built
cannot build derivation '/nix/store/c0cam7nrsc16avkgjbrcyab0yz6qxbpw-gnome-doc-utils-0.20.10.drv': 10 dependencies couldn't be built
cannot build derivation '/nix/store/pcvy22ijnh4n6z16z8nibv6k73k36vw9-shadow-4.5.drv': 11 dependencies couldn't be built
cannot build derivation '/nix/store/24p726d0hs0g92i9w538wnx669jpr3db-util-linux-2.32.drv': 5 dependencies couldn't be built
cannot build derivation '/nix/store/13479g4cli3h6faqzqr02hz5fsp9bsgq-glib-2.56.0.drv': 11 dependencies couldn't be built
cannot build derivation '/nix/store/r74hq1g8y2y1cxlqijgllmkqrh3c4spq-libSM-1.2.2.drv': 7 dependencies couldn't be built
cannot build derivation '/nix/store/sc1p52xhpw29f0zl7hxcy6kdhfd2b2qv-systemd-238.drv': 42 dependencies couldn't be built
cannot build derivation '/nix/store/jqlgighhpk5xf9x8h7qii81ka5yf1mx6-dbus-1.12.8.drv': 8 dependencies couldn't be built
error: build of '/nix/store/jqlgighhpk5xf9x8h7qii81ka5yf1mx6-dbus-1.12.8.drv' failed

Success on aarch64-linux (full log)
Attempted: dbus
Partial log (click to expand)
stripping (with command strip and flags -S) in /nix/store/x6zwbrfm3mm9wy3vv6zk3xcsdzz8029l-dbus-1.12.8-lib/lib
patching script interpreter paths in /nix/store/x6zwbrfm3mm9wy3vv6zk3xcsdzz8029l-dbus-1.12.8-lib
checking for references to /build in /nix/store/x6zwbrfm3mm9wy3vv6zk3xcsdzz8029l-dbus-1.12.8-lib...
shrinking RPATHs of ELF executables and libraries in /nix/store/q78mahnkvdc1m7anskdfni7x930dlrny-dbus-1.12.8-doc
strip is /nix/store/mlcnqzwci6q9cw1zfsfzzdphcyjks2n5-binutils-2.30/bin/strip
patching script interpreter paths in /nix/store/q78mahnkvdc1m7anskdfni7x930dlrny-dbus-1.12.8-doc
checking for references to /build in /nix/store/q78mahnkvdc1m7anskdfni7x930dlrny-dbus-1.12.8-doc...
Moving /nix/store/wc1fggxhyajvi3fzbzplkdcg8v7dk5jq-dbus-1.12.8/bin/dbus-launch to /nix/store/x6zwbrfm3mm9wy3vv6zk3xcsdzz8029l-dbus-1.12.8-lib/bin/dbus-launch
rmdir: failed to remove '/nix/store/wc1fggxhyajvi3fzbzplkdcg8v7dk5jq-dbus-1.12.8/bin': Directory not empty
/nix/store/wc1fggxhyajvi3fzbzplkdcg8v7dk5jq-dbus-1.12.8

Failure on x86_64-darwin (full log)
Attempted: dbus
Partial log (click to expand)
cannot build derivation '/nix/store/06pfq6b29msgpjwj68dm96wpmfsngjqb-IOKit-osx-10.11.6.drv': 3 dependencies couldn't be built
cannot build derivation '/nix/store/8m4q9dnmwyzbv8wifa26dig2gqwc8nm8-configd-osx-10.8.5.drv': 9 dependencies couldn't be built
cannot build derivation '/nix/store/3ivnl4dbcmhv91ici57pnd8la102kfj3-python-2.7.14.drv': 15 dependencies couldn't be built
cannot build derivation '/nix/store/dzvz0azrvlzj3xixii8jryp8v3dvv86d-libxml2-2.9.8.drv': 5 dependencies couldn't be built
cannot build derivation '/nix/store/gpsgmg84h0yxkilw7qg876d7lqgzdf5w-xcb-proto-1.12.drv': 4 dependencies couldn't be built
cannot build derivation '/nix/store/k4yr2pajcp4nzpqx3v4jrzx81rj6cj4p-libxslt-1.1.32.drv': 5 dependencies couldn't be built
cannot build derivation '/nix/store/ikg1x6pnpihx9r8c9dpr0rwvl4vf9vsd-libxcb-1.12.drv': 9 dependencies couldn't be built
cannot build derivation '/nix/store/14206ri0dwkn8i32rdh9s86z3v4jvhbc-libX11-1.6.5.drv': 10 dependencies couldn't be built
cannot build derivation '/nix/store/9krszis7g66ns40fv9wr7v2riss6mz84-dbus-1.12.8.drv': 7 dependencies couldn't be built
error: build of '/nix/store/9krszis7g66ns40fv9wr7v2riss6mz84-dbus-1.12.8.drv' failed


Official site http://agmrcet.com http://agmrcet.ac.in

Mail Id mail.agmrcet.com
CSE Course http://agmrcet.ac.in/cse.php

@allahbaksh Pull request merged. Thank you!


Integrated terminal crashed with error Cannot read property 'style' of undefined

VSCode Version: Version 1.31.0-insider (1.31.0-insider) 2018-12-21T06:07:14.943Z
OS Version: macOS Mojave Version 10.14.2

Steps to Reproduce:

Not sure how to reproduce, but the integrated terminal sometimes just crashed, I cannot scroll or
type. There is no error message.
Then I try to toggle the terminal down and up again, there will be an error alert: Cannot read property 'style' of undefined like this:

Does this issue occur when all extensions are disabled?: No
Errors from the Dev Tools Console:

https://github.com/Microsoft/vscode/issues/65702


Error: Not Enough User on Saving View Context

Error when Saving View Context as CdBill has not enought members of User

Fixed: Setting Minimum in Relationship to "Unbound"


after successful delivery of invitation - getting 502 nginx bad gateway error in browser

rbx 2.2.10, rails 4.1.6, devise 3.3.0, devise_invitable 1.3.6
I send an invitation, it is delivered successfully, the email arrives in inbox, but I invariably get a 502 NGINX Bad Gateway
any ideas as to why this might happen, or even how to debug. The invitations_controller seems to get through the create action ok.
here is an example extract from my log file which seems successful - but I'm getting the above-mentioned error at the end in my browser:
Devise::Mailer#invitation_instructions: processed outbound mail in 279.8ms
I, [2015-01-29T01:48:41.295106 #20753]  INFO -- :
Sent mail to<EMAIL_ADDRESS>(121561.4ms)
D, [2015-01-29T01:48:41.296184 #20753] DEBUG -- : Date: Thu, 29 Jan 2015 01:46:39 +0000
From<EMAIL_ADDRESS>Reply-To<EMAIL_ADDRESS>To<EMAIL_ADDRESS>Message-ID<EMAIL_ADDRESS>                                             Subject: Invitation instructions
Mime-Version: 1.0
Content-Type: text/html;
charset=UTF-8
Content-Transfer-Encoding: 7bit

    Hello RyanG30

You have been invited to Calm, the web site address is: https://myApp.au/en .

    To log in, please accept the invitation below. Upon following the link, you will be able to set up your password to access Calm 4.

Accept invitation

    Also please note that you will be able to log in with either of the following:

your username: RyanG30

your email<EMAIL_ADDRESS>

    If you don't want to accept the invitation, please ignore this email.

Your account won't be created until you access the link above and set your password.

actually, the invitations controller only gets through the create method sometimes, it is inconsistent but it always makes it into the if resource.errors.empty? block. sometimes it reaches respond_with - sometimes it doesn't.
def create
  self.resource = invite_resource
  if resource.errors.empty?
    yield resource if block_given?
    set_flash_message :notice, :send_instructions, :email => self.resource.email if self.resource.invitation_sent_at
    respond_with resource, :location => after_invite_path_for(resource)
  else
    respond_with_navigational(resource) { render :new }
  end
end

the nginx log reads
2015/01/29 02:53:11 [error] 4601#0: *312 upstream prematurely closed connection while reading response header from upstream, client: <IP_ADDRESS>, server: removed.org.au, request: "POST /en/users/invitation HTTP/1.1", upstream: "http://unix:///home/calm/apps/registration/shared/tmp/registration-puma.sock://en/users/invitation", host: "removed.org.au", referrer: "https://removed.org.au/en/users/invitation/new"


[BUG] KoP will consume duplicate message when send multi batches in one produce request for one TopicPartition

Describe the Bug
When producer send multi batches in one MemoryRecords, such as protocal [V0, V2] and [V8, +), it will packup multi batches in one  entry and stored in managedLeger.
However, the offset expose to consumer is in batch granularity. Consumer fetch message accroding to offset, and it will be converted to MessageId in KoP. As the following picture, one entry contains for batches

When consumer fetch from offset 6, offset 6 will be converted to entry 1, and KoP will fetch entry 1 from BookKeeper and return fetched entry to consumer without filtering  out message of offset 4 and offset 5. It will lead to consumer fetch duplicated messages.
Another affected area is getting LogStartOffset (LSO). https://github.com/streamnative/kop/pull/531
We are planing to calculate LSO by
LSO = LEO - numberOfEntries
LSO and numberOfEntries can get from managedLedger.
However, this formula is based on one entry contains one batch.
If one entry contains multi batches, we should use another variable to mark LSO in managedLedger.

Just a term correction. In Kafka, LSO is usually short for Last Stable Offset. For log started offsets, there seems to be no short name.
To solve this problem, I think we need to upgrade the Kafka dependency to 2.7.0 or 2.8.0 first. And if we want to handle the case that a single entry contains multiple batches, we can add a key-value to the entry's metadata.


zusammenhang zwischen correlation, LM und prediction hier erklären

Not sure I understand this issue. Has this been solved yet?

Ping @berndbischl


Fix grammar in migration template docblocks.

Also fixed a typo in a test file's name.

Q
A

Is bugfix?
no

New feature?
no

Breaks BC?
no

Tests pass?
yes

Fixed issues

Thank you!


Add good mecanism to parse custom packets

for example not data packet
see https://github.com/PocketMine/RakLib/blob/a5cca45a922ca193a616069f885866efc7158c67/server/Session.php#L396

https://gist.github.com/mhsjlw/8f2923d2e64f1052dab29fbcd86b91ab but what we really need are the packets

done


Add missing peer dependencies

Yarn requires peer dependencies to be specified at each level of nesting if you have deeply nested packages with peer deps.  This adds the missing peer deps to react-dom-interactions since it depends on @floating-ui/react-dom which has peer deps.
This is what the error currently looks like that this will fix.

Idk how that was missing but thanks 😄


Add http://repository.jboss.org/licenses/cc0-1.0.txt as CC0-1.0

org.jboss:jandex:2.0.5.Final
 - ERROR: Unknown license URL 'http://repository.jboss.org/licenses/cc0-1.0.txt' is NOT allowed
org.jboss.logging:jboss-logging:3.3.2.Final
 - ERROR: Unknown license URL 'http://repository.jboss.org/licenses/cc0-1.0.txt' is NOT allowed

I don't think we should add this one. It's effectively publishing the license on their own website rather than referencing a canonical URL from SPDX or the creative commons directly. We should implore them to switch to a standard URL.


Publishing of the ports doesn't work after a the container restart.

Bug Description
Finch doesn't publish the ports after restarting the container.
Steps to reproduce

In Terminal run finch run -it -p 3003:80 nginxdemos/hello
In another terminal tab run curl http://localhost:3003/. This should return some HTML
Stop the original docker container by pressing CTRL+C in the finch terminal tab
Start the docker container again by running finch run -it -p 3003:80 nginxdemos/hello. This will print some kind of error in the terminal similar to:

FATA[0000] failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error running hook #0: error running hook: exit status 1, stdout: , stderr: time="2023-01-17T10:56:31Z" level=fatal msg="conflict with ID 8"
Failed to write to log, write /home/tmikus.linux/.local/share/nerdctl/1935db59/containers/finch/29d8289e7ad41be113b94c8738ac2d690ea5aea16f0f9fd047c98e5aa8ee51e0/oci-hook.createRuntime.log: file already closed: unknown
FATA[0000] exit status 1

Start the container again by running finch run -it -p 3003:80 nginxdemos/hello. This should correctly start nginx
In another tab run curl http://localhost:3003/. This will hang and might return curl: (52) Empty reply from server after 30 seconds

Expected behaviour

Finch shouldn't return an error on step 4
Finch should publish the port 3003 on step 6 and should allow for the curl to return a result on step 7

Workaround
Currently, the only workaround I know for this is to restart the finch vm before starting the docker container:
finch vm stop && finch vm start

Thanks for reporting this bug. finch wraps on nerdctl which does most of the "heavy lifting". I noticed this is happening in nerdctl. I have opened an issue in their queue. We will continue with our investigation and post any updates here.

I think there are multiple nuances to this issue, the originally reported issue is not an issue about container restarts, but instead showing an error when creating a new container on the same port of a stopped container. This highlights a couple of bugs, and a different UX to the Docker Engine, so I have gone through multiple scenarios and here are my results:
Tests were carried out on Finch v0.4.0 on MacOS 12.6.3

Starting multiple running containers on the same port should consistently error out. This works as expected for test2 however it lets me start test3. That is a bug, Finch should have prevented test3 from being started.

$ finch run --detach --name test1 --publish 80:80 nginx
9fda2e5bb35edb963c08ab8b81a0af02528725e86b812f2c96b32a5d524fcf41

$ finch run --detach --name test2 --publish 80:80 nginx
FATA[0000] failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error running hook #0: error running hook: exit status 1, stdout: , stderr: time="2023-02-22T10:27:25Z" level=fatal msg="conflict with ID 4"
Failed to write to log, write /home/myuser.linux/.local/share/nerdctl/1935db59/containers/finch/0e05c244b7aa8db0e0cdf01bb3973698d40464102f43410363922a7a78564162/oci-hook.createRuntime.log: file already closed: unknown
FATA[0000] exit status 1

$ finch run --detach --name test3 --publish 80:80 nginx
867fa811b5f52de805d6d46953a41319bb7c721634f7c543799486caa17facd4

$ finch ps -a
CONTAINER ID    IMAGE                             COMMAND                   CREATED           STATUS     PORTS                 NAMES
0e05c244b7aa    docker.io/library/nginx:latest    "/docker-entrypoint.…"    24 seconds ago    Created    <IP_ADDRESS>:80->80/tcp    test2
867fa811b5f5    docker.io/library/nginx:latest    "/docker-entrypoint.…"    19 seconds ago    Up         <IP_ADDRESS>:80->80/tcp    test3
9fda2e5bb35e    docker.io/library/nginx:latest    "/docker-entrypoint.…"    37 seconds ago    Up         <IP_ADDRESS>:80->80/tcp    test1

Attempting to use the same port as a stopped container (recreating the originally reported issue). Here there are 2 issues:

Finch prevents you from starting a new container on the same port as a stopped container. This is a different UX from the Docker Engine were you are able to start a new container on the same port as a stopped container. If we had consistent behavior with the Docker Engine, test2 should have started.

Finch allows you to start a new container on the port of the stopped container via brute force (2 attempts). test3's port is unreachable even though it is started successfully, so I don't believe this 3rd container is properly wired up. This is a bug as Finch should have either prevented test3 from being started, or if it lets test3 start, wire up the networking correctly.

$ finch run --detach --name test1 --publish 80:80 nginx
b0f1a860e060b859b1ded9206e218f3bd3200ba707111be9fe984243e19b55f4

$ finch stop test1
test1

$ finch run --detach --name test2 --publish 80:80 nginx
FATA[0000] failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error running hook #0: error running hook: exit status 1, stdout: , stderr: time="2023-02-22T10:25:24Z" level=fatal msg="conflict with ID 2"
Failed to write to log, write /home/myuser.linux/.local/share/nerdctl/1935db59/containers/finch/50bfe5531cb592704abf835778ebe9d39b25f77e4250fe010c9f00309805ef7f/oci-hook.createRuntime.log: file already closed: unknown
FATA[0000] exit status 1

$ finch run --detach --name test3 --publish 80:80 nginx
39303ebec89e5dac7d6f42c0acfd0f510022d47bbe9884474681d71b55cdfd03

$ finch ps -a
CONTAINER ID    IMAGE                             COMMAND                   CREATED               STATUS                           PORTS                 NAMES
39303ebec89e    docker.io/library/nginx:latest    "/docker-entrypoint.…"    8 seconds ago         Up                               <IP_ADDRESS>:80->80/tcp    test3
50bfe5531cb5    docker.io/library/nginx:latest    "/docker-entrypoint.…"    56 seconds ago        Created                          <IP_ADDRESS>:80->80/tcp    test2
b0f1a860e060    docker.io/library/nginx:latest    "/docker-entrypoint.…"    About a minute ago    Exited (0) About a minute ago    <IP_ADDRESS>:80->80/tcp    test1
$

Just testing a container restart (the title of the issue). This seems to work ok without an issue.

$ finch run --detach --name test1 --publish 80:80 nginx
29305494d261e5206286154d6becb9799e1582fdb8192fb2f0c99bcfb40d203b

$ finch stop test1
test1

$ finch start test1
test1

$ finch ps -a
CONTAINER ID    IMAGE                             COMMAND                   CREATED           STATUS    PORTS                 NAMES
29305494d261    docker.io/library/nginx:latest    "/docker-entrypoint.…"    15 seconds ago    Up        <IP_ADDRESS>:80->80/tcp    test1

However I think there is a related bug here on container restarts. It appears Finch is not freeing up the port when you are stopping / starting the VM. This can be shown when trying to stop / start an existing container after restarting the VM. Through brute force (3 attempts) I can get the container to restart correctly.

$ finch run --detach --name test1 --publish 80:80 nginx
29305494d261e5206286154d6becb9799e1582fdb8192fb2f0c99bcfb40d203b

$ finch ps
CONTAINER ID    IMAGE                             COMMAND                   CREATED               STATUS    PORTS                 NAMES
29305494d261    docker.io/library/nginx:latest    "/docker-entrypoint.…"    About a minute ago    Up        <IP_ADDRESS>:80->80/tcp    test1

# Restart the VM
$ finch vm stop
INFO[0000] Stopping existing Finch virtual machine...
INFO[0002] Finch virtual machine stopped successfully
$ finch vm start
INFO[0000] Starting existing Finch virtual machine...
INFO[0022] Finch virtual machine started successfully

# Container is stopped when the VM  stops.
$ finch ps -a
CONTAINER ID    IMAGE                             COMMAND                   CREATED               STATUS     PORTS                 NAMES
29305494d261    docker.io/library/nginx:latest    "/docker-entrypoint.…"    About a minute ago    Created    <IP_ADDRESS>:80->80/tcp    test1

# Attempt 1
$ finch start test1
FATA[0000] failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error running hook #0: error running hook: exit status 1, stdout: , stderr: time="2023-02-22T10:32:37Z" level=fatal msg="failed to call cni.Setup: plugin type=\"bridge\" failed (add): failed to allocate for range 0: <IP_ADDRESS> has been allocated to finch-29305494d261e5206286154d6becb9799e1582fdb8192fb2f0c99bcfb40d203b, duplicate allocation is not allowed"
Failed to write to log, write /home/myuser.linux/.local/share/nerdctl/1935db59/containers/finch/29305494d261e5206286154d6becb9799e1582fdb8192fb2f0c99bcfb40d203b/oci-hook.createRuntime.log: file already closed: unknown
FATA[0000] exit status 1

# Attempt 2
$ finch start test1
FATA[0000] failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error running hook #0: error running hook: exit status 1, stdout: , stderr: time="2023-02-22T10:32:47Z" level=fatal msg="failed to call cni.Setup: plugin type=\"bridge\" failed (add): failed to set bridge addr: could not set bridge's mac: invalid argument"
Failed to write to log, write /home/myuser.linux/.local/share/nerdctl/1935db59/containers/finch/29305494d261e5206286154d6becb9799e1582fdb8192fb2f0c99bcfb40d203b/oci-hook.createRuntime.log: file already closed: unknown
FATA[0000] exit status 1

# Attempt 3. Success.
$ finch start test1
test1

$ finch ps -a
CONTAINER ID    IMAGE                             COMMAND                   CREATED          STATUS    PORTS                 NAMES
29305494d261    docker.io/library/nginx:latest    "/docker-entrypoint.…"    2 minutes ago    Up        <IP_ADDRESS>:80->80/tcp    test1

Test run on finch version 0.5.0 on macOS 13.2.1
TL;DR: Switching to rootful containerd causes a change in behavior for issues 1 and 2 described in the linked GitHub issue, but these issues are still not resolved. However, issue 4 has been fixed in rootful mode.

Starting multiple running containers on the same port should consistently error out. This works as expected for test2 however it lets me start test3. That is a bug, Finch should have prevented test3 from being started. This is still a bug and it should not allow multiple containers to use the same port.

In rootful containerd even test2 does not complain and is in running state. This is a bug as we don't want multiple containers to try to bind to the same port.
% finch run --detach --name test1 --publish 80:80 nginx
1e09a207bba6b0129c69f88a2a2f2bfe6f4b369a763c12f8272951a34639f469

% finch run --detach --name test2 --publish 80:80 nginx
190d2d5118d2700fd22740875518cc1c22e0203f139fc1e4ad4c079ed0a0facd

 % finch ps -a
CONTAINER ID    IMAGE                             COMMAND                   CREATED               STATUS    PORTS                 NAMES
190d2d5118d2    docker.io/library/nginx:latest    "/docker-entrypoint.…"    About a minute ago    Up        <IP_ADDRESS>:80->80/tcp    test2
1e09a207bba6    docker.io/library/nginx:latest    "/docker-entrypoint.…"    2 minutes ago         Up        <IP_ADDRESS>:80->80/tcp    test1

Attempting to use the same port as a stopped container (recreating the originally reported issue). Here there are 2 issues:

After switching to rootful containerd finch allows you to start a new container on the port of the stopped container without brute force. However the container is not wired correctly and can't be reached from the host.
 % finch run --detach --name test1 --publish 80:80 nginx
689ba20973837da8b825900c38b192264af71082847e831ec943d1d2417ded46
% finch stop test1
test1
 % finch run --detach --name test2 --publish 80:80 nginx
f47bded4b92e5f63ec98c47566e450c4d50d1b72ceeb26d5319df0eed248e870
% curl localhost:80
curl: (7) Failed to connect to localhost port 80 after 17 ms: Connection refused

Just testing a container restart (the title of the issue). This seems to work ok without an issue.

This works fine without any error in rootful mode as well.

However I think there is a related bug here on container restarts. It appears Finch is not freeing up the port when you are stopping / starting the VM. This can be shown when trying to stop / start an existing container after restarting the VM. Through brute force (3 attempts) I can get the container to restart correctly.

This is fixed by rootful.
 % finch vm stop
INFO[0000] Stopping existing Finch virtual machine...
INFO[0006] Finch virtual machine stopped successfully

% finch vm start
INFO[0000] Starting existing Finch virtual machine...
INFO[0050] Finch virtual machine started successfully

 % finch ps -a
CONTAINER ID    IMAGE                             COMMAND                   CREATED           STATUS     PORTS                 NAMES
689ba2097383    docker.io/library/nginx:latest    "/docker-entrypoint.…"    11 minutes ago    Created    <IP_ADDRESS>:80->80/tcp    test1
 % finch start test1
test1


Applications: the applications section needs rework

Description

[x] Should show the list (not summary pies) by default
[x] Show primary ratings in table
[ ] Enhanced filters

Resourcing
We intend to contribute this feature

We will try out slick-grid as an alternative to ui-grid, so we can break our dependence on angular for grid support.

Need to test on

[x] lots of apps (5000+)
[ ] no apps (0)


Improvements in Template add flow

Description

"Import" button should be renamed to "Add".
"File Location" should be renamed to "Template File"
When adding a template with a XML file with errors and clicking Import resets the already added template name.
XML errors in the uploaded file needs to be shown when adding a template.

Thank you for your contribution!
We are closing this issue since it has not been prioritized for a long time. Chances are that it has already been solved in more recent versions. If not, we will be re-evaluating this when it becomes a priority.


Ensure these failures and important events are being logged by osm-controller

Ensure the following events are being logged by osm-controller:

Certs issuance, expiry with any failures
SMI configuration CRUDs with any failures
Addition/removal of namespaces
Changes in ConfigMap

Some of these are already being logged but this list requires an audit and completion of any missing events.

I believe scenarios described in the issue are logged.


Update README URLs based on HTTP redirects

Created with https://github.com/dkhamsing/frankenstein
GitHub Corrected URLs

Was
Now

https://github.com/willwhitney/hydrogen/issues
https://github.com/nteract/hydrogen/issues

https://github.com/willwhitney/hydrogen/wiki/Troubleshooting
https://github.com/nteract/hydrogen/wiki/Troubleshooting

HTTPS Corrected URLs

Was
Now

http://www.freedesktop.org/wiki/Software/pkg-config/
https://www.freedesktop.org/wiki/Software/pkg-config/

Other Corrected URLs

Was
Now

http://continuum.io/downloads
https://www.continuum.io/downloads

https://code.google.com/p/gyp/issues/detail?id=36
https://bugs.chromium.org/p/gyp/issues/detail?id=36

Oh no a bot that needs to rebase!

uh oh indeed

I love all the http -> https bits here.
We do merge quickly, it just happened that I merged another PR that produced conflicts. If you submit again we'll be happy to take it.


Starting HTML

What to do now?

I'm following the HTML on GitHub but I can't seem to move pass step 1 in the course.
I've gone to settings and change the source under 'GitHub Pages' to master but nothing happens after reload.
What's the problem?


[BUG] Get-PnPTenantSite: The property or field 'AuthContextStrength' has not been initialized. It has not been requested or the request has not been executed. It may need to be explicitly requested.

I don't know since when exactly, but recently the command Get-PnPTenantSite started failing with the following error:
The property or field 'AuthContextStrength' has not been initialized. It has not been requested or the request has not been executed. It may need to be explicitly requested.
I have not changed anything in my PS script, nor did I update my PnP.PowerShell module.
Expected behavior
Get-PnPTenantSite should return the tenant site as expected.
Actual behavior

Steps to reproduce behavior
Connect-PnPOnline -Url $variables.Get_Item("AdminUrl") -ClientId $variables.Get_Item("AppClientId") -Tenant $variables.Get_Item("TenantName") -CertificatePath "$($variables.Get_Item("CertificatePath"))" -CertificatePassword $certificatePassword -ErrorAction Stop
Get-PnPTenantSite -Identity "[site url here]" -Detailed

Even without the detailed switch, the same error is thrown.
What is the version of the Cmdlet module you are running?
1.6.0
Which operating system/environment are you running PnP PowerShell on?

[X] Windows
[ ] Linux
[ ] MacOS
[ ] Azure Cloud Shell
[ ] Azure Functions
[ ] Other : please specify

Same issue here, started yesterday afternoon CET.

Same issue.

@erwinvanhunen - Any idea why this command fails? Sorry to PM you, but this is quite blocking for our customers :-(

Same here, from Powershell on my own PC with interactive logon as well as an Azure Automation runbook which is using certificate based logon.

Same here. This Issue seems to be solved by this commit: https://github.com/pnp/powershell/commit/22985f6f3d15c0d23919a24288d7f92a175c2ab9.

it's still giving the same error. it's totally immature and annoying and unprofessional to to such behaviour and cause many vital businesses to fail to be stopped suddenly without any rational !
… terSPList = Get-PnPTenantSite  -Detailed -Filter  "Url -like 'https:/ …
|                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| The property or field 'AuthContextStrength' has not been initialized. It has not been requested or the request has not been executed. It may need to be explicitly requested.

same issue:
[DBG]: PS C:\Users\xxxx> Get-PnPTenantSite -Url $siteUrl
Get-PnPTenantSite : The property or field 'AuthContextStrength' has not been initialized. It has not been requested or the request has not been executed. It may need to be
explicitly requested.
At line:1 char:1

Get-PnPTenantSite -Url $siteUrl

  + CategoryInfo          : WriteError: (:) [Get-PnPTenantSite], PropertyOrField

@fikryGaf - I'm gonna stop you right there.

it's totally immature and annoying and unprofessional to to such behaviour and cause many vital businesses to fail to be stopped suddenly without any rational !

First, in case you didn't know, this is a Community driven repository. This means that we do that on our personal time, and we also have day jobs.
Second, this command is using CSOM in the background, which is not something we - as repo maintainers - are creating. If you have any complaints, please redirect them to Microsoft directly.
Third, a fix has been committed today by @erwinvanhunen & @gautamdsheth, and will be available with the -nightly release tomorrow. Not sure you'll find a plethora of repos with the same turnaround.
And finally, just in case this is still not fast enough for you, you have other alternatives like CSOM or the SharePoint Management Shell.
Hope it clarifies expectations.

Still the same issue, unfortunately
Get-PnPTenantSite : The property or field 'AuthContextStrength' has not been initialized. It has not been requested or
the request has not been executed. It may need to be explicitly requested.
At line:1 char:1
+ Get-PnPTenantSite -Identity "https://tenant.sharepoint.com/team ..."
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : WriteError: (:) [Get-PnPTenantSite], PropertyOrFieldNotInitializedException
    + FullyQualifiedErrorId : EXCEPTION,PnP.PowerShell.Commands.GetTenantSite
PS C:\Users\xxx> Get-Module PnP.PowerShell

ModuleType Version    Name                                ExportedCommands
---------- -------    ----                                ----------------
Manifest   1.6.43     PnP.PowerShell                      {Add-PnPAlert, Add...

Also logging a job with MS

Still the same issue, unfortunately
Get-PnPTenantSite : The property or field 'AuthContextStrength' has not been initialized. It has not been requested or
the request has not been executed. It may need to be explicitly requested.
At line:1 char:1
+ Get-PnPTenantSite -Identity "https://tenant.sharepoint.com/team ..."
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : WriteError: (:) [Get-PnPTenantSite], PropertyOrFieldNotInitializedException
    + FullyQualifiedErrorId : EXCEPTION,PnP.PowerShell.Commands.GetTenantSite
PS C:\Users\xxx> Get-Module PnP.PowerShell

ModuleType Version    Name                                ExportedCommands
---------- -------    ----                                ----------------
Manifest   1.6.43     PnP.PowerShell                      {Add-PnPAlert, Add...

Also logging a job with MS

@kpinel , the build 1.6.43 does not contain Eric's fix (9 hours ago) https://github.com/pnp/powershell/commit/22985f6f3d15c0d23919a24288d7f92a175c2ab9
. We may need to wait for tonight's build?

Confirmed, issue resolved after installing 1.6.44-nightly, using
Install-Module -Name PnP.PowerShell -AllowPrerelease -Force -SkipPublisherCheck

Closing this issue, if you are facing this error please update to the latest 1.6.44-nightly .

Awesome job.. Thanks team...

I second the Awesome Job! Downloaded the update and it is now working as expedcted.
Kudos (and much appreciated)

The fix did solve the issue for Get-PnPTenantSite, but it now throws an error on Invoke-PnPSiteTemplate further on in the code :-(. Thanks for the replies and the quick solution - but the problem shifted towards another command.

@klaaslauwers Is a bug open for Invoke-PnPSiteTemplate ?

@sathya-bhat Nah, I have solved the issue myself. Apparently, there is something wrong with the SupportedUILanguages handler in the template. So I just added -ExcludeHandlers SupportedUILanguages at the end of the command and disabled the multilingual features manually afterwards through:
                        $Web = Get-PnPWeb -Includes IsMultilingual -Connection $newSiteConnection                         $Web.IsMultilingual = $false                         $Web.Update()                         Invoke-PnPQuery


Support wrangler.json configuration file in adapter-cloudflare-workers

Describe the problem
Currently, adapter-cloudflare-workers(2.6.0) only supports wrangler.toml as the configuration file for Cloudflare Workers. If there is only a wrangler.json file in the project, running npm run build will fail because wrangler.toml does not exist. Even if the adapter is configured as:
adapter: adapter({
    config: 'wrangler.json'
})

It does not work because the file is always read using the TOML format.
However, starting from version v3.91.0, Cloudflare Workers also supports wrangler.json as a configuration format. When using wrangler, it automatically searches for wrangler.json if wrangler.toml is not present in the base directory.
For projects with only a wrangler.json file, users are still forced to convert their JSON configuration to TOML, which is tedious and unnecessary.
Describe the proposed solution
The simplest solution is to check the file extension to support both wrangler.toml and wrangler.json. For example:
diff --git a/packages/adapter-cloudflare-workers/index.js b/packages/adapter-cloudflare-workers/index.js
index 8a4f9252d..8bce9848b 100644
--- a/packages/adapter-cloudflare-workers/index.js
+++ b/packages/adapter-cloudflare-workers/index.js
function validate_config(builder, config_file) {
    let wrangler_config;

    try {
+       if (config_file.endsWith(".json")) {
+           wrangler_config = JSON.parse(readFileSync(config_file, 'utf-8'));
+       } else {
            wrangler_config = /** @type {WranglerConfig} */ (
                toml.parse(readFileSync(config_file, 'utf-8'))
            );
+       }
    } catch (err) {
        err.message = `Error parsing ${config_file}: ${err.message}`;
        throw err;
    }
    // rest of the function
}

Additionally, the adapter could automatically detect wrangler.json if wrangler.toml is not specified in the adapter's options or does not exist. This can be achieved by modifying the logic to include:
 function validate_config(builder, config_file) {
+       if (!existsSync(config_file)) {
+            config_file = "wrangler.json"
+       }
        if (existsSync(config_file)) {

Alternatives considered
No response
Importance
nice to have
Additional Information

[Wrangler Configuration](https://developers.cloudflare.com/workers/wrangler/configuration/)
[SvelteKit Adapter for Cloudflare Workers](https://svelte.dev/docs/kit/adapter-cloudflare-workers)

Please feel free to send a PR


Climsoft station api

Merge conflicts are resolved. But the tests are not working yet.

@faysal-ishtiaq could you give a quick updates on which Climsoft tables are now supported and which ones remain?
We can either prioritse the order for implementing the final tables --- or, if all of the main tables that we need are already supported then we may move on to a couple of other issues first.

@isedwards
The following climsoft tables have CRUD:

acquisitiontype
data_forms
flags
obselement
paperarchivedefinition
qcstatusdefinition
qctype
regkeys
station
synopfeature
featuregeographicalposition
instrument
observationfinal
observationinitial
obsscheduleclass
stationelement

There are only a few remaining tables. They will be done by tonight.

@isedwards
just finished till integration tests for all models. starting snapshot tests

@isedwards
just gone through the target tables from test db in opencdms-test-data repository. Now adding more information on read me.

@isedwards
I have just fixed mch db issue. Here is a demo request and response using curl:
04:34:40 faysal@pop-os ~ → curl -X 'GET' \
>   'http://localhost:8000/mch/API/stations' \
>   -H 'accept: application/json' \
>   -H 'Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiJzdHJpbmciLCJleHAiOjE2Mzg2MTQwMzYsInRva2VuX3R5cGUiOiJhY2Nlc3MiLCJqdGkiOiJhZmM5YzU0MzI5NDY0MDA5OWM0ZGVlM2IzNzk1OTFhZSIsInVzZXJfaWQiOjF9.PDk23tWTzUTK-FOsNgcVhZcG9vybp1te1JGsoyg2zRc'

response:

[]


[BadMethodCallException]  Call to undefined method App\Role::create()

i just run command "php artisan db:seed --class=RolesTableSeeder" in my terminal, but isn't work.
it's display error =
[BadMethodCallException]
Call to undefined method App\Role::create()
anyone can help me please...?
this is my code
`<?php
use Illuminate\Database\Seeder;
use App\Role;
use App\User;
class RolesTableSeeder extends Seeder
{
/**
* Run the database seeds.
*
* @return void
*/
public function run()
{
//add role
$roles = [
[
'name' => 'admin',
'display_name' => 'Administration',
'description' => 'Only one and only admin',
],
[
'name' => 'user',
'display_name' => 'Registed User',
'description' => 'Access for registed user',
],
];
    foreach ($roles as $key => $value) {
                Role::create($value);
    }

//add user
$users = [
[
'nama' => 'admin1',
'username' =><EMAIL_ADDRESS>'password' => bcrypt('admin1'),
],
[
'nama' => 'user1',
'username' =><EMAIL_ADDRESS>'password' => bcrypt('user1'),
],
];
$n=1;
foreach ($users as $key => $value) {
$user=User::create($value);
$user->attachRole($n);
$n++;
}
}
}`

I am also facing this issue but with User class, when I add the trait I get call to undefined method App\User::create(). were you able to find out the reason?

I solved this issue when I change the value of CACHE_DRIVER in .env to array (my default value is file).
I hope that it can solve your issue too.

@Khoerintus if i change CACHE_DRIVER = file to CACHE_DRIVER = array, it will get error

Symfony \ Component \ HttpKernel \ Exception \ HttpException No message


Add ability to specify merge behavior of arrays

Sample
var deepmerge = require('deepmerge');

var target = {
  name: 'Fares',
  age: 44,
  favColors: ['red', 'blue', 'green']
};

var source = {
  name: 'Fares',
  age: 44,
  favColors: ['pink', 'yellow', 'white']
};

// Default behavior
var both = deepmerge(target, source, {
  // to specify the behavior of array merging (both, target, source)
  array: 'both'
});

// Include the arrays elements of the target
var target = deepmerge(target, source, {
  array: 'target'
});

// Include the arrays elements of the source
var source = deepmerge(target, source, {
  array: 'source'
});

console.log(JSON.stringify(both, null, 2));
console.log(JSON.stringify(target, null, 2));
console.log(JSON.stringify(source, null, 2));

Output
{
  "name": "Fares",
  "age": 44,
  "favColors": [
    "red",
    "blue",
    "green",
    "pink",
    "yellow",
    "white"
  ]
}
{
  "name": "Fares",
  "age": 44,
  "favColors": [
    "red",
    "blue",
    "green"
  ]
}
{
  "name": "Fares",
  "age": 44,
  "favColors": [
    "pink",
    "yellow",
    "white"
  ]
}

@faressoft hey! I'd love to make you a collaborator so you can merge this and other PRs and roll a new release! Please signup over at https://github.com/KyleAMathews/deepmerge/issues/25 and let's make this happen!

Interesting.  I can see why an option like this would make sense, array merging behavior is pretty subjective.
It's subjective enough that my tendency would be to allow consumers to pass in a merging function, something with a signature like
function(targetElement, sourceElement, index, targetArray, sourceArray) {
}

...and call that function for each element, using whatever value the function returned in the target.
That gives users flexibility in merging arrays, without increasing the complexity of this library's code much at all.
Anyone else have any thoughts?

Please comment on #37, another pull request with a potential solution to this issue.


[SPARK-31619][CORE] Rename config "spark.dynamicAllocation.shuffleTimeout" to "spark.dynamicAllocation.shuffleTracking.timeout"

What changes were proposed in this pull request?
The "spark.dynamicAllocation.shuffleTimeout" configuration only takes effect if "spark.dynamicAllocation.shuffleTracking.enabled" is true, so we should re-namespace that configuration so that it's nested under the "shuffleTracking" one.
How was this patch tested?
Covered by current existing test cases.

cc @vanzin @squito @tgravescs @skonto @dongjoon-hyun @gatorsmile @Ngone51

Test build #122150 has started for PR 28426 at commit ec985fd.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/26821/
Test PASSed.

Thank you for pinging me, @jiangxb1987 .

Thank you @dongjoon-hyun !

Test build #122150 has finished for PR 28426 at commit ec985fd.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/122150/
Test PASSed.

Merged to master and branch-3.0.

Thanks @HyukjinKwon @dongjoon-hyun !


Can not reach https://docker.elastic.co

Problem description
I cloned the repo, issued 'docker compose up setup' but can't reach the mentioned URL and therefore not pull the image.
Error with compose:
[+] Building 30.0s (2/2) FINISHED                                                                                docker:default
 => [elasticsearch internal] load build definition from Dockerfile                                                                                0.0s
 => => transferring dockerfile: 324B                                                                                0.0s
 => ERROR [elasticsearch internal] load metadata for docker.elastic.co/elasticsearch/elasticsearch:8.14.2                                                                                30.0s
------
 > [elasticsearch internal] load metadata for docker.elastic.co/elasticsearch/elasticsearch:8.14.2:
------
failed to solve: docker.elastic.co/elasticsearch/elasticsearch:8.14.2: failed to resolve source metadata for docker.elastic.co/elasticsearch/elasticsearch:8.14.2: failed to do request: Head "https://docker.elastic.co/v2/elasticsearch/elasticsearch/manifests/8.14.2": dial tcp <IP_ADDRESS>:443: i/o timeout

Extra information
I do have multiple other containers running and never had an issue reaching something on the net.

If yes, this was simply a transient error on Elastic's side.

Elastic's Docker registry is up so I'm going to conclude that this was simply a transient error.
If not, either a firewall/proxy or the ISP is blocking that IP range, both cases being IT issues which are unrelated to docker-elk (we are not affiliated with Elastic).


kube-apiserver does not restart after updating kube-apiserver.yaml file

What happened:

updated /etc/kubernetes/manifests/kube-apiserver.yaml file with IRSA config but kube-apiserver does not restart
What you expected to happen:
kube-apiserver should restart

How to reproduce it (as minimally and precisely as possible):

create an eks-anywhere cluster on an EC2 instance
follow this doc to setup an OIDC provider for pod IAM IRSA
add the kube-apiserver flags mentioned here to /etc/kubernetes/manifests/kube-apiserver.yaml

Anything else we need to know?:
Environment:

AWS Region: us-west-2
EKS Platform version (1.21, using EKS-Anywhere)
Kubernetes version (1.21)

cluster config:
apiVersion: anywhere.eks.amazonaws.com/v1alpha1
kind: Cluster
metadata:
  name: test-cluster
spec:
  clusterNetwork:
    cniConfig:
      cilium: {}
    pods:
      cidrBlocks:
      - <IP_ADDRESS>/16
    services:
      cidrBlocks:
      - <IP_ADDRESS>/12
  controlPlaneConfiguration:
    count: 1
  datacenterRef:
    kind: DockerDatacenterConfig
    name: test-cluster
  kubernetesVersion: "1.21"
  managementCluster:
    name: test-cluster
  workerNodeGroupConfigurations:
  - count: 3
    name: md-0

---
apiVersion: anywhere.eks.amazonaws.com/v1alpha1
kind: DockerDatacenterConfig
metadata:
  name: test-cluster
spec: {}

command ran to create the cluster eksctl anywhere create cluster -f test-cluster.yaml
more context: basically I'm trying to enable IRSA on the pods so that they can assume IAM roles on my EKS-Anywhere cluster running on EC2 instance.
The document here  is not very clear, it says that I need to add those flags but doesn't say where exactly those flags need to be added.
I restarted kubelet and containerd and I still don't see kube-apiserver come up, it just get's killed when I update the kube-apiserver.yaml
I add the following config:
args:
 - --api-audiences="sts.amazonaws.com"
 - --service-account-key-file="/etc/kubernetes/sa-pkcs8.pub"
 - --service-account-signing-key-file="/etc/kubernetes/sa.priv"
 - --service-account-issuer="https://s3-us-west-2.amazonaws.com/$S3_BUCKET"

volumes:
    name: sa-pub
   - hostPath:
      path: /etc/kubernetes/sa-pkcs8.pub
      type: File
    name: sa-pkcs8-pub
   - hostPath:
      path: /etc/kubernetes/sa.priv
      type: File
    name: sa-priv

volumemounts:
    - mountPath: /etc/kubernetes/sa-pkcs8.pub
      name: sa-pkcs8-pub
    - mountPath: /etc/kubernetes/sa.priv
      name: sa-priv

files sa.priv and sa-pkcs8.pub are manually added to the control plane node (docker container)

You didn't share your machine configs. Bottlerocket?

@TerryHowe
I'm using the publicly available AMI ubuntu/images/hvm-ssd/ubuntu-focal-20.04-amd64-server-20221212 (ami-0d31d7c9fc9503726)

I restarted kubelet and containerd and I still don't see kube-apiserver come up, it just get's killed when I update the kube-apiserver.yaml

If I understand correctly, the kube-apiserver pod is created but keeps restarting? Can you provide logs and kubectl describe pod output?

I restarted kubelet and containerd and I still don't see kube-apiserver come up, it just get's killed when I update the kube-apiserver.yaml

If I understand correctly, the kube-apiserver pod is created but keeps restarting? Can you provide logs and kubectl describe pod output?

No, it does NOT come up after I update the kube-apiserver.yaml file, that's the problem

I just spoke with AWS support and found out that eks-anywhere ON EC2 instances is not technically supported by AWS.

I'll leave it up to you guys to keep the ticket open/close

While true EKS-A is not supported on EC2, the docker provider which you are using is meant for testing on al2 or even Macs.  For OIDC specifically, you should be able to make that work following our doc. With those values set in your cluster.yaml correctly, you should see the generated kube-apiserver.yaml have the required flags. Directly modifying the static pod yamls in the EKS-A world is not really intended to work and would not be persisted through upgrades and what not.


Can I delete the STX address that the sandbox generates and generate a new one?

Please review the existing enhancement issues at the link below before creating a new one to ensure you do not create a duplicate request.
If you see an existing enhancement issues please comment on the issue or upvote the issue with a :thumbsup:
Is your feature request related to a problem? Please describe.
Can I delete the STX address that the sandbox generates and generate a new one?

Describe the solution you'd like
Would I be able to still see the button to generate a new address?
Describe alternatives you've considered
Is there a button to remove this address?
Additional context
This may just be weird functionality I am seeing on testnet, please let me know if this is a testnet issue only, and this works better on mocknet.

This feature is not implemented and not planned for. Ultimately the sandbox will use blockstack for the address etc. So it would all be handled there. I'm going to close this ticket for now.


test test branch-2.0's ci, do not merge it

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 47.66 seconds
stream load tsv:          583 seconds loaded<PHONE_NUMBER>9 Bytes, about 122 MB/s
stream load json:         19 seconds loaded<PHONE_NUMBER> Bytes, about 118 MB/s
stream load orc:          64 seconds loaded<PHONE_NUMBER> Bytes, about 16 MB/s
stream load parquet:          31 seconds loaded 861443392 Bytes, about 26 MB/s
insert into select:          29.6 seconds inserted 10000000 Rows, about 337K ops/s
storage size:<PHONE_NUMBER>1 Bytes


Add Yuriita::Search to allow custom param_keys

This allows a user to define any param_key value and then call
table.search.x, where x is the param_key, in order to retrieve the input
string. The search object was necessary in order to avoid conflicts if
the user defines param_key to be the name of a method that already
exists on Yuriita::Table.

Nice 👍 I take it this doesn't change the parameters that get submitted to the server?

If you mean that it doesn't change the developer defined param_key to q, then nope. If you define a param_key of query, the input will always be sent as query to the server and the param string will always contain query.

Ah sorry, I meant the hash of params submitted to the server from the form hasn't changed.
It's still
{ query: "some:string" }

and not
{ search: { query: "some:string" } }

This hasn't added any nesting from what I can see, right?

Ah! Yup, it's unchanged.


Allow to use existing secret to securely set credentials

Proposed changes
At the time of writing it was not possible to use an existing secret to bypass the plaintext credentials in the values.yaml. The change introduces the possibility to use an existing secret to read the credentials from. This allows the user to
Checklist

[x] Lint and unit tests pass locally with my changes.
[ ] I have added tests that prove my fix is effective or that my feature works.
[x] I have added documentation to describe my feature.
[x] I have squashed my commits into logic units.
[x] I have described the changes in the commit messages.

Merged, thanks for your contribution!


Attempt authing two times before failing

This should fix https://github.com/speric/kindle-highlights/issues/11
@speric

Bump @speric ^

👍 Thanks!


i don't know how to open Index.cshtml from command prompt.

Problem encountered on https://dotnet.microsoft.com/learn/aspnet/hello-world-tutorial/modify
Operating System: windows
Provide details about the problem you're experiencing. Include your operating system version, exact error message, code sample, and anything else that is relevant.

You need to open the file with a text editor. The tutorial says it explicitly:

Open Pages/Index.cshtml in any text editor
I'll close the issue since this question is resolved.


could not get user all tweets

i am using below code :
$settings = array(
'oauth_access_token' => "",
'oauth_access_token_secret' => "",
'consumer_key' => "",
'consumer_secret' => ""
);
$requestMethod = 'GET';
$url1="https://api.twitter.com/1.1/statuses/user_timeline.json";
$sc_name = 'DailyRapPics';
$count ='3200';
$getfield = '?screen_name='.$sc_name.'&exclude_replies=false&include_rts=true&contributor_details=true&count='.$count;

$twitter = new TwitterAPIExchange($settings);
$tweets  = $twitter->setGetfield($getfield)->buildOauth($url1, $requestMethod)->performRequest();
echo '';
$tweetarray = json_decode($tweets);
print_r($tweetarray);
echo '';
but it return only 200 tweets but this user have 470 tweets what am i missing

The documentation states:

count (optional): Specifies the number of tweets to try and retrieve, up to a maximum of 200 per distinct request.

yeah i want to get tweets more that 200 say 400 can you please do it form me i will pay you $5 please help i need it

hey please tell how can i get since_id and max_id

Grab 200, get the timestamp of the last one and make a second (or as many as you need) passing the last timestamp to since_id.
You could make a wrapper to just loop until the whole timeline is loaded. If you are doing this, make sure to not make the request too often, cache and get "updates" to the timeline using since_id of the last tweet you cached.
Hope that helps.


Fix build with latest zxing-cpp master sources (release 1.2.0)

Update SCodes.pri headers and sources to match latest zxing-cpp version (release 1.2.0).
https://github.com/nu-book/zxing-cpp/commit/2dad8be2466a2bd46037267d9f0e728e08b79140
Using Screen QML type requires importing QtQuick Window module in ScannerPage.qml
W libQmlBarcodeReader_armeabi-v7a.so: qrc:/qml/ScannerPage.qml:12: ReferenceError: Screen is not defined
W libQmlBarcodeReader_armeabi-v7a.so: qrc:/qml/ScannerPage.qml:10: ReferenceError: Screen is not defined

Thank you. I also updated the submodule version on the master branch.


Reduce memory allocation when diff'ing large manifests

With latest kapp-controller v0.48.1 (and related kapp version) we face the following issue:
We have an app with large manifests (based on https://github.com/prometheus-community/helm-charts/tree/main/charts/kube-prometheus-stack), namely about 4.4MB of manifest files. When we release a new version of this app, and say all labels do change, so the diff is large, kapp seems to allocate so much memory, that it crashed on our system with 4GB of memory allocated for the container (Reconcile failed: Deploying: signal: killed). After providing about 7GB of memory (limits), it finally could reconcile successfully.

This issue is about tracking this issue, and improving upon the memory allocation required for large diffs.
As @praveenrewar wrote:

The total memory allocation is almost 3 times when there is diff vs when there is no diff. I will try to look into it, meanwhile I think you should be able to reduce the memory limits for the container, unless you are planning to bump the helm chart version again. Also, feel free to create an issue on GitHub for tracking the progress.

Related Slack channel: https://kubernetes.slack.com/archives/CH8KCCKA5/p1686575635485759
(maybe also relates to https://github.com/carvel-dev/kapp/issues/599 ?)

We did some memory optimization as part of #863. Most of it is enabled by default. One optimization is feature gated. We have introduced a new flags --diff-anchored, this uses a different algorithm to compute diff between existing and new resources which consumes less memory, however the diff produced is also different from before, hence we haven't enabled it by default.
This flag has been enabled in kapp-controller starting kapp-controller v0.51.0, and it can be enabled via the kapp raw opts in kapp-controller configuration or in the package/app.


[Bug]: Overrides ssh key in ~/.ssh/authorized_keys when generating an ssh key

Description
so i'm using a vps that only allows to put an ssh key once while installing the os for the first time through their gui.
i put my public key ~/.ssh/id_rsa.pub in the server's authorized keys ~/.ssh/authorized_keys & i got access to the machine.
but then i installed coolify. when onboarding, i put my already existing ssh key but i got an error for some reason. maybe bcz i didn't put the last parts of my ssh key which is just myname@desktopname which i learned isn't needed at all. maybe that's why i got the error idk.
but then i thought maybe i'll let coolify generate an ssh key & it went successfully. however, i wasn't able to ssh into my remote server anymore. maybe coolify overrided the ssh key in authorized_keys instead of appending?
all i know is it worked before installing coolify onboarding.
Minimal Reproduction (if possible, example repository)
n/a
Exception or Error
n/a
Version
n/a

i don't think so, the key seems to be appended
https://github.com/coollabsio/coolify/blob/6b751f965bb6deab3423b74511451089e06f3d37/scripts/install.sh#L174

yeah, i did see it was indeed appended once i reinstalled another os.
im curious why the onboarding gave me error of public key denied when i entered my private key? i had to skip the onboarding flow to get it working.
if i generate ssh key during onboarding, it stopped working for some reason tho. idk why?

i understood that i need 2 ssh keys:
one for accessing server from my local computer & another one for coolify to access it.
there's an issue somewhere but i'm unable to pin-point it as i dont really understand devops that much so i'll close this one for now.
hopefully, i never face such issue again.


Return the updated doc in the result

Instead of just returning a result like
{
  rev: '2-x',
  updated: true
}

We should return:
{
  rev: '2-x',
  updated: true,
  doc: {/* ... */}
}

where doc is the newly updated document. We need this for https://github.com/pouchdb/mapreduce/pull/250

+1

Nah


feat(protocol): support for ERC1155 airdrop

This PR adds support for ERC1155 token airdrops, enhancing its versatility alongside existing ERC20 and ERC721 functionalities. This addition enhances the protocol, accommodating a wider range of token standards for airdrop distribution.

Yeah sure, I thought it would be a good extension to have it under protocol when we have an existing support for ERC721 & ERC20.


The last of the badge examples

With the v3 services, I extended the services after exporting them. With the v2 services, a simpler approach seemed possible so I went with that. PowerShell is an independent badge, so that one was straightforward.
Blocking further refactoring work on badge examples.

Warnings

:warning:
This PR modified service code for chocolatey but not its test code. That's okay so long as it's refactoring existing code.

:warning:
This PR modified service code for myget but not its test code. That's okay so long as it's refactoring existing code.

:warning:
This PR modified service code for nuget but not its test code. That's okay so long as it's refactoring existing code.

:warning:
This PR modified service code for powershellgallery but not its test code. That's okay so long as it's refactoring existing code.

:warning:
This PR modified service code for resharper but not its test code. That's okay so long as it's refactoring existing code.

Messages

:book:
:sparkles: Thanks for your contribution to Shields, @paulmelnikow!

:book:
Thanks for contributing to our documentation. We :heart: our [documentarians](http://www.writethedocs.org/)!

  Generated by :no_entry_sign: dangerJS


KAFKA-14589 [2/3] Tests of ConsoleGroupCommand rewritten in java

This PR is part of #14471
Is contains some of ConsoleGroupCommand tests rewritten in java.
Intention of separate PR is to reduce changes and simplify review.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

Hello @mimaison @jolshan
Can you, please, take a look?

Hello @showuon @jolshan @mimaison
Can you, please, take a look?

Hello, @rreddy-22 @dajac
Can you, please, take a look at these changes?
It PR moves DescribeConsumerGroupTest and ResetConsumerGroupOffsetTest as part of moving ConsoleGroupCommand to tools.
Having it in trunk will reduce your work while improving ConsoleGroupCommand (no need to duplicate test changes in java and scala) and help moving command to tools.
Big PR where all command code rewritten in java - #14471
Right now, changes in ConsoleGroupCommand leads to conflicts in my PR which is hard to resolve.

Hello @chia7712
Please, take a look.
If this patch to big to review I can split it to two.
WDYT?

If this patch to big to review I can split it to two.

please :)

@chia7712 Done.

@chia7712
Other PR is #15465
Seems, PR's are reviewable now.
Please, take a look.

@chia7712 This PR ready for review.
Please, take a look.

@nizhikov Thanks for the review.
All your comments fixed.
Please, take a look one more time.

the failed tests pass on my machine.
./gradlew cleanTest core:test --tests ReplicaManagerTest --tests LogDirFailureTest

will merge it

@nizhikov thanks for this nice patch


Points projections & Viewer features

This PR adds the Measurement type : a measured quantity can be a 2D keypoint, a GPS position, IMU angle or surveyed GCP. In this PR, we did the following :

Use Measurement type for describing 2D keypoints of reconstructed 3D points, that further allow for a complete scene geometry description.
Added point filtering by their # of projection using the above.
Added display of the camera connection graph using the first.

As a down-side, it makes the JSON files much heavier : Firefox might struggle at read > 200 Mb files (but Chrome can).

Closing, will not be merged.


Flutter Gradle imperative apply deprecation docs missing step

Steps to reproduce

See error message on app start about deprecated Gradle imperative apply in Flutter 3.19
Visit the suggested docs and follow the instructions
After following the doc instructions, app will not start and instead shows this error:

FAILURE: Build failed with an exception.

* Where:
Build file '/Users/yuzhshen/dev/curati/android/app/build.gradle' line: 68

* What went wrong:
A problem occurred evaluating project ':app'.
> Could not get unknown property 'kotlin_version' for object of type org.gradle.api.internal.artifacts.dsl.dependencies.DefaultDependencyHandler.

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 636ms
Running Gradle task 'assembleDebug'...                           1,134ms
Error: Gradle task assembleDebug failed with exit code 1

Expected results
Expected following the docs to result in clean run.
Actual results
Following the docs resulted in error. To get a clean run, I also needed to delete the android/app/build.gradle code block referenced in the startup error:
dependencies {
    implementation "org.jetbrains.kotlin:kotlin-stdlib-jdk7:$kotlin_version"
}

Code sample
N/A, documentation related
Screenshots or Video

Screenshots / Video demonstration
[Upload media here]

Logs
Logs
[Paste your logs here]

Flutter Doctor output
Doctor output
[Paste your output here]

i suggest trying to put the literal $kotlin_version because in the legacy methode this was defined in the top of the file now it's inside settings.gradle you can find there the kotlin version ypu need or try to delete this line and clean the run again

I understand that the reason kotlin_version is not found is because I deleted the buildscript block (as described in the official docs) that defines it. But it's still not clear to me whether I did the right thing by deleting the following block, or if I should have introduced a new kotlin_version variable:
dependencies {
    implementation "org.jetbrains.kotlin:kotlin-stdlib-jdk7:$kotlin_version"
}

I feel that this is something that the docs should clarify.

@auradigitaldev
i think u'r right and this should be added to the docs
have you solved you problem if you did i suggest you post the solution for anyone in the near future having the same issue can find this solution helpfull .

As I mentioned in the original post, I solved the error message by deleting this code block:
dependencies {
    implementation "org.jetbrains.kotlin:kotlin-stdlib-jdk7:$kotlin_version"
}

However, I would like clarification from the Flutter team on if this is the right way to solve the issue or if it secretly breaks something. And I believe this should be added to the docs.

Thanks for the report. I'll keep the issue open and label for team's input / tracking as documentation issue.

This is useful, it must be mentioned in the docs.

As I mentioned in the original post, I solved the error message by deleting this code block:
dependencies {
    implementation "org.jetbrains.kotlin:kotlin-stdlib-jdk7:$kotlin_version"
}

However, I would like clarification from the Flutter team on if this is the right way to solve the issue or if it secretly breaks something. And I believe this should be added to the docs.

Thank you

In my case I had ext.kotlin_version = '1.8.0'
So I've just replaced in the file android/app/build.gradle:
dependencies {     implementation "org.jetbrains.kotlin:kotlin-stdlib-jdk7:$kotlin_version" }
with
dependencies {     implementation "org.jetbrains.kotlin:kotlin-stdlib-jdk7:1.8.0" }
After that it built and run fine.

But it's still not clear to me whether I did the right thing by deleting the following block, or if I should have introduced a new kotlin_version variable:
dependencies {
    implementation "org.jetbrains.kotlin:kotlin-stdlib-jdk7:$kotlin_version"
}

I feel that this is something that the docs should clarify.

Yes, this block is safe to remove. The reason it wasn't included in the docs is that it was actually removed earlier from the templates - so when testing the change to create the linked docs, the pre-migration files already did not contain that block.
Realistically, the template Gradle files have changed enough that we can't provide accurate instructions for every possible setup. But that specific removal landed only days before the PR that deprecated the imperative apply, and so that block definitely warrants a mention in the migration docs. I'll make sure the docs get updated

Closing as the docs have been updated


Native Windows support

We recommend people to use WSL, but there the CLI does work on Windows (with some bugs). If there's sufficient demand, let's fix up the issues to make native Windows a supported platform.

FWIW, turso-cli runs perfectly fine on my WSL2 (e.g., I don't face missing urls from https://github.com/chiselstrike/turso-cli/issues/259), I installed via curl and are on Linux XXX <IP_ADDRESS>-microsoft-standard-WSL2
Looking at VS Code and all those remote extensions from Microsoft supporting developing in WSL2, I assume that developing in WSL2 on Windows is kinda of the default nowadays.

developing in WSL2 on Windows is kind of the default nowadays (unless you do native Windows software).

It may be the default for some, but I - I know for certain I am not alone - usually have more than enough with git-bash.
Install and use WSL only for Turso is kinda "heavy"!

Noticed this too when wanting to try out turso. I would prefer not to use WSL since I don't use it for anything else.

Is there an update for this? I really don't want to install so many dependencies just to connect to my DB.

We're currently busy wrapping up other work. We will take this issue into consideration when planning future work. Sorry for the inconvenience.

Noticed this too when wanting to try out turso. I would prefer not to use WSL since I don't use it for anything else.

same here :(

I don't use anything else either. Would love a native Windows installation.
Or winget/scoop support.
I can't even find a way to install turso without opening Git Bash.
Only use Powershell nowadays.
This should be prioritized tbh.

Is there a way to create a database without being able to install turso-cli?
I can't find anything in dashboard.
ps: the profile pic footer overlaps with everything. some css issue that makes me unable to click on those 4-5 items like settings, logout.

Same here. This is really annoying, would love MINGW64 support being implemented.

Still an issue and is what's discouraging me from buying a Turso plan :(

i've activated WSL2 on my Windows 10 system and tried install Turso CLI using command in the quickstart:
curl -sSfL https://get.tur.so/install.sh | bash

but I get this error message:
curl: (6) Could not resolve host: get.tur.so

No issue at all when I'm on my Linux system though...but sometimes I need to do something from Windows.
Also I tried the same command in Windows without WSL:
curl: (6) Could not resolve host: github.com

Seems to be a problem connecting to the source?

Any update for this?
The command curl -sSfL https://get.tur.so/install.sh -o install.sh is not working on Windows

@haaawk @penberg Are there plans to natively support Windows? What are the blockers currently? This is precluding experimentation by a large chunk of potential customers.


[BUG]: New 16/11/2020 PowerBI dashboard Microsoft Teams Environments is blank

Describe the bug
A clear and concise description of what the bug is.
Component (please tell us which flow or app you are experiencing issues with):

Solution [e.g. Core, Nurture]  CORE
Version [e.g. 1.29]  1.71
App or Flow [e.g. Sync Template (v2)]  POwerBI

To Reproduce
Steps to reproduce the behavior:

run Sync flows
Start PowerBI desktop
Show Dashboard-PowerPlatformAdminDashboard-2020-11-16

Expected behavior
AI expect to see some Microsoft Teams Environments.  The Environments Tab says there are 4 Microsoft Teams Envionments.  The Microsoft Teams Environments is blank.
Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

It appears that the issue is with the filter on the first screen you show.
Please change that filter as shown here to see if you have teams environments. You'll need to change it for the other environments on this page as well.

Thanks for spotting this, Nigel! I uploaded a new version just now that should have this filter fixed - here's a direct link to the new version: https://github.com/microsoft/powerapps-tools/raw/master/Administration/CoEStarterKit/Individual Components/Dashboard-PowerPlatformAdminDashboard-2020-11-16.pbit

Closing this, but let me know if you spot any other issues! Thank you!

Hi Manuela
I have just downloaded the version you created 40 ish minutes ago.
The environments tab now says there are no Microsoft Teams environments :-
<EMAIL_ADDRESS>There are still no environments in the Microsoft Teams Environments Tab either.
Regards
Nigel
From: Manuela Pichler<EMAIL_ADDRESS>Sent: 17 November 2020 11:02
To: microsoft/powerapps-tools<EMAIL_ADDRESS>Cc: Nigel Price<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [microsoft/powerapps-tools] [BUG]: New 16/11/2020 PowerBI dashboard Microsoft Teams Environments is blank (#573)
Thanks for spotting this, Nigel! I uploaded a new version just now that should have this filter fixed - here's a direct link to the new version: https://github.com/microsoft/powerapps-tools/raw/master/Administration/CoEStarterKit/Individual Components/Dashboard-PowerPlatformAdminDashboard-2020-11-16.pbit
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/powerapps-tools/issues/573#issuecomment-728853964, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACAXJUCWCT72LZS3HZZN2JLSQJJ2VANCNFSM4TXX6KDA.

If you go to aka.ms/ppac > Environments and filter by Microsoft Teams, do you see any Teams environments there?

Yes – I have 2 Teams type environments
From: Manuela Pichler<EMAIL_ADDRESS>Sent: 17 November 2020 12:31
To: microsoft/powerapps-tools<EMAIL_ADDRESS>Cc: Nigel Price<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [microsoft/powerapps-tools] [BUG]: New 16/11/2020 PowerBI dashboard Microsoft Teams Environments is blank (#573)
If you go to aka.ms/ppac > Environments and filter by Microsoft Teams, do you see any Teams environments there?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/powerapps-tools/issues/573#issuecomment-728896106, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACAXJUG4S3N333ZHD5KYF7TSQJUILANCNFSM4TXX6KDA.

Ah, I think I know what's happening here!

What version of the Core components solution are you on?
If you navigate to the Core Components solution and edit the Admin | Sync Template v2, scroll down a bit to the Get Environments action (it's within a scope). Click on "Show advanced options". Does that show 2020-09-01 as the API Version or something lower? Earlier versions of the API don't return Microsoft Teams as the Environment Type, but instead return NotSpecified which is what leads me to think that this is the issue as in your BI screenshot I can see NotSpecified.

If you are seeing an earlier version here, please upgrade to the latest version of the Core components that we also released yesterday.
Before you upgrade, please make sure to remove any unmanaged layers you might have on flows in the solution - if you have unmanaged layers (= that means you've made customizations to the flow), the upgrade won't take effect.
The screenshots here take you through how to check for unmanaged layers, and remove them.
https://docs.microsoft.com/en-us/power-platform/guidance/coe/setup#installing-updates

(re-opened the issue to investigate what's happening here)

When I downloaded the pbit file last night the Environmenst screen was working and at the top it said I had two Microsoft Teams Envvironments.  It was only when I downloaded the version an hour ago it disappeared.  But the Microsoft Teams Tab never worked.
From: Manuela Pichler<EMAIL_ADDRESS>Sent: 17 November 2020 12:46
To: microsoft/powerapps-tools<EMAIL_ADDRESS>Cc: Nigel Price<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [microsoft/powerapps-tools] [BUG]: New 16/11/2020 PowerBI dashboard Microsoft Teams Environments is blank (#573)
Ah, I think I know what's happening here!

What version of the Core components solution are you on?
If you navigate to the Core Components solution and edit the Admin | Sync Template v2, scroll down a bit to the Get Environments action (it's within a scope). Click on "Show advanced options". Does that show 2020-09-01 as the API Version or something lower? Earlier versions of the API don't return Microsoft Teams as the Environment Type, but instead return NotSpecified which is what leads me to think that this is the issue as in your BI screenshot I can see NotSpecified.
[image]https://user-images.githubusercontent.com/55705669/99391481-27265980-28d2-11eb-8c8f-3226441d6e31.png

If you are seeing an earlier version here, please upgrade to the latest version of the Core components that we also released yesterday.
Before you upgrade, please make sure to remove any unmanaged layers you might have on flows in the solution - if you have unmanaged layers (= that means you've made customizations to the flow), the upgrade won't take effect.
The screenshots here take you through how to check for unmanaged layers, and remove them.
https://docs.microsoft.com/en-us/power-platform/guidance/coe/setup#installing-updates
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/powerapps-tools/issues/573#issuecomment-728904111, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACAXJUC623Q474R5354RCCTSQJV7VANCNFSM4TXX6KDA.

Core Components version = 1.71
<EMAIL_ADDRESS>Uh Uh !
From: Manuela Pichler<EMAIL_ADDRESS>Sent: 17 November 2020 12:46
To: microsoft/powerapps-tools<EMAIL_ADDRESS>Cc: Nigel Price<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [microsoft/powerapps-tools] [BUG]: New 16/11/2020 PowerBI dashboard Microsoft Teams Environments is blank (#573)
Ah, I think I know what's happening here!

What version of the Core components solution are you on?
If you navigate to the Core Components solution and edit the Admin | Sync Template v2, scroll down a bit to the Get Environments action (it's within a scope). Click on "Show advanced options". Does that show 2020-09-01 as the API Version or something lower? Earlier versions of the API don't return Microsoft Teams as the Environment Type, but instead return NotSpecified which is what leads me to think that this is the issue as in your BI screenshot I can see NotSpecified.
[image]https://user-images.githubusercontent.com/55705669/99391481-27265980-28d2-11eb-8c8f-3226441d6e31.png

If you are seeing an earlier version here, please upgrade to the latest version of the Core components that we also released yesterday.
Before you upgrade, please make sure to remove any unmanaged layers you might have on flows in the solution - if you have unmanaged layers (= that means you've made customizations to the flow), the upgrade won't take effect.
The screenshots here take you through how to check for unmanaged layers, and remove them.
https://docs.microsoft.com/en-us/power-platform/guidance/coe/setup#installing-updates
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/powerapps-tools/issues/573#issuecomment-728904111, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACAXJUC623Q474R5354RCCTSQJV7VANCNFSM4TXX6KDA.

If you included an image, that didn't come through now!
Can you check on the Admin | Sync Template v2 flow that you don't have any unmanaged layers?

Can I change the API Version to 2020-09-01 simply by editing the field ??
From: Manuela Pichler<EMAIL_ADDRESS>Sent: 17 November 2020 12:46
To: microsoft/powerapps-tools<EMAIL_ADDRESS>Cc: Nigel Price<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [microsoft/powerapps-tools] [BUG]: New 16/11/2020 PowerBI dashboard Microsoft Teams Environments is blank (#573)
Ah, I think I know what's happening here!

What version of the Core components solution are you on?
If you navigate to the Core Components solution and edit the Admin | Sync Template v2, scroll down a bit to the Get Environments action (it's within a scope). Click on "Show advanced options". Does that show 2020-09-01 as the API Version or something lower? Earlier versions of the API don't return Microsoft Teams as the Environment Type, but instead return NotSpecified which is what leads me to think that this is the issue as in your BI screenshot I can see NotSpecified.
[image]https://user-images.githubusercontent.com/55705669/99391481-27265980-28d2-11eb-8c8f-3226441d6e31.png

If you are seeing an earlier version here, please upgrade to the latest version of the Core components that we also released yesterday.
Before you upgrade, please make sure to remove any unmanaged layers you might have on flows in the solution - if you have unmanaged layers (= that means you've made customizations to the flow), the upgrade won't take effect.
The screenshots here take you through how to check for unmanaged layers, and remove them.
https://docs.microsoft.com/en-us/power-platform/guidance/coe/setup#installing-updates
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/powerapps-tools/issues/573#issuecomment-728904111, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACAXJUC623Q474R5354RCCTSQJV7VANCNFSM4TXX6KDA.

Unfortunately not, the schema of the output has changed between API versions (some fields have different names, on some fields the structure of data is different) so we had to make some changes further down as well when we insert / update environments into  the Dataverse table.

<EMAIL_ADDRESS>From: Manuela Pichler<EMAIL_ADDRESS>Sent: 17 November 2020 12:55
To: microsoft/powerapps-tools<EMAIL_ADDRESS>Cc: Nigel Price<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [microsoft/powerapps-tools] [BUG]: New 16/11/2020 PowerBI dashboard Microsoft Teams Environments is blank (#573)
If you included an image, that didn't come through now!
Can you check on the Admin | Sync Template v2 flow that you don't have any unmanaged layers?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/powerapps-tools/issues/573#issuecomment-728908638, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACAXJUHYNT5DDS364LBTSD3SQJXC7ANCNFSM4TXX6KDA.

In the latest version there are lots of connection references which is playing havoc with my DLP –
<EMAIL_ADDRESS>I think some of them are hangovers from when the Solution was developed.
From: Manuela Pichler<EMAIL_ADDRESS>Sent: 17 November 2020 12:57
To: microsoft/powerapps-tools<EMAIL_ADDRESS>Cc: Nigel Price<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [microsoft/powerapps-tools] [BUG]: New 16/11/2020 PowerBI dashboard Microsoft Teams Environments is blank (#573)
Unfortunately not, the schema of the output has changed between API versions (some fields have different names, on some fields the structure of data is different) so we had to make some changes further down as well when we insert / update environments into the Dataverse table.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/powerapps-tools/issues/573#issuecomment-728909698, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACAXJUCIBSCVIGTL2RFSGSLSQJXK5ANCNFSM4TXX6KDA.

Unfortunately, screenshots aren't coming through when you reply via email - can you go straight to https://github.com/microsoft/powerapps-tools/issues/573 and add them here.
There may be a few connection references for the same connector, as there is a limit of how many connections a connection reference can support so we had to duplicate some. But as they are all for the same connector, this shouldn't have an impact on your DLP policy.
However, we did add the Microsoft Teams connector to the sync flows to gather further information about Microsoft Teams environments - that one is new, and included for the first time with this release. I think that's the only connector we added new, so maybe this is the one causing issues if it's not yet included in your DLP policy.

Hi Manuela
Ended up trashing all of my DLPs and flow now works.
Removed all non-manged layers from all of the Flows.
Re-Imported the Solution 1.71.1
All now works !
Thanks for your help.
I would have never found the unmanaged layers issue if you had not told me.
Thanks Again
Nigel
From: Manuela Pichler<EMAIL_ADDRESS>Sent: 17 November 2020 14:08
To: microsoft/powerapps-tools<EMAIL_ADDRESS>Cc: Nigel Price<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [microsoft/powerapps-tools] [BUG]: New 16/11/2020 PowerBI dashboard Microsoft Teams Environments is blank (#573)
Unfortunately, screenshots aren't coming through when you reply via email - can you go straight to #573https://github.com/microsoft/powerapps-tools/issues/573 and add them here.
There may be a few connection references for the same connector, as there is a limit of how many connections a connection reference can support so we had to duplicate some. But as they are all for the same connector, this shouldn't have an impact on your DLP policy.
However, we did add the Microsoft Teams connector to the sync flows to gather further information about Microsoft Teams environments - that one is new, and included for the first time with this release. I think that's the only connector we added new, so maybe this is the one causing issues if it's not yet included in your DLP policy.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/powerapps-tools/issues/573#issuecomment-728951066, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACAXJUCIIASD6MBGIO4ZCIDSQJ7SJANCNFSM4TXX6KDA.

YAY! And you are seeing Microsoft Teams environments in the Power BI Dashboard as well now?
Not related to the CoE kit itself, but for info - with the old solution import experience, you had the option to "override customizations" which then got rid of your unmanaged layer as part of the import. This often led to issues as some customers selected this but didn't know it would remove their customizations hence with the modern solution import experience, this option was removed and customers are now responsible for making sure their solution is "ready" to receive the upgrade.
There are a few items on the roadmap to make this easier and add notifications during the import on flows that have customizations and thus won't receive the upgrade etc! The team is going to continue investing and working on making this experience easier.
Closing this issue now but please let us know if you continue to experience other issues!

Hi Manuela
Yes, all working now.
Lets see what happens when I recreate my DLPs.
Thanks for your help again.
Nigel
From: Manuela Pichler<EMAIL_ADDRESS>Sent: 17 November 2020 15:28
To: microsoft/powerapps-tools<EMAIL_ADDRESS>Cc: Nigel Price<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [microsoft/powerapps-tools] [BUG]: New 16/11/2020 PowerBI dashboard Microsoft Teams Environments is blank (#573)
YAY! And you are seeing Microsoft Teams environments in the Power BI Dashboard as well now?
Not related to the CoE kit itself, but for info - with the old solution import experience, you had the option to "override customizations" which then got rid of your unmanaged layer as part of the import. This often led to issues as some customers selected this but didn't know it would remove their customizations hence with the modern solution import experience, this option was removed and customers are now responsible for making sure their solution is "ready" to receive the upgrade.
There are a few items on the roadmap to make this easier and add notifications during the import on flows that have customizations and thus won't receive the upgrade etc! The team is going to continue investing and working on making this experience easier.
Closing this issue now but please let us know if you continue to experience other issues!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/powerapps-tools/issues/573#issuecomment-729002954, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACAXJUDEN43GZI2DYXZXEVLSQKI6JANCNFSM4TXX6KDA.


Errors when reading PKCS7 Files

I am using Apache's tika parser v1.20 on PKCS7 files. I believe it is using BC v1.60 or v1.61. However, there is always a Java exception and it seems to be from the BC code.

A signed file: echo "hello world" | openssl cms -sign -inkey key.pem -signer cert.pem -md sha256 -outform der -nodetach -out sign.p7
A digest file:  echo "hello world" | openssl cms -digest_create -md sha256 -outform der -out digest.p7
A pkcs7 file from an existing issue: https://issues.apache.org/jira/projects/TIKA/issues/TIKA-1997

I don't know if it is caused by Tika using BC incorrectly or BC itself.
java  -jar tika-app-1.20.jar --config=tika.xml sign.p7
Exception in thread "main" org.apache.tika.exception.TikaException: TIKA-198: Illegal IOException from org.apache.tika.parser.ParserDecorator$1@ae45eb6
	at org.apache.tika.parser.CompositeParser.parse(CompositeParser.java:286)
	at org.apache.tika.parser.CompositeParser.parse(CompositeParser.java:280)
<snip>
Caused by: java.io.EOFException: DEF length 933 object truncated by 879
	at org.bouncycastle.asn1.DefiniteLengthInputStream.read(Unknown Source)
	at org.bouncycastle.asn1.DefiniteLengthInputStream.read(Unknown Source)
	at org.bouncycastle.asn1.DefiniteLengthInputStream.read(Unknown Source)
	at org.bouncycastle.asn1.DefiniteLengthInputStream.read(Unknown Source)
	at org.bouncycastle.asn1.DefiniteLengthInputStream.read(Unknown Source)
	at org.bouncycastle.asn1.DefiniteLengthInputStream.read(Unknown Source)

java  -jar tika-app-1.20.jar --config=tika.xml digest.p7
Exception in thread "main" org.apache.tika.exception.TikaException: Unexpected RuntimeException from org.apache.tika.parser.ParserDecorator$1@5dfcfece
	at org.apache.tika.parser.CompositeParser.parse(CompositeParser.java:282)
	at org.apache.tika.parser.CompositeParser.parse(CompositeParser.java:280)
	at org.apache.tika.parser.AutoDetectParser.parse(AutoDetectParser.java:143)
	at org.apache.tika.cli.TikaCLI$OutputType.process(TikaCLI.java:209)
	at org.apache.tika.cli.TikaCLI.process(TikaCLI.java:496)
	at org.apache.tika.cli.TikaCLI.main(TikaCLI.java:149)
Caused by: java.lang.ClassCastException: org.bouncycastle.asn1.DERSequenceParser cannot be cast to org.bouncycastle.asn1.ASN1SetParser
	at org.bouncycastle.asn1.cms.SignedDataParser.getDigestAlgorithms(Unknown Source)
	at org.bouncycastle.cms.CMSSignedDataParser.<init>(Unknown Source)
	at org.bouncycastle.cms.CMSSignedDataParser.<init>(Unknown Source)
	at org.apache.tika.parser.crypto.Pkcs7Parser.parse(Pkcs7Parser.java:68)

java  -jar tika-app-1.20.jar --config=tika.xml test.xml.p7m
Exception in thread "main" org.apache.tika.exception.TikaException: TIKA-198: Illegal IOException from org.apache.tika.parser.ParserDecorator$1@47c62251
	at org.apache.tika.parser.CompositeParser.parse(CompositeParser.java:286)
	at org.apache.tika.parser.CompositeParser.parse(CompositeParser.java:280)
	at org.apache.tika.parser.AutoDetectParser.parse(AutoDetectParser.java:143)
<snip>
Caused by: java.io.EOFException
	at org.bouncycastle.asn1.IndefiniteLengthInputStream.read(Unknown Source)
	at org.bouncycastle.asn1.IndefiniteLengthInputStream.read(Unknown Source)
	at org.bouncycastle.asn1.IndefiniteLengthInputStream.read(Unknown Source)
	at org.bouncycastle.asn1.IndefiniteLengthInputStream.read(Unknown Source)
	at org.bouncycastle.asn1.IndefiniteLengthInputStream.read(Unknown Source)
	at org.bouncycastle.asn1.IndefiniteLengthInputStream.read(Unknown Source)
	at org.bouncycastle.asn1.ASN1StreamParser.readObject(Unknown Source)
	at org.bouncycastle.asn1.ConstructedOctetStream.read(Unknown Source)

Example files can be created via specified openssl commands or as attachments at https://issues.apache.org/jira/browse/TIKA-2857

These all parse correctly with BC. Looking at the stack trace it looks like the streaming API is being used - it would be worth checking that it is being used correctly - as it's streaming you only get one shot at the data, and failure to read objects out of the stream that may be optional will result in the next step in the parsing failing.

My guess would be that the streaming in Tika is "generic" in that it doesn't know anything about PCKS7 structures especially regarding optional objects. It probably depends on the underlying classes to correctly parse the data. In any case, I will update the Tika issue with your comment.
As an aside, which BC tool are you using to read these files? Is it built with the BC source?

Yes, everything I do is built with the BC source. I just wrote a small app for these.
Closing, assuming this will be dealt with elsewhere.


Select open shapes

Allows for selection of open shapes by clicking on the filled region.

!build

What's the latest status on this? It's still marked as a draft so I assume there's more to do?

This is feature complete and awaiting review for code quality and robustness.

Any updates about getting the two code review comments resolved? (The question and the suggestion to reuse the existing winding function instead of reimplementing it.) Thanks!


Official guide to migrate to V4

I'm using d3 in my app built with vuejs and bundled with webpack. its mainly using a force. is there a plan to create an official migration guide for webpack users?

No, sorry. I will not be writing guides for specific bundling tools beyond the examples I have already provided for Rollup. Please read the Release Notes and the API Reference for documentation. You can also search the issues to see if other users have had related questions. Please use Stack Overflow tag d3.js or the d3-js Google group to ask for help. Thank you!


DEF_ADDR, SlaveAddress(), address read in init()

I added SlaveAddress() method to change meter Address using DEF_ADDR. Added init() code to read and store to .__addr and print current address.

Tested OK with latest commit 19b1e61
Single register parsing of msg[] was returning 'unknown valid response to 0x06 msg: ...' in __read_response(); fixed after checking msg[]: msg[2] = reg_addr, msg[3] = val. See code comments.
Tested with read ('None' arg) and write of both .SlaveAddress() and .PowerAlarm()


Spree 2.1 support

Does it work?

you can use this directly without any plugin
https://www.aftership.com/apps/spree-V2


[2 Feature Requests] About the AppGraber

[Request 1]
Is your feature request related to a problem? Please describe.
Sometimes if you have a bunch of applications added to the Programs menu in Cairo and you want to add another program, you get a messy list in the App Graber that lists all your Programs in every section/category.
Describe the solution you'd like
Hiding the Programs in the AppGraber by collapsing the sections/categories. Then Uncollapse the section/category when pressed on it.
Describe alternatives you've considered
Press the Up/Down arrows to move the section/category to the top for easier access.
Additional context
A picture how I imagine that to work is added here: (red text is me explaining)

Edit: Fond out that a Hide button exists,but I want to hide them automatically and unhide/hide specific categories
[Request 2]
Is your feature request related to a problem? Please describe.
Make the AppGraber Window sizeable/maximizeable for better access to categories if you have a bunch of them.
Describe the solution you'd like
MAke the window sizeable.
Describe alternatives you've considered
/
Additional context
/

This is not the first report of confusion regarding the "Hide" button that we have seen. If we used expand/collapse arrows on each category instead, would that have made more sense to you in the moment, and provide the flexibility you're looking for?

This is not the first report of confusion regarding the "Hide" button that we have seen. If we used expand/collapse arrows on each category instead, would that have made more sense to you in the moment, and provide the flexibility you're looking for?

Yeah something like that makes more sense. Expand/collpase buttons for each category individually are better in my opinion.


[ENH] where to run the jobs

add a new section in container's configuration YAML file: "job_compute_space"

Note: please use the up-to-date example container configuration yaml file, or add section 'job_compute_space' in the yaml file. Otherwise there will be error when babs-init!

Hi @djarecka! I'm about to merge this PR to main. Please update the YAML files you're using by adding section job_compute_space, otherwise you'll see errors when babs-init. For how to add this section, please refer to the updated docs (will be on after I merge it), or updated YAML files in notebooks directory.

In this PR, I added a section in container's configuration YAML file: job_compute_space. This is required by babs-init.


Fix tests by updating snapshot

Same as https://github.com/mirumee/saleor/pull/3226.
Do we need to fix the tests every month, any suggestions?
Pull Request Checklist

[ ] Privileged views and APIs are guarded by proper permission checks.
[ ] All visible strings are translated with proper context.
[ ] All data-formatting is locale-aware (dates, numbers, and so on).
[ ] Database queries are optimized and the number of queries is constant.
[ ] The changes are tested.
[ ] The code is documented (docstrings, project documentation).
[ ] GraphQL schema and type definitions are up to date.

Already fixed it in #3359 😂

I created a issue https://github.com/mirumee/saleor/issues/3377 for tracking this. How about merging this or https://github.com/mirumee/saleor/pull/3359 first, because I saw the CI for PRs are failing...

Close by https://github.com/mirumee/saleor/pull/3359