Will Clipy be updated for M1 processors?

Hi all! First off, thank you for writing the single most useful program I use on my computer.
I'm considering upgrading to an M1 computer and wondering if you'll be releasing a universal binary for Clipy?
Thanks very much!

+1

It will be supported. The M1 Mac will be delivered to me by the end of this year, so please wait a little longer.

Thanks @Econa77.
Off-topic #1: I have received my M1 laptop and I love it. Well, it's just a laptop after all. But so much of it just feels right. And I already notice that my battery anxiety has dropped significantly. I pay less and less attention to the symbol in the menubar.
Off-topic #2: Not to push but out of curiosity as a non-developer. I understood that one can develop and compile for either platform (M1, x86) from either platform. Is that not so? (because you are waiting for your M1 Mac).

It will be supported. The M1 Mac will be delivered to me by the end of this year, so please wait a little longer.

nice!  ありがとう！

Any news about version for Apple M1?

Oddly enough Clipy was working for me on my M1 chip, though slightly buggy, it would crash whatever program I was using if I wanted to paste an image that was in anything other than the first clipboard spot. So I deleted it, in hopes of downloading a newer version, only to have the issue that the program downloads fine but won't open. Despite looking like it's opening the application, it doesn't show in my toolbar nor in any of my open apps.

I have been using Clippy on my M1 mini without much issue. It may well be that my usage habits don't expose the issues or bugs others may be seeing. I will say that Clippy is ESSENTIAL to my job though. I would be back on an Intel Mac if Clippy were not working for me. I'm looking forward to an M1 native version.

M1 native version please +1

https://github.com/rene-dohan/Clipy/releases/tag/2.0.0

Crippled version that is working native on apple silicon

Crippled version that is working native on apple silicon

Broken link. Seems that fork has disappeared.

Hello @Econa77, thanks for making this great tool that I have been using for over 3 years. Since you already fixed building for m1, could you please make an official release?

Looking forward to native M1 support here too. Not that I have particular issues with it now.

I'm waiting on a native M1 version. Having Rosetta 2 running in the background uses up memory and somehow slows down an M1 Mac. Tried first with Mac Mini 8GB RAM and later with an M1 Pro MacBook Pro 14 with 16GB RAM. I'm not really a Clipy refugee but a ClipMenu user who is moving straight from Mojave to Monterey (with a brief visit of Big Sur on 2009 Intel Mac Pros and M1 Mac Mini). None of the alternatives compare with efficient ClipMenu and Clipy with too much interface, inadequate keyboard shortcuts and way too much code.

What's the update on this?

Having Rosetta 2 running in the background

@mntbighker Rosetta 2 does not run in the background. It translates "intel code" (x86-64) to "M1 code" the first time the app run (I believe it also support just in time compilation but seem to use ahead of time compilation most of the time). Furthermore, rosetta 2 complied code is fast mainly because Apple Silicon support support of x86-64 memory ordering.
In practice, on my M1 Clipy take about 30Mb ram. With 16GB it should definitely be no issue. When not pasting something Clipy is using less than 0.1% on my M1 air... so again should not be an issue. It take about 5% when pasting, and this could eventually be improved but really... who care?
For sure native M1 support would be a nice to have, but if your computer is slow it as certainly nothing to do with Clipy. Or it's a bug.

Is it possible that we can download and recompile the source on an M1 machine to get a native version?

But, I did find a pre-compiled version at https://github.com/ian4hu/Clipy that is a native ARM release.

Yes, good find. Thanks to your pointer, I'm now using the ian4hu ARM version on an M1 Max on Monterey and it works a treat. Great to have Clipy back.
I've also installed his Universal Binary on an Intel Mac Mini on Big Sur and it works fine there too. There's quite a few releases between the main Clipy version and the ian4hu versions since then. It would be great if the two teams could somehow join forces again.

Normally I wouldn't point to another project like this, but since clipy isn't really being maintained anymore... For those that want very similar functionality on a project that is still being maintained, I'd recommend checking out https://maccy.app

I'm not normally a fan of pointing to other projects either. Ian Hu's Clipy is working great on my M1 Max. But out of foolish curiousity, I am trying Maccy. Maccy installs okay from Github and does seem to do what it promises in a minimalist way. There is a release-quality M1 version since January 2021.
I.e. this is not a long term review but Maccy is worth checking out and worth donating to via Gumroad is it suits some better than Clipy. The search is a neat addition.

First of all, I'm such a huge fan of Clipy! It's in my laptop for several years now.
I just received my new M1 macbook today and the first thing I did was to look for arm64's version on Clipy, but sadly I found out that there is none "official" at the moment.
So I'm using Maccy, mentioned by @yourfavorite and @foliovision, and I have to say it seems really really great.

Is there any good alternative that has the same simplicity and snippets feature as Clipy?
I'm using this fork that does work on my M1 mac but for some reason, I lost the ability to edit the snippets, they do exist from my previous mac before I migrated to the M1.
I try several other forks like this but they are all crashing and not even starts
-------------------------------------
Translated Report (Full Report Below)
-------------------------------------

Process:               Clipy [13021]
Path:                  /Volumes/VOLUME/*/Clipy.app/Contents/MacOS/Clipy
Identifier:            com.clipy-app.Clipy
Version:               1.2.12 (1.2.12)
Code Type:             ARM-64 (Native)
Parent Process:        launchd [1]
User ID:               501

Date/Time:             2022-11-11 15:47:53.7334 +0200
OS Version:            macOS 13.0.1 (22A400)
Report Version:        12
Anonymous UUID:        580A62C9-6E27-1C9A-258E-7927EEEB4323

Sleep/Wake UUID:       9A43577C-9754-402F-B249-0D49FA572D01

Time Awake Since Boot: 820 seconds
Time Since Wake:       377 seconds

System Integrity Protection: enabled

Notes:
dyld_process_snapshot_create_for_process failed with 5

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_BREAKPOINT (SIGTRAP)
Exception Codes:       0x0000000000000001, 0x00000001a3fb7218

Termination Reason:    Namespace SIGNAL, Code 5 Trace/BPT trap: 5
Terminating Process:   exc handler [13021]

Error Formulating Crash Report:
dyld_process_snapshot_create_for_process failed with 5

Thread 0 Crashed::  Dispatch queue: com.apple.main-thread
0   libswiftCore.dylib            	       0x1a3fb7218 _assertionFailure(_:_:file:line:flags:) + 316
1   libswiftCore.dylib            	       0x1a3fb7218 _assertionFailure(_:_:file:line:flags:) + 316
2   libswiftCore.dylib            	       0x1a4029bc0 swift_unexpectedError + 652
3   Clipy                         	       0x1044224e4 0x1043f0000 + 206052
4   Clipy                         	       0x1043fc8dc 0x1043f0000 + 51420
5   CoreFoundation                	       0x19634d9d8 -[NSSet makeObjectsPerformSelector:] + 176
6   AppKit                        	       0x199592a68 -[NSIBObjectData nibInstantiateWithOwner:options:topLevelObjects:] + 828
7   AppKit                        	       0x1995885d8 loadNib + 340
8   AppKit                        	       0x199587c08 +[NSBundle(NSNibLoading) _loadNibFile:nameTable:options:withZone:ownerBundle:] + 560
9   AppKit                        	       0x19958790c -[NSBundle(NSNibLoading) loadNibNamed:owner:topLevelObjects:] + 180
10  AppKit                        	       0x199587730 +[NSBundle(NSNibLoading) loadNibNamed:owner:] + 300
11  AppKit                        	       0x19957aed0 NSApplicationMain + 488
12  Clipy                         	       0x1043f21f0 0x1043f0000 + 8688
13  dyld                          	       0x195f4fe50 start + 2544

Thread 1:
0   libsystem_pthread.dylib       	       0x196274e18 start_wqthread + 0

Thread 2:
0   libsystem_pthread.dylib       	       0x196274e18 start_wqthread + 0

Thread 3:
0   libsystem_pthread.dylib       	       0x196274e18 start_wqthread + 0

Thread 0 crashed with ARM Thread State (64-bit):
    x0: 0x000000014b808200   x1: 0x00000001a433f6d8   x2: 0x000000014b800000   x3: 0x0000000000000000
    x4: 0xffffffffffffb413   x5: 0x0000000000000013   x6: 0x0000000000000020   x7: 0x0000000000000001
    x8: 0x000000014b808208   x9: 0x0000000200000003  x10: 0xfffffffe00000000  x11: 0x0000000200000003
   x12: 0x0000000000000003  x13: 0x0000000000000003  x14: 0x000000014b800000  x15: 0x00000000ffff7dff
   x16: 0x00000002ec46be64  x17: 0x00000001960dfab8  x18: 0x0000000000000000  x19: 0x000000014b808200
   x20: 0x0000000000000002  x21: 0x0000000000000000  x22: 0x000000000000001b  x23: 0x0000000104808bb0
   x24: 0xf00000000000129e  x25: 0x00000001a4496224  x26: 0x000000000000000b  x27: 0x0000000d00000004
   x28: 0x0000000000000001   fp: 0x000000016ba0ecb0   lr: 0x00000001a3fb7218
    sp: 0x000000016ba0ec30   pc: 0x00000001a3fb7218 cpsr: 0x60001000
   far: 0x000060000380c000  esr: 0xf2000001 (Breakpoint) brk 1

Binary Images:
       0x1a3f80000 -        0x1a44cdfff libswiftCore.dylib (*) <18b6c203-512a-36e9-9c56-1eca60868332> /usr/lib/swift/libswiftCore.dylib
       0x1043f0000 -        0x1048b7fff com.clipy-app.Clipy (1.2.12) <5902f877-2b7a-310a-acd5-95a4783ef03b> /Volumes/VOLUME/*/Clipy.app/Contents/MacOS/Clipy
       0x1962d8000 -        0x1967affff com.apple.CoreFoundation (6.9) <f4ff83fc-e62c-30b4-b3a9-876c8a1fd595> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
       0x199577000 -        0x19a47efff com.apple.AppKit (6.9) <af9f6891-70ad-3c26-af08-b747344892d2> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
       0x195f4a000 -        0x195fd44bf dyld (*) <de46dd52-4994-3fd8-b4b4-e352a1a19354> /usr/lib/dyld
       0x196273000 -        0x19627fffb libsystem_pthread.dylib (*) <886caca0-5762-3640-8db2-3fa3b911c062> /usr/lib/system/libsystem_pthread.dylib

External Modification Summary:
  Calls made by other processes targeting this process:
    task_for_pid: 0
    thread_create: 0
    thread_set_state: 0
  Calls made by this process:
    task_for_pid: 0
    thread_create: 0
    thread_set_state: 0
  Calls made by all processes on this machine:
    task_for_pid: 0
    thread_create: 0
    thread_set_state: 0

VM Region Summary:
ReadOnly portion of Libraries: Total=1.1G resident=0K(0%) swapped_out_or_unallocated=1.1G(100%)
Writable regions: Total=698.3M written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=698.3M(100%)

                                VIRTUAL   REGION
REGION TYPE                        SIZE    COUNT (non-coalesced)
===========                     =======  =======
Activity Tracing                   256K        1
ColorSync                          448K       22
CoreGraphics                        16K        1
CoreServices                       192K        1
Kernel Alloc Once                   32K        1
MALLOC                           184.3M       28
MALLOC guard page                  192K       11
MALLOC_MEDIUM (reserved)         120.0M        1         reserved VM address space (unallocated)
MALLOC_NANO (reserved)           384.0M        1         reserved VM address space (unallocated)
STACK GUARD                       56.1M        4
Stack                             9808K        4
VM_ALLOCATE                         32K        2
__AUTH                             980K      231
__AUTH_CONST                      17.6M      423
__CTF                               756        1
__DATA                            6634K      411
__DATA_CONST                      19.5M      428
__DATA_DIRTY                      1246K      146
__FONT_DATA                        2352        1
__LINKEDIT                       763.2M        4
__OBJC_CONST                      2380K      195
__OBJC_RO                         65.1M        1
__OBJC_RW                         1981K        1
__TEXT                           400.6M      449
dyld private memory                256K        1
mapped file                      153.0M       12
shared memory                      848K       13
===========                     =======  =======
TOTAL                              2.1G     2394
TOTAL, minus reserved VM space     1.6G     2394

-----------
Full Report
-----------

{"app_name":"Clipy","timestamp":"2022-11-11 15:48:00.00 +0200","app_version":"1.2.12","slice_uuid":"5902f877-2b7a-310a-acd5-95a4783ef03b","build_version":"1.2.12","platform":1,"bundleID":"com.clipy-app.Clipy","share_with_app_devs":0,"is_first_party":0,"bug_type":"309","os_version":"macOS 13.0.1 (22A400)","roots_installed":0,"name":"Clipy","incident_id":"221AE851-AC7C-44A8-B3AD-025722856893"}
{
  "uptime" : 820,
  "procRole" : "Default",
  "version" : 2,
  "userID" : 501,
  "deployVersion" : 210,
  "modelCode" : "MacBookPro18,4",
  "coalitionID" : 1739,
  "osVersion" : {
    "train" : "macOS 13.0.1",
    "build" : "22A400",
    "releaseType" : "User"
  },
  "captureTime" : "2022-11-11 15:47:53.7334 +0200",
  "incident" : "221AE851-AC7C-44A8-B3AD-025722856893",
  "pid" : 13021,
  "translated" : false,
  "cpuType" : "ARM-64",
  "roots_installed" : 0,
  "bug_type" : "309",
  "procLaunch" : "2022-11-11 15:47:51.8474 +0200",
  "procStartAbsTime" :<PHONE_NUMBER>6,
  "procExitAbsTime" :<PHONE_NUMBER>1,
  "procName" : "Clipy",
  "procPath" : "\/Volumes\/VOLUME\/*\/Clipy.app\/Contents\/MacOS\/Clipy",
  "bundleInfo" : {"CFBundleShortVersionString":"1.2.12","CFBundleVersion":"1.2.12","CFBundleIdentifier":"com.clipy-app.Clipy"},
  "storeInfo" : {"deviceIdentifierForVendor":"D7A04B70-A9C4-5928-804C-6171178F02DA","thirdParty":true},
  "parentProc" : "launchd",
  "parentPid" : 1,
  "coalitionName" : "com.clipy-app.Clipy",
  "crashReporterKey" : "580A62C9-6E27-1C9A-258E-7927EEEB4323",
  "wakeTime" : 377,
  "sleepWakeUUID" : "9A43577C-9754-402F-B249-0D49FA572D01",
  "sip" : "enabled",
  "exception" : {"codes":"0x0000000000000001, 0x00000001a3fb7218","rawCodes":[1,7046132248],"type":"EXC_BREAKPOINT","signal":"SIGTRAP"},
  "termination" : {"flags":0,"code":5,"namespace":"SIGNAL","indicator":"Trace\/BPT trap: 5","byProc":"exc handler","byPid":13021},
  "os_fault" : {"process":"Clipy"},
  "extMods" : {"caller":{"thread_create":0,"thread_set_state":0,"task_for_pid":0},"system":{"thread_create":0,"thread_set_state":0,"task_for_pid":0},"targeted":{"thread_create":0,"thread_set_state":0,"task_for_pid":0},"warnings":0},
  "faultingThread" : 0,
  "threads" : [{"triggered":true,"id":56088,"threadState":{"x":[{"value":5561680384},{"value":7049836248,"symbolLocation":0,"symbol":"_swift_release_"},{"value":5561647104},{"value":0},{"value":18446744073709532179},{"value":19},{"value":32},{"value":1},{"value":5561680392},{"value":8589934595},{"value":18446744065119617024},{"value":8589934595},{"value":3},{"value":3},{"value":5561647104},{"value":4294934015},{"value":12553993828},{"value":6812465848,"symbolLocation":0,"symbol":"nanov2_try_free_default"},{"value":0},{"value":5561680384},{"value":2},{"value":0},{"value":27},{"value":4370500528},{"value":17293822569102709406},{"value":7051239972},{"value":11},{"value":55834574852},{"value":1}],"flavor":"ARM_THREAD_STATE64","lr":{"value":7046132248},"cpsr":{"value":1610616832},"fp":{"value":6100675760},"sp":{"value":6100675632},"esr":{"value":4060086273,"description":"(Breakpoint) brk 1"},"pc":{"value":7046132248,"matchesCrashFrame":1},"far":{"value":105553175035904}},"queue":"com.apple.main-thread","frames":[{"imageOffset":225816,"symbol":"_assertionFailure(_:_:file:line:flags:)","symbolLocation":316,"imageIndex":0},{"imageOffset":225816,"symbol":"_assertionFailure(_:_:file:line:flags:)","symbolLocation":316,"imageIndex":0},{"imageOffset":695232,"symbol":"swift_unexpectedError","symbolLocation":652,"imageIndex":0},{"imageOffset":206052,"imageIndex":1},{"imageOffset":51420,"imageIndex":1},{"imageOffset":481752,"symbol":"-[NSSet makeObjectsPerformSelector:]","symbolLocation":176,"imageIndex":2},{"imageOffset":113256,"symbol":"-[NSIBObjectData nibInstantiateWithOwner:options:topLevelObjects:]","symbolLocation":828,"imageIndex":3},{"imageOffset":71128,"symbol":"loadNib","symbolLocation":340,"imageIndex":3},{"imageOffset":68616,"symbol":"+[NSBundle(NSNibLoading) _loadNibFile:nameTable:options:withZone:ownerBundle:]","symbolLocation":560,"imageIndex":3},{"imageOffset":67852,"symbol":"-[NSBundle(NSNibLoading) loadNibNamed:owner:topLevelObjects:]","symbolLocation":180,"imageIndex":3},{"imageOffset":67376,"symbol":"+[NSBundle(NSNibLoading) loadNibNamed:owner:]","symbolLocation":300,"imageIndex":3},{"imageOffset":16080,"symbol":"NSApplicationMain","symbolLocation":488,"imageIndex":3},{"imageOffset":8688,"imageIndex":1},{"imageOffset":24144,"symbol":"start","symbolLocation":2544,"imageIndex":4}]},{"id":56115,"frames":[{"imageOffset":7704,"symbol":"start_wqthread","symbolLocation":0,"imageIndex":5}]},{"id":56116,"frames":[{"imageOffset":7704,"symbol":"start_wqthread","symbolLocation":0,"imageIndex":5}]},{"id":56117,"frames":[{"imageOffset":7704,"symbol":"start_wqthread","symbolLocation":0,"imageIndex":5}]}],
  "usedImages" : [
  {
    "source" : "P",
    "arch" : "arm64e",
    "base" :<PHONE_NUMBER>,
    "size" : 5562368,
    "uuid" : "18b6c203-512a-36e9-9c56-1eca60868332",
    "path" : "\/usr\/lib\/swift\/libswiftCore.dylib",
    "name" : "libswiftCore.dylib"
  },
  {
    "source" : "P",
    "arch" : "arm64",
    "base" :<PHONE_NUMBER>,
    "CFBundleShortVersionString" : "1.2.12",
    "CFBundleIdentifier" : "com.clipy-app.Clipy",
    "size" : 5013504,
    "uuid" : "5902f877-2b7a-310a-acd5-95a4783ef03b",
    "path" : "\/Volumes\/VOLUME\/*\/Clipy.app\/Contents\/MacOS\/Clipy",
    "name" : "Clipy",
    "CFBundleVersion" : "1.2.12"
  },
  {
    "source" : "P",
    "arch" : "arm64e",
    "base" :<PHONE_NUMBER>,
    "CFBundleShortVersionString" : "6.9",
    "CFBundleIdentifier" : "com.apple.CoreFoundation",
    "size" : 5079040,
    "uuid" : "f4ff83fc-e62c-30b4-b3a9-876c8a1fd595",
    "path" : "\/System\/Library\/Frameworks\/CoreFoundation.framework\/Versions\/A\/CoreFoundation",
    "name" : "CoreFoundation",
    "CFBundleVersion" : "1953.1"
  },
  {
    "source" : "P",
    "arch" : "arm64e",
    "base" :<PHONE_NUMBER>,
    "CFBundleShortVersionString" : "6.9",
    "CFBundleIdentifier" : "com.apple.AppKit",
    "size" : 15761408,
    "uuid" : "af9f6891-70ad-3c26-af08-b747344892d2",
    "path" : "\/System\/Library\/Frameworks\/AppKit.framework\/Versions\/C\/AppKit",
    "name" : "AppKit",
    "CFBundleVersion" : "2299"
  },
  {
    "source" : "P",
    "arch" : "arm64e",
    "base" :<PHONE_NUMBER>,
    "size" : 566464,
    "uuid" : "de46dd52-4994-3fd8-b4b4-e352a1a19354",
    "path" : "\/usr\/lib\/dyld",
    "name" : "dyld"
  },
  {
    "source" : "P",
    "arch" : "arm64e",
    "base" :<PHONE_NUMBER>,
    "size" : 53244,
    "uuid" : "886caca0-5762-3640-8db2-3fa3b911c062",
    "path" : "\/usr\/lib\/system\/libsystem_pthread.dylib",
    "name" : "libsystem_pthread.dylib"
  }
],
  "vmSummary" : "ReadOnly portion of Libraries: Total=1.1G resident=0K(0%) swapped_out_or_unallocated=1.1G(100%)\nWritable regions: Total=698.3M written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=698.3M(100%)\n\n                                VIRTUAL   REGION \nREGION TYPE                        SIZE    COUNT (non-coalesced) \n===========                     =======  ======= \nActivity Tracing                   256K        1 \nColorSync                          448K       22 \nCoreGraphics                        16K        1 \nCoreServices                       192K        1 \nKernel Alloc Once                   32K        1 \nMALLOC                           184.3M       28 \nMALLOC guard page                  192K       11 \nMALLOC_MEDIUM (reserved)         120.0M        1         reserved VM address space (unallocated)\nMALLOC_NANO (reserved)           384.0M        1         reserved VM address space (unallocated)\nSTACK GUARD                       56.1M        4 \nStack                             9808K        4 \nVM_ALLOCATE                         32K        2 \n__AUTH                             980K      231 \n__AUTH_CONST                      17.6M      423 \n__CTF                               756        1 \n__DATA                            6634K      411 \n__DATA_CONST                      19.5M      428 \n__DATA_DIRTY                      1246K      146 \n__FONT_DATA                        2352        1 \n__LINKEDIT                       763.2M        4 \n__OBJC_CONST                      2380K      195 \n__OBJC_RO                         65.1M        1 \n__OBJC_RW                         1981K        1 \n__TEXT                           400.6M      449 \ndyld private memory                256K        1 \nmapped file                      153.0M       12 \nshared memory                      848K       13 \n===========                     =======  ======= \nTOTAL                              2.1G     2394 \nTOTAL, minus reserved VM space     1.6G     2394 \n",
  "legacyInfo" : {
  "threadTriggered" : {
    "queue" : "com.apple.main-thread"
  }
},
  "trialInfo" : {
  "rollouts" : [
    {
      "rolloutId" : "5ffde50ce2aacd000d47a95f",
      "factorPackIds" : {

      },
      "deploymentId" : 240000215
    },
    {
      "rolloutId" : "61fd92db295c182621ececc3",
      "factorPackIds" : {
        "SIRI_DIALOG_ASSETS" : "6357deb4892de80b72cc9b97"
      },
      "deploymentId" : 240000215
    }
  ],
  "experiments" : [

  ]
},
  "reportNotes" : [
  "dyld_process_snapshot_create_for_process failed with 5"
]
}

Did you take the time to try the version of Clipy which I have working (noted above) from Ian Hu and which is still working fine for me on 12.6.1 (no Ventura going anywhere my M1 MacBook Pro for another year or two).
Or perhaps you took the time to try Maccy?
Or @arossert did you just start by posting a huge error report on a different version of Clipy in the wrong project to clutter up what was a very useful thread and vandalise Github?

@AlecKinnear You probably did not read my post if you ask these questions, I did try this fork and this is the error that I'm getting since I did not get an answer on that fork repo I tried here.
I looked at Maccy as mentioned in this thread but I do love the simplicity of Clipy and the ability to use snippets.
I hoped to get some direction on how to get Ian Hu fork to work but I see that you got very offended by my post so I will remove the error so you can be in peace.
Thanks for trying to help.

Seems like the last release was at 2018 so I will not get my hopes high ☺

I have switched to ClipTools in the App Store

@Econa77 hi, any update? :)

ClipTools in the App Store

Looks promising. And it's free. I'm still enjoying Ian Hu's M1 Clipy on Monterey 12.6.3 so I won't switch, but for anyone having issues with M1 Clipy, definitely worth a look.

IDK how but version 1.2.1 works
https://clipy-app.com/
MacBook Pro M1 Pro
Ventura 13.2.1

I have switched to Maccy, which works well for me.


Haichen/google sign in

Overview

Finished all onboarding screens.
Features

Sign in using a Google account, and an email check ensures that the user is a Cornell student
Fill in basic info, e.g. year, major, hometown, in the demographics page
Select interests and clubs
Filter through clubs using the search bar
Caching: the app automatically saves user progress as the user progresses from one screen to another throughout onboarding

Changes Made

Models

ClubOrInterest: stores a club/interest with its corresponding subtext (description)
InternalStorage: implements logic for writing and reading from disk. Used for caching.
UserProfile: stores the user's profile, including name, email, class, major, etc.

Activities

SignInActivity: for Google Sign-in (first screen).
CreateProfileActivity: for the demographics page of profile creation (second screen).
ClubInterestActivity: for selecting interests (third screen) and clubs (fourth screen).

Adapters

ClubInterestAdapter: used for the ListView in CreateProfileActivity

Others
Added drawables, new layouts, and values (colors, strings, styles).
Test Coverage

Tested on the emulator. Sign-in works, user can go through the onboarding screens successfully, and user's responses on the previous page are still there when the back button is pressed.
Screenshots

Onboarding

Fixed the issues from PR review and finished implementing all functionalities. The onboarding also resembles the design much more closely now (see the demo below).


fields variable is conflicting with other plugins probably vue validation module

[Vue warn]: The computed property "fields" is already defined as a prop.

following also having the same issue...

Hello guys, this issue is solved using the export-fields prop. Please read the "documentation" in the read me file for more details.

export-fields (exportFields)
Object
this prop is used to fix the problem with other components that use  the variable fields, like vee-validate. exportFields works exactly like  fields

Still shows the warning even after using export-fields


difference with https://github.com/kubernauts/jmeter-kubernetes?

This is not a issue but I don't know where else to ask.

@LeiYangGH different approach. I use the helmchart, currently no plan to implement operator and special support for openshift custom things. In next few week I would plan to bump version of tools and add a few other feature.
Basically I created this repo because I could not find jmeter helm package.

thanks. i'm just a QA of some cloud products and looking for some existing framework of jmeter in k8s. i looked both of the 2 repos but still not know which to choose yet(^_^)
please feel free to close this issue.


isEmptyRender Not Working for Children

Describe the bug
It seems like isEmptyRender fails when a component renders children, even if the children themselves are empty.
To Reproduce
This is a simplified test case that illustrates the problem:
class RenderChildren extends React.Component {
  render() {
    return this.props.children;
  }
}

class RenderNull extends React.Component {
  render() {
    return null;
  }
}

it("is an empty render", () => {
  let component = mount(
    <RenderChildren>
      <RenderNull />
    </RenderChildren>
  );

  expect(component.html()).toEqual(null);
  expect(component.isEmptyRender()).toEqual(true);
});

In this example, the first matcher passes but the second does not.
Expected behavior
If the component's HTML is null, then the component should be considered an empty render.
Screenshots

Desktop (please complete the following information):

OS: macOS 10.13.6
Browser N/A
Version 3.7.0

This is because component in this case is RenderChildren - which is not an empty render. You might want component.hostNodes().isEmptyRender()?

@ljharb Thanks for the quick reply. 🙂
I think I understand what you're saying, but it's not what I would expect from this function. My expectation when calling isEmptyRender is that it would work recursively. If the component ultimately ends up not rendering anything (by recursively evaluating to null, false or [], then I would expect isEmptyRender to return true. Is it possible to change the current behavior?

ah, true - in this case, .hostNodes() would return an empty wrapper because you don't have any.
isEmptyRender isn't currently designed to work recursively - although for mount, perhaps that makes sense.

Working on this for Mount only per @ljharb suggestion.
A few things I noticed, current implementation of isEmptyRender is only checking for null.
https://reactjs.org/docs/jsx-in-depth.html#booleans-null-and-undefined-are-ignored are the valid supported children.
Should we address supporting whats in the documentation in this tickets for isEmptyRender? or should we make another ticket for supporting those?  In addition, which of the following should we be supporting if not all of them.
Looks like the ones from the documentation that should make isEmptyRender return true:

fasle
null
undefined?
<></> (Fragments)
""

isEmptyRender should return false?

{ null }

{ undefined }

{ false }

"not an empty string"

Did I miss any or did I misunderstand any of the test cases?
Thanks

note, empty fragments, but not fragments containing non-empty things.

I think your analysis makes sense.

Thanks guys!


Remove HTTP namespace

This patch is against dev-2.0.0 and builds on #70, removing the classes and interfaces from the Zend\Stratigility\Http namespace deprecated by that patch.
Internally, this only affects MiddlewarePipe on this branch, as that class was decorating the incoming request and response at invocation; however, no other code was utilizing their features.
This patch targets the 2.0.0 release.

Marking as a WIP until #70 is merged to develop.

With #70 merged, ready for review; pinging @zendframework/community-review-team , @michaelmoussa , and @xtreamwayz.

I was wondering, the WhoopsErrorHandler checks for the Zend\Stratigility\Http\Request and grabs the original request from it. But I guess if you push it first in the pipeline it already has access to the original request, before any other middleware can mess with it.

Correct, and once we have a 1.3 version of Stratigility released, I'll update that handler to use the originalRequest attribute instead.

👍  LGTM too.

I really like all the changes. It makes understanding and customizing error handling a lot easier.

With this in place, I've updated the branch-aliases across all branches to:

dev-master => 1.2.x-dev
dev-develop => 1.3.0-dev
dev-dev-2.0.0 => 2.0.0-dev

As such, you should be able to test against the upcoming 1.3 or 2.0 versions using appropriate constraints (e.g., ^1.3.0@dev, ^2.0.0@dev).


TP-620: ADR for including preference code table.

It will be easiest to explain by reading the ADR.

Codecov Report

Merging #194 (a23e8ab) into master (ddf469d) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #194   +/-   ##
=======================================
  Coverage   61.58%   61.58%
=======================================
  Files         176      176
  Lines       10572    10572
  Branches      790      790
=======================================
  Hits         6511     6511
  Misses       3881     3881
  Partials      180      180

Continue to review full report at Codecov.

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


Rework README to showcase Gateway API

Is there an existing issue for this?

[X] I have searched the existing issues

Problem Statement
The repo readme only references Ingress and has zero mention of Gateway API.
Proposed Solution
Expose Gateway API as the upcoming recommendation for working with KIC.
Add a note that this is beta (and will likely become GA very soon)
Additional information
No response
Acceptance Criteria

[ ] The README puts Gateway API in front of the users' eyes

What is the event for Gateway API to become GA? If we have a GH issue for it, it would be beneficial to add updating README (removing mentioning about beta) to its acceptance criteria


Cocoa licensing and copyright

Just wondering, what is Apple's stance on web projects recreating the look and feel of Cocoa widgets?
I was thinking about starting a similar project using Custom Elements and Shadow DOM. However, I was unable to get any information from Apple regarding the restrictions that apply to third-party implementations of their widgets.
It's highly unlikely they would ever allow apps with Cocoa UI to be distributed on non-Apple platforms (including Web), but Electron looks like a grey area to me.

I guess you wanted to ask this in the Electron issue tracker, not Photon.

Electron is not recreating Cocoa widgets, it just provides a JS API to interact with the native implementation (menubar, dock, tabs, window).

I see many UI libraries for Electron which recreate this style and are still actively developed.


Initial version 1.0.0-pre.1

koa-esm-transform v1.0.0-pre.1
Middleware for Koa servers that transforms standard JavaScript modules to earlier versions of JavaScript and/or AMD modules (inlining loader script @polymer/esm-amd-loader into the HTML), for use with older browsers.
Consider an HTML file containing the following inline JavaScript module:
<script type="module">
import {someFunction} from './some-module.js';
someFunction();
</script>

The koa-esm-to-amd middleware would transform that HTML code to something like the following:
<script>
// An inline loader script from `@polymer/esm-amd-loader` package
// which adds the `define` function used below.
</script>
<script>
define(["./some-module.js"], function (_someModule) {
  "use strict";
  (0, _someModule.someFunction)();
});
</script>

Because this is middleware, you can use it in a simple static file server as well with a proxy server.  This makes it possible to use in front of a test server such as the one karma starts up. (See koa-karma-proxy for examples.)
Note: HTML and JavaScript are parsed on every request for those content-types, it is intended for use in development context to facilitate build-free testing/iteration as opposed to in a high volume production web server.
How it works
By default, a set of babel transform plugins are chosen based on the known capabilities of the browser/user-agent identified in the Koa Context for the request.
When downstream server returns HTML content, it is scanned for module script tags (e.g. <script type="module">).  Any src attribute values are appended with the __esmTransform queryparameter.
Inline module script content and URLs with the __esmTransform queryparameter have their import specifiers appended with the __esmTransform to indicate the requested content should be treated as a module and compiled with the selected babel plugins.
Depending on plugins being used, certain support scripts will also be inlined into the HTML, such as @polymer/esm-amd-loader and regenerator-runtime.
Options

babelPlugins: Either an Array of babel plugins (e.g. [require('@babel/plugin-transform-modules-amd')]) or a Function that takes a Koa Context and returns an Array of babel plugins (ctx) => [].  Providing a value for this option will override the default behavior of the middleware's capabilities-based babel plugin selection.
exclude: An array of requested paths or minimatch based patterns to match requested paths that should be excluded from any process/rewriting by the middleware.
queryParam: You can redefine the appended queryparameter string from __esmTransform as something else.
logger: Middleware will call debug, info, warn and error methods on console to log events.  If you use a different logger for your application, provide it here.
-logLevel: Set a minimum level for events to be logged to override the default level of info.

@aomarks Thanks for the great feedback.  I resolved all the trivial stuff and left open 4 items just to make sure you saw my responses.  I don't think there's further action required on them but I thought I'd leave for you to resolve if you a were satisfied.

Thanks, @aomarks


Some delay in UI refresh after depositing coins.

Bullet 4 no screen but can be seen in “Your assets” on “Wallet” page. After you deposit coins, this is not updated immediately but if you go to the “Transactions” page, you can see that coins have already arrived in the Ghostx Wallet. Can poll frequency for refresh be made more often perhaps?


Duplicated entries in catalog

I think within the catalog, there might be duplicated entries, how can I extract table with such issue?
only one table can be loaded at once (tables found: other_transport_injuries__both_sexes__70plus_years, transport_injuries__both_sexes__70plus_years)

Hey @similang. catalog.find returns a DataFrame where each row is a table. If you get back more than one rows, just select the one that you're interested in and call .load() on it.
For instance
from owid import catalog
# cat is a dataframe with two rows
cat = catalog.find(table='transport_injuries__both_sexes__70plus_years', dataset='gbd_cause')
# we select only the row matching `transport_injuries__both_sexes__70plus_years`
# calling `load` loads the actual data
t = cat[cat.table == 'transport_injuries__both_sexes__70plus_years'].load()
t.head()


Move add_target and references to core collector

Depends on:

[x] https://github.com/ManageIQ/manageiq/pull/21596

@agrare its look fine by me. do you want me to merge, or you prefer someone else will take a look?
note you may get conflicts with https://github.com/ManageIQ/manageiq-providers-autosde/pull/115 so manually merging may be required

@llivne yes you're correct, whichever one of these gets merged first I'll just rebase and force-push the other


Add pipeline for getting cloud.gov Pages operators GPG credentials into credhub

In order to enable commit_verification_keys on Pages concourse pipelines, we first need a way to gather cloud.gov Pages operators credentials and add them to credhub.
Re: #1765
Security considerations
Will require use of credhub admin credentials in another pipeline to automatically set a variable

Pipeline here: https://ci.fr.cloud.gov/teams/pages/pipelines/gpg-keys/
Source: https://github.com/cloud-gov/pages-gpg-keys


Benchmarks: Add Feature - Add GPU-Burn as microbenchmark

Description
Modifications adding GPU-Burn to SuperBench.

added third party submodule
modified Makefile to make gpu-burn binary
added/modified microbenchmarks to add gpu-burn python scripts
modified default and azure_ndv4 configs to add gpu-burn

@rafsalas19 Thanks a lot for the PR! Overall it looks good to me. I have some general comments:

Please help provide a unit-test (which should be both CUDA/ROCm test) that checks the output parsing logic. test_gpu_copy_bw_performance.py can be a reference.
Please help add an example usage file for gpu-burn microbenchmark. gpu_copy_bw_performance.py can be a reference.
Please help add description for new metrics in micro-benchmarks.md.


Broken on submodules since .git is not a directory

Happens with https://github.com/mvdan/git-picked, which does git.PlainOpen(".") and reads some info about the branches. This software works fine when the clone isn't a submodule.
But when it is...
 $ git-picked
open .git/objects/pack: not a directory

More info:
 $ ls -la .git
-rw-r--r-- 1 mvdan mvdan 34 Mar 27 16:58 .git
 $ cat .git
gitdir: ../.git/modules/webclient

@mvdan Thanks for reporting this. We're looking into it.

Work in progress: https://github.com/src-d/go-git/pull/363

Thank you both!


[question]  Zwave driver not inited, no port configured

I have been trying to get zwavejs2mqtt running in a docker container but it doesn't work.
My command is:
docker run --rm -it -p 8091:8091 -p 3000:3000 --device=/dev/serial/by-id/usb-0658_0200-if00:/dev/zwave -v $(pwd)/store:/usr/src/app/store zwavejs/zwavejs2mqtt:latest

which is from the getting started documentation but I get:
2022-06-18 22:27:51.761 WARN ZWAVE: Zwave driver not inited, no port configured

and my device doesn't show up on the webpage. I'm not sure what to do I already had this controller working with ozwdaemon so I am pretty sure everything works, and I am missing something in the setup of zwavejs2mqtt

You haven't configured the minimum required settings as mentioned in the Quick Start guide: https://zwave-js.github.io/zwavejs2mqtt/#/getting-started/quick-start?id=minimum-settings
See step 1, "Configure the serial port". Based on your docker command, the serial port needs to be configured as /dev/zwave. Even if it shows that when you go to the page, you still need to input it and save it.

Thank you that was my problem. It is not very obvious that you need to save the settings from the Quick Start Guide. To me saying "the template Docker Compose file maps the Z-Wave stick to /dev/zwave" made me assume that it would already be configured for /dev/zwave especially because this is pre-populated in the settings to make it seem like it is pre-configured.


RuntimeError importing Gevent

Grequest raise this exception "Gevent is required for grequests." when i use it with virtualenv(python 2.7.10 on linux ubuntu 14.04 LTS).

You must install gevent in order to use this library.


Gradle wrapper recipes should allow wrappers to come from places other than services.gradle.org

Currently the gradle wrapper update recipes operate under the assumption that all gradle distributions will come from serivces.gradle.org. Some organizations instead host gradle distributions within their internal artifact repository. Self-hosted gradle distributions may or may not be customized in some way.

Isn't this a duplicate of https://github.com/openrewrite/rewrite/issues/2651 ?

It is! Thanks tim


chore(package): update to Jest 24 and use Babel

WIP

make babelrc shared
ship updated imports as a separate PR

Warnings

:warning:
There are no updates provided to CHANGELOG. Ensure there are no publicly visible changes introduced by this PR.

  Generated by :no_entry_sign: dangerJS


Request interceptor containing an async call

Hi, Is it possible to perform asynchronous calls in a "request" interceptor? I have an interceptor that gets the access token from the localforage library but all methods are asynchronous. If so could you provide a code example please? Thanks

You might have realized this already but it already works this way:
this.unregisterFetch = fetchIntercept.register({
  request: async (url, config = {}) => {
    const fetchOptions = {
      ...config,
    };

    try {
      const token = await this.Authenticator.getIdToken();

      if (!fetchOptions.headers) {
        fetchOptions.headers = new Headers();
      }
      fetchOptions.headers.append('Authorization', `Bearer ${token}`);
    } catch (error) {
      // Should we re-login or inspect error here?
    }

    return [url, fetchOptions];
  },
});

If you're using something like adal/angular-adal note that my getIdToken is just a wrapper around their ridiculous synchronous/callback call that promisifies it.

You might have realized this already but it already works this way:
this.unregisterFetch = fetchIntercept.register({
  request: async (url, config = {}) => {
    const fetchOptions = {
      ...config,
    };

    try {
      const token = await this.Authenticator.getIdToken();

      if (!fetchOptions.headers) {
        fetchOptions.headers = new Headers();
      }
      fetchOptions.headers.append('Authorization', `Bearer ${token}`);
    } catch (error) {
      // Should we re-login or inspect error here?
    }

    return [url, fetchOptions];
  },
});

If you're using something like adal/angular-adal note that my getIdToken is just a wrapper around their ridiculous synchronous/callback call that promisifies it.

This way does not take effect

Hi, Is it possible to perform asynchronous calls in a "request" interceptor? I have an interceptor that gets the access token from the localforage library but all methods are asynchronous. If so could you provide a code example please? Thanks

I have the same issue


set topic message type name through struct tag

Describe the feature
set topic message type name through struct tag
Description
Thank you for providing such a user-friendly Go ROS communication library
I have a requirement in my project to use the reflect package to dynamically generate messages. The struct generated using reflect does not have a name, and the name of this struct will be used when obtaining the message name in msgproc.Type(). If the name is empty, it defaults to Msg. Therefore, when publishing a message, the ros message type name has changed to xxx/Msg. Can you modify the msgproc.Type function to pass the name in through the struct tag?
Thank you very match!

Hello, i've checked the code and i can confirm that the feature is missing.
It was never developed because the message name doesn't influence the checksum, it's just shown to clients.
Message names can now be set by using the msg.Name field:
type MessageName struct {
    msg.Package `ros:"my_package"`
    msg.Name `ros:"my_message_name"`
    Field1 bool
    Field2 int32
}


Fix for security risk of mutable list arguments in helpers.py.

The work for the code change was done in conjunction with three other students at the University of Nebraska at Omaha for a Master's level software assurance class project.  I scanned the Wagtail code using Pylint using swamp.org to identify security weaknesses.  The scan identified an issue with functions in helpers.py.  The issue found is if an list argument of a function is set to [] as the default, the previous call to the function could assign a value to the argument.  The next call to the function will use the assigned value as the default instead of [].  Setting the default of the lists arguments to None fixes the weakness.   See the "Important warning" in python's documentation for more information and an example.  The pull request sets the list defaults to None.
After the code change no additional tests failed and the issue for [] was removed in a Pylint scan.

Thanks @shoefler! Merged in 7994d19f6514019a392a40219251631e57ef6446.
(In this case, I don't think the bug would ever be triggered here, since the lists never get mutated within the lifetime of those methods, only used to build new lists... We definitely want to follow best practice, though.)


Odd cache behaviour

I'm was trying out s3fs with the new h5py with pretty large files (100gb and 1tb). Trying to access the root group keys, it look a long time. I monkey patched some functions with loggers to see what was getting accessed, and it seems with default_fill_cache=True, large parts of the file are being read.
Logging the function/methods calls with its arguments, I get:
>>>> h5f.keys()
seek (136,) {}
read (544,) {}
_fetch (136, 680) {}
seek (1072,) {}
read (328,) {}
_fetch (1072, 1400) {}
_fetch_range (<botocore.client.S3 object at 0x11399f160>, 'xxx', 'yyy.hdf5', None, 1032, 2424) {'req_kw': {}}
seek<PHONE_NUMBER>0,) {}
read (328,) {}
_fetch<PHONE_NUMBER>0,<PHONE_NUMBER>8) {}
_fetch_range (<botocore.client.S3 object at 0x11399f160>, 'xxx', 'yyy.hdf5', None, 2424,<PHONE_NUMBER>2) {'req_kw': {}}

As you can see the last request seems kind of odd: bytes 2424 to<PHONE_NUMBER>2 are fetched.
FYI: default_block_size=1024

Amazing work btw!

I guess here, the cache should only be "filled" in the case that the gap between the current location and the requested location is less than a block?
btw, fsspec contains a memory-map cache which would be very interesting in this kind of situation, and should work with s3fs (there is an stale branch on here for fsspec compatibility). If you have an interest, it would be very nice to pull it in and see how well it works for your situation.

Yes, I don't really follow the logic of the caching here, but that seems to be the issue indeed.
That is exactly what I want actually. I'm doing this for vaex actually, and I want in the end the file to be completely cached on an SSD. I was thinking of doing this at the DataFrame level, but doing it on file/byte level is much easier and portable. Using this I don't have to wait till the file is completely transferred, and most columns aren't used very often anyway.
Very interesting work.


[CORE] Minor code refactor for handling native write

How was this patch tested?
Existed Tests

@binmahone, @WolverineJiang, could you please take a review? This is simply some trivial code refactor. Thanks!


question; how to fix import Global.Unsafe (unsafeDecodeURI, unsafeEncodeURI)

[1/9 ModuleNotFound] .spago/halogen-storybook/master/src/Halogen/Storybook.purs:19:1

  19  import Global.Unsafe (unsafeDecodeURI, unsafeEncodeURI)
      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

  Module Global.Unsafe was not found.
  Make sure the source file exists, and that it has been provided as an input to the compiler.

I cannot find these methods

If it's possible to use decodeURIComponent and encodeURIComponent, then you can get the unsafe version by calling unsafePartial fromJust on the result of decoding or encoding.
If halogen-storybook does require just encodeURI and decodeURI, then we can add those bindings to this library as well and I'd accept a PR for that. It would largely follow the pattern used for the existing definitions of encodeURIComponent and decodeURIComponent.

ok, tnx https://github.com/rnons/purescript-halogen-storybook/pull/5/commits/55f76c95c72e22b05a32e21b51e2da3833a792de
no need to add for now

actually they are needed
usecase https://github.com/bodil/purescript-smolder/blob/5548710e5467cf7b08d7def62c8fcf5ebfb6d9ae/src/Text/Smolder/Renderer/String.purs#L144


Automatically fetch the newest versions

As mentioned here, the list of firmwares is static. It would be nice to create a Github Action that checks for new versions and then commits the new links. This way the "secret" authorization token could be stored as a secret in Github but users could get the newest versions.

Done :-)


Cannot connect to the management URL when multiple nodes are added

Reproduce steps:

Set up harvester from ISO(IP: <IP_ADDRESS>)
Add a compute node(IP: <IP_ADDRESS>)
Check dashboard

The dashboard shows that the management URL is https://<IP_ADDRESS>:8443, while the external IP of the lb svc is <IP_ADDRESS>
$ kubectl get svc -n harvester-system
harvester                     LoadBalancer   <IP_ADDRESS>     <IP_ADDRESS>   8443:30892/TCP   20m

close in favor of https://github.com/rancher/harvester-installer/pull/7 and the management URL is designed to use the first management node.


Mac OSX .app can not start second time.

Finally i managed to get my astilectron app running on a Mac.
I do not use go-astilectron-bootstrap as discussed and mentioned here: https://github.com/asticode/go-astilectron-bundler/issues/82
Now i have the following issue and i think this is something related to caching issues. But i'm not 100% sure.
I'm creating a bundle and move the generated Mac OS .app File to my /Applications/ Directory.
When i'm starting the App the first time everything works fine. resources and vendor directories are restored under
 /Applications/MyApp.app/Contents/MacOS
Now i'm closing my application and want to restart it. The app icon blinks a second in the Dock and then disappears. Nothing more happens. When i go into the  /Applications/MyApp.app/Contents/MacOS directory and run the application binary via Terminal by hand i get from the logs the following interesting part:
Astilectron has already been provisioned to version 0.41.0, moving on...
Electron has already been provisioned to version 7.1.10, moving on...
Listening...
Executing...
Starting cmd /Applications/MyApp.app/Contents/MacOS/vendor/electron-darwin-amd64/My App.app/Contents/MacOS/My App /Applications/MyApp.app/Contents/MacOS/vendor/astilectron/main.js <IP_ADDRESS>:59333 false
Closing...
astikit: stopping worker...
accept tcp <IP_ADDRESS>:59333: use of closed network connection while TCP accepting
Stopping...

The interesting part here is that the Name of my App is Wrong. In the path the name is My App with a space. But actually my app name is MyApp without a space.
The correct command should be:
Starting cmd /Applications/MyApp.app/Contents/MacOS/vendor/electron-darwin-amd64/MyApp.app/Contents/MacOS/MyApp /Applications/MyApp.app/Contents/MacOS/vendor/astilectron/main.js <IP_ADDRESS>:59333 false

Or am i wrong?
As i said i think it is related to cache issues because the app name My App with a space was the previous name i changed  to MyApp without a space. I already tried to clear the cache but this did not help.
Is it possible that somewhere the old electron / astilectron files are provisioned with my old App Name which i have to delete first?

My only guess is that your binary didn't get updated and your app name is still My App in it. It should be easy to check : just log the app name you're providing astilectron in your GO binary and see whether there's a space in it.

@asticode Nevermind. It was totally my fault. My issue was that i implemented before in my app (when the app had the "old" name with the space) an update functionality where the app downloads and replaces the binary with a potential update from a server.
To my disadvantage the update which still is on that server for testing purpose was compiled with the old app name (the space). Now it makes sense that the issue only appears on the second start..
I am sorry to bother you with sometimes very dumb issues which are my fault...but sometimes you just need someone you can tell your problems to ..


Athentication feature

Login auth with rallly

This is one step for build the first version, currently this doesn't need reviewer.


setRequestHeader

Hi thanks for your share,
I think it will be nice to be able to .setRequestHeader from options{requestHeaders:{ key1 : value1, key2 : value2 }...}
I will test it and maybe do my first PR :).

I agree, really need this functionality to authenticate against web services that require an API key etc. Any progress on this functionality?

see #33, note this is only necessary across domains, as if you are on the same domain those headers automatically get set.  Also note that it is only for ajax requests that it gets set as you can't set headers for jsonp requests

Any possibility for more progress on #33?
I need this to be able to content-negotiate on an API producing json or geojson by specifying 'accept' with value either 'application/json' or 'application/geo+json'

ac197b0d5d228543fbda6d47daa26f9bc2ef2d4d

Can you confirm my syntax is proper, because I do not see the headers server-side. So I want to know I'm doing it right before i dig any deeper.
var ajaxLayer = new L.GeoJSON.AJAX(
    layerEndpoint,{
        headers: {
            lon: currCenter.lng,
            lat: currCenter.lat,
            units: "mi",
            distance: 20,
        }
});

I've tried headers = {} and just the {} with my position info and I always see the data on the ajaxLayer object when I console log it, but while I do see a request on my server, I do not see the headers server side.
I have tested my server works properly by using JQuery $.getJSON() so i know if headers are present in the request I can see them in my server.
It's worth mentioning, I tried the code from  PR #50 and it did not work either. So my next assumption is that we have a bug or i'm doing it wrong.
Thanks!

PR #50 does fix this.

This is not entirely clear to me, the docu says:

If you want to set headers to the XMLHttpRequest set the 'headers' option equal to an object.

I thought this should work:
var geojsonLayer = L.geoJson.ajax("route/to/esri.json",{
    	dataType: 'json',
        headers: { 'X-Api-Key': 'jPmTlUOJHtr0JYR8yrsy8HgOn7Rs17Y413Fzxzp8' },
});

but probably I'm missing something


⚠ Bofrost.lu has degraded performance

In 350f5b1, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 895 ms

Resolved: Bofrost.lu performance has improved in ace4d26 after 9 minutes.


BUG: Vue: add missing .vue extension to component imports

Scope

[ ] This impacts ALL Mitosis outputs
[X] This only impacts specific generators/outputs (please list them here): Vue

Describe the bug
When outputting 2 components to Vue, where one uses the other, the import is missing the .vue extension and does not work.
To Reproduce
Problem is visible in this example, on the selected file, on line 25.
https://stackblitz.com/edit/node-3nrn7m?file=output%2Fvue%2Fnuxt2%2Fsrc%2Fcomponents%2Fmy-component.vue
This is a StackBlitz, not a fiddle, because it needs 2 components to illustrate the problem.
The incorrect line of output is:
import ItemList from "./item-list";

Expected behavior
import ItemList from "./item-list.vue";

@kylecordes Thanks for filing.
How are you generating these components? mitosis build, mitosis compile, or directly importing generator fns from @builder.io/mitosis?

It looks like compile expects command line arguments, while build looks at the config file

Not quite. Added a PR to outline the diffs between the two CLI commands a little better https://github.com/BuilderIO/mitosis/pull/467/files
But yes, using build is the right thing in this case, and I see in our own Vue SDKs that the .vue extension is not there. However, our Mitosis-generated Vue SDK work fine. I think it might be an env-based thing (Webpack vs esbuild vs vite vs nuxt...etc)
And reading online, it seems like importing without .vue was accepted but some recent changes in the Vue world are getting rid of it? https://github.com/vuejs/vue-cli/issues/5549#issuecomment-638850440

I guess it's best to include the explicit .vue extension to avoid problems though.
We have 2 functions that replace a .lite extension in an import statement:
Once when a Mitosis component's code is generated
https://github.com/BuilderIO/mitosis/blob/a2a8a53ed100abc7a944110c59b2d622dd30016e/packages/core/src/helpers/render-imports.ts#L31-L42
Once in a general transpilation step in mitosis build that renames imports across the folder (including mitosis & non-mitosis files).
https://github.com/BuilderIO/mitosis/blob/a2a8a53ed100abc7a944110c59b2d622dd30016e/packages/cli/src/build/helpers/extensions.ts#L1-L17
My understanding of using both of these 2 together is that we'd end up with the .vue extension, but that doesn't seem to be the case. Should be as easy as adding a switch case to the function in render-imports.ts though

Great to see the doc improvement!
In terms of code gen, I think the "just works" path is to generate files that will work with whatever the most common downstream tools are. Not sure if I picked right, using Vite+Vue for the E2E; maybe that is pickier than Vue's own CLI. Of course it would be best to work with both.
Ideally the result is a "pit of success" -> no matter what you throw at Mitosis, you get back either an explanatory error, or output which compiles and runs on all targets. Obviously a lot of work to get there!

Yeah 100%. Made the .vue extension always there now.


warning--filled--layered.svg with stylable [!]

Closes #
adds a warning--filled--layered.svg with stylable [!] so the BG fill and [!] can be independantly styled via css.
Changelog
New
16/warning--filled--layered.svg
20/warning--filled--layered.svg
24/warning--filled--layered.svg
32/warning--filled--layered.svg

@joshblack please confirm the two elements are independently stylable via CSS.
cc @shixiedesign @aagonzales

@chrisconnors-ibm is this a separate issue then what got added here: https://github.com/IBM/carbon-elements/pull/374 ?

This is a different design, and not one we currently offer. If we want to add a new icon, we should remove the old one that's very similar:

build is ignoring the white [!] shape layer:

@chrisconnors-ibm we can target the ! path to flip it to white 👍 By default it's black so it looks filled in

it will be hard to troubleshoot if we render it unstyled as just a single mass of black.

@chrisconnors-ibm agreed, that's why I was asking about that fill-rule thing or other CSS things to help fix this. Is there anyone with some expertise here that we could bug to see if we can do anything?

I think its supposed to be black because the icons will be changed to yellow and the ! will need to be black for accessibility.

we shouldn't be throwing away the white fill on the [!] when the icon colors are not being overridden via css styling.

This is a different design, and not one we currently offer. If we want to add a new icon, we should remove the old one that's very similar:

it's meant to replace 16/warning--filled.svg but until @joshblack can confirm/demonstrate that we can independently style the circle bg color and the [!] color.
When it's unstyled, as in the ESM demo site of in our icon library, they should remain circle bc color black and [!] color white
The other difference between this and #374 is that it includes all 4 sizes, and the [!] is based on Plex Sans (as it was in @conradennis' original)

I have a new set of guidance/assets from @conradennis that I'll up this afternoon.

Yup, we can style it. Although the default will still be the filled in black unless we find a way to avoid that 🤔


Why is this project named seata?

I am curious about the name of this project.
Looking forward to reply

@sanwancoder You can get it in README.md

Seata: Simple Extensible Autonomous Transaction Architecture

I will close this issue,if you have further question about this issue,please comment here.thank you!


[DOCS] Fix java code errors in quick_start_with_jdbc

Why are the changes needed?

There were obvious errors in the case code, so these cases were fixed.
How was this patch tested?
Just fix case code, no test need. Of course, I have run the case code and have confirmed that there is no problem.

Codecov Report

Merging #5347 (ec6ecf7) into master (57b6773) will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master   #5347   +/-   ##
======================================
  Coverage    0.00%   0.00%
======================================
  Files         590     590
  Lines       33493   33493
  Branches     4424    4424
======================================
  Misses      33493   33493

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

thanks, merging to branch-1.7(v1.7.4)/branch-1.8(v1.8.0)/master(v1.9.0).


ARGO-1052 Add logging mechanism for comparison script

logging ready
error handling ready

Looks very good! @agelostsal


Label PRs with PR size

Many OSS projects use bots to label PRs with labels like small, large, or XS, S, L, XL etc so that project maintainers know the size of the PRs when looking at the list of PRs in the PRs page and then they can choose to review small and big PRs depending on how much time they have to review PRs at the time based on PR size and priority (area of PR etc)

I'd be ok with this although I am generally cautious of adding too many labels and our labeling workflow growing too much. But we could easily automate this with a bot that fires on PR

Makes sense 👍 I'm not sure how we currently review PRs and if this makes sense and helps as part of the PR review process of folks. If this does not enable or fit into our existing PR review process, I think we can close it

Let's definitely revisit this if we find there's a need for the metadata (could be in the future when the project grows)


Upgrade to authjs v5

Additional context
https://authjs.dev/guides/upgrade-to-v5

I would advise against upgrading to v5 yet, as it's still experimental.


feat(buy): add buy button and page

So we wait to merge this PR until Simplex is ready? Or did I miss the feature flag for late activation?

So we wait to merge this PR until Simplex is ready? Or did I miss the feature flag for late activation?

I will set the flag once it will be reviewed and approved

Tested, LGTM except for some visual bugs on Buy AE Tokens page #1298


Ramda Curry makes VsCode Intellisense stop working

I reported this issue last week Link. Now I'm curious, I have two ways to write the code but one of them makes VsCode intellisense stop working when I export it by index.js
Directories:

function.js
index.js

// index.js
export * from './function'

This way to write the function makes VsCode insellisense stop working
// First way
// function.js

const remove =(schema, params) => {
 const getFilterFormat = R.cond([
   [_.isPlainObject, getRealmFilter],
   [R.T, R.F],
 ]);

 const removeRegisters = R.useWith(fwRemove, [
   R.identity,
   getSchemaName,
   getFilterFormat,
 ]);

 return removeRegisters(Realm, schema, params);
};

const curriedRemove = R.curry(remove )

export { curriedRemove };

But this way to write the function makes no problem. (But this way I can't export remove function without currying )
// Second way
// function.js

const curriedRemove = R.curry((schema, params) => {
 const getFilterFormat = R.cond([
   [_.isPlainObject, getRealmFilter],
   [R.T, R.F],
 ]);

 const removeRegisters = R.useWith(fwRemove, [
   R.identity,
   getSchemaName,
   getFilterFormat,
 ]);

 return removeRegisters(Realm, schema, params);
});

export { curriedRemove };

The second one doesn't let me to export the function without currying and that's my problem. There is something that I'm missing?

Because I can't replicate the problem, I can't offer much help.  Have you reported this to the VS Code team?  As far as I can tell, the Ramda functions are working the way they should.  But I have no idea how VS Code derives the metadata it uses for its "Intellisense" feature.
It may be that this is a long-standing problem, because I'm pretty sure most Ramda users would automatically use the latter format.  Remember that there is (perhaps too much) magic in Ramda's curry implementation so that wrapping curry around your function does not prevent you from using it as you would have without the curry.  It simply offers additional ways to call it.
That is, given this:
const curriedRemove = curry ((schema, params) => { /* ... */ })

We can call this in several ways, all yielding the same result:
const result = curriedRemove (mySchema, myParams);  //or
const result = curriedRemove (mySchema) (myParams); // or
const result = curriedRemove (__, myParams) (mySchema)

@CrossEye I understand, I think I'm going that way, trying to solve this exercise is making my head hurt lol.
But, would you advice me about some good practices? Should I exports a function as a curried function (export curriedFn) or should I let the user Curry the function (just exporting fn) ? And otherwise, It's good practice to name a function curried as a curried or just name it as ? Thanks a lot.

Okay, I found the issue. The problem isn't the export or the index.js it was the importation from the index.js
Ex:

main.js
index.js
function.js

I was importing remove like this:
// main.js

import * as Functions from './index'
...

But if I import it like this everything works fine.
// main.js

 import {remove} from './index'
...

So that's all.

Ok. Now I have the the specific problem (I hope).
I'm working with react Native so I have a functional component like this:
import {remove} from './somewhere'

const Login = () => {

   onPressSubmit = (a) => {
      const logInUser = R.pipe(
         ...
        R.tap(remove('myUser') ),
        ...
        )

    return R.tryCatch(logInUser, showModalError)( a )
  }

   return ( ... )
}

If I change that to this. Now everything works okay (so far):
import {remove} from './somewhere'

const Login = () => {

   onPressSubmit = (a) => {
       const removeUser = remove('MyUser')      // => new function

      const logInUser = R.pipe(
         ...
        R.tap(removeUser),              // => using new function
        ...
        )

    return R.tryCatch(logInUser, showModalError)( a )
  }

   return ( ... )
}

I hope it comes in handy for someone who has a similar problem.

Should I exports a function as a curried function (export curriedFn) or should I let the user Curry the function (just exporting fn) ?

While obviously it's up to you and your user, I personally like to have Ramda-style curried functions available.  They are more flexible to use.  Do note that there is some performance cost to this flexibility.  It's usually not huge, but it exists due to the extra function invocations required.  But I find it worth it.  In fact I and a host of others have built an entire library on this premise... :wink:

And otherwise, It's good practice to name a curried function as a curriedFn or just name it as fn? Thanks a lot.

Currying is a minor feature of your function.  The API and behavior are far more important.  Calling attention to the fact that it's curried just seems a distraction.  Document the various ways it can be called, or simply mention the currying in the documentation; that should be plenty.

@CrossEye That's make me sense. Thanks!


fix redhat-version for fedora and rhel for check-mem.sh

add regexp to be able to match fedora (> 20)or rhel (> 7.0), without
this patch, if not possible to use this plugins on rhel

@nhicher I will merge this but at some point soon this check will be depreciated for a pure Ruby check that will be platform independent.

Ok, no problem.
Thanks.
Nico
On 06/08/2015 02:23 PM, Matt Jones wrote:

@nhicher I will merge this but at some point soon this check will be depreciated for a pure Ruby check that will be platform independent.

Reply to this email directly or view it on GitHub:
https://github.com/sensu/sensu-community-plugins/pull/1196#issuecomment-110097836


include stopped containers

It may be interesting to see stopped containers.
For example, my use case was to expose volumes mount points to nginx, that contains the results of a dockerized script.

:+1:
I agree, this would be a really useful feature.  Our use case is generating vhost definitions for stopped containers that point to an internal web service that will start those containers back up again when visited.
I'm sure this is already known, but a change in the returned structs will require an update to the "Templating" section of the documentation and the addition of the include-stopped switch will require an update to the "Usage" section.
I wasn't sure whether or not this was done as part of PRs on this project, or as a pre-release task.

Can you rebase?

Yes, rebase is done.

Thanks @minhdoboi!


Expense Details - Header of conversation does not display [Amount] for [Merchant

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 9.0.42-1
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/5023024
Email or phone of affected tester (no customers<EMAIL_ADDRESS>Issue reported by: Applause Internal Team
Action Performed:

Go to https://staging.new.expensify.com/
Create a new workspace.
Navigate to the workspace chat.
Submit an expense, add a merchant, and complete the flow.
Click on the expense preview.

Expected Result:
The header should display the format "[Amount] for [Merchant]."
Actual Result:
The header only shows a generic report title, such as "Expense Report #4367516057538636," without displaying the amount or merchant.
Workaround:
Unknown
Platforms:

[ ] Android: Native
[x] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
https://github.com/user-attachments/assets/d174b1cb-7a0a-4cf2-9c39-096e8d0890e9

View all open jobs on GitHub

Proposal
Please re-state the problem that we are trying to solve in this issue.
Header of conversation does not display [Amount] for [Merchant]
What is the root cause of that problem?
When we create a new workspace, the title field is always enabled then the report.reportName is returned here.
https://github.com/Expensify/App/blob/7dde09e01e77ba55a79d043847b7ff86c5c1d1fd/src/libs/ReportUtils.ts#L2898-L2900
What changes do you think we should make in order to solve the problem?
We should add the check not to return report.reportName if the report field feature is not enabled
if (titleReportField && report?.reportName && isPaidGroupPolicyExpenseReport(report) && policy?.areReportFieldsEnabled) {
   return report.reportName;
}

https://github.com/Expensify/App/blob/7dde09e01e77ba55a79d043847b7ff86c5c1d1fd/src/libs/ReportUtils.ts#L2898-L2900
We can check for other places that we use the report field data and it has the same problem.
OPTIONAL: We can create a util to check the report field is enabled or not then we can use this in other places.
What alternative solutions did you explore? (Optional)

Proposal
Please re-state the problem that we are trying to solve in this issue.
The conversation header does not display the correct [Amount] for [Merchant].
What is the root cause of that problem?
The problem occurs because when a new workspace is created, the title field is always enabled, causing report.reportName to be returned. This happens regardless of whether report fields are enabled or not.
In the following code (Lines 2898 to 2900) from ReportUtils.ts:
if (titleReportField && report?.reportName && isPaidGroupPolicyExpenseReport(report)) {
    return report.reportName;
}

This results in the report name being returned, even when the report fields feature is disabled.
What changes do you think we should make in order to solve the problem?
To fix this, we should update the condition to ensure report.reportName is not returned if the report fields feature is disabled.
Here’s the revised condition:
if (titleReportField && report?.reportName && isPaidGroupPolicyExpenseReport(report) && policy?.areReportFieldsEnabled) {
    return report.reportName;
}

This change ensures that report.reportName is only returned when both the titleReportField is enabled and the policy.areReportFieldsEnabled condition is met.
Additional Considerations

Moving this back to daily and evaluating today. The PR above was incorrectly opened. So we still need to triage this, and then review proposals (if we decide to fix it).

Discussing

Thinking might be related to the above issue. Discussing there.

We decided this is a dupe of the above. Closing!


Can not set inBackground option in View

My Environment

ArangoDB Version:       3.7.3
Storage Engine:             RocksDB
Deployment Mode:      Single Server
Deployment Strategy:   Manual Start
Configuration:
Infrastructure:               own
Operating System:       18.04
Total RAM in your machine:       16Gb
Disks in use:        HDD
Used Package:              Debian or Ubuntu .deb

Component, Query & Data
Affected feature:
Update ArangoDB View using web interface.
Dataset:
View based on one collection with 790M documents.
Example:
{
    "_key": "10674927",
    "_id": "z_users/10674927",
    "_rev": "_XGBeK----_",
    "email": "***",
    "username": "***",
    "firstname": "***",
    "lastname": "***",
    "date_created":<PHONE_NUMBER>979,
    "date_updated":<PHONE_NUMBER>979,
    "roles": [
      "ROLE_MUSER"
    ],
    "enabled": true,
    "unsubscribed": false,
    "password": "***",
    "salt": "***",
    "computed": {
      "displayed_name": "***"
    }
}

Steps to reproduce

Create the view using web interface.
Update the view using web interface and add inBackground: true:

{
  "writebufferIdle": 64,
  "type": "arangosearch",
  "writebufferSizeMax": 33554432,
  "consolidationPolicy": {
    "type": "tier",
    "segmentsBytesFloor": 2097152,
    "segmentsBytesMax":<PHONE_NUMBER>,
    "segmentsMax": 10,
    "segmentsMin": 1,
    "minScore": 0
  },
  "primarySort": [],
  "globallyUniqueId": "hC9B524A1A5B3/13368217362",
  "id": "13368217362",
  "storedValues": [],
  "writebufferActive": 0,
  "consolidationIntervalMsec": 10000,
  "cleanupIntervalStep": 2,
  "commitIntervalMsec": 1000,
  "links": {
    "z_users": {
      "analyzers": [
        "text_en"
      ],
      "fields": {
        "username": {},
        "firstname": {}
      },
      "includeAllFields": true,
      "storeValues": "none",
      "trackListPositions": false,
      "inBackground": true
    }
  },
  "primarySortCompression": "lz4"
}

The document is updated but the option is not set.
SEARCH operations work, but there is a lock while indexing.

Problem:
I can't set the inBackground: true option.
Expected result:
Set inBackground option to true.

Edit: the inBackground is not kept in the document while reopening it:
"links": {
    "z_users": {
      "analyzers": [
        "text_en"
      ],
      "fields": {
        "username": {},
        "firstname": {}
      },
      "includeAllFields": true,
      "storeValues": "none",
      "trackListPositions": false
    }

Edit: the inBackground is not kept in the document while reopening it:
"links": {
    "z_users": {
      "analyzers": [
        "text_en"
      ],
      "fields": {
        "username": {},
        "firstname": {}
      },
      "includeAllFields": true,
      "storeValues": "none",
      "trackListPositions": false
    }

It is expected that the option "vanishes". It is a one-off option that is not persisted in the View definition. This this also the case with regular collection indexes.
Indexing should take place in background if you set inBackground: true when you add the link "z_users". First adding the link, then updating the View with inBackground: true might be ignored. Any change to a link should re-build the internal index, as it is immutable. But since inBackground is not a View property, it might not count as a change.

It is expected that the option "vanishes". It is a one-off option that is not persisted in the View definition. This this also the case with regular collection indexes.
Indexing should take place in background if you set inBackground: true when you add the link "z_users". First adding the link, then updating the View with inBackground: true might be ignored. Any change to a link should re-build the internal index, as it is immutable. But since inBackground is not a View property, it might not count as a change.

Hello,
If I want to be able to use inBackground option, do I have to add it when I add the link?
Are these steps correct?

Create the view
Edit the view and add the link on z_users collection with inBackground: true
Save the view

Hello,
If I want to be able to use inBackground option, do I have to add it when I add the link?
Are these steps correct?

Create the view
Edit the view and add the link on z_users collection with inBackground: true
Save the view

Sorry for the delay, yes setting the inBackground attribute when adding a link should do the trick.

Hi @AntoineAA,
does the latest suggestion work?

Hi,
Sorry for the delay.
It works, thank you!


website keep freezing.

when i turned on the eink viewable extension. some websites (for example reddit) keep freezing when i scroll.
when remove the eink style the issue disappear

.
the issue started around 1 or 2 weeks before.
it happens on the latest chrome mac os version.

Is there a way to reproduce this issue? I used it with Reddit on macOS Chrome (ARM version) but couldn't replicate the problem.


Instance: USP Course: Davi Mendes Fialho

Cloud Computing Instance Flavor
g3.xl - GPU instance (32 CPUs, 125 GB RAM and A100 GPU)
Description
This study relied on cyberinstructure supported by grants from National Science Foundation (MorphoCloud: DBI/2301405; JetStream2: OAC/2005506; Exosphere: TI/2229642) and National Institutes of Health (MorphoCloud: NICHD HD104435)
ORCID
0000-0002-0483-8797
Email
U2FsdGVkX1/N4+RO44p/izuItHIik1vSwiGXiFoSgK4kHoBdctkCrXO3MNDRKynE
Confirm Email
U2FsdGVkX1/N4+RO44p/izuItHIik1vSwiGXiFoSgK4kHoBdctkCrXO3MNDRKynE
Instance Name
instance-136
The instance name is derived from the GitHub issue number using the template instance-NNN. The instance may also be located in the exosphere interface using this name.
Volume Name
My-Data-136
The volume name is derived from the GitHub issue number using the template My-Data-NNN. The volume may also be located in the exosphere interface using this name.

/create

/unshelve

/unshelve

/unshelve

/unshelve


Extension crashes on startup

Godot version
4.1.1
Plugin version
1.0.2
System information
Ubuntu 22.04
Issue description
After adding the extension to my project, attempting to start the project, or closing and re-opening the editor, results in a crash with the following report:
================================================================
handle_crash: Program crashed with signal 11
Engine version: Godot Engine v4.1.1.stable.mono.official (bd6af8e0ea69167dd0627f3bd54f9105bda0f8b5)
Dumping the backtrace. Please include this when reporting the bug to the project developer.
[1] /lib/x86_64-linux-gnu/libc.so.6(+0x42520) [0x7f3acc880520] (??:0)
[2] std::__codecvt_utf8_utf16_base<char16_t>::do_unshift(__mbstate_t&, char*, char*, char*&) const (??:0)
[3] std::ostream& std::ostream::_M_insert<long>(long) (??:0)
[4] /usr/lib/dotnet/host/fxr/7.0.11/libhostfxr.so(+0x3a684) [0x7f3a982c9684] (??:0)
[5] /usr/lib/dotnet/host/fxr/7.0.11/libhostfxr.so(+0x26937) [0x7f3a982b5937] (??:0)
[6] /usr/lib/dotnet/host/fxr/7.0.11/libhostfxr.so(+0x28111) [0x7f3a982b7111] (??:0)
[7] /usr/lib/dotnet/host/fxr/7.0.11/libhostfxr.so(+0x221ab) [0x7f3a982b11ab] (??:0)
[8] /usr/lib/dotnet/host/fxr/7.0.11/libhostfxr.so(hostfxr_initialize_for_runtime_config+0xcf) [0x7f3a982accdf] (??:0)
[9] /home/erik/devel/godot/Godot_v4.1.1-stable_mono_linux_x86_64/Godot_v4.1.1-stable_mono_linux.x86_64() [0x15f75d1] (??:0)
[10] /home/erik/devel/godot/Godot_v4.1.1-stable_mono_linux_x86_64/Godot_v4.1.1-stable_mono_linux.x86_64() [0x1648396] (??:0)
[11] /home/erik/devel/godot/Godot_v4.1.1-stable_mono_linux_x86_64/Godot_v4.1.1-stable_mono_linux.x86_64() [0xf5b261] (??:0)
[12] /home/erik/devel/godot/Godot_v4.1.1-stable_mono_linux_x86_64/Godot_v4.1.1-stable_mono_linux.x86_64() [0xe598ed] (??:0)
[13] /lib/x86_64-linux-gnu/libc.so.6(+0x29d90) [0x7f3acc867d90] (??:0)
[14] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x80) [0x7f3acc867e40] (??:0)
[15] /home/erik/devel/godot/Godot_v4.1.1-stable_mono_linux_x86_64/Godot_v4.1.1-stable_mono_linux.x86_64() [0xe86e5e] (??:0)
-- END OF BACKTRACE --
================================================================

I tried doing the exact same thing on my Windows machine and I can run the project with no problems. I also tried building the extension from source and I got the exact same issue. I'm new to a lot of this, including Godot and WebRTC so I'm not sure where the issue lies.
Steps to reproduce
Unzip the extension .zip and place the webrtc folder in the root folder of the project, and attempt to run the project.
Minimal reproduction project
No response

I have the same issue! :sob:
Endevour OS (Arch)

I tried removing and re-installing dotnet, as well as installing the webrtc extension in an empty project and I have the same issue.

Just ran into the same issue on 6.5.5-1-MANJARO (Manjaro Linux).
Plugin Name: WebRTC for Godot 4.1+
Plugin Version: 1.0.3
(...)
.NET: Initializing module...
Found hostfxr: /usr/share/dotnet/host/fxr/7.0.11/libhostfxr.so

================================================================
handle_crash: Program crashed with signal 11
Engine version: Godot Engine v4.1.3.stable.mono.official (f06b6836a9ecfd0e6ec96d8bcf0fe9c9bc10dcbf)
Dumping the backtrace. Please include this when reporting the bug to the project developer.
[1] /usr/lib/libc.so.6(+0x3e710) [0x7f4d2ebf7710] (??:0)
[2] std::__codecvt_utf8_utf16_base<char16_t>::do_unshift(__mbstate_t&, char*, char*, char*&) const (??:0)
[3] std::ostream& std::ostream::_M_insert<long>(long) (??:0)
[4] /usr/share/dotnet/host/fxr/7.0.11/libhostfxr.so(+0x29883) [0x7f4cf8d6e883] (??:0)
[5] /usr/share/dotnet/host/fxr/7.0.11/libhostfxr.so(+0x1622e) [0x7f4cf8d5b22e] (??:0)
[6] /usr/share/dotnet/host/fxr/7.0.11/libhostfxr.so(+0x17c52) [0x7f4cf8d5cc52] (??:0)
[7] /usr/share/dotnet/host/fxr/7.0.11/libhostfxr.so(+0x11a0a) [0x7f4cf8d56a0a] (??:0)
[8] /usr/share/dotnet/host/fxr/7.0.11/libhostfxr.so(hostfxr_initialize_for_runtime_config+0xd1) [0x7f4cf8d521c1] (??:0)
[9] /opt/godot-mono-bin/godot/Godot_v4.1.3-stable_mono_linux.x86_64() [0x15fa4c1] (??:0)
[10] /opt/godot-mono-bin/godot/Godot_v4.1.3-stable_mono_linux.x86_64() [0x164af46] (??:0)
[11] /opt/godot-mono-bin/godot/Godot_v4.1.3-stable_mono_linux.x86_64() [0xf5c7a9] (??:0)
[12] /opt/godot-mono-bin/godot/Godot_v4.1.3-stable_mono_linux.x86_64() [0xe5aec5] (??:0)
[13] /usr/lib/libc.so.6(+0x27cd0) [0x7f4d2ebe0cd0] (??:0)
[14] /usr/lib/libc.so.6(__libc_start_main+0x8a) [0x7f4d2ebe0d8a] (??:0)
[15] /opt/godot-mono-bin/godot/Godot_v4.1.3-stable_mono_linux.x86_64() [0xe8843e] (??:0)
-- END OF BACKTRACE --
================================================================

This only happens with WebRTC for me.
Other GDExtensions seem to be fine.
Reinstalling dotnet-sdk doesn't help, nor does installing it via the Microsoft providen script like recommended by Godot.
DotNet-SDK 6.0 and 7.0 have the issue.
Any godot-mono version in AUR has this issue for me (godot-mono, godot-mono-bin, godot-mono-git).
The issue only occurs in -mono versions of Godot. The normal Godot version runs just fine.
Deleting the .godot folder inside the project directory temporary solves the issue. Godot-Mono opens and stuff can be done. However, the next time I open the project the issue is present again.
Removing the WebRTC library (and removing .godot) makes the crash disappear.
Even an empty project with WebRTC installed will crash on godot-mono, while godot opens it fine without and issues.
Dotnet:
> dotnet --info
.NET SDK:
 Version:   7.0.111
 Commit:    06c8b346e4

Runtime Environment:
 OS Name:     manjaro
 OS Version:
 OS Platform: Linux
 RID:         manjaro-x64
 Base Path:   /usr/share/dotnet/sdk/7.0.111/

Host:
  Version:      7.0.11
  Architecture: x64
  Commit:       ecb34f85ec

.NET SDKs installed:
  6.0.122 [/usr/share/dotnet/sdk]
  7.0.111 [/usr/share/dotnet/sdk]

.NET runtimes installed:
  Microsoft.NETCore.App 6.0.22 [/usr/share/dotnet/shared/Microsoft.NETCore.App]
  Microsoft.NETCore.App 7.0.11 [/usr/share/dotnet/shared/Microsoft.NETCore.App]

Other architectures found:
  None

Environment variables:
  DOTNET_ROOT       [/usr/share/dotnet]

global.json file:
  Not found

Learn more:
  https://aka.ms/dotnet/info

Download .NET:
  https://aka.ms/dotnet/download

Godot
> godot-mono --version
4.1.3.stable.mono.official.f06b6836a

Likely related to #116 , possibly fixed by https://github.com/godotengine/godot/pull/84947 , can anyone confirm?

Closing, as there have been no reply, and this is likely fixed by https://github.com/godotengine/godot/pull/84947

Could have also possibly been related to #127 actually, in any  case, please comment in case the issue is still relevant and I'll re-open it.


Use other metric than impact factor for data paper journals

As an organization valuing open science, please don't use impact factor as the (only) metric for data paper journals on http://demo.gbif.org/generic/publishing/data-papers.

Impact factors are a flawed metric (see this recent article) and by providing only that one, potential data paper writers are influenced in choosing a journal based on the wrong criteria. Rather, indicate which journals are full open access journals and maybe also their APC costs. I'm happy to provide that information.

Duly noted. I have no problem leaving out the impact factor altogether. We have APC costs and OA information already, so we can include this in the table instead.

Great!

How about something like this?

(estimate for easy comparison, based on 5000 words/15 pages)

Nice, some questions/suggestions

Open access = open access journal or does this also include hybrid journals?
Would express APC estimates in same currency + indicate that currency + use thousands separator.
I would drop impact factor altogether 😄

Thanks for your comments, Peter.

"Open Access" currently includes hybrid journals - I guess I could categorize them "pure OA", "hybrid OA" or "not OA"?
agreed
will consider :)

For OA, I would use the terms:

Yes
Hybrid
No

For those that are yes, you could link the word yes to the DOAJ journal page, e.g. for Phytokeys: https://doaj.org/toc/1314-2003/12
You could also opt to not include hybrid/no, but it including them gives an better overview of where not to publish.

Thanks Peter!

Turns out I was mistaken about the "hybrid" journals. In my list, "hybrid" indicates a journal that's not "pure data". So AFAIK "yes" means pure OA.
I was able to pull DOAJ links for most of them, except for these:
BioRisk (Pensoft)
Biota Colombiana (Alexander von Humboldt Biological Resources Research Institute, Colombia)
Check List (Biotaxa)
China Scientific Data (Chinese Acadademy of Sciencies)
Data (MDPI Open Access Journals)
@peterdesmet, are you familiar with DOAJ and why I might not be able to find these journals?

Here's my latest version of the table

Ideally, it will be sortable by clicking the column headers.

Nice. I wouldn't add decimals to the price + would use - for N/A impact factor. I'll have a look at the journals you mention, but the publisher of the journal has to submit their journal to DOAJ, so DOAJ might not be aware of all.
Can you post the whole table?

Didn't find those journals on DOAJ either. Have already notified Pensoft for BioRisk: https://twitter.com/peterdesmet/status/792029585596682240

Also, typo in Chinese Acadademy of Sciencies -> Chinese Academy of Sciences

Thanks @peterdesmet. I'll work these thing in and post a complete table later. I actually tweeted DOAJ, and Check List has now been added.

Here's the whole table with corrections. I've also hyperlinked the APC estimatse so that the source of that information is easily accessible:

Great! I assume - for APC means no costs?

Yeah, I actually changed it $0 for consistency. Agreed?

Yeah, seems fine + links are helpful. Guess this issue can be closed. Nice overview!

Thanks for your thoughts and comments! Very helpful :)


Skeleton

train.py for
a) overfit on several images of Pascal VOC
b) train on Pascal VOC train

Examples:
overfit
python train.py --overfit
a) default filename to save model
b) fixed lr_schedule with Adam, lr =0 .01, lr=0.001

train:
python train.py
Train on PascalVoc train

Purpose: overfit to loss < 1.0

At what condition should we finish the loop over the epochs when the --overfit parameter wasn't passed?


[NBS 1.0] Rename service config to options type

Hey, I just made a Pull Request!
Closes: https://github.com/backstage/backstage/issues/24923
Rename all *Service*Config types to *Service*Options types in order to standardize frontend and backend create* function signatures:

Rename ServiceRefConfig to ServiceRefOptions
Rename RootServiceFactoryConfig to RootServiceFactoryOptions
Rename PluginServiceFactoryConfig to PluginServiceFactoryOptions

:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

Currently on hold while waiting for service module feature: https://github.com/backstage/backstage/issues/24547


SciPy trunk compiled for Python3.9 does not work

(venv_********_3_9) [2020-02-21 12:09:02 ~ $] python
Python 3.9.0a3+ (heads/master-dirty:f2ee21d858, Feb 19 2020, 23:19:22)
[GCC 9.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import scipy
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/marco/Desktop/********/venv_********_3_9/lib/python3.9/site-packages/scipy/__init__.py", line 156, in <module>
    from . import fft
  File "/home/marco/Desktop/********/venv_********_3_9/lib/python3.9/site-packages/scipy/fft/__init__.py", line 76, in <module>
    from ._basic import (
  File "/home/marco/Desktop/********/venv_********_3_9/lib/python3.9/site-packages/scipy/fft/_basic.py", line 1, in <module>
    from scipy._lib.uarray import generate_multimethod, Dispatchable
  File "/home/marco/Desktop/********/venv_********_3_9/lib/python3.9/site-packages/scipy/_lib/uarray.py", line 28, in <module>
    from ._uarray import *
  File "/home/marco/Desktop/********/venv_********_3_9/lib/python3.9/site-packages/scipy/_lib/_uarray/__init__.py", line 115, in <module>
    from ._backend import *
  File "/home/marco/Desktop/********/venv_********_3_9/lib/python3.9/site-packages/scipy/_lib/_uarray/_backend.py", line 4, in <module>
    from . import _uarray  # type: ignore
ImportError: /home/marco/Desktop/********/venv_********_3_9/lib/python3.9/site-packages/scipy/_lib/_uarray/_uarray.cpython-39-x86_64-linux-gnu.so: undefined symbol: _ZTISt9bad_alloc

It looks like you aren't linking in the C++ runtime. How are you compiling SciPy and are you able to compile for other python versions in the same way?

Yes, with Python 3.8 I can pip install scipy without problems

Also we are not supporting nonrelease versions of python.

Python 3.9 works fine now, closing.


SOCIALFB-45: Support paging with since and until in API binding

Signed-off-by: Jose Alberto Hdez<EMAIL_ADDRESS>

@jahernandez Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.


For transparency, add section to wiki about how data is cleaned

Describe process of data standardization including how columns are identified and how their data is standardized (i.e. which raw values are assigned which final standardized values). This is necessary for release of code that allows for data cleaning

@sowdm what are your thoughts on the following? The plan is to add a section on the wiki homepage about the reasoning for our data is cleaning process described in
https://github.com/openpolicedata/opd-data/blob/main/CONTRIBUTING.MD#adding-a-dataset-to-openpolicedata. This will be written for an audience who want to know the why instead of the how and does not assume the audience is a developer.

After discussion we decided to close this issue and possibly create a new issue later to add this documentation to the website.


Fix GL error by properly using float uniform

Fixes: https://github.com/godotengine/godot/issues/33787
In my previous fix I thought I was already using floats in the shader. Turns out I wasn't...
For some off reason I am not getting any error output, not even when running verbose. It could be because NVidia drivers just don't care, or it could be the same reason why I no longer get backtraces.

Thanks!