Initial container start stalls before starting slapd when using docker-compose

I can't get the container to finish the initialization of openldap when I use a docker-compose file. If I use the example docker run commands with no customization, it will complete.
Here is my setup:

I cloned v1.2.1 (I also tried stable and v1.2.0) from here.
Ran docker build --network host --build-arg LDAP_OPENLDAP_GID=1000 --build-arg LDAP_OPENLDAP_UID=1000 -t local_osixia_openldap .
Moved to my docker compose project and ran docker-compose up -d.

My docker-compose.yml:
version: "3.3"

networks:
  osinet:
    driver: bridge
    driver_opts:
      com.docker.network.bridge.name: osinet

services:
  ldap:
    container_name: osi_ldap
    image: local_osixia_openldap
    command: --loglevel debug
    environment:
      # - LDAP_OPENLDAP_GID=1000 # leftover from when I was trying to set that without building.....
      # - LDAP_OPENLDAP_UID=1000
      - LDAP_ORGANISATION="My Org"
      - LDAP_DOMAIN="mydomain.com"
      - LDAP_ADMIN_PASSWORD="password"
    volumes:
      - type: bind
        source: ./data/ldap/var-lib-ldap
        target: /var/lib/ldap
      - type: bind
        source: ./data/ldap/etc-ldap-slap.d
        target: /etc/ldap/slap.d
    ports:
      - <IP_ADDRESS>:3389:389
    networks:
      - osinet
    restart: "no"

Note: the ./data directories are owned, and grouped, by 1000.
My docker logs --follow osi_ldap output:
*** CONTAINER_LOG_LEVEL = 4 (debug)
*** Search service in CONTAINER_SERVICE_DIR = /container/service :
*** link /container/service/:ssl-tools/startup.sh to /container/run/startup/:ssl-tools
*** link /container/service/slapd/startup.sh to /container/run/startup/slapd
*** link /container/service/slapd/process.sh to /container/run/process/slapd/run
*** Set environment for startup files
*** ignore : LANG = en_US.UTF-8 (keep LANG = en_US.UTF-8 )
*** ignore : LANGUAGE = en_US.UTF-8 (keep LANGUAGE = en_US:en )
*** Environment files will be proccessed in this order :
Caution: previously defined variables will not be overriden.
/container/environment/99-default/default.startup.yaml
/container/environment/99-default/default.yaml

*** --- process file : /container/environment/99-default/default.startup.yaml ---
*** ignore : LDAP_ORGANISATION = Example Inc. (keep LDAP_ORGANISATION = "My Org" )
*** ignore : LDAP_ADMIN_PASSWORD = admin (keep LDAP_ADMIN_PASSWORD = "password" )
*** ignore : LDAP_DOMAIN = example.org (keep LDAP_DOMAIN = "mydomain.com" )
*** --- process file : /container/environment/99-default/default.yaml ---
*** Run commands before startup...
*** Running /container/run/startup/:ssl-tools...
*** ------------ Environment dump ------------
*** LDAP_LOG_LEVEL = 256
*** SSL_HELPER_AUTO_RENEW_SERVICES_IMPACTED = slapd
*** LDAP_REPLICATION = False
*** LDAP_READONLY_USER_PASSWORD = readonly
*** LC_CTYPE = en_US.UTF-8
*** LDAP_ADMIN_PASSWORD = "password"
*** INITRD = no
*** LDAP_DOMAIN = "mydomain.com"
*** LDAP_REPLICATION_DB_SYNCPROV = binddn="cn=admin,$LDAP_BASE_DN" bindmethod=simple credentials="$LDAP_ADMIN_PASSWORD" searchbase="$LDAP_BASE_DN" type=refreshAndPersist interval=00:00:00:10 retry="60 +" timeout=1 starttls=critical
*** PATH = /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
*** LDAP_SSL_HELPER_PREFIX = ldap
*** LDAP_TLS_KEY_FILENAME = ldap.key
*** LDAP_TLS_VERIFY_CLIENT = demand
*** LANG = en_US.UTF-8
*** LDAP_READONLY_USER = False
*** CONTAINER_SERVICE_DIR = /container/service
*** LANGUAGE = en_US:en
*** LDAP_REPLICATION_HOSTS_ROW_1 = ldap://ldap.example.org
*** LDAP_REPLICATION_HOSTS_ROW_2 = ldap://ldap2.example.org
*** LDAP_READONLY_USER_USERNAME = readonly
*** LDAP_BASE_DN =
*** HOME = /root
*** LDAP_BACKEND = mdb
*** LDAP_TLS = True
*** LDAP_ORGANISATION = "My Org"
*** CONTAINER_LOG_LEVEL = 4
*** LC_ALL = en_US.UTF-8
*** KEEP_EXISTING_CONFIG = False
*** LDAP_TLS_CRT_FILENAME = ldap.crt
*** LDAP_REMOVE_CONFIG_AFTER_SETUP = True
*** HOSTNAME = f5dbd3e91f6d
*** CONTAINER_STATE_DIR = /container/run/state
*** LDAP_TLS_CA_CRT_FILENAME = ca.crt
*** LDAP_REPLICATION_CONFIG_SYNCPROV = binddn="cn=admin,cn=config" bindmethod=simple credentials="$LDAP_CONFIG_PASSWORD" searchbase="cn=config" type=refreshAndPersist retry="60 +" timeout=1 starttls=critical
*** LDAP_RFC2307BIS_SCHEMA = False
*** LDAP_REPLICATION_HOSTS = #COMPLEX_BASH_ENV:TABLE: LDAP_REPLICATION_HOSTS_ROW_1 LDAP_REPLICATION_HOSTS_ROW_2
*** LDAP_CONFIG_PASSWORD = config
*** LDAP_TLS_CIPHER_SUITE = SECURE256:+SECURE128:-VERS-TLS-ALL:+VERS-TLS1.2:-RSA:-DHE-DSS:-CAMELLIA-128-CBC:-CAMELLIA-256-CBC
*** LDAP_TLS_ENFORCE = False
*** ------------------------------------------
*** Running /container/run/startup/slapd...
*** ------------ Environment dump ------------
*** LDAP_LOG_LEVEL = 256
*** SSL_HELPER_AUTO_RENEW_SERVICES_IMPACTED = slapd
*** LDAP_REPLICATION = False
*** LDAP_READONLY_USER_PASSWORD = readonly
*** LC_CTYPE = en_US.UTF-8
*** LDAP_ADMIN_PASSWORD = "password"
*** INITRD = no
*** PATH = /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
*** LDAP_REPLICATION_DB_SYNCPROV = binddn="cn=admin,$LDAP_BASE_DN" bindmethod=simple credentials="$LDAP_ADMIN_PASSWORD" searchbase="$LDAP_BASE_DN" type=refreshAndPersist interval=00:00:00:10 retry="60 +" timeout=1 starttls=critical
*** HOME = /root
*** LDAP_SSL_HELPER_PREFIX = ldap
*** LDAP_BASE_DN =
*** LDAP_TLS_VERIFY_CLIENT = demand
*** LANG = en_US.UTF-8
*** LDAP_READONLY_USER = False
*** CONTAINER_SERVICE_DIR = /container/service
*** LANGUAGE = en_US:en
*** LDAP_REPLICATION_HOSTS_ROW_1 = ldap://ldap.example.org
*** LDAP_REPLICATION_HOSTS_ROW_2 = ldap://ldap2.example.org
*** LDAP_READONLY_USER_USERNAME = readonly
*** LDAP_TLS_KEY_FILENAME = ldap.key
*** LDAP_DOMAIN = "mydomain.com"
*** LDAP_REMOVE_CONFIG_AFTER_SETUP = True
*** LDAP_BACKEND = mdb
*** LDAP_TLS = True
*** LDAP_ORGANISATION = "My Org"
*** CONTAINER_LOG_LEVEL = 4
*** LC_ALL = en_US.UTF-8
*** KEEP_EXISTING_CONFIG = False
*** LDAP_TLS_CRT_FILENAME = ldap.crt
*** HOSTNAME = f5dbd3e91f6d
*** CONTAINER_STATE_DIR = /container/run/state
*** LDAP_TLS_CA_CRT_FILENAME = ca.crt
*** LDAP_REPLICATION_CONFIG_SYNCPROV = binddn="cn=admin,cn=config" bindmethod=simple credentials="$LDAP_CONFIG_PASSWORD" searchbase="cn=config" type=refreshAndPersist retry="60 +" timeout=1 starttls=critical
*** LDAP_RFC2307BIS_SCHEMA = False
*** LDAP_REPLICATION_HOSTS = #COMPLEX_BASH_ENV:TABLE: LDAP_REPLICATION_HOSTS_ROW_1 LDAP_REPLICATION_HOSTS_ROW_2
*** LDAP_CONFIG_PASSWORD = config
*** LDAP_TLS_CIPHER_SUITE = SECURE256:+SECURE128:-VERS-TLS-ALL:+VERS-TLS1.2:-RSA:-DHE-DSS:-CAMELLIA-128-CBC:-CAMELLIA-256-CBC
*** LDAP_TLS_ENFORCE = False
*** ------------------------------------------
Database and config directory are empty...
Init new ldap server...
invoke-rc.d: could not determine current runlevel
invoke-rc.d: policy-rc.d denied execution of stop.

From the non-cusomtized runs, I know that there should be output like Start OpenLDAP..., etc. after the last line I pasted above.
Even after waiting more than 10 minutes, docker logs show no more output, and any attempt to connect to slapd fails (as expected.)
I also ran into this same problem using osixia/openldap:latest.
I have not tried the customizations outside of docker-compose because of https://github.com/moby/moby/issues/23910#issuecomment-407555248
I am on Ubuntu 18.04.
Docker version 18.06.0-ce, build 0ffa825.

Hi @jerrac , I had a similar issue, I think the environment section of your docker compose is incorrect. Also try without quotes in env variables.

@plewin Thank you! It worked!

I've been trying things way too long only to find this issue after literal hours and see that the problem was quotes around my environment variables :man_facepalming:
It would be great if the container could report this issue somehow instead of just stalling, it would save some people a lot of time.

@PureTryOut I am pretty sure that what you are asking for is impossible or at least very difficult to achieve. It seems to me like asking to bash/any shell/program to cope with potential user input mistakes. Only debugging can allow this from my perspective but I may very well be wrong ...


Update KOReader to v2024.04

reMarkable specific changes:

More robust Wi-Fi scripts

v2024.03 Release Notes
v2024.03.1 Release Notes
v2024.04 Release Notes

A quick test of this and it appears to work as expected.


zig 0.9.0

Looks like there are syntax errors in the Lua file. Can you please verify with gofish lint before submitting the PR? Thanks!


XQConnection problems

XQJ API only supports XQuery v3.0, not XQuery v3.1, so the map{} implementation is not supported.
This means that either we 1) switch APIs just for search highlighting or 2) figure out a different method of exporting the qvar map

My solution was to create a BaseXClient class taken from here

I would vote to look for an alternative to the map function
On Jun 15, 2015 7:50 PM, "Jimmy Li"<EMAIL_ADDRESS>wrote:

My solution was to create a BaseXClient class taken from here
https://github.com/BaseXdb/basex/blob/master/basex-examples/src/main/java/org/basex/examples/api/BaseXClient.java
—
Reply to this email directly or view it on GitHub
https://github.com/TU-Berlin/mathosphere/issues/62#issuecomment-112152003
.

I tried but it turns out to be very complicated and I'm not sure it would be possible - the only thing i can maybe think of is to export a string, something like this:
"x: $x/*[1]/@xml:id"

and then parse it using some string functions such as ````fn:tokenize```
Is this a good solution? It seems very unwieldy to me, compared to adding one class

I'm looking forward to process the same xquery expressions with flink i.e. a special flink library that is currently being developed. I can barly imagine that they'd support xquery 3.1.
I guess xquery 3.1 is just too new. But go ahead for now. We can care about backwards compatibility later by adding a xquery version attribute to MathML query generator later.


Zmw/update readme for pass prompt

Coverage decreased (-0.1%) to 92.049% when pulling 86ea27ce60a67abd3dda805ca6019404b0063ccd on zmw/update_readme_for_pass_prompt into<PHONE_NUMBER>a7933362109f177ec0483d8f421fae on master.


Add simple mac addr regression test, refactor bad config regression.

Special thanks to @haesbaert for help with onboarding to project.

@haesbaert updated.


types(runtime-core): add h function overload

I have added an overload for the h function to retrieve types and event types from the HTMLElementTagNameMap. This allows for better event binding in the h function.

/cc @pikax  Do you think this PR is helpful?

@Alfred-Skyblue yes, even if very few people use it, is still good for the overall vue typescript usage :)

The language-tools ecosystem-ci failure isn't related to this PR.

cc @sodatea  Is it possible for ecosystem-ci to implement the functionality of navigating to the corresponding repository in the suite column? This would make it convenient to navigate to the relevant repository when troubleshooting errors. For example:

suite
result
latest scheduled

vueuse
✅ success
✅ success

Of course, this would require us to maintain additional configurations.


Update chain spec for flaming fir 7

Reset flaming fir to master as of today.

Can you please increment the spec_version?

Will reset flaming fir shortly again with these updates if there's no more feedback.


What do the predict Pka output?

Hey @xiaolinpan @Xundrug ,
I am using your pKa predictor for chemoinformatics-related analysis and upon running get the following output:

> {'Acid': {'18': '13.88'},
>  'Base': {},
>  'MolBlock':

What do the Acid and Base dictionaries contain (here: what do '18' and '13.88' indicate)? Is it the atom position and the corresponding pH value?

'18' is the atom index, and '13.88' is the predicted pKa value of the atom '18'.


Background color of buttons is messed up

It seems when I fixed #21 , it messed up the background-color of other buttons too. I apologize for not paying attention to it at that moment.
Would like to fix it under GSSOC' 21.
Thanks!
Screenshot reference:

Hi I am a Gssoc'21 participant and would like to work on this issue , I have experience in css and js , please assign me this issue

This works fine in my system.


Make default materials accessible to users

If you create a tileset and click on the "Opaque Material" slot, it won't show the Cesium default materials included in the Cesium for Unity Package. It seems like that window only brings up materials available in the Assets folder. We should try to find a way to make those materials accessible, whether if its from the package itself, or by importing the materials (and other user-accessible resources) into a folder under Assets.

They do show up if you click the little eye icon. Not sure what the principle is here.

Apparently Unity hides packages that are "imported in an immutable way." Toggling package visibility affects other packages than Cesium for Unity -- for example, "Input System" and "TextMesh Pro." Maybe that's the reason why "TextMesh Pro" prompts users to import the assets, so that they're not hidden from the assets menu.
I looked around the PackageManager API to see if we could make it visible despite being immutable. It seems like local and embedded packages are visible without needing to click the eye icon, embedded meaning that the package is explicitly stored in the project folder and in a custom state.) where, perhaps, the user could make changes. But it may be too much trouble (and also undesired) to embed the package in the user's project.

Would it be a good idea to have a button on the tileset that can generate a custom material (really just clones the default material) and puts it in the user's Assets folder? The new material would automatically be set as the override material for the tileset. We don't really want users to directly manipulate plugin assets anyways - that might cause issues during plugin upgrades, for instance.
In the future, we could make this button do more than just cloning the material - instead it might auto-generate a shadergraph based on a user-defined list of features (metadata properties, transparency, watermask, etc.).


[synthetics-minion] upgrade authorization API from v1beta1 to v1

Is this a new chart
What this PR does / why we need it:
This change will allow the CPM to be built using K8s v1.22+, where the v1beta1 version of the authorization API has been deprecated. The v1 versions of Role and RoleBinding should be drop-in replacements.
Which issue this PR fixes
Special notes for your reviewer:
Thank you!
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] Chart Version bumped
[x] Title of the PR starts with chart name (e.g. [mychartname])

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Kaela Schaefer seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

It looks like I can't sign the CLA until I set my GitHub email address, which can't be retro-actively applied to commits. Closing and reopening so I can sign the CLA.


Update splash image

The splash image is just a placeholder, and you don't particularly like the pastels. This is to serve as a reminder to update it. Make sure to update the citation at the bottom / make sure that we're using an image we "have the rights" to.

TapTap** is a mobile app that allows users to send customizable haptic vibrations to people you care about.


fix: inventory csv pod container creating

Description
When no poller.inventory is specified, there is a problem with an infinite ContainerCreating state.
Fixes # (issue)
Type of change
Please delete options that are not relevant.

[x] Bug fix

How Has This Been Tested?
Manual and integration tests
Checklist

[x] My commit message is conventional
[x] I have run pre-commit on all files before creating the PR
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] I have checked my code and corrected any misspellings

:tada: This PR is included in version 1.7.1-beta.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Usafe use of unsafe that leads to data corruption

This library main perfomance gain based in unsafe hack in decoding strings:
https://github.com/francoispqt/gojay/blob/cce191b2eaf5400d428bf8cb841202ae27fb03c2/decode_string.go#L23-L25
It's will lead to very hard debugging problems with data corruption in some use cases with reuse raw data source bytes.
This behaviour must be specified in the documentation, becuse it's limits library usege ( as general purpose decoder replacement )  and makes benchmarks not really fair.
Here is th demo:
package main

import (
	"bytes"
	"fmt"
	"github.com/francoispqt/gojay"
	"net/http"
	"net/http/httptest"
	"sync"
)

var (
	users   = []*user{}
	bufPool = sync.Pool{
		New: func() interface{} {
			// this line must be printed once
			// to be sure that we reuse previous buffer
			fmt.Println("make new buf")
			return bytes.NewBuffer(make([]byte, 0, 64))
		},
	}
)

type user struct {
	email string
}

func (u *user) UnmarshalObject(dec *gojay.Decoder, key string) error {
	switch key {
	case "email":
		return dec.AddString(&u.email)
	}
	return nil
}

func (u *user) NKeys() int {
	return 1
}

func main() {
	postData :=<EMAIL_ADDRESS>	req := httptest.NewRequest("POST", "http://example.com/", postData)
	w := httptest.NewRecorder()
	ProcessUser(w, req)

	postData =<EMAIL_ADDRESS>	req = httptest.NewRequest("POST", "http://example.com/", postData)
	w = httptest.NewRecorder()
	ProcessUser(w, req)

	// ----------------------------------
	// expected equal users
	fmt.Println(users[0], users[1])
	// got
	//<EMAIL_ADDRESS><EMAIL_ADDRESS>	// ----------------------------------
}

func ProcessUser(w http.ResponseWriter, r *http.Request) {
	buf := bufPool.Get().(*bytes.Buffer)
	buf.Reset() // now we will reuse same bytes buffer from previous request

	// users[0].email (previous user) uses memory from this buffer underliying bytes
	// overriding it will corrupt users[0].email
	// because now there will be different data
	buf.ReadFrom(r.Body)
	defer r.Body.Close()

	newUser := &user{}
	gojay.UnmarshalObject(buf.Bytes(), newUser)
	users = append(users, newUser)

	bufPool.Put(buf)
}

Thanks for the feedback. This is a know side effect. We should definitely add it to the documentation.
Note that using the Decoder api is safer because it keeps its own buffer internally and io.Reader must use copy. So using:
newUser := &user{}
dec := gojay.NewDecoder(strings.NewReader(`{"id":1,"name":"go","email":"gojay@email.com"}`))
dec.DecodeObjec(newUser)

Although, in order to keep the Unmarshal api safe, I have 3 solutions in mind:

We could use unsafe only if a specific config is set or by using gojay.Unsafe.UnmarshalObjec() for example.
Copy the given buffer into the internal buffer at the beginning,
Just not using unsafe at all.

I have tested and benchmarked point 2 and 3. Copying the buffer is faster and results in less allocations.
What do you suggest?

I have made changes copying the buffer at the beginning in the standard API and added an Unsafe api to a new branch. Will add details to documentation and merge the branch. Those changes are in branch update/make-unmarshal-api-safer-for-strings https://github.com/francoispqt/gojay/tree/update/make-unmarshal-api-safer-for-strings

Just merged the branch. Still working on making standard API safer and adding an explicit Unsafe api. Docs have been updated.


Owners should be able to dynamically change the highlights on the dashboard

A scaffold should be created that allows this

Improved admin interface with 42a0a240f5affd1e00e9eb044c3559985cd93719


weaveproxy doesn't handle HostConfig json on start request named "HostConfig"

We handle a HostConfig structure passed unnamed at top level, i.e.
{
   "Memory":0
}

, but not something like:
"HostConfig": {
   "Memory":0
}

Docker appears to handle either, in ContainerConfigWrapper.getHostConfig(), but I haven't tested it yet.

Is this problem present in 1.1.x?

In the sense that passing any kind of HostConfig on start broke the proxy, yes.  That was #1368, which is not fixed on the 1.1 branch.

Fixed by #1534


An error occurs when debugging a python durable project

OS: Mac (Intel)
Build Version: 20230207.6
Repro Steps:

Create and open a python project with "Durable Function orchestrator" function and select "Azure Storage" durable storage type.
Create functions with "Durable Functions activity" and "Durable Functions HTTP Starter" templates.
F5 -> Select "Connect Azure SQL Database".
Check whether no error occurs.

Expect:
No error occurs.
Actual:
An error occurs, more details in Output as below.
*  Executing task: .venv/bin/python -m pip install -r requirements.txt source /Users/admin/Desktop/py-s/.venv/bin/activate
Collecting azure-functions
  Using cached azure_functions-1.13.2-py3-none-any.whl (162 kB)
Collecting azure-functions-durable
  Downloading azure_functions_durable-1.2.2-py3-none-any.whl (215 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 215.0/215.0 KB 784.0 kB/s eta 0:00:00
Collecting aiohttp>=3.6.2
  Downloading aiohttp-3.8.3-cp39-cp39-macosx_10_9_x86_64.whl (360 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 360.7/360.7 KB 1.7 MB/s eta 0:00:00
Collecting requests==2.*
  Downloading requests-2.28.2-py3-none-any.whl (62 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 62.8/62.8 KB 448.8 kB/s eta 0:00:00
Collecting python-dateutil>=2.8.0
  Downloading python_dateutil-2.8.2-py2.py3-none-any.whl (247 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 247.7/247.7 KB 587.9 kB/s eta 0:00:00
Collecting furl>=2.1.0
  Downloading furl-2.1.3-py2.py3-none-any.whl (20 kB)
Collecting certifi>=2017.4.17
  Downloading certifi-2022.12.7-py3-none-any.whl (155 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 155.3/155.3 KB 650.8 kB/s eta 0:00:00
Collecting idna<4,>=2.5
  Downloading idna-3.4-py3-none-any.whl (61 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 61.5/61.5 KB 625.3 kB/s eta 0:00:00
Collecting urllib3<1.27,>=1.21.1
  Downloading urllib3-1.26.14-py2.py3-none-any.whl (140 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 140.6/140.6 KB 730.1 kB/s eta 0:00:00
Collecting charset-normalizer<4,>=2
  Downloading charset_normalizer-3.0.1-cp39-cp39-macosx_10_9_x86_64.whl (124 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 124.0/124.0 KB 785.8 kB/s eta 0:00:00
Collecting aiosignal>=1.1.2
  Downloading aiosignal-1.3.1-py3-none-any.whl (7.6 kB)
Collecting async-timeout<5.0,>=4.0.0a3
  Downloading async_timeout-4.0.2-py3-none-any.whl (5.8 kB)
Collecting charset-normalizer<4,>=2
  Downloading charset_normalizer-2.1.1-py3-none-any.whl (39 kB)
Collecting multidict<7.0,>=4.5
  Downloading multidict-6.0.4-cp39-cp39-macosx_10_9_x86_64.whl (29 kB)
Collecting yarl<2.0,>=1.0
  Downloading yarl-1.8.2-cp39-cp39-macosx_10_9_x86_64.whl (61 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 61.2/61.2 KB 724.3 kB/s eta 0:00:00
Collecting attrs>=17.3.0
  Downloading attrs-22.2.0-py3-none-any.whl (60 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 60.0/60.0 KB 899.6 kB/s eta 0:00:00
Collecting frozenlist>=1.1.1
  Downloading frozenlist-1.3.3-cp39-cp39-macosx_10_9_x86_64.whl (36 kB)
Collecting orderedmultidict>=1.0.1
  Downloading orderedmultidict-1.0.1-py2.py3-none-any.whl (11 kB)
Collecting six>=1.8.0
  Downloading six-1.16.0-py2.py3-none-any.whl (11 kB)
Installing collected packages: azure-functions, urllib3, six, multidict, idna, frozenlist, charset-normalizer, certifi, attrs, async-timeout, yarl, requests, python-dateutil, orderedmultidict, aiosignal, furl, aiohttp, azure-functions-durable
Successfully installed aiohttp-3.8.3 aiosignal-1.3.1 async-timeout-4.0.2 attrs-22.2.0 azure-functions-1.13.2 azure-functions-durable-1.2.2 certifi-2022.12.7 charset-normalizer-2.1.1 frozenlist-1.3.3 furl-2.1.3 idna-3.4 multidict-6.0.4 orderedmultidict-1.0.1 python-dateutil-2.8.2 requests-2.28.2 six-1.16.0 urllib3-1.26.14 yarl-1.8.2
WARNING: You are using pip version 22.0.4; however, version 23.0 is available.
You should consider upgrading via the '/Users/admin/Desktop/py-s/.venv/bin/python -m pip install --upgrade pip' command.
*  Terminal will be reused by tasks, press any key to close it. *  Executing task: . .venv/bin/activate && func host start Found Python version 3.9.13 (python3). Azure Functions Core Tools
Core Tools Version:       4.0.4776 Commit hash: N/A Integration build number: PreRelease220902-0439 (64-bit)
Function Runtime Version: <IP_ADDRESS>03
Functions:         DurableFunctionsHttpStart: [POST,GET] http://localhost:7071/api/orchestrators/{functionName}         DurableFunctionsOrchestrator: orchestrationTrigger         Hello1: activityTrigger For detailed output, run func with --verbose flag.
[2023-02-10T08:31:01.599Z] Worker process started and initialized.
[2023-02-10T08:31:02.041Z] Worker failed to load function: 'DurableFunctionsHttpStart' with function id: '4e9aad98-9f6d-4cfe-876b-3ba8ec9f35a5'.
[2023-02-10T08:31:02.041Z] Result: Failure
[2023-02-10T08:31:02.041Z] Exception: ModuleNotFoundError: No module named 'azure.durable_functions'. Please check the requirements.txt file for the missing module. For more info, please refer the troubleshooting guide: https://aka.ms/functions-modulenotfound
[2023-02-10T08:31:02.041Z] Stack:   File "/usr/local/bin/workers/python/3.9/OSX/X64/azure_functions_worker/dispatcher.py", line 355, in _handle__function_load_request
[2023-02-10T08:31:02.041Z]     func = loader.load_function(
[2023-02-10T08:31:02.041Z]   File "/usr/local/bin/workers/python/3.9/OSX/X64/azure_functions_worker/utils/wrappers.py", line 42, in call
[2023-02-10T08:31:02.041Z]     raise extend_exception_message(e, message)
[2023-02-10T08:31:02.041Z]   File "/usr/local/bin/workers/python/3.9/OSX/X64/azure_functions_worker/utils/wrappers.py", line 40, in call
[2023-02-10T08:31:02.041Z]     return func(*args, **kwargs)
[2023-02-10T08:31:02.041Z]   File "/usr/local/bin/workers/python/3.9/OSX/X64/azure_functions_worker/loader.py", line 127, in load_function
[2023-02-10T08:31:02.041Z]     mod = importlib.import_module(fullmodname)
[2023-02-10T08:31:02.041Z]   File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/importlib/__init__.py", line 127, in import_module
[2023-02-10T08:31:02.041Z]     return _bootstrap._gcd_import(name[level:], package, level)
[2023-02-10T08:31:02.041Z]   File "/Users/admin/Desktop/py-s/DurableFunctionsHttpStart/__init__.py", line 11, in <module>
[2023-02-10T08:31:02.041Z]     import azure.durable_functions as df
[2023-02-10T08:31:02.041Z] .
[2023-02-10T08:31:02.049Z] Worker failed to load function: 'DurableFunctionsOrchestrator' with function id: 'efaf0e24-cd19-4e65-99fc-8543530a9d07'.
[2023-02-10T08:31:02.049Z] Result: Failure
[2023-02-10T08:31:02.049Z] Exception: ModuleNotFoundError: No module named 'azure.durable_functions'. Please check the requirements.txt file for the missing module. For more info, please refer the troubleshooting guide: https://aka.ms/functions-modulenotfound
[2023-02-10T08:31:02.049Z] Stack:   File "/usr/local/bin/workers/python/3.9/OSX/X64/azure_functions_worker/dispatcher.py", line 355, in _handle__function_load_request
[2023-02-10T08:31:02.050Z]     func = loader.load_function(
[2023-02-10T08:31:02.050Z]   File "/usr/local/bin/workers/python/3.9/OSX/X64/azure_functions_worker/utils/wrappers.py", line 42, in call
[2023-02-10T08:31:02.050Z]     raise extend_exception_message(e, message)
[2023-02-10T08:31:02.050Z]   File "/usr/local/bin/workers/python/3.9/OSX/X64/azure_functions_worker/utils/wrappers.py", line 40, in call
[2023-02-10T08:31:02.050Z]     return func(*args, **kwargs)
[2023-02-10T08:31:02.050Z]   File "/usr/local/bin/workers/python/3.9/OSX/X64/azure_functions_worker/loader.py", line 127, in load_function
[2023-02-10T08:31:02.050Z]     mod = importlib.import_module(fullmodname)
[2023-02-10T08:31:02.050Z]   File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/importlib/__init__.py", line 127, in import_module
[2023-02-10T08:31:02.050Z]     return _bootstrap._gcd_import(name[level:], package, level)
[2023-02-10T08:31:02.050Z]   File "/Users/admin/Desktop/py-s/DurableFunctionsOrchestrator/__init__.py", line 13, in <module>
[2023-02-10T08:31:02.050Z]     import azure.durable_functions as df
[2023-02-10T08:31:02.050Z] .
[2023-02-10T08:31:05.884Z] Host lock lease acquired by instance ID '0000000000000000000000006BBC7B5B'.

More Info:

This issue also reproduces for the C# project created with "Netherite/MSSQL" durable storage type.
This issue doesn't reproduce on Windows and Linux.

Verified this issue using build 20230304.7 and Python version 3.10.9, it doesn't reproduce for now. So close it.


Bug: tweet-count-sync cronjob fetches cached tweet count every time

Every time the vercel cron job runs the tweet-count-sync route it fetches the cached tweet count number and never updates.

.take


Added caching of the sphericart class

As the title says - the C++ class gets cached to avoid recomputing prefactors and allocating buffers

one question would be whethere we should have a global cache (and mutex) or these static variables inside the function call are better / acceptable. no strong feelings.

Before merging this, I would like to see some benchmarks showing the additional code complexity actually makes a difference in the run time!

Fair point. Of course this will matter most for single-point evaluations:
main:
**** Timings for l_max=10, n_samples=1, n_tries=10000, dtype=<class 'numpy.float64'> ****
 No derivatives:   176133.6 ns/sample ±   210027.3 (std)
Warm-up timings / sec.:
 [0.02956653 0.00033665 0.00021601 0.00020289 0.00019646]
 No derivatives, jit:    21250.1 ns/sample ±    96404.4 (std)
Warm-up timings / sec.:
 [2.13901997e-02 4.07695770e-05 1.97887421e-05 1.74045563e-05
 1.74045563e-05]
******************************************************************************
**** Timings for l_max=10, n_samples=1, n_tries=10000, dtype=<class 'numpy.float32'> ****
 No derivatives:   318842.6 ns/sample ±   449239.1 (std)
Warm-up timings / sec.:
 [0.05334806 0.00054049 0.00036287 0.00033236 0.00033402]
 No derivatives, jit:    24297.7 ns/sample ±   142685.3 (std)
Warm-up timings / sec.:
 [2.74960995e-02 7.12871552e-05 2.38418579e-05 1.95503235e-05
 2.00271606e-05]
******************************************************************************

and with the caching
**** Timings for l_max=10, n_samples=1, n_tries=10000, dtype=<class 'numpy.float64'> ****
building cache for 10
 No derivatives:   154535.5 ns/sample ±    84238.2 (std)
Warm-up timings / sec.:
 [0.03519225 0.00052285 0.00022197 0.00019693 0.00018859]
 No derivatives, jit:    10995.7 ns/sample ±    26506.2 (std)
Warm-up timings / sec.:
 [1.27654076e-02 2.55107880e-05 1.09672546e-05 9.05990601e-06
 9.29832458e-06]
******************************************************************************
**** Timings for l_max=10, n_samples=1, n_tries=10000, dtype=<class 'numpy.float32'> ****
building cache for 10
 No derivatives:   155199.5 ns/sample ±    73677.0 (std)
Warm-up timings / sec.:
 [0.03316307 0.00039434 0.00023556 0.00020313 0.00019813]
 No derivatives, jit:    10775.5 ns/sample ±    59800.5 (std)
Warm-up timings / sec.:
 [1.67512894e-02 4.45842743e-05 1.09672546e-05 9.53674316e-06
 9.29832458e-06]
******************************************************************************

one-sample evaluation may not be the typical use case, but a 2x speedup in this corner case seems to me worth the 10 extra lines of code

Probably not to be fixed in this PR, but looks like Hessian evaluation is 1000x more expensive than gradients


Weird scrolling bug in Android 9

Summary
When scrolling the message pane, the scroll direction reverses after you let go.
Environment Information

Device Name: Pixel
OS Version: 9
Mattermost App Version: 1.12.0 (142)
Mattermost Server Version: 5.3.0 (Build 5.3.1)

Steps to reproduce
Open any channel/conversation history, and swipe rapidly down (to scroll up to older messages) or up (to scroll down to newer messages). Then let go of the screen.
Expected behavior
After letting go, the pane continues moving in the same direction, gradually slowing down.
Observed behavior
After letting go, the pane begins to move in the opposite direction. This effect can only be avoided by coming to a complete stop before letting go of the screen.
Possible fixes
Not sure, but I'm guessing there's a sign error somewhere.

Hi @cburschka, this issue will be fixed in v1.13 - here are links to the fixes for reference:
-https://mattermost.atlassian.net/browse/MM-12273
-https://github.com/mattermost/mattermost-mobile/pull/2161
If you want to, you can sign up for beta testing and then download the latest app version from Google Playstore. It includes a fix for this scrolling issue and community members have reported that it works.

Thanks very much! I'll be using the beta version for now, which seems to be working well so far.


Add screenshot of the GitHub Card!

That looks good, mate!! 🔥
Keep crushing 🚀

@pushkaraj2007 Just noticed, the image link is from my repository. Make sure to change it!


crypto/tls: QUICConn.SendSessionTicket should check Config.SessionTicketsDisabled

What version of Go are you using (go version)?

$ go version
go version go1.21.0 darwin/arm64

Does this issue reproduce with the latest release?
Yes
What did you do?
When QUICConn.SendSessionTicket is called even though Config.SessionTicketsDisabled is set, an error is returned ("session ticket keys unavailable").
Now one could argue that the QUIC stack do that check before calling SendSessionTicket (and that's what quic-go does), however, the QUIC stack won't have access to the tls.Config used on the connection if it is a config returned by GetConfigForClient (unless the QUIC stack wraps that callback and keeps track of the invocations, which would be quite a bit of complexity).
What did you expect to see?
Instead, it would be easy for crypto/tls to check the Config.SessionTicketsDisabled flag on the config that's in use on the connection.
API-wise, there are two options here:

return nil
return a sentinel error

No strong preference in either direction.
cc @neild @FiloSottile

Seems reasonable to me. The TLS layer should be checking SessionTicketsDisabled, since it owns that configuration, and the QUIC layer shouldn't be left holding an uninterpretable error when tickets are disabled.
I think its safe at the moment for the QUIC layer to just ignore all errors from SendSessionTicket, but it's reasonable to want a way to identify the expected error case.
I don't have a strong opinion on whether SendSessionTicket should return nil or a distinguishable error when tickets are disabled. nil is less API surface, but doesn't give the QUIC layer any way to identify the case where a ticket wasn't sent. I don't know why the QUIC layer would need to care, though; I presume all it's going to do is ignore the error, so maybe nil is simple and sufficient.


Audit/Testing: various tweaks

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[x] Have you successfully run brew tests with your changes locally?

Working on replacing myself with CI so I can ride off into the sunset/be more useful around brew rather than core. Here's some changes.
You probably hate the test one, let me know. The change itself has been discussed between @MikeMcQuaid & I for a while, but I'm not promising the implementation will be to everyone's admiration.

:+1: 🚢

This can cause false negatives we currently do not get so I'm not sure why you'd want to ship it since it doesn't actually fix any existing bug anyone has pointed to.

Some of your concerns are valid and I'll think about them before shipping that aspect of the changes here. I had stuff to do yesterday so wasn't around.
I'll note though that if you want me to look at your comments on maintaining the core with more significance it would be helpful if you helped maintain more of the core; your own PRs are of a high standard & you throw a lot of work into contributing to those and keeping formulae up-to-date, which is fantastic.
You've got issues specifically reopened that were then left for dead, tracking issues which aren't particularly complicated & could be resolved relatively swiftly, and there's stuff like https://github.com/Homebrew/brew/pull/770 which was a solid fix improving UX that needed just a little tweaking & you closed it citing "lack of patience".
If you want to take over core stuff completely, please, feel free, but I find it quite grating till then to have my concerns about the status quo dismissed by someone who proposes changes, is asked to help implement them and in reply there's a vaguely non-committal shrug. You're entirely welcome to pick & choose what you work on, everyone does to some extent, but if you want to dismiss my concerns I'd appreciate it if you didn't leave those concerns on my plate forevermore.
Whilst I may be a total PITA to work with, I'm a total PITA who at least attempts to propose or even implement alternatives if I shoot down someone else's fix for an issue that is bothering them.

I'm confident you'll realize at some point the above comment is not only gratuitous but also entirely inappropriate for this venue.

I'm going to pretty drastically cut back on the amount of core work I do, so I've dropped the test changes. Someone else can pick it up if they care.


Can it be run without cuda?

Am trying to start predict.py, but throws exception, RuntimeError: CUDA environment is not correctly set up
Though am not using --gpu parameter.

I think you are supposed to explicitly set --gpu -1 as opposed to using the default setting; I believe --gpu 0 instructs the cupy library used in the program to use the first available gpu.


Batch processing - Run batch - Disable when invalid inputs

Story
As a scientist, I want to execute segmentation workflows on a batch of many files so that I can do real science
A/C

Given I have selected a JSON config file
And a channel index
And an input directory
And an output directory
Then the "Run batch" button is enabled
Otherwise, if any field is missing, the "Run batch" button is disabled

Details

Enable / disable "Run batch" button based on status of form
All 4 inputs should be entered for the button to be enabled. Update status of button as user interacts with the form.

included in this PR: https://github.com/AllenCell/napari-aicssegmentation/pull/97


fix: decouple info with security

POC for https://github.com/omisego/elixir-omg/issues/1065
https://github.com/omisego/elixir-omg/issues/1065#issuecomment-549185608

Coverage decreased (-12.6%) to 76.756% when pulling 9968de5e3b6cb183a50ca5d6b730b374838ff5d6 on infoapi_bus_poc into 403990c59f351f4fa46d11b288b50e2dd34bc03a on master.

@unnawut This is starting to get interesting, you may wanna have a look and we can discuss tomorrow.

@InoMurko From discussion with @T-Dnzt, how would this bus work for retrieving past events?
A listener downstream that consume & store all events, then serve that outside this OMG.Bus and OMG.Bus.PubSub? Or it'll be handled by OMG.Bus.PubSub.

Not sure I fully grasp the dimension of your question because the answer rather simple:
security properties of watcher ensure all events are aligned to a certain block. When syncing stops (for example because of byzantine events) watcher continues synchronization from the last known block. If watcher syncs, you get all the events from the bus.
Does that answer your question? If not, what product requirements are you talking about?

To sum up the discussion, we were talking two approaches indeed:

A lean Informational API. Exposes as much raw data as possible. Provides no derived information. Likely only few endpoints with simple and flat response structure.

A feature-rich informational API. Exposes as much useful data as possible. Performs aggregations and 3rd party sources to compile a complete response. Advanced filtering and conditions.

The lean approach is straightforward and probably not even need a split. And the OMG.Bus is suffice for the data flow within the umbrella app. So no questions there.
My question was specifically to the feature-rich approach with the Informational API split out to a new umbrella app. And so in this scenario we would need ...

A sync mechanism, including replay.
The sync mechanism would not reside in OMG.Bus.
The sync code would rely solely on the OMG.Bus to maintain strict separation of concerns as a data transporter.

Extra note: I take it that your primary concern now is to get the separation of concerns between security vs. info up via the OMG.Bus. Then the sync mechanism, be it DB inserts, DB replica, PubSub feed, options are all open, as long as it talks to the bus and only the bus.

Thanks for putting together these notes. I'm indeed in favor of a feature-rich informational API. As you said, if it's going to be lean, probably no reason to split it.
The feature-rich split will allow us to do pretty much anything business or product would like us to do. We could do DB aggregations in SQL rather than in code. It will give us the freedom to add tables as needed (eg: an ERC20 token table, reporting rollup tables). We could also build and perform our own business-analytics on our DB without having to worry about putting load on the watcher.
In addition to a feature-rich API, if we start the split off in the right way, we can get some really good tests written. Testable code is well-designed code. 😄

I would just like to emphasize that splitting the codebase IS in our roadmap.

Childchain
Watcher (no reason to further divide the codebase if it's much easier to support security and informational in the same codebase)
Common stuff

My opinion is that it is much much harder to maintain stability with increased fragmentation. And increasing fragmentation WILL not solve code quality. If you can't address code quality in a mono repo, you sure won't in a fragmented codebase.

Glad to hear about the common lib. Didn't know about that part.
I know this is only anecdotal evidence, but I started working at Amazon around January 2000. Their entire codebase was a single C++ app that was so large it could literally not be built. When running it almost could not fit in memory either.
It was a nightmare. During my time they we refactored the code out to CustomerService, OrderService, etc...
That changed everything. Features of each service  could be released independently. The API boundaries between what defined OrderService and CustomerService became clearly defined and testable...
You've also got the whole Micro Services pattern these days. It has its merits and strengths too....but also some drawbacks.
My real-life experience in splitting things up into logical-grouped components is pretty compelling. Indeed that's exactly what classes and module are for.
Nothing is free though. There are tradeoffs. For example this does have a DevOps cost. Sorry Jake. 😉

We’re hardly Amazon.


[!] CocoaPods could not find compatible versions for pod "SwiftJWT":   In Podfile:     SwiftJWT

Why don't I install SwiftJWT.

@Bruce9487
Thanks for raising this issue, is it possible you could provide the contents of your Podfile?
Thanks!

Also, What is your ios deployment target? SwiftJWT currently requires ios 11.0. If you require 10.0 you should be able to point at the 3.2 release:
pod 'SwiftJWT' , '~> 3.2'

@ddunn2 @Andrew-Lees11
Thanks, I change my platform to ios '11.0', and it's work to download.
Sorry for reporting this issue.

You don't have to apologize. I'm glad we were able to help.


Run unit tests in CI

Run node unit tests in CI

There's a single failing test, but I also saw an error message (see below) that makes it seem like a live version (ie hosted by a running webserver) is expected. Let me know if that's required
NetworkError: Error: connect ECONNREFUSED <IP_ADDRESS>:80

@ivan-c My apology for the failing test, please see my fix here. Also, feel free to ignore the network error you see. It is expected, see here.  The tests should be able to complete even with the network error.


Running GenericContainer with CMD isn't working properly

What I understand from https://www.testcontainers.org/features/commands/ the docs for creating a container with CMD is that the following command
docker container run
--publish 9092:9082
--detach
--name h2
nemerosa/h2
must be equivalent to
@ClassRule
public static GenericContainer h2db =
new GenericContainer("nemerosa/h2")
.withCommand("--publish 9092:9082", "--detach", "--name lm", "nemerosa/h2")
.withStartupTimeout(Duration.ofSeconds(Constants.TIMEOUT_DURATION));
In test-containers. Which is not the case or I am missing something ?

publish, detach and others are Docker's flags. "command" is what comes after the image (empty, in your case)

Thank you for the verification

Btw is there a way to use publish or detach, somehow with the library ?

for publish see https://www.testcontainers.org/features/networking/#exposing-container-ports-to-the-host
detach - you don't really need it, since it is Docker CLI's feature (to start in background), while in Testcontainers everything is "started in background", if one can call it so


Bug: Obvious keys for tag and delete are unavailable

Neither space, delete nor backspace work as key sequences, either alone or with a modifier. As there is only an option of a like tag at the moment, the space bar is an obvious key to use as it's the largest, and delete/backspace are the most obvious choice for deleting. This is with Chrome on Windows 11. Haven't tested Linux yet or fired up Browser Stack to test other environments, and it may be a feature/limitation and not necessarily a bug per-se, however one would expect it to work so worth resolving is possible.

only key sequences involving the keys 'shift', 'ctrl', and alphanumeric characters (a to z, 0 to 9) are currently allowed


dpp training stuck ( lightning=1.4.9 )

I'm stuck using lightning=1.4.9
the numbers "96% 4260/4435" keeps the same forever.

Dear @yinrong,
Would it be possible for you to provide a reproducible script, possibly with the BoringModel ?
Best,
T.C

@tchaton could you continue to work on this issue?

Hey @yinrong,
Could you make sure you have the same number of batches for all ranks.
It will hang if there is an uneven number of batches
Best,
T.C

To expand on @tchaton answer: When you randomly select your dataset, make sure each process chooses the same one. You  can set the seed to make sure of this:
from pytorch_lightning import seed_everything
seed_everything(1)


Add variation use a simplified template for sections with open ends (endless) (--download-sections)

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I intentionally remove or skip any mandatory* field

Checklist

[X] I'm requesting a feature unrelated to a specific site
[X] I've looked through the README
[X] I've verified that I have updated yt-dlp to nightly or master (update instructions)
[X] I've searched known issues and the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue

Provide a description that is worded well enough to be understood
Please, add for faster operation of sections with time (--download-sections) in the command line for a short, intuitive command
--download-sections "*1:00-inf"
--download-sections "*0:00-1:00"
add:
--download-sections "0:00+"
--download-sections "+0:00"
or: "*0:00--", "*0:00..."
Provide verbose output that clearly demonstrates the problem

[ ] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[ ] If using API, add 'verbose': True to YoutubeDL params instead
[ ] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
No response

That's good, thanks, sorry.
As far as I understand, this is not indicated in the main documentation.


Django. Several DoesNotExist exceptions not reached

When we try to catch mutiple DoesNotExist exceptions in different code blocks pylance says that those which are not the first will not be reached. But in fact, they will be reached and raise the corresponding exception.
Environment data

Language Server version: v2023.2.10
OS and version: macOS Monterrey v12.5.1
Python version (& distribution if applicable, e.g. Anaconda): 3.10.9

Code Snippet

from django.db import models

class User(models.Model):
    email = models.EmailField(max_length=250)

class Notification(models.Model):
    message = models.CharField(max_length=250)

class Media(models.Model):
    file = models.FileField()

def do_things(user_id: int, notification_id: int, media_id: Media) -> None:
    try:
        user = User.objects.get(id=user_id)
        note = Notification.objects.get(id=notification_id)
        media = Media.objects.get(id=media_id)
    except User.DoesNotExist:
        raise Exception(f"User with id {user_id} does not exist.")
    except Notification.DoesNotExist:
        raise Exception(f"Notification with id {notification_id} does not exist.") # <- pylance marks this as not reached
    except Media.DoesNotExist:
        raise Exception("Example exception") # <- also marked as unreachable

Expected behavior
Do not mark the following exceptions as unreachable code
Actual behavior
From the second DoesNotExist exception the code is marked as unreachable.

Please provide a self-contained, minimal code sample that demonstrates your issue. The code sample above references many symbols that are not stdlib symbols. You are presumably importing them from another file or defining them outside of the code snippet. Without the additional context, it's difficult to diagnose your problem.

Please provide a self-contained, minimal code sample that demonstrates your issue. The code sample above references many symbols that are not stdlib symbols. You are presumably importing them from another file or defining them outside of the code snippet. Without the additional context, it's difficult to diagnose your problem.

Sorry. I've just updated with additional context and de version of the Django package that we're using. Anything you need, just let me know and I will get back to you as soon as possible. Thank you.

Thanks for the additional information.
This looks like a bug in the django type stubs that are bundled with pylance. The django implementation dynamically registers a DoesNotExist exception class for each model class, but the stubs model all of these as the same class. Pyright (the static type analyzer that underlies pylance) therefore concludes that the three except clauses are targeting the same exception class.
We can fix this by updating the bundled type stubs. In particular, we should update the Model class and replace class DoesNotExist(ObjectDoesNotExist): ... with DoesNotExist: ClassVar[type[ObjectDoesNotExist]].

why pylance uses a fork off of typeddjango/django-stubs that is so many commits behind the parent?

@bschnurr would know better, but I believe this issue mentioned in the README is the main reason:

Note: this project was forked from https://github.com/typeddjango/django-stubs with the goal of removing the mypy plugin dependency so that mypy can't crash due to Django config, and that non-mypy type checkers like pyright will work better with Django.

Happy to discuss if this is no longer true.


chore: manually update graalvm docker image tag to 3.26.0

Release-please was unable to update the image tag because the configs weren't up-to-date with the new directory structure (https://github.com/googleapis/sdk-platform-java/pull/2524). Performing a one time update to ensure the docker image tag matches the shared-dependencies version.

Closing this PR (according to offline discussion). We will be re-releasing sdk-platform-java with the fixed release-please configs.


Switch to pathlib from os for handling paths.

Hi, I would like to take on this issue. Could you assign me to it?

sure @mojoee

is this issue fixed? @pybash1

no @VG08

@gh-adithya no, the issue is still up for grabs if ur interested... sorry for the late reply


Question about Anchors

This may be a silly question, but in order to get convergence, do you always need to use the same anchors for the entire training session, or can the anchors be selected at random from within the DataLayer forward pass?
Thanks!

@ZoroDerVonCodier Hi, It's random sampling,  an epoch training means every sample is picked as anchor for one time.

Perfect! Thanks.


Add quoted strings which allow substitutions

Today quoted strings do not allow substitutions to keep full compatibility with JSON. Triple double-quoted strings also don't allow substitutions, even if there is no JSON-compatibility which could be broken.
If you want substitutions in multi-line strings, you would have to do something like
config.longtext="""first line
more lines...
line with """${value1}""" and """${value2}""".
more text with    tab
""""

This is a little bit cumbersome. Therefore I propose these solutions:

a configuration option which changes the behavior of """
a new quote $"""..."""
a new quote $"...", which would also allow multi-line strings

In addition to substitution the default backslash-escapes should be interpreted.
Another feature to think about are improved indentation rules, where the indentation of the first line after the first line break is considered to be the zero indentation. The very first line would be ignored, if it was empty. For all lines after the first line break, the common prefix between the current and first line would be removed. This would work for spaces and tabs, but may not have the desired effect for mixed tabs and spaces. If you have those, the first line after the first line break should start at column one.
This would allow:
config {
    longtext=$"""
        first line
        more lines...
        line with ${value1} and ${value2}.
        more text with\ttab
        """"
}

to be the same as above, albeit more readable.
If that is too much magic, there is still the original """.

Just saw, that this is more or less a duplicate of #391. Havoc's suggestion was to use the backtick, as it is used in ES6. This syntax allows multiline and substitutions. I would not allow general expressions, as HOCON is no programming language.
An addition would be using three backticks similar to three double quotes, which will also use the indentation rules.


Developer Guide: Add underline for the use of list use case in delete use case.

Good job adding product scope, user stories, use cases, NFRs and glossary in your DG! Keep up the good work in morphing the DG to fit your courier project.


Meeting accessibility standards-3

Image and icon elements contain accessible alt attributes
Heading attributes fall in sequential order
Title elements contain a concise, descriptive title

Added alt attributes to icons in aside part of page and cleaned  tag coding


Example usage?

Are there any examples of how to use this library?
Examples for functions like getting the solstice?
I'm struggling to see any info on how to use this code.

Please take a look at the tests https://github.com/commenthol/astronomia/blob/master/test/solstice.test.js


use tox, fix mongoengine & python 2.6 tests

The MongoEngine tests were broken because MongoEngine now requires a recent version of Flask-WTF which requires WTForms 2 for its CSRF validation implementation. I fixed this by skipping WTForms 1 tests for the MongoEngine backend.
The Python 2.6 tests were broken because the keys method calls the normal (unordered) dict.keys(). I fixed this by adding ordereddict as a dependency for 2.6 and removing the "Bare-bones OrderedDict implementation for Python2.6 compatibility" in case there are other problems with it. If we want to keep it, we could probably also fix this by adding a keys method that returns self.ordered_keys.
I added a tox.ini to make these sorts of issues easier to test locally. And, I made the travis.yml use tox so we can do stuff like running flake8 in the future. I also made it test Python 3.6.

Once this is merged, I'm also planning to make another PR for adding flake8 tests to the tox.ini: https://github.com/pawl/flask-admin/compare/fix_mongoengine_tests...pawl:add_flake8?expand=1


Reduce test log noise on Travis

We might be hitting the log limit soon if we add more tests, see #1439.
The detailed logs are very helpful but really we are only interested in failure logs. Can we reduce log output for passing tests?

@levitte

If there's some way to convince Travis to make the compile collapsable when that passed but tests failed, that would also be handy. The compile is rather noisy. It seems Travis has some ability to fold things in the log viewer, but I'm not clear on how it works.
The compile could also stand to be quieter. Ninja does this nice buffering thing where it only shows a build line (or, in console mode, it keeps it all on one status line), but once a command fails or shows warinings, it prints the full command and build output for just edge. (Ninja is wonderful. Now that you all have the new buildsystem, I wonder how hard it'd be to make a Ninja output for it...)

We could make -s? That might be too quiet (you only see the compile error but not the failing compile line - sometimes we may want to see the build line options) but we can always revisit if we ever end up needing more information? Pretty much 100% of the time now I end up loading a huge log only to scroll to the end to see where it failed.

I’m in favor of 'make -s' for exactly the same reason.
And we could replace the Configure output with just a repeat of its command-line arguments, for example.

(I'm on vacation this week, but...)
Regarding ninja, it should be extremely easy. Make a config that mentions build.ninja (or whatever the default name is) as build file instead if Makefile, then create Configurations/unix build.ninja.tmpl. That's about it.
It would be cool to add an option to Configure to choose another build file than the default (Makefile for Unix, makefile for Windows, descrip.mms for VMS)
(going back to vacation)

I believe supporting anything beyond make is a waste of time.

To be clear, I pointed to ninja primarily as an example of how to do build output well, not saying you should use it. Buffering and replay full command on error is really the way to go.
Whether you all want to support ninja I'll leave to you. But I would highly recommend trying it once. (Give the BoringSSL build a go. We do make and ninja via cmake.) Ninja is wonderful.

Ninja support doesn't have to be part of our mainstream source. It can be a side project that simply adds two files and that's it.

Back to the actual issue, there's unfortunately no way to separate the build from the test, as they're both in the script step.  I can't really see a way to separate build and test in different steps, which means they won't be separately collapsible.
We might want to consider an enhancement of our runner.  Currently, it just runs all tests through Test::Harness's runtests().  Instead, we could use execute_tests, which returns a lot of interesting values including exactly what tests failed, and have the runner save those in a file (let's call it a test status file for further reference) while doing the usual printout of failed tests.
With that, our .travis.yml could do a first make test without verbosity, and then re-run make test with the additional arguments TESTS={test names picked up from the test status file) and V=1.  That would limit the verbosity to the specific tests that failed.

The other option is to have the test runner do all of the above automatically if verbosity is on, regardless of Travis and anything else.

So I suggest

get Configure to spit out the configure line (@levitte, will you do that when back?), then make -s in .travis.yml for quick relief
not a fan of re-running tests on failure to get the log - tests can be flaky so the original failure may not be easily reproducible. Can we write the test output to a log file (one per recipe), then dump it to the console if the test failed? This can be for post 1.1.0.

get Configure to spit out the configure line (@levitte, will you do that when back?)

If you can explain to me exactly what "the configure line" is supposed to be.  I assume, btw, that this would be in addition to what it currently spits out.

then make -s in .travis.yml for quick relief

Sure.  I'm frankly not keen on it since that will never show the command line for failing compiles, buuuuut that's seldom needed anyway.  So yeah, sure.

not a fan of re-running tests on failure to get the log - tests can be flaky so the original failure may not be easily reproducible. Can we write the test output to a log file (one per recipe), then dump it to the console if the test failed? This can be for post 1.1.0.

It's kind of meh to do so, it means that we must recreate all the mechanisms to make the summary at the end of running the tests.  I can't say that prospect makes me very entusiastic...

I'm frankly not keen on it since that will never show the command line for failing compiles, buuuuut that's seldom needed anyway. So yeah, sure.

So long as you see the Configure, I think that's practically never needed in the remote Travis logs. We can also have one BUILDONLY run emit the full build log, just in case.

So long as you see the Configure, I think that's practically never needed in the remote Travis logs. We can also have one BUILDONLY run emit the full build log, just in case.

#1457

Now that #1457 is merged, I think we've done quite a bit to reduce the noise.  I suggest closing this issue.

Suggestion :
Move these two defines from command-line
... -DOPENSSLDIR="\"/usr/local/ssl\"" -DENGINESDIR="\"/usr/local/lib/engines-1.1\"" ...
into opensslconf.h file who is already a generated file ...
These path could even be larger on windows plateforms...
@levitte : any opinion ?

Apparently, I missed that last question.
The problem is the the paths for OPENSSLDIR and ENGINESDIR is generated from build file (Makefile) values, and since that differs between the platforms, it's a bit hard to do.  opensslconf.h is generated from opensslconf.h.in and values in configdata.pm, which in turn is generated by Configure.  In other words, it's not the easiest thing to accomodate...

Ping @levitte. Can we close this?

Yup


[Політика конфіденційності] Does not redirect the user to the main page of the site

Environment: OS, Windows 11 Browser: Google Chrome Version 114.0.5735.135. , Iphone 11 Pro
Reproducible: always
Build found: https://github.com/ita-social-projects/StreetCode/commit/0230695f2bfd4febeabec81b7b7154908215c400
Preconditions

Go to the site as user.

Steps to reproduce

Go to 'Політика конфіденційності' page
Click on every link  www.streetcode.com.ua that present on the page

Actual result

Does not redirect the user to the main page of the site

Expected result

Redirects the user to the main page of the site

1 Mobile and tablet version:
https://github.com/ita-social-projects/StreetCode/assets/109734235/c8864cb6-be7b-4a47-b917-f7f2b53e050f
2 Desktop version:
https://github.com/ita-social-projects/StreetCode/assets/109734235/29550d2c-6759-40c3-85ce-234d89eb734e
User story and test case links
E.g.: "User story #139
Labels to be added
"Bug", Priority ("pri: medium"), Severity ("severity: low"), Type ( "Functional")

The bug from the 1st attached video still reproduces - iPhone 11 Pro, 13 Pro Max, 15, 15 ProMax.

The bug from the 1st attached video still reproduces - iPhone 11 Pro, 13 Pro Max, 15, 15 ProMax.

I can't reproduce this error. When you click a link, you simply go to the ref https://www.streetcode.com.ua/. Maybe the reason could be at displaying of site-page itself


Year greater than 3177

I found that the moment jalaali moment works for years less than 3177. Is it a must ?!
I am using moment isValid, isSame , and other functions which get user input directly, and it is possible that user enters some invalid date. Although I can check user date manually, but I want to know if the plugin can accept larger years, may be up to 9999 !

The conversion algorithm works in a 3 thousand years span. So dates should be in this range to be valid. If you don't need exact validity check, you can ignore isValid and check format manually. This way you won't be able to check leap years which may not be important in that large time span.

As a matter of curiosity  ....  It seemed to me that if the algorithm works for three thousand years it should work for the rest, which seems not true ! Can you describe why this will not work after 3177 ? Or can you direct me to link which I can read more about it.
I have see http://www.time.ir/ and https://github.com/farhadi/JalaliJSCalendar they both have year limitation.

A link to the algorithm is on the homepage of this repository. There you can find the reason for 3000 years limitation.
On Wed, Jun 24, 2015 at 4:22 PM, afattahi54<EMAIL_ADDRESS>wrote:

As a matter of curiosity  ....  It seemed to me that if the algorithm works for three thousand years it should work for the rest, which seems not true ! Can you describe why this will not work after 3177 ? Or can you direct me to link which I can read more about it.
I have see http://www.time.ir/ and https://github.com/farhadi/JalaliJSCalendar they both have year limitation.
Reply to this email directly or view it on GitHub:
https://github.com/jalaali/moment-jalaali/issues/33#issuecomment-114842815


build failed with msg: Authentication credentials are missing or invalid.

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Issue Description

(Note: ASC = App Store Connect)
I created a new project, and then tried to build it with fastlane and upload it to TestFlight, but there is an error occur on upload:
[16:58:08]: Authentication credentials are missing or invalid. - Provide a properly configured and signed bearer token, and make sure that it has not expired. Learn more about Generating Tokens for API Requests https://developer.apple.com/go/?id=api-generating-tokens

I checked the issues related to this error and it didn't seem to help my case (I made sure the ASC API Keys was correct), so I created this issue.
And, I have another app, which is also under this asc team, and it builds and uploads normally. I have tried to use the same ASC api key in the new project, or to create a new api key in ASC, both of these errors occurred

[16:58:01]: Cruising back to lane 'ios tf' 🚘
[16:58:01]: --------------------------------------------
[16:58:01]: --- Step: Switch to ios asc_api_key lane ---
[16:58:01]: --------------------------------------------
[16:58:01]: Cruising over to lane 'ios asc_api_key' 🚖
[16:58:01]: ---------------------------------------
[16:58:01]: --- Step: app_store_connect_api_key ---
[16:58:01]: ---------------------------------------
[16:58:01]: Cruising back to lane 'ios tf' 🚘
[16:58:01]: ----------------------------------
[16:58:01]: --- Step: upload_to_testflight ---
[16:58:01]: ----------------------------------
[16:58:01]: Creating authorization token for App Store Connect API
+---------------------------------+---------------------------------+
|                           Lane Context                            |
+---------------------------------+---------------------------------+
| DEFAULT_PLATFORM                | ios                             |
| PLATFORM_NAME                   | ios                             |
| LANE_NAME                       | ios tf                          |
| VERSION_NUMBER                  | 1.00.01                         |
| SIGH_PROFILE_TYPE               | app-store                       |
| MATCH_PROVISIONING_PROFILE_MAP  | {"xx.yy.zz"=>"match   |
| PING                            | AppStore xx.yy.zz",   |
|                                 | "xx.yy.zz.PushServic  |
|                                 | e"=>"match AppStore             |
|                                 | xx.yy.zz.PushService  |
|                                 | ",                              |
|                                 | "xx.yy.zz.PushConten  |
|                                 | t"=>"match AppStore             |
|                                 | xx.yy.zz.PushContent  |
|                                 | "}                              |
| GIT_REPO_WAS_CLEAN_ON_START     | true                            |
| BUILD_NUMBER                    | 5                               |
| IPA_OUTPUT_PATH                 | /xx/yy.ipa  |
| XCODEBUILD_ARCHIVE              | /Users/zz/Library/Developer/X  |
|                                 | code/Archives/2023-03-24/yy  |
|                                 | 2023-03-24 16.54.52.xcarchive   |
| DSYM_OUTPUT_PATH                | /xx/yy.app.dSYM.zip  |
+---------------------------------+---------------------------------+
[16:58:08]: Authentication credentials are missing or invalid. - Provide a properly configured and signed bearer token, and make sure that it has not expired. Learn more about Generating Tokens for API Requests https://developer.apple.com/go/?id=api-generating-tokens
+------+---------------------+-------------+
|             fastlane summary             |
+------+---------------------+-------------+
| Step | Action              | Time (in s) |
+------+---------------------+-------------+
| 1    | default_platform    | 0           |
| 2    | get_version_number  | 0           |
| 3    | Switch to ios       | 0           |
|      | c_build_app lane    |             |
| 4    | Switch to ios       | 0           |
|      | match_cer lane      |             |
| 5    | match               | 1           |
| 6    | ensure_git_status_  | 0           |
|      | clean               |             |
| 14   | cocoapods           | 3           |
| 15   | build_app           | 227         |
| 16   | Switch to ios       | 0           |
|      | asc_api_key lane    |             |
| 17   | app_store_connect_  | 0           |
|      | api_key             |             |
| 💥   | upload_to_testflig  | 6           |
|      | ht                  |             |
+------+---------------------+-------------+
[16:58:08]: fastlane finished with errors
Looking for related GitHub issues on fastlane/fastlane...
[!] The request could not be completed because:
Authentication credentials are missing or invalid. - Provide a properly configured and signed bearer token, and make sure that it has not expired. Learn more about Generating Tokens for API Requests https://developer.apple.com/go/?id=api-generating-tokens

Command executed

# tf is a custom lane, check the key code below
bundle exec fastlane tf

Complete output when running fastlane, including the stack trace and command used

There is the key code in running fastlane file:
# asc api key
@key_id = ENV['ASC_KEY_ID']
@issuer_id = ENV['ASC_ISSUER_ID']
@key_filepath = ENV['ASC_KEY_FILEPATH']

app_store_connect_api_key(
    key_id: @key_id,
    issuer_id: @issuer_id,
    key_filepath: @key_filepath,
    duration: 1200, # optional (maximum 1200)
    in_house: true # optional but may be required if using match/sigh
)

# upload to tf
upload_to_testflight(
    skip_waiting_for_build_processing: true
)

Environment

 ✅ fastlane environment ✅
Stack

Key
Value

OS
13.2

Ruby
3.0.0

Bundler?
true

Git
git version 2.37.1 (Apple Git-137.1)

Installation Source
~/.rvm/gems/ruby-3.0.0/bin/fastlane

Host
macOS 13.2 (22D49)

Ruby Lib Dir
~/.rvm/rubies/ruby-3.0.0/lib

OpenSSL Version
OpenSSL 1.1.1m  14 Dec 2021

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

Xcode Path
/Applications/Xcode.app/Contents/Developer/

Xcode Version
14.2

Swift Version
5.7.2

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL
en_US.UTF-8
✅

LANGUAGE

fastlane files:
(Unable to provide)
There is the key code in running fastlane file:
# asc api key
@key_id = ENV['ASC_KEY_ID']
@issuer_id = ENV['ASC_ISSUER_ID']
@key_filepath = ENV['ASC_KEY_FILEPATH']

app_store_connect_api_key(
    key_id: @key_id,
    issuer_id: @issuer_id,
    key_filepath: @key_filepath,
    duration: 1200, # optional (maximum 1200)
    in_house: true # optional but may be required if using match/sigh
)

# upload to tf
upload_to_testflight(
    skip_waiting_for_build_processing: true
)

fastlane gems

Gem
Version
Update-Status

fastlane
2.212.1
✅ Up-To-Date

Loaded fastlane plugins:

Plugin
Version
Update-Status

fastlane-plugin-appcenter
2.0.0
✅ Up-To-Date

fastlane-plugin-firim
0.2.2
✅ Up-To-Date

fastlane-plugin-pgyer
0.2.4
✅ Up-To-Date

Loaded gems

Gem
Version

did_you_mean
1.6.3

bundler
2.4.7

pathname
0.2.1

rake
13.0.6

rexml
3.2.5

CFPropertyList
3.0.6

concurrent-ruby
1.2.2

i18n
1.12.0

minitest
5.18.0

tzinfo
2.0.6

zeitwerk
2.6.7

activesupport
<IP_ADDRESS>

public_suffix
4.0.7

addressable
2.8.1

httpclient
2.8.3

json
2.6.3

algoliasearch
1.27.5

artifactory
3.0.15

atomos
0.1.3

aws-eventstream
1.2.0

aws-partitions
1.733.0

aws-sigv4
1.5.2

jmespath
1.6.2

aws-sdk-core
3.171.0

aws-sdk-kms
1.63.0

aws-sdk-s3
1.119.2

babosa
1.0.4

claide
1.1.0

fuzzy_match
2.0.4

nap
1.1.0

netrc
0.11.0

ffi
1.15.5

ethon
0.16.0

typhoeus
1.4.0

cocoapods-core
1.11.3

cocoapods-deintegrate
1.0.5

cocoapods-downloader
1.6.3

cocoapods-plugins
1.0.0

cocoapods-search
1.0.1

cocoapods-trunk
1.6.0

cocoapods-try
1.2.0

colored2
3.1.2

escape
0.0.4

fourflusher
2.3.1

gh_inspector
1.1.3

molinillo
0.8.0

ruby-macho
2.5.1

nanaimo
0.3.0

xcodeproj
1.22.0

cocoapods
1.11.3

cocoapods-pod-linkage
0.0.1

colored
1.2

highline
2.0.3

commander
4.6.0

declarative
0.0.20

digest-crc
0.6.4

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20190701

dotenv
2.8.1

emoji_regex
3.2.3

excon
0.99.0

faraday-em_http
1.0.0

faraday-em_synchrony
1.0.0

faraday-excon
1.1.0

faraday-httpclient
1.0.1

multipart-post
2.0.0

faraday-multipart
1.0.4

faraday-net_http
1.0.1

faraday-net_http_persistent
1.2.0

faraday-patron
1.0.0

faraday-rack
1.0.0

faraday-retry
1.0.3

ruby2_keywords
0.0.5

faraday
1.10.3

http-cookie
1.0.5

faraday-cookie_jar
0.0.7

faraday_middleware
1.2.0

fastimage
2.2.6

jwt
2.7.0

memoist
0.16.2

multi_json
1.15.0

os
1.1.4

signet
0.17.0

googleauth
1.5.0

mini_mime
1.1.2

trailblazer-option
0.1.2

uber
0.1.0

representable
3.2.0

retriable
3.1.2

webrick
1.8.1

google-apis-core
0.11.0

google-apis-androidpublisher_v3
0.37.0

google-apis-playcustomapp_v1
0.13.0

google-apis-iamcredentials_v1
0.17.0

google-apis-storage_v1
0.19.0

google-cloud-env
1.6.0

google-cloud-errors
1.3.1

google-cloud-core
1.6.0

google-cloud-storage
1.44.0

mini_magick
4.12.0

naturally
2.2.1

optparse
0.1.1

plist
3.7.0

rubyzip
2.3.2

security
0.1.3

simctl
1.6.10

terminal-notifier
2.0.0

unicode-display_width
1.8.0

terminal-table
1.8.0

tty-screen
0.8.1

tty-cursor
0.7.1

tty-spinner
0.9.3

word_wrap
1.0.0

rouge
2.0.7

xcpretty
0.3.0

xcpretty-travis-formatter
1.0.1

fastlane-plugin-appcenter
2.0.0

firim
0.2.9

fastlane-plugin-firim
0.2.2

fastlane-plugin-pgyer
0.2.4

stringio
3.0.5

psych
5.1.0

xcode-install
2.8.1

generated on: 2023-03-24

We were able to work around the issue by removing duration: 1200 as a parameter to app_store_connect_api_key

We were able to work around the issue by removing duration: 1200 as a parameter to app_store_connect_api_key

Thanks for your reply. I tried it and removed the duration parameter, but the same problem still exists.
In addition, errors occurred in upload_to_testflight (upload to tf), not app_store_connect_api_key (request asc api key)

@iTofu have you set params apple_id and skip_waiting_for_build_processing as pilot parameters. Reference from pilot fastlane documents
pilot/upload_to_testflight can use an [Application Specific Password via the FASTLANE_APPLE_APPLICATION_SPECIFIC_PASSWORD environment variable](https://docs.fastlane.tools/best-practices/continuous-integration/#application-specific-passwords) to upload a binary if both the skip_waiting_for_build_processing and apple_id options are set. (If any of those are not set, it will use the normal Apple login process that might require 2FA authentication.)

notice that apple_id is the Apple ID property in the App Information section in App Store Connect, it is not same as your apple_id in AppFile config.
you can reach more here https://docs.fastlane.tools/actions/pilot/

@iTofu have you set params apple_id as pilot parameters. Reference from pilot fastlane documents
pilot/upload_to_testflight can use an [Application Specific Password via the FASTLANE_APPLE_APPLICATION_SPECIFIC_PASSWORD environment variable](https://docs.fastlane.tools/best-practices/continuous-integration/#application-specific-passwords) to upload a binary if both the skip_waiting_for_build_processing and apple_id options are set. (If any of those are not set, it will use the normal Apple login process that might require 2FA authentication.)

notice that apple_id is the Apple ID property in the App Information section in App Store Connect, it is not same as your apple_id in AppFile config.
I'm not sure how it affected, but it works for me.
you can reach more here https://docs.fastlane.tools/actions/pilot/

Thanks for your reply.
I tried adding apple_id manually, but it still didn't work.
In addition, I communicate with ASC through App Store Connect API Key, so there is no need for apple_id

I've just seen the same error while I was renewing the certificates. In my case, the error message was not related to the fundamental issue.
If you've updated AppStore Connect API key, verify the Issuer ID, the Key ID, and the key file path in your local machine match with the Fastfile code.
AppStore Connect -> Users & Access -> Keys

Fastfile

Thank you for your reply.
I have reconfirmed that the relevant parameters are correct. And puts the result of app_store_connect_api_key(), which outputs an obviously valid string, like this:
[15:15:45]: app_store_connect_api_key: {:key_id=>"XXX", :issuer_id=>"\"XX-XX-XX", :key=>"-----BEGIN PRIVATE KEY-----\nXXX\n-----END PRIVATE KEY-----", :is_key_content_base64=>false, :duration=>500, :in_house=>true}

I'm running into this issue currently. It happened before but "fixed itself" so it does seem to be sporatic and related to app store connect (and not with the actual tokens).
To get more info:
Run fastlane with --verbose. Also, look in /tmp/spaceship* for logs that show the responses from app store connect. You'll probably see something like:
GET apps: 401 {"errors"=>[{"status"=>"401", "code"=>"NOT_AUTHORIZED", "title"=>"Authentication credentials are missing or invalid.", "detail"=>"Provide a properly configured and signed bearer token, and make sure that it has not expired. Learn more about Generating Tokens for API Requests https://developer.apple.com/go/?id=api-generating-tokens"}]}

Unfortunately the actual requests are not logged, and to do that you need to set SPACESHIP_DEBUG=1 and then use the charles web proxy to see the requests. All this to determine that app store connect sometimes craps out.

Sorry, I finally confirmed my problem because I entered an extra " for a certain value, which is a typo. Like this:
# …
key = "value""
# …

### Azure DevOps API Key Issues for deploying to Apple
To get this to successfully work on Azure DevOps Pipeline with an API Key. I ran into so many problems and tried everything I could find and this finally worked.  Azure DevOps says you need use the base64 key.  Well if you open up the .p8 and copy the base64 encoded string in there, that isn't what they want.  They literally want you to copy all of the contenxt in the .p8 file to a base64 string. Don't modify the .p8 file.  I found the solution at the follow source, and once you get the data.b64 file open it and copy the base64 string in that file.  In the following article is discusses how to do this for Windows, Mac, and Ubuntu.
https://github.com/fastlane/fastlane/issues/21531#issuecomment-1873633417


WCC Team: Hero

The page contains:
Title - Reuse the existing component for the background colour.
Tab - Check if the reusable component for the tab already exists. If not, create it.
Subtitle and Body - Ensure that both are displayed properly.
Contact Us rectangle:
Display an Email icon - the link redirect to the Women Coding Community email.
Display a Slack icon - the link redirect to the Women Coding Community slack channel.
Background - Set the content inside of a rectangle with a light blue background colour. This will be aligned with the title.
Laptop view:

Mobile view:

I’ve assigned you to this one, but you’re welcome to assign yourself to anything else you’d like to work on, no need to ask. 😊

Oh i dont have access to assign thats why :)

Oh, okay! I’ll look into why that’s happening and fix it so you’ll be able to do it yourself in the future!

You'll need to split this down to smaller tickets -> the Hero/Title component can be reused as you have created it for the mentorship page already

Ok I will talk with @Amenawon to see which part she started. Thanks @stepsen89

I would rename this - as it's not part of the Hero per see (and reusable) so just calling it Section or TextBlock or something is easier recognisable

Need to add a section wrapper on the sections to be used on the reusable tabs


1.0 MVP Release

Issues

[ ] #52 Import email templates from sendgrid
[ ] #111 Implement blockchain follower coordination in database
[ ] #105 Incorrect result counting in get_priorty_count
[ ] #100 Fix query in notification sender for run_notifications
[ ] #97 Basic functionality: ensure each type of notification triggers transports
[ ] #112 Add SMS message templates
[ ] #110 Fix rate limits
[ ] #108 Request the user's phone number from steemit api to send sms using signed request
[ ] #109 Request the user's email address from steemit api using signed request

#100 should be good


Question - Events vs Continuous query

Hi
We are currently working on a use case where we will need data modifications events for cache to be triggered and sent to the listener or handler and inside the registered listener we will be performing operations to update or insert data into another Cache.
For the above use case we came across below two options.

Ignite Events
Continuous query

i)  Out of these two contenders would you suggest any approach?
ii) which one guarantees event updates to be delivered even in case of any primary node failures?
iii) which is more resilient in case of clustering?
iv) Are there any drawbacks of using one over the other especially with performance?
Any suggestions are greatly appreciated.

The answer is Continuous Query, it has built-in resiliency, batching, exactly-once delivery guarantee.
Events are better suited for things like observability and diagnostics.

The answer is Continuous Query, it has built-in resiliency, batching, exactly-once delivery guarantee.
Events are better suited for things like observability and diagnostics.

Thank you for your response @ptupitsyn.


⚠ PrivateHD has degraded performance

In a502b6f, PrivateHD ($PHD) experienced degraded performance:

HTTP code: 200
Response time: 1738 ms

Resolved: PrivateHD performance has improved in bbb5303.


Enum and min_length Validation

Initial Checks

[x] I have searched GitHub for a duplicate issue and I'm sure this is something new
[X] I have searched Google & StackOverflow for a solution and couldn't find anything
[X] I have read and followed the docs and still think this is a bug
[X] I am confident that the issue is with pydantic (not my code, or another library in the ecosystem like FastAPI or mypy)

Description
I use pydantic 2.7.3, and import v1 version.
type is defined as a str_enum and min_length is used at the same time, unexpected results occur.
pydantic v2 produces different results than v1, I'm not sure if this is a feature of v1 or a bug.
I'm not sure if it's weird to use enum with min_length.
Example Code
from enum import Enum

class LangEnum(str, Enum):
    en = "en"
    zh = "zh"

from pydantic.v1 import BaseModel, Field

class LangModelV1(BaseModel):
    lang: LangEnum = Field(..., min_length=2)

LangModelV1(lang="aa")
# This will succeed, which is an unexpected result because it is not within the Enum range.

from pydantic import BaseModel, Field

class LangModelV2(BaseModel):
    lang: LangEnum = Field(..., min_length=2)

LangModelV2(lang="aa")
# This will fail(ValidationError) which is my expected result.

Python, Pydantic & OS Version
pydantic version: 2.7.3
pydantic-core version: 2.18.4
python version: 3.10.12 (main, Nov 20 2023, 15:14:05) [GCC 11.4.0]
platform: Linux-6.5.0-35-generic-x86_64-with-glibc2.35

Affected Components

[ ] Compatibility between releases
[X] Data validation/parsing
[ ] Data serialization - .model_dump() and .model_dump_json()
[ ] JSON Schema
[ ] Dataclasses
[ ] Model Config
[ ] Field Types - adding or changing a particular data type
[ ] Function validation decorator
[ ] Generic Models
[ ] Other Model behaviour - model_construct(), pickling, private attributes, ORM mode
[ ] Plugins and integration with other tools - mypy, FastAPI, python-devtools, Hypothesis, VS Code, PyCharm, etc.

@gbaian10,
Looks like a V1 bug, but we're no longer actively developing V1, so going to close this as not planned!

OK, thank you for your reply, I will avoid this way of writing when using v1.


As an author, posts I make can be in markdown (commonMark is good)

 Issue by kdhaywar
Tuesday Jan 19, 2016 at 17:16 GMT
Originally opened as https://github.com/shawnwanderson/cmput404-project/issues/11

Dun'


[BUG] Failed to allocate buffers

Describe the bug
 Failed to allocate buffers
Bug report
[23:50:08.514187869] [4304] �[1;31mERROR �[1;37mV4L2 �[1;34mv4l2_videodevice.cpp:1241 �[0;32m/dev/video0[12:cap]: �[0mUnable to request 1 buffers: Cannot allocate memory ERROR: *** failed to allocate capture buffers **
Additional context
Error generated within Allsky software. This error is rpi cam related which we cant solve. It has been adressed by alot more ppl in the past. Please pick it up again.
#555
** Hardware
RPI 4B 8GB with HQ Camera. Cables good attached, no throtteling when it happens, no memory leakage, no overheating.

Please can you give more details on this.  There could be several reasons for your error.  What rpicam-apps command line are you running?  Have you modified anything in config.txt or any other configuration file?  Can you reproduce this error outside of the allsky software?

It uses libcamerastill in CL. I dont have modified anything in config.txt. Looks to me standard file.
No i cannot reproduce this error outside allysky.

Any update on this?  If not I'll close shortly.

Hi, hope it's ok to reply to this. I have ran into the same problem , with the same software, and I did run the command you asked. Below the error and the output of you requested command:
Mode selection for 2028:1520:12:P     SRGGB10_CSI2P,1332x990/0 - Score: 3456.22     SRGGB12_CSI2P,2028x1080/0 - Score: 1083.84     SRGGB12_CSI2P,2028x1520/0 - Score: 0     SRGGB12_CSI2P,4056x3040/0 - Score: 887 Mode selection for 4056:3040:12:P     SRGGB10_CSI2P,1332x990/0 - Score: 10552.2     SRGGB12_CSI2P,2028x1080/0 - Score: 8179.84     SRGGB12_CSI2P,2028x1520/0 - Score: 7096     SRGGB12_CSI2P,4056x3040/0 - Score: 0 dmaHeap allocation failure for rpicam-apps0 ERROR: *** failed to allocate capture buffers for stream *** pe2bz@allsky:~ $ grep -i cma /proc/meminfo CmaTotal:         524288 kB CmaFree:          289372 kB


Dependency errors while installation inside a Laravel 10 project

I think you’re not installing it correctly, did you try without the W flag? All the resolutions are stuff conflicting with your lock.

Yeah I have tried with -W

@frankdejonge Is it safe to install the package by deleting the composer.lock file?


Populate consumerID in PlatformEntity

-updated dependencies for terracotta-apis 1.0.6.beta and terracotta-configuration 10.0.6.beta
-this is mostly just plumbing the consumerID down through ManagementTopologyEventCollector

Self-merging to get the release out, as this change was discussed, earlier.


data.category vs data.categories in ActivityTriggered and TestSuiteStarted

Sketching a proposal of TestSuiteStarted, I realized that an array data.categories would be more helpful than a string data.category. Given that, the same should apply to ActivityTriggered.
Thoughts?

From a genericity perspective an array would be better.

Putting it differently, is there a perspective from which it would be worse?

Not that I can see.


Queue tracing bugfixes

Fixes the following:

Moves the queue tests to a more logical place, and adds tests for the queue job tracing feature flag
Fixes bug where feature tests are incorrectly memoized in the feature class (this goes for all feature classes, not just the queue although it was only noticeable there since it had multiple options of the same category)
Fixes trace context being lost for queue.process transactions because the context was overwritten by the default context because there was no active span in the scope which is required for the correct context being added to the transaction event

Especially the last point is important, this fixes data to get lost for queue job transactions, the before:

and after the change:

this also fixes the missing operation name in the performance dashboard (top one old, bottom one new) and missing data on the transaction itself (the queue job name and attempts and such):

getsentry/sentry-php#1668 fixes part of this PR, back to draft to validate and update.


configure: error: Cannot find libpq.so. Please specify correct PostgreSQL installation path

I want to install from source and when I run the following command:
./configure --with-php-config=/usr/bin/php-config --enable-sockets=yes --enable-openssl=yes --enable-http2=yes --enable-mysqlnd=yes --enable-swoole-json=yes --enable-swoole-curl=yes --with-postgres
I get the following error
configure: error: Cannot find libpq.so. Please specify correct PostgreSQL installation path
my OS:

This is while libpq.so exists

@amirhossein-fzl Can you try to pass the path of libpq when installing?

Can you try to pass the path of libpq when installing

@doubaokun Its path is in /lib64 ...

!?
@doubaokun

please !!


Individual Booster Set isn't used in Sealed

Expand the use of this setting to sealed.

Mostly a UI problem.
The Sealed modal needs to be expanded to allow the selection of specific sets for each booster (basically a collapsible copy of the regular "Individual Booster Set" setting, but for the adjusted booster count).
The server should only need a minor adjustment to handle this new way of setting Individual Booster Set temporarily.

Mostly a UI problem.
The Sealed modal needs to be expanded to allow the selection of specific sets for each booster (basically a collapsible copy of the regular "Individual Booster Set" setting, but for the adjusted booster count).
The server should only need a minor adjustment to handle this new way of setting Individual Booster Set temporarily.

08f4dd522a66dc84917dc342e3430878ac56aedd

08f4dd522a66dc84917dc342e3430878ac56aedd


add 3 more tools

@TorHou you need to update ephemeris for the new global options.

@bgruening I see, I like global options, those dependency parameters were "a bit" redundant. There is no way to test these changes easily right?


Quotes

Alright I switched from a very old version I hosted on my PC to Debian server hosting.
Setting everything up while keeping the old data was pretty easy except for one thing which are user quotes. The only reason why I switched from the old version to the newest one, was because I wasn't able to manually add quotes in the DB using sqlite. I tried the same thing again on the current version and as it turns out it still doesn't work. The bot shows the single entry by ID (.quoteid 1) but can't select it by keyword "test". So afterwards I just wiped that one entry the table had (with DELETE FROM Quotes) and restarted the Bot.
And now the bot doesn't recognize ".." and "..." anymore. It simply shows nothing on console, .listquotes and all the other functions are still working.
Is there a quick workaround to this problem? I somehow doubt that one INSERT/DELETE Statement can break this whole quote function. The bot is starting up with 0 issues/warnings after all and the db file is fine too.

if you kept the nadekobot.db file you can paste your old nadekobot.db into the new nadeko and everything will work again.

well you obviously messed something up and there is no way for us to know what.


Noticeable Issues and Solutions for Ubuntu Runners

Pull Request Description

It has been tested with the following parameters:

Runner Virtual Environments:

Linux

[ ] Ubuntu 22.04
[ ] Ubuntu 20.04

macOS

[ ] macOS 13
[ ] macOS 12

Windows

[ ] Windows 2022
[ ] Windows 2019

VPN Modes:

[x] OpenVPN (ovpn)
[ ] WireGuard (wg)

Client Versions:

[x] Installed from the package manager
Version specific

[ ] 1.3.3883.60

Start Connection: If the connection is started on the setup step.

[x] True
[ ] False

Runner Types:

[x] Tested on GitHub-hosted runner

Tested on Self-Hosted runner
If it runs on a self-hosted runner:

[ ] Manage Self-hosted
[ ] Action Runner Controller (ARC) (a Kubernetes Operator)

Solutions for Issues #209 and #206
README Updated: Added a Section for Noticeable Issues and Solutions


[MWPW-134330] Icon List CSS layout issue fix

Resolves: MWPW-134330
Fixed text align centering from h5+p
Fixed over-reaching padding application on all first divs inside the same section
Test URLs:

Before:

https://main--express--adobecom.hlx.page/express/create/video?lighthouse=on

https://main--express--adobecom.hlx.page/drafts/qiyundai/marketing/?lighthouse=on

After:

https://mwpw-134330--express--adobecom.hlx.page/express/create/video?lighthouse=on

https://mwpw-134330--express--adobecom.hlx.page/drafts/qiyundai/marketing/?lighthouse=on

Codecov Report

Merging #122 (dd4e836) into stage (ec58203) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##            stage     #122   +/-   ##
=======================================
  Coverage   34.33%   34.33%
=======================================
  Files          24       24
  Lines        9295     9295
=======================================
  Hits         3191     3191
  Misses       6104     6104

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


[BUG] The helm test on CI is fragile

Describe the bug
We have noticed a lot random failure in recent CI runs.
Additional context
Add any other context about the problem here.

Maybe a timeout or something like that?


DO NOT MERGE - work where Fabian can see it

Here are a preliminary set of manifests I've been using to experiment with Prometheus and Grafana

If there is no intention of merging this and this is just scratch space, would you mind keeping this in your fork? If there is intention of getting this merged eventually - it's fine to leave here.

Gotcha - getting rid of it. Thanks!


Made make_disk_resources.py report total size instead of free space.

High-level description
We have seen that when a user removes mesos-resources and restarts the
agent with a new ID, the new agent reports less disk space because the
disk size calculation is based on free space before previous sandboxes
has been GC'ed. This patch makes the disk size calculation based on
total size with some headroom instead.
Corresponding DC/OS tickets (obligatory)
These DC/OS JIRA ticket(s) must be updated (ideally closed) in the moment this PR lands:

DCOS_OSS-2418 make_disk_space.py should not exclude disk spaces used by old agents.

Checklist for all PRs

[ ] Added a comprehensible changelog entry to CHANGES.md or explain why this is not a user-facing change:
[ ] Included a test which will fail if code is reverted but test is not. If there is no test please explain here:
[ ] Read the DC/OS contributing guidelines
[ ] Followed relevant code rules Rules for Packages and Systemd

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[ ] Change log from the last version integrated (this should be a link to commits for easy verification and review): example
[ ] Test Results: [link to CI job test results for component]
[ ] Code Coverage (if available): [link to code coverage report]

PLEASE FILL IN THE TEMPLATE ABOVE / DO NOT REMOVE ANY SECTIONS ABOVE THIS LINE
Instructions and review process
What is the review process and when will my changes land?
All PRs require 2 approvals using GitHub's pull request reviews.
Reviewers should be:

Developers who understand the code being modified.
Developers responsible for code that interacts with or depends on the code being modified.

It is best to proactively ask for 2 reviews by @mentioning the candidate reviewers in the PR comments area. The responsibility is on the developer submitting the PR to follow-up with reviewers and make sure a PR is reviewed in a timely manner. Once a PR has 2 ship-it's, no red reviews, and all tests are green it will be included in the next train.

Hey, can you please address the following linter complaints?
E124 closing bracket does not match visual indentation
 E128 continuation line under-indented for visual indent 	2 failures in one build
 E201 whitespace after '('
 E303 too many blank lines (2)
 F401 'shutil' imported but unused


Update menus/jsonpp.cson to fix deprecation call.

Fixes: https://github.com/swenson/atom-jsonpp/issues/6

LGTM

Thanks!