Write guidance on how to extend and modify components

What
Add guidance explaining how to correctly extend or modify existing components outside of the options the Design System provides.
Why
We've had a number of queries on our support channels about how to do this, and as long as we're not providing guidance on this, there's a risk that users will do it wrong and may break something.
Further detail
Consideration will need to be given to how we include this information in the Design System. It could be some boilerplate guidance and / or an example on every component page, or it could be a central guide that the component pages link to.
It's probably a good idea to start with one component as an example.
Who needs to know about this
Pete, Hanna / Nick, Dave, Amy
Done when

[x] Session booked with Pete, Dave and Hanna or Nick to draft guidance
[ ] Session has been run
[ ] Guidance drafted
[ ] Amy has reviewed guidance
[ ] Guidance published

I'm very interested in this. Things that I'd like to know about include:

What class names and prefixes should be used. app- or hmcts- or ?
With (1) if our department specific design system does this say with hmcts-button--secondary it seems like it should belong in “styles” as opposed to “components” like this: http://hmcts-design-system.herokuapp.com/styles/secondary-button
If creating a new component that depends on an existing component. For example, I've been looking at creating a currency input for HMCTS. And I'm wrestling with the following options:

a) to depend on the text input component and override bits of it.
b) to duplicate the underlying macro/html and try and keep the params for both currency input and text input the same.

Frankie: "It'd be helpful, at some point (not immediately) to have some guidance on good and bad names for components. E.g generic names like 'banner' or 'hero' might not be as descriptive as 'version-history' or 'bar-chart'?"
Something to think about in the future...


[SAGE-765] - fix(sage-react): input was using an invalid prop 'inputType'

Prop should have been 'type'
Description
It was called out that the React component Input was raising a warning about an invalid prop name inputType.
Also took the liberty to fix a couple of other small hanging fruits.

Hero, propType.sizes
suppressDefaultClass warning should go away
Storybook, fix input not responding to keyboard input

Screenshots

Before
After

Testing in sage-lib

Navigate to Storybook input-email...here
Enter an invalid value and you should be greeted with a tooltip similar to the one below.

Should not see any warnings related to Hero or suppressDefaultClass in the console.

Fix looks good. 🙌
Not a blocker but what do you think about moving the quotation fixes (unrelated to this?) to a different PR?

@philschanely Thanks, the quotations are an artifact of the deprecation changes for the import statement. Based on my eslint and prettier configs is what changed the single to double quotes. <- Knowledge sharing not justifying.
The main change for those were going from '@storybook/addon-docs/blocks' to "@storybook/addon-docs".

@philschanely Took your advice and removed all unrelated changes. I will create a separate PR to remove warning and deprecations.


Add multi-tenancy guide

Hmm sorry, not sure what happened here, I've updated the guide but it just pushed master. I've opened #195 with your commit and my updates to the guide. Thanks!


calculation of standardized anomalies

responsible: @mdaber, @konradmayer, @tjurlina

as at least a trend component is expected to be present after internal discussions it was decided to

first do a gridpoint-wise classical timeseries decomposition into trend, seasonality (covering doy and hour variation) as well as residuals
calculate a climatology (#2) on the residuals for each doy and hour
calculate standardized anomalies

timeseries decomposition may be done via seasonal_decompose from the package  statsmodels in python applied to dask arrays.

as we habe diurnal and annual seasonality included using MSTL from statsmodels should be considered

reopening here as the residuals still need to be computed for the test data

residuals are now also available for test data


Repo sync for protected CLA branch

The pull request is created from master637388994018651992 to master to fix git push error for protected CLA branch

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


django 1.8, 1.9 support and remove support less then 1.7

Hi there,
is this package still maintained @bradleyayers? Afaik there is a fork which works with 1.6 only (which I have used with some modifications) here https://github.com/nyaruka/django-celery-transactions. But for 1.7 upwards there is no real solution, yet. As mentioned here https://github.com/aaugustin/django-transaction-signals this could be implemented via django-transaction-hooks (https://github.com/carljm/django-transaction-hooks) for django 1.7 - 1.8 and the native transactions.on_commit hook in django >= 1.9. I would happily be part of starting this implementation. Is there anyone who would be willing to join in? Should this be started as a new package?
Regards
Jakob


Update Composer dependencies (2024-01-22-00-17)

Visual regression test passed!
View the visual regression test report


[Bug] transport: Error while dialing: dial tcp <IP_ADDRESS>:9090

Search before asking

[X] I had searched in the issues and found no similar issues.

Version
Doris v 2.1.3
python package:
adbc-driver-flightsql     1.0.0
pydoris                   <IP_ADDRESS>
pydoris-client            1.0.4
What's Wrong?
OperationalError: IO: [FlightSQL] connection error: desc = "transport: Error while dialing: dial tcp <IP_ADDRESS>:9090: connectex: No connection could be made because the target machine actively refused it." (Unavailable; DoGet: endpoint 0: [uri:"grpc+tcp://<IP_ADDRESS>:9090"])
possible related issue:
fix Fix Arrow Flight bind wrong Host in Fqdn #34850
'### What You Expected?
'## 1
'##################
dbapi_adbc_execute_fetchallarrow, cost:0:00:00.033296, bytes:101, len(arrow_data):6
'## 2
<class 'pandas.core.frame.DataFrame'>
RangeIndex: 6 entries, 0 to 5
Data columns (total 1 columns):
'#   Column    Non-Null Count  Dtype

0   Database  6 non-null      object
dtypes: object(1)
memory usage: 547.0 bytes
None
'## 3
Database
0    __internal_schema
1     arrow_flight_sql
2   information_schema
3                mysql
4  pydoris_client_test
How to Reproduce?
Run python script remotely (not in the same vm as doris be'):
import adbc_driver_manager
import adbc_driver_flightsql.dbapi as flight_sql
import pandas
from datetime import datetime
#import pyarrow as pa
#import pyarrow.flight as fl

conn = flight_sql.connect(uri="grpc://x.x.x.x:9090", db_kwargs={
            adbc_driver_manager.DatabaseOptions.USERNAME.value: "root",
            adbc_driver_manager.DatabaseOptions.PASSWORD.value: ""
        },
        autocommit=False
)
cursor = conn.cursor()

#cursor.execute("DROP DATABASE IF EXISTS arrow_flight_sql FORCE;")
#cursor.execute("select now();")
cursor.execute("show databases;")

start_time = datetime.now()
arrow_data = cursor.fetchallarrow()
dataframe = arrow_data.to_pandas()

print("## 1")
print("\n##################\n dbapi_adbc_execute_fetchallarrow" +
      ", cost:" + str(datetime.now() - start_time) +
      ", bytes:" + str(arrow_data.nbytes) +
      ", len(arrow_data):" + str(len(arrow_data))
)
print("## 2")
print(dataframe.info(memory_usage='deep'))
print("## 3")
print(dataframe)

Anything Else?
The tcp packets captured by wireshark show:
The doris be server return 'grpc+tcp://<IP_ADDRESS>:9090' to client. This could be the reason why client is trying to connect the endpoint: <IP_ADDRESS>:9090
No response
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Hi,
+1 I'm also facing the same issue, were you able to figure out what the problem is / fix is ?

Hi @zhaopinglu @drreddy

check Doris BE version and upgrade it to 2.1.3-rc08 or above, in 2.1.3-rc08 fix #34850.
use FE host to connect, //host:9090
show the results of show frontends; and show backends;
do you use fqdn?

Hi @xinyiZzz
We've upgraded our cluster to doris-2.1.4-rc03-e93678fd1e and retried the same, we are still facing the same issue. We are not using fqdn anywhere.

Hi @xinyiZzz
We've upgraded our cluster to doris-2.1.4-rc03-e93678fd1e and retried the same, we are still facing the same issue. We are not using fqdn anywhere.

If you could provide the following information, It would be helpful to analyze this issue.

show frontends; execution results
show backends; execution results
fe.log partial log of query from start to end.
be.INFO partial log of query from start to end.

Hi @xinyiZzz
PFB the responses for the queries:

show frontends output:
mysql> show frontends\G *************************** 1. row ***************************            Name: fe_584773d2_b483_446a_bad8_040765483c48            Host: <IP_ADDRESS>     EditLogPort: 9010        HttpPort: 8030       QueryPort: 9030         RpcPort: 9020 ArrowFlightSqlPort: 9090            Role: FOLLOWER        IsMaster: true       ClusterId: 339655541            Join: true           Alive: true ReplayedJournalId: 169718   LastStartTime: 2024-07-02 10:46:27   LastHeartbeat: 2024-07-03 06:21:23        IsHelper: true          ErrMsg:         Version: doris-2.1.4-rc03-e93678fd1e CurrentConnected: Yes

Show backends output
mysql> show backends\G *************************** 1. row ***************************            BackendId: 13058                 Host: <IP_ADDRESS>        HeartbeatPort: 9050               BePort: 9060             HttpPort: 8040             BrpcPort: 8060   ArrowFlightSqlPort: 9091        LastStartTime: 2024-07-02 10:46:58        LastHeartbeat: 2024-07-03 06:21:13                Alive: true SystemDecommissioned: false            TabletNum: 3645     DataUsedCapacity: 789.687 MB    TrashUsedCapacity: 1.845 GB        AvailCapacity: 124.288 GB        TotalCapacity: 127.936 GB              UsedPct: 2.85 %       MaxDiskUsedPct: 2.85 %   RemoteUsedCapacity: 0.000                  Tag: {"location" : "default"}               ErrMsg:              Version: doris-2.1.4-rc03-e93678fd1e               Status: {"lastSuccessReportTabletsTime":"2024-07-03 06:21:08","lastStreamLoadTime":-1,"isQueryDisabled":false,"isLoadDisabled":false} HeartbeatFailureCounter: 0             NodeRole: mix *************************** 2. row ***************************            BackendId: 13059                 Host: <IP_ADDRESS>        HeartbeatPort: 9050               BePort: 9060             HttpPort: 8040             BrpcPort: 8060   ArrowFlightSqlPort: 9091        LastStartTime: 2024-07-02 10:47:24        LastHeartbeat: 2024-07-03 06:21:13                Alive: true SystemDecommissioned: false            TabletNum: 3779     DataUsedCapacity: 3.440 GB    TrashUsedCapacity: 245.602 MB        AvailCapacity: 123.218 GB        TotalCapacity: 127.936 GB              UsedPct: 3.69 %       MaxDiskUsedPct: 3.69 %   RemoteUsedCapacity: 0.000                  Tag: {"location" : "default"}               ErrMsg:              Version: doris-2.1.4-rc03-e93678fd1e               Status: {"lastSuccessReportTabletsTime":"2024-07-03 06:20:47","lastStreamLoadTime":-1,"isQueryDisabled":false,"isLoadDisabled":false} HeartbeatFailureCounter: 0             NodeRole: mix *************************** 3. row ***************************            BackendId: 62290                 Host: <IP_ADDRESS>        HeartbeatPort: 9050               BePort: 9060             HttpPort: 8040             BrpcPort: 8060   ArrowFlightSqlPort: 9091        LastStartTime: 2024-07-02 10:47:54        LastHeartbeat: 2024-07-03 06:21:13                Alive: true SystemDecommissioned: false            TabletNum: 3777     DataUsedCapacity: 3.283 GB    TrashUsedCapacity: 488.622 MB        AvailCapacity: 123.146 GB        TotalCapacity: 127.936 GB              UsedPct: 3.74 %       MaxDiskUsedPct: 3.74 %   RemoteUsedCapacity: 0.000                  Tag: {"location" : "default"}               ErrMsg:              Version: doris-2.1.4-rc03-e93678fd1e               Status: {"lastSuccessReportTabletsTime":"2024-07-03 06:21:03","lastStreamLoadTime":-1,"isQueryDisabled":false,"isLoadDisabled":false} HeartbeatFailureCounter: 0             NodeRole: mix

w.r.t the logs I'm not sure for which query you want the log for ?? Also I've have never handled doris logs, could you guide me on how to get the specific logs for a query.

2.1.4-rc03

i also use doris-version:2.1.4-rc03.  Have you solved the problem? I have the same problem as you.

Same issue using doris-2.1.5-rc02. However, the ADBC connection works with doris-2.1.2-rc04 with the same configuration.

@denniskyleung @zhaopinglu @chengxin1374 @drreddy
Fixed in https://github.com/apache/doris/pull/40002, sorry for taking so long.
This problem occurs when query results are returned from FE Arrow Flight server, such as show tables;, show databases;. no problem when query results are returned from BE Arrow Flight server, such as the normal query statement select * from xxx.


Lack of Documentation

Please make documentation for it, otherwise it's totally useless.
There's no point in downloading it if we can't use it.
CurseForge

https://github.com/DaedalusGame/Modular-Diversity/wiki
Probably done, unless there's something left unclear by that.


--wish-specs not useful without the add of --wish-includes

--wish-specs at the moment finds and imports the top level modules of the listed distributions.
Contrary to what happens when --wish-modules is given it is made no attempt to set a sensible default to --wish-includes. A sensible default could be the list of all distributions top level modules but we don't collect this list at the moment.
The user is required to work-around this limitation by explicitly adding --wish-includes.

The plan is to add the top level module found from the specs to the modules passes to the command line and then call `ìmport_modules`` only once.


Code consulting

I see your code , There is such a “object EngineCallback” in your code。
What does this class do? Can you share his design ideas？
Looking forward to your reply！

This object is used for callback.
when enginemanager started a new engine, the new engine will use RPC to callback some message to enginemanager.
This object will serialize the access information of enginemanager, and pass to the engine by java args, so engine can use it to instance a RPC connection.


Fri, 30 Jun 2017 22:56:26 GMT EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP Response is finished
Fri, 30 Jun 2017 22:56:26 GMT EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP request: /characteristics?id=11.9
Fri, 30 Jun 2017 22:56:26 GMT HAPServer [23:D6:0D:63:EF:12] HAP Request: GET /characteristics?id=11.9
Fri, 30 Jun 2017 22:56:26 GMT Accessory [Jeedom_Repaired_e2] Getting value for Characteristic "Current Position"
Fri, 30 Jun 2017 22:56:26 GMT Accessory [Jeedom_Repaired_e2] Got Characteristic "Current Position" value: 0
Fri, 30 Jun 2017 22:56:26 GMT EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP Response is finished
Fri, 30 Jun 2017 22:56:26 GMT EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP request: /characteristics?id=7.9
Fri, 30 Jun 2017 22:56:26 GMT HAPServer [23:D6:0D:63:EF:12] HAP Request: GET /characteristics?id=7.9
Fri, 30 Jun 2017 22:56:26 GMT Accessory [Jeedom_Repaired_e2] Getting value for Characteristic "Security System Current State"
Fri, 30 Jun 2017 22:56:26 GMT Accessory [Jeedom_Repaired_e2] Got Characteristic "Security System Current State" value: 4
Fri, 30 Jun 2017 22:56:26 GMT EventedHTTPServer [::ffff:<IP_ADDRESS>] Muting event '7.9' notification for this connection since it originated here.
Fri, 30 Jun 2017 22:56:26 GMT EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP Response is finished
Fri, 30 Jun 2017 22:56:26 GMT EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP request: /characteristics?id=5.9
Fri, 30 Jun 2017 22:56:26 GMT HAPServer [23:D6:0D:63:EF:12] HAP Request: GET /characteristics?id=5.9
Fri, 30 Jun 2017 22:56:26 GMT Accessory [Jeedom_Repaired_e2] Getting value for Characteristic "Current Door State"
Fri, 30 Jun 2017 22:56:26 GMT Accessory [Jeedom_Repaired_e2] Got Characteristic "Current Door State" value: 1
Fri, 30 Jun 2017 22:56:26 GMT EventedHTTPServer [::ffff:<IP_ADDRESS>] Muting event '5.9' notification for this connection since it originated here.
Fri, 30 Jun 2017 22:56:26 GMT EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP Response is finished
Fri, 30 Jun 2017 22:56:26 GMT EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP request: /characteristics?id=5.11
Fri, 30 Jun 2017 22:56:26 GMT HAPServer [23:D6:0D:63:EF:12] HAP Request: GET /characteristics?id=5.11
Fri, 30 Jun 2017 22:56:26 GMT Accessory [Jeedom_Repaired_e2] Getting value for Characteristic "Obstruction Detected"
Fri, 30 Jun 2017 22:56:26 GMT Accessory [Jeedom_Repaired_e2] Got Characteristic "Obstruction Detected" value: false
Fri, 30 Jun 2017 22:56:26 GMT EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP Response is finished
Fri, 30 Jun 2017 22:56:26 GMT EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP request: /characteristics?id=2.9
Fri, 30 Jun 2017 22:56:26 GMT HAPServer [23:D6:0D:63:EF:12] HAP Request: GET /characteristics?id=2.9
Fri, 30 Jun 2017 22:56:26 GMT Accessory [Jeedom_Repaired_e2] Getting value for Characteristic "Current Temperature"
Fri, 30 Jun 2017 22:56:26 GMT Accessory [Jeedom_Repaired_e2] Got Characteristic "Current Temperature" value: 22.49
Fri, 30 Jun 2017 22:56:26 GMT EventedHTTPServer [::ffff:<IP_ADDRESS>] Muting event '2.9' notification for this connection since it originated here.
Fri, 30 Jun 2017 22:56:26 GMT EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP Response is finished
Fri, 30 Jun 2017 22:56:26 GMT EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP request: /characteristics?id=2.12
Fri, 30 Jun 2017 22:56:26 GMT HAPServer [23:D6:0D:63:EF:12] HAP Request: GET /characteristics?id=2.12
Fri, 30 Jun 2017 22:56:26 GMT Accessory [Jeedom_Repaired_e2] Getting value for Characteristic "Current Relative Humidity"
Fri, 30 Jun 2017 22:56:26 GMT Accessory [Jeedom_Repaired_e2] Got Characteristic "Current Relative Humidity" value: 61
Fri, 30 Jun 2017 22:56:26 GMT EventedHTTPServer [::ffff:<IP_ADDRESS>] Muting event '2.12' notification for this connection since it originated here.
Fri, 30 Jun 2017 22:56:26 GMT EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP Response is finished
Fri, 30 Jun 2017 22:56:26 GMT EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP request: /characteristics?id=3.9
Fri, 30 Jun 2017 22:56:26 GMT HAPServer [23:D6:0D:63:EF:12] HAP Request: GET /characteristics?id=3.9
Fri, 30 Jun 2017 22:56:26 GMT Accessory [Jeedom_Repaired_e2] Getting value for Characteristic "Current Temperature"
Fri, 30 Jun 2017 22:56:26 GMT Accessory [Jeedom_Repaired_e2] Got Characteristic "Current Temperature" value: 21.39
Fri, 30 Jun 2017 22:56:26 GMT EventedHTTPServer [::ffff:<IP_ADDRESS>] Muting event '3.9' notification for this connection since it originated here.
Fri, 30 Jun 2017 22:56:26 GMT EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP Response is finished
Fri, 30 Jun 2017 22:56:26 GMT EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP request: /characteristics?id=3.12
Fri, 30 Jun 2017 22:56:26 GMT HAPServer [23:D6:0D:63:EF:12] HAP Request: GET /characteristics?id=3.12
Fri, 30 Jun 2017 22:56:26 GMT Accessory [Jeedom_Repaired_e2] Getting value for Characteristic "Current Relative Humidity"
Fri, 30 Jun 2017 22:56:26 GMT Accessory [Jeedom_Repaired_e2] Got Characteristic "Current Relative Humidity" value: 59
Fri, 30 Jun 2017 22:56:26 GMT EventedHTTPServer [::ffff:<IP_ADDRESS>] Muting event '3.12' notification for this connection since it originated here.
Fri, 30 Jun 2017 22:56:26 GMT EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP Response is finished
Fri, 30 Jun 2017 22:56:26 GMT EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP request: /characteristics?id=9.12
Fri, 30 Jun 2017 22:56:26 GMT HAPServer [23:D6:0D:63:EF:12] HAP Request: GET /characteristics?id=9.12
Fri, 30 Jun 2017 22:56:26 GMT Accessory [Jeedom_Repaired_e2] Getting value for Characteristic "Current Relative Humidity"
Fri, 30 Jun 2017 22:56:26 GMT Accessory [Jeedom_Repaired_e2] Got Characteristic "Current Relative Humidity" value: 62
Fri, 30 Jun 2017 22:56:26 GMT EventedHTTPServer [::ffff:<IP_ADDRESS>] Muting event '9.12' notification for this connection since it originated here.
Fri, 30 Jun 2017 22:56:26 GMT EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP Response is finished
Fri, 30 Jun 2017 22:56:26 GMT EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP request: /characteristics?id=9.9
Fri, 30 Jun 2017 22:56:26 GMT HAPServer [23:D6:0D:63:EF:12] HAP Request: GET /characteristics?id=9.9
Fri, 30 Jun 2017 22:56:26 GMT Accessory [Jeedom_Repaired_e2] Getting value for Characteristic "Current Temperature"
Fri, 30 Jun 2017 22:56:26 GMT Accessory [Jeedom_Repaired_e2] Got Characteristic "Current Temperature" value: 22.18
Fri, 30 Jun 2017 22:56:26 GMT EventedHTTPServer [::ffff:<IP_ADDRESS>] Muting event '9.9' notification for this connection since it originated here.
Fri, 30 Jun 2017 22:56:26 GMT EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP Response is finished
Fri, 30 Jun 2017 22:56:26 GMT EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP request: /characteristics?id=12.9
Fri, 30 Jun 2017 22:56:26 GMT HAPServer [23:D6:0D:63:EF:12] HAP Request: GET /characteristics?id=12.9
Fri, 30 Jun 2017 22:56:26 GMT Accessory [Jeedom_Repaired_e2] Getting value for Characteristic "On"
Fri, 30 Jun 2017 22:56:26 GMT Accessory [Jeedom_Repaired_e2] Got Characteristic "On" value: true
Fri, 30 Jun 2017 22:56:26 GMT EventedHTTPServer [::ffff:<IP_ADDRESS>] Muting event '12.9' notification for this connection since it originated here.
Fri, 30 Jun 2017 22:56:26 GMT EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP Response is finished
Fri, 30 Jun 2017 22:56:27 GMT EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP request: /characteristics?id=12.14
Fri, 30 Jun 2017 22:56:27 GMT HAPServer [23:D6:0D:63:EF:12] HAP Request: GET /characteristics?id=12.14
Fri, 30 Jun 2017 22:56:27 GMT Accessory [Jeedom_Repaired_e2] Getting value for Characteristic "Hue"
Fri, 30 Jun 2017 22:56:27 GMT Accessory [Jeedom_Repaired_e2] Got Characteristic "Hue" value: 136
Fri, 30 Jun 2017 22:56:27 GMT EventedHTTPServer [::ffff:<IP_ADDRESS>] Muting event '12.14' notification for this connection since it originated here.
Fri, 30 Jun 2017 22:56:27 GMT EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP Response is finished
Fri, 30 Jun 2017 22:56:27 GMT EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP request: /characteristics?id=12.12
Fri, 30 Jun 2017 22:56:27 GMT HAPServer [23:D6:0D:63:EF:12] HAP Request: GET /characteristics?id=12.12
Fri, 30 Jun 2017 22:56:27 GMT Accessory [Jeedom_Repaired_e2] Getting value for Characteristic "On"
Fri, 30 Jun 2017 22:56:27 GMT Accessory [Jeedom_Repaired_e2] Got Characteristic "On" value: false
Fri, 30 Jun 2017 22:56:27 GMT EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP Response is finished
Fri, 30 Jun 2017 22:56:27 GMT EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP request: /characteristics?id=12.13
Fri, 30 Jun 2017 22:56:27 GMT HAPServer [23:D6:0D:63:EF:12] HAP Request: GET /characteristics?id=12.13
Fri, 30 Jun 2017 22:56:27 GMT Accessory [Jeedom_Repaired_e2] Getting value for Characteristic "Brightness"
Fri, 30 Jun 2017 22:56:27 GMT Accessory [Jeedom_Repaired_e2] Got Characteristic "Brightness" value: 38
Fri, 30 Jun 2017 22:56:27 GMT EventedHTTPServer [::ffff:<IP_ADDRESS>] Muting event '12.13' notification for this connection since it originated here.
Fri, 30 Jun 2017 22:56:27 GMT EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP Response is finished
Fri, 30 Jun 2017 22:56:27 GMT EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP request: /characteristics?id=12.15
Fri, 30 Jun 2017 22:56:27 GMT HAPServer [23:D6:0D:63:EF:12] HAP Request: GET /characteristics?id=12.15
Fri, 30 Jun 2017 22:56:27 GMT Accessory [Jeedom_Repaired_e2] Getting value for Characteristic "Saturation"
Fri, 30 Jun 2017 22:56:27 GMT Accessory [Jeedom_Repaired_e2] Got Characteristic "Saturation" value: 38
Fri, 30 Jun 2017 22:56:27 GMT EventedHTTPServer [::ffff:<IP_ADDRESS>] Muting event '12.15' notification for this connection since it originated here.
Fri, 30 Jun 2017 22:56:27 GMT EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP Response is finished
Fri, 30 Jun 2017 22:56:27 GMT EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP request: /characteristics?id=6.19
Fri, 30 Jun 2017 22:56:27 GMT HAPServer [23:D6:0D:63:EF:12] HAP Request: GET /characteristics?id=6.19
Fri, 30 Jun 2017 22:56:27 GMT Accessory [Jeedom_Repaired_e2] Getting value for Characteristic "Current Ambient Light Level"
Fri, 30 Jun 2017 22:56:27 GMT Accessory [Jeedom_Repaired_e2] Got Characteristic "Current Ambient Light Level" value: 44
Fri, 30 Jun 2017 22:56:27 GMT EventedHTTPServer [::ffff:<IP_ADDRESS>] Muting event '6.19' notification for this connection since it originated here.
Fri, 30 Jun 2017 22:56:27 GMT EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP Response is finished
Fri, 30 Jun 2017 22:56:27 GMT EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP request: /characteristics?id=6.10
Fri, 30 Jun 2017 22:56:27 GMT HAPServer [23:D6:0D:63:EF:12] HAP Request: GET /characteristics?id=6.10
Fri, 30 Jun 2017 22:56:27 GMT Accessory [Jeedom_Repaired_e2] Getting value for Characteristic "Brightness"
Fri, 30 Jun 2017 22:56:27 GMT Accessory [Jeedom_Repaired_e2] Got Characteristic "Brightness" value: 80
Fri, 30 Jun 2017 22:56:27 GMT EventedHTTPServer [::ffff:<IP_ADDRESS>] Muting event '6.10' notification for this connection since it originated here.
Fri, 30 Jun 2017 22:56:27 GMT EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP Response is finished
Fri, 30 Jun 2017 22:56:27 GMT EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP request: /characteristics?id=6.11
Fri, 30 Jun 2017 22:56:27 GMT HAPServer [23:D6:0D:63:EF:12] HAP Request: GET /characteristics?id=6.11
Fri, 30 Jun 2017 22:56:27 GMT Accessory [Jeedom_Repaired_e2] Getting value for Characteristic "Hue"
Fri, 30 Jun 2017 22:56:27 GMT Accessory [Jeedom_Repaired_e2] Got Characteristic "Hue" value: 18
Fri, 30 Jun 2017 22:56:27 GMT EventedHTTPServer [::ffff:<IP_ADDRESS>] Muting event '6.11' notification for this connection since it originated here.
Fri, 30 Jun 2017 22:56:27 GMT EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP Response is finished
Fri, 30 Jun 2017 22:56:28 GMT EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP request: /characteristics?id=6.12
Fri, 30 Jun 2017 22:56:28 GMT HAPServer [23:D6:0D:63:EF:12] HAP Request: GET /characteristics?id=6.12
Fri, 30 Jun 2017 22:56:28 GMT Accessory [Jeedom_Repaired_e2] Getting value for Characteristic "Saturation"
Fri, 30 Jun 2017 22:56:28 GMT Accessory [Jeedom_Repaired_e2] Got Characteristic "Saturation" value: 80
Fri, 30 Jun 2017 22:56:28 GMT EventedHTTPServer [::ffff:<IP_ADDRESS>] Muting event '6.12' notification for this connection since it originated here.

*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see <http://0pointer.de/avahi-compat?s=libdns_sd&e=nodejs&f=DNSServiceRegister>
WARNING : IPv6 est activé sur votre système, il peut poser problème avec Homebridge
[7/1/2017, 12:58:50 AM] Loaded plugin: homebridge-camera-ffmpeg
[7/1/2017, 12:58:50 AM] Registering platform 'homebridge-camera-ffmpeg.Camera-ffmpeg'
[7/1/2017, 12:58:50 AM] ---
[7/1/2017, 12:58:50 AM] Loaded plugin: homebridge-jeedom
[7/1/2017, 12:58:50 AM] Registering platform 'homebridge-jeedom.Jeedom'
[7/1/2017, 12:58:50 AM] ---
[7/1/2017, 12:58:50 AM] Loaded config.json with 0 accessories and 1 platforms.
[7/1/2017, 12:58:50 AM] ---
[7/1/2017, 12:58:50 AM] Loading 1 platforms...
Load homebridge-camera-ffmpeg.Camera-ffmpeg
Scan this code with your HomeKit App on your iOS device to pair with Homebridge:
┌────────────┐
│ 031-45-154 │
└────────────┘
Fri, 30 Jun 2017 22:58:51 GMT EventedHTTPServer Server listening on port 51826
[7/1/2017, 12:58:51 AM] Homebridge is running on port 51826.
Fri, 30 Jun 2017 23:02:44 GMT EventedHTTPServer [::ffff:<IP_ADDRESS>] New connection from client
Fri, 30 Jun 2017 23:02:44 GMT EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP server listening on port 37047
----- ADDING ALL MY ACCESSORIES DYNAMICALLY-------
Fri, 30 Jun 2017 23:02:44 GMT EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP request: /pair-verify
Fri, 30 Jun 2017 23:02:44 GMT HAPServer [23:D6:0D:63:EF:12] HAP Request: POST /pair-verify
Fri, 30 Jun 2017 23:02:44 GMT HAPServer [23:D6:0D:63:EF:12] Pair verify step 1/2
Fri, 30 Jun 2017 23:02:44 GMT EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP Response is finished
Fri, 30 Jun 2017 23:02:44 GMT EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP request: /pair-verify
Fri, 30 Jun 2017 23:02:44 GMT HAPServer [23:D6:0D:63:EF:12] HAP Request: POST /pair-verify
Fri, 30 Jun 2017 23:02:44 GMT HAPServer [23:D6:0D:63:EF:12] Pair verify step 2/2
Fri, 30 Jun 2017 23:02:44 GMT HAPServer [23:D6:0D:63:EF:12] Client 33A44D85-9086-44D8-8A05-089CFF2AB6D5 verification complete
Fri, 30 Jun 2017 23:02:44 GMT EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP Response is finished
Fri, 30 Jun 2017 23:02:44 GMT EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP request: /accessories
Fri, 30 Jun 2017 23:02:44 GMT HAPServer [23:D6:0D:63:EF:12] HAP Request: GET /accessories
Fri, 30 Jun 2017 23:02:44 GMT EventedHTTPServer [::ffff:<IP_ADDRESS>] HTTP Response is finished
Fri, 30 Jun 2017 23:08:51 GMT EventedHTTPServer [::ffff:<IP_ADDRESS>] Sending HTTP event 'keepalive' with data: {"characteristics":[]}
Fri, 30 Jun 2017 23:08:51 GMT EventedHTTPServer [::ffff:<IP_ADDRESS>] Sending HTTP event 'keepalive' with data: {"characteristics":[]}

and that's all... when i refresh in Eve app, all characteristics have the exclamation mark. and no more logs (except the keepalive)
after that, the sole solution is to delete persist and accessores, change the username and the name of the bridge (and even restart avahi-daemon who is in "registering" instead of "running").
<IP_ADDRESS> is my iphone
<IP_ADDRESS> is my appleTV 4
do you have any lead ? Idea or anything

Dears,
i have sanitized all the data i send to homebridge and i have less error but sometimes it still happens...
here is the sanitization :
function sanitizeValue(currentValue,characteristic) {
	let val=0;
	switch(characteristic.props.format) {
			case "uint8" :
			case "uint16":
			case "uint32" :
			case "uint64" :
				val = parseInt(currentValue);
				if(val == undefined || val == null || isNaN(val)) val = 0;
				val = Math.abs(val); // unsigned
			break;
			case "int" :
				val = parseInt(currentValue);
				if(val == undefined || val == null || isNaN(val)) val = 0;
			break;
			case "float" :
				val = minStepRound(parseFloat(currentValue),characteristic);
				if(val == undefined || val == null || isNaN(val)) val = 0;
			break;
			case "bool" :
				val = toBool(currentValue);
			break;
			case "string" :
			case "tlv8" :
				val = currentValue;
				if(val == undefined || val == null) val = '';
				val = val.toString();
			break;
	}
	if(characteristic.props.minValue != null && characteristic.props.minValue != undefined && val < characteristic.props.minValue) val = characteristic.props.minValue;
	if(characteristic.props.maxValue != null && characteristic.props.maxValue != undefined && val > characteristic.props.maxValue) val = characteristic.props.maxValue;
	return val;
}
function minStepRound(val,characteristic) {
	if(characteristic.props.minStep == null || characteristic.props.minStep == undefined) {
		characteristic.props.minStep = 1;
	}
	let prec = (characteristic.props.minStep.toString().split('.')[1] || []).length;
	val = val * Math.pow(10, prec);
	val = Math.round(val); // round to the minStep precision
	val = val / Math.pow(10, prec);
	return val;
}

any review ?

Just my two cents:

there are characteristics with a fixed value list
check your minStepRound() with all Step values that might occur, I had some trouble with node's implementation of float arithmetics: v/(1/step) != v*step ...

thank you for your reply

do you know how I could verify that ? I've found props.validValues & props.validValueRanges in the code would it help ? does it contains those values ?
I didn't found any step like 0.2 in official Characteristics (I do have control on the characteristics used, so no customs other than the ones I choose)


Network Morphism - Deepening a layer

Hi,
I have a query related to deepening operation in the project. After going through the implementation for deepening a network, I found that the approach is the one defined in Net2Net Paper rather than Network Morphism Paper. Is the deepening operation based on Network Morphism Paper or Net2Net Paper ?

Yes, the deeper operation and wider operation is similar to the implementation in Net2Net.


receive: Create proposal for backfiling on remote write

As per our discussion here we decided to enable Remote Write backfilling.
Thoughts so far:

Use cases: Lagging behind clusters (currently only 2h  is allowed, same with Cortex), clock skew for clusters, forgotten metrics, a batch job with old dataset, monitoring remote site. Artificial data.
Something inefficient for a start is ok. We can aim for rare cases only. Someday as something continuous.
Easiest would be to just open new TSDB on this case.

Help wanted, but the topic is extremely difficult. The design must-have apriori.
cc @gouthamve @pracucci  @brancz @richiH, @tomwilkie @squat

This use case is very important for us since even some normal amount of upstream metrics batch ingest will easily result in metrics with over an hour but within 2 hours of lag. The linked discussion in Cortex is very helpful, but ultimately doesn't help until it is implemented here in Thanos :)

This has also been discussed at the Prometheus dev summit. Once Prometheus implements it, we should probably follow the same strategy in Thanos. I believe it's unlikely that that will happen in the receive component, but that's a detail I believe.

Hello. Not quite sure if this issue is exactly the right one, but coming from https://github.com/thanos-io/thanos/issues/2490 I have an use case. Please tell me, if there is an ticket that fits better.
We are currently implementing an anomaly detection with Thanos. It works well so far, but it is a quite complex query which needs data from up to 4 weeks ago. Due to the complexity it is more readable and has a better performance when reusing calculations by intermediate recording rules. Of course we do not have data from 4 weeks ago yet, because we just started to write the recording rules. Therefore we would need to wait full 4 weeks to be sure that the rules are working properly.
With backfilling we might be able to retrospectively calculate the recording rules and see the result immediately.
Of course we can inline most of the queries and skip the immediate recording rules, but this requires a lot of resources. Also it is impossible, when using a counter which does not have a rate recording rule yet, because something like avg_over_time(rate(foobar[5m])[1w] does not work.

Here is an example rule file:
The version without intermediate recording rules
groups:
  - name: anomaly-detection-1m
    interval: 30s
    rules:
    - record: rule_action:wafsc_evaluations:rate1m:seasonal_prediction
      expr: >
        quantile(0.5,
          label_replace(
            avg_over_time(rule_action:wafsc_evaluations:rate1m[4h] offset 166h)
            + avg_over_time(rule_action:wafsc_evaluations:rate1m[1w])
            - avg_over_time(rule_action:wafsc_evaluations:rate1m[1w] offset 1w)
            , "offset", "1w", "", "")
          or
          label_replace(
            avg_over_time(rule_action:wafsc_evaluations:rate1m[4h] offset 334h)
            + avg_over_time(rule_action:wafsc_evaluations:rate1m[1w])
            - avg_over_time(rule_action:wafsc_evaluations:rate1m[1w] offset 2w)
            , "offset", "2w", "", "")
          or
          label_replace(
            avg_over_time(rule_action:wafsc_evaluations:rate1m[4h] offset 502h)
            + avg_over_time(rule_action:wafsc_evaluations:rate1m[1w])
            - avg_over_time(rule_action:wafsc_evaluations:rate1m[1w] offset 3w)
            , "offset", "3w", "", "")
        ) without (offset)

    - record: rule_action:wafsc_evaluations:rate1m:seasonal_prediction:z_score
      expr: >
        (
          rule_action:wafsc_evaluations:rate1m
          - rule_action:wafsc_evaluations:rate1m:seasonal_prediction
        ) / stddev_over_time(rule_action:wafsc_evaluations:rate1m[1w])

The optimized version
groups:
  - name: anomaly-detection-1m
    interval: 30s
    rules:
    - record: rule_action:wafsc_evaluations:rate1m:avg_over_time_1w
      expr: avg_over_time(rule_action:wafsc_evaluations:rate1m[1w])

    - record: rule_action:wafsc_evaluations:rate1m:stddev_over_time_1w
      expr: stddev_over_time(rule_action:wafsc_evaluations:rate1m[1w])

    - record: rule_action:wafsc_evaluations:rate1m:z_score
      expr: >
        (
          rule_action:wafsc_evaluations:rate1m -
          rule_action:wafsc_evaluations:rate1m:avg_over_time_1w
        ) / rule_action:wafsc_evaluations:rate1m:stddev_over_time_1w

    - record: rule_action:wafsc_evaluations:rate1m:seasonal_prediction
      expr: >
        quantile(0.5,
          label_replace(
            avg_over_time(rule_action:wafsc_evaluations:rate1m[4h] offset 166h)
            + rule_action:wafsc_evaluations:rate1m:avg_over_time_1w
            - rule_action:wafsc_evaluations:rate1m:avg_over_time_1w offset 1w
            , "offset", "1w", "", "")
          or
          label_replace(
            avg_over_time(rule_action:wafsc_evaluations:rate1m[4h] offset 334h)
            + rule_action:wafsc_evaluations:rate1m:avg_over_time_1w
            - rule_action:wafsc_evaluations:rate1m:avg_over_time_1w offset 2w
            , "offset", "2w", "", "")
          or
          label_replace(
            avg_over_time(rule_action:wafsc_evaluations:rate1m[4h] offset 502h)
            + rule_action:wafsc_evaluations:rate1m:avg_over_time_1w
            - rule_action:wafsc_evaluations:rate1m:avg_over_time_1w offset 3w
            , "offset", "3w", "", "")
        ) without (offset)

    - record: rule_action:wafsc_evaluations:rate1m:seasonal_prediction:z_score
      expr: >
        (
          rule_action:wafsc_evaluations:rate1m
          - rule_action:wafsc_evaluations:rate1m:seasonal_prediction
        ) / rule_action:wafsc_evaluations:rate1m:stddev_over_time_1w

There is work on retroactive rule evaluations happening on Prometheus already. Once that's figured out there we'll probably implement the same mechanism in Thanos. We look at backfilling data more as a thing for retrofitting non Prometheus data into the system, retroactive rule evaluations may make use of the same infrastructure but should be a first class feature, at least eventually.

For those who found this issue via search: thanks to @bwplotka and @dipack95 work on prometheus side it is now possible to import custom data in prometheus text format into Thanos via https://github.com/sepich/thanos-kit/ import command.
(It is currently reading all the imported data to memory, hope the feature would be implemented better in upstream version. Unfortunately we need this "yesterday" so can't wait anymore ;)

Currently, we have lots of backfill solutions that rely on block upload. We should invest in them and make them better.
BUT, this issue is for remote write backfill, which is in dev and design by the amazing Grafana team!. PTAL there.

Since the OOO feature has been merged into main, I will close this issue. Feel free to reopen if you think it is not addressed.


Add support for "date" and "date-time" with fractional seconds decoding in accordance with RFC 3339

Motivation
The current runtime uses the ISO8601DateFormatter provided by Swift to decode properties with the format 'date' and 'date-time'. OpenAPI docs & Swagger docs both mention these formats.
The standard mentioned in the docs and in the comments of this runtime is RFC 3339.
According to the Swagger docs, OpenAPI's "date" is RFC 3339's "full-date" and "date-time" has the same name on both ends.
Unfortunately "date" is not supported by this runtime at all and "date-time" only to limited effect. According to RFC 3339, "date-time" is defined as full-date "T" full-time. full-time is defined as partial-time time-offset. And partial-time is defined as time-hour ":" time-minute ":" time-second [time-secfrac].
The date-time decoding in this runtime stops working if the optional time-secfrac is included in the String, despite it being part of RFC 3339.
This change aims to fix both of this issues and decoding the date strings in accordance with RFC 3339.
Modifications
Before decoding the dateString with the ISO8601DateFormatter I am setting certain options depending on the String provided.
If the String contains a dot ("."), I am setting the options to [.withFractionalSeconds, .withInternetDateTime] to decode it correctly. According to RFC 3339, "fractional seconds" is the only case where a dot will ever be included in the date String, meaning this change will not break any other RFC 3339 date formats.
To handle dates without any time, I am setting the options to [.withFullDate] if dateString matches the following regex:
^\d{4}-\d{2}-\d{2}$.
No other format mentioned in RFC 3339 will produce a String with this exact regex.
Therefore these two changes should not influence any current decoding, but improve it to match the RFC 3339 standard.
Result
The following date strings...

"2023-05-21T11:22:33.123456+02:00"
"2023-05-21T11:22:33.123Z"
"2023-06-01"

...will all be correctly decoded in accordance to the RFC 3339 standard, whereas before, the decoding would fail. The data after the milliseconds gets lost during the decoding, but according to https://stackoverflow.com/a/23685280 this is a problem caused by the DateFormatter itself, and is not trivial to correct.
Test Plan
I have tested this change manually with the different formats listed above. I have also verified, that this doesn't break any current decoding by testing it with "2023-05-21T11:22:33Z" and "2023-05-21T11:22:33+02:00".
In addition to my manual tests, I will update the tests in this project to include the examples I listed above if you believe this change makes sense and should be merged.
Note about encoding different RFC 3339 date formats
This change only fixes the decoding of RFC 3339 date formats, not encoding.
Encoding RFC 3339 date-time with fractional seconds
This one is quite tricky, as it is not apparent from either the OpenAPI file or the Date provided if (or how many) decimals should be included in the date String. You would probably have to be able to pass this somewhere during the request, but this makes little sense in my opinion with my current limited overview over this project. It's probably easier to create a custom DateTranscoder instead of including this here to handle this case.
Encoding RFC 3339 date
This one however should be possible. In the OpenAPI file "date" and "date-time" are clearly distinguished. Therefore it may make sense to create a second DateTranscoder in this project to decode and encode the properties with the "date" format. At the moment I do not possess a good enough grasp of this project to implement this change cleanly, but it may make sense for a future version.
This would allow this runtime to decode all possible RFC 3339 formats mentioned by OpenAPI and encode all except for the date-time with fractional seconds.
(If this change was implemented, the "date" decoding I created here using the regex would become redundant.)

Both issues are handled:
"format: date": https://github.com/apple/swift-openapi-generator/pull/137
fractional seconds: https://github.com/apple/swift-openapi-generator/issues/84
I believe this change makes little sense with the provided solutions and should therefore be closed.


feat: FIR-28769: special treatment of 404 status when accessing account

Can we add an integration test for this? We can create an account with restrictive RBAC and another with correct RBAC but not linked to a user and use those in our tests.

Do we have such tests in other drivers that have the same feature? Let's separate this: first create special account, then implement this test for each driver. BTW I even not sure that this feature is already supported at the server side.

Do we have such tests in other drivers that have the same feature? Let's separate this: first create special account, then implement this test for each driver. BTW I even not sure that this feature is already supported at the server side.

We do, all our changes should contain the relevant tests as well. Let's keep the change and tests together in here as well.
A better strategy instead of having one persistent account was discussed on one of the dailies - a test account is created in the test itself, via the SQL and destroyed on the test completion.

Done


Remove dupilicate bir and jar generation for test if mocking feature is not used

Description:

Describe your problem(s)
Describe your solution(s)
Related Issues (optional):

https://github.com/ballerina-platform/ballerina-lang/issues/35097

Suggested Labels (optional):

Suggested Assignees (optional):

Blocked on #35093


test(x/twap): geometric twap edge case tests

Closes: #XXX
What is the purpose of the change
Adds geometric twap edge case tests. Defines min spot price as sdk.SmallestDec()
Brief Changelog
Overflow test
The old test case setup was incorrect as it was taking the logarithm of the accumulator instead of just the price. To mimic the real environment, this test case is now incorporated into TestComputeGeometricStrategyTwap table-driven test with quote assets in both denomes.
With one of the denoms, there is a panic due to precision loss. This happens because we end up taking 1 / < extremely large value >, resulting in a value smaller than the smallest Dec possible.
Underflow Test
This test case assumes that the spot price is the smallest dec possible. By taking a logarithm of the smallest value (0, 1) and multiplying it by 100 years, we confirm that our math functions do not accidentally cause an underflow.
The test is run in both denoms as quote assets.
Zero Accumulator Differences
This unlikely case might happen if all spot prices in history had returned a spot price error, resulting in geometric accumulators for start and end records as well as their difference always being 0.
While this is unlikely, this test helps to ensure that we have accounted for all kinds of risky outcomes.

LGTM for merge once we add that if statement for divide by zero -> min spot price!


chore: Release Noir(0.27.0)

:robot: I have created a release beep boop
0.27.0
0.27.0 (2024-04-10)
⚠ BREAKING CHANGES

Brillig typed memory (https://github.com/AztecProtocol/aztec-packages/pull/5395)

Features

acir_gen: Fold attribute at compile-time and initial non inlined ACIR (https://github.com/AztecProtocol/aztec-packages/pull/5341) (a0f7474)
acvm_js: Execute program  (#4694) (386f6d0)
acvm: Execute multiple circuits  (https://github.com/AztecProtocol/aztec-packages/pull/5380) (a0f7474)
Add remove_enable_side_effects SSA pass (#4224) (94952db)
Allow slices to brillig entry points (#4713) (62423d5)
Brillig typed memory (https://github.com/AztecProtocol/aztec-packages/pull/5395) (0bc18c4)
docs: Documenting noir codegen (#4454) (24f6d85)
Improve nargo check cli with --override flag and feedback for existing files (#4575) (5e7fbd4)
Improve optimisations on range constraints (#4690) (96b8110)
Improve SSA type-awareness in EQ and MUL instructions (#4691) (669f1a0)
nargo: Multiple circuits info for binary programs (#4719) (50d2735)

Bug Fixes

"Types in a binary operation should match, but found T and T" (#4648) (30c9f31)
acvm: Mark outputs of Opcode::Call solvable (#4708) (8fea405)
Correct ICE panic messages in brillig convert_black_box_call (#4761) (f3eee6c)
Error when a type variable is unbound during monomorphization instead of defaulting to Field (#4674) (03cdba4)
Field comparisons (#4704) (079cb2a)
Impl search no longer selects an impl if multiple are applicable (#4662) (0150600)
Last use analysis & make it an SSA pass (#4686) (0d3d5fd)
Slice coercions (#4640) (c0bae17)
ssa: Accurate constant type for slice dummy data in flattening (#4661) (b87654e)
ssa: Do not use get_value_max_num_bits when we want pure type information (#4700) (b55a580)
ssa: Fix slice intrinsic handling in the capacity tracker  (#4643) (1b50ce1)
Unknown slice lengths coming from as_slice (#4725) (f21129e)
Update commit for noir-gates-diff (#4773) (a9766c5)

0.43.0
0.43.0 (2024-04-10)
⚠ BREAKING CHANGES

Brillig typed memory (https://github.com/AztecProtocol/aztec-packages/pull/5395)
acir: Program and witness stack structure (https://github.com/AztecProtocol/aztec-packages/pull/5149)
automatic NoteInterface and NoteGetterOptions auto select (https://github.com/AztecProtocol/aztec-packages/pull/4508)
Acir call opcode (https://github.com/AztecProtocol/aztec-packages/pull/4773)
Support contracts with no constructor (https://github.com/AztecProtocol/aztec-packages/pull/5175)
Internal as a macro (https://github.com/AztecProtocol/aztec-packages/pull/4898)
move noir out of yarn-project (https://github.com/AztecProtocol/aztec-packages/pull/4479)
note type ids (https://github.com/AztecProtocol/aztec-packages/pull/4500)
rename bigint_neg into bigint_sub (https://github.com/AztecProtocol/aztec-packages/pull/4420)
Add expression width into acir (https://github.com/AztecProtocol/aztec-packages/pull/4014)
init storage macro (https://github.com/AztecProtocol/aztec-packages/pull/4200)
acir: Move is_recursive flag to be part of the circuit definition (https://github.com/AztecProtocol/aztec-packages/pull/4221)
Sync commits from aztec-packages (#4144)
Breaking changes from aztec-packages (#3955)
Rename Arithmetic opcode to AssertZero (#3840)
Remove unused methods on ACIR opcodes (#3841)

Features

Acir call opcode (https://github.com/AztecProtocol/aztec-packages/pull/4773) (c3c9e19)
acir_gen: Fold attribute at compile-time and initial non inlined ACIR (https://github.com/AztecProtocol/aztec-packages/pull/5341) (a0f7474)
acir: Program and witness stack structure (https://github.com/AztecProtocol/aztec-packages/pull/5149) (13eb71b)
acvm_js: Execute program  (#4694) (386f6d0)
acvm: Execute multiple circuits  (https://github.com/AztecProtocol/aztec-packages/pull/5380) (a0f7474)
Add bit size to const opcode (https://github.com/AztecProtocol/aztec-packages/pull/4385) (158c8ce)
Add CMOV instruction to brillig and brillig gen (https://github.com/AztecProtocol/aztec-packages/pull/5308) (13eb71b)
Add expression width into acir (https://github.com/AztecProtocol/aztec-packages/pull/4014) (158c8ce)
Add instrumentation for tracking variables in debugging (#4122) (c58d691)
Add poseidon2 opcode implementation for acvm/brillig, and Noir (#4398) (10e8292)
Add support for overriding expression width (#4117) (c8026d5)
Added cast opcode and cast calldata (https://github.com/AztecProtocol/aztec-packages/pull/4423) (78ef013)
Allow brillig to read arrays directly from memory (https://github.com/AztecProtocol/aztec-packages/pull/4460) (158c8ce)
Allow nested arrays and vectors in Brillig foreign calls (https://github.com/AztecProtocol/aztec-packages/pull/4478) (158c8ce)
Allow variables and stack trace inspection in the debugger (#4184) (bf263fc)
Automatic NoteInterface and NoteGetterOptions auto select (https://github.com/AztecProtocol/aztec-packages/pull/4508) (13eb71b)
avm: Back in avm context with macro - refactor context (https://github.com/AztecProtocol/aztec-packages/pull/4438) (158c8ce)
avm: Brillig CONST of size > u128 (https://github.com/AztecProtocol/aztec-packages/pull/5217) (c3c9e19)
aztec-nr: Initial work for aztec public vm macro (https://github.com/AztecProtocol/aztec-packages/pull/4400) (158c8ce)
Backpropagate constants in ACIR during optimization (#3926) (aad0da0)
Breaking changes from aztec-packages (#3955) (5be049e)
Brillig IR refactor (https://github.com/AztecProtocol/aztec-packages/pull/5233) (c3c9e19)
Brillig typed memory (https://github.com/AztecProtocol/aztec-packages/pull/5395) (0bc18c4)
Check initializer msg.sender matches deployer from address preimage (https://github.com/AztecProtocol/aztec-packages/pull/5222) (c3c9e19)
Evaluation of dynamic assert messages (#4101) (c284e01)
Init storage macro (https://github.com/AztecProtocol/aztec-packages/pull/4200) (158c8ce)
Initial Earthly CI (https://github.com/AztecProtocol/aztec-packages/pull/5069) (c3c9e19)
Internal as a macro (https://github.com/AztecProtocol/aztec-packages/pull/4898) (5f57ebb)
New brillig field operations and refactor of binary operations (https://github.com/AztecProtocol/aztec-packages/pull/5208) (c3c9e19)
Note type ids (https://github.com/AztecProtocol/aztec-packages/pull/4500) (78ef013)
Remove range constraints from witnesses which are constrained to be constants (#3928) (afe9c7a)
Remove replacement of boolean range opcodes with AssertZero opcodes (#4107) (dac0e87)
Signed integer division and modulus in brillig gen (https://github.com/AztecProtocol/aztec-packages/pull/5279) (c3c9e19)
Support contracts with no constructor (https://github.com/AztecProtocol/aztec-packages/pull/5175) (c3c9e19)
Sync aztec-packages (#4011) (fee2452)
Sync commits from aztec-packages (#4068) (7a8f3a3)
Sync commits from aztec-packages (#4144) (0205d3b)
Sync from aztec-packages (#4483) (fe8f277)
Sync from noir (https://github.com/AztecProtocol/aztec-packages/pull/5234) (c3c9e19)
Sync from noir (https://github.com/AztecProtocol/aztec-packages/pull/5286) (c3c9e19)

Bug Fixes

acvm: Mark outputs of Opcode::Call solvable (#4708) (8fea405)
Noir test incorrect reporting (https://github.com/AztecProtocol/aztec-packages/pull/4925) (5f57ebb)
Remove panic from init_log_level in acvm_js (#4195) (2e26530)
Return error rather instead of panicking on invalid circuit (#3976) (67201bf)

Miscellaneous Chores

acir: Move is_recursive flag to be part of the circuit definition (https://github.com/AztecProtocol/aztec-packages/pull/4221) (158c8ce)
Move noir out of yarn-project (https://github.com/AztecProtocol/aztec-packages/pull/4479) (78ef013)
Remove unused methods on ACIR opcodes (#3841) (9e5d0e8)
Rename Arithmetic opcode to AssertZero (#3840) (836f171)
Rename bigint_neg into bigint_sub (https://github.com/AztecProtocol/aztec-packages/pull/4420) (158c8ce)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/noir-lang/noir/releases/tag/v0.27.0 :sunflower:


cannot be compiled

Version
List the version(s) of hyper, and any relevant hyper dependency (such as h2 if this is related to HTTP/2).
0.14.18
Platform
The output of uname -a (UNIX), or version and 32 or 64-bit (Windows)
Darwin nikoss-MacBook-Pro.local 21.5.0 Darwin Kernel Version 21.5.0: Tue Apr 26 21:08:29 PDT 2022; root:xnu-8020.121.3~4/RELEASE_ARM64_T8101 arm64

Description
cargo check on an empty project fails to compile
[short summary of the bug]
I tried this code:

cargo add hyper
cargo check
[code sample that causes the bug]
empty main function

I expected to see this happen: [explanation]
Successful compilation
Instead, this happened: [explanation]
    Checking hyper v0.14.18
error[E0596]: cannot borrow `self.data_tx` as mutable, as `self` is not declared as mutable
   --> /Users/nikos/.cargo/registry/src/github.com-1ecc6299db9ec823/hyper-0.14.18/src/body/body.rs:658:11
    |
656 |       pub fn abort(self)
    |                    ---- help: consider changing this to be mutable: `mut self`
657 |       {
658 |           let _ = self
    |  _________________^
659 | |             .data_tx
660 | |             // clone so the send works even if buffer is full
661 | |             .try_send(Err(crate::Error::new_body_write_aborted()));
    | |__________________________________________________________________^ cannot borrow as mutable

For more information about this error, try `rustc --explain E0596`.
error: could not compile `hyper` due to previous error

Do you have an older version of rustc?

@seanmonstar i have the latest version and  v0.13 compiles just fine but as it turned out this was an issue with cargo not hyper itself. for whatever reason cargo registry got corrupted


POM cleanup

Removing artifacts and configuration related to Elasticsearch integration test framework. We are not using it for now.

Hey, Mr. CI, wake up! 🔔

add to whitelist

[merge]


[BUG] datatrail clear command failing to clear staged baseband.raw data on arc

Describe the bug
datatrail clear command regularly fails to clear staged raw baseband data on /arc. The issue was noticed when an inordinate number of failed instances of the baseband pipelines were reporting failures at final unstage_data step of the pipeline. (see e.g. https://frb.chimenet.ca/workflow/web/CHIMEFRB/pipelines/mckinven-baseband-processing/66c78aabc05879f572d2ee8d)
To Reproduce
Issue can be reproduced by running the following command in jupyter notebook session on CANFAR (using image: baseband-analysis:lastest)
os.system("datatrail clear chime.event.baseband.raw 214414053 -vvv -f")
The traceback for the above command is the following:
[20:48:43] DEBUG    `clear` called with:                             ]8;id=435533;file:///opt/pysetup/.venv/lib/python3.8/site-packages/dtcli/clear.py\clear.py]8;;\:]8;id=893582;file:///opt/pysetup/.venv/lib/python3.8/site-packages/dtcli/clear.py#69\69]8;;\
           DEBUG    scope: chime.event.baseband.raw [<class 'str'>]  ]8;id=307743;file:///opt/pysetup/.venv/lib/python3.8/site-packages/dtcli/clear.py\clear.py]8;;\:]8;id=36172;file:///opt/pysetup/.venv/lib/python3.8/site-packages/dtcli/clear.py#70\70]8;;\
           DEBUG    dataset: 214414053 [<class 'str'>]               ]8;id=703882;file:///opt/pysetup/.venv/lib/python3.8/site-packages/dtcli/clear.py\clear.py]8;;\:]8;id=492021;file:///opt/pysetup/.venv/lib/python3.8/site-packages/dtcli/clear.py#71\71]8;;\
           DEBUG    directory: None [<class 'NoneType'>]             ]8;id=687894;file:///opt/pysetup/.venv/lib/python3.8/site-packages/dtcli/clear.py\clear.py]8;;\:]8;id=201015;file:///opt/pysetup/.venv/lib/python3.8/site-packages/dtcli/clear.py#72\72]8;;\
           DEBUG    clear_parents: False [<class 'bool'>]            ]8;id=222935;file:///opt/pysetup/.venv/lib/python3.8/site-packages/dtcli/clear.py\clear.py]8;;\:]8;id=298572;file:///opt/pysetup/.venv/lib/python3.8/site-packages/dtcli/clear.py#73\73]8;;\
           DEBUG    verbose: 3 [<class 'int'>]                       ]8;id=125098;file:///opt/pysetup/.venv/lib/python3.8/site-packages/dtcli/clear.py\clear.py]8;;\:]8;id=758414;file:///opt/pysetup/.venv/lib/python3.8/site-packages/dtcli/clear.py#74\74]8;;\
           DEBUG    quiet: False [<class 'bool'>]                    ]8;id=345939;file:///opt/pysetup/.venv/lib/python3.8/site-packages/dtcli/clear.py\clear.py]8;;\:]8;id=268726;file:///opt/pysetup/.venv/lib/python3.8/site-packages/dtcli/clear.py#75\75]8;;\
           DEBUG    Loading configuration.                           ]8;id=464776;file:///opt/pysetup/.venv/lib/python3.8/site-packages/dtcli/clear.py\clear.py]8;;\:]8;id=937050;file:///opt/pysetup/.venv/lib/python3.8/site-packages/dtcli/clear.py#79\79]8;;\
           DEBUG    Site set to: canfar                              ]8;id=419845;file:///opt/pysetup/.venv/lib/python3.8/site-packages/dtcli/clear.py\clear.py]8;;\:]8;id=282839;file:///opt/pysetup/.venv/lib/python3.8/site-packages/dtcli/clear.py#82\82]8;;\
           INFO     No directory, setting to:                        ]8;id=114362;file:///opt/pysetup/.venv/lib/python3.8/site-packages/dtcli/clear.py\clear.py]8;;\:]8;id=171106;file:///opt/pysetup/.venv/lib/python3.8/site-packages/dtcli/clear.py#85\85]8;;\
                    /arc/projects/chime_frb/

Searching for files for 214414053 chime.event.baseband.raw...

           DEBUG    Loading configuration.                      ]8;id=818809;file:///opt/pysetup/.venv/lib/python3.8/site-packages/dtcli/src/functions.py\functions.py]8;;\:]8;id=906034;file:///opt/pysetup/.venv/lib/python3.8/site-packages/dtcli/src/functions.py#388\388]8;;\
           DEBUG    Server: https://frb.chimenet.ca/datatrail   ]8;id=44794;file:///opt/pysetup/.venv/lib/python3.8/site-packages/dtcli/src/functions.py\functions.py]8;;\:]8;id=73367;file:///opt/pysetup/.venv/lib/python3.8/site-packages/dtcli/src/functions.py#392\392]8;;\
           DEBUG    Configuration loaded successfully.          ]8;id=617588;file:///opt/pysetup/.venv/lib/python3.8/site-packages/dtcli/src/functions.py\functions.py]8;;\:]8;id=433847;file:///opt/pysetup/.venv/lib/python3.8/site-packages/dtcli/src/functions.py#393\393]8;;\
           INFO     Querying Datatrail for 214414053            ]8;id=239627;file:///opt/pysetup/.venv/lib/python3.8/site-packages/dtcli/src/functions.py\functions.py]8;;\:]8;id=459523;file:///opt/pysetup/.venv/lib/python3.8/site-packages/dtcli/src/functions.py#398\398]8;;\
                    chime.event.baseband.raw.
           DEBUG    URL:                                        ]8;id=537021;file:///opt/pysetup/.venv/lib/python3.8/site-packages/dtcli/src/functions.py\functions.py]8;;\:]8;id=902176;file:///opt/pysetup/.venv/lib/python3.8/site-packages/dtcli/src/functions.py#401\401]8;;\
                    https://frb.chimenet.ca/datatrail/query/dat
                    aset/find
╭───────────────────── Traceback (most recent call last) ──────────────────────╮
│ /opt/pysetup/.venv/bin/datatrail:8 in <module>                               │
│                                                                              │
│   5 from dtcli.cli import cli                                                │
│   6 if __name__ == '__main__':                                               │
│   7 │   sys.argv[0] = re.sub(r'(-script\.pyw|\.exe)?$', '', sys.argv[0])     │
│ ❱ 8 │   sys.exit(cli())                                                      │
│   9                                                                          │
│                                                                              │
│ /opt/pysetup/.venv/lib/python3.8/site-packages/click/core.py:1130 in         │
│ __call__                                                                     │
│                                                                              │
│   1127 │                                                                     │
│   1128 │   def __call__(self, *args: t.Any, **kwargs: t.Any) -> t.Any:       │
│   1129 │   │   """Alias for :meth:`main`."""                                 │
│ ❱ 1130 │   │   return self.main(*args, **kwargs)                             │
│   1131                                                                       │
│   1132                                                                       │
│   1133 class Command(BaseCommand):                                           │
│                                                                              │
│ /opt/pysetup/.venv/lib/python3.8/site-packages/click/core.py:1055 in main    │
│                                                                              │
│   1052 │   │   try:                                                          │
│   1053 │   │   │   try:                                                      │
│   1054 │   │   │   │   with self.make_context(prog_name, args, **extra) as c │
│ ❱ 1055 │   │   │   │   │   rv = self.invoke(ctx)                             │
│   1056 │   │   │   │   │   if not standalone_mode:                           │
│   1057 │   │   │   │   │   │   return rv                                     │
│   1058 │   │   │   │   │   # it's not safe to `ctx.exit(rv)` here!           │
│                                                                              │
│ /opt/pysetup/.venv/lib/python3.8/site-packages/click/core.py:1657 in invoke  │
│                                                                              │
│   1654 │   │   │   │   super().invoke(ctx)                                   │
│   1655 │   │   │   │   sub_ctx = cmd.make_context(cmd_name, args, parent=ctx │
│   1656 │   │   │   │   with sub_ctx:                                         │
│ ❱ 1657 │   │   │   │   │   return _process_result(sub_ctx.command.invoke(sub │
│   1658 │   │                                                                 │
│   1659 │   │   # In chain mode we create the contexts step by step, but afte │
│   1660 │   │   # base command has been invoked.  Because at that point we do │
│                                                                              │
│ /opt/pysetup/.venv/lib/python3.8/site-packages/click/core.py:1404 in invoke  │
│                                                                              │
│   1401 │   │   │   echo(style(message, fg="red"), err=True)                  │
│   1402 │   │                                                                 │
│   1403 │   │   if self.callback is not None:                                 │
│ ❱ 1404 │   │   │   return ctx.invoke(self.callback, **ctx.params)            │
│   1405 │                                                                     │
│   1406 │   def shell_complete(self, ctx: Context, incomplete: str) -> t.List │
│   1407 │   │   """Return a list of completions for the incomplete value. Loo │
│                                                                              │
│ /opt/pysetup/.venv/lib/python3.8/site-packages/click/core.py:760 in invoke   │
│                                                                              │
│    757 │   │                                                                 │
│    758 │   │   with augment_usage_errors(__self):                            │
│    759 │   │   │   with ctx:                                                 │
│ ❱  760 │   │   │   │   return __callback(*args, **kwargs)                    │
│    761 │                                                                     │
│    762 │   def forward(                                                      │
│    763 │   │   __self, __cmd: "Command", *args: t.Any, **kwargs: t.Any  # no │
│                                                                              │
│ /opt/pysetup/.venv/lib/python3.8/site-packages/click/decorators.py:26 in     │
│ new_func                                                                     │
│                                                                              │
│    23 │   """                                                                │
│    24 │                                                                      │
│    25 │   def new_func(*args, **kwargs):  # type: ignore                     │
│ ❱  26 │   │   return f(get_current_context(), *args, **kwargs)               │
│    27 │                                                                      │
│    28 │   return update_wrapper(t.cast(F, new_func), f)                      │
│    29                                                                        │
│                                                                              │
│ /opt/pysetup/.venv/lib/python3.8/site-packages/dtcli/clear.py:107 in clear   │
│                                                                              │
│   104 │                                                                      │
│   105 │   # Find number of files in common directory and size.               │
│   106 │   console.print(f"\nSearching for files for {dataset} {scope}...\n") │
│ ❱ 107 │   common_path = find_dataset_common_path(scope, dataset, site, verbo │
│   108 │   if common_path:                                                    │
│   109 │   │   common_path = (directory + common_path).replace("//", "/")     │
│   110 │   if not common_path:                                                │
│                                                                              │
│ /opt/pysetup/.venv/lib/python3.8/site-packages/dtcli/src/functions.py:418 in │
│ find_dataset_common_path                                                     │
│                                                                              │
│   415 │   │   file_paths = [f.replace("cadc:CHIMEFRB/", "") for f in file_ur │
│   416 │   │                                                                  │
│   417 │   │   common_path = os.path.commonprefix(file_paths).replace("//", " │
│ ❱ 418 │   │   if common_path[-1] != "/":                                     │
│   419 │   │   │   common_path = "/".join(common_path.split("/")[:-1])        │
│   420 │                                                                      │
│   421 │   else:                                                              │
╰──────────────────────────────────────────────────────────────────────────────╯
IndexError: string index out of range

Expected behavior
Raw baseband data temporarily staged at /arc/projects/chime_frb/data/baseband/raw/YYYY/MM/DD/astro_<event_id>/ should be cleared once singlebeam.h5 file is produced and yet for event 214414053 and other like it staged data remains.

@rmck1 can you copy in the contents of the file at this location
~/.datatrail/config.yaml
i.e. in your home directory somewhere

Here are the contents of the file: ~/.datatrail/config.yaml
root_mounts:
  canfar: /arc/projects/chime_frb/
  chime: /
  gbo: /
  hco: /
  kko: /
  local: ./
server: https://frb.chimenet.ca/datatrail
site: canfar
vospace_certfile: /arc/home/Mckinven/.ssl/cadcproxy.pem

Yeah so the issue is that the post request to find the relevant filepaths returns filepaths with a mix of
data/chime/baseband/raw/...
and
cadc:CHIMEFRB/data/chime/baseband/raw/..
Now normally code exists to account for this by simply finding and replacing all those prefix's.
However in this case, for some reason I don't understand the result gives something like this
...
   'data/chime/baseband/raw/2022/03/06/astro_214414053/baseband_214414053_725.h5',
   'cadc:CHIMEFRB//data/chime/baseband/raw/2022/03/06/astro_214414053/baseband_214414053_811.h5',
   'cadc:CHIMEFRB//data/chime/baseband/raw/2022/03/06/astro_214414053/baseband_214414053_771.h5',
   'cadc:CHIMEFRB//data/chime/baseband/raw/2022/03/06/astro_214414053/baseband_214414053_773.h5',
   'cadc:CHIMEFRB//data/chime/baseband/raw/2022/03/06/astro_214414053/baseband_214414053_784.h5',
   'cadc:CHIMEFRB//data/chime/baseband/raw/2022/03/06/astro_214414053/baseband_214414053_776.h5',
   'cadc:CHIMEFRB//data/chime/baseband/raw/2022/03/06/astro_214414053/baseband_214414053_775.h5',
   'data/chime/baseband/raw/2022/03/06/astro_214414053/baseband_214414053_7.h5',
   'data/chime/baseband/raw/2022/03/06/astro_214414053/baseband_214414053_757.h5',
   'data/chime/baseband/raw/2022/03/06/astro_214414053/baseband_214414053_926.h5',
   'data/chime/baseband/raw/2022/03/06/astro_214414053/baseband_214414053_939.h5',
   'data/chime/baseband/raw/2022/03/06/astro_214414053/baseband_214414053_948.h5',
   'data/chime/baseband/raw/2022/03/06/astro_214414053/baseband_214414053_949.h5',

...
which upon close inspection shows a different prefix cadc:CHIMEFRB//data/baseband/raw..., i.e. it has a double forward slash, and so in the find and replace it catches only part of the prefix, leaving the following mix of filepaths remaining
...
 'data/chime/baseband/raw/2022/03/06/astro_214414053/baseband_214414053_302.h5',
 'data/chime/baseband/raw/2022/03/06/astro_214414053/baseband_214414053_309.h5',
 'data/chime/baseband/raw/2022/03/06/astro_214414053/baseband_214414053_311.h5',
 'data/chime/baseband/raw/2022/03/06/astro_214414053/baseband_214414053_312.h5',
 '/data/chime/baseband/raw/2022/03/06/astro_214414053/baseband_214414053_319.h5',
 '/data/chime/baseband/raw/2022/03/06/astro_214414053/baseband_214414053_283.h5',
 '/data/chime/baseband/raw/2022/03/06/astro_214414053/baseband_214414053_316.h5',
 'data/chime/baseband/raw/2022/03/06/astro_214414053/baseband_214414053_296.h5',
 'data/chime/baseband/raw/2022/03/06/astro_214414053/baseband_214414053_297.h5',
 'data/chime/baseband/raw/2022/03/06/astro_214414053/baseband_214414053_303.h5',
 'data/chime/baseband/raw/2022/03/06/astro_214414053/baseband_214414053_314.h5',

...
with forward slashes at the start of some, and as a result there is no common filepath between this set, and the result of that search is common_path='', which then when you try to index common_path[-1] results in the string error. To fix this we can simply search and replace cadc:CHIMEFRB// first before subsequently finding and replacing the original cadc:CHIMEFRB/, but I'm relatively confounded as to why this happens in the first place, and what about these certain events that is different.

No that's not the issue, the existing scripts already find and replace the cadc:CHIMEFRB to nothing, i.e. removing that prefix from the filename and so those differences are handled, the issue is that some are cadc:CHIMEFRB/data...' and some are cadc:CHIMEFRB//data` and so there is a discrepancy even once the prefix has been removed based on whether there are 1 or 2 forward slashes. So I guess the solution is that this edge case also needs to be checked?

Right, I understand but ultimately it comes from the fact that the data in the database isn't consistent. If you don't want to touch the data in the database, you can reorganise the logic that you mention, these lines. With something like the following:
    if dataset_locations["file_replica_locations"].get("minoc"):  # type: ignore
        file_uris = dataset_locations["file_replica_locations"]["minoc"]  # type: ignore
-       file_paths = [f.replace("cadc:CHIMEFRB/", "") for f in file_uris]
+       file_paths = [f.replace("//", "/").replace("cadc:CHIMEFRB/", "") for f in file_uris]

-        common_path = os.path.commonprefix(file_paths).replace("//", "/")
+        common_path = os.path.commonprefix(file_paths)

Either way should address this issue.

Right that makes sense. I guess if this is going to keep happening then logic is better than triaging the database. If it's due to a change in the past then I guess I expect it to be a once off and therefore it's just simpler to change the database, but then I don't know why it would be different for files within a single event?

@tjzegmott did the changes you mention already get implemented? Seems like the new code is already in there, if so we can close this issue

I didn't create any commits and I don't see the changes in the code. At least not on the main branch. I will create the commit and PR now.


Omit first argument label of delegate method

I think to omit first argument label of delegate method is standard. For example, some delegate methods in UIKit omit first argument label.
https://developer.apple.com/documentation/uikit/uitextfielddelegate
Also, raywenderlich.com recommends the style.
https://github.com/raywenderlich/swift-style-guide#delegates

@culumn
Thanks for your work, 👍


Fix repo references after repo move

The react-native-tvos repo has been moved out of https://github.com/react-native-community/, and into its own dedicated Github organization https://github.com/react-native-tvos.
Accordingly, some changes need to be made in the files, particularly in package.json, Podfile, template.
For more context around this move, see https://github.com/react-native-community/discussions-and-proposals/blob/master/partners/0002-apply-organization-repository-policy.md

react-native-tvos/CONTRIBUTING.md
L47: * **High-quality plugins** for React Native can be found throughout the [React Native Directory](https://reactnative.directory).

@Krisztiaan we're not really a plugin, but I'll look into getting this repo into that directory

Oh no, I meant the CONTRIBUTING.md could be updated to redirect users reading it to reactnative.directory instead of react-native-community.

@Krisztiaan Aha thanks.... That file comes from core and they have not changed that URL to point to the reactnative.directory listing.
Maybe we should create a new issue to rewrite that whole file specifically for this repo 👍

Oh yes, good point! I'm not sure I like this change in react-native-community, but fingers crossed it's for the best.
LGTM for now?

@Krisztiaan we're not really a plugin, but I'll look into getting this repo into that directory

react-native-tvos is listed in the Directory footer with other available platforms.

Lately we have also added a separate platform flag for tvOS compatibility:

https://github.com/react-native-community/directory/pull/485

Feel free to add or mark any other compatible libraries with tvOS in the Pull Request. 🙂


Message bubbles alignment issue: bubbles jump on 4.7" screens

I encounter an irregular behaviour where the bubbles are not aligned to the edges but have an offset. After receiving a new message the offsets are removed.
This is what it looks like:

This is what it should look like:

This bug does not appear on screens smaller than 4.7".

I put this in viewWillAppear and it solved it:
        self.collectionView.layoutIfNeeded()
        self.collectionView.performBatchUpdates({
            self.collectionView.reloadData()
            }, completion: nil)

But why did it happen in the first place?

Ok, I assume the problem occured because I have a custom cell that is loaded form nib. Its size is declared in sizeForItemAtIndexPath method:
       if message.isSystemMessage {             return CGSizeMake(self.collectionView!.frame.width, 44)         }
The alignment error occured maybe because the collectionView.frame.width had not the correct size when sizeForItemAtIndexPath was called first. I changed it to:
        if message.isSystemMessage {             return CGSizeMake(UIScreen.mainScreen().bounds.width, 44)         }
It seems to work now.

The problem still occurs. And sometimes the cell top label has an offset too. Also: the code above makes the view appear very laggy when it gets pushed on the navigation stack. So I think it is not a good workaround. How to fix it?

@MHX792 do you still see this issue on 7.3.4? If you are able to replicate it in the sample app, that would be great. 😃

Hello everyone!
I'm sorry to inform the community that I'm officially deprecating this project. 😢 Please read my blog post for details:
http://www.jessesquires.com/blog/officially-deprecating-jsqmessagesviewcontroller/
Thus, I'm closing all issues and pull requests and making the necessary updates to formally deprecate the library. I'm sorry if this is unexpected or disappointing. Please know that this was an extremely difficult decision to make. I'd like to thank everyone here for contributing and making this project so great. It was a fun 4 years. 😊
Thanks for understanding,
— jsq


KeyError: 'state_dict' running test.py

After I trained the model with only drivable area detection task, I wanna evaluate my model by using test.py

It raised me the following key error

I avoid the issue by using 'final_state.pth'. instead, I used 'epoch_240.pth'. Don't know why but I am running now.

我也有同样的问题，请问你是怎样解决的？

同问


Youku issue help needed please

annie https://v.youku.com/v_show/id_XNTEyOTUzOTYw.html?spm=a2h0c.8166622.PhoneSokuUgc_44.dtitle
Downloading https://v.youku.com/v_show/id_XNTEyOTUzOTYw.html?spm=a2h0c.8166622.PhoneSokuUgc_44.dtitle error:
客户端无权播放,201
how to get past this please

@iawia002

@iawia002 please help needed to get through on Mac

I do not use Youku, but you can look at this issue here: #867.

I do not know how to replace the code @john-black-3k

I do not use Youku, but you can look at this issue here: #867.

The README.md contains info on this. Just use this command:
annie -ccode 0532 <youku_video_url>

I tested with the URL you provided and it worked.

Updated in ffb34d810df408a4570ef6930813ca140a975011


Kasparovsyncd dag/selected-tip does not seem to contain block relation info

When receiving dag/selected-tip, notifications, there doesn't seem to be any information meant to relate incoming block to another.

Apologies. Block has a new field called parentBlockHashes. It was added 3 days ago. Can you get the latest version, and let me know if it solves it for you?

Furthermore, the purpose of dag/selected-tip is for calculating confirmations for transactions and blocks that you know of.
The calculation is block.confirmations = dag.selected_tip_block.blue_score - block.accepting_block.blue_score + 1.
This allows you to recalculate the confirmations on all blocks that you have, whenever there is a new selected tip block coming in as a notification from dag/selected-tip.

resolved.


Move fading to effect and add collision fading support.

This PR moves the fade logic to a common effect accessible by all nodes - including with the ability to fade to colors.
Additionally it adds collision-based fading to prevent looking through walls.

lgtm, thanks again malcolm for working this out!

Added a basic damage area to the basic movement scene.
https://github.com/GodotVR/godot-xr-tools/assets/1863707/74977229-2e61-495f-9bbc-7100c101e8e5


Missing directories

When starting ./dmon-agent.sh there are missing directories that are not created by default. These are pid/ and log/

Added provisional fix, created issue #99 for use of setuptools for all monitoring  microservice installation and bootstrapping.


Specify macOS version

error: the library 'web3swift' requires macos 10.10, but depends on the product 'CryptoSwift' which requires macos 10.12; consider changing the library 'web3swift' to require macos 10.12 or later, or the product 'CryptoSwift' to require macos 10.10 or earlier.

The package.swift doesn't specify a platforms key and relies on CryptoSwift which specifies macOS 10.12. To reproduce the error, create a Swift Package and specify this repository as a dependency. Then, run swift build.
https://github.com/krzyzanowskim/CryptoSwift/blob/master/Package.swift#L8

Hey, @rehatkathuria  have your initial issue been resolved? Please let us know if it can be closed.
If you still experience any problems, feel free to add more details in this issue or open another one.


Execute child.stdout.on before child.on("exit")

var shell = require('shelljs');

var child = shell.exec('node --version', {silent:true, async:true});

child.stdout.on('data', function(data) {
    console.log(data);
});

child.on("exit", function(code) {
    console.log(code);
});

child.on("error", function (error) {
console.log(error);
});

The output of this command is :
0
v1.0.4

What do i have to do, to make shelljs return all data immediately and before on exit is executed ?

child.stdout.on('data', stuff);
child.stdout.on('end', otherStuff);

Everything is now printed in the correct order, but end is always undefined:
child.stdout.on('end', function(end) {
    console.log(end);
});

var code;
child.on('exit', function(c) {
    code = c;
});
child.stdout.on('data', function(data) {
    console.log(data);
});
child.stdout.on('end', function() {
    console.log(code);
});

@devTristan this now results in undefined. end is triggered before exit.
This gives me the correct output with exit code:
var child = shell.exec(cmd, {async: true, silent: true});
var output = "";

child.on('exit', function(c) {
    console.log(output);
    console.log('Exit code is ' + c);
});

child.stdout.on('data', function (data) {
    if (!!data)
        output += data;
});

@Synturas @kevin-smets is this resolved now?

Assuming this is fixed (we did a heavy refactor of exec())