Incorrect SPR number on PowerPC

On PowerPC, for compatibility with old POWER the encoding of the SPR number in mtspr, mfspr is reversed, see Green Cloth p.385:

…the SPR number coded in assembler language does not appear directly as a 10-bit binary number in the instruction.

This explanation, combined with the pseudocode:
n = spr[5:9] || spr[0:4]

and the diagram of the XFX-form on p.384, is extremely confusing.
Be it as it may, both rs/rt and spr operand modifiers in the PDL are simply %imm and this obviously results in emitting the wrong code.  The bug is especially vicious in the presence of extended mnemonics, because the special lr, ctr, xer have the reversed encoding baked in the set_asm, e.g. LR=8:
mtspr.set_asm("mtlr %imm", rs, sprf=0x100);

because 00000 01000 ⇔ 01000 00000.

@janvrany what happens to them on RISC-V when we encode split-fields, is it the "assembly source" or the "value" that gets into these set_asm operand constraints?

It in most complicated cases it is both. For example, consider J-type instruction where 20bit displacement is encoded in 4 different fields and the encoded binary value is shifted one bit right (i.e, you do not encode last bit because it is always zero). The set_asm statement looks like:
xxx.set_asm("xxx %gpr, %exp(bimm16)", rd, imm1+imm2+imm3+imm4)"

Here bimm16 modifier does the shifting and imm1+imm2+imm3+imm4 does the splitting
IIUC the issue in POWER can be solved by either:

introducing special modifier for this POWER weirdness, specifying the register as 10bit field and then in set_asm do something like set_asm("xxx %imm(ppcsprnum)", LR
or changing the format to have instead of %spr:10 something like %spr_lo:5 %spr_hi:5 and then in in set_asm do something like `set_asm("xxx %imm", spr_hi+spr_lo")

That being said, there's so many issues with POWER PDL that I'm disinclined to put much effort into "fixing" it. We should (re)start thinking of sourcing POWER model from authoritative sources, like we do for RISC-V.

issue in POWER can be solved by

Well, in practical terms (i.e. using these SPR numbers) it's not a real issue, because the ISA definition guarantees that mfspr and mtspr have extended mnemonics for every defined SPR.  Now, SPR numbers are processor- / profile-specific, so realistically we are bound by #34.
What does feel scary to me, is that n = spr[5:9] || spr[0:4] line in the Green Cloth.  It suggests to me that we no longer have a clear concept of "instruction".  Say, what is mflr?  Is it mfspr 8, which is the undoubtedly the canonical assembly for it (and consistent with p.387); or is it mfspr 0x100, which is "mfspr with spr field at 0x100" (consistent with the pseudocode)?  It looks like the definitions of assembly is still left completely informal.

We should (re)start thinking of sourcing POWER model from authoritative sources, like we do for RISC-V.

That's the thing.  It appears there is no "authoritative source" for a lot of things.  Even if we were to parse the BookMaster source of the instruction encoding tables and be extremely successful at it — so we would have "the authoritative instruction encoding" — we are still left with prose explanations of assembly, such as that "Compiler and Assembler Note" in the right margin of p.385.
The Sail definition of RISC-V seems no better, it's a function from a binary program to a behavior, really with no clear definiton of "instruction" as in something like instr = add | lw | sw | … .

It suggests to me that we no longer have a clear concept of "instruction"

It was never "clear", there are multiple ways how to model instructions in ArchC language and always been.
What is defined is assembly at one end and encoding at the other - everything in between can be done in multiple ways. Note also, that as code stands now it assumes there are some other concepts, like opcode field but really, there's no such thing.

The Sail definition of RISC-V seems no better

True, but in case of RISC-V  those opcodes files maintained by RISC-V foundation and "more authoritative" that if we just write ArchC PDL by hand. So by "authortitative" sources I meant really "more authoritative" than what we have now. Parsing BookMaster sources would give us that "more". All that w.r.t. encoding / decoding. Poor quality of POWER PDL is one thing that holds Tinyrossa's POWER backend back.

It was never "clear", there are multiple ways how to model instructions in ArchC language

That's not what I am talking about.  The problem is not ArchC.  The problem is the Green Cloth (and whatever other "authoritative sources" we have for any number of ISAs):

Parsing BookMaster sources would give us that "more"

Only in the limited example of instruction-encodings, but not for other aspects such as assembly.  Case in point: that right margin of p.385, written in the kind of "prophetic English" which I was talking about in the Cambridge-2014 talk ("…don't step on the rake…boom!").  I would go as far as saying that the ArchC language is actually better than the Green Cloth even though it's wrong, because the Green Cloth is informal no matter how you parse it.

Now, I am not contesting that the current quality of the POWER ArchC PDL is unusable for what we are trying to do.  What I am saying is that parsing Green Cloth will not help, no matter how sophisticated parsing technology.


Need to check the resource attribute - Alarm notification

Notification proxy message:
{
"notification-proxy-1-0:alarm-event-notification": {
"alarm-event-sequence-number": 1,
"timestamp": "2024-02-07T09:49:41.0+00:00",
"resource": "/core-model-1-4:network-control-domain=live/control-construct=513250009/logical-termination-point=LTP-MWPS-TTP-RADIO-1A/layer-protocol=LP-MWPS-TTP-RADIO-1A/air-interface-2-0:air-interface-pac",
"alarm-type-id": "siae-alarms-1-0:radioEquipLinkTelemetryFailAlarm",
"alarm-type-qualifier": "",
"problem-severity": "major"
}
}
The 500 error is caused by an error in the resource attribute of the message.
/core-model-1-4:network-control-domain=live/control-construct=513250009/logical-termination-point=LTP-MWPS-TTP-RADIO-1A/layer-protocol=LP-MWPS-TTP-RADIO-1A/air-interface-2-0:air-interface-pac is not correct as is not present in MWDI...
The available APIs are :
•	/core-model-1-4:network-control-domain=cache/control-construct={mountName}/logical-termination-point={uuid}/layer-protocol={localId}/air-interface-2-0:air-interface-pac/air-interface-capability
•	/core-model-1-4:network-control-domain=cache/control-construct={mountName}/logical-termination-point={uuid}/layer-protocol={localId}/air-interface-2-0:air-interface-pac/air-interface-configuration
•	/core-model-1-4:network-control-domain=cache/control-construct={mountName}/logical-termination-point={uuid}/layer-protocol={localId}/air-interface-2-0:air-interface-pac/air-interface-status
•	/core-model-1-4:network-control-domain=cache/control-construct={mountName}/logical-termination-point={uuid}/layer-protocol={localId}/air-interface-2-0:air-interface-pac/air-interface-historical-performances
It seems that in the resource attribute is missing the last part of the url.

The resource attribute contains "/core-model-1-4:control-construct" twice.
"resource":"/core-model-1-4:network-control-domain=live/control-construct=CO17694/core-model-1-4:control-construct/equipment=HUAWEI-EQUIPMENT-1",

{"notification-proxy-1-0:alarm-event-notification":{
"alarm-event-sequence-number":1702,
"timestamp":"2024-02-14T05:53:11+00:00",
"resource":"/core-model-1-4:network-control-domain=live/control-construct=CO17694/core-model-1-4:control-construct/equipment=HUAWEI-EQUIPMENT-1",
"alarm-type-id":"alarms-1-0:ALARM_TYPE_ID_TYPE_NE_OBJ",
"alarm-type-qualifier":"DCNSIZE_OVER/13110-20/FFFFFFFFFF",
"problem-severity":"major"
}
}

The output resource contained in the "notification-proxy-1-0:alarm-event-notification" is built correctly according to the specification and the data received from the controller.
@openBackhaul The current "resource" structure is missing parts at the end according to MWDI specification. Please check if there is something wrong with controller input for NotificationProxy (device alarms) or the MWDI specification, as this is not an NP issue.
Example input data from controller:
data: {"ietf-restconf:notification":{"alarms-1-0:alarm-event-notification":{"alarm-event-sequence-number":21,"problem-severity":"alarms-1-0:SEVERITY_AND_CLEARED_TYPE_CLEARED","timestamp":"2024-02-14T10:49:19.0+00:00","resource":"/core-model-1-4:control-construct/logical-termination-point[uuid='LTP-MWPS-TTP-RADIO-1A']/layer-protocol[local-id='LP-MWPS-TTP-RADIO-1A']/air-interface-2-0:air-interface-pac","alarm-type-qualifier":"","alarm-type-id":"siae-alarms-1-0:radioBranchTxPowerAlarm"}},"event-time":"2024-02-14T10:49:21Z","node-id":"513250009"}

As per the discussion, this issue will be fixed by MWDI team


Null reference related to layout rebuilder

I'm not sure if any of you are experiencing this but I keep getting a null reference error everytime I click the send button. I'm not sure where the problem is located because when I checked if I have everything correctly it shows that I have and the problem is also not code based as far as I can see, to my knowledge at least.
I just went to my application, then run the start button, go to the NPC and speak to her and then see the error pop up.

What is supposed to happen is that the character should be responding after the send button is clicked

OS: Windows 11
Unity Version 2021.3.20f1
I used the latest version of this plugin for unity
some words in the pictures are dutch

Hi @DylanPipping,
The UI provided in the samples are for demonstration purposes and may not work stably. I'd suggest you to develop a solution that suits you game.


61 alternative setup script for local non dockerised sql database

Manual version works - will test Docker tomorrow

./setup.sh
Welcome to PanelSearch!
If you would like to setup the app with a Docker container SQL database, please enter '1'. If you would like to setup the app with a cloud SQL database, please enter '2'.
1
Proceeding with docker set up...
Checking for docker.io:
No docker.io. Setting up docker.io.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies.
containerd.io : Conflicts: containerd
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
Checking for docker-buildx:
No docker-buildx. Setting up docker-buildx.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies.
containerd.io : Conflicts: containerd
docker-ce : Conflicts: docker.io but 24.0.5-0ubuntu1~22.04.1 is to be installed
docker-ce-cli : Conflicts: docker.io but 24.0.5-0ubuntu1~22.04.1 is to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
Docker running
Checking for mysql-server: install ok installed
Error response from daemon: network with name panelsearch-network already exists
panelsearch-network created
panelsearch-volume
panelsearch-volume created
c7f2008f96d719420084529a8de3566611a4fe9264a43499316324f47599fcf9
panelsearch-database container created
mysql: [Warning] Using a password on the command line interface can be insecure.
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
Attempt 1 failed. Trying again...
mysql: [Warning] Using a password on the command line interface can be insecure.
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
Attempt 2 failed. Trying again...
mysql: [Warning] Using a password on the command line interface can be insecure.
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
Attempt 3 failed. Trying again...
mysql: [Warning] Using a password on the command line interface can be insecure.
The command was successful after 4 attempts.
panelsearch database created
database tables 'searches' and 'patients' created
permissions enabled
[+] Building 2.6s (13/13) FINISHED                                                                                docker:desktop-linux
=> [internal] load .dockerignore                                                                                0.0s
=> => transferring context: 680B                                                                                0.0s
=> [internal] load build definition from Dockerfile                                                                                0.0s
=> => transferring dockerfile: 2.09kB                                                                                0.0s
=> resolve image config for docker.io/docker/dockerfile:1                                                                             1.1s
=> CACHED docker-image://docker.io/docker/dockerfile:1@sha256:ac85f380a63b13dfcefa89046420e1781752bab202122f8f50032edf31be0021        0.0s
=> [internal] load metadata for docker.io/library/python:3.10-slim                                                                    1.1s
=> [stage-1 1/6] FROM docker.io/library/python:3.10-slim@sha256:903313fe670c4a5ca8c73fee2dab499f677545f1f1029cf455dfb2ba1e024930      0.0s
=> => resolve docker.io/library/python:3.10-slim@sha256:903313fe670c4a5ca8c73fee2dab499f677545f1f1029cf455dfb2ba1e024930              0.0s
=> [internal] load build context                                                                                0.0s
=> => transferring context: 24.48kB                                                                                0.0s
=> CACHED [stage-1 2/6] WORKDIR /app                                                                                0.0s
=> CACHED [stage-1 3/6] RUN adduser     --disabled-password     --gecos ""     --home "/nonexistent"     --shell "/sbin/nologin"      0.0s
=> CACHED [stage-1 4/6] RUN chown appuser:appuser -R /app                                                                             0.0s
=> CACHED [stage-1 5/6] RUN --mount=type=cache,target=/root/.cache/pip     --mount=type=bind,source=requirements.txt,target=requirem  0.0s
=> [stage-1 6/6] COPY . .                                                                                0.0s
=> exporting to image                                                                                0.1s
=> => exporting layers                                                                                0.1s
=> => writing image sha256:f6951a58e81c81059cccb2f04e2f7fd5d118a5696d59cefce4ecc2336f6b1fe2                                           0.0s
=> => naming to docker.io/library/panelsearch                                                                                0.0s
panelsearch app container created
running panelsearch app...
successful connection to docker database
Traceback (most recent call last):
File "/app/./PanelSearch/main.py", line 29, in
RotatingFileHandler(log_file, maxBytes=50000, backupCount=1)
File "/usr/local/lib/python3.10/logging/handlers.py", line 155, in init
BaseRotatingHandler.init(self, filename, mode, encoding=encoding,
File "/usr/local/lib/python3.10/logging/handlers.py", line 58, in init
logging.FileHandler.init(self, filename, mode=mode,
File "/usr/local/lib/python3.10/logging/init.py", line 1169, in init
StreamHandler.init(self, self._open())
File "/usr/local/lib/python3.10/logging/init.py", line 1201, in _open
return open_func(self.baseFilename, self.mode,
PermissionError: [Errno 13] Permission denied: '/app/panel_search.log'

./setup.sh
Welcome to PanelSearch!
If you would like to setup the app with a Docker container SQL database, please enter '1'. If you would like to setup the app with a cloud SQL database, please enter '2'.
2
[+] Building 3.1s (13/13) FINISHED                                                                                docker:desktop-linux
=> [internal] load .dockerignore                                                                                0.0s
=> => transferring context: 680B                                                                                0.0s
=> [internal] load build definition from Dockerfile                                                                                0.0s
=> => transferring dockerfile: 2.09kB                                                                                0.0s
=> resolve image config for docker.io/docker/dockerfile:1                                                                             1.6s
=> CACHED docker-image://docker.io/docker/dockerfile:1@sha256:ac85f380a63b13dfcefa89046420e1781752bab202122f8f50032edf31be0021        0.0s
=> [internal] load metadata for docker.io/library/python:3.10-slim                                                                    1.2s
=> [stage-1 1/6] FROM docker.io/library/python:3.10-slim@sha256:646f0a074d101fae8a85c8889f9458d2fb52763b47f12ac654c8dcb2ee6e43f4      0.0s
=> => resolve docker.io/library/python:3.10-slim@sha256:646f0a074d101fae8a85c8889f9458d2fb52763b47f12ac654c8dcb2ee6e43f4              0.0s
=> [internal] load build context                                                                                0.0s
=> => transferring context: 4.25kB                                                                                0.0s
=> CACHED [stage-1 2/6] WORKDIR /app                                                                                0.0s
=> CACHED [stage-1 3/6] RUN adduser     --disabled-password     --gecos ""     --home "/nonexistent"     --shell "/sbin/nologin"      0.0s
=> CACHED [stage-1 4/6] RUN chown appuser:appuser -R /app                                                                             0.0s
=> CACHED [stage-1 5/6] RUN --mount=type=cache,target=/root/.cache/pip     --mount=type=bind,source=requirements.txt,target=requirem  0.0s
=> CACHED [stage-1 6/6] COPY . .                                                                                0.0s
=> exporting to image                                                                                0.0s
=> => exporting layers                                                                                0.0s
=> => writing image sha256:f6951a58e81c81059cccb2f04e2f7fd5d118a5696d59cefce4ecc2336f6b1fe2                                           0.0s
=> => naming to docker.io/library/panelsearch                                                                                0.0s
panelsearch app container created
running panelsearch app...
Traceback (most recent call last):
File "/usr/local/lib/python3.10/site-packages/pymysql/connections.py", line 644, in connect
sock = socket.create_connection(
File "/usr/local/lib/python3.10/socket.py", line 845, in create_connection
raise err
File "/usr/local/lib/python3.10/socket.py", line 833, in create_connection
sock.connect(sa)
TimeoutError: timed out
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.10/site-packages/sqlalchemy/engine/base.py", line 145, in init
self._dbapi_connection = engine.raw_connection()
File "/usr/local/lib/python3.10/site-packages/sqlalchemy/engine/base.py", line 3292, in raw_connection
return self.pool.connect()
File "/usr/local/lib/python3.10/site-packages/sqlalchemy/pool/base.py", line 452, in connect
return _ConnectionFairy._checkout(self)
File "/usr/local/lib/python3.10/site-packages/sqlalchemy/pool/base.py", line 1269, in _checkout
fairy = _ConnectionRecord.checkout(pool)
File "/usr/local/lib/python3.10/site-packages/sqlalchemy/pool/base.py", line 716, in checkout
rec = pool._do_get()
File "/usr/local/lib/python3.10/site-packages/sqlalchemy/pool/impl.py", line 169, in _do_get
with util.safe_reraise():
File "/usr/local/lib/python3.10/site-packages/sqlalchemy/util/langhelpers.py", line 146, in exit
raise exc_value.with_traceback(exc_tb)
File "/usr/local/lib/python3.10/site-packages/sqlalchemy/pool/impl.py", line 167, in _do_get
return self._create_connection()
File "/usr/local/lib/python3.10/site-packages/sqlalchemy/pool/base.py", line 393, in _create_connection
return _ConnectionRecord(self)
File "/usr/local/lib/python3.10/site-packages/sqlalchemy/pool/base.py", line 678, in init
self.__connect()
File "/usr/local/lib/python3.10/site-packages/sqlalchemy/pool/base.py", line 902, in __connect
with util.safe_reraise():
File "/usr/local/lib/python3.10/site-packages/sqlalchemy/util/langhelpers.py", line 146, in exit
raise exc_value.with_traceback(exc_tb)
File "/usr/local/lib/python3.10/site-packages/sqlalchemy/pool/base.py", line 898, in __connect
self.dbapi_connection = connection = pool._invoke_creator(self)
File "/usr/local/lib/python3.10/site-packages/sqlalchemy/engine/create.py", line 637, in connect
return dialect.connect(*cargs, **cparams)
File "/usr/local/lib/python3.10/site-packages/sqlalchemy/engine/default.py", line 616, in connect
return self.loaded_dbapi.connect(*cargs, **cparams)
File "/usr/local/lib/python3.10/site-packages/pymysql/connections.py", line 358, in init
self.connect()
File "/usr/local/lib/python3.10/site-packages/pymysql/connections.py", line 711, in connect
raise exc
pymysql.err.OperationalError: (2003, "Can't connect to MySQL server on '<IP_ADDRESS>' (timed out)")
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/app/./PanelSearch/main.py", line 21, in
from API_to_SQL_cloud import PK_Parse_Data_to_SQL_cloud
File "/app/PanelSearch/API_to_SQL_cloud.py", line 3, in
from SQL_Cloud_Functions import connect_cloud_db, add_new_cloud_record
File "/app/PanelSearch/SQL_Cloud_Functions.py", line 46, in
connection_string = docker_or_cloud()
File "/app/PanelSearch/SQL_Cloud_Functions.py", line 39, in docker_or_cloud
conn = engine.connect()
File "/usr/local/lib/python3.10/site-packages/sqlalchemy/engine/base.py", line 3268, in connect
return self._connection_cls(self)
File "/usr/local/lib/python3.10/site-packages/sqlalchemy/engine/base.py", line 147, in init
Connection._handle_dbapi_exception_noconnection(
File "/usr/local/lib/python3.10/site-packages/sqlalchemy/engine/base.py", line 2430, in _handle_dbapi_exception_noconnection
raise sqlalchemy_exception.with_traceback(exc_info[2]) from e
File "/usr/local/lib/python3.10/site-packages/sqlalchemy/engine/base.py", line 145, in init
self._dbapi_connection = engine.raw_connection()
File "/usr/local/lib/python3.10/site-packages/sqlalchemy/engine/base.py", line 3292, in raw_connection
return self.pool.connect()
File "/usr/local/lib/python3.10/site-packages/sqlalchemy/pool/base.py", line 452, in connect
return _ConnectionFairy._checkout(self)
File "/usr/local/lib/python3.10/site-packages/sqlalchemy/pool/base.py", line 1269, in _checkout
fairy = _ConnectionRecord.checkout(pool)
File "/usr/local/lib/python3.10/site-packages/sqlalchemy/pool/base.py", line 716, in checkout
rec = pool._do_get()
File "/usr/local/lib/python3.10/site-packages/sqlalchemy/pool/impl.py", line 169, in _do_get
with util.safe_reraise():
File "/usr/local/lib/python3.10/site-packages/sqlalchemy/util/langhelpers.py", line 146, in exit
raise exc_value.with_traceback(exc_tb)
File "/usr/local/lib/python3.10/site-packages/sqlalchemy/pool/impl.py", line 167, in _do_get
return self._create_connection()
File "/usr/local/lib/python3.10/site-packages/sqlalchemy/pool/base.py", line 393, in _create_connection
return _ConnectionRecord(self)
File "/usr/local/lib/python3.10/site-packages/sqlalchemy/pool/base.py", line 678, in init
self.__connect()
File "/usr/local/lib/python3.10/site-packages/sqlalchemy/pool/base.py", line 902, in __connect
with util.safe_reraise():
File "/usr/local/lib/python3.10/site-packages/sqlalchemy/util/langhelpers.py", line 146, in exit
raise exc_value.with_traceback(exc_tb)
File "/usr/local/lib/python3.10/site-packages/sqlalchemy/pool/base.py", line 898, in __connect
self.dbapi_connection = connection = pool._invoke_creator(self)
File "/usr/local/lib/python3.10/site-packages/sqlalchemy/engine/create.py", line 637, in connect
return dialect.connect(*cargs, **cparams)
File "/usr/local/lib/python3.10/site-packages/sqlalchemy/engine/default.py", line 616, in connect
return self.loaded_dbapi.connect(*cargs, **cparams)
File "/usr/local/lib/python3.10/site-packages/pymysql/connections.py", line 358, in init
self.connect()
File "/usr/local/lib/python3.10/site-packages/pymysql/connections.py", line 711, in connect
raise exc
sqlalchemy.exc.OperationalError: (pymysql.err.OperationalError) (2003, "Can't connect to MySQL server on '<IP_ADDRESS>' (timed out)")
(Background on this error at: https://sqlalche.me/e/20/e3q8)

./setup.sh
Welcome to PanelSearch!
If you would like to setup the app with a Docker container SQL database, please enter '1'. If you would like to setup the app with a cloud SQL database, please enter '2'.
1
Proceeding with docker set up...
Checking for docker.io:
No docker.io. Setting up docker.io.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies.
containerd.io : Conflicts: containerd
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
Checking for docker-buildx:
No docker-buildx. Setting up docker-buildx.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies.
containerd.io : Conflicts: containerd
docker-ce : Conflicts: docker.io but 24.0.5-0ubuntu1~22.04.1 is to be installed
docker-ce-cli : Conflicts: docker.io but 24.0.5-0ubuntu1~22.04.1 is to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.

ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
Attempt 1 failed. Trying again...
mysql: [Warning] Using a password on the command line interface can be insecure.
ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
Attempt 2 failed. Trying again...
mysql: [Warning] Using a password on the command line interface can be insecure.
ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: YES)
Attempt 3 failed. Trying again...
mysql: [Warning] Using a password on the command line interface can be insecure.
The command was successful after 4 attempts.
panelsearch database created
database tables 'searches' and 'patients' created
permissions enabled
[+] Building 1.9s (15/15) FINISHED                                                                                docker:desktop-linux
=> [internal] load build definition from Dockerfile                                                                                0.0s
=> => transferring dockerfile: 2.22kB                                                                                0.0s
=> [internal] load .dockerignore                                                                                0.0s
=> => transferring context: 680B                                                                                0.0s
=> resolve image config for docker.io/docker/dockerfile:1                                                                             0.8s
=> CACHED docker-image://docker.io/docker/dockerfile:1@sha256:ac85f380a63b13dfcefa89046420e1781752bab202122f8f50032edf31be0021        0.0s
=> [internal] load metadata for docker.io/library/python:3.10-slim                                                                    0.8s
=> [stage-1 1/8] FROM docker.io/library/python:3.10-slim@sha256:e91e79e5af602e7dbe9200e71c8e39006aa60621b547b26f75e9bddc9f7b07c9      0.0s
=> [internal] load build context                                                                                0.0s
=> => transferring context: 4.25kB                                                                                0.0s
=> CACHED [stage-1 2/8] WORKDIR /app                                                                                0.0s
=> CACHED [stage-1 3/8] RUN adduser     --disabled-password     --gecos ""     --home "/nonexistent"     --shell "/sbin/nologin"      0.0s
=> CACHED [stage-1 4/8] RUN chown appuser:appuser -R /app                                                                             0.0s
=> CACHED [stage-1 5/8] RUN chmod 777 -R /app                                                                                0.0s
=> CACHED [stage-1 6/8] RUN --mount=type=cache,target=/root/.cache/pip     --mount=type=bind,source=requirements.txt,target=requirem  0.0s
=> CACHED [stage-1 7/8] COPY . .                                                                                0.0s
=> CACHED [stage-1 8/8] WORKDIR ./PanelSearch                                                                                0.0s
=> exporting to image                                                                                0.0s
=> => exporting layers                                                                                0.0s
=> => writing image sha256:3bfe7b2939f277ed3873f1c7210c4e046dfc8a3fa66ff99a18612f2cf167bb86                                           0.0s
=> => naming to docker.io/library/panelsearch                                                                                0.0s
panelsearch app container created
running panelsearch app...
successful connection to docker database
If you would like to search by R-code, enter 1. If you would like to enter a disease description, enter 2.
1
Enter your search term: (e.g., R128 or pneumothorax)
R128
Which genome build would you like to use? Enter 1 for GRCh37. Enter 2 for GRCh38.
1
GRch37 build selected.
 (Y/N)
Y
Traceback (most recent call last):
File "/app/PanelSearch/generate_bed.py", line 20, in
RotatingFileHandler(log_file, maxBytes=10000, backupCount=1)
File "/usr/local/lib/python3.10/logging/handlers.py", line 155, in init
BaseRotatingHandler.init(self, filename, mode, encoding=encoding,
File "/usr/local/lib/python3.10/logging/handlers.py", line 58, in init
logging.FileHandler.init(self, filename, mode=mode,
File "/usr/local/lib/python3.10/logging/init.py", line 1169, in init
StreamHandler.init(self, self._open())
File "/usr/local/lib/python3.10/logging/init.py", line 1201, in _open
return open_func(self.baseFilename, self.mode,
PermissionError: [Errno 13] Permission denied: '/app/PanelSearch/generate_bed.log'
Would you like to save this search against a patient ID? (Y/N)
Y
What patient ID would you like to save this search against?
hester
Brugada syndrome and cardiac sodium channel disease
GRch37
GRch37 build selected.
Panel ID: 13
Panel Name: Brugada syndrome and cardiac sodium channel disease
GMS Sign-off Status: Signed Off
Associated NGTD R-codes: R128
Gene Number: 23
Gene List:
HGNC_ID  Symbol  Coords  Mane_Select_Transcript
HGNC:10593 SCN5A  3:38589548-38691164 NM_000335.5
HGNC:6251 KCNH2  7:150642049-150675403 NM_000238.4
HGNC:60 ABCC9  12:21950335-22094336 NM_020297.4
HGNC:493 ANK2  4:113739265-114304896 NM_001148.6
HGNC:1390 CACNA1C  12:2079952-2802108 NM_000719.7
HGNC:1399 CACNA2D1  7:81575760-82073114 NM_000722.4
HGNC:1402 CACNB2  10:18429606-18830798 NM_201596.3
HGNC:1529 CAV3  3:8775486-8883492 NM_033337.3
HGNC:2900 DLG1  3:196769431-197026171 NM_001366207.1
HGNC:28956 GPD1L  3:32147181-32210205 NM_015141.4
HGNC:16882 HCN4  15:73612200-73661605 NM_005477.3
HGNC:6239 KCND3  1:112313284-112531777 NM_001378969.1
HGNC:6243 KCNE3  11:74165886-74178774 NM_005472.5
HGNC:6241 KCNE5  X:108866929-108868393 NM_012282.4
HGNC:6269 KCNJ8  12:21917889-21928515 NM_004982.4
HGNC:9024 PKP2  12:32943679-33049774 NM_001005242.3
HGNC:17679 RANGRF  17:8191815-8193410 NM_016492.5
HGNC:10582 SCN10A  3:38738293-38835501 NM_006514.4
HGNC:10586 SCN1B  19:35521588-35531352 NM_001037.5
HGNC:10589 SCN2B  11:118032666-118047388 NM_004588.5
HGNC:20665 SCN3B  11:123499895-123525952 NM_001040151.2
HGNC:16643 SLMAP  3:57741177-57914895 NM_001377540.1
HGNC:17993 TRPM4  19:49660998-49715093 NM_017636.4
1
Your search was saved
Thank you for using PanelSearch. Goodbye.

Error with option 1 is now fixed thank you


Lucky - Milestone 3 delivery

@HashWarlock please find this PR for milestone 3 delivery

If all checks on Milestone 3 are finished on business side, this LGTM

I see the todo for the contract. I'll wait for that link to be added before merging @GuiGou12358


Normalize method tracing pattern

Description
Currently, in various methods there is the following pattern to trace them:
SomeClass::SomeMethod()
{
    boolean bTrace = false;
    // <some code>

    if (bTrace)
    {
        cout << "Some trace information" << endl;
        // ...
    }
}

This pattern allows to diagnose bugs in complex code by setting bTrace = true temporarily. The pattern is not normalized because

There are many names for the boolean flag: bTrace, bLocalTrace, bDisplay ... etc.
Some of them use const boolean while others boolean.

Questions/Ideas

Proposal:

The trace booleans must be defined at the top of the method

before or after a potential bOk?

Either be called bTrace or use it as a suffix (ex. bTraceResults)
Always be const

Do compilers warn a lot ?
We should not expect performance gains

A ajouter dans le wiki dans les normes de dev + faire une autre issue de reprise de qualité de code.


Issue 151 dropdown update styling

Issue 151 dropdown update styling

One other thing I noticed is the vertical spacing between tags when they span multiple lines seems incorrect:

I guess the spacing between lines of tags should be the same as the box padding(?)


Fixing login page header issue

What
Fixes the header issue on the main page
How to test

Checkout this branch
Run the server
Browse http://<IP_ADDRESS>:8000

Who can test
Anyone apart from @warren-methods

¬¬LGTM :+1:


Fix documentation hosted 404 page

404 page in the documentation is not appearing correctly:

I think it's because we haven't set site_url in mkdocs.yml. See https://github.com/squidfunk/mkdocs-material/issues/755#issuecomment-380814739.
I've tested setting this locally and it still works. dev_addr overrides site_url during local tests so there's no issue there. I'll open a PR for this shortly.


update this

Q: what should SKCro do with WebTV HD?
A: UPDATE IT!

I'm working on a big update soon. Stay tuned :P

:D

Just pushed the update


remove depth from Savepoint

Savepoints with the same name nest properly without issue.  This doesn't work with rusqlite unless savepoints are always released on drop.
closes #1326

I guess that:
https://github.com/rusqlite/rusqlite/blob/841014bfd11f0077ff2f4c8a0f11c919d0e9cbb7/src/transaction.rs#L347
is buggy.
In case of error on RELEASE, we ROLLBACK the savepoint.
But we should ROLLBACK AND RELEASE, no?
sqlite> PRAGMA foreign_keys = true;
sqlite> CREATE TABLE r(n INTEGER PRIMARY KEY NOT NULL);
sqlite> CREATE TABLE f(n REFERENCES r(n) DEFERRABLE INITIALLY DEFERRED);
sqlite> SAVEPOINT s;
sqlite> INSERT INTO f VALUES (0);
sqlite> RELEASE s;
Runtime error: FOREIGN KEY constraint failed (19)
sqlite> ROLLBACK TO s;
sqlite> COMMIT; -- does not failed s is still on the stack...

Ah, yes, you're right.  I had overlooked that.


Added BMR Calculator

Title : Added new BMR Calculator
Issue : #68

@Surajit0573 please resolve the conflicts, and add a relevant background image for the calculator page

Hi @ritika728 , I resolved all conflicts, and added a relevant background image.

Looks good to merge


Add github-act-runner

It might be useful to add a runner to the matrix which runs on previously unusable:

Operating Systems like Openbsd, Freebsd, Netbsd, Solaris, Dragonfly, Plan9, Android and Illumos.
Architectures like riscv64, s390x, ppc64, ppc64le, mips, mipsle, mips64, mips64le.

This runner is build around nektos/act + an (re)implementation of the runner protocol (works without docker).
I'm not shure if the column Architectures includes the Operating System. Not all OS/Arch combinations are supported.

Thanks a lot for your contribution :octocat: :heart:


Add an LRU cache to make_trie_root_and_nodes()

Unfortunately this won't be enough by itself because we'd still be making one block.get_receipts() call for every tx applied, and that's too expensive to run for every tx.

And caching ChainDB.get_receipts() doesn't help because every time it is called (as part of VM.apply_transaction()) it is passed a different receipt_root for the trie containing only the receipts of the transactions that have already been applied

So, this won't replace #565 but it might still be beneficial, specially since Byzantium blocks may have duplicate receipt_roots. Will benchmark to find out

Now that #565 has been merged and we're no longer generating/storing partial tx/receipt tries, it makes more sense to cache the whole thing here.


Imported privileges on SNOWFLAKE database not registered in state

Provider Version
0.69.0
Terraform Version
1.5.4
Describe the bug
The GRANT IMPORTED PRIVILEGES ON DATABASE SNOWFLAKE TO ROLE X  is not properly registered in the state file, which causes every terraform plan to consider these privileges as non-existent privileges every time.
Expected behavior
For these privileges to be registered in the state file.
Code samples and commands
resource "snowflake_grant_privileges_to_role" "snowflake_imported_privileges_usage_monitoring" {
  privileges = ["IMPORTED PRIVILEGES"]
  role_name  = snowflake_role.usage_monitoring.name
  on_account_object {
    object_type = "DATABASE"
    object_name = "SNOWFLAKE"
  }
}

I'm seeing this in provider version 0.68.0 as well

So happy to see this issue raised again, it's been driving me nuts.  I've needed to manually comment/uncomment this line in my snowflake_database_grant resource to work around it:
  lifecycle {
    ignore_changes = all
  }

Related: https://github.com/Snowflake-Labs/terraform-provider-snowflake/issues/1573

We had been facing the same issue, wherein snowflake.account_usage grant would show up on each terraform plan. We would ignore it and apply the changes and nothing would change. But from past few days apply has been failing for this resource with insufficient privileges error. Can you please help to check this?

We are facing the same issue with a USAGE grant on version 0.70.0 of the provider. It is not properly recoded in the state. For example applying following resource:
resource "snowflake_grant_privileges_to_role" "<some_grant_name>" {
  for_each   = var.schemas
  privileges = ["USAGE"]
  role_name  = snowflake_role.<some-role>.name
  on_schema {
    schema_name = "${snowflake_database.<some-db>.name}.${snowflake_schema.<some-schema>[each.key].name}"
  }
}

It will still yield the following changes when using plan:
# snowflake_grant_privileges_to_role.<some_grant_name>["<some-key>"] will be updated in-place
~ resource "snowflake_grant_privileges_to_role" "<some_grant_name>" {
      id                = "<generated-id>"
    ~ privileges        = [
        + "USAGE",
      ]
      # (4 unchanged attributes hidden)
      # (1 unchanged block hidden)
  }

Any update on this issue. Our terraform apply keep getting failed because of this issue.

I am also observing this bug and documented it in #1981

We are having this error with the new snowflake_grant_privileges_to_role grant resources of v0.70.1
resource "snowflake_grant_privileges_to_role" "role1" {
  provider          = snowflake.accountadmin
  privileges        = ["IMPORTED PRIVILEGES"]
  role_name         = "ROLE1"
  on_account_object {
    object_type = "DATABASE"
    object_name = "SNOWFLAKE"
  }
}

The grant is in the state, visible with terraform state show, but terraform still detects changes in the Terraform plan.

I am also getting this error. Any updates on a fix?

I am seeing this behavior as well. Is anyone looking into this?

This issue is still present on 0.75.0

I'm still observing this in 0.79.1. It occurs with both the snowflake_database_grant resource and the snowflake_grant_privileges_to_role resource. Anything we can do to get some eyes on this from the Snowflake team?

Hi all,
IMPORTED PRIVILEGES is one of the problematic privileges to handle in the Terraform. Mainly, because it's more of an "abstract" privilege. It cannot be queried and that's the main reason behind the infinite plan.
We will be working soon on a workaround that will work for now. It won't be a final fix and we will come back to it sooner or later, but it should fix the infinite plan issue everyone is mentioning.

Hi again 👋
Yesterday we released a new version (v0.86.0). @dlouseiro Could you and others confirm the issue has been resolved and the ticket can be closed? Thanks :)

@sfc-gh-jcieslak, I upgrded the provider to v0.87.0, but still have the same issue.  And I tried both ways snowflake_grant_privileges_to_role and snowflake_database_grant
resource "snowflake_grant_privileges_to_role" "database_grant_usage" {
  provider   = snowflake.security
  privileges = ["IMPORTED PRIVILEGES"]
  role_name  = module.read_role.name
  on_account_object {
    object_type = "DATABASE"
    object_name = local.name
  }
}

And got change on plan after apply.
Terraform will perform the following actions:

  # module.snowflake_database.snowflake_grant_privileges_to_role.database_grant_usage will be updated in-place
  ~ resource "snowflake_grant_privileges_to_role" "database_grant_usage" {
        id                = "SNOWFLAKE_READ|IMPORTED PRIVILEGES|false|false|false|true|false|false|false|false|DATABASE|SNOWFLAKE||false||false|"
      ~ privileges        = [
          + "IMPORTED PRIVILEGES",
        ]
        # (4 unchanged attributes hidden)

        # (1 unchanged block hidden)
    }

Plan: 0 to add, 1 to change, 0 to destroy.

resource "snowflake_database_grant" "database_grant_usage" {
  provider      = snowflake.security
  database_name = local.name
  privilege     = "IMPORTED PRIVILEGES"
  roles         = [module.read_role.name]

Terraform will perform the following actions:

  # module.snowflake_database.snowflake_database_grant.database_grant_usage will be updated in-place
  ~ resource "snowflake_database_grant" "database_grant_usage" {
        id                     = "SNOWFLAKE|IMPORTED PRIVILEGES|false|SNOWFLAKE_READ|"
      ~ roles                  = [
          + "SNOWFLAKE_READ",
        ]
        # (5 unchanged attributes hidden)
    }

Plan: 0 to add, 1 to change, 0 to destroy.

Did I miss something?

@Tideorz Please see this thread - https://github.com/Snowflake-Labs/terraform-provider-snowflake/issues/2459 We need to take additional steps to make it work, but I'm working on it right now.

@sfc-gh-jcieslak, I still got the same error.

@Tideorz Interesting, could you share more details? Terraform CLI version, Snowflake provider version, configuration that's causing the issue? The latest resource to grant privileges to account role is snowflake_grant_privileges_to_account_role and that's the most updated version. Other deprecated resources are not supported, so if you are still using deprecated resources, please migrate to the newest ones. Here's a list of currently deprecated resources and here's a guide on migrating resources with no downtime with grants as an example.

@sfc-gh-jcieslak, thanks for your information. I didn't use the snowflake_grant_privileges_to_account_role before.
And I tried on the v0.87.2
resource "snowflake_grant_privileges_to_account_role" "database_grant_usage" {
  provider          = snowflake.admin
  privileges        = ["IMPORTED PRIVILEGES"]
  account_role_name = module.read_role.name
  on_account_object {
    object_type = "DATABASE"
    object_name = local.name
  }
}

But I got the error:
╷
│ Error: error revoking privileges from account role: [grants_validations.go:44] exactly one of AccountRoleGrantPrivileges fields [AllPrivileges GlobalPrivileges AccountObjectPrivileges SchemaPrivileges SchemaObjectPrivileges] must be set
│

Do you know how I could fix this?

@Tideorz Since it's an error from "revoking" privileges, I'm guessing that's the error from the old resource you just removed and not the one you're trying to add. Because old resources didn't support IMPORTED PRIVILEGES it may be hard to remove it properly. Please, follow the guide and remove the old privilege granting resource from the state and "replace" it with the new one. The whole process of removing old resource and adding a new one is described in the guide.

@sfc-gh-jcieslak, thanks a lot.
And I've another question, the terraform-provider-snowflake has changed a lot recently. And I found my Terraform code has a lot of deprecated resources. Do you know whether we'll remove these deprecated resources from the provider someday? I want to know how urgent I should take care of this resource migration work if you can give me some information.
Thanks

We won't be removing resources any time soon, but it's always recommended to use the latest TF provider versions/resources because they're the most complete (like in this example the newer grant resource has more edge cases covered). The deprecated resources will be probably removed with the v1.0.0 version, but it will still take some time until we get there (cannot say when) because there's still a lot to do.

Closing, as the fix was confirmed in other threads and gh issues. If the issue persists, please create another gh issue. Remember, we're not supporting the deprecated resources and before creating an issue, please check the latest provider version with non-deprecated resources to see if the issue is still present.


ReceiptCard is not displaying the ReceiptItem -> quantity field.

Github issues should be used for bugs and feature requests. Use Stack Overflow for general "how-to" questions.
Version
4.9.0
Describe the bug
When using the ReceiptCard , Emulator is not displaying the ReceiptItem -> quantity field.
To Reproduce
Steps to reproduce the behavior:
using the ReceiptCard with ReceiptItem with quantity
4. See error
Expected behavior
It should display the ReceiptItem with quantity
Screenshots

[bug]

@corinagum Could you take a look at this?
@rvinothrajendran Could you try out Adaptive Cards? Because it could make your card more expressive.

@compulim Yes you are correct,  This issue I found in while preparing the bot tutorial  ☹

Thanks for reporting this. This is an error in Web Chat where not all ReceiptItem properties are utilized. Looks like both quantity and text are missing.

@corinagum  would you please provide a status update for this issue.

This is on our TBD list for R11. Fairly confident it will be scoped to that milestone.

We will triage it in R11.


btrfs-progs: Missing dependency util-linux

-*blkid
in order arch and crux consider this cycle:
e2fsprogs requires util-linux (libblkid)
btrfs-progs requires e2fsprogs
alpine treat it differently:
libblkid in "main" origin from util-linux
e2fsprogs and brtfs-progs requires libblkid.
We should decide how to treat it.

The simplest solution is to just make btrfs-progs depend on util-linux.

Ok, i change depends and bump at release 5.6 in next PR. I think for now it's can close.

This has been fixed. Thanks all.


DMC scan no pages found

Source information
DMC scan 1.4.10
Source language
English
Steps to reproduce

Update chapter list, and the new chapter show up
Download / read chapter from app not working, says no page
From webview is fine

Expected behavior
Can read / download
Actual behavior
Can't read / download
Mihon/Tachiyomi version
0.16.5
Android version
Android 12
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] I have updated the app to version 0.15.3.
[X] I have updated all installed extensions.
[X] I have tried the troubleshooting guide.
[X] If this is an issue with the app itself, I should be opening an issue in the app repository.
[X] I will fill out all of the requested information in this form.

the website seems dead, do you know if they changed domain?

https://didachapters.blogspot.com/?m=1

closing in favor of #4675


package: mark as requiring node v4+

This way users will at least get a warning that this package requires
node v4+ instead of only finding out when it bails on first load.

Landed on df03b7b.  Thanks!


ARROW-17613: [C++] Add function execution API for a preconfigured kernel

See https://issues.apache.org/jira/browse/ARROW-17613

@lidavidm, are you a good person to review this? or can you suggest someone?

The idea sounds reasonable to me. I'd like to see unit tests here.

Will do.

Possibly expression evaluation can take advantage of this? Right now it manually resolves a kernel and evaluates it, being able to replace that would help prove out the API/implementation here

Perhaps. My motivation for this change is related to UDFs, which would have their kernel bound once and executed multiple times over a stream of batches.

I'm not sure what purpose this serves; when will we be able to use this? When executing an ExecPlan for example we already resolve all the kernels and types in Expression::Bind, then re-use those kernels for each input batch. Maybe this would be better as adding ExecuteScalarOrVectorExpression?

The focus here is on the function execution API, i.e., a lower-level API than the plan execution API. Currently, the function execution API goes through kernel selection on each invocation, because the types of the passed arguments may change each time. This PR adds a faster-path for executing a preconfigured kernel when the argument types are known to be fixed across invocations. Note that, in general, these invocations need not be over a stream of batches, like in an execution plan, but could be dynamically driven.

I'd like to see unit tests here.

Will do.

First, a user may directly use this where they would use the original function execution API.

I understand, but when do users touch the function execution API? I think that'd primarily be through the python or R bindings to handle ad-hoc cases like adding two arrays together... and in that case, constructing a FunctionExecutor would not be useful since the user input time delay will greatly outweigh kernel lookup.
A FunctionExecutor would only be useful when executing the same function multiple times- for example when applied to multiple batches from a stream of data. What I'd like to hear is when that's beneficial and isn't served by construction of an ExecPlan.

Second, as noted above, my motivation for this is related to UDFs, where their kernel would be preconfigured once then executed multiple times over a stream of batches (the kernel state ends up holding Python stuff). It's possible this kernel-preconfiguration can be integrated into expression binding too; I haven't looked into this.

Kernel preconfiguration is precisely the function of Expression::Bind, among other things:

invokes Function::DispatchBest to acquire a kernel and types for implicit casts
caches the Kernel and its state for later use in execution
note that currently Expression execution assumes only scalar functions are referenced and that KernelState is not mutated

In short, it seems that we won't be able to use FunctionExecutor where it seems to me we'd most like to see UDF capabilities: in filter and project expressions in ExecPlans. Since that will eventually require refactoring/extension of the Expression utilities, I'd prefer we start there so that we can have a better picture of the ways ExecPlan etc will need to change to accommodate UDFs. Building parallel streaming execution functionality which will ultimately need to be accommodated or assimilated by ExecPlans seems like much more churn.

@bkietz, before I answer your points, I should note that the code here is extracted from a working end-to-end (Ibis/Substrait/PyArrow) prototype for UDFs and UDTs, which are UDFs that provide a stream of tabular data, that I developed. While this doesn't mean its design would be accepted as is (and I do welcome feedback on it, or parts of it that I extract), there is currently no alternative working design. I'd expect to see a comparable alternative put forward, so I could evaluate pros and cons in the context of end-to-end support for UDFs and UDTs. In my mind, just evolving expression binding is not a comparable alternative.

I understand, but when do users touch the function execution API?

I said "user" but didn't mean "end-user" necessarily; I should have said "caller" for clarity. Still, the pre-PR function execution API is public, so we should assume it is used by end-users and the burden is actually in claiming the opposite (e.g., for deprecation purposes). The fact that there exists a higher-level API, which may be convenient for a lot of use cases (like streaming), does not change this.
Granted, there is also a burden of showing the proposed API is useful. I could point you to how the prototype uses this new function execution API, if that would be helpful. The general idea is that the end-user is driving from PyArrow and registers a UDT. The UDT is a Python-implemented function that may be invoked multiple times, each at a different source node in the execution plan. Each such invocation returns a stream object implemented in Python that is managed in a kernel state. Invoking the kernel returns tabular data that is part of the dynamically generated stream. The new function execution API is designed to enable this setup.

A FunctionExecutor would only be useful when executing the same function multiple times

Yes, on arguments of the same types.

What I'd like to hear is when that's beneficial and isn't served by construction of an ExecPlan.

AFAICS, the above described UDT functionality cannot be served by an ExecPlan nor by expression binding.

Kernel preconfiguration is precisely the function of Expression::Bind, among other things:
* [invokes Function::DispatchBest](https://github.com/apache/arrow/blob/40ec95646962cccdcd62032c80e8506d4c275bc6/cpp/src/arrow/compute/exec/expression.cc#L372) to acquire a kernel and types for implicit casts

* [caches the Kernel and its state](https://github.com/apache/arrow/blob/40ec95646962cccdcd62032c80e8506d4c275bc6/cpp/src/arrow/compute/exec/expression.h#L54-L58) for later use in execution

* note that currently Expression execution assumes only scalar functions are referenced and that KernelState is not mutated

IIUC, C++ code (for expression binding) is the driver here. In the prototype's design, it is end-user code, via PyArrow, who is the driver. It's not clear how to reconcile the two in a proposal based on expression binding. At least this will need to be explained in the context of a more complete description of an alternative.

A few thoughts:

I understand, but when do users touch the function execution API? I think that'd primarily be through the python or R bindings to handle ad-hoc cases like adding two arrays together... and in that case, constructing a FunctionExecutor would not be useful since the user input time delay will greatly outweigh kernel lookup.

I'm pretty sure there are existing cases where users have interacted directly with functions and not via an execution plan (I think @marsupialtail does this with Take and I seem to recall @drin using the compute API directly as well).  I'm not sure those cases couldn't be converted to an execution plan but they do exist.  IIRC these are cases where the user already has an engine / execution plan of their own and they are simply trying to integrate Arrow compute.
That being said, if we were going to go down this road, I think it would be more valuable to have an "expression executor" and not merely a "function executor".  Also, removing the lookup / argument resolution time is nice but the biggest win would be removing allocations for temporaries / outputs but that can be deferred for a future PR :).

@bkietz, before I answer your points, I should note that the code here is extracted from a working end-to-end (Ibis/Substrait/PyArrow) prototype for UDFs and UDTs, which are UDFs that provide a stream of tabular data, that I developed. While this doesn't mean its design would be accepted as is (and I do welcome feedback on it, or parts of it that I extract), there is currently no alternative working design. I'd expect to see a comparable alternative put forward, so I could evaluate pros and cons in the context of end-to-end support for UDFs and UDTs. In my mind, just evolving expression binding is not a comparable alternative.

I think the alternative (and this may be a misunderstanding of your goal) is that a UDT not be put into the function registry, even if it looks like a UDF elsewhere (e.g. Substrait).  As an example, consider an embedded python Substrait UDT (which does very much look like a UDF).  When we consume that plan we would convert that embedded UDT into a function.  Let's say it is a python function that returns an iterator of tabular data.  Instead of creating a stateful function to poll that iterator we could put that iterator into a source node, probably one of the source nodes you just created in #14207.  The it_maker would be a wrapper around your python function that returns a wrapper around your python iterable (I am fairly certain we wrap python iterators in either RecordBatchReader or AsyncGenerator<RecordBatch>) somewhere else too.  This removes the overhead of the function registry entirely.

I think it would be more valuable to have an "expression executor" and not merely a "function executor".

While I don't know enough about expression use cases, this sounds right to me in the wider context, i.e., outside of just UDFs/UDTs. Does this mean the expression executor should be built on top of the function executor proposed here?

Also, removing the lookup / argument resolution time is nice but the biggest win would be removing allocations for temporaries / outputs but that can be deferred for a future PR :).

I agree that removing allocations etc would be a significant win. What do you think is missing from this PR to do so? At least at the function executor API level, I believe repeated invocations of FunctionExecutor::Execute(const std::vector<Datum>& args, int64_t passed_length) should be able to avoid repeated allocations.

I think the alternative (and this may be a misunderstanding of your goal) is that a UDT not be put into the function registry.

This is an interesting alternative to compare to. I'll try to explain below the differences between this and the one proposed in this PR. I think each of the two alternatives has its merits, and we'll just need to choose whether we want one or both.
The source-node (Weston's) proposal for UDTs has several pros that I can see. It requires less changes to Arrow in an end-to-end solution, probably just in the Substrait engine component. It bypasses the need to manage nested registries for UDTs (though these are still needed for UDFs). And its PyArrow part builds on fewer Arrow APIs, probably just the source-node related APIs. OTOH, it also has some cons. It requires a separate source-node per UDT. It does not directly support composing UDFs (say, from a library) with a UDT. And it does not directly support ordering of UDTs within one execution.
The function-executor (my) proposal for UDTs, besides supporting the expression executor feature Weston mentioned, has pretty much the reverse pros and cons. I'll elaborate on the less trivial points about UDT composition and ordering. In the prototype, from Arrow's point of view, a UDT is defined as a function that returns a generator of tabular data. However, from Substrait's point of view, a UDT is modeled like a monad, which abstracts out side-effects. This enables composition of UDTs and UDFs in a single expression (rather than placing each UDT in a separate node), kind of like functions and monads can be composed in a functional programming language. For example, one can consider an expression like a * prng(1) + b * prng(2), where prng(seed) generates a pseudorandom sequence using seed. This expression yields a different value on each evaluation, but the same sequence of values when restarted. While this example is slightly contrived, and it should (and can easily) be extended to tabular data, it is intended for demonstrating composition and ordering with UDTs.

Any idea how to deal with the error in this job: undefined reference to arrow::compute::internal::GenericOptionsType::Serialize(arrow::compute::FunctionOptions const&) const'? My guess is the error is triggered by my recent commit but the fix should be around GenericOptionsType`.

@rtpsw It probably means that the GenericOptionsType class should be marked for export by the DLL

@pitrou, is the API here acceptable, at least in principle? Do you think this PR could go through soon? I have a follow-up PR that depends on the API here and would be easier to handle if the API here were pushed.

@pitrou, is the API here acceptable, at least in principle?

The API looks ok generally, but see question in the comments.

Ping @pitrou - see my response.

I'll note that I didn't take a look at the implementation and tests yet.

I'll note that I didn't take a look at the implementation and tests yet.

Thanks for your comments so far. Since I'm going to be out soon until Thursday, I'll hold for your further comments on implementation and tests.

I'll note that I didn't take a look at the implementation and tests yet.

Thanks for your comments so far. Since I'm going to be out soon until Thursday, I'll hold for your further comments on implementation and tests.

@pitrou, could you take a look?

@rtpsw Probably but our immediate priority is to get the codebase in shape for the impending 10.0.0 release, which explains the delays here. Sorry for that :-(

No problem. I could ping afterwards.

@pitrou, is it a good time to get back to this?

Yes, sorry for the long delay!

OK, I believe I have addressed your remaining comments. Let me know if see anything more.

@pitrou, the CI job's failure copied below seems to need attention.

The reason for the error is that the Arrow function cast is being called with a Table argument whereas arrow::compute::internal::GetFunctionArgumentTypes(...), which is invoked by arrow::compute::<anonymous>::ExecuteInternal and arrow::compute::GetFunctionExecutor, expects array or scalar argument only, as checked by arrow::compute::internal::CheckAllArrayOrScalar(...). However, the current pre-PR Arrow code has the same implementation of arrow::compute::internal::CheckAllArrayOrScalar(...) which is invoked by arrow::compute::<anonymous>::ExecuteInternal before dealing with cast, so one would expect the same error for the current Arrow code. Presumably, the current Arrow code passed CI and the error didn't happen for it. But then, I don't see yet why this PR's code is different. I'd like to understand this before trying to fix.

This is probably because we were returning Status::Invalid before, and we're now returning Status::TypeError.
Returning Status::TypeError is the right thing to do, so we should just change the Python test.

@pitrou, I think I addressed all issues. Let me know if you see anything more.

CI failures are unrelated.

Thanks a lot @rtpsw !
By the way, we have a long PR queue. If you're interested, you might want to start reviewing some of them.


[FFmpegFixupM3u8PP] Fix postprocessing for non-AAC audio codecs

Fixes #6673
Template

Before submitting a pull request make sure you have:

[x] At least skimmed through contributing guidelines including yt-dlp coding conventions
[x] Searched the bugtracker for similar pull requests
[x] Checked the code with flake8 and ran relevant tests

In order to be accepted and merged into yt-dlp each piece of code must be in public domain or released under Unlicense. Check all of the following options that apply:

[x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[ ] Fix or improvement to an extractor (Make sure to add/update tests)
[ ] New extractor (Piracy websites will not be accepted)
[x] Core bug fix/improvement
[ ] New feature (It is strongly recommended to open an issue first)

Do non-aac even have to run the fixup?

Do non-aac even have to run the fixup?

won't the video be be mpegts in mp4 container if we don't fixup?

You are right. I forgot about pre-merged formats


(Closes #28) Get Particle pointer functionality

Codecov Report

Merging #31 (2b4763b) into main (ffe946a) will decrease coverage by 0.27%.
The diff coverage is 50.00%.

@@             Coverage Diff             @@
##              main      #31      +/-   ##
===========================================
- Coverage   100.00%   99.72%   -0.28%
===========================================
  Files           15       15
  Lines         1094     1100       +6
===========================================
+ Hits          1094     1097       +3
- Misses           0        3       +3

Impacted Files
Coverage Δ

src/HartreeParticleDSL/backends/C_AOS/C_AOS.py
99.58% <50.00%> (-0.42%)
:arrow_down:

...c/HartreeParticleDSL/backends/FDPS_backend/FDPS.py
99.54% <50.00%> (-0.46%)
:arrow_down:

...artreeParticleDSL/backends/base_backend/backend.py
97.14% <50.00%> (-2.86%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ffe946a...2b4763b. Read the comment docs.


distModules appears to be broken

Maybe from a Gradle update and we didn't notice, or the modules just go somewhere unexpected locally (Jenkins is fine, but then it only builds with the bundled modules)
Adding a line to log does output the right list of modules at configuration time, but at execution time nothing happens and Gradle insists distModules is UP-TO-DATE
    into("$distsDir/app/modules")
    rootProject.terasologyModules().each {
        println "Working on module " + it.name
        from "$rootDir/modules/${it.name}/build/libs"
        include "*.jar"
    }

Edit: Alternatively it may be moduleJars that's broken, and no module jars are generated in the first place, which would then have it make sense that there's nothing to copy.
gradlew jar seems to cause the modules jars to be built correctly.

Cannot replicate this anymore, at least with the Gradle 6 engine PR. Assuming resolved - both moduleJars and moduleClasses seem to work again, as does distModules (with a caveat: we now have transitive modules required by the embedded modules...)


Clean up resource list params in reducer

Purpose
As we're not caching list responses anymore, we don't need the query key. On the other hand, we do need the current params to modify them as users interact with the filters.
Proposal
Set defaults and clean up APIListCommonRequestParams.
It makes more sense to have them specified and then use Partial<> when we accept incomplete subsets.

@jmaupetit done


Fix httpoxy

https://httpoxy.org/
https://github.com/composer/composer/commit/34553804132ef6291bf2aa1c794a044cc09745c6

Coverage remained the same at 81.556% when pulling 117f68d8d72d4ca75cabad6bcb2bc1bbf6bdb6cc on httpoxy into 250e5fcb07508848c2abf96da84be6da1652ddd8 on master.


qemu: Enable virtio-net vhost by default

Signed-off-by: Samuel Ortiz<EMAIL_ADDRESS>

cc @mcastelino

LGTM

Coverage decreased (-0.02%) to 65.585% when pulling 5bb4196de086c12b60cfca32b4149e91217959b9 on topic/networking into 4e3f56a880420c78ba1e0049e5b42856265bdc82 on master.

lgtm


Python 3.5 final is available.

BTW: I changed the get-pip.py invocation so that we can see its output.  It was failing for a distant reason: https://github.com/ThomasWaldmann/argparse/issues/91   But now we'll be able to see more information from it in any case.

Now  that the pip / argparse thing is fixed, we get a real compiler issue with Python 3.5:
%CMD_IN_ENV% python setup.py nosetests
...
C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\BIN\cl.exe /c /nologo /Ox /W3 /GL /DNDEBUG /MD -IC:\Python35\include -IC:\Python35\include "-IC:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\INCLUDE" "-IC:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\ATLMFC\INCLUDE" "-IC:\Program Files (x86)\Windows Kits\10\include\wdf\ucrt" "-IC:\Program Files (x86)\Windows Kits\NETFXSDK\4.6\include\um" "-IC:\Program Files (x86)\Windows Kits\10\include\wdf\shared" "-IC:\Program Files (x86)\Windows Kits\10\include\wdf\um" "-IC:\Program Files (x86)\Windows Kits\10\include\wdf\winrt" /Tcpyappveyordemo/extension.c /Fobuild\temp.win32-3.5\Release\pyappveyordemo/extension.obj
extension.c
C:\Python35\include\pyconfig.h(68): fatal error C1083: Cannot open include file: 'io.h': No such file or directory
error: command 'C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\BIN\\cl.exe' failed with exit status 2
Command exited with code 1

https://ci.appveyor.com/project/ogrisel/python-appveyor-demo/build/1.0.176/job/tgdhpcpw8jp3jpb5
So the CMD_IN_ENV script is probably not handling properly the final release of 3.5.0 for some reason.

Actually the compiler issue is probably not related to our  CMD_IN_ENV but maybe from the fact that the handling of the vcruntime140.dll by distutils has changed between 3.5.0rc4 and final:
http://stevedower.id.au/blog/building-for-python-3-5-part-two/
However I don't understand how this is related to the lookup of the io.h header file. Maybe this is caused by the fact that several versions of VS are installed concurrently on the appveyor hosts?

I googled a bit but found nothing convincing. @zooba do you have the list of -I flags on a windows building that works on your side? That should help us understand what's wrong in our setup. Where is the io.h supposed to come from?

@nedbat @ogrisel the io.h failure is caused by a bug in WDK (it tramples the ucrt cause there's a sorting bug in one of their damn batch scripts). See this commit for fix/details: https://github.com/ionelmc/python-lazy-object-proxy/commit/ca5e65c35db8fa9b65fc64d0df51a743d831d657#diff-d7c025352b794932ee322a013be90c90R22

Thanks very much @ionelmc this is really helpful. I won't have time to include this workaround in python-appveyor-demo this WE so if someone else want to do it first please feel free to do so.
Otherwise I might work on that next week.

I applied @ionelmc's fix.  Looks good.

Thanks all, this is great. Merging!


Switch Cargo.toml in packages to use workspace dependencies

What was wrong?
Fix #845
How was it fixed?
My process:

Copied the version definitions into the workspace Cargo.toml and referred to them from each package
If multiple versions are used in different packages, specify the highest version to use in the workspace
If different features are used in different packages, specify the minimal subset in the workspace, and add features as needed in each package

There are several dependencies that are only used in a single package. I can see arguments for moving them to the workspace for tracking too. For example, if we don't move the dependencies, then it will be easy to accidentally create duplicates again in the future. But I landed on leaving them in place, because:

It highlights that removing a singular dependency from a package will completely remove it from the whole workspace
It feels a tiny bit burdensome to add every future dependency to the workspace when it's only in use in one place. So I wasn't ready to pick that as the new norm

But I'm open to persuasive arguments :)
To-Do

[x] root
[x] e2store
[x] ethportal-api
[x] ethportal-peertest
[x] light-client
[x] portal-bridge
[x] portalnet
[x] rpc
[x] trin-beacon
[x] trin-execution
[x] trin-history
[x] trin-metrics
[x] trin-state
[x] trin-storage
[x] trin-utils
[x] trin-validation
[x] utp-testing
[x] Clean up commit history and use conventional commits.

Since Cargo.lock wasn't updated, does that mean that there was no dependency that was used with different version?

Yeah, I think because of the regular updates, like this one, most of the locked dependencies were further ahead of the Cargo.toml spec anyway.

Somewhat related, should we create issue(s) for

Sure, I'll take a stab at writing some up 👍🏻


[build-script] Propagate libdispatch-cmake-options

PR #25085 [1] enabled building and installing the static variant of the
libdispatch library in build-script-impl. This broke the
tsan-libdispatch-test preset [2].
Let's make sure we pass along the options specified in
libdispatch-cmake-options when building the static variant.
[1] https://github.com/apple/swift/pull/25085
[2] https://github.com/apple/swift/pull/24330
rdar://problem/49177823

@swift-ci Please test


bug: usePrepareSendTransaction returns error even if enabled: false

Is there an existing issue for this?

[X] I have searched the existing issues

Package Version
0.7.9
Current Behavior
Hello
i just copy example code with enabled:false and got an error
const {error, data} = usePrepareSendTransaction({
    request: {
      to: contract,
      value: utils.parseEther("0"),
    },
    enabled: false,
  });

error code: UNPREDICTABLE_GAS_LIMIT
I know what it's about zero value, but why it's even happened if enabled:false
Expected Behavior
Do not throw any errors if enabled:false
Steps To Reproduce
No response
Link to Minimal Reproducible Example (CodeSandbox, StackBlitz, etc.)
No response
Anything else?
No response

Just tried out the code snippet you shared and was not able to reproduce the issue.  (I substituted a different address from contract since you did not share the value.)
Please provide a minimal reproducible example and reopen this issue.


Script to BLAST antiCRISPR genes against host genome

Download antiCRISPR gene sequences
BLAST against genomes

This can be two functions: the first to download the antiCRISPR genes, and the second to BLAST.
The second function should take an accession number for an organism (i.e. NC_000853) and blast the known antiCRISPR genes, saving the output as XML.
Issue #60 is similar but for spacers - look there for more info!

@aays, this is for you!

I just realized this -- it appears that all the accession numbers for the antiCRISPR genes bring up protein sequences and not nucleotide sequences when searched with Entrez. Would I be using tblastn then to BLAST them against genomic data? Or is there something I'm missing?

@aays good point. I'll ask April (whose lab got these sequences) if she recommends nucleotide or protein blast. If nucleotide, we'll need to get the nucleotide sequences from them as well.
We could try, in the meantime, using blastp (protein blast) on the translated coding regions of each organism. The genbank files (example here) also come with translations.

Issue #70 is linked to a function that, among other things, extracts the protein translations from a genbank file. You could probably re-use some of this! Or even split it into chunks that can be re-used.

Here's the function: PFAM_db.py

This blast syntax should still apply, you'd just have to change db = 'nuccore' to subject = 'bac_genome.fasta'

Got it!

I'm about ready to upload phageblast.py, which addresses the second part of the problem and is more or less ready to go -- however, I keep encountering a 400 Bad Gateway error, which the report indicates has to do with fetching the organism's genome given an accession number in the command line arguments. I'm going to try troubleshooting further after I leave the lab today, but in the meantime do you know what the problem might be?

I'm not sure what that is. What command is giving you the error? Is it blast?
The genome you blast against should already be downloaded from the script's perspective, so you only need to fetch the protein sequences.

Ah, I misunderstood! I included a command to fetch the genome, and that was what kept giving me an error, but if the genome is already downloaded from the script's perspective then that isn't necessary in the first place. I assumed that the function taking an accession number for an organism as input involved the genome being downloaded as part of the script.

I should add that for some reason, using cat  in the bash command kept giving me blank .xml files as output, but switching that to echo  did the trick. I feel like this is a bit of a clumsy workaround, and if that is the case, any advice would be appreciated!

Completed by @aays! :clap:


set arrowOrientation,but coachMarkBodyView in a wrong position

Describe the bug
[  public func coachMarksController(_ coachMarksController: CoachMarksController, coachMarkViewsAt index: Int, madeFrom coachMark: CoachMark) -> (bodyView: CoachMarkBodyView, arrowView: CoachMarkArrowView?) {
var desc = ""
switch index {
case 0:
desc = "点击这里，获得帮助"
case 1:
desc = "相机扫描数独区域，以AR的形式展示数独的答案"
case 2:
desc = "相机扫描数独区域，获得数独的答案"
case 3:
desc = "从相册选择一张数独的截屏或者照片，得到数独答案"
default:
desc = "帮助功能引导"
}
let coachViews = coachMarksController.helper.makeDefaultCoachViews(withArrow: true, arrowOrientation:.top, hintText: desc, nextText: nil)
return (bodyView: coachViews.bodyView, arrowView: coachViews.arrowView)
}]
To Reproduce
[set the arrow orientation to a custom orientation, for example "top", when the target view's position become half bottom of the screen , the arrow orientation is right as you set "top",while the bodyView of the coachMark 's position are wrong ]
Expected behavior
[A clear and concise description of what you expected to happen.]
Screenshots
[

.]
Environment:

Device: [ iPhone X]
iOS version : [ 11.4]

Additional context
[Add any other context about the problem here.]

This bit:
    let coachViews = coachMarksController.helper.makeDefaultCoachViews(withArrow: true, arrowOrientation:.top, hintText: desc, nextText: nil)

doesn't set the orientation. It creates and returns the default views according to the provided parameters.
If you want the coach mark at index 3 to show under the cutout path, you should set:
    coachMark.arrowOrientation = .top

in
    coachMarksController(_:, coachMarkAt:)

In makeDefaultCoachViews(withArrow:, arrowOrientation:, hintText:, nextText:), it's generally a good idea to pass coachMark.arrowOrientation rather than a literal enum. That way you only have to set the orientation once.

arrowOrientation is a bit confusing. I plan to rename it to something like coachMarkPosition, with .top, .bottom, .left and .right positioning the coach mark where expected.

thanks for your help，got it.


[Fix#314]: Fixes sort announcements on table header cells

fixes #314
this fix will make screen readers like NVDA to announce the sort direction when pressing column header cells
checklist:

[x] Resolve conflicts
[x] Unit tests
[x] Manual verification

Great, Here is the link for windows PTE machine: https://rd-htm-pte-3.rdlund.qliktech.com/sense/app/c271b37a-b526-4d2a-b694-cea4b5d0e8fc
please just make sure you change the browser ( for sense-client and sn-table to pick up the language translations ) and nvda ( to announce in the target language ).

I see that nvda says 'space', is it needed?


Simplify code to generate unique emails

https://trello.com/c/wp7WjPN6/693-draft-email-to-send-out-to-checker-subscribers-following-an-announcement
This introduces a new "dedup_by_subscriber" scope as an alternative
to the current "subscription_ids_by_subscriber", and switches bulk
and immediate email generation to use it. In doing this, we simplify
the code to focus on single subscription objects.
Please see the commits for more details.

Thanks for the review @kevindew - hopefully the next people who work on this system will appreciate the simplicity! I've also done a bit of performance testing of this in Integration (bars on the right are with the change). If anything, the time is reduced, which makes sense because there's generally "less stuff" than there was before.

Thanks for the review @kevindew - hopefully the next people who work on this system will appreciate the simplicity! I've also done a bit of performance testing of this in Integration (bars on the right are with the change). If anything, the time is reduced, which makes sense because there's generally "less stuff" than there was before.


Docs/improve readme

The PR improves the documentation by adding the sections: OKP4 Networks, Supported platforms, Releases and Community (now that this repository is public). There's room for improvement, but for now, it seems sufficient to me.

:tada: This PR is included in version 2.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Update requirements in recipe

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

@conda-forge-admin, please rerender

Hi! This is the friendly automated conda-forge-webservice.
I tried to rerender for you, but it looks like there was nothing to do.
This message was generated by GitHub actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/11951190757.

Hi! This is the friendly automated conda-forge-webservice.
I tried to rerender for you, but it looks like there was nothing to do.
This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/11975633061. Examine the logs at this URL for more detail.

Current failure is a bit special.
It doesn't occur in the main oda_api repo tests because there the dispatcher is installed in the environment (it's imported in conftest.py and is used in some tests). And the dispatcher restricts numpy version to be <2.0.0. Then everything works for oda_api. So there are some compatibility issues with the recent numpy, it should be explicitly restricted in the requirements of the main package.
What happens here, is that conftest.py doesn't get copied in the package (but it should, if we include tests), so oda_api in conda doesn't have this implicit dependency (and we definitely don't want the whole conda package to depend on dispatcher. It's not in conda anyway.)
But conftest.py should be in the package if tests are there. Then we need to declare it to be an extra dependency in [test]. And it will be a repo branch as a dependency. It's not being published as a package for a long time.
But then, we should not run tests here, when building the recipe.
@volodymyrss what do you think?

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found some lint.
Here's what I've got...
For recipe/meta.yaml:

❌ requirements: run: numpy < 2.0 should not contain a space between relational operator and the version, i.e. numpy <2.0

For recipe/meta.yaml:

ℹ noarch: python recipes should usually follow the syntax in our documentation for specifying the Python version.

For the host section of the recipe, you should usually use python {{ python_min }} for the python entry.
For the run section of the recipe, you should usually use python >={{ python_min }} for the python entry.
For the test.requires section of the recipe, you should usually use python {{ python_min }} for the python entry.
If the package requires a newer Python version than the currently supported minimum version on conda-forge, you can override the python_min variable by adding a Jinja2 set statement at the top of your recipe (or using an equivalent context variable for v1 recipes).

ℹ PyPI default URL is now pypi.org, and not pypi.io. You may want to update the default source url.

This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12052517766. Examine the logs at this URL for more detail.

@volodymyr this allows to create a conda package of the latest available version


EFS updates (Aug 9, 2016)

http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/ReleaseHistory.html

Thanks!


capabilities of node

Report information about capabilities of node
Signed-off-by: Petr Fedchenkov<EMAIL_ADDRESS>

I added comments and make check to fire one time (or repeat in case of errors).

@rvs this look fine to me now. I think your concerns have been taken care of. Please check.

Welp, looks like this needs rebasing @giggsoff -- if you can do it over the weekend -- that'd be great since we can then pull it into an upcoming release

Rebased.
But seems, tests will fail without https://github.com/lf-edge/eden/pull/587 on current master.

10x! I just pulled the Eden one!


The central slide does not work with the centerMode option

short description of the bug / issue, provide more detail below.
An increase in the central slide using the .slick-center class works when the slider does not have more than 4 elements. When they become more than 5, the slider starts initializing the central class with a jerk. On my jsfiddle it is visually shown. The first slider works fine (it has no more than 4 elements), the second slider does not work (it has more than 4 elements, it works with interruption).
====================================================================

[  paste your jsfiddle link here  ]
https://jsfiddle.net/kc15u84b/1/
====================================================================
Steps to reproduce the problem

...
...

====================================================================
What is the expected behaviour?
...
====================================================================
What is observed behaviour?
...
====================================================================
More Details

Which browsers/versions does it happen on?
Which jQuery/Slick version are you using?
Did this work before?

My pull request #3307 fixes this


How can I get the product image urls in baseline_models/data/il_trajs_finalized_images.jsonl?

hi~ How can I get the image urls of the products in baseline_models/data/il_trajs_finalized_images.jsonl?
I tried to look in the items_shuffle.json, but did not match any using the asin id.

I'll close for now but feel free to open a new one.


abduco/dvtm

Hi, this a great idea. Thank you for making this!
Do you think it would be possible to implement this with abduco and dvtm instead?
In other words, is there something missing from abduco and/or dvtm that tmux has in oder to send to a repl?

Yes. Tmux has a scripting interface, so you can call its commands from outside of the tmux process by executing the tmux binary. For example you can call tmux split from whereever and it will split the currently focused pane in your active tmux session.
This plugin relies in particular on the command tmux send-keys that is executed from vis to simulate keypresses to another terminal.
I'm not very familiar with dvtm, but I don't think it has these functionalities.
Thank you for your interest!


ARTEMIS-1875 Add message address if not set during redistribution

I ran the whole testsuite and this was fine.. making this failure a non issue.
Merging this.


Violin Plot 'growth' logic

Okay, so when the violin plot has just a few plots the current height is fine, but where there's lots of plots it should grow in height so that the plots are 'smooshed'

@brifordwylie we can define the figure height based on the number of rows *
this should work well enough I believe. Unfortunately I don't think we can directly set the dimensions of the subplots in pixels.

@luiztauffer seems good.. there's an internal calculation for the number of rows... so we could just use that to change the figure height... I'm not sure how to change the figure height.. but I'm sure you know :)


add cohere embedding example

Thanks! How about we merge this with https://github.com/pyg-team/pytorch-frame/blob/master/examples/openai_embedding.py, since both are using API?
and rename to text_api_embeddings.py?

Thanks! How about we merge this with https://github.com/pyg-team/pytorch-frame/blob/master/examples/openai_embedding.py, since both are using API? and rename to text_api_embeddings.py?

But I want to put the experiment results we produced yesterday somewhere. Or we can put it in the readme?

Got it, but I think it's cleaner to have well-organized example code according to their functionality. I don't think where you keep results is so important.

Got it, but I think it's cleaner to have well-organized example code according to their functionality. I don't think where you keep results is so important.

Resolved~


Make PropagateExceptions() actually propagate exceptions

Also, using BackgroundService instead of implementing IHostedService from scratch significantly simplifies the SpectreConsoleWorker implementaiton.

Thanks for your contribution! I initially avoided BackgroundService because it used to be slower for some reason but now i cannot reproduce this. Might have been something unrelated ¯_(ツ)_/¯


chore(blockifier): access self.execution_flags instead of passing as args

This change is

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#2491  👈 (View in Graphite)
#2479
#2478
#2470
#2437
#2431
#2429
#2428 : 1 other dependent PR (#2354 )
#2412
#2377
#2331
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Merge activity

Dec 6, 4:37 PM EST: A user started a stack merge that includes this pull request via Graphite.


Migration to cakephp 3.6

Hi Chris
thank you for your plugin: I have recently upgraded cakephp to 3.6 which introduced a lot of deprecation: actually the plugin no longer works:  do you plan to release a compatible cake 3.6 release ?
Thank you again
Rudy

@rudy1976s I will be creating a compatible release in the next few days.

Hi Chris,
I thank you for your plugin too. Just wonder if you still plan to create a compatible release.
Thank your for your answer.
Kitcat

@Kitcat711 I am fixing the travis-ci issues and then a release should be ready :)

@Kitcat711 @rudy1976s I have updated the code to support 3.6
Let me know if you have any issues.


added hint to rebuses.js

Associated Issue: #180
Summary of Changes

hint of "watchman" changed

Pull Request Test Coverage Report for Build 791

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 87.143%

Totals

Change from base Build 514:
0.0%

Covered Lines:
158

Relevant Lines:
180

💛  - Coveralls


Gauge+Taiko usage should be captured

Expected behavior
Gauge+Taiko usage should be captured
Actual behavior
Only OS and language runner details are captured
Steps to replicate

Open a gauge-taiko project.

The analytics data is showing the event as language runner, OS. It does not capture taiko usage.

Version
gauge-core - 1.0.4.nightly-2018-12-14

Blocks #1251

use_test_ga is now being honoured. So you should see some information in the test analytics instance.

This issue was moved to getgauge/gauge-js#180


Timestep interval not always being respected

@joshday I think with the intermediate hook some of addiotional steps are being injected that are not intervals. I could do some post processing on the dataset to strip them out (filter rows using isinteger) but it might better to fix this in the operation itself. Either way works for me.

This was due to the callback and handled in https://github.com/DARPA-ASKEM/simulation-service/pull/94


Delete NuGet.Config

┆Issue is synchronized with this Asana task

Don't we need this for when deploying and using packages locally?

There will be some changes with our nuget. i just follw this task: https://app.asana.com/0/1135578189430322/1136105640340193

Saw the post now, it makes sense. Go for it 👌


Update requirements.txt

Signed-off-by: Gaurav Gupta<EMAIL_ADDRESS>

Codecov Report
Base: 71.51% // Head: 71.51% // No change to project coverage :thumbsup:

Coverage data is based on head (595a768) compared to base (48ef38c).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #324   +/-   ##
=======================================
  Coverage   71.51%   71.51%
=======================================
  Files          26       26
  Lines        3468     3468
=======================================
  Hits         2480     2480
  Misses        988      988

Flag
Coverage Δ

unittests
71.51% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.