text:
Unable to connect two SAP Hana DB Data Lake

Description
Hello,
i managed to sucessfully establish a connection two an SAP Hana DB cloud instance but not two the coresponding
SAP HANA DB data Lake.
I got the follwing Error message:
SAP DBTech JDBC: Cannot connect to jdbc:sap://3023f74f-249d-4325-8079-7b770216e54c.iq.hdl.trial-us10.hanacloud.ondemand.com:443 [Object is closed: com.sap.db.jdbc.SecureChannelSession@5d475444 3023f74f-249d-4325-8079-7b770216e54c.iq.hdl.trial-us10.hanacloud.ondemand.com:443 ConnectionID:0 SessionID:0 on sun.nio.ch.WindowsAsynchronousSocketChannelImpl[connected local=/[0:0:0:0:0:0:0:0]:59708 remote=3023f74f-249d-4325-8079-7b770216e54c.iq.hdl.trial-us10.hanacloud.ondemand.com/52.23.3.236:443]: w.x.y.z.z:59708 -> 3023f74f-249d-4325-8079-7b770216e54c.iq.hdl.trial-us10.hanacloud.ondemand.com:443 ConnectionID:0 SessionID:0].
Note: w.x.y.z.z = my local IP adress within our companies LAN
The SQL connection settings two db that works is like:

The connection that does not work to SAP Hana Cloud DB Data Lake

I asked myself what wen't wrong with connection to DATA LAke ?
Thanks in advance
DBeaver Version
Community Version 24.0.2.202404071654
Operating System
Windows 10 22H2
Database and driver
No response
Steps to reproduce
No response
Additional context
No response

Probably, we don't support SAP HANA DB Data Lake connection

HANA Cloud Data Lake Relational Engine is based in SAP IQ (formerly known as Sybase IQ) technology.
Please look here to figure out the right ODBC or JDBC driver and here on how to configure in DBeaver.

@marcrupprath, did the suggested advice help you?

@E1izabeth : Yes i have gotten a Driver from a 3-rd party and it then works fine with DBeaver.

authors: E1izabeth kai-morich marcrupprath


text:
In spatial data view, filter geometries based on current view

Is your feature request related to a problem? Please describe.
With PostgreSQL, when viewing a large table with GIS data, it is often required to see all available data in the given map location, not the entire table. This is especially important when individual geometries are small and/or not sorted (i.e. sequential items could appear all over the earth).  At the moment, I must switch to QGIS to view this data.
Describe the solution you'd like
After switching from Grid to Spatial view, run a query for the currently viewed location (top N). It might be good to check if a corresponding GIS index exists, and suggest it if not.  Unless "locked", any movement of the map view should re-query the data.
Describe alternatives you've considered
Use QGIS tool for similar functionality -- but harder to use for DB usecase.
Additional context

See also #13501 - a similar request that was misunderstood at first, but later arrived to a similar feature request (but was already closed by then)

Thank you for the idea

source: gharchive/issue

repo: dbeaver/dbeaver

license_type: permissive

license_source: github-api


text:
Add FK awareness (eg: Navigation Links) in Views

I have several views in my database for ease of navigation , eg, a subset of a table, or some prejoined tables.
But when one selects from a view, the displayed resultset in DBeaver does not recognized underlying foreign keys, and one loses the (very useful) features of Navigation Links.
This happens even for the simplest views, say CREATE VIEW v_mytable_a as select t.* from mytable t where kind  = 'A'
It would be nice if this feature is available.

Thank you for request.


text:
[SECURITY] drivers.xml file should be encrypted

Is your feature request related to a problem? Please describe.
When you manually add properties to a driver in dbeaver, they are visible clearly in the drivers.xml file. Several parameters such as password, certificates etc... are sensitive.
Describe the solution you'd like
It would be great to encrypt the drivers.xml file.

But.. drivers' configuration is not intended for connection-specific parameters, like credentials! Driver's configuration applied for all the database connections using this driver including connections of other users! If you want to set specific driver properties for a certain connection, you should use connection-specific driver properties in the corresponding connection's settings, not the global driver properties.

When you have hundreds of connections with ldap accounts whose passwords change regularly, you don't really have a choice... :(

So then its about sharing credentials between connections to simplify batch credentials update, not about driver configuration. =)

yes absolutely, you choose the way of implementation that seems cleanest to you.

It is not the way of implementation. With respect to the real problem, these are completely different features. DBeaver seems just doesn't cover your specific scenario by default, so to walk around this you used driver configuration to keep authentication parameters, which completely contradicts its purpose. As a result you've come up with a requirement to encrypt intentionally shared piece of configuration, which is available for modifications by design due to its purpose. While the real problem it that you needed completely different feature to fulfill your real needs: to be able to share credentials between connections and get centralized management of these shared credentials.
As far as i can tell from this issue, such a feature might be already available in PRO versions of DBeaver.

Thank you @ged-yuko
You're right, we have such feature in PRO editions. You can read more about it here https://github.com/dbeaver/dbeaver/wiki/Authentication-DBeaver-profile
@valentintraen you can try 14-days trial version https://dbeaver.com/trial/ to check if it's what you need

And what about the keyStorePassword propertie ?

@valentintraen, you can specify all connection parameters, including sensitive ones, in the Connection configuration->Connection settings->Driver properties. Then, they will be stored in connection configuration instead of drivers.xml and will not be shared with all connections.

Drivers configuration is not intended to be secure.

We made profiles  for such cases

authors: E1izabeth ged-yuko valentintraen


text:
Use of Connection General Filters for Schemas/Users broken with version 5.1.0

DBeaver - Version 5.1.0 CE
DBeaver JDBC driver: Microsoft
Operating System: Windows 7 / Windows 8.1 /  Windows 10
Database Server: Microsoft SQL Express 2014
The use of Connection filters for Schemas/Users seems to have been broken with DBeaver version 5.1.0.
Neither Include nor Exclude filtering works any more.
PS. Unsure if it misbehaves for other drivers than "Microsoft JDBC".
PPS. This looks like the same misbehaviour that I reported for DBeaver version 4.3.1.

I can't reproduce this. Schema or catalog filters works ok in our test env.
Could you post sample of filters, some screenshots would be also useful.

Hmmmm. The issue can be closed. My bad.
o My mistake as I got confused on the change in layout of the Filter links (ie. I clicked on the wrong link).
o Also tried out to filter Tables using the format . which did not work at all. Seems the table filter is only text based not anything where I can specify a specific schema.

Ok

authors: pdanie serge-rider


text:
Firebird SQL async "Event"

Firebird SQL event system
POST_EVENT  etc.
Exist java functions: http://firebirdsql.org/file/documentation/drivers_documentation/java/2.2.4/release_notes.html#__RefHeading__2757_1560579136
Documentation https://www.firebirdsql.org/file/documentation/papers_presentations/Power_Firebird_events.pdf
Examples https://github.com/FirebirdSQL/jaybird/wiki/Jaybird-Events-API

Prototypes
https://github.com/FirebirdSQL/jaybird/wiki/AsynchronousEventNotifier.java
https://github.com/FirebirdSQL/jaybird/wiki/SynchronousEventNotifier.java


text:
Connection to MariaDB via PAM failed since MariaDB Connector/J 2.5.1

DBeaver version 6.3.2.202001051908
Maxscale Version 2.4.5 and 2.4.6
MariaDB Version 10.4.10_4
MariaDB Connector/ J (trying versions 2.4.3, 2.5.0, 2.5.1 - 2,5,4
Connection to Maxscale via SSL

I connect to  MariaDB over MaxScale.
Connecting via Connector/J 2.4.3 - 2.5.0 works, but Connector/J 2.5.1+ does not and that MariaDB support mentioned a new feature was added which DBeaver may need to recheck its implementation for to ensure compatibility with 2.5.1+ (and provide them the link to https://jira.mariadb.org/browse/CONJ-738)
First connection via PAM works,after that I get error message:
Could not connect to HostAddress{host='mdb-tx.ads.provinzial.com', port=33012, type='master'}. PAM authentication request multiple passwords, but 'password3' is not set
The number after "password" growth by every new try.
Don't get entries in error log files..log

@Step-65 any luck on this?  Did you just have to downgrade your Connector until this is implemented?

Nothing changed but the versions of the involved products, for example I use the newest dbeaver 7.1.2
We get still the same error I wrote above.

@Step-65 Thanks.  I was using 2.6.0 and ran into this.  I was able to avoid it using 2.5.0 but I may try upgrading to 2.6.1 to see if that fixes it.

Sorry, my last statement wasn't correct:
I get the errors with connector 2.6.1., too.
Von:	"KC Baltz" notifications@github.com
An:	"dbeaver/dbeaver" dbeaver@noreply.github.com
Kopie:	"Step-65" Schnur@provinzial.com, "Mention"
mention@noreply.github.com
Datum:	16.07.2020 21:56
Betreff:	Re: [dbeaver/dbeaver] Connection to MariaDB via PAM failed
since MariaDB Connector/J 2.5.1 (#7903)
@Step-65 Thanks. I was using 2.6.0 and ran into this. I was able to avoid
it using 2.5.0 but I may try upgrading to 2.6.1 to see if that fixes it.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
Provinzial Rheinland Versicherung AG – Die Versicherung der Sparkassen ; Amtsgericht Düsseldorf HRB 41241;
Vorsitzende des Aufsichtsrats: Ulrike Lubek
Provinzial Rheinland Lebensversicherung AG – Die Versicherung der Sparkassen; Amtsgericht Düsseldorf HRB 41741;
Vorsitzender des Aufsichtsrats: Rainer Jahnke
Sitz der Gesellschaften: Provinzialplatz 1, D-40591 Düsseldorf;
Vorstände: Patric Fedlmeier, Vorsitzender; Guido Schaefers (Stv. Vors.), Dr. Volker Heinke, Sabine Krummenerl
www.provinzial.com
Bitte denken Sie an die Umwelt, bevor Sie diese E-Mail ausdrucken!

I am having the same issue with DBeaver 7.1.4 & Connector/J 2.6.2. The server is MariaDB 10.4.x. Switching back to Connector/J 2.5.0 did also avoid the issue for me.

I have the same issue with DBVisualizer 12.0.5 and MariaDB Connector/J 2.7.3 works for me

Seems to be fixed for now (22.0.1)

authors: Step-65 amitghosh-inwt houndegnonm kcbaltz uslss


text:
Why is the http maven repository configured and actually accessing the https repository

System information:

Operating system ：Windows 10 1909 18363.657
DBeaver version :  6.3.5.202002151353

Connection specification:

Maven Drivers download

Describe your question:
i want to download mysql driver by maven
and i configured a maven repository url with "http://maven.aliyun.com/repository/public/"

but I get an error when I click download
Error resolving dependencies
  Maven artifact 'maven:/mysql:mysql-connector-java:RELEASE' not found

the dbeaver-debug.log logs

> Start DBeaver UI Editors - Connections [org.jkiss.dbeaver.ui.editors.connection 1.0.18.202002151353]
> Start DBeaver MySQL Support [org.jkiss.dbeaver.ext.mysql 2.1.112.202002151353]
2020-02-28 22:43:48.109 - Open [http://maven.aliyun.com/repository/public/mysql/mysql-connector-java/5.1.44/mysql-connector-java-5.1.44.pom]
2020-02-28 22:43:48.181 - Retry number 2
2020-02-28 22:43:48.182 - Open [https://maven.aliyun.com/repository/public/mysql/mysql-connector-java/5.1.44/mysql-connector-java-5.1.44.pom]
2020-02-28 22:43:48.431 - Error loading version info: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
2020-02-28 22:43:48.432 - Error loading version info: D:\software\dbeaver\maven-local\mysql\mysql-connector-java\5.1.44\mysql-connector-java-5.1.44.pom (系统找不到指定的路径。)
2020-02-28 22:43:48.432 - Maven artifact 'mysql:mysql-connector-java:5.1.44' not found in any available repository.
2020-02-28 22:43:48.432 - Error resolving library 'mysql:mysql-connector-java:RELEASE' dependencies
java.io.IOException: Maven artifact 'maven:/mysql:mysql-connector-java:RELEASE' not found

I noticed the "http://maven.aliyun.com" change to "https://maven.aliyun.com/"
That's why the error occurred
but I do not know why
Can anyone help me about this issue? Thank you

Server http://maven.aliyun.com automatically redirects to its https version.
Recently HTTP maven repositories were banned (e.g. Maven Central no longer provides plain http access). Because using untrusted Maven repos are very dangerous.

@serge-rider  Thank you for your reply。Solved my problem

authors: ilisten serge-rider


text:
Added option to skip bind values during multi-row insert

Has changes for the below feature request
https://github.com/dbeaver/dbeaver/issues/13498
Thanks, @ShadelessFox for providing the approach. I have implemented the same.

Hi @LonwoLonwo
I noticed @akilovich mentioned in another OceanBase plugin thread that he would be on a vacation.
Do you know tentatively when you would be able to review this PR and which release this can be target to be released on?
It will be a huge performance improvement for our end users who are using DBeaver to access Redshift.

Generally looks good. I think that we may enable this parameter by default for some drivers (like Redshift).
I'll review it in details later this week.

@serge-rider  Thanks.

Let's merge it. We can improve UIX later.

source: gharchive/pull-request

authors: deepaksenthilkumar serge-rider


text:
#2407 Introduce @export command for running data transfer from SQL

https://user-images.githubusercontent.com/35821147/164252883-76c4a938-5c95-498e-8bad-42806c4e73cd.mp4

Verified


text:
#16597 add proper null monitor handling in getSchemas of GenericCatalog

Closes #16597
NULL monitor led to generic catalogs being counted as containing DBSTable instead of DBSSchema.

We can't fix it like this

authors: Destrolaric serge-rider


text:
#22916 [CUBRID] Add Query Plan Feature for the CUBRID plugin

Display query cost plan as table view
Show raw query plan in property

Hello @rathana-pvs
Thanks for your contribution.
We will look at it.

Please format your code according to our code style rules:

Place { at the same line where the method is declared
Use @NotNull/@Nullable annotations for method arguments and return type

Will it apply to the entire Cubrid plugin?

Will it apply to the entire Cubrid plugin?

Hello @rathana-pvs
This advice is only for your code.

What else do I need to do to get this PR merged into devel?

Hello @rathana-pvs,
It awaits our QA team. Once it passes the QA, it will be merged.

authors: LonwoLonwo ShadelessFox rathana-pvs


text:
Added .NET 4.5 console application as binary (Issue #22)

Added console application built with .NET 4.5 that is used in binary
unit tests. It will prove a bug in ResourceLib where unit tests will
succeed on atl.dll but fail on ConsoleApplication_NET4.5.exe.

@FantasticFiasco could you please check the current sources? Some more x64 issues have been fixed recently, which occured only in .NET 4.5.

Sorry but no. Don't get me wrong, I understand the purpose of open source, I'm a active contributor and collaborator to other GitHub projects, but this maintainer really rubbed me the wrong way. His lack of commitment to the project pushed me into looking for alternative solutions to my problem, and it didn't take many minutes to find a suitable one using Mono.Cecil.
I think you can be obnoxious and get away with it if what you are creating is truly remarkable. Obviously this isn't the case here.

@thoemmi thanks for digging this up and commenting
@fantasticfiasco thanks for your two cents

I'll continue @FantasticFiasco's work a the new PR #33 .

authors: FantasticFiasco dblock thoemmi

repo: dblock/resourcelib

license: mit

license_source: bigquery


text:
Control sampling rate

I would like to use this tool to extract some frames from image to train deep learning system.
The issue i have is too many similar frames generated.
Would it be possible to set constant sampling rate for video?
I.e show and annotate only two frames per second?

I think we can change the config in line 180 from https://github.com/dbolkensteyn/vatic.js/blob/master/index.html.

authors: Arsakes Peratham


text:
Branching update message incorrect when using dbpatch status

use 'dbpatch update branch=branch1' to apply the patches
need to be:
use 'dbpatch update --branch=branch1' to apply the patches

Fixed bug in develop [2537391083867c6e374e7c57c51afb2068a1144e]

repo: dbpatch/DbPatch


text:
[CT-2394] [Bug] Dropped tables causing error when following dbt-core Snowflake Quickstart tutorial

Is this a new bug in dbt-core?

[X] I believe this is a new bug in dbt-core
[X] I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior
Hi, I've been following the Quickstart, which refers to loading data here.
create warehouse transforming;
create database raw;
create database analytics;
create schema raw.jaffle_shop;
create schema raw.stripe;

create table raw.jaffle_shop.customers
( id integer,
  first_name varchar,
  last_name varchar
);

copy into raw.jaffle_shop.customers (id, first_name, last_name)
from 's3://dbt-tutorial-public/jaffle_shop_customers.csv'
file_format = (
    type = 'CSV'
    field_delimiter = ','
    skip_header = 1
    );

[...]

 select * from raw.jaffle_shop.customers; # lists current data

When executing the dbt run mentioned here at building my first model, I run into an issue where the table raw.jaffle_shop.customers is dropped first; after which it errors when trying to build the view because that same table is now missing. As a beginner following the quickstart, I have no idea why this is happening. It seems like it should be dropping any previous view rather than the table itself..
This is where the drop happens:
07:52:41.232530 [debug] [Thread-1  ]: Dropping relation "RAW"."JAFFLE_SHOP"."CUSTOMERS" because it is of type table

Full logs:
07:52:41.204799 [debug] [Thread-1  ]: Began running node model.jaffle_shop.customers
07:52:41.205882 [info ] [Thread-1  ]: 1 of 1 START sql view model jaffle_shop.customers .............................. [RUN]
07:52:41.206875 [debug] [Thread-1  ]: Acquiring new snowflake connection 'model.jaffle_shop.customers'
07:52:41.207172 [debug] [Thread-1  ]: Began compiling node model.jaffle_shop.customers
07:52:41.210659 [debug] [Thread-1  ]: Writing injected SQL for node "model.jaffle_shop.customers"
07:52:41.211423 [debug] [Thread-1  ]: Timing info for model.jaffle_shop.customers (compile): 2023-04-11 07:52:41.207378 => 2023-04-11 07:52:41.211338
07:52:41.211693 [debug] [Thread-1  ]: Began executing node model.jaffle_shop.customers
07:52:41.232530 [debug] [Thread-1  ]: Dropping relation "RAW"."JAFFLE_SHOP"."CUSTOMERS" because it is of type table
07:52:41.236138 [debug] [Thread-1  ]: Using snowflake connection "model.jaffle_shop.customers"
07:52:41.236307 [debug] [Thread-1  ]: On model.jaffle_shop.customers: /* {"app": "dbt", "dbt_version": "1.4.4", "profile_name": "jaffle_shop", "target_name": "dev", "node_id": "model.jaffle_shop.customers"} */
drop table if exists "RAW"."JAFFLE_SHOP"."CUSTOMERS" cascade
07:52:41.236440 [debug] [Thread-1  ]: Opening a new connection, currently in state closed
07:52:41.789535 [debug] [Thread-1  ]: SQL status: SUCCESS 1 in 1 seconds
07:52:41.799746 [debug] [Thread-1  ]: Writing runtime sql for node "model.jaffle_shop.customers"
07:52:41.801822 [debug] [Thread-1  ]: Using snowflake connection "model.jaffle_shop.customers"
07:52:41.802081 [debug] [Thread-1  ]: On model.jaffle_shop.customers: /* {"app": "dbt", "dbt_version": "1.4.4", "profile_name": "jaffle_shop", "target_name": "dev", "node_id": "model.jaffle_shop.customers"} */
create or replace   view raw.jaffle_shop.customers

   as (

with customers as (

    select
        id as customer_id,
        first_name,
        last_name

    from raw.jaffle_shop.customers

),

orders as (

    select
        id as order_id,
        user_id as customer_id,
        order_date,
        status

    from raw.jaffle_shop.orders

),

customer_orders as (

    select
        customer_id,

        min(order_date) as first_order_date,
        max(order_date) as most_recent_order_date,
        count(order_id) as number_of_orders

    from orders

    group by 1

),

final as (

    select
        customers.customer_id,
        customers.first_name,
        customers.last_name,
        customer_orders.first_order_date,
        customer_orders.most_recent_order_date,
        coalesce(customer_orders.number_of_orders, 0) as number_of_orders

    from customers

    left join customer_orders using (customer_id)

)

select * from final
  );
07:52:41.904929 [debug] [Thread-1  ]: Snowflake adapter: Snowflake query id: 01ab8d18-0000-21d9-0000-0000438d60c9
07:52:41.905339 [debug] [Thread-1  ]: Snowflake adapter: Snowflake error: 002003 (42S02): SQL compilation error:
Object 'RAW.JAFFLE_SHOP.CUSTOMERS' does not exist or not authorized.
07:52:41.905841 [debug] [Thread-1  ]: Timing info for model.jaffle_shop.customers (execute): 2023-04-11 07:52:41.211859 => 2023-04-11 07:52:41.905741
07:52:41.906167 [debug] [Thread-1  ]: On model.jaffle_shop.customers: Close
07:52:42.061190 [debug] [Thread-1  ]: Database Error in model customers (models/customers.sql)
  002003 (42S02): SQL compilation error:
  Object 'RAW.JAFFLE_SHOP.CUSTOMERS' does not exist or not authorized.
  compiled Code at target/run/jaffle_shop/models/customers.sql
07:52:42.061990 [debug] [Thread-1  ]: Sending event: {'category': 'dbt', 'action': 'run_model', 'label': '337f5b89-9516-4f13-aba0-80b5d2dcb876', 'context': [<snowplow_tracker.self_describing_json.SelfDescribingJson object at 0x105e94130>]}
07:52:42.062610 [error] [Thread-1  ]: 1 of 1 ERROR creating sql view model jaffle_shop.customers ..................... [ERROR in 0.86s]
07:52:42.064533 [debug] [Thread-1  ]: Finished running node model.jaffle_shop.customers
07:52:42.066379 [debug] [MainThread]: Acquiring new snowflake connection 'master'
07:52:42.067063 [debug] [MainThread]: Connection 'master' was properly closed.
07:52:42.067303 [debug] [MainThread]: Connection 'model.jaffle_shop.customers' was properly closed.
07:52:42.067562 [info ] [MainThread]:
07:52:42.067956 [info ] [MainThread]: Finished running 1 view model in 0 hours 0 minutes and 3.19 seconds (3.19s).
07:52:42.068411 [debug] [MainThread]: Command end result
07:52:42.075323 [info ] [MainThread]:
07:52:42.075751 [info ] [MainThread]: Completed with 1 error and 0 warnings:
07:52:42.076064 [info ] [MainThread]:
07:52:42.076352 [error] [MainThread]: Database Error in model customers (models/customers.sql)
07:52:42.076594 [error] [MainThread]:   002003 (42S02): SQL compilation error:
07:52:42.076866 [error] [MainThread]:   Object 'RAW.JAFFLE_SHOP.CUSTOMERS' does not exist or not authorized.
07:52:42.077114 [error] [MainThread]:   compiled Code at target/run/jaffle_shop/models/customers.sql
07:52:42.077334 [info ] [MainThread]:
07:52:42.077580 [info ] [MainThread]: Done. PASS=0 WARN=0 ERROR=1 SKIP=0 TOTAL=1
07:52:42.077895 [debug] [MainThread]: Sending event: {'category': 'dbt', 'action': 'invocation', 'label': 'end', 'context': [<snowplow_tracker.self_describing_json.SelfDescribingJson object at 0x104d02940>, <snowplow_tracker.self_describing_json.SelfDescribingJson object at 0x105ecf1f0>, <snowplow_tracker.self_describing_json.SelfDescribingJson object at 0x105ecf550>]}
07:52:42.078132 [debug] [MainThread]: Flushing usage events

Snowflake activity looks like this:

The only 2 relevant files (I think) in my project are dbt_project.yml and ./models/cusomters.sql:
# dbt_project.yml
name: 'jaffle_shop'
version: '1.0.0'
config-version: 2

profile: 'jaffle_shop'

model-paths: ["models"]
analysis-paths: ["analyses"]
test-paths: ["tests"]
seed-paths: ["seeds"]
macro-paths: ["macros"]
snapshot-paths: ["snapshots"]

target-path: "target"  # directory which will store compiled SQL files
clean-targets:         # directories to be removed by `dbt clean`
  - "target"
  - "dbt_packages"

models:
  jaffle_shop:
    +materialized: view

# ./models/customers.yml

{{
  config(
    materialized='view'
  )
}}

with customers as (

    select
        id as customer_id,
        first_name,
        last_name

    from raw.jaffle_shop.customers

),

orders as (

    select
        id as order_id,
        user_id as customer_id,
        order_date,
        status

    from raw.jaffle_shop.orders

),

customer_orders as (

    select
        customer_id,

        min(order_date) as first_order_date,
        max(order_date) as most_recent_order_date,
        count(order_id) as number_of_orders

    from orders

    group by 1

),

final as (

    select
        customers.customer_id,
        customers.first_name,
        customers.last_name,
        customer_orders.first_order_date,
        customer_orders.most_recent_order_date,
        coalesce(customer_orders.number_of_orders, 0) as number_of_orders

    from customers

    left join customer_orders using (customer_id)

)

select * from final

Expected Behavior
Run should succeed as shown in Quickstart tutorial.
Steps To Reproduce

Follow the dbt-core Quickstart tutorial
Execute dbt run
Observe error Object RAW.JAFFLE_SHOP.CUSTOMERS` does not exist or not authorized.

Relevant log output
No response
Environment
- OS: MacOS Ventura 13.3
- Python: 3.9.6
- dbt: 1.4.4 (snowflake 1.4.1)

Which database adapter are you using with dbt?
snowflake
Additional Context
No response

When I rename the file from ./models/customers.sql to ./models/customers_anything_else_really.sql it succeeds. Before it was generating this code in ./target/run:
# ./target/run/jaffle_shop/models/customers.sql

  create or replace   view raw.jaffle_shop.customers

   as (
   ...

Now it is creating:
# ./target/run/jaffle_shop/models/customers_test.sql

  create or replace   view raw.jaffle_shop.customers_test

   as (
   ...

Which does not drop my table. I'm still not sure why it was dropping the table when it says create or replace view ... initially though.

repo: dbt-labs/dbt-core


text:
Add Snowplow tracking for behavior flags

resolves #10552
Problem
We need to track deprecated states of behavior flags in Snowplow so that we get telemetry for both Cloud and Core users.
Solution
Handle the event that is already firing for logging with a callback that tracks the event in Snowplow.
Checklist

[x] I have read the contributing guide and understand what's expected of me.
[ ] I have run this code in development, and it appears to resolve the stated issue.
[x] This PR includes tests, or tests are not required or relevant for this PR.
[x] This PR has no interface changes (e.g., macros, CLI, logs, JSON artifacts, config files, adapter interface, etc.) or this PR has already received feedback and approval from Product or DX.
[x] This PR includes type annotations for new and modified functions.

@cla-bot check

I think these tests are failing due to updates in dbt-common on which this is dependent. I'll rerun the tests once that PR is merged; it's currently queued.


text:
Support additional linux builds

As a part of #51 we had to revert #45. Let's get this functionality back in, test the release process, and publish the additional wheels. If we have to release a new patch version that's fine since dbt-core should pick that up automatically now.

resolved via #53

repo: dbt-labs/dbt-extractor


text:
[CT-957] Refactor incremental materialization, using new incremental_strategy foundations

Follow up to https://github.com/dbt-labs/dbt-spark/issues/402, which implemented the minimal version to keep the current code working
See https://github.com/dbt-labs/dbt-snowflake/pull/196 for reference implementation:

Define valid_incremental_strategies
Add to materialization code:

    {#-- Get the incremental_strategy, the macro to use for the strategy, and build the sql --#}
    {% set incremental_strategy = config.get('incremental_strategy') or 'default' %}
    {% set incremental_predicates = config.get('incremental_predicates', none) %}
    {% set strategy_sql_macro_func = adapter.get_incremental_strategy_macro(context, incremental_strategy) %}
    {% set strategy_arg_dict = ({'target_relation': target_relation, 'temp_relation': tmp_relation, 'unique_key': unique_key, 'dest_columns': dest_columns, 'predicates': incremental_predicates }) %}
    {% set build_sql = strategy_sql_macro_func(strategy_arg_dict) %}

Take stock of remaining discrepancies between default + spark incremental materializations, identify opportunities for further refactor + eventual deduplication

As-of v1.7, dbt-spark currently only supports these incremental strategies:

append
merge
insert_overwrite

So it currently does not support this one:

delete+insert

https://docs.getdbt.com/docs/build/incremental-models#supported-incremental-strategies-by-adapter

Since ~dbt-core~ dbt-adapters has default definitions of append and delete+insert, it should be trivial for dbt-spark to support both of those during implementation of this issue.

repo: dbt-labs/dbt-spark


text:
Moving CI to GitHub actions

Description
resolves #3688

This PR moves our CI to GitHub actions. I created 4 workflows:
main.yml
This workflow is the "main" CI workflow. This will run on all PRs, pushes to mainline branches ('develop', '*.latest`, etc.), and when manually dispatched in the GitHub UI. Today this workflow run static code checks (mypy, flake8) and unit tests. This could also include other lint checks, formatting checks, etc. It is important that this workflow does not use any configured secrets or require a github token with write permissions. This workflow runs for PRs from forked repositories and GitHub Actions does not pass secrets to forks, so this workflow would fail if it tried to access them.
build.yml
This workflow ensures that dbt can be packaged and installed on linux, windows, and macos for python3.6-python3.9. It will run on all PRs, pushes to mainline branches ('develop', '*.latest`, etc.), and when manually dispatched in the GitHub UI. This stores python distributions (wheel and source) as well, this can be used in other workflows (build docker image, publishing, etc.). Again, like the main CI workflow, this workflow should not require secrets or a github token with write permissions to run. We'd like this run for all PRs, including PRs from outside contributors (forks).
integration.yml
This workflow runs all integration tests, for all supported platforms, python versions, and core adapters. It will run all combinations by default and will only run when pushing to mainline branches (develop, release branches, etc.) or when manually triggered via the GitHub UI. This is a trusted workflow, meaning that it can only be triggered by actions from trusted actors (folks with write access to the repo). That means we can use secrets without any additional checks.
integration-pr.yml
This workflow can be triggers by untrusted actors. Like the integration workflow, this run integration tests for some matrix of operating systems, python versions (well only python3.8 at the moment, but we can change that), and core adapters. It supports conditionally running all or additional tests using PR labels as well.
Be default, only integration test affected by the code changes in the PR will be run. The mapping of file changes and tests run can be found here: https://github.com/dbt-labs/dbt/blob/0d556de6994891561b408fe53ba8c521bc165730/.github/workflows/integration-pr.yml#L43-L55
If someone would like to run all tests or tests for a specific adapter, you can add a label to the pr to do so.
test all -> run all integration tests
test ${adapter} -> run tests for that specific ${adapter}
It also requires an additional check when the PR is from a forked repository. Right now, that additional check is a PR label ok to test. This extra check is needed to ensure that outside contributors do not exploit any secrets or compute. Since this action runs on the pull_request_target event, it is important to note that the action runs in the context of the "target" of a PR. So, for a PR pointing at the develop branch, the action will run on the develop branch, but also include all secrets and even a github token with write permissions. We explicitly checkout the head of the branch that the PR is coming from in order to run checks against the code to be merged. Since only folks with write access to the repo can add labels to PRs, we can ensure that the PR is coming from a trusted actor. Please see https://securitylab.github.com/research/github-actions-preventing-pwn-requests/ for more info why we do this.
Additional notes
While testing these new workflows, I discovered an issue with python3.9 unit tests. I have turned them off for the time being and created () to follow up with a fix. https://github.com/dbt-labs/dbt/blob/0d556de6994891561b408fe53ba8c521bc165730/.github/workflows/main.yml#L34
I think there is still work to be done to increase the reliability and trust in our test suite, but I believe that this PR will contribute towards that.
Checklist

[x] I have signed the CLA
[x] I have run this code in development and it appears to resolve the stated issue
[x] This PR includes tests, or tests are not required/relevant for this PR
[ ] I have updated the CHANGELOG.md and added information about my change to the "dbt next" section.

Still need to update repo secrets with the relevant warehouse credentials in order to integration tests to work.

repo: dbt-labs/dbt


text:
Getting Started With the dbt Semantic Layer: How To Metric

Contact Details
@callummccann
I have read the dbt Developer Blog contribution guidelines.

[X] I have read the dbt Developer Blog contribution guidelines.

Which of these best describes you?

[X] I am a dbt Community member or partner contributing to the Developer Blog
[X] I work for dbt Labs and am creating this issue for a community or marketing approved piece.

What is the topic of your post?
This blog covers what the semantic layer is, what components it is built from, and how to use it today and in the future! It is the devhub companion blog post to a soon-to-be released product post from Drew on the Semantic Layer.
Link to an initial outline.
https://www.notion.so/dbtlabs/Getting-Started-With-The-dbt-Semantic-Layer-To-Metric-Or-Not-To-Metric-46e562ec6f1549b3b5e6af2a483d8439

Hey @callum-mcdata can we close this out now :)

Let it close!

authors: KiraFuruichi callum-mcdata


text:
Adapter constraint support tables

Preview
What are you changing in this pull request and why?
Adding tables outlining adapter-specific constraint support to the model contracts page
Checklist

[x] Review the Content style guide and About versioning so my content adheres to these guidelines.
[x] Add a checklist item for anything that needs to happen before this PR is merged, such as "needs technical review" or "change base branch."

yep i prefer that @dbeatty10 ! i was going to suggest changing the table but i didn't want to mess anything going on between yall. separating them out is clearer!
i still think having a paragraph explaining what supported and enforced or not enforced means in this context is helpful -- just to be super clear with users.

@dbeatty10 Thank you for that context - much clearer and that makes the tables easier to follow. Will implement.


text:
Package storage blog post

What are your changes?
Adding a blog post describing the new local package storage feature in DC/OS 1.9
What is the urgency level of this change?

[ ] Blocker
[X] High (need to release on Jan 10)
[ ] Medium

I have completed these items:

[ ] I have built locally and tested for broken links and formatting.
[ ] If appropriate, I have added redirects.

If you included a comment with your commit, it appears here:

@jsancio @larioj @joel-hamill this is the first draft. Some parts likely need more elaboration. I'd appreciate any feedback!

It's not critical to release a blog post for 1.9, so closing this for now.

repo: dcos/dcos-website


text:
Added redirect for moved security topic

What are your changes?
Added redirect for moved security topic
What is the urgency level of this change?

[ ] Blocker
[ ] High
[x] Medium

I have completed these items:

[ ] I have built locally and tested for broken links and formatting.
[x] If appropriate, I have added redirects.

If you included a comment with your commit, it appears here:

duplicate. already on develop/master

authors: joel-hamill karlkfi


text:
Bump dcos-mesos to 1.2.0-rc2

High Level Description
Bumps dcos-mesos to the official Apache Meso 1.2.0-rc2 tag to include such critical fixes as:
e1c11f0 Fixed fetcher to not pick up environment variables it should not see.
4683320 Fixed nested container agent flapping issue after reboot.
056978a Modified the executor driver to always relink on agent failover.
12e99f7 Fixed a bug around executor not able to use reserved resources.
d80af6c Fixed a crash on the default executor due to a failed invariant check.
7e5439d Fixed a crash on the agent when handling the SIGUSR1 signal.
e53fcaf Fixed a crash on the master upon receiving an invalid inverse offer.

Related Issues

CORE-864 Mesos masters crashing after receiving inverse offers
CORE-779 Bump dcos-mesos to Mesos 1.2 (when ready)

Checklist for all PR's

[x] Included a test which will fail if code is reverted but test is not. If there is no test please explain here: Relying on Apache Mesos unit tests and existing (and continuously improving) dcos-integration-tests.
[x] Read the DC/OS contributing guidelines
[x] Followed relevant code rules Rules for Packages and Systemd

Checklist for component/package updates:

[x] Change log from the last version integrated: https://github.com/mesosphere/mesos/compare/e619e9ff2cd7e6cf0397660bd4cbfb9a5549ecbe...dfd332085e9dec451239aa17102d912e909f8a98
https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=1.2.0-rc2
[x] Test Results: https://jenkins.mesosphere.com/service/jenkins/job/mesos/job/Mesos_CI-build/391
[x] Code Coverage (if available): N/A

@mesosphere-mergebot bump-ee

I checked out the branch that this PR bumps Mesos to - the cherry-picks included there look good to me. 🚢

Rebased on latest dcos/dcos master.

@mesosphere-mergebot bump-ee

@mesosphere-mergebot bump-ee

authors: adam-mesos greggomann

repo: dcos/dcos


text:
[master] Bump Mesos to nightly master 9171af20eda9ee31b75e86dc833e06a6d856d329

High-level description
This is a routine bump to the latest Mesos and mesos-modules.
Related JIRA Issues
Checklist for all PRs

[ ] Included a test which will fail if code is reverted but test is not. If there is no test please explain here:
[x] Read the DC/OS contributing guidelines
[x] Followed relevant code rules Rules for Packages and Systemd

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

[x] Changelog:
https://github.com/apache/mesos diff
https://github.com/dcos/dcos-mesos-modules diff

[ ] Test Results: [link to CI job test results for component]

[ ] Code Coverage (if available): [link to code coverage report]

@mesosphere-mergebot bump-ee

This repo has @mesosphere-mergebot integration. You can interact with the following commands.
@mesosphere-mergebot override-status
@mesosphere-mergebot merge-it
@mesosphere-mergebot label [Ready For Review |Holding |Request For Comment |Ship It |Work In Progress]
@mesosphere-mergebot bump-ee

PR creators can apply one of  [Ready For Review |Work In Progress]. Owners can apply any label.


text:
Bump telegraf version, introducing dcos related metrics

High-level description
This PR bumps telegraf to include two custom input plugins, a prometheus output, and related configuration. It builds on top of #3120.
Corresponding DC/OS tickets (obligatory)
These DC/OS JIRA ticket(s) must be updated (ideally closed) in the moment this PR lands:

DCOS_OSS-3716 Write a Telegraf input plugin to get data for each container
DCOS_OSS-3717 Add Mesos service discovery to the Telegraf prometheus metrics input plugin

Checklist for all PRs

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

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

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

@mesosphere-mergebot bump-ee

@mesosphere-mergebot bump-ee

@mesosphere-mergebot label ready for review

@branden and @klueska , mind giving this a look over?

@mesosphere-mergebot bump-ee

@mesosphere-mergebot bump-ee

Closing this out; these changes would make metrics temporarily less useful on master and we have been asked not to take the incremental approach.


text:
[1.13] Support large uploads and processing times for services via AR

High-level description
Backport #5376 to 1.13
Support large uploads and long processing times for services accessed through Admin Router's /service endpoint. This supports package upload, required for package registries launched using Marathon.
This has been tested manually using the 10GB beta-mesosphere-jupyter-service-1.3.0-0.35.4-beta.dcos package.
There is a separate issue DCOS-51222 for creation of an integration test. I consider this separation to be appropriate in this case, as there are non-trivial problems to be overcome for the test (time and bandwidth usage).
Corresponding DC/OS tickets (obligatory)
These DC/OS JIRA ticket(s) must be updated (ideally closed) in the moment this PR lands:

DCOS-52768 COPS-4651 repo 413 Entity too large / 504 timeout

Related tickets (optional)
Other tickets related to this change:

COPS-4651 413 Entity Too Large error when trying to add any packages where the .dcos bundled file is over 1 GB

Checklist for all PRs

[x] Added a comprehensible changelog entry to CHANGES.md or explain why this is not a user-facing change:
[ ] Included a test which will fail if code is reverted but test is not. If there is no test please explain here: Manually tested. Testing requires a large (10GB) download/upload, which takes significant time and bandwidth.
[x] Read the DC/OS contributing guidelines
[x] Followed relevant code rules Rules for Packages and Systemd

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

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

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

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

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

The conflict in CHANGES.md will probably be fine as of the union merge strategy that Mergebot applies for CHANGES.md, but to be sure this PR should probably be rebased onto the current head of the 1.13 branch.

@mesosphere-mergebot label Ready For Review

authors: jgehrcke jongiddy


text:
[1.12] Bump Mesos to nightly 1.7.x 869df35

High-level description
This is a routine bump to the latest Mesos and mesos-modules.
Related JIRA Issues
Checklist for all PRs

[ ] Included a test which will fail if code is reverted but test is not. If there is no test please explain here:
[x] Read the DC/OS contributing guidelines
[x] Followed relevant code rules Rules for Packages and Systemd

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

[x] Changelog:
https://github.com/apache/mesos/compare/71685b5c807e4d4d1a5ebe33a3c3c0a2f824b9b4...869df3552dcd97db2b62d2207eba3099ea823084

[ ] Test Results: [link to CI job test results for component]

[ ] Code Coverage (if available): [link to code coverage report]

@mesosphere-mergebot bump-ee

@mesosphere-mergebot label Ready For Review


text:
Two Features

I added two features :

The game will ask for words, if the user did not wrote any words in the main page before. ( A game can't start without words..)
The game will give the opportunity to go back to main page if and only if the game is done. That means if user has 4 words and all 4 has been done, the user will be asked if he wants to add more words afterwards. So he can be redirected to main page at will.

thank you!

thank you!

repo: dcselek/react-game-of-word

license: MIT


text:
🛑 Danbs is down

In 9fd6c53, Danbs (https://danbs.net) was down:

HTTP code: 404
Response time: 126 ms

Resolved: Danbs is back up in cecede4 after 50 minutes.

repo: ddanbs/upptime


text:
🛑 Danbs is down

In d974a52, Danbs (https://danbs.net) was down:

HTTP code: 404
Response time: 2902 ms

Resolved: Danbs is back up in c19fcc1 after 8 minutes.


text:
🛑 Danbs is down

In dffa9f5, Danbs (https://danbs.net) was down:

HTTP code: 404
Response time: 123 ms

Resolved: Danbs is back up in 7ce3ec6 after 16 minutes.


text:
🛑 Danbs is down

In 9046e82, Danbs (https://danbs.net) was down:

HTTP code: 404
Response time: 102 ms

Resolved: Danbs is back up in 5ba3cd6.


text:
🛑 Danbs is down

In 953e0e9, Danbs (https://danbs.net) was down:

HTTP code: 404
Response time: 101 ms

Resolved: Danbs is back up in 143636d.


text:
🛑 Danbs is down

In 2aee318, Danbs (https://danbs.net) was down:

HTTP code: 404
Response time: 166 ms

Resolved: Danbs is back up in 0e7114b.


text:
🛑 Danbs is down

In 6f94b9d, Danbs (https://danbs.net) was down:

HTTP code: 404
Response time: 94 ms

Resolved: Danbs is back up in 8246f8e.


text:
打开了OnlineMode验证的服务器进不去

有没有兴趣加上给微软的正版验证？
这个假人项目好多服务器都很有需求

发现问题不在OnlineMode
而是FakePlayer与白名单冲突
将白名单关闭之后就可以正常使用了

我是憨批
白名单里把xuid删了就能进了

假人在正确配置公钥后可以通过正版验证
如果服务器开启了白名单，需要手动将假人添加到白名单

假人在正确配置公钥后可以通过正版验证
如果服务器开启了白名单，需要手动将假人添加到白名单

蟹蟹指导~这个假人挺好用的


text:
Streaming a possible list and expecting only one answer is needed?

https://github.com/de4a-wp5/de4a/blob/d47997f6deda975bc61f036432c1494e96ae3276/de4a-connector/src/main/java/eu/de4a/connector/api/manager/ResponseManager.java#L125
This method takes a list of files but ONLY cares about the first found. Is this actually intended behaviour? What if there are 10 files in the list? How do we know they are not all needed?

It is an intended behaviour, it will be only one attached file, that would be modified along with: TODO

authors: aosunacab daffyDukk


text:
fix(gui): added loader to credit history panel

@eKatchko
A load-indicator is added to project overview at credit history panel. "creditHistoryLoaded" in overview.component.ts controls when the loader should be shown, it is set to true after the first time credit history is fetched.
Try to fulfill the following points before the Pull Request is merged:

[ ] Give a meaningfull description for the PR
[ ] The PR is reviewed by one of the team members.
[ ] It must be checked if anything in the Readme must be adjusted (development-, production-, setup).
[ ] It must be checked if any section in the wiki (https://cloud.denbi.de/wiki/) should be adjusted.
[ ] If the PR is merged in the master then a release should be be made.
[ ] The PR is responsive on smaller screens.
[ ] If the requirements.txt have changed, check if the patches still work
[ ] If the new code is readable, if not it should be well commented
[ ] In case the code is not well commented: An respectice commenting issue with tag "important" is opened.
[ ] If a squash of commits is required, it has been performed or will be performed at final merge
[ ] Finally a second team member checks if all requirements met

For releases only:

[ ] If the review of this PR is approved and the PR is followed by a release then the .env file
in the cloud-portal repo should also be updated.

Works - the only problem at the moment is when you load a project overview and after loading the credits - creditHistoryLoaded is set to true and you go directly to the overview of another project the value is still set to true.
This is because the page is not recreated but only ngOninit is loaded again - for this creditsHistoryLoaded would have to be set - either in the ngOninit  or simply at the beginning of the fetchCreditHistoryOfProject method (which I would prefer) - to false.

Looks great, just one addition: could you move 'this.creditHistoryLoaded = false;' from the 'fetchCreditHistoryOfProject' function to the 'ngOnInit' function right after 'clearInterval(this.updateCreditsHistoryIntervals);'?
When it is set to false inside the 'fetchCreditHistoryOfProject' function, everytime new history data is requested from the api the loading indicator is shown and one can not read the history data for this period of time.

authors: dweinholz eKatchko qqmok

repo: deNBI/cloud-portal-webapp


text:
Visual Studio theme

I suggest adding a theme from Visual Studio in the themes for the editor. Because a lot of people are used to working there!

I think I already have a look!

repo: deadlyjack/Acode


text:
Last item disappears when sorting

Hello.
When I move the last item to an other place, it renderers it, in the correct position, but it's "invisible".
If I try to place an item on top of this "invisible" item, that item is also becomes "invisible".
I tried to reproduce it in a snack, but I couldn't.
I checked, every item gets rendered after sorting. The strange thing to me, that it leaves exactly as much empty place as the component itself.
Did someone encountered similar bug?

I am encountering the same problem you have described.


text:
UI: Add finish button on wizard step 2

Since the last 3 steps of the create connector wizard are optional, the user should be able to 'Finish' the wizard after validating the properties on step 2.  Add a separate Finish button in addition to Next after validating, which will allow the user to Finish without clicking thru the last 3 steps

Pr raised https://github.com/debezium/debezium-ui-poc/pull/129

pr merged.

authors: indraraj mdrillin

repo: debezium/debezium-ui-poc


text:
Update confirmation dialog

Addresses issue #198 , partial #197

update the patternfly version to get updates to modal
made updates to ConfirmationDialog, allows dialog to choose the correct title icon based upon the type
change dialog title to sentence case per UX request
minor update to readme to specify node version requirement
add styling to kafka connect selector

Closing this PR - will resubmit


text:
[tutorial] Added missing step when deleting customers

I've followed the tutorial and I got to the step when we had to delete a customer.
When running:
DELETE FROM customers WHERE id=1004;

I got back:
ERROR 1451 (23000): Cannot delete or update a parent row: a foreign key constraint fails (`inventory`.`addresses`, CONSTRAINT `addresses_ibfk_1` FOREIGN KEY (`customer_id`) REFERENCES `customers` (`id`))

So I added some instructions on deleting this entry first before continuing.

Ah yes, good addition. The addresses table was added later on and nobody thought of this implication in the tutorial. Thanks!

authors: gunnarmorling theodesp

repo: debezium/debezium


text:
chore(main): release 0.8.0

:robot: I have created a release beep boop
0.8.0 (2024-09-07)
Features

add Docker (3675235)

Bug Fixes

fix the url links and add some (efc0a18)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v0.8.0
:sunflower:

repo: debrid/wiki


text:
Update Next.js version

Description
Notes
Issue / Notion doc (if applicable)
Testing
Screenshots (if applicable)

Closing this in favor of https://github.com/decent-dao/fractal-interface/pull/1264

authors: herbig mudrila

repo: decent-dao/fractal-interface


text:
Is the demo broken for some reason?

I am unable to get the did of the participants. It shows an error in the console.

Thanks

This is a problem related to the DID of the mediator used by default. We're investigating! Thanks for the report.

If you refresh (with cache clearing), https://demo.didcomm.org should be working again :slightly_smiling_face:

authors: SuryaSHalwasia dbluhm

repo: decentralized-identity/didcomm-demo


text:
Downloads are super slow

Am i the only one that has slow download speed? Again its not my wifi because when im downloading normally on chrome it fast not like in the app. I even tried to download 1 at a time but its still slow.
To Reproduce
Steps to reproduce the behavior:

Go to any anime
Click on download in 1080p
See error/bug

android 11
1.2.1
Realme8pro

Additional context
Just want to make sure if this is an app problem or just me

I am not getting much faster speeds than on chrome. Their servers are just slow. Use the manual download picker to pick other servers if available.

repo: deceptions/no


text:
Unable to install  getting error

Environment:
image: python:3.9.13-alpine3.15
Collecting pylbfgs==0.2.0.13 (from -r /tmp/tmpnqe55yh1 (line 173))
111.3   Downloading PyLBFGS-0.2.0.13.tar.gz (105 kB)
111.3      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 105.2/105.2 kB 4.8 MB/s eta 0:00:00
111.4   Installing build dependencies: started
120.7   Installing build dependencies: finished with status 'done'
120.7   Getting requirements to build wheel: started
121.4   Getting requirements to build wheel: finished with status 'error'
121.5   error: subprocess-exited-with-error
121.5
121.5   × Getting requirements to build wheel did not run successfully.
121.5   │ exit code: 1
121.5   ╰─> [53 lines of output]
121.5       Compiling lbfgs/_lowlevel.pyx because it changed.
121.5       [1/1] Cythonizing lbfgs/_lowlevel.pyx
121.5       /tmp/pip-build-env-4zuuu0hm/overlay/lib/python3.9/site-packages/Cython/Compiler/Main.py:381: FutureWarning: Cython directive 'language_level' not set, using '3str' for now (Py3). This has changed from earlier releases! File: /tmp/pip-install-c3shc_f2/pylbfgs_5d43d814162f405a9fc40586d659ea84/lbfgs/_lowlevel.pyx
121.5         tree = Parsing.p_module(s, pxd, full_module_name)
121.5
121.5       Error compiling Cython file:
121.5       ------------------------------------------------------------
121.5       ...
121.5
121.5               x_a = aligned_copy(x0.ravel())
121.5
121.5               try:
121.5                   callback_data = (f, progress, x0.shape, args)
121.5                   r = lbfgs(n, x_a, fx_final, call_eval,
121.5                                               ^
121.5       ------------------------------------------------------------
121.5
121.5       lbfgs/_lowlevel.pyx:395:40: Cannot assign type 'lbfgsfloatval_t (void *, lbfgsconst_p, lbfgsfloatval_t *, int, lbfgsfloatval_t) except? -1' to 'lbfgs_evaluate_t'
121.5
121.5       Error compiling Cython file:
121.5       ------------------------------------------------------------
121.5       ...
121.5               x_a = aligned_copy(x0.ravel())
121.5
121.5               try:
121.5                   callback_data = (f, progress, x0.shape, args)
121.5                   r = lbfgs(n, x_a, fx_final, call_eval,
121.5                             call_progress, <void *>callback_data, &self.params)
121.5                             ^
121.5       ------------------------------------------------------------
121.5
121.5       lbfgs/_lowlevel.pyx:396:22: Cannot assign type 'int (void *, lbfgsconst_p, lbfgsconst_p, lbfgsfloatval_t, lbfgsfloatval_t, lbfgsfloatval_t, lbfgsfloatval_t, int, int, int) except? -1' to 'lbfgs_progress_t'
121.5       Traceback (most recent call last):
121.5         File "/usr/local/lib/python3.9/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 353, in
121.5           main()
121.5         File "/usr/local/lib/python3.9/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 335, in main
121.5           json_out['return_val'] = hook(**hook_input['kwargs'])
121.5         File "/usr/local/lib/python3.9/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 118, in get_requires_for_build_wheel
121.5           return hook(config_settings)
121.5         File "/tmp/pip-build-env-4zuuu0hm/overlay/lib/python3.9/site-packages/setuptools/build_meta.py", line 341, in get_requires_for_build_wheel
121.5           return self._get_build_requires(config_settings, requirements=['wheel'])
121.5         File "/tmp/pip-build-env-4zuuu0hm/overlay/lib/python3.9/site-packages/setuptools/build_meta.py", line 323, in _get_build_requires
121.5           self.run_setup()
121.5         File "/tmp/pip-build-env-4zuuu0hm/overlay/lib/python3.9/site-packages/setuptools/build_meta.py", line 487, in run_setup
121.5           super(_BuildMetaLegacyBackend,
121.5         File "/tmp/pip-build-env-4zuuu0hm/overlay/lib/python3.9/site-packages/setuptools/build_meta.py", line 338, in run_setup
121.5           exec(code, locals())
121.5         File "", line 27, in
121.5         File "/tmp/pip-build-env-4zuuu0hm/overlay/lib/python3.9/site-packages/Cython/Build/Dependencies.py", line 1134, in cythonize
121.5           cythonize_one(*args)
121.5         File "/tmp/pip-build-env-4zuuu0hm/overlay/lib/python3.9/site-packages/Cython/Build/Dependencies.py", line 1301, in cythonize_one
121.5           raise CompileError(None, pyx_file)
121.5       Cython.Compiler.Errors.CompileError: lbfgs/_lowlevel.pyx
121.5       [end of output]
121.5
121.5   note: This error originates from a subprocess, and is likely not a problem with pip.
121.5 error: subprocess-exited-with-error
121.5
121.5 × Getting requirements to build wheel did not run successfully.
121.5 │ exit code: 1
121.5 ╰─> See above for output.
121.5
121.5 note: This error originates from a subprocess, and is likely not a problem with pip.
122.2 Traceback (most recent call last):
122.2   File "/usr/local/bin/pip-sync", line 8, in
122.2     sys.exit(cli())
122.2   File "/usr/local/lib/python3.9/site-packages/click/core.py", line 1157, in call
122.2     return self.main(*args, **kwargs)
122.2   File "/usr/local/lib/python3.9/site-packages/click/core.py", line 1078, in main
122.2     rv = self.invoke(ctx)
122.2   File "/usr/local/lib/python3.9/site-packages/click/core.py", line 1434, in invoke
122.2     return ctx.invoke(self.callback, **ctx.params)
122.2   File "/usr/local/lib/python3.9/site-packages/click/core.py", line 783, in invoke
122.2     return __callback(*args, **kwargs)
122.2   File "/usr/local/lib/python3.9/site-packages/piptools/scripts/sync.py", line 203, in cli
122.2     sync.sync(
122.2   File "/usr/local/lib/python3.9/site-packages/piptools/sync.py", line 263, in sync
122.2     run(  # nosec
122.2   File "/usr/local/lib/python3.9/subprocess.py", line 528, in run
122.2     raise CalledProcessError(retcode, process.args,
122.2 subprocess.CalledProcessError: Command '['/usr/local/bin/python', '-m', 'pip', 'install', '-r', '/tmp/tmpnqe55yh1']' returned non-zero exit status 1.

First guess would be a cython 3 incompatibility?
Maybe as a hotfix we can limit the build dependency to a version earlier than 3.0.

Hello @fzimmermann89
Thanks for your reply, I really appreciate it, I am new to docker, Could you guide me to do it?

For now, you may use
pip install git+https://github.com/fzimmermann89/pylbfgs.git@fzimmermann89-cython to install a fixed version

So just to clarify: the source of the issue in Cython 3.0 isn't compatible because we've changed the default behaviour of cdef functions to be able to propagate exceptions. This means that you can't assign them to a function point where the function pointer expects a function that won't propagate exceptions.
This is an incompatible change, but by design. We're going to improve the error message a little in the next release I think to give a bit more guidance about how to fix it.
The solution is likely to add noexcept to functions that are used as pointers.

Thanks @da-woods

Any update on this one we are unable to deploy our app due to this

Hello @fzimmermann89
I need to build a Django docker image, in my requirement file this module is dependent Since I am unable to install this, I can't build a docker image can you suggest me anything?

So you have a requirements.txt that specifies this package?
And this requirements.txt you use in a docker file?
If yes, either do the pip install mentioned above before installing the requirements.txt contents,
or specify  the dependency in the requirements.txt as:
pylbfgs @ git+https://github.com/fzimmermann89/pylbfgs.git@fzimmermann89-cython
to install a fixed version.

Hello @fzimmermann89
Thanks working.

authors: da-woods fzimmermann89 iamMohamed

repo: dedupeio/pylbfgs


text:
deep select returns empty array of lnks in plv8 handler

How to reproduce

Login as admin
Create Type contained in admin
Create SyncTextFile contained in admin with this value:

({ deep, data: { newLink, triggeredByLinkId } }) => {
    throw new Error(
      JSON.stringify(
        deep.select(newLink.id)
      )
    )
}

Create Handler from plv8SupportsJs to your syncTextFile
Create HandleUpdate from your type to Handler
Insert Value from your type to String
Insert a link of your type
Update value of your link
See error. See that deep.select returns empty array of links

Error: DeepClient Insert Error: {"data":[]}

Additional Info
I have created my Deep workspace in gitpod approximately a few days ago

Tests:
gitpod /workspace/dev/packages/deeplinks (main) $ npm run test -- --testNamePattern "sync handlers"

> @deep-foundation/deeplinks@0.0.322 test
> npm run package:build && cross-env DEEPLINKS_HASURA_PATH=localhost:8080 DEEPLINKS_HASURA_SSL=0 DEEPLINKS_HASURA_SECRET=myadminsecretkey DOCKER_DEEPLINKS_URL=http://localhost:3006 NODE_OPTIONS=--experimental-vm-modules jest --config jest.config.js *.js --testTimeout=50000 --testNamePattern sync handlers

> @deep-foundation/deeplinks@0.0.322 package:build
> tsc --project tsconfig.json

(node:209984) ExperimentalWarning: VM Modules is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)

ReferenceError: You are trying to `import` a file after the Jest environment has been torn down. From react.test.js.

ReferenceError: You are trying to `import` a file after the Jest environment has been torn down. From react.test.js.

ReferenceError: You are trying to `import` a file after the Jest environment has been torn down. From react.test.js.

ReferenceError: You are trying to `import` a file after the Jest environment has been torn down. From react.test.js.

ReferenceError: You are trying to `import` a file after the Jest environment has been torn down. From react.test.js.

 FAIL   dom  ./react.test.js
  ● Test suite failed to run

    Jest encountered an unexpected token

    Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax.

    Out of the box Jest supports Babel, which will be used to transform your files into valid JS based on your Babel configuration.

    By default "node_modules" folder is ignored by transformers.

    Here's what you can do:
     • If you are trying to use ECMAScript Modules, see https://jestjs.io/docs/ecmascript-modules for how to enable it.
     • If you are trying to use TypeScript, see https://jestjs.io/docs/getting-started#using-typescript
     • To have some of your "node_modules" files transformed, you can specify a custom "transformIgnorePatterns" in your config.
     • If you need a custom transformation specify a "transform" option in your config.
     • If you simply want to mock your non-JS modules (e.g. binary assets) you can stub them out with the "moduleNameMapper" config option.

    You'll find more details and examples of these config options in the docs:
    https://jestjs.io/docs/configuration
    For information about custom transformations, see:
    https://jestjs.io/docs/code-transformation

    Details:

    /workspace/dev/node_modules/@react-hook/debounce/dist/module/index.js:1
    ({"Object.<anonymous>":function(module,exports,require,__dirname,__filename,jest){import * as React from 'react';
                                                                                ^^^^^^

    SyntaxError: Cannot use import statement outside a module

      at Runtime.createScriptFromCode (../../node_modules/jest-runtime/build/index.js:1505:14)

ReferenceError: You are trying to `import` a file after the Jest environment has been torn down. From react.test.js.

ReferenceError: You are trying to `import` a file after the Jest environment has been torn down. From react.test.js.

ReferenceError: You are trying to `import` a file after the Jest environment has been torn down. From react.test.js.

ReferenceError: You are trying to `import` a file after the Jest environment has been torn down. From react.test.js.

ReferenceError: You are trying to `import` a file after the Jest environment has been torn down. From react.test.js.

ReferenceError: You are trying to `import` a file after the Jest environment has been torn down. From react.test.js.

(node:209990) ExperimentalWarning: VM Modules is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
(node:209983) ExperimentalWarning: VM Modules is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
  console.log
    11

      at log (tests/sync-handlers.ts:768:19)

  console.log
    123

      at log (tests/sync-handlers.ts:770:19)

  console.log
    error Bad Request {
      internal: {
        statement: `select links__sync__handlers__deep__client(380::bigint, 'select', '{"id":1}'::jsonb, '{"table":"strings"}'::jsonb)`,
        prepared: false,
        error: {
          exec_status: 'FatalError',
          hint: null,
          message: 'select not from "links" not permitted',
          status_code: 'XX000',
          description: null
        },
        arguments: []
      },
      path: '$.args',
      error: 'query execution failed',
      code: 'postgres-error'
    }

      at Object.HasuraApi.defaultErrorHandler [as errorHandler] (../../node_modules/@deep-foundation/hasura/api.tsx:22:45)

  console.log
    error Bad Request {
      internal: {
        statement: `select links__sync__handlers__deep__client(2137::bigint, 'insert', '{"type_id":23}'::jsonb, '{}'::jsonb)`,
        prepared: false,
        error: {
          exec_status: 'FatalError',
          hint: null,
          message: 'Insert not permitted',
          status_code: 'XX000',
          description: null
        },
        arguments: []
      },
      path: '$.args',
      error: 'query execution failed',
      code: 'postgres-error'
    }

      at Object.HasuraApi.defaultErrorHandler [as errorHandler] (../../node_modules/@deep-foundation/hasura/api.tsx:22:45)

  console.log
    error Bad Request {
      internal: {
        statement: `select links__sync__handlers__deep__client(2183::bigint, 'insert', '{"type_id":23}'::jsonb, '{}'::jsonb)`,
        prepared: false,
        error: {
          exec_status: 'FatalError',
          hint: null,
          message: 'Insert not permitted',
          status_code: 'XX000',
          description: null
        },
        arguments: []
      },
      path: '$.args',
      error: 'query execution failed',
      code: 'postgres-error'
    }

      at Object.HasuraApi.defaultErrorHandler [as errorHandler] (../../node_modules/@deep-foundation/hasura/api.tsx:22:45)

  console.log
    error Bad Request {
      internal: {
        statement: `select links__sync__handlers__deep__client(2233::bigint, 'insert', '{"type_id":2263, "from_id": 2302, "to_id": 2218}'::jsonb, '{}'::jsonb)`,
        prepared: false,
        error: {
          exec_status: 'FatalError',
          hint: null,
          message: 'insert [{"id":2303,"from_id":2302,"to_id":2218,"type_id":2263}] rejected because selector_id: 2290 query_id: 2293 user_id: 2233 return false',
          status_code: 'P0001',
          description: null
        },
        arguments: []
      },
      path: '$.args',
      error: 'query execution failed',
      code: 'postgres-error'
    }

      at Object.HasuraApi.defaultErrorHandler [as errorHandler] (../../node_modules/@deep-foundation/hasura/api.tsx:22:45)

  console.log
    error Bad Request {
      internal: {
        statement: `select links__sync__handlers__deep__client(380::bigint, 'delete', '{"id":2308}'::jsonb, '{"table":"selectors"}'::jsonb)`,
        prepared: false,
        error: {
          exec_status: 'FatalError',
          hint: null,
          message: 'delete from selectors not permitted',
          status_code: 'XX000',
          description: null
        },
        arguments: []
      },
      path: '$.args',
      error: 'query execution failed',
      code: 'postgres-error'
    }

      at Object.HasuraApi.defaultErrorHandler [as errorHandler] (../../node_modules/@deep-foundation/hasura/api.tsx:22:45)

  console.log
    error Bad Request {
      internal: {
        statement: `select links__sync__handlers__deep__client(2310::bigint, 'delete', '{"id":2309}'::jsonb, '{}'::jsonb)`,
        prepared: false,
        error: {
          exec_status: 'FatalError',
          hint: null,
          message: 'Delete not permitted',
          status_code: 'XX000',
          description: null
        },
        arguments: []
      },
      path: '$.args',
      error: 'query execution failed',
      code: 'postgres-error'
    }

      at Object.HasuraApi.defaultErrorHandler [as errorHandler] (../../node_modules/@deep-foundation/hasura/api.tsx:22:45)

  console.log
    error Bad Request {
      internal: {
        statement: `select links__sync__handlers__deep__client(2355::bigint, 'delete', '{"id":2389}'::jsonb, '{}'::jsonb)`,
        prepared: false,
        error: {
          exec_status: 'FatalError',
          hint: null,
          message: 'Delete not permitted',
          status_code: 'XX000',
          description: null
        },
        arguments: []
      },
      path: '$.args',
      error: 'query execution failed',
      code: 'postgres-error'
    }

      at Object.HasuraApi.defaultErrorHandler [as errorHandler] (../../node_modules/@deep-foundation/hasura/api.tsx:22:45)

  console.log
    error Bad Request {
      internal: {
        statement: `select links__sync__handlers__deep__client(2390::bigint, 'delete', '{"id":2471}'::jsonb, '{}'::jsonb)`,
        prepared: false,
        error: {
          exec_status: 'FatalError',
          hint: null,
          message: 'delete [{"id":2471,"from_id":0,"to_id":0,"type_id":23}] rejected because selector_id: 2461 query_id: 2464 user_id: 2390 return false',
          status_code: 'P0001',
          description: null
        },
        arguments: []
      },
      path: '$.args',
      error: 'query execution failed',
      code: 'postgres-error'
    }

      at Object.HasuraApi.defaultErrorHandler [as errorHandler] (../../node_modules/@deep-foundation/hasura/api.tsx:22:45)

  console.log
    error Bad Request {
      internal: {
        statement: `select links__sync__handlers__deep__client(2420::bigint, 'delete', '{"id":2473}'::jsonb, '{}'::jsonb)`,
        prepared: false,
        error: {
          exec_status: 'FatalError',
          hint: null,
          message: 'delete [{"id":2473,"from_id":0,"to_id":0,"type_id":23}] rejected because selector_id: 2461 query_id: 2464 user_id: 2420 return false',
          status_code: 'P0001',
          description: null
        },
        arguments: []
      },
      path: '$.args',
      error: 'query execution failed',
      code: 'postgres-error'
    }

      at Object.HasuraApi.defaultErrorHandler [as errorHandler] (../../node_modules/@deep-foundation/hasura/api.tsx:22:45)

  console.log
    {
      actualErrorMessage: 'DeepClient Delete Error: Success! Handler is called',
      expectedErrorMessage: 'DeepClient Delete Error: Success! Handler is called'
    }

      at log (tests/sync-handlers.ts:2151:21)

  console.log
    updated { data: [ { id: 2583, __typename: 'links' } ] }

      at log (tests/sync-handlers.ts:2183:19)

 FAIL   node  ./integration.test.js (158.599 s)
  client
    ○ skipped deep.linkId guest and login
    ○ skipped name
    ○ skipped { id: 5 }
    ○ skipped { id: { _eq: 5 } }
    ○ skipped { value: 5 }
    ○ skipped { value: 'a' }
    ○ skipped { number: 5 }
    ○ skipped { string: 'a' }
    ○ skipped { number: { value: { _eq: 5 } } }
    ○ skipped { string: { value: { _eq: 'a' } } }
    ○ skipped { object: { value: { _contains: { a: 'b' } } } }
    ○ skipped { from: { value: 5 } }
    ○ skipped { out: { type_id: Contain, value: item, from: where } }
    ○ skipped { value: 5, link: { type_id: 7 } }
    ○ skipped { type: ['@deep-foundation/core', 'Value'] }
    ○ skipped { type: ['@deep-foundation/core', 'Value'] }
    ○ skipped id(packageName,contain)
    ○ skipped { type_id: { _type_of: 25 } }
    ○ skipped { from_id: { _type_of: 25 } }
    ○ skipped { to_id: { _type_of: 25 } }
    ○ skipped { id: { _id: ['@deep-foundation/core', 'Package'] } }
    ○ skipped { type_id: { _id: ['@deep-foundation/core', 'Package'] } }
    ○ skipped { up: { parent_id: { _id: ['@deep-foundation/core', 'Package'] } } }
    ○ skipped idLocal get from minilinks
    ○ skipped insert link with reserved id and string value
    ○ skipped select string table
    ○ skipped deepClient token must not be undefined when secret is passed to apolloClient
    serial
      insert
        ○ skipped one insert
        ○ skipped multiple inserts in one operation
        ○ skipped multiple inserts ine multiple operations
      update
        ○ skipped one update
        ○ skipped multiple updates in one operation
        ○ skipped multiple updates in multiple operations
      delete
        ○ skipped one delete
        ○ skipped multiple deletes in one operation
        ○ skipped multiple deletes in multiple operations
    short value insert
      ○ skipped insert string
      ○ skipped insert number
      ○ skipped insert object
      ○ skipped insert inherited links with values
  join-insert
    ○ skipped { type_id: 1, string: { data: { value: 'abc' } }, from: { data: { type_id: 1 } }, to: { data: { type_id: 1 } } }
  typing
    ○ skipped type required
    ○ skipped particular links
    ○ skipped type 1
    ○ skipped custom id restricted
    ○ skipped link equal from/to type
    ○ skipped link invalid from type
  selectors
    ○ skipped selector include exclude
    criteria
      ○ skipped selector include exclude boolExp
  bool_exp
    value convertation
      ○ skipped insert separately
      ○ skipped insert with link
      ○ skipped update
      ○ skipped delete
      ○ skipped X-Deep-User-Id
      ○ skipped X-Deep-Item-Id
  permissions
    select
      ○ skipped user contain range
      ○ skipped rule select include 1 depth but exclude 2 depth
    insert
      ○ skipped root can insert
      ○ skipped guest cant insert by default
      ○ skipped insert permission can be gived to guest
      ○ skipped insert permission with SelectorFilter
    update
      ○ skipped root can update string value
      ○ skipped guest cant update string value
      ○ skipped update permission can be gived to guest
    delete
      ○ skipped root can delete
      ○ skipped guest cant delete by default
      ○ skipped delete permission can be gived to guest
      ○ skipped delete permission with SelectorFilter
    login
      ○ skipped login permission can be granted
  demo
    ○ skipped user can basic dc operations
  packager
    class
      ○ skipped export import
    sorting
      ○ skipped strict mode: no sorting
      ○ skipped sorting with package, value, and dependencies
      ○ skipped sorting existing package
  tree
    ○ skipped promiseTree
  SerialTransitionsBuilder
    ○ skipped should instantiate correctly
    ○ skipped should append insert transition
    ○ skipped should clear transitions
    ○ skipped should get correct transition type for insert
    ○ skipped should get correct transition type for update
    ○ skipped should get correct transition type for delete
    ○ skipped should execute transition
    ○ skipped should execute transitions
    ○ skipped should execute multiple transitions
    ○ skipped should execute transition and result link be accessible by both alias and index
    ○ skipped should execute transitions and result links be accessible by both alias and index
  sync handlers
    Prepare fuction
      ✓ handleInsert (28 ms)
    DeepClient mini
      ✓ id (21 ms)
      ✓ login as guest and insert (595 ms)
      ✓ login as guest, relogin as admin and insert (998 ms)
      ✓ new client by linkId (398 ms)
      ✓ new client by jwt (308 ms)
      ✓ can (751 ms)
      ✓ objectGet (74 ms)
      ✓ objectSet (62 ms)
      unsafe
        ✓ objectSet (70 ms)
        ✓ objectGet (61 ms)
      select
        ✓ select should return value (74 ms)
        number
          ✓ number: { value: number }} (96 ms)
          ✓ number: { value: { "_in": [ number, number ] }} (103 ms)
          ✓ number: number (87 ms)
          ✓ number: { "_in": [ number, number ]} (241 ms)
        string
          ✓ string: { value: string } (118 ms)
          ✓ string: { value: { "_in": [ string, string ] }} (97 ms)
          ✓ string: 'string' (145 ms)
          ✕ string: { "_in": ['string', 'string'] } (80 ms)
        object
          ✓ object: { value: object } (91 ms)
          ✓ object: { value: { "_in": [ object, object ] }} (90 ms)
          ✓ object: object (92 ms)
          ✓ object: { "_in": [object, object] } (254 ms)
        value
          ✓ value: { value: string } (156 ms)
          ✓ value: string (109 ms)
          ✓ value: { value: object } (115 ms)
          ✓ value: object (110 ms)
          ✓ value: { value: { _in: [ string, number, object ] } }} (115 ms)
          ✓ value: {"_in":[ string, number, object ]} } (179 ms)
      update
        ✓ update string (211 ms)
        ✓ update number (97 ms)
        ✓ update object value (142 ms)
        ✓ update object value by value (81 ms)
      permissions
        select
          ✓ root can select from tree (10705 ms)
          ✓ root can select from can (70 ms)
          ✓ root can select from selectors (16 ms)
          ✓ nobody can select from not permitted tables (29 ms)
          ✓ user contain range (614 ms)
          ✓ rule select include 1 depth but exclude 2 depth (1943 ms)
        insert
          ✓ root can insert (73 ms)
          ✓ guest cant insert by default (312 ms)
          ✓ insert permission can be gived to guest (1484 ms)
          ✓ insert permission with SelectorFilter (6676 ms)
        update
          values
            ✓ root can update value (113 ms)
        delete
          ✓ root can delete (59 ms)
          ✓ nobody can delete from not permitted tables (33 ms)
          ✓ guest cant delete by default (350 ms)
          ✓ delete permission can be gived to guest (1725 ms)
          ✓ delete permission with SelectorFilter (6670 ms)
    require package
      ✓ require mathjs (1697 ms)
      ✓ require jsonschema (350 ms)
    Handle operations
      Handle insert
        ✓ Handle insert on type (253 ms)
        ✓ Handle insert 2 triggers and broke transaction in second (439 ms)
        ✓ Handle insert 1 trigger and 2 types, check not triggered twice (393 ms)
        ✓ Handle insert on type throw error (215 ms)
        ✓ Handle insert on selector (575 ms)
        ✓ Handle insert on type any (365 ms)
        ○ skipped Handle insert on type with sql injection (DAMAGES DATABASE SHOULD BE SKIPPED UNTIL FIXED)
      Handle delete
        ✓ Handle delete on type (263 ms)
        ✓ Handle delete on selector (532 ms)
        ✓ Handle delete on type any (269 ms)
      Handle update
        ✓ Handle update on type (334 ms)
        ✓ Handle update on selector (744 ms)
        ✓ Handle update on type any (223 ms)
      Handle value
        ✓ Handle update on type any (199 ms)
        Handle strings
          ✓ Handle insert string (308 ms)
          ✓ Handle update string (388 ms)
          ✓ Handle delete string (267 ms)
        Handle numbers
          ✓ Handle insert number (313 ms)
          ✓ Handle update number (397 ms)
          ✓ Handle delete number (342 ms)
        Handle objects
          ✓ Handle insert object (344 ms)
          ✓ Handle update object (487 ms)
          ✓ Handle delete object (289 ms)
      Handle IUD for values
        ✓ Handle IUD for strings (599 ms)
        ✓ Handle IUD for numbers (596 ms)
        ✓ Handle IUD for object (552 ms)
      Check data for not bigint
        ✓ Check in delete link (275 ms)
        ✓ Check in update link (694 ms)
  Async handlers
    sync function handle by type with resolve
      ✓ handle insert (1314 ms)
      ✓ handle update when value is inserted (1292 ms)
      ✓ handle update when value is updated (2420 ms)
      ✓ handle update when value is deleted (2416 ms)
      ✓ handle delete (1287 ms)
    sync function handle by type with reject
      ✓ handle insert (1294 ms)
      ✓ handle delete (2313 ms)
    async function handle by type with reject
      ✓ handle insert (1274 ms)
      ✓ handle update (1299 ms)
      ✓ handle delete (1300 ms)
    sync function handle by schedule with resolve
      ✓ handle schedule (17455 ms)
    async function handle by type with resolve using deep client
      ✓ handle insert (1303 ms)
      ✓ handle insert with package jwt (1291 ms)
    handle port
      ✓ handle port (13425 ms)
    handle route
      ✓ handle route (7222 ms)
      ✓ handle route hierarchical insert (9907 ms)
      ✓ handle route hierarchical insert with throw error (14962 ms)
      ✓ handle route gql handler (15071 ms)
    handle by selector
      ✓ handle insert (1871 ms)
      ✓ handle delete (1837 ms)
      ✓ handle update when value is updated (3070 ms)

  ● sync handlers › DeepClient mini › select › string › string: { "_in": ['string', 'string'] }

    assert.strictEqual(received, expected)

    Expected value to strictly be equal to:
      "hellobugfixerstest"
    Received:
      undefined

    Message:
      expected undefined to equal 'hellobugfixerstest'

    Difference:

      Comparing two different types of values. Expected string but received undefined.

      600 |           log('selected', selected?.data?.[0]);
      601 |           await deep.delete(id);
    > 602 |           assert.equal(value?.value, 'hellobugfixerstest');
          |                  ^
      603 |         });
      604 |       });
      605 |       describe('object', () => {

      at equal (tests/sync-handlers.ts:602:18)
      at fulfilled (tests/sync-handlers.js:10:24)

Test Suites: 2 failed, 1 skipped, 2 of 3 total
Tests:       1 failed, 105 skipped, 99 passed, 205 total
Snapshots:   0 total
Time:        159.36 s
Ran all test suites matching /index.js|integration.test.js|jest.config.js|react.test.js|unit.test.js/i with tests matching "sync handlers" in 2 projects.
npm ERR! Lifecycle script `test` failed with error:
npm ERR! Error: command failed
npm ERR!   in workspace: @deep-foundation/deeplinks@0.0.322
npm ERR!   at location: /workspace/dev/packages/deeplinks

This problem interferes https://github.com/deep-foundation/object-to-links-converter development because it uses plv8 handlers

repo: deep-foundation/deeplinks

license: Unlicense


text:
Sweep: Do not install latest npm in github workflow npm-build.yml

Do not install latest npm in github workflow npm-build.yml
https://github.com/deep-foundation/workflows/blob/d12184a1d834a379abd2d907e50e7c555887a66c/.github/workflows/npm-build.yml#L23

Sweep: retry

Sweep: retry

@FreePhoenix888 what is the problem with installation of latest npm? It usually fixes lots of problems, so it may safely stay.
I suggest to close this issue as not planned.

repo: deep-foundation/workflows