fmstrat

cross-posted from: https://lemmy.nowsci.com/post/7576006

Hey all,

In the market for a GPU, would like to use Bazzite, mostly a Steam user with some SteamVR (rare), and have run into nvidia issues with Bazzite and a 3070 previously.

With the recent news on nVidia's beta drivers and Plasma's sync support in beta, I'm newly on the fence about switching to AMD given nvidia having a better performance to cost ratio, the power usage (big one for a compact living room system), and the fact that they have the potential for HDMI2.1 support which AMD doesn't have a solution to yet.

What are community thoughts? I'll probably hold out for some reports on the new drivers regardless, but wanted to check in with the hive mind.

Thanks!

Hey all,

In the market for a GPU, would like to use Bazzite, mostly a Steam user with some SteamVR (rare), and have run into nvidia issues with Bazzite and a 3070 previously.

With the recent news on nVidia's beta drivers and Plasma's sync support in beta, I'm newly on the fence about switching to AMD given nvidia having a better performance to cost ratio, the power usage (big one for a compact living room system), and the fact that they have the potential for HDMI2.1 support which AMD doesn't have a solution to yet.

What are community thoughts? I'll probably hold out for some reports on the new drivers regardless, but wanted to check in with the hive mind.

Thanks!

Hi all,

Hoping someone can help me out here. I just did the upgrade, I've updated my ENV variables, and started, and I get:

2024-05-18T19:13:07.047224829Z 2024-05-18T19:13:07.046998Z  INFO migrate_04: pict_rs::repo::migrate: Running checks
2024-05-18T19:13:08.177484313Z 2024-05-18T19:13:08.177294Z  INFO migrate_04: pict_rs::repo::migrate: Checks complete, migrating repo
2024-05-18T19:13:08.177524752Z 2024-05-18T19:13:08.177323Z  INFO migrate_04: pict_rs::repo::migrate: 362224 hashes will be migrated

I then proceed to get the following item for 110,670 files:

2024-05-18T19:13:08.196186995Z 2024-05-18T19:13:08.196036Z ERROR pict_rs::repo::migrate: Failed to migrate hash 0000181884f6a92c7f6ee411dc8049474b2872204fafebbc6b0170e7499d902b, skipping
2024-05-18T19:13:08.207066220Z 
2024-05-18T19:13:08.207078792Z    0: Error in store
2024-05-18T19:13:08.207089618Z    1: Requested file is not found
2024-05-18T19:13:08.207099605Z    2: No such file or directory (os error 2)
2024-05-18T19:13:08.207109313Z 
2024-05-18T19:13:08.207119231Z Location:
2024-05-18T19:13:08.207129638Z    /drone/src/src/repo/migrate.rs:32

And then pict-rs just exits.

Turning on debug gives me more info, but nothing helpful after each of the above errors:

|lemmy-pictrs  | 2024-05-18T19:21:15.631508936Z 2024-05-18T19:21:15.631417Z DEBUG sled::pagecache::iobuf: advancing offset within the current segment from 102576771 to 102576797    
|lemmy-pictrs  | 2024-05-18T19:21:15.631606646Z 2024-05-18T19:21:15.631504Z DEBUG sled::pagecache::iobuf: advancing offset within the current segment from 102576797 to 102576823    
|lemmy-pictrs  | 2024-05-18T19:21:15.631643803Z 2024-05-18T19:21:15.631531Z DEBUG sled::pagecache::iobuf: wrote lsns 3029152387-3029152412 to disk at offsets 102576771-102576796, maxed false complete_len 26    
|lemmy-pictrs  | 2024-05-18T19:21:15.631661473Z 2024-05-18T19:21:15.631541Z DEBUG sled::pagecache::iobuf: advancing offset within the current segment from 102576823 to 102576849    
|lemmy-pictrs  | 2024-05-18T19:21:15.631676419Z 2024-05-18T19:21:15.631549Z DEBUG sled::pagecache::iobuf: mark_interval(3029152387, 26)    
|lemmy-pictrs  | 2024-05-18T19:21:15.631689340Z 2024-05-18T19:21:15.631561Z DEBUG sled::pagecache::iobuf: new highest interval: 3029152387 - 3029152412

My env (left old values in, too):

      - PICTRS_OPENTELEMETRY_URL=http://otel:4137
      - PICTRS__API_KEY=...
      - PICTRS__SERVER__API_KEY=...
      - RUST_LOG=debug
      #- RUST_BACKTRACE=full
      - PICTRS__MEDIA__VIDEO_CODEC=vp9
      - PICTRS__MEDIA__GIF__MAX_WIDTH=256
      - PICTRS__MEDIA__GIF__MAX_HEIGHT=256
      - PICTRS__MEDIA__GIF__MAX_AREA=65536
      - PICTRS__MEDIA__GIF__MAX_FRAME_COUNT=400
      - PICTRS__MEDIA__ANIMATION__MAX_WIDTH=256
      - PICTRS__MEDIA__ANIMATION__MAX_HEIGHT=256
      - PICTRS__MEDIA__ANIMATION__MAX_AREA=65536
      - PICTRS__MEDIA__ANIMATION__MAX_FRAME_COUNT=400
      - PICTRS__MEDIA__VIDEO__ENABLE=True
      - PICTRS__MEDIA__VIDEO__MAX_FILE_SIZE=20

Any idea how to get pict-rs started? Or what I should look to for figuring this out.

Edit: Scanning the logs more closely I see that I never get the Migration complete message from here https://git.asonix.dog/asonix/pict-rs/src/commit/d45e3fa386e62e0538b3d7ba399ceaec80fdd7ca/src/repo/migrate.rs#L175, but I do get percentage completes up to Migration 59% complete - 213698/362224. Nothing else indicates, though.

A long read for normal Lemmy posts, but well cited including a study on stress during pregnancy. The links to the studies do have statistics if you are interested in further reading.

It's not just what you'd expect, it includes things like algae blooms growing that release neurotoxins, etc.

cross-posted from: https://lemmy.nowsci.com/post/3852588

I'll be creating one for GifYourGame, too.

An interesting tidbit from Mozilla's latest privacy release (https://www.ghacks.net/2023/11/21/firefox-120-ships-today-with-massive-privacy-improvements/):

The first introduces support for the Global Privacy Control in Settings. The privacy feature informs websites that you visit that you don't want your data sold or shared. It is legally binding in some states in the United States, including in California and Colorado.

What's to stop users from utilizing a VPN exit point in California or Colorado to force the binding nature of the request?

Hi all,

I'm not sure how/where to report something like this. I conducted a change of address on USPS.com, and they partner with MYMOVE to handle Voter Registration. However, instead of sending me my VR form, they sent me someone else's, which, considering the "password" was the new zip code, leaves that individual's name and address information exposed, and thus potentially my own to others.

While I have reached out to MYMOVE including requesting any PDF generation and/or delivery of my information, who should I reach out to for reporting something like this?

Thanks.

So I'm doing some testing of USB-C cables using a tester and a constant load (I'll have another post soon with some questions on this). But before running each test, I'm checking the E-mark chip and then enumerating the charge capabilities of each to see what they report being capable of.

I'll use 3 different brands of cables as samples of my question. Power Supply (PS) 1 is an Anker 100W with PPS support. PS2 is a MacBook Pro 94W brick with no PPS support.

• Cable A
  • Emark: 20V@5A USB3.2 Gen 2
  • Max PD using PS1: PD3.0 PPS 29W
  • Max PD using PS2: PD2.0 94W
• Cable B
  • Emark: 20V@5A USB3.2 Gen 2
  • Max PD using PS1: PD3.0 PPS 100W
  • Max PD using PS2: Not tested
• Cable C
  • Emark: 50V@5A USB2.0
  • Max PD using PS1: PD3.0 PPS 29W
  • Max PD using PS2: PD2.0 94W

So the question: What would be limiting Cables A and C to PPS 29W?

As with many others, I've recently needed to do some purging of media in Pict-rs. What I also discovered is that due to an issue with either Lemmy, Pict-rs, or my setup, at some point Pict-rs was not properly removing files from the file system on a purge, leaving about 20GB of media orphaned.

To combat this, I've updated LPP with some additional configuration options to do both direct "purge" of leftover media in Pict-rs not tied to "kept" posts and a forced "remove" of files on the file system that are not properly purged (if using local storage).

You can find all the new options at the GitHub link above.

As a reminder, LPP only removes posts/media older than a specified time if they have not been posted, marked read, voted on, commented on, had comments voted on, or saved by users on your instance.