Error when composer version updated (Linux, docker 23.0.0)

Is there an existing issue for this?
Existing issue with docker 23.0.0 is at

https://github.com/drud/ddev/issues/4616

[X] I have searched the existing issues

Run a Diagnostic and Paste Link Here
I need composer versin less than 2.4
So i updated composer_version: "2.2" in config.yaml
ddev restart gives below error
---- ', stderr='failed to solve: process "/bin/sh -c export XDEBUG_MODE=off; composer self-update --stable || composer self-update --stable || true; composer self-update --2.2 || composer self-update --2.2 || true" did not complete successfully: exit code: 1'
Expected Behavior
Composer show be downgarded to 2.2 and ddev starts
Actual Behavior
ddev start shows error
Steps To Reproduce
No response
Anything else?
No response

I'm unable to reproduce this. Please provide the requested ddev debug test output (preferably as a gist or other pastebin) and please show the full output of your ddev restart. It's most likely a network problem.

`ddev restart
Restarting project shopware...
Container ddev-shopware-dba  Removed
Container ddev-shopware-db  Removed
Container ddev-shopware-web  Removed
Network ddev-shopware_default  Removed
failed to solve: process "/bin/sh -c export XDEBUG_MODE=off; composer self-update --stable || composer self-update --stable || true; composer self-update --2.2 || composer self-update --2.2 || true" did not complete successfully: exit code: 1
Failed to restart shopware: ComposeCmd failed to run 'COMPOSE_PROJECT_NAME=ddev-shopware docker-compose -f /home/sanoop/Projects/shopware/.ddev/.ddev-docker-compose-full.yaml up --build -d', action='[up --build -d]', err='exit status 17', stdout='#1 [drud/ddev-dbserver-mariadb-10.4:v1.21.4-shopware-built internal] load .dockerignore
#1 transferring context: 2B done
#1 DONE 0.1s
#2 [drud/ddev-dbserver-mariadb-10.4:v1.21.4-shopware-built internal] load build definition from Dockerfile
#2 transferring dockerfile: 591B done
#2 DONE 0.1s
#3 [drud/ddev-webserver:v1.21.4-shopware-built internal] load .dockerignore
#3 transferring context: 2B done
#3 DONE 0.1s
#4 [drud/ddev-webserver:v1.21.4-shopware-built internal] load build definition from Dockerfile
#4 transferring dockerfile: 926B done
#4 DONE 0.1s
#5 [drud/ddev-dbserver-mariadb-10.4:v1.21.4-shopware-built internal] load metadata for docker.io/drud/ddev-dbserver-mariadb-10.4:v1.21.4
#5 DONE 0.0s
#6 [drud/ddev-dbserver-mariadb-10.4:v1.21.4-shopware-built 1/2] FROM docker.io/drud/ddev-dbserver-mariadb-10.4:v1.21.4
#6 DONE 0.0s
#7 [drud/ddev-dbserver-mariadb-10.4:v1.21.4-shopware-built 2/2] RUN (groupadd --gid 1000 "sanoop" || groupadd "sanoop" || true) && (useradd  -l -m -s "/bin/bash" --gid "sanoop" --comment '' --uid 1000 "sanoop" || useradd  -l -m -s "/bin/bash" --gid "sanoop" --comment '' "sanoop" || useradd  -l -m -s "/bin/bash" --gid "1000" --comment '' "sanoop" || useradd -l -m -s "/bin/bash" --comment '' sanoop )
#7 CACHED
#8 [drud/ddev-webserver:v1.21.4-shopware-built internal] load metadata for docker.io/drud/ddev-webserver:v1.21.4
#8 DONE 0.0s
#9 [drud/ddev-webserver:v1.21.4-shopware-built 1/4] FROM docker.io/drud/ddev-webserver:v1.21.4
#9 DONE 0.0s
#10 [drud/ddev-dbserver-mariadb-10.4:v1.21.4-shopware-built] exporting to image
#10 exporting layers done
#10 writing image sha256:7f7f3be3dc97d84f46cc2baeb502c361f48db5d61a8de83865c298f5c2efb57b 0.0s done
#10 naming to docker.io/drud/ddev-dbserver-mariadb-10.4:v1.21.4-shopware-built done
#10 DONE 0.0s
#11 [drud/ddev-webserver:v1.21.4-shopware-built 2/4] RUN (groupadd --gid 1000 "sanoop" || groupadd "sanoop" || true) && (useradd  -l -m -s "/bin/bash" --gid "sanoop" --comment '' --uid 1000 "sanoop" || useradd  -l -m -s "/bin/bash" --gid "sanoop" --comment '' "sanoop" || useradd  -l -m -s "/bin/bash" --gid "1000" --comment '' "sanoop" || useradd -l -m -s "/bin/bash" --comment '' sanoop )
#11 CACHED
#12 [drud/ddev-webserver:v1.21.4-shopware-built 3/4] RUN export XDEBUG_MODE=off; composer self-update --stable || composer self-update --stable || true; composer self-update --2.2 || composer self-update --2.2 || true
#12 0.305 runc run failed: unable to start container process: exec: "/bin/sh": stat /bin/sh: no such file or directory
#12 ERROR: process "/bin/sh -c export XDEBUG_MODE=off; composer self-update --stable || composer self-update --stable || true; composer self-update --2.2 || composer self-update --2.2 || true" did not complete successfully: exit code: 1

[drud/ddev-webserver:v1.21.4-shopware-built 3/4] RUN export XDEBUG_MODE=off; composer self-update --stable || composer self-update --stable || true; composer self-update --2.2 || composer self-update --2.2 || true:
#12 0.305 runc run failed: unable to start container process: exec: "/bin/sh": stat /bin/sh: no such file or directory

', stderr='failed to solve: process "/bin/sh -c export XDEBUG_MODE=off; composer self-update --stable || composer self-update --stable || true; composer self-update --2.2 || composer self-update --2.2 || true" did not complete successfully: exit code: 1'
sanoop@sanoop-TUXEDO:~/Projects/shopware$
`

ddev restart
Restarting project shopware...
Container ddev-shopware-dba  Removed
Container ddev-shopware-db  Removed
Container ddev-shopware-web  Removed
Network ddev-shopware_default  Removed
failed to solve: process "/bin/sh -c export XDEBUG_MODE=off; composer self-update --stable || composer self-update --stable || true; composer self-update --2.2 || composer self-update --2.2 || true" did not complete successfully: exit code: 1
Failed to restart shopware: ComposeCmd failed to run 'COMPOSE_PROJECT_NAME=ddev-shopware docker-compose -f /home/sanoop/Projects/shopware/.ddev/.ddev-docker-compose-full.yaml up --build -d', action='[up --build -d]', err='exit status 17', stdout='#1 [drud/ddev-dbserver-mariadb-10.4:v1.21.4-shopware-built internal] load .dockerignore
#1 transferring context: 2B done
#1 DONE 0.1s
#2 [drud/ddev-dbserver-mariadb-10.4:v1.21.4-shopware-built internal] load build definition from Dockerfile
#2 transferring dockerfile: 591B done
#2 DONE 0.1s
#3 [drud/ddev-webserver:v1.21.4-shopware-built internal] load .dockerignore
#3 transferring context: 2B done
#3 DONE 0.1s
#4 [drud/ddev-webserver:v1.21.4-shopware-built internal] load build definition from Dockerfile
#4 transferring dockerfile: 926B done
#4 DONE 0.1s
#5 [drud/ddev-dbserver-mariadb-10.4:v1.21.4-shopware-built internal] load metadata for docker.io/drud/ddev-dbserver-mariadb-10.4:v1.21.4
#5 DONE 0.0s
#6 [drud/ddev-dbserver-mariadb-10.4:v1.21.4-shopware-built 1/2] FROM docker.io/drud/ddev-dbserver-mariadb-10.4:v1.21.4
#6 DONE 0.0s
#7 [drud/ddev-dbserver-mariadb-10.4:v1.21.4-shopware-built 2/2] RUN (groupadd --gid 1000 "sanoop" || groupadd "sanoop" || true) && (useradd  -l -m -s "/bin/bash" --gid "sanoop" --comment '' --uid 1000 "sanoop" || useradd  -l -m -s "/bin/bash" --gid "sanoop" --comment '' "sanoop" || useradd  -l -m -s "/bin/bash" --gid "1000" --comment '' "sanoop" || useradd -l -m -s "/bin/bash" --comment '' sanoop )
#7 CACHED
#8 [drud/ddev-webserver:v1.21.4-shopware-built internal] load metadata for docker.io/drud/ddev-webserver:v1.21.4
#8 DONE 0.0s
#9 [drud/ddev-webserver:v1.21.4-shopware-built 1/4] FROM docker.io/drud/ddev-webserver:v1.21.4
#9 DONE 0.0s
#10 [drud/ddev-dbserver-mariadb-10.4:v1.21.4-shopware-built] exporting to image
#10 exporting layers done
#10 writing image sha256:7f7f3be3dc97d84f46cc2baeb502c361f48db5d61a8de83865c298f5c2efb57b 0.0s done
#10 naming to docker.io/drud/ddev-dbserver-mariadb-10.4:v1.21.4-shopware-built done
#10 DONE 0.0s
#11 [drud/ddev-webserver:v1.21.4-shopware-built 2/4] RUN (groupadd --gid 1000 "sanoop" || groupadd "sanoop" || true) && (useradd  -l -m -s "/bin/bash" --gid "sanoop" --comment '' --uid 1000 "sanoop" || useradd  -l -m -s "/bin/bash" --gid "sanoop" --comment '' "sanoop" || useradd  -l -m -s "/bin/bash" --gid "1000" --comment '' "sanoop" || useradd -l -m -s "/bin/bash" --comment '' sanoop )
#11 CACHED
#12 [drud/ddev-webserver:v1.21.4-shopware-built 3/4] RUN export XDEBUG_MODE=off; composer self-update --stable || composer self-update --stable || true; composer self-update --2.2 || composer self-update --2.2 || true
#12 0.305 runc run failed: unable to start container process: exec: "/bin/sh": stat /bin/sh: no such file or directory
#12 ERROR: process "/bin/sh -c export XDEBUG_MODE=off; composer self-update --stable || composer self-update --stable || true; composer self-update --2.2 || composer self-update --2.2 || true" did not complete successfully: exit code: 1

[drud/ddev-webserver:v1.21.4-shopware-built 3/4] RUN export XDEBUG_MODE=off; composer self-update --stable || composer self-update --stable || true; composer self-update --2.2 || composer self-update --2.2 || true:
#12 0.305 runc run failed: unable to start container process: exec: "/bin/sh": stat /bin/sh: no such file or directory

', stderr='failed to solve: process "/bin/sh -c export XDEBUG_MODE=off; composer self-update --stable || composer self-update --stable || true; composer self-update --2.2 || composer self-update --2.2 || true" did not complete successfully: exit code: 1'
sanoop@sanoop-TUXEDO:~/Projects/shopware$

Apparently you're on Linux and you updated to Docker v23.0.0. Please see pinned issue

https://github.com/drud/ddev/issues/4616

Try the fixes in https://github.com/drud/ddev/issues/4616#issuecomment-1421429448

Apparently you're on Linux and you updated to Docker v23.0.0. Please see pinned issue

Linux: Can't start project with docker 23.0.0; fix with ddev debug refresh #4616

Try the fixes in #4616 (comment)

thanks very much , it solved my issue

Glad it's working for you!


emacsPackages: forge package missing dependencies?

Issue description
Forge not working as expected.
Running Mx - forge gives error: No EmacSQL SQLite binary available, aborting
I think perhaps the emacsql dependency requires some additional build-steps.
cc @adisbladis
Steps to reproduce
nix-shell -p emacsPackagesNg.melpaPackages.magit emacsPackagesNg.melpaPackages.forge
emacs -Q
M-x package-initialize
M-x magit-status on any git repository
M-x forge-pull
Error message:
Compiling EmacSQL SQLite binary ...
emacsql-sqlite-ensure-binary: No EmacSQL SQLite binary available, aborting

Technical details

system: "x86_64-linux"
host os: Linux 4.20.1, NixOS, 19.03.git.46717df (Koi)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.2
nixpkgs: /home/jethro/nix-config/nixpkgs

Closed with #53868


Enable dts-trimming for packages/common

Description
Related: 18176
This PR adds type-trimming for packages/common directory. The changes introduced are:

Add npm copyfiles package as devDependency
Add dtsRollup in api-extractor.json
Enable both type-trimming for both ESM & CJS
Make fluidBuild to fetch dependencies from the scripts included in dependsOn

What about container-definitions and core-interfaces? Are those going to be done separately?

What about container-definitions and core-interfaces? Are those going to be done separately?

I believe the work on commons/container-definitions and commons/core-interfaces are already completed from your previous work on the dts-trimming 18176.
container-definitions/api-extractor.json: Main
container-definitions/package.json: Main
core-interfaces/api-extractor.json: Main
container-definitions/package.json: Main
I also see the alpha, beta and public d.ts files correctly generated in dist folder for those packages in the main branch.

What about container-definitions and core-interfaces? Are those going to be done separately?

I believe the work on commons/container-definitions and commons/core-interfaces are already completed from your previous work on the dts-trimming 18176.
container-definitions/api-extractor.json: Link container-definitions/package.json: Link
core-interfaces/api-extractor.json: Link container-definitions/package.json: Link
I also see the alpha, beta and public d.ts files correctly generated in dist folder for those packages in the main branch.

Ha, forgot I did that. Sorry! :)


Utility Network card needs updating for v4/v5 changes

The card is missing the Valid Junctions and the Edge/Junction objects.  @previnWong I cannot assign this to you, do not have permission

verified, bug noted on categories and sent to previn


Interim Guide for iD Editor - ES

In English.

Merging just so you can see the result but I don't think the link here will work. Otherwise looks very good.
This guide is available in [English] (https://http://learnosm.org/en/beginner/id-editor/)

@Anwaario  I've merged your file & you can view it at http://nick-tallguy.github.io/es/beginner/id-editor/
( @althio For your info )
but the link to the English version needs amending
  from [English] (https://http://learnosm.org/en/beginner/id-editor/)
   to [English](/en/beginner/id-editor/)

remove the gap between ](
and just use the 'permalink' from the header section of the target file
---
layout: doc
title: iD Editor
permalink: /en/beginner/id-editor/
lang: en
category: beginner
---

A very good start  - keep up the good work, thanks.
Please can you amend this interim guide according to my comments, and then produce the others. I'm just about to check the contents of the other guides in the beginners section, and if they are in English only I will delete them & update the spreadsheet to show 'missing' - an interim guide will be needed for them as well.


pubsub.mqtt: all messages are sent to the same handler regardless of topic

I have pinpointed this issue in the code and will include a fix in a PR soon.
Repro code
Component:
apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
  name: orders
spec:
  type: pubsub.mqtt
  version: v1
  metadata:
    - name: url
      value: "tcp://<IP_ADDRESS>:1883"
    - name: qos
      value: 1

Code:
package main

import (
	"context"
	"errors"
	"log"
	"math/rand"
	"net/http"

	"github.com/dapr/go-sdk/service/common"
	daprd "github.com/dapr/go-sdk/service/http"
)

var sub1 = &common.Subscription{
	PubsubName: "orders",
	Topic:      "topic1",
	Route:      "/checkout1",
}
var sub2 = &common.Subscription{
	PubsubName: "orders",
	Topic:      "topic2",
	Route:      "/checkout2",
}

func main() {
	s := daprd.NewService("<IP_ADDRESS>:6002")
	if err := s.AddTopicEventHandler(sub1, eventHandler1); err != nil {
		log.Fatalf("error adding topic 1 subscription: %v", err)
	}
	if err := s.AddTopicEventHandler(sub2, eventHandler2); err != nil {
		log.Fatalf("error adding topic 2 subscription: %v", err)
	}
	if err := s.Start(); err != nil && err != http.ErrServerClosed {
		log.Fatalf("error listenning: %v", err)
	}
}

func eventHandler1(ctx context.Context, e *common.TopicEvent) (retry bool, err error) {
	log.Printf("eventHandler1 (topic=%s): Subscriber received: %s", e.Topic, e.Data)
	log.Printf("eventHandler1 (topic=%s): Done processing: %s", e.Topic, e.Data)
	return false, nil
}

func eventHandler2(ctx context.Context, e *common.TopicEvent) (retry bool, err error) {
	log.Printf("eventHandler2 (topic=%s): Subscriber received: %s", e.Topic, e.Data)
	log.Printf("eventHandler2 (topic=%s): Done processing: %s", e.Topic, e.Data)
	return false, nil
}

Run:
dapr run \
    --app-id myapp \
    --app-port 6002 \
    --dapr-http-port 3602 \
    --dapr-grpc-port 60002 \
    --components-path ./components \
    --log-level debug \
    --\
        go run main.go

Send messages to the two topics:
curl \
    -X POST \
    "http://localhost:3602/v1.0/publish/orders/topic1" \
    -H "Content-Type: application/json" \
    -d "{\"orderId\": \"1"}"
curl \
    -X POST \
    "http://localhost:3602/v1.0/publish/orders/topic2" \
    -H "Content-Type: application/json" \
    -d "{\"orderId\": \"2"}"

Expected Behavior
Should log:
eventHandler1 (topic=topic1): Subscriber received: map[orderId:1]
eventHandler1 (topic=topic1): Done processing: map[orderId:1]
eventHandler2 (topic=topic2): Subscriber received: map[orderId:2]
eventHandler2 (topic=topic2): Done processing: map[orderId:2]

Actual Behavior
Logs:
eventHandler2 (topic=topic1): Subscriber received: map[orderId:1]
eventHandler2 (topic=topic1): Done processing: map[orderId:1]
eventHandler2 (topic=topic2): Subscriber received: map[orderId:2]
eventHandler2 (topic=topic2): Done processing: map[orderId:2]

(Sometimes all messages go to eventHandler1 instead, depending on which one is registered first)
Release Note
RELEASE NOTE: FIX Routing pubsub.mqtt messages to the correct handler when more than one is registered

/assign

Dupe of https://github.com/dapr/components-contrib/issues/1709. Closing


Prefix log statements with timestamp

Closes https://github.com/serverless/event-gateway/issues/251

Thanks @RafalWilinski!


@Tratcher @HaoK

Hi @Eilon, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by .NET Foundation and real humans are currently evaluating your PR.
TTYL, DNFBOT;

Does that make it possible to get > 100% code coverage then?

Yay :shipit:

Not sure about >%100 but we'll see :smile:

Thanks!


Scrollbar goes on top of Telescope

You can see scrollbar is renderd on to of telescope popu window:

Other than that it works great.

Thanks for reporting this @JoseConseco!
I don't have a solution yet.
I plan to explore whether it's possible to set the precedence of floating windows, similar to the zindex property for Vim's popup windows. That way, the scrollbars could have low precedence, which would result in other floating windows appearing above them.
If it's not possible to set floating window precedence, perhaps calling nvim_win_set_config causes an existing window to take higher precedence (as if it were a new floating window, assuming new floating windows appear over existing ones). If so, nvim-scrollview could call nvim_win_set_config on existing floating windows after the scrollbars are shown.
Another possible workaround could be for nvim-scrollview to check whether a scrollbar would overlap existing floating windows, and if so, skip displaying that scrollbar.

An unintended side effect of d15b750c584b69f33071239d76ce624c5fe28dc2 is that it's now less likely for scrollbars to cover floating windows. However, a more substantial update is required for a more robust solution.

Thank  the update seems to fix the scrollbar rendering on top of telescope popu.

I think you have seen this : https://github.com/neovim/neovim/pull/14468 .  But I do not have any problems with ui sorting now

As of 1e6a6954c62f57953cd718ca5ed453321037a193, nvim-scrollview now uses a default z-index of 40, which is intentionally lower than the default z-index of 50 that's used for floating windows. This way, nvim-scrollview scrollbars will have a lower z-index than other floating windows that use the default value.

Thx for the fix. Issue is gone now


sendHTTPRequest Function using Deno

Closes appwrite/appwrite#4174
Proof of working

Thanks for the amazing PR 😇 I have added small changes to fix empty body requests.
Merging the PR now 🥳


[VRM - Bug]: Battery is at the evening not at 100 % and next day I have to buy with higher costs

Contact Details
No response
VRM portal ID
b827eb6ff17f
Country / region
Germany (de)
B max
26
TB max
6,5
FB max
7
TG max
30
FG max
30
Battery costs
0,02
Buy price
p+0.217+0.0161
Sell price
0,115
feed-in possible
yes
feed-in control
yes
What happened?
At the evening is the battery not at 100% end I will have to by power next day for a higher price :-/
When did it happen?
15/10/2023 15:01 I have manual change to from auto mode to buy mode.
Screenshots

price overvview for 15/10/2023

price overview for 16/10/2023

fill the battery to 100% is much better ;-)

Thing is the moment DESS knew about this (which is 15:00) it would have charged, but you jumped the gun and decided to turn on Sell prices at 15:01, right after checking it yourself. It might be that Dynamic ESS showed something different (at the very start of the hour), but we are pretty sure you were just impatient here.


non optimal

You are splitting a batch of potentially hundreds of events into separate run_command calls which doesn't seem very optimal. Why not just pass all the events as they arrive and let users iterate over them instead?
https://github.com/kapitanluffy/sublime-file-watcher/blob/95c4c06802a0e33fb77760ae26aa519446d72c32/src/file_watcher_handler.py#L49-L50

Thanks @rchl. Updated it. Let me know if that is more optimal
https://github.com/kapitanluffy/sublime-file-watcher/blob/master/src/file_watcher_handler.py#L49-L78

Well, you lose information about the original order of events that way, which might be relevant for some use cases. You could just broadcast events as they come.

There you go. I just broadcasted it at once and let the user handle it.

That's better.


1124-2021 Building & Deploying Web Apps with SASjs CLI

This PR is dependent on #11 - if this is not to be merged, then we can close this PR, and I will remove the extra files and submit just the README / PDF

I merged #11 but now there's a conflict with this one in a README, @allanbowe

@cjdinger  - resolved!

@allanbowe remember you still need to upload the PDF and update the SGF proceedings on SAS Communities. But great to see this openly committed here too. Thanks for contributing to the community!

Done - thanks for the reminder !
https://communities.sas.com/t5/SAS-Global-Forum-Proceedings/Scaffolding-SAS-Projects-With-NPM-and-SASjs/ta-p/726347
On Thu, 15 Apr 2021 at 23:15, Christopher Blake @.***>
wrote:

@allanbowe https://github.com/allanbowe remember you still need to
upload the PDF and update the SGF proceedings on SAS Communities. But great
to see this openly committed here too. Thanks for contributing to the
community!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/sascommunities/sas-global-forum-2021/pull/12#issuecomment-820736210,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABBXIB3MV7CJERC5PHJZFQDTI5JP7ANCNFSM43ADW5TA
.


Encrypted File Operations handling of null

Right now, if a file doesn't exist, getFile should return null, however, when encryption and decryption is enabled, the decryption routine attempts to decrypt null, resulting in some kind of Type Error. This should return null instead.

This is fixed and deployed in blockstack.js v0.14.1.
Thank you @kantai !


[TODO]  Active / standby deployment to improve availability

It is suggest to use Kubernete election model, such as Kube-scheduler.


Azure SAS authorization fails with <AuthenticationErrorDetail>Signature fields not well formed.

Environment
Delta-rs version: 0.6.2
Binding: python
Using a sas token to access a deltalake on AzureStorage throws an authorization error. The sas token was verified out of band.
Interestingly, the thrown error provides a failed blob url. Comparing this with a working url, the sas fields in the failed url are url-quoted. For instance:
>>> from urllib.parse import quote_plus
>>> failed_url_sas_sig == quote_plus(working_url_sas_sig)
True

Hey @xbrianh, thanks for reporting. I'm working on improving our testing for Azure in #912.
Could you share exactly how you are passing credentials to DeltaTable? Are you passing through storage_options? Or using environment variables? And which variables are you passing?

Hi @wjones127, thanks for looking into this so quickly!
Here's my access pattern:
storage_options = dict(account_name=storage_account, sas_token=sas)
t = deltalake.DeltaTable(azure_uri, storage_options=storage_options)

I also tried some aliases for "account_name" and "sas_token" found here

@xbrianh - could you confirm really quick. I think we are expecting the sas token in the form as it would be if generated in the Storage Explorer. I that how you are passing it in?

Same issue with sas token generated in Storage Explorer.

I'm not able to reproduce with Azurite, so the SAS token signature might not be validated there in full. We should test against the real API.

I was able to reproduce the error against a real account. Will have to do some digging, as we tested this quite throughly when integrating it  into object store.

I faced the same problem with SAS tokens generated by Azure Portal or Azure Storage explorer.
I'm using deltalake-0.6.4
Any updates on this?


Bump comms-templates and enable caching

This PR was successfully deployed to production by CircleCI build 156 at 2017-03-31 14:37 BST.


Expose flush on Promise

I need to flush the queue synchronously to be able to use promises with indexeddb on some older platforms that don't check the microtask queue before closing active transactions (IE11 on Windows7), like so.
I considered using the already exposed setScheduler function but it would be hard to just flush the queue around the resolution of one promise without reimplementing the MutationObserver strategy, given that you can't assume which resolve will queue a microtask, and as I still want promises outside of idb requests to resolve async.
The changes are minimal, but the authors might or might not want to expose this. I'm happy to just keep this in a fork if not.

Not sure why the tests fail, but seems unrelated to changes?

Ya, I don't feel comfortable exposing this functionality in this library. But a fork is perfectly reason in this case.
Thank you for the PR, but I will be closing it


[fix-#14447]The judgment in k8sUtils#getPodLog is not accurate

Purpose of the pull request
plz close : #14447
Brief change log

Verify this pull request

This pull request is code cleanup without any test coverage.

Codecov Report

Merging #14448 (a1c4402) into dev (9cbb262) will increase coverage by 0.00%.
The diff coverage is 0.00%.

:exclamation: Current head a1c4402 differs from pull request most recent head 92032c1. Consider uploading reports for the commit 92032c1 to get more accurate results

@@            Coverage Diff            @@
##                dev   #14448   +/-   ##
=========================================
  Coverage     38.52%   38.53%
+ Complexity     4555     4553    -2
=========================================
  Files          1236     1236
  Lines         43486    43438   -48
  Branches       4817     4785   -32
=========================================
- Hits          16755    16738   -17
+ Misses        24875    24844   -31
  Partials       1856     1856

Impacted Files
Coverage Δ

...lphinscheduler/plugin/task/api/utils/K8sUtils.java
3.50% <0.00%> (ø)

... and 36 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

PTAL @Radeity


Fix of Rich#getEditorOptions

Hello!
I attentively followed through all gem's setup steps in readme.
Right after adding :as => :rich to my text field I began seeing error "can't convert nil into Hash".
Exploration led me to #getEditorOptions method of Rich class. The problem there is that previous function in caller chain passes nil as arg which causes error because default "overrides={}" doesn't work if nil passed.
The simplest demonstration of this:
def a b={};puts b.inspect;end;a(nil)
=> nil

I didn't run into details of gem deep, but it seems that anyway #getEditorOptions method itself should be fixed to reflect this issue. Mine quick hack just points direction.
And one more:
Why not to follow ruby's conventions and name method get_editor_options? Strange to see javascript's notation in .rb files.
Thanks, hope this makes sense.

Thanks for this! A silly mistake on my part.
Also, I totally agree with the naming; it's on my list. I've been looking at the ckeditor code too much ;)


collect2:ld returned 1 exit status

In the step:
""""""""""
cd rnnlm-0.2b
make
""""""""""
error comes out "collect2:ld returned 1 exit status"
the error comes when "make rnn2fst" and "make wfst-ppl"
openfst and kmeans had already installed

gcc/g++ need 4.6.1


[New game]: Flappy Bird

🎮 Game Request
A simple JS clone of the flappy bird. The Flappy Bird game is a popular side-scrolling mobile game where players control a bird and navigate it through a series of pipes. The objective of the game is to fly the bird as far as possible without hitting the pipes or the ground.
Point down the features
In the Flappy Bird game, points are typically scored based on successfully passing through the gaps between the pipes. If you hit the pipe or ground, the game is over and the total score will be shown.
Select program in which you are contributing
GSSoC23
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

Hey @Arka2708 !! We are already having similar game in #22 !!

Hey @Arka2708 ! Thank you so much for your raising the issue💗
It’s all yours, you can come anytime again and make some contributions! 🚀
Alone, we can do little, but together we can do so much! 😇


QC: Update pkgdown.yaml sample report generation step

QC Details
Currently uses old workflows to create SampleReportSite.html and SampleReportCountry.yaml. need to update this to current workflow for proper report generation
Additional Comments

@lauramaxwell check out #1640 for a potentially easier way to handle this.

so we would create and store them in the docs folder and then just reference them in articles section of the _pkgdown.yml? I think we want them created during the checks, iirc.  I'm probably missing something obvious here.

Build SampleReportSite with an Rmd in vignettes/articles. Or along those lines. I haven't dug in but the idea is, if it's html we're generating dynamically, we should do it as a vignette or article.


Messed Up HUD Elements

Your mod mashes the air meter down into the hunger meter and I've even tested it with just this mod in a pack by itself.  When I remove this add the elements return to their proper places.

Thank you, fixed.


end to end wireup/prototype

@PWKad / @EisenbergEffect / anyone who's interested...
I put together an end-to-end wireup with a form, some entities, the binding behavior, a bootstrap renderer and reporter.  The code is here:  https://github.com/jdanyow/skeleton-navigation/tree/validation/skeleton-es2016/src
It uses the existing aurelia-validation and aurelia-validatejs code.  Anything that was changed is in the repo mentioned above under src/aurelia-validation/, src/aurelia-validatejs/ and src/aurelia-bootstrap-validation/ folders.
When looking at this, it would probably make the most sense to look at src/app.html, followed by src/app.js then over to src/aurelia-validation/validate-binding-behavior.js.
The current code isn't actually validating anything or observing any properties, the ValidateJSValidationReporter just fires a couple errors on an interval to verify things are hooked up.  Will go back and fill in the observation and calls to the validator once we discuss a bit more.
Let me know what you think.  Definitely some questionable items in there... I'm looking at you "NewInstance.of(...).as(...)" :wink:
Here's what it looks like when it's running: animated gif

cc @mbroadst

@PWKad This looks pretty good to me. There are still a few open questions but I think we can resolve them if we can move forward with this. Please review with top priority.

This looks good to me. As a matter of fact in the past week I've sort of been throwing my eggs into the json-schema basket, so I'm getting more to a point where I'm more focused on the "reporting" and templating side of the equation rather than the validation primitives themselves. Looks like the flexibility exists in this design, so hopefully once this is locked down I can provide a json-schema hookup for it


Add netrc support for LFS API requests

This PR adds support for using netrc for LFS API requests. The priority becomes:

Check the LFS URL for authentication. Ex<EMAIL_ADDRESS>Check netrc for authentication.
Check the Git remote URL for authentication IF it's the same scheme and host of the LFS URL.
Ask 'git credential' to fill in the password from one of the above URLs.

TODO:

[x] Add netrc support
[x] Add automated tests
[ ] What happens on Windows? Does netrc work there?

//cc #705

I added central caching of the *netrc.Netrc object in Config. Also added a platform specific netrcBasename var that's set to .netrc everywhere except windows, which uses _netrc.

This looks good, but script/integration is hanging locally after the last test. The "master" and even the latest "cred-fixes" branches both work flawlessly for me.
I'm going to hold it back from v1.1 until that can be checked out, and the netrc feature itself can be tested a bit more.  Should be a shoe-in for v1.2 though.

It hangs because netrcBasename is blank because go on osx won't build the file config_linux.go, even if the build tag tells it to. You have to name it something that isn't a platform name:
Naming a file dns_windows.go will cause it to be included only when building the package for Windows; similarly, math_386.s will be included only when building the package for 32-bit x86.

I think I usually see them as _nix or _unix.

Doh, good catch.
On Wed, Nov 18, 2015 at 11:47 AM, Scott Barron<EMAIL_ADDRESS>wrote:

It hangs because netrcBasename is blank because go on osx won't build the
file config_linux.go, even if the build tag tells it to. You have to name
it something that isn't a platform name:
Naming a file dns_windows.go will cause it to be included only when building the package for Windows; similarly, math_386.s will be included only when building the package for 32-bit x86.
I think I usually see them as _nix or _unix.
—
Reply to this email directly or view it on GitHub
https://github.com/github/git-lfs/pull/715#issuecomment-157817845.

--
Rick Olson

I pushed a change that renames the file, but also changes the way the variable is set. Instead of a var + init() in the build flagged files, the build flagged files should define the variable. With this pattern, the build would have failed immediately because nothing defined netrcBasename.


Revert "PHOENIX-6198 Add option to IndexTool to specify the source table for scan"

Reverts apache/phoenix#937

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 29s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 2 new or modified test files.

_ 4.x-PHOENIX-5182 Compile Tests _

+1 :green_heart:
mvninstall
10m 41s
4.x-PHOENIX-5182 passed

+1 :green_heart:
compile
0m 54s
4.x-PHOENIX-5182 passed

+1 :green_heart:
checkstyle
0m 54s
4.x-PHOENIX-5182 passed

+1 :green_heart:
javadoc
0m 45s
4.x-PHOENIX-5182 passed

+0 :ok:
spotbugs
2m 59s
phoenix-core in 4.x-PHOENIX-5182 has 954 extant spotbugs warnings.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
5m 37s
the patch passed

+1 :green_heart:
compile
0m 55s
the patch passed

+1 :green_heart:
javac
0m 55s
the patch passed

-1 :x:
checkstyle
0m 54s
phoenix-core: The patch generated 13 new + 965 unchanged - 53 fixed = 978 total (was 1018)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
javadoc
0m 45s
the patch passed

+1 :green_heart:
spotbugs
3m  6s
the patch passed

_ Other Tests _

-1 :x:
unit
122m 22s
phoenix-core in the patch failed.

+1 :green_heart:
asflicense
0m 37s
The patch does not generate ASF License warnings.

153m 41s

Reason
Tests

Failed junit tests
phoenix.end2end.StoreNullsIT

phoenix.end2end.OrphanViewToolIT

phoenix.end2end.DeleteIT

Subsystem
Report/Notes

Docker
ClientAPI=1.40 ServerAPI=1.40 base: https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-968/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/phoenix/pull/968

Optional Tests
dupname asflicense javac javadoc unit spotbugs hbaseanti checkstyle compile

uname
Linux fd3a0461f650 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev/phoenix-personality.sh

git revision
4.x-PHOENIX-5182 / 0d33ce9

Default Java
Private Build-1.8.0_242-8u242-b08-0ubuntu3~16.04-b08

checkstyle
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-968/1/artifact/yetus-general-check/output/diff-checkstyle-phoenix-core.txt

unit
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-968/1/artifact/yetus-general-check/output/patch-unit-phoenix-core.txt

Test Results
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-968/1/testReport/

Max. process+thread count
7058 (vs. ulimit of 30000)

modules
C: phoenix-core U: phoenix-core

Console output
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-968/1/console

versions
git=2.7.4 maven=3.3.9 spotbugs=4.1.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.


Ordering guarantees for pipeline

If I use redis pipeline like this
const keys = ['key1', 'key2'];
const pipeline = redis.pipeline();
keys.forEach(key, pipeline.get(key));
const results = await pipeline.exec();
I get an array of results. I wanted to know if the order of the commands I set with pipeline and order of results I get are same or not?
I have tested with a few examples and I got results in the same order but that could just be a chance. I checked the documentation but couldn't find information related to this.

Ordering is guaranteed by Redis. You can rely on the order of the results.


getStorageSize()/getUsedStorage() functions for OC or Detector mode

These functions would return the total amount of storage available in the network and the total used storage in the network, it might also be helpful to have an optional argument that will limit them to a certain type of storage (drive/external), that could be useful as with some external inventories  (such as the drawer controller), the available storage doesn't get read correctly.
It could be very useful for things like quarries made with frames such as the ones from funky locomotion so that it would stop once there isn't any more space in the system to prevent it from breaking.
This could also be implemented as a mode to the Detector so that it will emit a signal if there is less then a certain amount of space.

The integration already has these two functions that can be used to calculate this.
getItems():table | Gets a list of all items in this network.
getStorages():table | Gets a list of all connected storage disks and blocks in this network.
Comparator support like requested in #972 makes more sense than adding more functionality to the detector.


Fixes CASMPET-5037: Update image refs

What are we commit chart packages under kubernetes/cray-postgres-operator/charts?

Did we intend to check the entire parent chart (expanded) into the charts directory?

What are we committing (and have committed) chart packages under kubernetes/cray-postgres-operator/charts?

I did not want to do that, but the lint dependency check would fail without including the expanded charts. Is there a way around this, or could you ignore the lint errors?

Did we intend to check the entire parent chart (expanded) into the charts directory?

Without expanding the charts, the dependency check by lint would fail. I haven't found a way to go around it unless we ignore the lint dependency check.


[FEAT] Add str.left() funtion

Returns the left-most n characters
Resolves #1926

@colin-ho  pushed the changes.

@colin-ho thanks for the review. Addressed.

@colin-ho thanks for the review. Addressed.

Awesome, thanks!


Shouldn't Identity state transition trigger OnExit/OnEnter ?

I don't know about other bevy users but personally my state switching logic always looks something like this:

if I'm in state A and condition is met => transition to state B

There are however many cases where we want state A to lead to state A (refreshing UI, going to the next level when we're already in a level, etc…), so in these cases I naturally try to write:

if I'm in state A and condition is met => transition to state A

wishing to trigger OnExit(state A) and OnEnter(state A). But it doesn't work, as we know. Instead, we have to go through hoops and write quite a bit more code to fulfill this simple need.
Now if there are any technical reasons for which it is not desirable to make identity state transition trigger OnExit/OnEnter, I would understand.
If however, if this wasn't implemented for UX reasons, then I want to argue this decision, because:

this behavior is desirable in many legit use cases
I always know which state I'm in when I execute a transition, it's part of the natural state machine design;
so there is no way I would "accidentally" transition from state A to state A and be surprised that OnExit/OnEnter triggers, it's not a footgun
if for some reason I'm blindly transitioning to state A without checking the state I'm in and also didn't want OnExit/OnEnter, the simple solution would be to just… well check the current state ? Problem solved.

So I'm raising this issue to bring up these points because I think it's a common need (from what I could gather on discord anyway) and if it's intentional I think it's interesting to list here the arguments for and against for future google searches :)

I completely agree. In pyri_state you can mutate the next state, and then if current != next, change detection will set a flag to trigger a state transition. However, you can also set that flag yourself to "force" a transition, even if the state hasn't changed.
And then to schedule a system to handle only state change, or state change and refresh, etc., is done via run conditions so you have maximum flexibility there.

This has some unwanted behavior when using substates/computed states. If parent state transitioned (identity transitions included), the child will always emit a transition (identity transitions included). This can be very difficult to debug in the case of identity transitions that are desired, but not caused by parent states.

IMO that's an example of computed / sub states being the wrong abstraction compared to dependent states, which don't have that issue. But that requires a larger change ofc.

I always know which state I'm in when I execute a transition, it's part of the natural state machine design; so there is no way I would "accidentally" transition from state A to state A and be surprised that OnExit/OnEnter triggers, it's not a footgun.

The API design is such that reading states and writing states are distinct. I do have systems that set states without reading them, so for me this kind of feature would interfere with those systems. And I'd expect a state transition to mean a change so I feel like this violates the principle of least surprise.
Rather than overloading OnEnter/OnExit, I wonder if instead there's a new verb like OnReset that might not suffer from those problems.

I do have systems that set states without reading them, so for me this kind of feature would interfere with those systems.
And in those systems you really need identity transition to not trigger OnExit/OnEnter ?
Would it not be acceptable to check the state here as a workaroud ?

I'd be really curious to have a concrete example of your usecase if possible

Sure thing.
/// Check components to determine MinibufferState's state.
pub(crate) fn set_minibuffer_state(
    query: Query<&AskyPromptState>,
    key_chords: Query<&GetKeyChord>,
    mut next_minibuffer_state: ResMut<NextState<MinibufferState>>,
) {
    let is_active = query.iter().any(|x| matches!(x, AskyPromptState::Waiting))
        || key_chords.iter().next().is_some();

    next_minibuffer_state.set(if is_active {
        MinibufferState::Active
    } else {
        MinibufferState::Inactive
    });
}

Any system that has NextState without State is an instance of this pattern.

Here's an idea for an alternative:
        .add_systems(OnExit(AppState::Menu), cleanup_menu)
        .add_systems(OnEnter(AppState::InGame), setup_game)
        .add_systems(OnExit(AppState::InGame), cleanup_game)
        .add_systems(Update, (cleanup_game, setup_game).chain().run_if(on_reset(AppState::InGame)))
//...

#[derive(Event)]
pub struct ResetState<S>(pub S);

pub fn on_reset<T: States>(state: T) -> impl FnMut(EventReader<ResetState<T>>) -> bool + Clone {
    move |mut reader: EventReader<ResetState<T>>| reader.read().any(|e| e.0 == state)
}

To give context as to where this stands right now:

States have internal identity transitions
OnTransition can detect identity transitions
OnEnter, OnExit cannot
custom_transitions example shows how you can add OnReenter and OnReexit, which behave as described

The reason why the "Re" schedules aren't in core is because it adds overhead even when not used.
A more resilient approach would be to decide which schedules to enable when adding state:
app.add_state(MyState::Startup)
  .no_default_transitions()
  .reenter()
  .reexit();

but that was way out of scope for 0.14. We can definitely have this in 0.15 though.

Rather than overloading OnEnter/OnExit, I wonder if instead there's a new verb like OnReset that might not suffer from those problems.

Users can have any verb they want, without adding overhead for the users that don't want them, if we use run conditions instead of schedules for "on enter" / "on exit" etc.

@Inspirateur does the https://github.com/MiniaczQ/bevy/blob/main/examples/state/custom_transitions.rs resolve this issue?

@Inspirateur does the https://github.com/MiniaczQ/bevy/blob/main/examples/state/custom_transitions.rs resolve this issue?

Been a while but I think this is the "going through hoops and write quite a bit more code" I was referring to. I would like it to be simpler :/

No, there's a proof of concept in pyri_state that works just fine. This is not an unsolveable problem.

I've created an issue with a proposal to upstream the approach taken in the custom_transitions example: https://github.com/bevyengine/bevy/issues/15478. I don't have time currently to work on implementing this myself.


Function access own URL

Hi there,
I need an AWS Function to have access to its own URL. I can't seem to link a Function to itself. Have I failed at reading comprehension?
Cheers,
Wilfred

Config, code, and error
// config.sst.ts snippet
    new sst.aws.Function("WebhookStripeFunction", {
      handler: "src/lambdas/webhook/stripe.paymentConfirmation",
      url: true,
      link: [],
      vpc,
    })

// src/lambdas/webhook/stripe snippet
    const { url } = Resource.WebhookStripeFunction

 Error    "WebhookStripeFunction" is not linked in your
          sst.config.ts to app-stage-WebhookStripeFunctionFunction

Nah this is tricky to do. It's a circular dependency. There are some work arounds, which is basically putting it in an SSM parameter and fetching it later. Or having a custom domain so you know the url upfront.


Github Label request for App Toolkit

Problem Statement
App Toolkit as a package leverages TCE as the community, and the user engagement interface. This means that TCE users will raise issues typically in the TCE repo about App Toolkit.
Request
From a tracking and collecting user feedback perspective, it will be really helpful if we can create a label area/packages/app-toolkit so that I can label any incoming issues correspondingly.
Describe alternatives you've considered
My alternative is to manually look for the issues today, and it is not sustainable at all :)

@kartiklunkad26 Does package/app-toolkit for a label work?

Totally!


Add examples for for JACK transport and timebase master

Follow up to #72. Obsoletes #19.
Signed-off-by: Christopher Arndt<EMAIL_ADDRESS>

You have already changed a few double quotes to single quotes, but for my taste you could change even more.
I haven't been completely consistent TBH, but #77 should improve this.

Thanks for the review!
I'm currently a bit busy, but I will try to address these issues / questions in a few days.

@mgeier Please review again.

Sorry @SpotlightKid, I kinda forgot about this PR ...
Thanks for your recent changes, what do you think about my still open comments?
There is still a lack of an official way to use jack._lib.JackPositionBBT. Do you want to implement this or should I?
Do you have a suggestion how we should do this?

Since jack_position_bits_t is a bit field, i.e. values are meant to be ORed together, I would just export these as module level constants:
JACK_POSITION_BBT = _lib.JacKPositionBBT
JACK_POSITION_TIMECODE = _lib.JackPositionTimecode
JACK_POSITION_BBT_FRAME_OFFSET _lib.JackBBTFrameOffset
JACK_POSITION_AUDIO_VIDEO_RATIO = _lib.JackAudioVideoRatio
JACK_POSITION_VIDEO_FRAME_OFFSET = _lib.JackVideoFrameOffset

what do you think about my still open comments?

TBH, I don't really care too much, just change these things it in the way you like.

what do you think about my still open comments?

TBH, I don't really care too much, just change these things it in the way you like.

OK, cool, will do.
But I'd first like to hear your opinion on which of those options is the best:

add dict2position(), see #78
add JACK_POSITION_* module constants, as mentione above (https://github.com/spatialaudio/jackclient-python/pull/74#issuecomment-549089422)
add both

I have the feeling that adding only one of them would suffice for now.
If needed, the other one could be added later.


python311Packages.dogpile-cache: 1.3.0 -> 1.3.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python311Packages.dogpile-cache is: A caching front-end based on the Dogpile lock
meta.homepage for python311Packages.dogpile-cache is: https://github.com/sqlalchemy/dogpile.cache
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.3.1 with grep in /nix/store/75av13m0fivn5iys67y1c0l4mnmmqdf6-python3.11-dogpile-cache-1.3.1
found 1.3.1 in filename of file in /nix/store/75av13m0fivn5iys67y1c0l4mnmmqdf6-python3.11-dogpile-cache-1.3.1

Rebuild report (if merged into master) (click to expand)

24 total rebuild path(s)

24 package rebuild(s)

First fifty rebuilds by attrpath
heatclient
ironicclient
manilaclient
nox
openstackclient
python311Packages.bugwarrior
python311Packages.dogpile-cache
python311Packages.openstacksdk
python311Packages.osc-lib
python311Packages.python-heatclient
python311Packages.python-ironicclient
python311Packages.python-manilaclient
python311Packages.python-openstackclient
python311Packages.python-swiftclient
python311Packages.subliminal
python312Packages.dogpile-cache
python312Packages.openstacksdk
python312Packages.osc-lib
python312Packages.python-heatclient
python312Packages.python-ironicclient
python312Packages.python-manilaclient
python312Packages.python-openstackclient
python312Packages.python-swiftclient
swiftclient

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/75av13m0fivn5iys67y1c0l4mnmmqdf6-python3.11-dogpile-cache-1.3.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python311Packages.dogpile-cache https://github.com/r-ryantm/nixpkgs/archive/9d1a45841f9ae5b77e5f2a37b50463ae7dfe98f6.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/9d1a45841f9ae5b77e5f2a37b50463ae7dfe98f6#python311Packages.dogpile-cache

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/75av13m0fivn5iys67y1c0l4mnmmqdf6-python3.11-dogpile-cache-1.3.1
ls -la /nix/store/75av13m0fivn5iys67y1c0l4mnmmqdf6-python3.11-dogpile-cache-1.3.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

9 packages marked as broken and skipped:

python311Packages.subliminal
python312Packages.dogpile-cache
python312Packages.openstacksdk
python312Packages.osc-lib
python312Packages.python-heatclient
python312Packages.python-ironicclient
python312Packages.python-manilaclient
python312Packages.python-openstackclient
python312Packages.python-swiftclient

10 packages built:

heatclient (python311Packages.python-heatclient)
ironicclient (python311Packages.python-ironicclient)
manilaclient (python311Packages.python-manilaclient)
nox
openstackclient (python311Packages.python-openstackclient)
python311Packages.bugwarrior
python311Packages.dogpile-cache
python311Packages.openstacksdk
python311Packages.osc-lib
swiftclient (python311Packages.python-swiftclient)

Maintainer pings

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python311Packages.dogpile-cache is: A caching front-end based on the Dogpile lock
meta.homepage for python311Packages.dogpile-cache is: https://github.com/sqlalchemy/dogpile.cache
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.3.2 with grep in /nix/store/g9zyxchzcrn84nf63lgrjain2vcxa03m-python3.11-dogpile-cache-1.3.2
found 1.3.2 in filename of file in /nix/store/g9zyxchzcrn84nf63lgrjain2vcxa03m-python3.11-dogpile-cache-1.3.2

Rebuild report (if merged into master) (click to expand)

24 total rebuild path(s)

24 package rebuild(s)

First fifty rebuilds by attrpath
heatclient
ironicclient
manilaclient
nox
openstackclient
python311Packages.bugwarrior
python311Packages.dogpile-cache
python311Packages.openstacksdk
python311Packages.osc-lib
python311Packages.python-heatclient
python311Packages.python-ironicclient
python311Packages.python-manilaclient
python311Packages.python-openstackclient
python311Packages.python-swiftclient
python311Packages.subliminal
python312Packages.dogpile-cache
python312Packages.openstacksdk
python312Packages.osc-lib
python312Packages.python-heatclient
python312Packages.python-ironicclient
python312Packages.python-manilaclient
python312Packages.python-openstackclient
python312Packages.python-swiftclient
swiftclient

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/g9zyxchzcrn84nf63lgrjain2vcxa03m-python3.11-dogpile-cache-1.3.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python311Packages.dogpile-cache https://github.com/r-ryantm/nixpkgs/archive/3519ab4c1c73cde2a2dfdfca4561e62aa66683a5.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/3519ab4c1c73cde2a2dfdfca4561e62aa66683a5#python311Packages.dogpile-cache

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/g9zyxchzcrn84nf63lgrjain2vcxa03m-python3.11-dogpile-cache-1.3.2
ls -la /nix/store/g9zyxchzcrn84nf63lgrjain2vcxa03m-python3.11-dogpile-cache-1.3.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

9 packages marked as broken and skipped:

python311Packages.subliminal
python312Packages.dogpile-cache
python312Packages.openstacksdk
python312Packages.osc-lib
python312Packages.python-heatclient
python312Packages.python-ironicclient
python312Packages.python-manilaclient
python312Packages.python-openstackclient
python312Packages.python-swiftclient

10 packages built:

heatclient (python311Packages.python-heatclient)
ironicclient (python311Packages.python-ironicclient)
manilaclient (python311Packages.python-manilaclient)
nox
openstackclient (python311Packages.python-openstackclient)
python311Packages.bugwarrior
python311Packages.dogpile-cache
python311Packages.openstacksdk
python311Packages.osc-lib
swiftclient (python311Packages.python-swiftclient)

Maintainer pings


[AzureMonitorExporter] update test and readme

Changes

update test to explicitly flush
This test has failed twice in the last month. Adding the explicit flush to mitigate.
update readme
Updated instructions to resolve some problems I had today creating test resources.

API change check
API changes are not detected in this pull request.


setInterval throwing Invalid start date error

This is how I'm setting up the schedule:
const sched = later.parse.recur()
    .on(hours).hour()
    .on(minutes).minute();
later.setInterval(fn, sched);

But when I run our unit test suite, it throws Error: Invalid start date.
I've tried it using the text parser as well with a string like at 00:00, but the same error occurs.
I'm thinking either I've missed something important, or there's a weird issue I'm hitting.

I think I've found the culprit: later.js line 633. When the startDate parameter is falsy, it gets set to the Unix epoch; the subsequent call to getTime() is therefore zero. And since JS treats zero as falsy, it fails the check and throws.
There are two other places that are affected: later-core.js line 633 and src/core/schedule.js line 52.

I'm not sure how you are running into this as an issue.  If startDate is null, then it will use the current date as the start date.  If you pass in valid date (or value > 0) then it will use that date.  The only error case would be if you passed in new Date(0)  but it doesn't look like that is what you are doing.  Could you provide the full test case that is failing for you?

PR #112 has the fix needed; all you needed to do was click a button. But if you're happy leaving a bug in that is going to hit a lot of people just because you don't use something, then who am I to argue?

The PR may fix this problem, but it's not clear what the root cause was.  Also, I make assumptions about falsy get time values all over the place so I'm not sure if this fixes all scenarios.
If you know exactly what it is about sinon fake timers that are causing the issue I'd be more inclined to take a fix. Then I would need additional test cases to go with the PR showing that the PR does in fact fix the problem (i.e. they should fail without the fix) when in use with sinon.


Publish docs

Addressed issues
Where can I find the docs?
Description
Added doc build for every push. But, it will only publish with push to main branch. I've already published initial version and it is available under https://tataratat.github.io/bezman/
You might wanna fix some formats, but I think that's for the next PR. Here's an exemplary candidate for potential format improvements.

@jzwar


autosomal recessive cutis laxa type 2, classic type

I am confused by the distinction/cross references on
autosomal recessive cutis laxa type 2, classic type MONDO:0009054
and
autosomal recessive cutis laxa type 2A MONDO:0018163 .
OMIM 219200 https://www.omim.org/entry/219200  should maybe map to ARCL2A (not Classic type)? Same for GARD 0001638 https://rarediseases.info.nih.gov/diseases/1638/cutis-laxa-autosomal-recessive-type-2a
Orphanet 357074  seems appropriately placed on the Classic type.
And why are the ARCL Type 2C and 2D children of the 2A/2 Classic? These have distinct molecular etiologies and would make more sense as siblings of ARCL2A.
Based on the cross-refernces and this page from NORD https://rarediseases.org/rare-diseases/cutis-laxa/ I suggest the following hierarchy:
(Multiple parent terms possible, no change)

-ARCL2A MONDO:0018163
A.-ARCL2, CT MONDO:0009054 (aka ARCL Debre type, etc)
2.-ARCL2C
3.-ARCL2D

@kanems sorry for the delay, I hope to get to this soon. :)

@kanems

I made OMIM:219200 equiv to 'autosomal recessive cutis laxa type 2A', as you requested.
made GARD:0001638 equiv to 'autosomal recessive cutis laxa type 2A' as well
moved synonyms from classic type to 'autosomal recessive cutis laxa type 2A'

Looks like Type 2C and 2D are no longer children of CT


setup config to use user as sudo

Closing issue 78

hi @almaron . Thanks for you contributions. Would you be interested in becoming a maintainer for this repo?


winfile do not work on windows pe 10

It crashed on  windows pe 10:
VCRUNTIME140.dll Not Found、
I see:
Runtime:
Winfile.exe depends on the VS 2015 C++ runtime; you can download that from
https://www.microsoft.com/en-us/download/details.aspx?id=48145

It is expected that WinFile requires the Visual C++ runtime.  I don't think that link is the right one though - download the latest from https://aka.ms/vcredist .  After installing the runtime, does it still fail to launch?

I try to install vcredist on Win 10 PE,But failed.
vcredist  can not be installed on Win 10 PE,

For your information, I had copied these files to the same folder of WinFile executable from my Win 10 installation, and WinFile seemed to be working normally in both Win 10 PE and Win 11 PE:
msvcp140.dll
vcruntime140.dll
vcruntime140_1.dll

(I know it may be discouraged, but sometimes having suitable tools running under PE is very comfortable.)

Oh, I fully understand why it'd be useful to have Winfile run on WinPE.  What I don't know is the best way to support it.  Normally Microsoft distributes software linked against the C runtime as a DLL, because doing so allows the DLL to be updated independently of the program.  WinPE either wants to be statically linked with the runtime DLL, or possibly using an older compiler, to ensure the DLL is already there.  Neither of these would be good to do except to support WinPE.
Good to know that it works by copying the DLLs though.


BUGFIX: Fixed issue where a shortcode's location would not get set to split when using the class leftAlone

In 3.1 to 3.4 at least when using the class or the location leftAlone in a shortcode the location does not get set to split. Which causes the html tag to not get split up correctly, this is simply caused by the wrong case being used in the check for leftAlone, the check is looking for leftALone instead.

I think this either partially fixes  #4095 maybe completely.


Add size parameter to elastic search query #2229

Passing k as size on elastic vector store
Also include test to validate the length
Fixes #2229

Seems good to me - CC @ezimuel!

@mEliehl can you run yarn format please?

@jacoblee93 LGTM, thanks.

Thank you!


Show account Signa balance

As the title says, get account available lock commited balances

@ohager @frankTheTank72 Should we also show the Reserved balance?
On XT Wallet and Phoenix reserved balance is not shown


Not knowing server costs

You can't tell what the cost of a server is without trying to buy it. Perhaps add it to the help tool tip?

Nevermind, you can do buy -info. Should have played longer before making an issue

No problem, but we should look for an easier way to check prices instead of always typing buy -info.
Do you have a suggestion for this?

Oh, btw you want to take part of the SkidInc community and join the subreddit (/r/skidinc? When the game will be in closed-alpha testing, you will be able to post all what you think about the game (feedback, ideas, bugs), and will be notified of any new version.

Hey, I have joined. Reddit user is Rysty :+1:

Oh okay it's you! :smile:
Let me know if you have any suggestion for a better price display for the servers!


RoR group project: set up your Kanban board

We @melkamu12 and @mariegrace31 as group

[ ] Create tasks on your Kanban board based on the project requirements as following

https://github.com/users/melkamu12/projects/9

Hi @melkamu12 and @mariegrace31,
Highlights!

Descriptive and assigned tasks ✔

Your project is complete!  There is nothing else to say other than... it's time to merge it :shipit:
Congratulations! 🎉
Status: Approved ✔
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.

As described in the Code reviews limits policy  you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.


Add unix socket support for --opcache.fcgi-uri parameter with backwards compatibility.

This PR adds support for a user-configurable scheme for the fcgi connection. This makes it possible to use this exporter with php-fpm servers that only expose a unix socket.
I've added backwards compatibility for the old default --opcache.fcgi-uri="<IP_ADDRESS>:9000" (or any other IP:PORT combination without a scheme) to default to tcp.

@floodcode @andrii-bodnar wondering if you guys could take a look at this PR :)


help

(node:25220) UnhandledPromiseRejectionWarning: Error [TOKEN_INVALID]: An invalid token was provided.
at WebSocketManager.connect (C:\Users\user\Downloads\DraconianJSBot-main\DraconianJSBot-main\node_modules\discord.js\src\client\websocket\WebSocketManager.js:133:26)
at Client.login (C:\Users\user\Downloads\DraconianJSBot-main\DraconianJSBot-main\node_modules\discord.js\src\client\Client.js:223:21)
at processTicksAndRejections (internal/process/task_queues.js:93:5)
(Use node --trace-warnings ... to show where the warning was created)
(node:25220) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:25220) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
[DisTube] Downloaded youtube-dl 2<IP_ADDRESS>
(node:93068) UnhandledPromiseRejectionWarning: Error [SHARDING_READY_TIMEOUT]: Shard 0's Client took too long to become ready.
at Timeout.onTimeout (C:\Users\user\Downloads\DraconianJSBot-main\DraconianJSBot-main\node_modules\discord.js\src\sharding\Shard.js:163:16)
at listOnTimeout (internal/timers.js:554:17)
at processTimers (internal/timers.js:497:7)
(Use node --trace-warnings ... to show where the warning was created)
(node:93068) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:93068) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

uh, thats mean ur token is incorrect and if u are using some hosing where not .env environment value not supported, add dotenv code on the top of index.js and shard.js

Just add this

and create a file called “.env” and input code:
TOKEN=UR TOKEN GOES HERE WITHOUT SPACE

(node:98484) UnhandledPromiseRejectionWarning: Error [TOKEN_INVALID]: An invalid token was provided.
at WebSocketManager.connect (C:\Users\user\Downloads\DraconianJSBot-main\DraconianJSBot-main\node_modules\discord.js\src\client\websocket\WebSocketManager.js:133:26)
at Client.login (C:\Users\user\Downloads\DraconianJSBot-main\DraconianJSBot-main\node_modules\discord.js\src\client\Client.js:223:21)
at processTicksAndRejections (internal/process/task_queues.js:93:5)
(Use node --trace-warnings ... to show where the warning was created)
(node:98484) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:98484) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
(node:97060) UnhandledPromiseRejectionWarning: Error [SHARDING_READY_TIMEOUT]: Shard 0's Client took too long to become ready.
at Timeout.onTimeout (C:\Users\user\Downloads\DraconianJSBot-main\DraconianJSBot-main\node_modules\discord.js\src\sharding\Shard.js:163:16)
at listOnTimeout (internal/timers.js:554:17)
at processTimers (internal/timers.js:497:7)
(Use node --trace-warnings ... to show where the warning was created)
(node:97060) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:97060) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
[DisTube] Downloaded youtube-dl 2<IP_ADDRESS>


Fix a bug where 'indices' property from Collections doesn't show up for code-completion.

What's in this pull request?
Fixes a bug where 'indices' property is missing from Set/Dictionary and 'indices' and 'makeIterator()' is missing from Array.
Suggestion on how to fix and final review was done by Doug Gregor.
Resolved bug number: (SR-)
rdar://26642818

Before merging this pull request to apple/swift repository:

[ ] Test pull request on Swift continuous integration.

Triggering Swift CI
The swift-ci is triggered by writing a comment on this PR addressed to the GitHub user @swift-ci. Different tests will run depending on the specific comment that you use. The currently available comments are:
Smoke Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please smoke test
    All supported platforms     | @swift-ci Please smoke test and merge
    OS X platform               | @swift-ci Please smoke test OS X platform
    Linux platform              | @swift-ci Please smoke test Linux platform

Validation Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please test
    All supported platforms     | @swift-ci Please test and merge
    OS X platform               | @swift-ci Please test OS X platform
    OS X platform               | @swift-ci Please benchmark
    Linux platform              | @swift-ci Please test Linux platform

Lint Testing
    Language     | Comment
    ------------ | -------------
    Python       | @swift-ci Please Python lint

Note: Only members of the Apple organization can trigger swift-ci.

@swift-ci smoke test OS X platform


Fix: add mobile app association files

They are needed for the mobile apps.

I don't know about Android.
But for iOS this files needs to be accessible at the same hostname that is used for the deep links. As far as I can tell that is
app.safe.global
So we need this file at: https://app.safe.global/.weel-known/apple-app-site-association
And that probably means: not in this repository?

I see, @biafra23, closing this then.
Please provide the complete and correct files for app.safe.global and I will upload them.

Alternatively please feel free to make the PR yourself in https://github.com/safe-global/web-core, the files should be in the root of the public folder.

@katspaugh I am sorry. I was wrong. Given the correct entitlement (*.safe.global instead of safe.global) in the iOS app, it is possible to have this file at: https://safe.global/.weel-known/apple-app-site-association


Who rewrite

It's still awkward but I wrote a different version of the who are we section.
There's also new images in the project showcase.
Request for comments.

There was a bug in gatsby-background-image.
https://github.com/timhagn/gatsby-background-image/issues/29
They fixed it though, so I'm not sure why we still have the problem. I
think it works locally though...
On Tue, May 7, 2019, 8:53 AM Ryan Drew<EMAIL_ADDRESS>wrote:

@ryandrew14 requested changes on this pull request.
Two more small changes. Only other thing that's making me not want to
merge is that you're going to pass me in commits again. Dang.
In src/content/who/who.json
https://github.com/sandboxneu/sandboxneu.com/pull/22#discussion_r281612641
:

@@ -3,7 +3,7 @@
"img2": "./img2.jpg",
"img3": "./img3.jpg",
"title1": "Who we are",

"p1": "Sandbox is a proudly student-led software group focusing on the enablement of research through technology. We do this by working directly with PIs to build powerful software to help in experiment conduction and data collection.",

"p1": "Sandbox is a club at Northeastern University that accelerates research by building custom software applications to enable data collection, visualization, and more. We work closely with researchers to help them best leverage computation in their work.",

"We work with researchers in across disciplines" or something like that to
show that we don't just work with CS researchers.
In src/content/builds/builds.json
https://github.com/sandboxneu/sandboxneu.com/pull/22#discussion_r281612972
:

@@ -4,21 +4,21 @@
{
"title": "Empathic Accuracy",
"tags": ["React", "Node.js", "Video", "Emotion", "Psychology"],

 "image": "http://www.youandthemat.com/wp-content/uploads/nature-2-26-17.jpg",

 "image": "./empathic.jpg",

Not sure what happened but all the images are Arun now:
[image: Screen Shot 2019-05-07 at 8 53 02 AM]
https://user-images.githubusercontent.com/13836027/57300819-900a0000-70a5-11e9-964f-1ff6f743c5d0.png
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/sandboxneu/sandboxneu.com/pull/22#pullrequestreview-234492268,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABWK2BQZDMJ3GO5W2UL2NKDPUF3WHANCNFSM4HK5DQUA
.


[Refactor] S3 refactor

Reviews
1/1

brad-larson
1

Pull request is reviewed and can be merged to master!
More info

Reviews
1/1

brad-larson
1

Pull request is reviewed and can be merged to master!
More info


External dependencies upgrade - Spring Boot 2.7.1 and Spring Cloud 2021.0.3

Updates external dependencies to align with Spring Boot version 2.7.1 from 2.6.7 and Spring Cloud version 2021.0.3 from 2021.0.2.
Release notesSourced from spring-boot releases.   🐞  Bug Fixes  Values in a spring.data.cassandra.config file can't override some defaults defined in CassandraProperties #31503 @RestControllerAdvice @ExceptionHandler Inconsistent behavior with @RestControllerEndpoint #31501 Malformed json causes BasicJsonParser to throw a NullPointerException #31499 Metadata generated by the configuration properties annotation processor can miss inherited properties from nested classes #31484 JarFile implementation calls close early which breaks verification of signed unpacked nested jars on Oracle JDK #31395 Health indicators that take a long time to respond are difficult to diagnose #31384 Custom Converter annotated with @ConfigurationPropertiesBinding does not get selected if targetType has a static factory method different return type #31341 Tomcat server.max-http-header-size property is ignored when using HTTP/2 #31329 OAuth2 Resource Server Auto-Configuration can only configure a single JWS algorithm #31321 Maven shade plugin configuration in spring-boot-starter-parent does not append META-INF/spring/*.imports files #31316 GraphQL RouterFunctions are unordered which prevents other functions from being ordered after them #31314 spring-boot-dependencies manages spring-ldap-ldif-batch which no longer exists #31254 Dependency task can fail due to BootJar and BootWar afterResolve hooks #31213 MimeMappings does not include application/wasm #31188 spring-configuration-metadata.json is missing for additional-spring-configuration-metadata.json after switching from @Configuration to @AutoConfiguration #31186 Binder(ConfigurationPropertySource... sources) does not assert that sources contains only non-null elements #31183 WebMvcMetricsFilter stopped working since 2.7.0 #31150 Dependency management for mimepull is redundant and the managed version is incompatible with Java 8 #31145 layers.xsd is out of sync with the documentation and implementation for including and excluding module dependencies #31128     📔  Documentation  Make SpringApplication Kotlin samples idiomatic #31463 Harmonize Kotlin example #31458 Remove duplicate content from "The Spring WebFlux Framework" section #31381 Document that property placeholders should use the canonical property name form #31369 Fix typos in the reference documentation #31366 Enable Links for the Javadoc of the Gradle Plugin #31362 Remove "earlier in this chapter" from places where content is now elsewhere in the documentation #31360 Restore custom favicon documentation #31358 Document that when using Lombok it must be configured to run before spring-boot-configuration-processor #31356 Use Lambda-based API in Spring Security examples #31354 Fix typo in name of imports file in javadoc of ImportCandidates.from #31277 Typos in documentation ("spring-factories" instead of "spring.factories") #31206 Fix Custom Layers Configuration section title in Maven plugin docs #31180 org.springframework.boot.actuate.autoconfigure.metrics.graphql has no package info #31140 Update Dynatrace Micrometer registry documentation #31132     🔨  Dependency Upgrades  Upgrade to AppEngine SDK 1.9.97 #31421 Upgrade to Byte Buddy 1.12.11 #31508 Upgrade to Couchbase Client 3.3.1 #31422 Upgrade to Dropwizard Metrics 4.2.10 #31488 Upgrade to Elasticsearch 7.17.4 #31423 Upgrade to Embedded Mongo 3.4.6 #31424 Upgrade to Flyway 8.5.13 #31425 Upgrade to Groovy 3.0.11 #31426 Upgrade to H2 2.1.214 #31427 Upgrade to Hazelcast 5.1.2 #31428 Upgrade to Jetty 9.4.48.v20220622 #31509 Upgrade to jOOQ 3.14.16 #31429 Upgrade to Kotlin Coroutines 1.6.3 #31490 Upgrade to MariaDB 3.0.5 #31431 Upgrade to Micrometer 1.9.1 #31372 Upgrade to MongoDB 4.6.1 #31432 Upgrade to Neo4j Java Driver 4.4.6 #31433 Upgrade to Netty 4.1.78.Final #31434 Upgrade to Postgresql 42.3.6 #31435 Upgrade to Reactive Streams 1.0.4 #31436 Upgrade to Reactor 2020.0.20 #31371 Upgrade to Solr 8.11.2 #31491 Upgrade to Spring AMQP 2.4.6 #31376 Upgrade to Spring Data 2021.2.1 #31374 Upgrade to Spring Framework 5.3.21 #31319 Upgrade to Spring HATEOAS 1.5.1 #31465 Upgrade to Spring Integration 5.5.13 #31483 Upgrade to Spring Kafka 2.8.7 #31377 Upgrade to Spring LDAP 2.4.1 #31373 Upgrade to Spring Security 5.7.2 #31375 Upgrade to Tomcat 9.0.64 #31437 Upgrade to Undertow 2.2.18.Final #31438
This PR is created by GitHub Actions: https://github.com/Azure/spring-cloud-azure-tools/actions/runs/2552732805

/azp run java - spring - tests

/azp run java - cosmos - tests

/azp run - keyvault - tests

API change check
API changes are not detected in this pull request.


Inform user of known long-term export problems for specific languages

Motivation

The export for a few languages (including but not limited to right-to-left languages, see #2020/#2021/#2022/#2385, #2870 as well as #1498) is defective and will not be able to be fixed anytime soon for technical reasons. This might pose a pitfall for users of the system, who should generally be able to expect the system to either work as intended or be fixed in due time.
Proposed Solution

Add a notice when the user is about to export a page to a language where problems are known (that won't be resolved any time soon). Optionally decline to complete the action altogether.
Alternatives

Continue leaving it to the user to stumble across export problems, likely in situations where they are depending on it and where the problem becomes apparent on second or third glance only. This can mean high stress for the person who thought they got help, frustration, additional work and loss of trust for the user of our system as well as a continued baseline of load for the service team.

User Story

As a user, I prefer to be notified of problem areas within the system beforehand so I can work around them to finding out something went wrong after the fact.
Additional Context

It is to be discussed with the service team whether this desirable and to be implemented.
Design Requirements

Proposed to take the form of simple warning messages within the existing message system, which would not require additional design.

To be discussed:

For which languages the PDF export function should be deactivated
How the info sencense should be.

Most problems are caused by the xhtml2pdf library right?
If so, we could also go for an intermediate solution and redirect the user to the html page that we would normally feed into xhtml2pdf instead. Then we could use some js like window.print() to use the browsers built-in export to pdf functionality.
Disadvantages would be that the user experience would be a bit worse and that there are probably slight differences how different browsers convert html to pdf.
Advantage would be that we would have working export and could be pretty sure that the browser handles all languages correctly.
For the ui, we could also show a warning that normal export does not work and offer this as an alternative.
@PeterNerlich @MizukiTemma Do you think something like this could be useful?

Here is a proof of concept:

@david-venhoff
Hmm, technically it should work and provide a temporary solution, but I'm not sure if it is "intuitiv" for users, especially when the existing export bulk action is working for some languages, while they have to use the new procedure for other languages 🤔
What do you think @osmers @nassabay @dkehne ?

I'd have to see it in action to be able to say if it's confusing for users or not...bcs I cannot imagine right now what it looks like

how is table of content then generated/visualised and how is the formatting? Is there a chance to generate the whole munich app as pdf as an example?
We use the print to pdf feature in the entitlement card project but i am not convincend that it is a suitable choice here. Convice me :D

@dkehne
The browser-printed-PDF is only thought for RTL languages (So I understood).
I guess we have to implement our own function to produce table of content for browser-printed-PDF, and probably this will have such difficulties like xhtml2pdf repository 🤔


Android Basics: Fragments Navigation component

URL of codelab
In which task and step of the codelab can this issue be found?
In Jetpack Navigation Component section of Fragments and the Navigation Component
Describe the problem
Typo

NavHost: A NavHost is used to display destinations form a navigation graph within an activity. When you navigate between fragments, the destination shown in the NavHost is updated. You'll use a built-in implementation, called NavHostFragment, in your MainActivity.

This has now been fixed, thanks for filing!


Take advantage of more accurate comment to code mapping?

Assuming that the comments are included in the committed code (and not just the commit comment), perhaps you could use the more accurate comment to code mapping for browsing and search purposes?

Would you mind giving an example? Having a hard time understanding what this means in relation to feature/fix/improvement.

For each line of code in the most recent version, you could associate with it all commit comment fragments that have applied to that line in particular.
With this information, you can get a lot of motivation for why the code is the way it is via browsing/searching based on this information.

For example, you might want to search for "drag and drop" to find code fragments, possibly spread out, that collectively implement drag and drop.

Ah I understand. You'd like to see a relation between the commit comments and the lines of code which they were applied to.
Then be able to search for keywords int the commit comments themselves to see the lines of code which they referenced?
If that's the case, I'm afraid that feature might be a bit out of the scope of the current Bash scripts (which only searches & replaces lines).
One solution might be to perform a grep search on the output of git log using the -A or -B options. Those might give some context to the commit comments.

So do you include the @commit comments in the code submitted? There's a lot of valuable information there with regards to the more accurate comment/lines of code mapping.
One problem with doing this though is that other developers may not be using your tool and so checking out code with @commit comments still included from the last commit would not be good.

@commit comments are removed from the code via the post-commit hook.
As far as code mapping goes, I don't see solution which does not require a database or file of some kind.
If this is just for the programmer to see cool/neat relationships between their commit comments and actual code, it might be worth file for someone else to fork this project.


[BUG] Test suite failing with equinox 0.11.10

Context: bumping equinox in nixpkgs
When using the latest version of equinox (0.11.10), several tests in tests/test_vmap_vmap.py fail with:
AttributeError: module 'equinox.internal' has no attribute 'if_mapped'

Is an update planned to ensure compatibility with equinox ?
Thanks a lot in advance.
-> This is not urgent in any way. I am just anticipating the issue reporting. Don't feel urged to look at this ;)

Hi Gaetan,
this was due to a test case using the now-removed if_mapped. Lineax itself did not actually make use of it, and therefore has remained compatible with equinox.
I just checked - eqxi.if_mapped can be removed from said test case on pre- and post JAX 0.4.36 and the relevant tests run with equinox 0.11.9, as well as 0.11.10.
I'll re-run on the full test suite just in case and will open a PR, @patrick-kidger :)

Hehe we're looking at this at the exact time @johannahaffner . I just opened #119! :D

:D :D
Just out of curiosity: I just set out_axes to the input at the same level (so for instance vmap1_op), what does the extra condition you included do?

Convert eqx.if_array(0) into just a 0. Which is completely pointless on my part, because the output of .as_matrix() is always an array. :p

Haha I see! Thanks :)


FMREST --> curl communication error: (77) after recent RHEL patch

Hello -- Trying to track down the root cause of this issue:
My server applied a patch this morning and afterwards FMREST throws a CURL communication error when trying to call our filemaker server. I ran an undo on the patch and it was working normally again:

Installed     rpm-4.11.3-48.el7_9.x86_64                  @rhel-7-server-rpms
Installed     subscription-manager-1.24.52-2.el7_9.x86_64 @rhel-7-server-rpms
Installed     yum-3.4.3-168.el7.noarch                    @rhel-7-server-rpms

Packages Altered:
Updated nspr-4.34.0-3.1.el7_9.x86_64             @rhel-7-server-rpms
Update       4.35.0-1.el7_9.x86_64               @rhel-7-server-rpms
Updated nss-3.79.0-5.el7_9.x86_64                @rhel-7-server-rpms
Update      3.90.0-2.el7_9.x86_64                @rhel-7-server-rpms
Updated nss-softokn-3.79.0-4.el7_9.x86_64        @rhel-7-server-rpms
Update              3.90.0-6.el7_9.x86_64        @rhel-7-server-rpms
Updated nss-softokn-freebl-3.79.0-4.el7_9.x86_64 @rhel-7-server-rpms
Update                     3.90.0-6.el7_9.x86_64 @rhel-7-server-rpms
Updated nss-sysinit-3.79.0-5.el7_9.x86_64        @rhel-7-server-rpms
Update              3.90.0-2.el7_9.x86_64        @rhel-7-server-rpms
Updated nss-tools-3.79.0-5.el7_9.x86_64          @rhel-7-server-rpms
Update            3.90.0-2.el7_9.x86_64          @rhel-7-server-rpms
Updated nss-util-3.79.0-1.el7_9.x86_64           @rhel-7-server-rpms
Update           3.90.0-1.el7_9.x86_64           @rhel-7-server-rpms

Are you aware of any CURL compatibility issues with recent RHEL updates that I can investigate? I know it wasn't the firewall as I toggled it off and on with no improvement. Are there CURL verify settings I can configure in FMREST?

I haven't heard of any issues yet. This would be the first.
The only security checks the class file does is to check for SSL. You try
turning off that level of security.  Let me know if that works.
$fm -> secure = false;
Otherwise, I believe we're using pretty standard cURL calls.
Ken

Ken d'Oronzio
Paradise Partners, Inc.
866-999-4006 x201
On Mon, Oct 9, 2023 at 9:24 AM bearinaustin @.***>
wrote:

Hello -- Trying to track down the root cause of this issue:
My server applied a patch this morning and afterwards FMREST throws a CURL
communication error when trying to call our filemaker server. I ran an undo
on the patch and it was working normally again:
Installed     rpm-4.11.3-48.el7_9.x86_64                  @rhel-7-server-rpms
Installed     subscription-manager-1.24.52-2.el7_9.x86_64 @rhel-7-server-rpms
Installed     yum-3.4.3-168.el7.noarch                    @rhel-7-server-rpms
Packages Altered:
Updated nspr-4.34.0-3.1.el7_9.x86_64 @rhel-7-server-rpms
Update 4.35.0-1.el7_9.x86_64 @rhel-7-server-rpms
Updated nss-3.79.0-5.el7_9.x86_64 @rhel-7-server-rpms
Update 3.90.0-2.el7_9.x86_64 @rhel-7-server-rpms
Updated nss-softokn-3.79.0-4.el7_9.x86_64 @rhel-7-server-rpms
Update 3.90.0-6.el7_9.x86_64 @rhel-7-server-rpms
Updated nss-softokn-freebl-3.79.0-4.el7_9.x86_64 @rhel-7-server-rpms
Update 3.90.0-6.el7_9.x86_64 @rhel-7-server-rpms
Updated nss-sysinit-3.79.0-5.el7_9.x86_64 @rhel-7-server-rpms
Update 3.90.0-2.el7_9.x86_64 @rhel-7-server-rpms
Updated nss-tools-3.79.0-5.el7_9.x86_64 @rhel-7-server-rpms
Update 3.90.0-2.el7_9.x86_64 @rhel-7-server-rpms
Updated nss-util-3.79.0-1.el7_9.x86_64 @rhel-7-server-rpms
Update 3.90.0-1.el7_9.x86_64 @rhel-7-server-rpms
Are you aware of any CURL compatibility issues with recent RHEL updates
that I can investigate? I know it wasn't the firewall as I toggled it off
and on with no improvement. Are there CURL verify settings I can configure
in FMREST?
—
Reply to this email directly, view it on GitHub
https://github.com/kdoronzio/fmREST.php/issues/15, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEKUF7BQPVMZFO3DUX52XN3X6P3KRAVCNFSM6AAAAAA5YZYJ2OVHI2DSMVQWIX3LMV43ASLTON2WKOZRHEZTGMBWGM2TMOI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Publish ABAP Unit code coverage result

Is it possible to publish ABAP Unit code coverage result in Azure pipelines?
Thanks,
Srini

Yes, definitely, that's how we use it. Here are the steps we use
First npm install to install all node dependencies
steps:
- task: Npm@1
  displayName: 'npm install'
  inputs:
    workingDir: '$(System.DefaultWorkingDirectory)/_<Repo>/drop/'
    verbose: false

then run the script
steps:
- script: 'npm start -- --host=<host> --protocol=https --insecure=true --username=<username> --password=<password> --package=<package>'
  workingDirectory: '$(System.DefaultWorkingDirectory)/_<Repo>/drop'
  displayName: 'Run test'

Then publish the result
steps:
- task: PublishTestResults@2
  displayName: 'Publish Test Results **/result/*.xml'
  inputs:
    testResultsFiles: '**/result/*.xml'

I'm sure you don't need to define the working directory, but "if it works don't fix it"

Hello @matt1as ,
First of all, very nice and informative blog. I have some doubts related to, ABAP system connection guide.
For environment variables, we have to change only the yaml file or do we need to update our system variables like, host, client, user and password anywhere else inside the repo files ?
also, there is one doubt related to, the result files and the test data result, that where we can see all the pipeline output and the graphs.

@Srinu3366  hello, did you get any output, while performing these commands directly into your YML file ? Actually i am facing some issues. Need some help

Sorry for the slow slow reply, I've been more or less afk the last 8 months, but now I'm back. Did you manage to solve the issue?

@matt1as , I used, but, it is not working, I have raised a separate issue also.
NPM start command is not showing any output. Even not any error....


Tseitin Encoding

Closes #5

It'd be great to get your input on this, as I'm still trying to adapt to the style you've used. Took me a while to figure out what you were doing here...
@st.composite
def NNF(draw):
    return draw(st.recursive(variables(), internal))

...but it's some awesome stuff!
As I was writing the test case, I found myself needing a "forgetting" mechanism (cf. #7 ). Let me know if it happens to be somewhere there under a different name.

@blyxxyz Good to merge with this one? Thanks for bearing with me!

Ouch...T.models vs models is what I get for last minute commits.
Lgtm. Merge away if you're fine with it. Will make kissat optional tonight on the other branch.

Merged to have a cleaner PR on the kissat integration. Feel free to re-open if anything remains, but I think we're pretty well set here.


[FLINK-30787][debug] Adds dmesg call to test_controller to check whether it would succeed on Alibaba instances.

This draft adds dmesg to the test_controller.sh to check whether it would work on Alibaba instances to determine whether FLINK-13978 is the cause for the error in the e2e tests.

I mean, it also fails in your personal azure, and the whole dmesg business was added after FLINK-13978.
Chances are this just fails because the tests are run in docker :shrug:

I wanted to verify it because of Robert's comment. He sounded confident that it worked at some point in time. But you're right; it looks like the azure pipeline change didn't cause that. I actually verified the order of the commits, beforehand, but must have mixed up the commit order.
So, I see two options here:

we remove this part of the code again because nobody complained in the passed.
We enable kernel log access in the docker container as explained in this StackExchange thread

I'd say lets remove it since no one has been asking for it.

I was leaning towards this as well. I just wasn't sure whether the dmesg would be of any help in situations where we were just not aware that this dmesg output would be helpful. But looking into example dmesg output, I couldn't come up issues from the past where this would have been useful. :thinking:


Adding Operator

Adding Operator to case sensitive words list.
https://redhat-documentation.github.io/supplementary-style-guide/#operator
https://regexr.com/7eann

Removed in https://github.com/redhat-documentation/vale-at-red-hat/pull/544


Added support for custom engine.

@adamrehn Please note that for now, this has not been tested yet.

Thanks for submitting this! Due to the refactoring that was involved in implementing the prerequisites for this functionality, the actual commit from this pull request can't be merged in, but I have implemented the same functionality in commit 7f682cd and tested that it functions correctly. The command-line syntax is slightly more verbose than what had been proposed, but has the benefit of being more explicit and also facilitating simpler validation logic.
Cheers,
Adam


feat(addon-mobile): possibility drop mobile calendar header

Closes #

@MillerSvt any updates?

@splincode awaiting #8296

@MillerSvt merged

@MillerSvt why cypress tests are failed?

@splincode I think test is incorrect.

In Test component, we provide TUI_CALENDAR_DATE_STREAM with TuiDay of tomorrow
When we create component, tomorrow date will automatically select
When we click on today date, TuiDayRange should be TuiDayRange(today, tomorrow) (not TuiDayRange(today, today))

What do you think?

@MillerSvt can you rewrite the test?

@nsbarsukov