text:
Network unavailable - MacOS connecting to Azure SQL in cloud

Description
DBeaver Version 23.2.5.202311160022 installed on Mac OS Ventura 13.5
installed via dmg.
Mac has jdk 1.8 and 11 installed.
configured Azure SQL connection. when click test connection get following error.
Network error
Reason:
Network unavailable
java.net.SocketException:java.security.NoSuchAlgorithmException: Error constructing implementation (algorithm: Default, provider: SunJSSE, class: sun.security.ssl.SSLContextImpl$DefaultSSLContext)
when click ok, get another error
com.microsoft.sqlserver.jdbc.SQLServerDriver
Error creating driver instance
jar may be missing
configure jar in the settings
but if going to Driver properties to configure, get Network Error above
DBeaver Version
DBeaver Version 23.2.5.202311160022 community edition
Operating System
Mac OS Ventura 13.5
Database and driver
Azure SQL selected. cannot get to the setting up driver, get Network Error see above
Steps to reproduce

Create connection\
Azure SQL (tried old jTDS MS SQL with same resaukt)
populate host, db, name and password
Click driver properties]
Get network error. Click ok
Get driver missing error

Additional context
No response

Hello @sasha-gerasimenko
Looks like network issues here.
Did you check your Internet connection? Does DBeaver have all requeried permissions to use network?

i dont know what BEaver specific permission for network and how they could
be defined. I'm able to use SquirellSQL to connect to same db. from same
laptop. I also abl to access urls shown in Beaver Driver config in browser.
So internt connection is ok and connection to end db exists.
On Thu, 23 Nov 2023 at 08:05, Anastasiya @.***> wrote:

Hello @sasha-gerasimenko https://github.com/sasha-gerasimenko
Looks like network issues here.
Did you check your Internet connection? Does DBeaver have all requeried
permissions to use network?
—
Reply to this email directly, view it on GitHub
https://github.com/dbeaver/dbeaver/issues/21957#issuecomment-1823948460,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGGXHGCAWZLDFLMQPOJSE2DYF37S7AVCNFSM6AAAAAA7W664R6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRTHE2DQNBWGA
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Sasha

You can download and add driver files manually. In your connection settings -> driver settings -> libraries
https://mvnrepository.com/artifact/com.microsoft.sqlserver/mssql-jdbc/9.2.0.jre8
https://mvnrepository.com/artifact/com.microsoft.sqlserver/mssql-jdbc_auth/9.2.0.x64
Now we are using these versions, but you can use newer ones.

authors: LonwoLonwo sasha-gerasimenko


text:
Eclipse EMF model integration

After all we should do this.
We need to integrate some DBx models (at least DBS) and SQL editor semantic model.

We decided that we don't want to add EMF dependency to DBeaver.

source: gharchive/issue

repo: dbeaver/dbeaver

license_type: permissive

license_source: github-api


text:
Native client is not specified for connection - Mac

System information:

Mac OS X Catalina
DBeaver version 6.3.5

Connection specification:

this is proprietary, I don't know why you'd want this

Describe your question:
I'm trying to just import a database by right-clicking it then Tools > Restore Database, but the pop-up box says under Script configuration "Native client is not specified for connection"... I click the "Client..." button, it pops up "Configure local client", I click the drop-down by Native client, it's empty except for Browse, I click that, it pops up another box named Database Client Homes, which has empty fields (I'm more confused at this point), I then click Add Home, and it opens up a Finder Open box...
I read in the docs that "Native client" just means DBeaver needs some mysql exe from somewhere to run the mysqldump stuff (why this is necessary when it can do all the other things already, I don't know), but I'm not sure where to look at this point. The docs imply DBeaver will just find it if it exists in the normal places or if I have MySQL Workbench installed, which I do (version 6 and 8), but it doesn't.
I've been using MySQL Workbench for normal database stuff, then Sequel Pro for importing (because the progress bar actually works), and I had DBeaver recommended to me yesterday, but this particular feature has been vexing. I'm typing this while importing databases using Sequel Pro. Sorry that I don't know what to select for my Mac's Native MySQL client, I don't run mysql commands on it because I use GUIs that make it easier and for some reason they're just able to do import/export no problem.

Any update on that?
I get the same error when trying to dump a MySQL DB using latest DBeaver (7.1.0)

We need to improve native client management on MacOS.

Any update on this?

@anurag2pirad function should be implemented in 7.3.1

Same problem on linux mint 20 and dbeaver 7.2.3 (today's update), for postgresql,  native client drop down is empty

ame here, postgres on linux. 7.2.4

neither in 7.2.3 nor in 7.0.0. strange, didnt notice. may be another problem?

nevermind, just hit client, left bottom, browse, add /usr/bin (where the psql lives on linux)...then, choose the /usr/bin (it may be empty on initial selection!)...

Work around for Mac:  CAN BE DANGEROUS

Open Terminal program
type  which mysql
will return something like: /usr/local/bin/mysql
copy portion of path before bin/mysql. '/usr/local/bin' for above example
Open Finder. Select Go -> Go to Folder and paste in your location  /usr/local/bin
drag folder bin from path bar (bottom bar. if not visible turn on using Finder View -> Show Path Bar) to Finder Side Bar
bin folder should now appear in sidebar. If not make sure you did not move bin folder! (In Finder Edit -> Undo Move of "bin") and try again.
In DBeaver when you Browse to add home select bin from sidebar. Database Client home will now show /usr/local/bin

Native client management on macOS has been improved. Now DBeaver tries to find Postgres, MySQL, or MariaDB in the places they are most commonly installed.

Could you please think about following improvements:

Now dump via task becomes possible only after running it from context menu>Tools at first (error appears: "Native client is not found")
What do you think about selecting a client by default in the dump wizard? Now an additional click is needed to select it

Can SQL extension be available by default when you select a file for Restore (now backup is offered, but exported files have SQL extension)

Can you add an option to run Dump/restore task for non-default database for PostgreSQL (now dump works only for default database in Database Task Panel)?

Points 1 and 2 are valid only for connections added before my fix. You can easily bypass those problems by selecting a local client manually. Unfortunately, there is no good solution here. Points 3 and 4 are not related to this particular ticket and require their own.

Closed. New tickets will be created for 3 and 4

The client disappeared from EA version 7.3.1.202012162110

It seems to me that this is somehow related to the upcoming dmg redesign, but the exact root cause is a mystery to me. More investigation needed.

The problem was in the mysql/psql process spawn.
Actual error was java.io.IOException: error=316, posix_spawn failed.
Apparently problem wa in the missing executable bit on the jspawnhelper binary in the bundled jre.
Fixed.

verified

I'am using DBeaver version 7.3.3 and when i try to load a script file from. rigth click on my data base > Tools > Execute script, y select my file but i can't start the button is disable and the window show me = Native client is not specified for connection. idon't know if i'm making something wrong o is this bug still is?.

I'am using DBeaver version 7.3.3 and when i try to load a script file from. rigth click on my data base > Tools > Execute script, y select my file but i can't start the button is disable and the window show me = Native client is not specified for connection. idon't know if i'm making something wrong o is this bug still is?.

Please try to press Local Client.. in the left bottom corner and select Native Client there.

Please try to press Local Client.. in the left bottom corner and select Native Client there.

@kseniiaguzeeva don't show me the Native Client option, only Browse and . Well my postgresql is on docker container. i don't know if this maybe could be the problem.

@kseniiaguzeeva don't show me the Native Client option, only Browse and . Well my postgresql is on docker container. i don't know if this maybe could be the problem.

Was this issue solved?

@lotar94 The docker container is the reason. DBeaver doesn't have an access to its file system. You should install the client on your local machine, and Script execute will work.

@kseniiaguzeeva Thanks, yes this is the problem, i installed the client on my local machine and work fine.

Hi
I am trying to setup Dbeaver for the first time and I am trying to connect to my local PC mysql server. Not sure what I am missing on this local setup

Anyone able to help?

This ticket is overloaded. Could you please create a new one? Also please tell what is your issue about? Which DBeaver version do you use? Logs are often can be helpfull too  https://github.com/dbeaver/dbeaver/wiki/Log-files.

I don't see why this is closed - this issue has been present for me on ubuntu 20.10 for a good 2 months. I literally can't dump or restore any sql files with this software. Why do I need to specify anything like this? It's not even clear what I'm expected to do to fix this (not that the user should need to)
Version 21.0.0.202102281712

Hi Folks!
The Command below solved my problem on Mac:
1 - Install PostgresSQL, download here: https://www.postgresql.org/download/macosx/
2 - on DBeaver: Local Client -> Choose /Library/PostgreSQL/XX/bin

I pointed the "home" to my /usr/bin folder expecting it to execute mysqldump but it doesn't find it.
I even added a ln -sf mysqldump /usr/bin/mysqldump to my home folder if it was having permission issues.  Does this operation not execute as my user?

I wouldn't waste my time with this. DBeaver is an awesome tool for other things. This is not one of those things.
Just do this through the command line - here is what I did after a very long struggle, installing the deb, then the flatpak then back to the deb - and a whole lot of looking for mysql client files... I managed to land my db server in a masked state - at least I know what that is now.
Anyway - here is what worked for me:
cd /usr/bin (or where ever your mysql command is - probably right here and not at all correct from dbeaver's assessment)
mysql -u usr -p dbname < /path/to/filename.sql
et voila
I do think the issue is with mariadb and the way that the whole shebang is aliased through mysql... but I have absolutely no proof of this and am not about to dig deeper. I've spent way more time trying to restore a db by being lazy than I should have...
Good luck good people

Alternative fix for Mac users with (mariaDB but will works for every dialect i think) and using brew for applications ->
brew install mariadb
Restart DBeaver and choose Local Client -> your client

#14620
#15092
#15093

Well I solved the issue by clicking in Local client and typing the path to where my pg and pg_dump are installed in my local machine that in my case was /opt/bin/pg_dump

On Mac, after clicking Add Home, you can use command + shift + G to go directly to any hidden folder. I'm using homebrew so I had to type /opt/homebrew/bin.
Solution found here, tested on Monterey.

https://github.com/dbeaver/dbeaver/issues/7976#issuecomment-725436879

nevermind, just hit client, left bottom, browse, add /usr/bin (where the psql lives on linux)...then, choose the /usr/bin (it may be empty on initial selection!)...

It worked for me using docker! 🐳 🐋

On Mac, after clicking Add Home, you can use command + shift + G to go directly to any hidden folder. I'm using homebrew so I had to type /opt/homebrew/bin. Solution found here, tested on Monterey.

Perfectly worked for me

On Mac, after clicking Add Home, you can use command + shift + G to go directly to any hidden folder. I'm using homebrew so I had to type /opt/homebrew/bin. Solution found here, tested on Monterey.

Thanks for the solution

Why do I have to install postgresql on my Mac? Does it only need a client?

Localclient set this "/Users/{account}/Library/DBeaver/drivers"

Can it be made to search for the path directly, using
which MySQL

in my case this returns /opt/homebrew/bin/mysql

On Mac, after clicking Add Home, you can use command + shift + G to go directly to any hidden folder. I'm using homebrew so I had to type /opt/homebrew/bin. Solution found here, tested on Monterey.

This is probably the most useful thing I've learned all year. Never knew I could do that. You are a God send!

What I did on mac ?
I am running mysql on docker ..
brew install mysql-client
it gave me output
echo 'export PATH="/usr/local/opt/mysql-client/bin:$PATH"' >> ~/.zshrc
I just added this to home and it worked
/usr/local/opt/mysql-client/bin

On my part I import it using the command line mysql -u user -p database_name < database_dump.sql dbbeaver is a great tool, but its somehow frustrating that doing this simple task require such hacky solutions.

Hi All, You can use brew install mysql-client and set local Client => Home to /usr/local/opt/mysql-client/bin, problem will be solved.

nevermind, just hit client, left bottom, browse, add /usr/bin (where the psql lives on linux)...then, choose the /usr/bin (it may be empty on initial selection!)...

Worked for me using docker and mysql.

Using Postgres I was able to solve this by pointing load client to /opt/homebrew/opt/libpq/bin

for me 'opt/homebrew/bin' worked

On Mac, after clicking Add Home, you can use command + shift + G to go directly to any hidden folder. I'm using homebrew so I had to type /opt/homebrew/bin.
Solution found here, tested on Monterey.

this is work for me ! thanks @ynnsnr

nevermind, just hit client, left bottom, browse, add /usr/bin (where the psql lives on linux)...then, choose the /usr/bin (it may be empty on initial selection!)...

Worked for me using docker and mysql.

How did you run your docker container Even im using docker with mysql but getting error mysql not found

bagus

authors: AliRazaLilani BlaineOmega Daviontheone Goddard Lemmynjash Matvey16 OlivierRicca akbarginanjar akilovich ammarfaris anurag2pirad azdream baditaflorin benzkji bessa3301 briancalma burtonboucher corleroux felix-penrose guigons guiqui hoanghog isalmanhaider jmada kseniiaguzeeva lincoln310 lotar94 michael1593 orgoldfus serge-rider skyvondave sondoskareem souravpakhira2 tate801 taufikmuharrom uslss ynnsnr


text:
Fixed PostgreInsertReplaceMethod not quoting the column in CONFLICT

When using the import data wizard (in my case, a CSV) on a Postgres table that had capitalized column names (like HelloWorld rather than helloworld) this caused the insert/replace function to error out, because it did not properly quote the column name, and Postgres defaults capitalized column names to all-lowercase when they are unquoted. This fixes that.
I'm not really a Java programmer, so I just did the most straight-forward fix.

Hello @Seanld
Thanks for your contribution!
But we can't always use quotes for attribute names. Usually, we use quotes only for attributes that need them.
However, thanks for the bug report. I'll create a new issue on our board and fix this bug.

https://github.com/dbeaver/dbeaver/pull/15231

source: gharchive/pull-request

authors: LonwoLonwo Seanld


text:
#20724 use text execution plan for YellowBrick

Verified


text:
[BUG] Orbit download error - hopefully this is transient.

Describe the bug
Approximately 1% of GUNW jobs are failing with the below API error at RAiDER step.
Here is an example of inputs and log. Please investigate.
{'job_id': 'a897b1f7-0a0d-41ac-b6c7-f3b09644c7e9',
  'job_type': 'INSAR_ISCE_TEST',
  'request_time': '2023-08-17T20:30:41+00:00',
  'status_code': 'FAILED',
  'user_id': 'cmarshak',
  'name': 'track4-n3',
  'job_parameters': {'compute_solid_earth_tide': True,
   'estimate_ionosphere_delay': True,
   'frame_id': 494,
   'granules': ['S1A_IW_SLC__1SDV_20230807T230644_20230807T230711_049776_05FC51_52AC',
    'S1A_IW_SLC__1SDV_20230807T230709_20230807T230736_049776_05FC51_0329'],
   'secondary_granules': ['S1A_IW_SLC__1SDV_20230714T230643_20230714T230710_049426_05F188_8808',
    'S1A_IW_SLC__1SDV_20230714T230708_20230714T230735_049426_05F188_5416'],
   'weather_model': 'HRRR'},
  'logs': ['https://hyp3-tibet-jpl-contentbucket-81rn23hp7ppf.s3.us-west-2.amazonaws.com/a897b1f7-0a0d-41ac-b6c7-f3b09644c7e9/a897b1f7-0a0d-41ac-b6c7-f3b09644c7e9.log'],
  'expiration_time': '2023-09-02T00:00:00+00:00',
  'processing_times': [8714.966, 6.619]}

Here is the log reproduced from the link above.
â•â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â•®
 â”‚ I'm building Herbie's default config file.      â”‚
 â•°â•¥â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â•¯
 ðŸ‘·ðŸ»â€â™‚ï¸
 â•â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â•®
 â”‚ You're ready to go.                             â”‚
 â”‚ You may edit the config file here:              â”‚
 â”‚ /home/raider/.config/herbie/config.toml         â”‚
 â•°â•¥â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â”€â•¯
 ðŸ‘·ðŸ»â€â™‚ï¸
/opt/conda/envs/RAiDER/lib/python3.10/site-packages/RAiDER/cli/__main__.py:36: DeprecationWarning: Accessing entry points by index is deprecated. Cast to tuple if needed.
  process_entry_point = entry_points(group='console_scripts', name=f'{args.process}.py')[0]
Downloading s3://hyp3-tibet-jpl-contentbucket-81rn23hp7ppf/96473d6f-d41e-4950-a510-7d1d0e53dc75/S1-GUNW-A-R-004-tops-20230807_20230620-230825-00080W_00041N-PP-86ec-v3_0_0.nc to S1-GUNW-A-R-004-tops-20230807_20230620-230825-00080W_00041N-PP-86ec-v3_0_0.nc
Downloading s3://hyp3-tibet-jpl-contentbucket-81rn23hp7ppf/96473d6f-d41e-4950-a510-7d1d0e53dc75/S1-GUNW-A-R-004-tops-20230807_20230620-230825-00080W_00041N-PP-86ec-v3_0_0.json to S1-GUNW-A-R-004-tops-20230807_20230620-230825-00080W_00041N-PP-86ec-v3_0_0.json
Traceback (most recent call last):
  File "/opt/conda/envs/RAiDER/lib/python3.10/runpy.py", line 196, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/opt/conda/envs/RAiDER/lib/python3.10/runpy.py", line 86, in _run_code
    exec(code, run_globals)
  File "/opt/conda/envs/RAiDER/lib/python3.10/site-packages/RAiDER/cli/__main__.py", line 46, in <module>
    main()
  File "/opt/conda/envs/RAiDER/lib/python3.10/site-packages/RAiDER/cli/__main__.py", line 42, in main
    process_entry_point.load()()
  File "/opt/conda/envs/RAiDER/lib/python3.10/site-packages/RAiDER/cli/raider.py", line 529, in calcDelaysGUNW
    path_cfg, wavelength = RAiDER.aria.prepFromGUNW.main(args)
  File "/opt/conda/envs/RAiDER/lib/python3.10/site-packages/RAiDER/aria/prepFromGUNW.py", line 358, in main
    GUNWObj = GUNW(args.file, args.weather_model, args.output_directory)
  File "<string>", line 6, in __init__
  File "/opt/conda/envs/RAiDER/lib/python3.10/site-packages/RAiDER/aria/prepFromGUNW.py", line 124, in __post_init__
    self.OrbitFile  = self.get_orbit_file()
  File "/opt/conda/envs/RAiDER/lib/python3.10/site-packages/RAiDER/aria/prepFromGUNW.py", line 238, in get_orbit_file
    path_orb = download_eofs([dt], [sat], save_dir=orbit_dir)
  File "/opt/conda/envs/RAiDER/lib/python3.10/site-packages/eof/download.py", line 89, in download_eofs
    query = client.query_orbit_by_dt(orbit_dts, missions, orbit_type=orbit_type)
  File "/opt/conda/envs/RAiDER/lib/python3.10/site-packages/eof/scihubclient.py", line 168, in query_orbit_by_dt
    self._select_orbit(
TypeError: ScihubGnssClient._select_orbit() got an unexpected keyword argument 'orbit_type'

@asjohnston-asf and/or @jtherrmann are there reasons that hyp3lib uses both ESA and ASF for the orbit download vs. sentineleof just uses ESA.
@bbuzz31 - will likely be good to update prepGUNW accordingly if we can improve robustness via hitting ESA and ASF.
See the hyp3 code - it cycles through both endpoints: https://github.com/ASFHyP3/hyp3-lib/blob/develop/hyp3lib/get_orb.py#L110-L147
We use hyp3lib in dockerized topsapp and cannot remember last time we had issues downloading orbit: https://github.com/ACCESS-Cloud-Based-InSAR/DockerizedTopsApp/blob/dev/isce2_topsapp/localize_orbits.py

I'm not familiar with the sentineleof package or this particular error message.
Years past ASF had seen occasional outages of the Copernicus orbit service. I haven't revisited uptime in a few years but anecdotally it's improved. We saw breaking changes introduced to the service API in 2021 and again in 2022, however, which having a fallback to ASF's orbit archive helped mitigate.

Looks like a bug in sentineleof. _select_orbit defined at https://github.com/scottstanie/sentineleof/blob/master/eof/scihubclient.py#L88 has no orbit_type parameter, but it's called with that parameter at https://github.com/scottstanie/sentineleof/blob/master/eof/scihubclient.py#L168 .

At a glance this might only impact recent scenes for which no precision orbit is available. I notice your example is from 2023-08-07. Worth checking if your other failures are from recent dates.

To be clear though, both libraries provide access to restituted and precise orbits (the former for recent acquisitions). May want to ensure we are using API correctly.

This was my fault- I added another fix+test, it's up on pypi now with v0.8.1, and i'll bump the conda-forge version too

authors: asjohnston-asf cmarshak scottstanie

repo: dbekaert/RAiDER


text:
Add features to change User attributes

[x] Change username
[x] Change email
[x] Change password
[x] Delete account
[x] Change profile picture
[x] Change bio

Features added in f32a0ea.

license: MIT


text:
latest repo state not working

the last commit seem to have broken the gstore. The container cannot be started.
gstore_1    | no main manifest attribute, in /app/app.jar
databus-dev_gstore_1 exited with code 1```

Seems to be resolved. Reopen if needed.

repo: dbpedia/gstore


text:
unncessary breaking change with --markdown flag

tldr node-js client still has the -m/--markdown flag still instead of the -r/--raw flag. https://github.com/tldr-pages/tldr-node-client/blob/8de0d9d60f71ac4c6a30c4ad1f5e59cd8210e94c/bin/tldr#L24
navi uses --markdown https://github.com/denisidoro/navi/blob/6f316ec7eb2f1f56a7609048e67860eb84c1aacf/src/clients/tldr.rs#L54
And it recommends installing rust client for tldr which I assume is this (tealdeer) https://github.com/denisidoro/navi/blob/6f316ec7eb2f1f56a7609048e67860eb84c1aacf/src/clients/tldr.rs#L9.
Now navi has to remove the rust recommendation and recommend python client in its place.
Which is a bummer as python/node needs to be installed in the system, and rust version being a single binary is clearly superior.
There is no need to break this, https://github.com/dbrgn/tealdeer/pull/290 and the other flags too. If possible to maintain backward compatability please do!
Someone else had the same issue.

Well, there is no need to remove deprecated options, but one would want to eventually get rid of them to reduce code complexity, compile time, etc. As for why the markdown flag was renamed to raw: We at some point felt that raw is a better name, because the output is not markdown that is ready to be displayed as is, but still has the {{ markers in it that tealdeer highlights as user input (the commit that made this change is 8833b6b40179eef6161035d10d7e218694facca1). I am not sure how to proceed here, best case would be if the tldr project could decide a name for the desired behavior. I think I would oppose re-introducing the alias unless there is a good reason to do so.

True. It renders tealdeer useless with thirdparty clients. Just realized it doesn't work with navi.

It renders tealdeer useless with thirdparty clients.

Not true, navi just has to stop making the wrong assumptions. The --markdown flag is not part of the tldr client specification and just happens to be a feature that a number of clients shared. Tealdeer decided to rename the flag, the previous name worked with a deprecation warning for over a year and no one complained. To be honest, I feel that if navi doesn't have it's dependencies under control, it's not our issue. Have you considered opening an issue with navi?

Maybe this should then become a part of the tldr client specification if a number of clients share this?

the previous name worked with a deprecation warning for over a year and no one complained

I have only recently switched to tealdeer and thus navi broke only after I switched to tealdeer and thus I am a little late for the complaint box, I would've raised an issue had I discovered tealdeer early and saw the deprecation notice.

To be honest, I feel that if navi doesn't have it's dependencies under control, it's not our issue

Tealdeer is not a navi dependency. Tldr is the navi dependency which I intend to replace with a better version which is tealdeer. But alas tealdeer is not compatible with navi because the markdown flag was deprecated for no reason whereas it once was compatible.
And tealdeer names/declares itself to be tldr in the PATH env variable so I assume the intent is to act as a tldr client and being as compatible with the python implementation as much as possible. And the python version has the m flag so I don't get why the markdown flag isn't in the client specification other than that most users never used so much for it to make or break their workflow.
To be honest there is no proper justification for this breaking change. And it is not navi's responsibility to check if the markdown flag fails and fallback to raw flag which only tealdeer uses among the tldr client implementations, this is convoluted.
And I would like @dbrgn's input on this issue too as he was the one who made the change.
I opened the issue here first in hopes it can be rectified at the source instead of going staright to implementing a workaround. I'll open an issue there as well once this issue reaches some kind of conclusion.
Frankly I don't see why reverting this markdown flag removal warrants this much discussion.

I am not sure how to proceed here, best case would be if the tldr project could decide a name for the desired behavior

@niklasmohrin  I am saying the same thing, I must've missed this part of your first response.

Maybe this should then become a part of the tldr client specification if a number of clients share this?

The client specification is here: https://github.com/tldr-pages/tldr/blob/main/CLIENT-SPECIFICATION.md
Feel free to open an issue in that repository to suggest standardization! If a flag is standardized, then we'll implement it with high probability.

And tealdeer names/declares itself to be tldr in the PATH env variable so I assume the intent is to act as a tldr client and being as compatible with the python implementation as much as possible.

No, the goal is to act as a tldr client and being compatible with the client specification.

To be honest there is no proper justification for this breaking change. And it is not navi's responsibility to check if the markdown flag fails and fallback to raw flag which only tealdeer uses among the tldr client implementations, this is convoluted.

It's not tealdeer's responsibility to conform to navi's expectations either 😉 If navi wants a stable API that is compatible with all standards-conforming tldr clients, then the API should be standardized through the client specification linked above. If navi only works with the Python client, then they should document that (and users should follow that).
In my opinion, the best approach for navi would be to simply pull down the cache directly, without relying on other clients being installed. It's just a few lines of code, and it prevents incompatibilities like the one you have discovered.

To be honest there is no proper justification for this breaking change.

There is: As @niklasmohrin explained, we think it's a better-fitting name. We develop this project in our free time, and do what we think is best for the long-term goals of the project.

As a last comment: Every change has the potential to break something. See https://xkcd.com/1172/. If we keep compatibility with all historic options, then we end up with an ossified, hard-to-maintain piece of code.
Also, I kinda forgot to mention this: If the previous version of tealdeer suited your needs, you could use that older version? It still works fine. Nobody forces you to upgrade to newer versions. Since Rust projects can be built into a single binary, you can simply throw that into your /usr/local/bin and it will keep working.

Ok I'll open a new issue over at tldr linking to this issue and raise a proposal for markdown/m flag and also suggest renaming it to raw, I understand open source and the effort that goes into it.
And also request navi to not rely on the markdown flag and reimplement things like you said.
And I will consider downgrading, thanks for the response.

authors: arashm dbrgn niklasmohrin phanirithvij

repo: dbrgn/tealdeer

license_source: bigquery


text:
Quoting changes from 1.4.0 to 1.4.1 break MSCK REPAIR TABLE pre-hooks in models

I have a project that makes use of pre_hook in a handful of models to run MSCK REPAIR TABLE on source tables. Example such model:

https://github.com/sacundim/covid-19-puerto-rico/blob/e864bd14ca6a016e92086849c7321f24e0041c27/aws/athena-dbt/models/covid19datos_v2/staging/casos.sql#L8

Just the other day I rebuilt my Docker image for this DBT project for the first time after several weeks, but the project started failing with errors like this (fuller stack trace at the bottom of the ticket):
An error occurred (InvalidRequestException) when calling the StartQueryExecution operation: line 1:1: mismatched input 'MSCK'. Expecting: 'ALTER', 'ANALYZE', 'CALL', 'COMMENT', 'COMMIT', 'CREATE', 'DEALLOCATE', 'DELETE', 'DENY', 'DESC', 'DESCRIBE', 'DROP', 'EXECUTE', 'EXPLAIN', 'GRANT', 'INSERT', 'MERGE', 'PREPARE', 'REFRESH', 'RESET', 'REVOKE', 'ROLLBACK', 'SET', 'SHOW', 'START', 'TRUNCATE', 'UNLOAD', 'UPDATE', 'USE', 'USING', <query>

I have managed to determine that pinning dbt-athena-community at version 1.4.0 doesn't experience the problem, it happens when I use v1.4.1 instead:

https://github.com/sacundim/covid-19-puerto-rico/commit/e864bd14ca6a016e92086849c7321f24e0041c27

Looking at dbt.log, I see that with adapter v1.4.1, the schema and table name are quoted with double quotes:
18:57:41.706289 [debug] [Thread-4 (]: On model.covid_19_puerto_rico_etl.casos:
        MSCK REPAIR TABLE "covid19datos_v2_sources"."casos_parquet_v1"

And running that statement in the AWS Athena console gets the same error "mismatched input 'MSCK'" that I show above. Athena uses the Hive-style quoting in MSCK REPAIR TABLE statements, like this one that works:
MSCK REPAIR TABLE `covid19datos_v2_sources`.`casos_parquet_v1`

Full stack trace:
Failed to execute query.
--
Traceback (most recent call last):
File "/root/.local/pipx/venvs/dbt-core/lib/python3.9/site-packages/pyathena/common.py", line 520, in _execute
query_id = retry_api_call(
File "/root/.local/pipx/venvs/dbt-core/lib/python3.9/site-packages/pyathena/util.py", line 68, in retry_api_call
return retry(func, *args, **kwargs)
File "/root/.local/pipx/venvs/dbt-core/lib/python3.9/site-packages/tenacity/__init__.py", line 379, in __call__
do = self.iter(retry_state=retry_state)
File "/root/.local/pipx/venvs/dbt-core/lib/python3.9/site-packages/tenacity/__init__.py", line 314, in iter
return fut.result()
File "/usr/local/lib/python3.9/concurrent/futures/_base.py", line 439, in result
return self.__get_result()
File "/usr/local/lib/python3.9/concurrent/futures/_base.py", line 391, in __get_result
raise self._exception
File "/root/.local/pipx/venvs/dbt-core/lib/python3.9/site-packages/tenacity/__init__.py", line 382, in __call__
result = fn(*args, **kwargs)
File "/root/.local/pipx/venvs/dbt-core/lib/python3.9/site-packages/botocore/client.py", line 530, in _api_call
return self._make_api_call(operation_name, kwargs)
File "/root/.local/pipx/venvs/dbt-core/lib/python3.9/site-packages/botocore/client.py", line 960, in _make_api_call
raise error_class(parsed_response, operation_name)
botocore.errorfactory.InvalidRequestException: An error occurred (InvalidRequestException) when calling the StartQueryExecution operation: line 1:1: mismatched input 'MSCK'. Expecting: 'ALTER', 'ANALYZE', 'CALL', 'COMMENT', 'COMMIT', 'CREATE', 'DEALLOCATE', 'DELETE', 'DENY', 'DESC', 'DESCRIBE', 'DROP', 'EXECUTE', 'EXPLAIN', 'GRANT', 'INSERT', 'MERGE', 'PREPARE', 'REFRESH', 'RESET', 'REVOKE', 'ROLLBACK', 'SET', 'SHOW', 'START', 'TRUNCATE', 'UNLOAD', 'UPDATE', 'USE', 'USING', <query>

Workaround: explicitly use render_hive() in the pre-hooks:

https://github.com/sacundim/covid-19-puerto-rico/commit/e17a6c32f1eeb241c8cdfcf22df4a3c83cbd84c6

An idea that doesn't solve the fundamental problem but may mitigate most of the instances people will encounter (and get mightily confused by): instead of automatically double quoting all identifiers, maybe check them first against a regexp that accepts only valid identifiers and quote them only if they don't match?

Is it really an issue? as you find out using render_hive() is the key and needs only to be documented IMHO, the same is valid for other commands like vacuum and optimize for iceberg. I would avoid to introduce any regex that replace quoting just for specific scenarions.

@nicor88 The problem with "just document it" is that it's a surprising behavior with an obscure cause, which is likely to cause significant grief to unsuspecting users and, as a result, lead to repeated inquiries and bug reports to library maintainers from people who maybe even read the documentation but didn't remember that one sentence.
It's basically XKCD's toaster that stabs users in the face.

Well, we could make it clear for users to explicitly put guidelines and highlight breaking changes in release. Don't people read docs when working with a tool/framework? If they don't they should ;)

repo: dbt-athena/dbt-athena


text:
Requiring Python >=3.8 enables walrus operator

resolves #849
docs N/A

Problem & Solution
The problem and solution are explained clearly in https://github.com/dbt-labs/dbt-bigquery/issues/849
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/relevant for this PR
[x] This PR has no interface changes (e.g. macros, cli, logs, json artifacts, config files, adapter interface, etc)

Could we backport this as well?

Could we backport this as well?

Agreed. We need to backport it all the way since py37 is EOL and no longer supported.

@dbeatty10, do you mind updating the comment at the top of setup.py as well? It doesn't do anything, but if we're updating this, we might as well do both.

@dbeatty10, do you mind updating the comment at the top of setup.py as well? It doesn't do anything, but if we're updating this, we might as well do both.

I updated the comment to be evergreen:
- # require python 3.7 or newer
+ # require a supported version of Python

repo: dbt-labs/dbt-bigquery


text:
Impala support

Support Apache Impala. Apache Impala is a widely distributed engine, used by thousands of enterprise around the world.

How difficult it would be to implement? I know Python to be dangerous but I am not a daily Python developer, only use it occasionally.

Hey @boristyukin - have you seen the docs on building a new adapter? If you're looking for inspiration, you can find some similar adapter plugins here:

https://github.com/jacobm001/dbt-mssql
https://github.com/fishtown-analytics/dbt-spark
https://github.com/fishtown-analytics/dbt-presto

There are broadly two things you need to do when building a new adapter:

write the connection logic for issuing queries and getting back results
write the SQL that dbt uses to build models and inspect the state of the database

I definitely recommend checking out the links above - they should give you a good feel for what's involved here! Please don't hesitate to let me know if you have any questions :)

thanks @drewbanin! looking now...

Hi, @drewbanin I work with @boristyukin and have been looking at dbt for a bit with respect to perhaps implementing an adapter for Impala. I've reviewed the doc and looked at some of the source and have a fundamental question. Given the current design and implementation of dbt, is schema a required attribute for dbt supported databases? (e.g. "schema.table_name")
The folks who designed Impala opted not to implement it this way, and instead only support database.table_name. There's no notion of schema in the sense that you might have with postgres, for instance.
Before I head down a rabbit hole, I thought I'd check with you to see if this would be possible. I tried hacking up some macros for Impala that basically ignored schema in favor of relation.identifer and while a basic "select xxxx from yyyy" type model works fine, anything more advanced than that starts throwing errors due to schema being expected.
Any thoughts?
Thanks!

Hey @ghaskell44! That's really cool, I think Impala is a great target for a dbt database plugin. dbt does generally assume that the databases it works with will have a notion of a database + schema, but I think there's a way to work around that.
We built a plugin for SparkSQL which also does not have a proper notion of "schemas". On Spark, schema is just an alias for database.
We worked around this by making both the database and schema properties required in the Credentials contract, but using some clever logic to use the supplied schema value as the database (if a database config was not provided). The solution on Impala might look a little different, but you should just be able to supply a phony value for the schema I think.
You may also want to set the include_policy for the schema to False. This should cause dbt to render out Relations with <database>.<identifier> instead of <database>.<schema>.<identifier>.
In general, feel free to peruse the Spark plugin and let me know if you have any questions! I think it should account for many of the implementation challenges that you'll see on Impala.

Thanks, @drewbanin! That worked great. I went ahead and set database to False in the include_policy just like Spark since Impala treats database and schema the same, then just used schema in the macros. I think the main thing I was missing was the include_policy but I also added the "clever logic" bit and removed dbname from the profile. My simple models that were failing before are now working correctly.
Thanks again for the pointers. If I get something working that looks full-featured, I'll put it up on GitHub.

closing this one - out of scope for core
@ghaskell44 were you able to get something working? If so, would love to link out to it in the documentation!

we had some roadblocks unfortunately and went a different route with a different tool that already supports Impala. sorry

Hi @boristyukin , Impala user here too, and interested in adopting dbt. May I ask what tool you ended up going for?

Hi @boristyukin , Impala user here too, and interested in adopting dbt. May I ask what tool you ended up going for?

hey @ynouri, we ended up building custom processor in NiFi, that can pick up SELECT statements from files and persist them into tables. Worked quite well for our needs. We could not make Impala work with dbt unfortunately

Hi @boristyukin , yet another Impala user here too, we are considering writing an adapter for Impala for DBT as we are looking to adopt dbt. I was wondering if you recall what were challenges your team hit with it. Thanks!

Hi @boristyukin , yet another Impala user here too, we are considering writing an adapter for Impala for DBT as we are looking to adopt dbt. I was wondering if you recall what were challenges your team hit with it. Thanks!

sorry @tozka I do not remember exactly the challenged we had, but after spending a week or so we gave up because we also had NiFi and we built something custom that worked great for us.

Hi, We now have a working version of dbt-imapla adapter at: https://github.com/cloudera/dbt-impala
Please try out if there is still interest around.

authors: boristyukin drewbanin ghaskell44 tovganesh tozka ynouri

repo: dbt-labs/dbt-core


text:
[CT-2411] [Bug] Ephemeral materialization not working properly with recursive CTE

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
When performing the expansion of the referenced ephemeral models in the final query, the generated CTE are misplaced if the query starts with a WITH RECURSIVE statement.
Expected Behavior
The CTE for the ephemeral models should be inserted after the WITH RECURSIVE statement.
Steps To Reproduce
Let's say we have model_1 using ephemeral materialization:
{{ config(materialized="ephemeral") }}

SELECT
  "Hello" AS greetings

And model_2 using a WITH RECURSIVE statement and referencing model_1:
{{ config(materialized="table") }}

WITH RECURSIVE

  # Not actually recursive CTE.
  target AS (
    SELECT
      "world" AS target
  )

SELECT
  CONCAT(m1.greetings, ", ", t.target, " !!") AS col
FROM
  {{ ref("model_1") }} AS m1
CROSS JOIN
  target AS t

The generated SQL is not valid as the model_1 CTE is inserted between the WITH and the RECURSIVE keywords:
   create or replace table `XXXX`.`XXXX`.`model_2`  as (

WITH  __dbt__cte__model_1 as (
SELECT
  "Hello" AS greetings
),RECURSIVE

  # Not actually recursive CTE.
  target AS (
    SELECT
      "world" AS target
  )

SELECT
  CONCAT(m1.greetings, ", ", t.target, " !!") AS col
FROM
  __dbt__cte__model_1 AS m1
CROSS JOIN
  target AS t
    );

After looking at the source code, it seems the issue comes from this code that only looks for a WITH keyword for determining at which position to insert the CTE generated for the ephemeral models.
Relevant log output
No response
Environment
- OS: Linux Mint 20.3
- Python: 3.11.2
- dbt: 1.4.5

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

Thank you for reporting this @pcasteran !
Thanks also for your simple reprex; I was able to reproduce the behavior you reported (after updating any BigQuery-specific syntax).
Would you be interested in contributing a PR to fix this by any chance?
If so, this could be a nice example to include in the testing.

For anyone wondering the value of recursive CTE, here are a couple resources:

https://duckdb.org/docs/sql/query_syntax/with.html
https://motherduck.com/blog/solving-advent-code-duckdb-dbt/

The following patch:
diff --git a/core/dbt/compilation.py b/core/dbt/compilation.py
index e5503af4..47c6f3fe 100644
--- a/core/dbt/compilation.py
+++ b/core/dbt/compilation.py
@@ -231,7 +231,17 @@ class Compiler:
         with_stmt = None
         for token in parsed.tokens:
             if token.is_keyword and token.normalized == "WITH":
-                with_stmt = token
+                _, next_token = parsed.token_next(
+                    parsed.token_index(token), skip_ws=True, skip_cm=True
+                )
+                if (
+                    next_token is not None
+                    and next_token.is_keyword
+                    and next_token.normalized == "RECURSIVE"
+                ):
+                    with_stmt = next_token
+                else:
+                    with_stmt = token
                 break

         if with_stmt is None:

Works perfectly, but I can't push it right now because mypy complains:
core/dbt/compilation.py:234: error: "Statement" has no attribute "token_next"  [attr-defined]
core/dbt/compilation.py:235: error: "Statement" has no attribute "token_index"  [attr-defined]

So I guess I need to figure out how to add those definitions now.

NM, simplified it to just carry on the loop. Just need to add a test case now.

OK, MR is ready to go now, I think.

authors: dbeatty10 pcasteran willbryant


text:
quoting config not working with 1.8

resolves #1074
docs dbt-labs/docs.getdbt.com/#

Problem
During decoupling work we updated some naming conventions in some macros that seem to go around quotiing_policy, reverting to put us back in good standing.

Solution

Checklist

[x] I have read the contributing guide and understand what's expected of me
[x] I have run this code in development and it appears to resolve the stated issue
[ ] This PR includes tests, or tests are not required/relevant for this PR
[ ] 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

We do this in two spots, so this line would also need updating.

repo: dbt-labs/dbt-snowflake


text:
Feature: Add option to remove the source_column_name on the union_relations macro

This is a:

[ ] documentation update
[ ] bug fix with no breaking changes
[x] new functionality
[ ] a breaking change

All pull requests from community contributors should target the main branch (default).
Description & motivation

This covers issue #331, which allows passing in none in order to omit a source_column_name column when unioning.
Checklist

[x] I have verified that these changes work locally on the following warehouses (Note: it's okay if you do not have access to all warehouses, this helps us understand what has been covered)

[ ] BigQuery
[ ] Postgres
[ ] Redshift
[x] Snowflake - This PR only adds a Jinja snippet and does not modify any SQL.

[x] I followed guidelines to ensure that my changes will work on "non-core" adapters by: N/A

[ ] dispatching any new macro(s) so non-core adapters can also use them (e.g. the star() source)
[ ] using the limit_zero() macro in place of the literal string: limit 0
[ ] using dbt_utils.type_* macros instead of explicit datatypes (e.g. dbt_utils.type_timestamp() instead of TIMESTAMP

[x] I have updated the README.md (if applicable)
[x] I have added tests & descriptions to my models (and macros if applicable)
[x] I have added an entry to CHANGELOG.md

@joellabes I committed your suggestion and also added integration tests! Requested re-review. 😊

repo: dbt-labs/dbt-utils


text:
Update not_null_proportion.sql to handle function in group_by_columns

resolves #
Problem

Refer to In not_null_proportion.sql, when function (e.g. date_trunc) is used in one of group_by_columns, it fails..
Solution

Assign alias to first column in validation CTE, which the alias is used in the following CTE.
Checklist

[v] This code is associated with an issue which has been triaged and accepted for development.
[v] I have read the contributing guide and understand what's expected of me
[v] I have run this code in development and it appears to resolve the stated issue
[v] This PR includes tests, or tests are not required/relevant for this PR
[ ] I have updated the README.md (if applicable)

An error is encountered when running tests against Snowflake. Looks to be a config issue with CircleCI? Can someone help me on this please? Thanks.
10:26:45  Encountered an error:
Runtime Error
  Credentials in profile "integration_tests", target "snowflake" invalid: Runtime Error
    Could not find adapter type snowflake!


text:
Database Error in model: Label value "..." has invalid characters

Describe the bug
After migrating to v0.20.0 my jobs keep failing with the following error:
Database Error in model stg_facebookads__ads (models/staging/facebook_ads/stg_facebookads__ads.sql)
  Label value "__database____REDACTED____schema____dev_edbizarro____identifier____stg_facebookads__ads__" has invalid characters.
  compiled SQL at target/run/insights_lab/models/staging/facebook_ads/stg_facebookads__ads.sql

Steps To Reproduce
Config labels in dbt_project.yml
query-comment:
  comment: "{{ query_comment(node) }}"
  append: false
  job-label: true

Run any model
Expected behavior
Screenshots and log output
If applicable, add screenshots or log output to help explain your problem.
System information
Which database are you using dbt with?

[ ] postgres
[ ] redshift
[x] bigquery
[ ] snowflake
[ ] other (specify: ____________)

The output of dbt --version:
 ❯ dkc exec dbt dbt --version                                                                                [17:52:32]
installed version: 0.20.0
   latest version: 0.20.0

Up to date!

Plugins:
  - redshift: 0.20.0
  - snowflake: 0.20.0
  - bigquery: 0.20.0
  - postgres: 0.20.0

The operating system you're using:
Arch Linux
The output of python --version:
Running through official docker image
Additional context
Add any other context about the problem here.

@edbizarro I see you switched on query-comment.job-label, which is new in v0.20.0. The way that feature works:

Try reading your query comment as a dictionary. If it can, pass each key-value pair as a separate job label. "Sanitize" each value by replacing whitespace and special characters with underscores.
If your query comment can't be read as a dictionary, pass the entire (sanitized) query comment as a single job label.

The latter is what's happening here. Unfortunately, the error BigQuery is giving back is a bit misleading:
Label value "__database____REDACTED____schema____dev_edbizarro____identifier____stg_facebookads__ads__" has invalid characters.

The real issue here is that the label is >63 characters in length (docs), and this string is 89 characters in length. If I shorten the string to 63 characters, everything works just fine.
In the original PR for this feature, we discussed potential approaches for handling too-long labels: https://github.com/dbt-labs/dbt/pull/3145#discussion_r598050639. The options are:

Truncate, hash, or otherwise handle the label length within dbt. This would happen silently, and could result in indistinguishable label values.
Raise an error within dbt.
Do nothing, and return any errors from BigQuery.

We picked the third option. Given the lack of clarity BigQuery's error message, and the ensuing confusion indicated by this issue, I think there's good reason to prefer the second: I think we should raise a compilation error any time query-comment.job-label is switched on and a label value would be >63 characters.
That should be a straightforward change. Is it something you'd be interested in contributing @edbizarro?
In any event, you'll need to work around this error by:

Refactoring your query_comment macro to return a dictionary
Refactoring your query_comment macro to return a shorter string (post-sanitization)
Switching off query-comment.job-label

@jtcohen6 I'm happy to take this issue on if @edbizarro doesn't want to!

@sungchun12 I'd love that!

@jtcohen6 This is officially in my personal backlog that I'll spend the next week or so focusing on!
I'll be diving into #3145. And I'm assuming the solution to this problem will be extending the validations and raising specific error messages in functions like: this and/or create another function dedicated to verifying string length after sanitization.

@sungchun12 Sure! I really want to take this challenge but unfortunately I'm little short in time this next weeks so i would love that someone taking on this

@sungchun12 Yes! I think _sanitize_label raising a ValidationException if passed a string longer than 63 characters will get the job done.

repo: dbt-labs/dbt


text:
Experimental packaging

This PR merges the new packaging functionality. It provides a new subcommand called experimental, along with three new packaging commands dcos experimental package add, dcos experimental package build, and dcos experimental service start. It also provides tests, although a large portion of them are commented out since some of the required functionality is not enabled in cosmos.

Have you run the skipped tests locally? We should have them run if an env var is set.

@tamarrow Yes.

Closing this to avoid permission issues. See for #858 for the continuation.

authors: larioj tamarrow

repo: dcos/dcos-cli


text:
test (Universe) Adds Universe system tests.

Adds the following cases:

Install a certified package using quick-install
Install a community package using quick-install
install certified package using advanced install
Install a community package using advanced install

refs: DCOS-15718
docker run -it --rm --ipc=host \
  -e CLUSTER_URL=$CLUSTER_URL  \
  -v `pwd`:/dcos-ui \
  mesosphere/dcos-ui dcos-system-test-driver \
  --only "universe" \
  ./system-tests/driver-config/dev.sh

Checklist

[x] Did you add a JIRA issue in a commit message or as part of the branch name?
[ ] Did you add new unit tests?
[x] Did you add new integration tests?
[ ] If this is a regression, did you write a test to catch this in the future?

I tested locally on your branch and using a OSS cluster but the test failed.

@weblancaster I fixed it :)

authors: rcorral weblancaster

repo: dcos/dcos-ui


text:
chore(deps): update dependency @types/md5 to v2.2.1

This PR contains the following updates:

Package
Type
Update
Change

@types/md5
devDependencies
patch
2.2.0 -> 2.2.1

Renovate configuration
:date: Schedule: At any time (no schedule defined).
:vertical_traffic_light: Automerge: Disabled by config. Please merge this manually once you are satisfied.
:recycle: Rebasing: Whenever PR becomes conflicted, or if you modify the PR title to begin with "rebase!".
:no_bell: Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

Available now for Enterprise: Renovate Pro with real-time webhook handling and priority job queue.

:tada: This PR is included in version 6.1.14 :tada:
The release is available on:

v6.1.14
GitHub release

Your semantic-release bot :package::rocket:

authors: mesosphere-ci mesosphere-renovate


text:
Admin Router: /marathon endpoint fix

High Level Description
This PR:

fixes /marathon endpoint redirect (see the discussion in the issue for more details)
piggybacks removing some redundant information from README.md
make is_endpoint_redirecting_properly test more flexible - now it is possible to verify the code of the redirect sent by the backend

Related Issues

https://jira.mesosphere.com/browse/DCOS_OSS-1163 - "mycluster.com/marathon" routes to "mycluster.com/ui" => 404

Related PRs
EE PR:

@mesosphere-mergebot bump-ee

@mesosphere-mergebot bump-ee

repo: dcos/dcos


text:
Fix flask-compress import

High-level description
flask.ext.compress moved to flask_compress. This updates the import accordingly.
Corresponding DC/OS tickets (obligatory)
These DC/OS JIRA ticket(s) must be updated (ideally closed) in the moment this PR lands:

DCOS_OSS-2422 test_history_service is failing on master

Checklist for all PRs

[x] Added a comprehensible changelog entry to CHANGES.md or explain why this is not a user-facing change: This fixes an import, no other change is intended.
[x] Included a test which will fail if code is reverted but test is not. If there is no test please explain here: This fixes the unit tests for dcos-history.
[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]

@mesosphere-mergebot bump-ee

@mesosphere-mergebot bump-ee

@mesosphere-mergebot label ready for review

@mesosphere-mergebot label ship-it

@mesosphere-mergebot merge-it

authors: branden orsenthil


text:
[master] Bump Mesos to nightly master f050bf0

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/e65ab60bff4b1b7d4dc9fd892dd632f0d5d57083...f050bf01af8f9f92bbada2c0a2025a459290ed98

[ ] 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 bump-ee

@mesosphere-mergebot Ready For Review

@mesosphere-mergebot label Ready For Review

@mesosphere-mergebot merge-it

authors: jieyu mesosphere-teamcity rukletsov


text:
chore: eslint configuration was added

Summary
We didn't have linter to find problems, so I add this configuration and configured to work with prettier formatter.
This PR can be related with:

Add eslint configuration
Compability with prettier to format the code
Refactor some components with bugs marked of linter

Affected sections

Most components was modified with lint fix

How did you test this change?

All tests was passed ✅

Guys, can you check this PR? @Antonio-Feregrino @jasanhdz @arielsrodriguez @lautarovilas @JuanDominguez1 @Misael840 👀


text:
🛑 Danbs is down

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

HTTP code: 404
Response time: 4541 ms

Resolved: Danbs is back up in 269e9ac after 30 minutes.

repo: ddanbs/upptime


text:
🛑 Danbs is down

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

HTTP code: 404
Response time: 169 ms

Resolved: Danbs is back up in ebea0e1 after 6 minutes.


text:
🛑 Danbs is down

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

HTTP code: 404
Response time: 135 ms

Resolved: Danbs is back up in 66dce40 after 6 minutes.


text:
🛑 Danbs is down

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

HTTP code: 404
Response time: 2004 ms

Resolved: Danbs is back up in dee43e9 after 30 minutes.


text:
🛑 Danbs is down

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

HTTP code: 404
Response time: 91 ms

Resolved: Danbs is back up in 35855d3.


text:
🛑 Danbs is down

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

HTTP code: 404
Response time: 115 ms

Resolved: Danbs is back up in 2d2c054.


text:
🛑 Danbs is down

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

HTTP code: 404
Response time: 3120 ms

Resolved: Danbs is back up in cb74349.


text:
Shouldn't pmiab set the DNSSEC (DS) record when it acts as the primary DNS zone server?

As it is, I have change the domain's NS records at the registrar to point to pmiab and have a secondary set as well.  When I got the registrar's control panel, there are no DNS records to set, since this is delegated to pmiab.
What am I missing here please?

Google domains here. I use glue records and normal NS in the DNS records. Worked fine. Maybe a few more details to get you the help you need.

This has little if anything to do with NS glue records, so I'm not sure I understand your response.   To add DNSSEC I need to add these records somewhere.  That somewhere should be where the zone file is, which is the pmiab machine, not the registrar.   Unless this is not so, the message on the status page of pmiab doesn't make sense.

The DS records (Delegation Signature record) are added to the server that does the delegation.
The server doing the delegation to the server is the registry. Because of that, the DS record needs to be added to the registry. It works exactly the same way with MiaB.
If the DS record was published on it's own zone, it would be basically like issuing a self-signed certificate.

Ah, that makes sense.  I'll have to engage the registrar then.
Thanks for the clarification.
On Fri, 4 Nov 2022 at 00:00, David Duque @.***> wrote:

The DS records (Delegation Signature record) are added to the server that
does the delegation.
The server doing the delegation to the server is the registry. Because of
that, the DS record needs to be added to the registry. It works exactly the
same way with MiaB.
If the DS record was published on it's own zone, it would be basically
like issuing a self-signed certificate.
—
Reply to this email directly, view it on GitHub
https://github.com/ddavness/power-mailinabox/issues/91#issuecomment-1302722968,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABEZPJ744BRWM5TKQ5DURQ3WGQYW3ANCNFSM6AAAAAARV3VKH4
.
You are receiving this because you authored the thread.Message ID:
@.***>

authors: ddavness lifeboy

repo: ddavness/power-mailinabox


text:
Add Astro v3 ViewTransitions support.

Adds View Transitions support.
https://www.youtube.com/watch?v=4Ohi9G-RCcE&ab_channel=LearnWithJason
I saw this on the video above the other day.

yeah, that's one tricky bug to overcome.

Does astro v4 help with any of this?

Not sure it does. As this is a bit of an issue between native javascript API's.
The transition API makes some assumptions that our current script does not take into account.


text:
r still not defined

Describe the bug
I tried node.js v18.15, 18.7 and 19.7 but none worked.
Reproduction
r not defined. consistency issue.
System Info
> chatgpt-api-demo@0.0.1 dev
> astro dev

   astro  v2.1.2 started in 690ms

  ┃ Local    http://localhost:3000/
  ┃ Network  use --host to expose

 error   r is not defined
  File:
    C:\Users\Owner\Desktop\chatgpt-demo-main\chatgpt-demo-main\node_modules\solid-js\web\dist\server.js:297:5
  Code:
    296 |     timeoutHandle = setTimeout(() => reject("renderToString timed out"), timeoutMs);
    > 297 |   });
          |     ^
      298 |   return Promise.race([renderToStream(code, options), timeout]).then(html => {
      299 |     clearTimeout(timeoutHandle);
      300 |     return html;
  Stacktrace:
ReferenceError: r is not defined
    at eval (/node_modules/solid-js/web/dist/server.js:297:5)
    at Module.createRoot (/node_modules/solid-js/dist/server.js:49:14)
    at Module.renderToString (/node_modules/solid-js/web/dist/server.js:294:36)
    at Object.renderToStaticMarkup (@astrojs/solid-js/server.js:16:38)
    at renderFrameworkComponent (/node_modules/astro/dist/runtime/server/render/component.js:178:66)

Used Package Manager
npm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
[X] The provided reproduction is a minimal reproducible of the bug.

Pull the latest code, reinstall the dependencies and try.


text:
Support python 3.12

Some packages' version can't be installed in python 3.12. Need to modify requirements.txt to support python3.12.
numpy==1.24.4
scipy==1.10.1

Hi @ttt-77, Can I help with this?

Yes

Hi @ttt-77, I was able to update numpy and scipy to their Python 3.12 compatible versions, but there the following required modules are blocked for Python 3.12:
ChromaDB:
Requires onnxruntime>=1.14.1 which does not support Python 3.12 yet:
https://github.com/microsoft/onnxruntime/issues/17842
DuckDB:
DuckDB v0.9 does not yet support Python 3.12. The next version, v0.10, will support Python 3.12.
https://duckdb.org/docs/api/python/overview.html
faiss-cpu:
faiss-cpu support for Python 2.12 is also blocked:
https://github.com/kyamagu/faiss-wheels/issues/87
Numba: The issue for numba is still open, I couldn’t test the workaround on 3.12 due to the other blockers.
https://github.com/ddkang/aidb/issues/105
The following modules need to be updated to the specified versions to be 3.12 compatible:
asyncpg==0.28.0 → 0.29.0
greenlet==2.0.2→3.0.3
numpy==1.24.4→1.26.3
scipy==1.10.1→1.12.0

repo: ddkang/aidb


text:
Build and test with Travis CI?

Any interest in getting a build for node-segfault-handler put into Travis CI? In particular, it could be interesting for testing Node 4 as well as doing some kind of integration testing on OS X. If there is, I'll work on a pull request.

Hey @vielmetti that would be fantastic thanks

Also note it would be great to get some tests for travis to actually run
I did an initial one here https://github.com/No9/node-segfault-handler/blob/master/tests/child-test.js
But if you have something more in mind then please work away.

Noting that prebuild Prebuild https://github.com/mafintosh/prebuild would be handy in this area too.

This would be necessary (as well as with appveyor for windows) for #33, and I'd be happy to help :+1:

Hey @maxkorp I would love to get prebuilds in some shape or other into this.
I have found prebuild from @mafintosh "just works" but I haven't seen node-pre-gyp in action although I can see it is used in a lot of projects.
Sorry if I have this wrong but it seems like you want to use both prebuild and node-pre-gyp?
Can you outline the idea a little more as I don't want to waste anybodies time.
Thanks

saying we build on the CI servers normally (just like we would for testing), and then we can publish them using node-pre-gyp (and tie node-pre-gyp into the install lifecycle).

authors: No9 maxkorp vielmetti

repo: ddopson/node-segfault-handler


text:
Support gnome 3.24

Tested this out just now on OpenSUSE Tumbleweed and it seems to be working :)

That's odd, I wonder why it works for me and not for you. Debugging this would probably help a lot.
Speaking of which, does anyone know what the correct way to debug gnome extensions is? I cannot figure out how to "run" gnome extensions from source code so that I can print variables / run breakpoints and there doesn't seem to be any documentation available.

@MichaelAquilina , here are a few tips:
To see the log: sudo journalctl -f /usr/bin/gnome-shell
Gnome shell extensions are installed in: .local/share/gnome-shell/extensions/
You can edit the files in there, adding something like:
let myVariable = 0;
global.log("Value of my variable: " + myVariable.toString());

So that the value is printed to the log.

Found the issue, this extensions needs xprop to be installed otherwise it can't hide the titlebar.

@deadalnix any update on this?

Let's go if people tested.

authors: MichaelAquilina deadalnix franglais125 taaem

repo: deadalnix/pixel-saver


text:
no case clause matching: {:plugin_module_unloadable}

accept
The following plugins have been configured:
rabbitmq_management
rabbitmq_management_agent
rabbitmq_web_dispatch
Applying plugin configuration to rabbit@mq02...
** (CaseClauseError) no case clause matching: {:plugin_module_unloadable, 'prometheus_process_collector', {:error, :on_load_failure}}
(rabbitmqctl) lib/rabbitmq/cli/plugins/plugins_helpers.ex:218: RabbitMQ.CLI.Plugins.Helpers.update_enabled_plugins/2
(rabbitmqctl) lib/rabbitmq/cli/plugins/plugins_helpers.ex:115: RabbitMQ.CLI.Plugins.Helpers.update_enabled_plugins/4
(rabbitmqctl) lib/rabbitmq/cli/plugins/commands/enable_command.ex:104: anonymous fn/6 in RabbitMQ.CLI.Plugins.Commands.EnableCommand.do_run/2
(elixir) lib/stream.ex:1298: anonymous fn/2 in Stream.iterate/2
(elixir) lib/stream.ex:1482: Stream.do_unfold/4
(elixir) lib/stream.ex:1553: Enumerable.Stream.do_each/4
(elixir) lib/stream.ex:933: Stream.do_enum_transform/7
(elixir) lib/stream.ex:1553: Enumerable.Stream.do_each/4

I am getting this error when I enable the plugin, what is the problem?


text:
clipper not saving images along side markdown

I am using Firefox.  In the options for the extension I have:

download API checked
always show save as dialog
download images alongside markdown checked
{title}_data/ as the Image filename prefix template

When I download a page I get the content as content.md but no imahes.  I do get a files called content(1).md which is empty.
EDIT:  I found that even though in Firefox for download location I have "Ask me every time", I could get images downloaded burt they are saved in what was the Downloads (c:\web\saved) folder specified before I switched to "ask every time"

I have this issue too. It asks for the md location and saves it there. But the images are always saved to the default firefox download location.

I have the same problem.
If I "Send Tab to Obsidian", the images are not downloaded and their links in the md file remain the same.
If I "Download Tab as Markdown", the md file and the images are downloaded to the "Download" folder and the links in the md file are updated to local links.

So I check the code, it is a bug for sure https://github.com/aancw/markdownload/blob/82688b831b4e268fdf404d3a2cfccc82b713062e/src/background/background.js#L786
download image is false here, so it will never download the image

solution?

authors: Kmfernan5 csadam lynhai maxisam pcause

repo: deathau/markdownload


text:
Fix or silence clang-tidy warnings

clang-analyzer-security.insecureAPI.DeprecatedOrUnsafeBufferHandling: complains about memset in -std=gnu11 mode
bugprone-macro-parentheses: gives a warning but doesn't say where, looks like a bug to me

I don't see these warnings in Clion, how did you call clang-tidy? What version are you using?

https://gist.github.com/rojer/76819527895acb16b0ea69b9778f6b5a

oh, and the version:
[rojer@nbd ~]$ clang-tidy-15 --version
Ubuntu LLVM version 15.0.7
  Optimized build.
  Default target: x86_64-pc-linux-gnu
  Host CPU: icelake-client

Fixed in 363e7f7480a262f0bbf94c2c9dbe531c80b83418
Thank you

authors: debevv rojer

repo: debevv/nanoMODBUS


text:
DBZ-882 Correct whitelist and blacklist description

schemaName.tableName is not working for me, but I figured that it should be
databaseName.schemaName.tableName. If that's not the desired behavior you can
treat this as a bug report. If that is the desired behavior you have already a
change in the docs.
Please check https://issues.jboss.org/browse/DBZ-882

@jpechane Any thoughts on ^?

@gunnarmorling SQL Server connector instance could theoretically monitor multiple databases in parallel but I am afraid it woould significantly complicate streaming logic so I'd keep the current limitation. I'd look at the filter common code if we can omit the database component from the name.

authors: gunnarmorling jpechane kleewho


text:
TypeError: Cannot read properties of undefined (reading 'length')

Describe the bug
can't add / see content
To Reproduce
Expected behavior
Screenshots

Applicable Versions:

Netlify CMS version: netlify-cms-app@2.12.19
Git provider: git-gateway
Browser version: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/95.0.4638.69 Safari/537.36

CMS configuration
publish_mode: simple
slug:
  encoding: unicode
  clean_accents: false
  sanitize_replacement: "-"
backend:
  name: git-gateway
  branch: main
local_backend: true
media_folder: static/img
public_folder: /img
collections:
  - name: customPages
    label: Custom Pages
    delete: false
    files:
      - file: src/pages/_custom-pages/index.md
        label: Homepage
        name: index
        fields:
          - label: Template Key
            name: templateKey
            widget: hidden
            default: index-page
          - label: Title
            name: title
            widget: string
          - label: Heading
            name: heading
            widget: string
          - label: Introduction
            name: introduction
            widget: string
          - label: Keyframe Text
            name: keyframeText
            widget: list
            collapsed: false
            fields:
              - label: Text
                name: text
                widget: text
              - label: Start Frame
                name: start
                widget: number
                min: 0
                max: 1110
              - label: Stop Frame
                name: stop
                widget: number
                min: 0
                max: 1110
          - label: What We Do Heading
            name: whatWeDoHeading
            widget: string
          - label: What We Do Items
            name: whatWeDoItems
            widget: list
            collapsed: false
            label_singular: Item
            fields:
              - label: Icon
                name: icon
                widget: image
                media_library:
                  config:
                    allow_multiple: false
              - label: Title
                name: title
                widget: string
              - label: Description
                name: description
                widget: text
          - label: Platform Heading
            name: platformHeading
            widget: string
          - label: Platform Items
            name: platformItems
            widget: list
            collapsed: false
            label_singular: Item
            fields:
              - label: Icon
                name: icon
                widget: image
                media_library:
                  config:
                    allow_multiple: false
              - label: Title
                name: title
                widget: string
          - label: How We Create Impact Heading
            name: howWeCreateImpactHeading
            widget: string
          - label: How We Create Impact Items
            name: howWeCreateImpactItems
            widget: list
            collapsed: false
            label_singular: Item
            fields:
              - label: Icon
                name: icon
                widget: image
                media_library:
                  config:
                    allow_multiple: false
              - label: Title
                name: title
                widget: string
              - label: Description
                name: description
                widget: text
          - label: Where We Can Help Heading
            name: whereWeCanHelpHeading
            widget: string
          - label: Where We Can Help Items
            name: whereWeCanHelpItems
            widget: list
            collapsed: false
            label_singular: Item
            fields:
              - label: Icon
                name: icon
                widget: image
                media_library:
                  config:
                    allow_multiple: false

...

Closing as stale.

authors: jadonogh martinjagodic

repo: decaporg/decap-cms


text:
Add instructions on how to add blog posts

Hey, I don't think there are instructions on how to add blog posts and lightning talks to the Participants page for your YAML file. The only thing first flight says is to write your first blog post, but it doesn't say to add it to your YAML file.

This seems like a reasonable request. For the record most of the time @decause will just tell the class (and the TA) the YAML key that the blog post should be tagged with.
An example YAML with firstflight turned in should be
blog: http://fsf.org
feed: http://blog.com/rss.xml
forges:
- http://github.com/username
irc: username
name: Thunder Dome
rit_dce: abc123
hw:
  firstflight: http://google.com

blog: http://fsf.org
feed: http://blog.com/rss.xml
forges: # This is a list
  - http://github.com/username
irc: username
name: Thunder Dome
rit_dce: abc123
hw: # This is  a dictionary (key value)
  firstflight: http://google.com

@Nolski please add these instructions to add firstflight to the students' yaml into the upstream ofcourse repository.
Did we ever implement that ofcourse sync command @liam-middlebrook or @ryansb ?

@decause what does ofcourse sync do?
I'm assuming it's something like update the templates from the ofcourse templates folder into an already-existing content repo. Obviously with conformation for each file unless a -y flag is given.

@liam-middlebrook yeah, that'd be correct

And no, it isn't implemented IIUC.

See ryansb/ofCourse#35

authors: Nolski decause jeid64 liam-middlebrook ryansb

repo: decause/hfoss


text:
Encrypted/signed cookie based session

Hi
As discussed over google group, please merge the branch in which you already implemented the encrypted/signed cookie based session to master.
Thanks a lot
Yans

Read Session section from documentation to find how you can set a custom SessionManager for your application.

I updated the SNAPSHOT on sonatype

That was fast! Thank you,
does this section in the doc still holds true?

Pippo allow you to customize Session via pippo-session module.
If you want a (custom) session manager in your application then you must inject that manager with:
application.setSesionManager(new SessionManager());

Thanks

See here the session demo application.

does this section in the doc still holds true?

I must do a review of Session section.

By the way, Pippo comes with a lot of implementations for Session (ehcache, mongodb, hazelcast, ...). See here the full list.
Thannks @barrantesgerman.

@yan5 Please test the current implementation and if it's OK for you please close it.

Hello @decebals
Thanks for the constant improvements
I was thinking if everything related to encryption should be in a new implementation of SessionDataTranscoder.
Would I like to know your opinion?, and if you agree, I could make the change

@barrantesgerman I understand what you say. The idea is not bad. We can use for implementation the wrapper/decorator (pattern) over a regular SessionDataTranscoder (it's only an idea).
I don't know if it's so valuable for other session implementation but I think that we can do it, so please propose an implementation.

@yan5 We made a little refactoring related to this subject. Please see https://github.com/decebals/pippo/pull/302

authors: barrantesgerman decebals yan5

repo: decebals/pippo


text:
Usul metadata

Description
This PR:

Updates the Usul proposal creation process to include a metadata step with fields for "title", "description", and "additional resources" (an external link)
Replaces the generated proposal titles from decoded data with the metadata title, if one was provided

Notes

Issue / Notion doc (if applicable)
https://github.com/decent-dao/fractal-interface/issues/862

Testing

Create various proposals on a Usul DAO, some providing titles, descriptions, and links, and others not.
Verify that the proposals are displayed correctly in the various views, and show the metadata values when appropriate

Screenshots (if applicable)

Working through these now. Can we handle the changes from "timelock" to "queue" in a separate PR since that is unrelated to this?

@herbig Working through these now. Can we handle the changes from "timelock" to "queue" in a separate PR since that is unrelated to this?

repo: decent-dao/fractal-interface


text:
Odd Invisible Colliders

Carl reports that he found some unexpected invisible colliders in one of his scenes.
He made this video to show the bug:
https://youtu.be/tvcbvSTtseg

My best guess is that it's related to the neighbor scenes, that probably have something that extends outwards. But even if that's the case, we shouldn't have entities from the neighbors interfering with a scene.

According to the video this happens in 15,101 ORG. Leaving this as memo.

I cannot reproduce it, @nearnshaw could you confirm with Carl?

This definitely is still happening.  One place shown in the video has nothing in neighboring scene.  This interferes with dancing in the Conference Center Cafe, too.

@nchamo please raise priority of fixing this.  It is not hard to reproduce, by me or my guests, and is unrelated to content if scenes.  If you follow the steps in the video you should see it.  If not please have someone contact me to demo it.

authors: AjimenezDCL BrianAmadori cfravel nearnshaw

repo: decentraland/explorer


text:
The VideoPlayer component can't be added

If I add components to an empty entity with the + sign, I don't see the VideoPlayer component in the list.
We do have a UI for the VideoPlayer component, because the Video Player smart item does include it and I can configure it there. But I can't add this to a fresh new entity.

this was removed since a video requires a certain components configuration for it to be showed on the preview. Allowing a VideoPlayer component to be added to a new entity will be confusing for a user that does not know what other pieces need to be configured for the video to work.
We definitely can do this, but we should talk about how

authors: nearnshaw nicoecheza

repo: decentraland/sdk


text:
fix: avoid nametag with inconsistend messages

What does this PR change?
Fix #2169
Fix #1774
This PR fixes the issue that caused other user messages to be displayed in our own nametag chat bubble
...
How to test the changes?

Launch the explorer
Chat and check that nametags and chat bubble are on the correct user

Our Code Review Standards
https://github.com/decentraland/unity-renderer/blob/master/docs/code-review-standards.md

Looking over the code it should not affect anything regarding the profiles and right now profiles are broken on main so I think this is OK to merge.

repo: decentraland/unity-explorer


text:
Function-style metaInfo broken with keep-alive

When I use vue-meta with vue-router and <keep-alive>, I can't reliably use the function-style metaInfo.
I have two pages in my application, with the following in their component definitions:
// Page one
...
metaInfo: {
	title: 'Hello world!'
},
...

// Page 2
...
metaInfo: function () {
	return {
		title: 'Route name: ' + this.$route.name
	};
},
...

When I load my application and enter page one, I will see "Hello world!" as the page title. When I switch to page 2, I will see something like "Route name: pageTwoRouteName" as expected. However when I then switch back to page one, the page title is something like "Route name: pageOneRouteName". (The route names are what I have defined in my route configuration.)
It seems that when using a function to return the values for metaInfo, vue-meta starts $watching for the changes but never stores or calls the unwatch callback that would stop listening to the changes and writing, in my case, a new title for the component that has been transitioned out and deactivated but is still alive in the background.
If this is the case then I suspect similar unexpected results happen in any situation where components that use function-style metaInfo are used for a component that is not destroyed when navigating away from them, so it's not vue-router-specific issue even if it's probably the most common use case.
I can work on a PR later on but maybe someone can confirm if this is what's actually happening. If so, maybe just adding the unwatch callbacks to deactivated and beforeDestroy  will do the trick.

It would be indeed awesome if could create a PR to check if the component is deactivated to not watch it.

when keep-alive,

Having this problem too. When using keep-alive the meta tags for that view will stay in the DOM. When navigating instead of updating them new ones are added.
Any ideas for strategies to avoid / circumvent this?

It should be fixed with last version of vue-meta

this bug has not fix yet

authors: Atinux Eiskis Super-Meng jorngeorg laoyoufen

repo: declandewet/vue-meta

license: mit


text:
open pre-trained weights?

Hi @Clement25,
have the pre-trained weights for the different modalities on MEL been made available?

Do you mean "MELD"?

Hi @Clement25, yes, MELD

Sorry for missing this issue and we do not save and upload the pre-trained weights.

repo: declare-lab/MM-Align


text:
Invalid passphrase when creating new account

User reported on the forum:
"I retrieved my wallet with my seed using the GUI wallet, and I was then asked to create a private passphrase. I created a new one. Then, I was able to get my wallet properly, but I can't create a new account, I have a message saying "invalid passphrase for master private key". when I type my new private passphrase."
PM 1.0.5, was a wallet freshly resorted from seed so passphrase was just set.

If this is a bug and not a typo, it will be difficult to track down the cause unless we have more details about the passphrase, or even the passphrase itself.

authors: jcvernaleo jrick

repo: decred/Paymetheus

license: isc


text:
git merge artifacts in translations

I tried a random language (French) and for the 'Decred Network Fee policy' I see:
Frais de réseau>>>>>>> upstream/master
I did not do any more serious checking but it is likely that more of those are in the translations if someone looked.

This one looks good too.  Closing.

repo: decred/copay


text:
Allow installation with fltk-1.3.3

Many linux distros still have the older fltk-1.3.3. Because fltk-1.3.4 is backwards compatible we could make the build smarter to allow both.
This would make installing fltkhs very easy, just install the fltk-dev package and cabal install fltkhs.

When I was coming up with install guides I was pretty torn on whether to tell people to install from the package manager or compile from scratch. At least on Arch and Debian I found that the packages led to runtime dependencies that didn't happen when compiling from scratch (eg. libjpeg, libpng).
Also while 1.3.4 is backwards compatible it does add to the API symbols to the API. I have in turn added bindings for them. I could go with ifdef's and flags but I made the decision that for my own maintenance sanity I would track the latest stable version.
These are great thoughts, though and I like how you're thinking of making the install process easier. It was also primary on my mind when I was writing the package.

Since I am tracking the stable version maybe it makes sense to bundle FLTK source, have Cabal build it along with the bindings and install it the .stack-work directory rather than /usr/lib? Earlier I decided against that because I thought it might piss off some sysadmins.
Another option is to use the linker to smush all the archives into one.
Thoughts?

Those are all valid options. I've learned that, if you want to reach many people, having many build options is the way to go, but providing a default which is very easy to get the hello-world going.
I don't have much time, but would love to put effort in the fltkhs project.

That great news! I welcome and thank you in advance for your efforts.
Do you think that bundling FLTK should be the first step?

Does https://github.com/deech/fltkhs/pull/51 fix this issue?

Yep

authors: deech jputcu

repo: deech/fltkhs


text:
imports/aframe/aframe-graph.tsx(1,1): error TS1208: 'aframe-graph.tsx' cannot be compiled under '--isolatedModules' because it is considered a global script file. Add an import, export, or an empty 'export {}' statement to make it a module.

WARN[0000] /workspace/dev/node_modules/@deep-foundation/hasura/local/docker-compose.yml: `version` is obsolete
[+] Running 37/2
 ✔ minio Pulled             10.1s B Pulling 10.1s
 ✔ storage Pulled           5.3s .3s ⣿⣿⣿⣿] 32.71MB / 32.71MB Pulling 5.3s s
WARN[0010] volume "deep-db-data" already exists but was not created by Docker Compose. Use `external: true` to use an existing volume
[+] Running 4/4
 ✔ Container deep-postgres        Running0.0s
 ✔ Container deep-minio           Started11.2s
 ✔ Container deep-hasura          Started11.2s
 ✔ Container deep-hasura-storage  Started1.5s
npm warn using --force Recommended protections disabled.

> @deep-foundation/deepcase@0.0.121 package:build
> tsc --project tsconfig.json

imports/aframe/aframe-graph.tsx(1,1): error TS1208: 'aframe-graph.tsx' cannot be compiled under '--isolatedModules' because it is considered a global script file. Add an import, export, or an empty 'export {}' statement to make it a module.
imports/test.ts(1,1): error TS1208: 'test.ts' cannot be compiled under '--isolatedModules' because it is considered a global script file. Add an import, export, or an empty 'export {}' statement to make it a module.
npm error Lifecycle script `package:build` failed with error:
npm error code 2
npm error path /workspace/dev/packages/deepcase
npm error workspace @deep-foundation/deepcase@0.0.121
npm error location /workspace/dev/packages/deepcase
npm error command failed
npm error command sh -c tsc --project tsconfig.json
exit

🍊 This task ran as a workspace prebuild
⏱ Well done on saving 5 minutes

This error is reproducible:
gitpod /workspace/dev/packages/deepcase (main) $ npm run package:build

> @deep-foundation/deepcase@0.0.121 package:build
> tsc --project tsconfig.json

imports/aframe/aframe-graph.tsx:1:1 - error TS1208: 'aframe-graph.tsx' cannot be compiled under '--isolatedModules' because it is considered a global script file. Add an import, export, or an empty 'export {}' statement to make it a module.

1 // import * as THREE from "three";

imports/test.ts:1:1 - error TS1208: 'test.ts' cannot be compiled under '--isolatedModules' because it is considered a global script file. Add an import, export, or an empty 'export {}' statement to make it a module.

1

Found 2 errors in 2 files.

Errors  Files
     1  imports/aframe/aframe-graph.tsx:1
     1  imports/test.ts:1
npm ERR! Lifecycle script `package:build` failed with error:
npm ERR! Error: command failed
npm ERR!   in workspace: @deep-foundation/deepcase@0.0.121
npm ERR!   at location: /workspace/dev/packages/deepcase

repo: deep-foundation/deepcase

license: Unlicense


text:
Throw proper error if there is no Value link for type

When we create a type-link:
const {data: [{id: newTypeLinkId}]} = await deep.insert({
  type_id: await deep.id("@deep-foundation/core", "Type")
});

And do not create a Value link from a Type link to a (String)|(Number)|(Object)|(File) link:
// This code should not be executed to reproduce a problem
await deep.insert({
    type_id: await deep.id("@deep-foundation/core", "Value"),
    from_id: newTypeLinkId,
    to_id: await deep.id("@deep-foundation/core", "Number")
})

We get error

field "link_id" not found in type 'links_insert_input'

But should get something like

A link with type_id ["@deep-foundation/core", "Type"] must be created from typeLinkId to (String)|(Number)|(Object)|(File)LinkId to update a value of a link

Or there should be visual message in user interface.

Or there should be visual message in user interface in this case this issue should be transferred to deepcase repository.

This issue should not be transferred to deepcase repository because we still need proper error for deeplinks users. Of course it would be fine to show what's the problem and how to fix it in deepcase

repo: deep-foundation/deeplinks


text:
certbot: ModuleNotFoundError: No module named 'six'

rroot@vds2441251:~/nginx# node configure-nginx.js --configurations "$DEEPCASE_HOST 3007" "$DEEPLINKS_HOST 3006" --certbot-email drakonard@gmail.com
Executing: sudo apt-get update && sudo apt-get install -y nginx certbot ...
Get:1 http://security.ubuntu.com/ubuntu focal-security InRelease [128 kB]
Get:2 http://ppa.launchpad.net/deadsnakes/ppa/ubuntu focal InRelease [18.1 kB]
Get:3 http://mirrors.ubuntu.com/mirrors.txt Mirrorlist [380 B]
Get:5 http://mirrors.powernet.com.ru/ubuntu focal-updates InRelease [128 kB]
Get:7 http://ppa.launchpad.net/deadsnakes/ppa/ubuntu focal/main amd64 Packages [30.0 kB]
Get:8 http://ppa.launchpad.net/deadsnakes/ppa/ubuntu focal/main i386 Packages [14.7 kB]
Hit:4 https://mirror.neftm.ru/ubuntu focal InRelease
Get:9 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages [2,956 kB]
Get:10 http://security.ubuntu.com/ubuntu focal-security/main i386 Packages [756 kB]
Get:11 http://security.ubuntu.com/ubuntu focal-security/main Translation-en [444 kB]
Get:6 https://mirror.truenetwork.ru/ubuntu focal-backports InRelease [128 kB]
Get:12 http://security.ubuntu.com/ubuntu focal-security/restricted i386 Packages [36.4 kB]
Get:13 http://security.ubuntu.com/ubuntu focal-security/restricted amd64 Packages [2,837 kB]
Ign:15 http://mirror.corbina.net/ubuntu focal-updates/main amd64 Packages
Get:21 http://mirrors.powernet.com.ru/ubuntu focal-updates/universe amd64 Packages [1,189 kB]
Get:14 http://mirror.timeweb.ru/ubuntu focal-updates/main i386 Packages [980 kB]
Get:17 http://mirror.corbina.net/ubuntu focal-updates/restricted amd64 Packages [2,953 kB]
Get:16 http://mirror.docker.ru/ubuntu focal-updates/main Translation-en [525 kB]
Get:25 http://security.ubuntu.com/ubuntu focal-security/restricted Translation-en [397 kB]
Get:26 http://security.ubuntu.com/ubuntu focal-security/universe amd64 Packages [963 kB]
Get:27 http://security.ubuntu.com/ubuntu focal-security/universe i386 Packages [659 kB]
Get:28 http://security.ubuntu.com/ubuntu focal-security/universe Translation-en [203 kB]
Get:29 http://security.ubuntu.com/ubuntu focal-security/multiverse amd64 Packages [24.0 kB]
Get:19 https://mirror.truenetwork.ru/ubuntu focal-updates/restricted Translation-en [413 kB]
Get:30 http://security.ubuntu.com/ubuntu focal-security/multiverse Translation-en [5,904 B]
Get:24 http://archive.ubuntu.com/ubuntu focal-updates/multiverse Translation-en [7,880 B]
Get:23 http://mirror.docker.ru/ubuntu focal-updates/multiverse amd64 Packages [26.2 kB]
Get:18 https://mirror.hyperdedic.ru/ubuntu focal-updates/restricted i386 Packages [37.7 kB]
Get:22 http://mirrors.powernet.com.ru/ubuntu focal-updates/universe Translation-en [285 kB]
Get:20 https://mirror.truenetwork.ru/ubuntu focal-updates/universe i386 Packages [786 kB]
Get:15 http://mirror.timeweb.ru/ubuntu focal-updates/main amd64 Packages [3,332 kB]
Fetched 20.3 MB in 4s (4,768 kB/s)
Reading package lists... Done
Reading package lists... Done
Building dependency tree
Reading state information... Done
nginx is already the newest version (1.18.0-0ubuntu1.4).
certbot is already the newest version (0.40.0-1ubuntu0.1).
The following packages were automatically installed and are no longer required:
  libstd-rust-1.70 linux-headers-5.4.0-29 linux-headers-5.4.0-29-generic linux-image-5.4.0-29-generic linux-modules-5.4.0-29-generic
  linux-modules-extra-5.4.0-29-generic
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 52 not upgraded.
Executing: sudo touch /etc/nginx/sites-available/deep ...
Executing: sudo chmod 777 /etc/nginx/sites-available/deep ...
Executing: sudo ln -sf /etc/nginx/sites-available/deep /etc/nginx/sites-enabled/ ...
Executing: sudo nginx -t ...
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful
Executing: sudo systemctl restart nginx ...
Executing: sudo certbot certonly --webroot --webroot-path=/var/www/html -d chatgpt.deep.foundation -n --agree-tos -m drakonard@gmail.com ...
Traceback (most recent call last):
  File "/usr/bin/certbot", line 11, in <module>
    load_entry_point('certbot==0.40.0', 'console_scripts', 'certbot')()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 490, in load_entry_point
    return get_distribution(dist).load_entry_point(group, name)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2854, in load_entry_point
    return ep.load()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2445, in load
    return self.resolve()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2451, in resolve
    module = __import__(self.module_name, fromlist=['__name__'], level=0)
  File "/usr/lib/python3/dist-packages/certbot/main.py", line 9, in <module>
    import configobj
  File "/usr/lib/python3/dist-packages/configobj.py", line 22, in <module>
    import six
ModuleNotFoundError: No module named 'six'
Error: Command exited with code 1.

Solution
apt --reinstall install python3-debian
apt --reinstall install python3-six
apt --reinstall install python3-certifi
apt --reinstall install python3-requests

repo: deep-foundation/dev


text:
[CONTROLLER/TAGRECORDER] support cluster redis #19808

Server

Fixes cluster redis error
Steps to reproduce the bug
Changes to fix the bug
Affected branches

main

Checklist

[ ] Added unit test to verify the fix.

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

repo: deepflowys/deepflow


text:
adds css + svg for playground call-out

adds the css for the new API Playground callout
adds codey svg
tested locally, renders correctly.

@SandraRodgers  I could use some help getting the SVG to positioned within the call-out itself based on the design.

repo: deepgram-devs/docs-cdn


text:
Improve retries for failed Requests

Issue
Performing retries on failed Rest requests could be easier.
Acceptance Criteria

For Rest Requests make it easy to implement retries

@lukeocodes

repo: deepgram/deepgram-js-sdk


text:
iris grid partition selector can only display 1000 paritions

from deephaven import empty_table
t = empty_table(15000).update(["x = i", "y = i"]).partition_by(["x"])

Viewing multiple years of a daily partitioned table can easily exceed the 1000 item limit. The partition select is limited by us to 1000 items for performance. (And is capped by the browser at 10000 in chrome).
We should switch the selector to use the spectrum select which is virtualized and can handle a much higher number of rows (hundreds of thousands).

Should use the Picker component from @deephaven/jsapi-components.

authors: dsmmcken mofojed

repo: deephaven/web-client-ui


text:
perf: remove workspace dependancy from iris-grid-panel and memoize settings redux selector

Discovered as part of #1977 investigation. Typing in a notebook triggers a workspace update, which was triggering all tables to re-render. Removed deprecated dependeny of workspace from iris-grid.
Further settings is derived from workspace and returns a new settings object. Iris-grid depends on settings, but the object had no changes. Memoize the selector so it always returns the same object if settings haven't changed.
Removes ~100ms of lag that was occuring 400ms after the debounce of notebook key press events.
BREAKING CHANGE: getPluginContent deprecatedProps have been removed from iris-grid

Was this tested with enterprise table plugins? I think it would break any customers using table plugins

authors: dsmmcken mattrunyon


text:
🛑 Provider IFCA-LCG2   org.openstack.nova is down

In c3e2611, Provider IFCA-LCG2   org.openstack.nova (https://api.cloud.ifca.es:5000/v3) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Provider IFCA-LCG2   org.openstack.nova is back up in 7da6361.

repo: deephdc/status


text:
feat: add geographiclib

Geographiclib is a C++ library to solve some geodesic problems
Log: add geographiclib
Issue: https://github.com/deepin-community/sig-deepin-sysdev-team/issues/327

@chenchongbiao OBS通过，请老师检查

repo: deepin-community/geographiclib