Battery App opens in full setting on every restart and needs to be closed. Options to not open it do not work. Colour selection for full charge does not remain selected.

This is duplicated with issue #4 which has been resolved. Closing this one.
Please try uninstalling and reinstalling the latest version from Microsoft Store to resolve this issue.

Thanks will try but I have done this already a few days ago without anly luck.
Regards,
Leslie Klein, Ph.D., P.Enghttp://P.Eng.
President and CEO
C-COM Satellite Systems Inc.
2574 Sheffield Road
Ottawa, Canada, K1B 3V7
Direct Line:613-986-4110
email<EMAIL_ADDRESS>web site: www.c-comsat.comhttp://www.c-comsat.com
Trading Symbol: CMI on
TSX Venture (Canada) and
CYSNF on OTCQB (USA)

From: Long Zhou @.>
Sent: Wednesday, December 18, 2024 9:33:30 PM
To: soleon/Percentage @.>
Cc: Leslie Klein @.>; Author @.>
Subject: Re: [soleon/Percentage] Battery App opens in full setting on every restart and needs to be closed. Options to not open it do not work. Colour selection for full charge does not remain selected. (Issue #19)
You don't often get email from @.*** Learn why this is importanthttps://aka.ms/LearnAboutSenderIdentification
This is duplicated with issue #4https://github.com/soleon/Percentage/issues/4 which has been resolved. Closing this one.
Please try uninstalling and reinstalling the latest version from Microsoft Store to resolve this issue.
—
Reply to this email directly, view it on GitHubhttps://github.com/soleon/Percentage/issues/19#issuecomment-2552649035, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BN2APPZYTZMLNMMTUZVM6PD2GIV7VAVCNFSM6AAAAABT3VX7BWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJSGY2DSMBTGU.
You are receiving this because you authored the thread.Message ID: @.***>

Hi Long,
I have uninstalled and reinstalled as you suggested, but the start up process still brings up the entire setting page even though I set the option to hide. See my setting:
@.***
From: Long Zhou @.>
Sent: December 18, 2024 9:34 PM
To: soleon/Percentage @.>
Cc: Leslie Klein @.>; Author @.>
Subject: Re: [soleon/Percentage] Battery App opens in full setting on every restart and needs to be closed. Options to not open it do not work. Colour selection for full charge does not remain selected. (Issue #19)
You don't often get email from<EMAIL_ADDRESS>Learn why this is importanthttps://aka.ms/LearnAboutSenderIdentification
This is duplicated with issue #4https://github.com/soleon/Percentage/issues/4 which has been resolved. Closing this one.
Please try uninstalling and reinstalling the latest version from Microsoft Store to resolve this issue.
—
Reply to this email directly, view it on GitHubhttps://github.com/soleon/Percentage/issues/19#issuecomment-2552649035, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BN2APPZYTZMLNMMTUZVM6PD2GIV7VAVCNFSM6AAAAABT3VX7BWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJSGY2DSMBTGU.
You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>

@Velkyhores can you try deleting the following file  then reset all settings to default in the app see if this helps?
C:\Users\<user name>\AppData\Local\Percentage.App\Percentage.App_Url_<unique ID>\<IP_ADDRESS>\user.config

Hi Long,
I do not see Percentage.App in that folder..
From: Long Zhou @.>
Sent: December 19, 2024 8:27 AM
To: soleon/Percentage @.>
Cc: Leslie Klein @.>; Mention @.>
Subject: Re: [soleon/Percentage] Battery App opens in full setting on every restart and needs to be closed. Options to not open it do not work. Colour selection for full charge does not remain selected. (Issue #19)
You don't often get email from<EMAIL_ADDRESS>Learn why this is importanthttps://aka.ms/LearnAboutSenderIdentification
@Velkyhoreshttps://github.com/Velkyhores can you try deleting the following file then reset all settings to default in the app see if this helps?
C:\Users<user name>\AppData\Local\Percentage.App\Percentage.App_Url_\<IP_ADDRESS>\user.config
—
Reply to this email directly, view it on GitHubhttps://github.com/soleon/Percentage/issues/19#issuecomment-2553968093, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BN2APP7LN5XF2IQXF7SP62T2GLCSVAVCNFSM6AAAAABT3VX7BWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJTHE3DQMBZGM.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

@Velkyhores can you follow my comment in issue #22 see if it can help you solving this issue please.

Will try. Thanks for the assistance. Having problems locating the installation folder for the app on my drive.
Regards,
Leslie Klein, Ph.D., P.Enghttp://P.Eng.
President and CEO
C-COM Satellite Systems Inc.
2574 Sheffield Road
Ottawa, Canada, K1B 3V7
Direct Line:613-986-4110
email<EMAIL_ADDRESS>web site: www.c-comsat.comhttp://www.c-comsat.com
Trading Symbol: CMI on
TSX Venture (Canada) and
CYSNF on OTCQB (USA)

From: Long Zhou @.>
Sent: Thursday, December 19, 2024 9:23:52 PM
To: soleon/Percentage @.>
Cc: Leslie Klein @.>; Mention @.>
Subject: Re: [soleon/Percentage] Battery App opens in full setting on every restart and needs to be closed. Options to not open it do not work. Colour selection for full charge does not remain selected. (Issue #19)
You don't often get email from @.*** Learn why this is importanthttps://aka.ms/LearnAboutSenderIdentification
@Velkyhoreshttps://github.com/Velkyhores can you follow my commenthttps://github.com/soleon/Percentage/issues/22#issuecomment-2556131886 in issue #22https://github.com/soleon/Percentage/issues/22 see if it can help you solving this issue please.
—
Reply to this email directly, view it on GitHubhttps://github.com/soleon/Percentage/issues/19#issuecomment-2556133931, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BN2APP4U6OM6BZ6XT4FKJDD2GN5TRAVCNFSM6AAAAABT3VX7BWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJWGEZTGOJTGE.
You are receiving this because you were mentioned.Message ID: @.***>

Hi Long,
Folder does not exist in suggested location. Issue is now only with startup which I can close. Everything else is OK and colour selection remains saved.
From: Long Zhou @.>
Sent: December 19, 2024 9:24 PM
To: soleon/Percentage @.>
Cc: Leslie Klein @.>; Mention @.>
Subject: Re: [soleon/Percentage] Battery App opens in full setting on every restart and needs to be closed. Options to not open it do not work. Colour selection for full charge does not remain selected. (Issue #19)
You don't often get email from<EMAIL_ADDRESS>Learn why this is importanthttps://aka.ms/LearnAboutSenderIdentification
@Velkyhoreshttps://github.com/Velkyhores can you follow my commenthttps://github.com/soleon/Percentage/issues/22#issuecomment-2556131886 in issue #22https://github.com/soleon/Percentage/issues/22 see if it can help you solving this issue please.
—
Reply to this email directly, view it on GitHubhttps://github.com/soleon/Percentage/issues/19#issuecomment-2556133931, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BN2APP4U6OM6BZ6XT4FKJDD2GN5TRAVCNFSM6AAAAABT3VX7BWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJWGEZTGOJTGE.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

Hi Long,
The app started to work out of the blue. No issues. Nothing has changed and I was unable to make any changes. Total mistery.
Thanks for your effort.
From: Leslie Klein
Sent: December 19, 2024 8:13 AM
To: soleon/Percentage @.***>
Subject: RE: [soleon/Percentage] Battery App opens in full setting on every restart and needs to be closed. Options to not open it do not work. Colour selection for full charge does not remain selected. (Issue #19)
Hi Long,
I have uninstalled and reinstalled as you suggested, but the start up process still brings up the entire setting page even though I set the option to hide. See my setting:
@.***
From: Long Zhou<EMAIL_ADDRESS>Sent: December 18, 2024 9:34 PM
To: soleon/Percentage<EMAIL_ADDRESS>Cc: Leslie Klein<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [soleon/Percentage] Battery App opens in full setting on every restart and needs to be closed. Options to not open it do not work. Colour selection for full charge does not remain selected. (Issue #19)
You don't often get email from<EMAIL_ADDRESS>Learn why this is importanthttps://aka.ms/LearnAboutSenderIdentification
This is duplicated with issue #4https://github.com/soleon/Percentage/issues/4 which has been resolved. Closing this one.
Please try uninstalling and reinstalling the latest version from Microsoft Store to resolve this issue.
—
Reply to this email directly, view it on GitHubhttps://github.com/soleon/Percentage/issues/19#issuecomment-2552649035, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BN2APPZYTZMLNMMTUZVM6PD2GIV7VAVCNFSM6AAAAABT3VX7BWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJSGY2DSMBTGU.
You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>


Simulator vs. device performance

I'm trying to use the example application with the Xcode 9 and iOS 11 GMs here, and seeing significant performance differences between the two.
On my mid-2014 15-inch MacBook Pro, the example app absolutely flies, working perfectly, pretty much. Meanwhile, on my 6s Plus, it's dropping frames left, right, and centre. I tried messing with the usual suspects (clear memory, low power mode, etc.) but device just keeps dropping frames.
I know there's a performance difference between simulator and device, but it usually tends to be in the device's favour, especially with graphics stuff. There's also an OpenGL simulator bug in the GM, which might be at play here: https://twitter.com/xenadu02/status/911463433521860609
Any ideas for increasing on device performance? I tried but can't seem to find any way to toggle CPU-based rendering like with CIContext, for example.
Thanks

Hey @HarshilShah, thanks for pointing this out! There used to be a performance issue with generating the gradient image, but I'm not sure if it could affect the frame rate so much. Can you check if you have the same issue on a Release config?
More info here - https://github.com/maxkonovalov/MKGradientView#performance

Yup, looks like a CPU-bound issue then, as everything is drawn using CGContext. Definitely need to profile and optimize that. Don't know when I can get my hands on it though, so if you have any ideas about fixing it, any help would be appreciated!
Btw I tested the demo on a iPhone 7+ device with iOS 11 and the performance was not bad at all.

Yup, I’ve got a couple of ideas I’ll be trying. Also I do need to upgrade my phone 😅
Sent with GitHawk

Btw, here’s what it looks like on my end. Kinda surprised iOS screen recording works even when there isn’t even enough perf to render frames in time, but this is exactly what I’m seeing:
ScreenRecording_09-25-2017 15:04.MP4.zip
(Zipped because GitHub doesn't support .mp4)

Thanks for posting the video! I thought the issue was much worse actually))

It gets worse with progress, basically. More than one rotation of any ring makes it way worse

Hi @HarshilShah, I updated the lib with some optimizations - can you please check v2.0 and let me know if the performance improved for you.


Slow initialisation

Satosa takes around 7-10 minutes from loading the daemon to being able to service requests.
It doesn't seem to matter how many metadata feeds I supply or how large the files are.
Code Version/Hardware
Version: 3.4.8
OS: CentOS Linux release 7.5.1804 (Core)
HW: VMware VM, 2vCPU Intel(R) Xeon(R) CPU E5-2667 v4 @ 3.20GHz, 4 GB RAM, SAN Disks.
Custom RPM, installed/compiled with rh-python36 packages and virtualenv.
Entropy sources rngd and HAVEGEd are set up.
Expected Behavior
faster startup time
Current Behavior
journalctl output:
Jul 26 13:57:06 satosa.local scl[11016]: [2018-07-26 13:57:06 +0200] [11020] [INFO] Starting gunicorn 19.9.0
Jul 26 13:57:06 satosa.local scl[11016]: [2018-07-26 13:57:06 +0200] [11020] [INFO] Listening at: http://<IP_ADDRESS>:8080 (11020)
Jul 26 13:57:06 satosa.local scl[11016]: [2018-07-26 13:57:06 +0200] [11020] [INFO] Using worker: gevent
Jul 26 13:57:06 satosa.local scl[11016]: [2018-07-26 13:57:06 +0200] [11024] [INFO] Booting worker with pid: 11024
Jul 26 13:57:06 satosa.local scl[11016]: [2018-07-26 13:57:06 +0200] [11025] [INFO] Booting worker with pid: 11025
Jul 26 13:57:07 satosa.local scl[11016]: [2018-07-26 13:57:07] [INFO ]: Loading backend modules...
Jul 26 13:57:07 satosa.local scl[11016]: [2018-07-26 13:57:07] [INFO ]: Loading backend modules...
Jul 26 14:01:07 satosa.local scl[11016]: [2018-07-26 14:01:07] [INFO ]: Setup backends: ['saml2_backend']
Jul 26 14:01:07 satosa.local scl[11016]: [2018-07-26 14:01:07] [INFO ]: Loading frontend modules...
Jul 26 14:01:07 satosa.local scl[11016]: [2018-07-26 14:01:07] [INFO ]: Setup frontends: ['Saml2IDP']
Jul 26 14:01:07 satosa.local scl[11016]: [2018-07-26 14:01:07] [INFO ]: Loading micro services...
Jul 26 14:01:07 satosa.local scl[11016]: [2018-07-26 14:01:07] [INFO ]: Loaded request micro services: []
Jul 26 14:01:07 satosa.local scl[11016]: [2018-07-26 14:01:07] [INFO ]: Loaded response micro services: ['AddStaticAttributes']
Jul 26 14:01:08 satosa.local scl[11016]: [2018-07-26 14:01:08] [INFO ]: Setup backends: ['saml2_backend']
Jul 26 14:01:08 satosa.local scl[11016]: [2018-07-26 14:01:08] [INFO ]: Loading frontend modules...
Jul 26 14:01:08 satosa.local scl[11016]: [2018-07-26 14:01:08] [INFO ]: Setup frontends: ['Saml2IDP']
Jul 26 14:01:08 satosa.local scl[11016]: [2018-07-26 14:01:08] [INFO ]: Loading micro services...
Jul 26 14:01:08 satosa.local scl[11016]: [2018-07-26 14:01:08] [INFO ]: Loaded request micro services: []
Jul 26 14:01:08 satosa.local scl[11016]: [2018-07-26 14:01:08] [INFO ]: Loaded response micro services: ['AddStaticAttributes']
Jul 26 14:05:09 satosa.local scl[11016]: [2018-07-26 14:05:09] [DEBUG]: Loaded backends with endpoints: [<satosa.backends.saml2.SAMLBackend object at 0x7f8809e7a860>]
Jul 26 14:05:09 satosa.local scl[11016]: [2018-07-26 14:05:09] [DEBUG]: Loaded frontends with endpoints: [<satosa.frontends.saml2.SAMLFrontend object at 0x7f87f6d66d30>]
Jul 26 14:05:09 satosa.local scl[11016]: [2018-07-26 14:05:09] [DEBUG]: Loaded micro services with endpoints: [<satosa.micro_services.attribute_modifications.AddStaticAttributes object at 0x7f87f6d66b00>]
Jul 26 14:05:09 satosa.local scl[11016]: [2018-07-26 14:05:09] [DEBUG]: read request data: {'SAMLRequest': 'xxx'}

Steps to Reproduce

compile & run the software

Hello. It seems the initialization time is impacted when loading the backends. By the logs you've posted, only the SAMLBackend is loaded. This mean that initialization of the SAMLBackend is very slow. I am not sure why that happens without looking into the backend configuration. This is probably due to pysaml2 handling of the saml-backend configuration.
Related issues have been reported in #79, IdentityPython/pysaml2#472, IdentityPython/pysaml2#472 regarding the metadata parsing and generation.


A little problem about Spatital mapping prefab.

I used the MRTK package to achieve spatital mapping, but when I use this prefab,the scaning model in Hololens is not my room, it is the last room model that I scan in my lab.  I have set Room Model  None(Game object). So what's the reason leading to this problem?

@loveXMTX, what version of the toolkit are you using? Also, does your app ever set the Room Model property?

I just use the latest version package. This Unity project had been built once ,and then I change the scene content and some scripts to rebuild it, but  I uninstalled this app,then rebuild app,this trouble  still happened. Do some documents in project remember the scene property leading to this ?How could I do to solve ?

Closing issues older than 180 days. If this is still an issue, please reactivate with recent information.


New feature: Use a different source directory instead of /

My use case involves backing up user data, and not the system itself.  For example, I want to backup /pool/UserData1 and /pool/UserData2.  Since these files are not in the root directory, and I don't want extraneous characters in my tarsnap archive names, I added a new variable "$backuproot", which tarsnaps relative to that instead of /.
> git diff acts
diff --git a/acts b/acts
index da1f966..0728751 100755
--- a/acts
+++ b/acts
@@ -137,13 +137,13 @@ fi
 # PART 3: Backup
 backuprc=0 # Notice any failed backups
 for dir in $backuptargets ; do
-    log_verbose "Backing up /$dir..."
+    log_verbose "Backing up $backuproot/$dir..."
     archive_starttime=$(date +%s)
     nicedirname=$(echo "$dir" | tr -d '/')
     # Uncontrolled expansion is bad, but we have little choice. See https://github.com/koalaman/shellcheck/wiki/Sc2086
     # shellcheck disable=SC2086
-    if ! output="$($tarsnap -c -f "$hostname-$archivetype-$today-$nicedirname" -C / $tarsnapbackupoptions "$dir" 2>&1)" ; then
-        log_message "Failed to back up \"$dir\"! ($output)"
+    if ! output="$($tarsnap -c -f "$hostname-$archivetype-$today-$nicedirname" -C $backuproot $tarsnapbackupoptions "$dir" 2>&1)" ; then
+        log_message "Failed to back up \"$backuproot/$dir\"! ($output)"
         backuprc=1
     fi
     archive_endtime=$(date +%s)

I don't actually know how to use git, so I hope this diff is sufficient if you want to include this for real.  Note that acts.conf.sample should also be updated to include this variable.  I have tested this for my one use case, but I probably messed things up, so please test first. :)

Thanks for the patch. I won't include this in acts since I suspect it's a niche need, but like #6 I'm open to receiving +1s.


Inconsistent reference

This documentation page references DbgHelp Interface (https://learn.microsoft.com/en-us/windows/win32/debug/dbghelp-functions) but SymbolServerXxx functions are not documented there.
https://github.com/MicrosoftDocs/windows-driver-docs/blob/2fcdf46a86a17ba5782b2d893de60b005ea7539f/windows-driver-docs-pr/debugger/symbol-server-api.md?plain=1#L12

@mikepal2 - Thanks for this issue, this page was in need of some updates and it now no longer references those older APIs. In addition to changing the local DLL to acquire remote symbols from a server, I also added some links to other related options that are available, for example to change the server hosting using custom symbol servers. Other options on the server side, are the use of SymStore accessed via SymProxy to create custom symbol hosting. Good luck with your API work, and thanks for helping to improve the debugger API docs.


bug: Notifications (Matrix) does not follow "Rooms" declaration

Describe the bug
While testing the notification functions, a variety of issues have been identified specifically with the matrix type. I have no access to test others at this time.
When referencing the Shoutrrr instructions and Argus instructions it states that one can send messages to a specific "room". If no room is given, it will send to all rooms the user is subscribed to. I am unable to send to a scoped room and it appears to not be registering this configuration.
To Reproduce
Steps to reproduce the behavior:
Configuration:
notify:
  matrix:
    type: matrix
    url_fields:
      ...
    params:
       DisableTLS: no
       Rooms: #software-updates:example.com
       Title: Argus

service:
  org/repo:
  ...
  notify:
     matrix: {}

Expected behavior
Ability to send to scoped room
Additional context
Argus details:
2023/01/11 20:17:20 DEBUG: org/repo (url_commands), Resolved to 3.0
2023/01/11 20:17:20 INFO: org/repo, New Release - "3.0"
2023/01/11 20:17:20 DEBUG: matrix (org/repo), Sending "org/repo - 3.0 released" to "matrix://user:password@matrix.example.com:443/?disableTLS=no" with params=map["disabletls":"no" "rooms":"" "title":"Argus"]

FWIW I have also tried by using the Room ID, and Also using notify.matrix.params.rooms (lowercase) with no success.

This is from me not accounting for

Note: Don't use unescaped # for the channel aliases as that will be treated as the fragment part of the URL. Either omit them or URL encode them, I.E. rooms=%23alias:server or rooms=alias:server

I've added something to correctSelf to remove #'s in rooms as they're only allowed as the prefix and Shoutrrr handles without them


[Doc] Add reader configuration description for Java client

@yjshen could you please help review? Thank you
Should I add resetIncludeHead here?
If yes, could you please provide description for it? (I did not find the description in Pulsar project)

Fix https://github.com/apache/pulsar/issues/4509

run java8 tests
run cpp tests


JNI for Raspberry Pi

Java is currently supported on Linux, macOS and Windows. It would be great to also add JNI libraries for Raspberry Pi.

Thanks for the feedback. What would be the use case? I'm wondering what people are using Java for on RPI these days...

I am working on a home assistant for my own needs. Backend is written in Java and Spring boot framework.
Microphone, speakers and zigbee coordinator are connected to Raspberry Pi. I have couple smart devices that is sending data to RPI. In frontend application you can make request from web server, for example to show you inside temperature chart or turn on the light.
When Ikea zigbee button is pressed, RPI starts recording audio, send it to Amazon for speech recognition and then for example turn on light or tell you current temperature inside.
Instead of Ikea button press, it would be more convinient to use Picovoice hotword detection.

support has been added in #475


WIP: [x2cpg] Added server mode

Preliminary benchmark results with hello world code snippet being run 50 times:

Frontend
Server mode
Staged script (new JVM instance)

jssrc2cpg
25 sec 800 ms
72 sec 100 ms

c2cpg
1 sec 400 ms
53 sec 300 ms


libgtop: fix darwin build

Motivation for this change
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

Success on x86_64-darwin (full log)
Attempted: libgtop
Partial log (click to expand)
make[1]: Leaving directory '/private/tmp/nix-build-libgtop-2.38.0.drv-0/libgtop-2.38.0'
glibPreFixupPhase
glibPreFixupPhase
post-installation fixup
Removing /nix/store/7i1zg08352sw65ivba0c8gfyg9ia31ic-libgtop-2.38.0/share/gtk-doc
rmdir: failed to remove '/nix/store/7i1zg08352sw65ivba0c8gfyg9ia31ic-libgtop-2.38.0/share': Directory not empty
strip is /nix/store/yyak5sjv68n9vdgnkd2cb5djk1l9sqj5-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/7i1zg08352sw65ivba0c8gfyg9ia31ic-libgtop-2.38.0/lib  /nix/store/7i1zg08352sw65ivba0c8gfyg9ia31ic-libgtop-2.38.0/bin
patching script interpreter paths in /nix/store/7i1zg08352sw65ivba0c8gfyg9ia31ic-libgtop-2.38.0
/nix/store/7i1zg08352sw65ivba0c8gfyg9ia31ic-libgtop-2.38.0

Success on x86_64-linux (full log)
Attempted: libgtop
Partial log (click to expand)
glibPreFixupPhase
post-installation fixup
Removing /nix/store/kddsx0nwpzgr9kvpxnrnhk507k76fwdd-libgtop-2.38.0/share/gtk-doc
rmdir: failed to remove '/nix/store/kddsx0nwpzgr9kvpxnrnhk507k76fwdd-libgtop-2.38.0/share': Directory not empty
shrinking RPATHs of ELF executables and libraries in /nix/store/kddsx0nwpzgr9kvpxnrnhk507k76fwdd-libgtop-2.38.0
shrinking /nix/store/kddsx0nwpzgr9kvpxnrnhk507k76fwdd-libgtop-2.38.0/lib/libgtop-2.0.so.11.0.0
strip is /nix/store/21ymadblbmsbb2bk4q7gl4kjasp8zmgd-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/kddsx0nwpzgr9kvpxnrnhk507k76fwdd-libgtop-2.38.0/lib
patching script interpreter paths in /nix/store/kddsx0nwpzgr9kvpxnrnhk507k76fwdd-libgtop-2.38.0
checking for references to /build in /nix/store/kddsx0nwpzgr9kvpxnrnhk507k76fwdd-libgtop-2.38.0...

Success on aarch64-linux (full log)
Attempted: libgtop
Partial log (click to expand)
glibPreFixupPhase
post-installation fixup
Removing /nix/store/hagv8zv9fgr36vhq38y76h68dniks0gz-libgtop-2.38.0/share/gtk-doc
rmdir: failed to remove '/nix/store/hagv8zv9fgr36vhq38y76h68dniks0gz-libgtop-2.38.0/share': Directory not empty
shrinking RPATHs of ELF executables and libraries in /nix/store/hagv8zv9fgr36vhq38y76h68dniks0gz-libgtop-2.38.0
shrinking /nix/store/hagv8zv9fgr36vhq38y76h68dniks0gz-libgtop-2.38.0/lib/libgtop-2.0.so.11.0.0
strip is /nix/store/qg2agrqkf240s656d207zqhipl0bc2id-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/hagv8zv9fgr36vhq38y76h68dniks0gz-libgtop-2.38.0/lib
patching script interpreter paths in /nix/store/hagv8zv9fgr36vhq38y76h68dniks0gz-libgtop-2.38.0
checking for references to /build in /nix/store/hagv8zv9fgr36vhq38y76h68dniks0gz-libgtop-2.38.0...


No response header or body displays on 400 Bad Request

We are using swagger-play version 1.5.3 with Play 2.5.
Below are the relevant dependencies in the build.sbt:
libraryDependencies ++= Seq(
...
  "io.swagger" %% "swagger-play2" % "1.5.3",
  "org.webjars" %% "webjars-play" % "2.5.0-4",
  "org.webjars" % "swagger-ui" % "2.2.0"
)

When I curl my endpoint to get a 400 error: `curl -vvv -X POST http://localhost:9000/users/login -H "X-Logon-Id: baduser" -H 'X-Password: badpassword'
I get this response:
< HTTP/1.1 400 Bad Request
< errorCode: -66
< errorDesc: INVALID DATABASE USER
< Content-Length: 66
< Content-Type: application/json
< Date: Wed, 17 May 2017 14:49:50 GMT
<
* Connection #0 to host localhost left intact
{"returnStatus":-66,"returnStatusMessage":"INVALID DATABASE USER"}

However, when I try the same thing in the swagger ui, I see neither the response headers nor the response body.
Below is the code from the controller:
@ApiOperation(value = "User login")
  @ApiImplicitParams(Array(
    new ApiImplicitParam(name = logonHeader, dataType = "java.lang.String", required = true,
      paramType = "header", value = ""),
    new ApiImplicitParam(name = pwHeader, dataType = "java.lang.String", required = true,
      paramType = "header", value = "")))
  @ApiResponses(Array(
    new ApiResponse(code = 200, message = "Success", response = classOf[models.ApiResponse]),
    new ApiResponse(code = 400, message = "Error", response = classOf[models.ApiResponse])))
  def loginUser() = Action { request => {
      val response = loginDAO.loginUser(
        request.headers.get(logonHeader).getOrElse(""),
        request.headers.get(pwHeader).getOrElse(""))
      if (response.returnStatus == 0)
        Ok(Json.toJson(response))
      else
        Result(
        header = ResponseHeader(400,
          Map("errorCode" -> response.returnStatus.toString, "errorDesc" -> response.returnStatusMessage)),
        body = HttpEntity.Strict(ByteString(Json.toJson(response).toString()), Some("application/json"))
      )
    }

I used Result  instead of BadRequest b/c I wanted to set additional header information and see if that was the issue.
I believe either I haven't done the annotations correctly, or this is possibly a bug in the swagger ui.

Sorry, turns out not to be an issue with play-swagger, but with swagger-ui newer versions.


Feature: Balanced Accuracy

Click to expand!
Issue Type
Feature Request
Source
binary
Tensorflow Version
tf 2.10.0-rc3
Custom Code
No
OS Platform and Distribution
Debian 11
Mobile device
No response
Python version
3.9
Bazel version
No response
GCC/Compiler version
No response
CUDA/cuDNN version
11.2
GPU model and memory
No response
Current Behaviour?
I suggest adding Balanced Accuracy as additional Keras metrics.
It is useful for training with an imbalanced validation dataset.
(Note: I see various suggestions on StackOverflow: 1, 2)
Standalone code to reproduce the issue
import tensorflow as tf
metrics = [tf.keras.metrics.BalancedAccuracy()]

Relevant log output
No response

@jondo,
Could you please try to use tfma.metrics.BalancedAccuracy as mentioned in this doc link & SO link and let us know if you are looking for the similar feature. Thank you!

I think that the request regards the implementation of the BalancedAccuracy metric as an option in tf.keras.metrics. Actually, the proposed method in the SO link is to write a custom metric class, while the documentation linked is referring to TFX and not to the standard TF library

The BalancedAccuracy metric needs to be implemented in the standard TF library, It's really helpful with imbalanced data.

Totally agree with @Mustafa-MS, any updates on this?


🌈 Various improvements for Color

Similar to #56 but for the Color type:

Inline props
Document everything, including some methods that do require me to read the source like Darken
Use GeneratedRegex
Include some basic colors that were missing (Yellow and Cyan)

Looks great! Thanks!


super minor typo on the apiary

I am not trying to be annoying, really! I just noticed it and figured to let you know.
At http://docs.panoptes.apiary.io/#reference/subject-set/subjectset/retrieve-a-single-subject-set
The response text reads  "set_member_subject_cound": 100, (which is see fixed in the actual response from my server).

Also, at the http://docs.panoptes.apiary.io/#reference/classification/classification-collection/create-a-classification the following comments.

Create a classification by providing a JSON-API formatted object that must include annotations and a links hash with a set_member_subject, a project, and a workflow.

Which if I am not mistaken should be the subjects

Optionally may include the complete field, which will be set to true by default.

Which apart from the completed, could also use an explanation for what it does. (Does this imply that I can save incomplete classifications for example, so the user can later continue where he left it?).

Feel free to fix the docs and issue a pull request. Google hit hub and contributing via a pull request.
Completed is indeed for temporarily storing incomplete classifications. Cross device as well!

Erm sure, but how? If I get it right I need to fork the project, do my changes, then issue a pull request. But where are the docs?

https://github.com/zooniverse/Panoptes/blob/master/apiary.apib

Closed by #510

I am assuming you fixed them yourself. Sorry I didn't do it promptly, I have no git experience so it takes a while to understand how things work.

No worries, just trying to encourage you. Any contribution back from the community is great. Hopefully we can leverage your JS code as API examples when your they are stable and your happy with them.

Sure thing. Actually I just installed git and managed to fork and clone to the server. So for training I will make the effort to spell check the documentation. The documentation you just updated could also use some clarification, so I can do that as well if you clarify it.
We are talking for http://docs.panoptes.apiary.io/#reference/classification/classification-collection/create-a-classification

and a links hash containing a subjects hash, a project and workflow ids.

a) Does this mean a lot of ids so I update the code with a workflow id hash instead of a single id
b) It is a typo and should be "workflow id" and not "ids"
c) Neither
for reference
'links': {
      'subjects': [
        '11'
      ],
      'workflow': '81',
      'project': '2'
    }

Create a classification by providing a JSON-API formatted object that must include metadata. The metadata hash must contain the keys specified below.

There is no below. Does this mean all the keys we see in the code are mandatory?
'metadata': {
      'started_at': '2014-08-24T22:20:21Z',
      'finished_at': '2014-08-24T22:24:31Z',
      'user_agent': 'cURL',
      'user_language': 'es_MX',
      'workflow_version': '11.12'
    },

Re 1), it could be clearer and it's both, a workflow id and a project id.
Again any doc PR's that you reword would be appreciated, as a consumer of the API docs your opinions is valued!
Re 2), below mean the classification example in the docs. On apiary it's formatted to display in another panel, in the docs it's below. Feel free to PR this change too!


fix: Enable EventBridge rules/targets before EKS cluster

Description
The eventbridge target for the rule eks-api-endpoint-create wasn't getting created with the first terraform apply command and it doesn't get created until after the EKS cluster is completely setup causing the initial ENI create events to be missed.
This PR ensures that the first  terraform apply command:

Includes the target module.eventbridge that takes care of creating both modules module.create_eni_lambda and module.delete_eni_lambda
For the above to be possible, it removes the dependency of module.delete_eni_lambda on module.eks

How was this change tested?

[ ] Yes, I have tested the PR using my local account setup (Provide any test evidence report under Additional Notes)
[ ] Yes, I ran pre-commit run -a with this PR

@vchintal please see the error in the CI check.

Hi @askulkarni2, its a know issue unfortunately. Since we do not run all of the TF at once, we cannot expect the TF plan to succeed.
If you see in the README we have broken this up into two TF apply commands. If the first command is run and then the TF plan is run, it will succeed. Let me know if this explanation makes sense.

Gotcha. Can you please update the github workflow to skip this blueprint then?

@askulkarni2  Sure, can do! Can you please point me to where I have to make the necessary changes? I haven't done this before and do not want to assume.

Sure, it would just be under https://github.com/aws-ia/terraform-aws-eks-blueprints/blob/main/.github/scripts/plan-examples.py.

@askulkarni2  Think I have done it right, please check the latest commit. Thanks 🙏🏼


Mini Map

Need to know how much effort to show a mini process map that is clickable to that location on the canvas.

There's an example of a mini-map on the JointJS website: https://resources.jointjs.com/tutorial/multiple-papers. It seems setting up a basic mini-map won't take too long; making it interactive and having it show the viewport overlay would be the tricky part. I'd give it 2-3 days to implement.

Let's hold on this.

@velkymx
The mini-map is implemented. We thought the best place for it would be the top left corner of the canvas because if it were to be placed in the bottom right corner the validation drawer would overlap the mini-map.
Also we styled the buttons with the bootstrap classes.

How do we want to handle interaction with the mini-map ?
Ideas

scale the mini-map with the main canvas
clicking an area on the mini-map will move the canvas to where you clicked
dragging either mini-map or canvas will mirror each other


[doc] Use Rainbond deployment DolphinScheduler Cluster

Signed-off-by: Qi Zhang<EMAIL_ADDRESS>
Purpose of the pull request
This pull request add new installation,use Rainbond deploy DolphinScheduler cluster.

Brief change log

Verify this pull request

This pull request is code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:

One more thing, maybe we should put this doc in new section named integrated better than Installation

docs/docs/zh/guide/installation/integrated/rainbond.md
Put the doc in this directory?

@zhongjiajie proposal has been dealt with.please review

I had approved to run CI.

@SbloodyS I don't quite understand why ci didn't pass.Can you give me some guidance?

@SbloodyS I don't quite understand why ci didn't pass.Can you give me some guidance?

Sorry for late reply. You can find the detail of errors in https://github.com/apache/dolphinscheduler/runs/7368120405?check_suite_focus=true. And you can find this url in the Dead Link's Detail.

@SbloodyS All checks have passed.Please review

@zhongjiajie PTAL.

@zhongjiajie @EricGao888 PTAL.

Hi @zzzhangqi, I just added some comments, thx

Hi @EricGao888 ,I have revised your suggest.please approve run ci. 🤗

Hi @EricGao888 ,I have revised your suggest.please approve run ci. 🤗

@zzzhangqi Hi, thx for the update. CI already seems running. GitHub CI has been extremely slow recently, all we could do is wait. 🤣

@EricGao888 Hi, All checks have passed.Please again  review.😜

LGTM

Thanks,This pr auto merge?

LGTM

Thanks,This pr auto merge?

@zzzhangqi We need two approvals here to get it merged. Maybe you could ping another committer if you're hurried to get it in : )

Thanks 😘

@zhongjiajie Hi, Please review, Thanks.

And BTW, I think it belong to section integration instead of deployment, maybe we should add a new sidebar named integration to hold this or other content like that, WDTY @EricGao888 @zzzhangqi

LGTM

Thanks,This pr auto merge?

@zzzhangqi We need two approvals here to get it merged. Maybe you could ping another committer if you're hurried to get it in : )

FYI, @EricGao888 currently we only need one approval to merge PR

And BTW, I think it belong to section integration instead of deployment, maybe we should add a new sidebar named integration to hold this or other content like that, WDTY @EricGao888 @zzzhangqi

Sounds good to me.

https://dolphinscheduler.apache.org/en-us/docs/dev/user_doc/guide/homepage.html

No problem

Can we remove img monitor-dolphinscheduler.png and homepage-dolphinscheduler.png and it related content? it is duplicate to exists https://dolphinscheduler.apache.org/en-us/docs/dev/user_doc/guide/homepage.html and https://dolphinscheduler.apache.org/en-us/docs/dev/user_doc/guide/monitor.html
maybe you add a hyper link to above link, or directly use pure markdown content without img

No problem

And BTW, I think it belong to section integration instead of deployment, maybe we should add a new sidebar named integration to hold this or other content like that, WDTY @EricGao888 @zzzhangqi

move to dev/user_doc/guide/installation/integration ? @EricGao888 @zhongjiajie  Is that okay?

Hi @zhongjiajie , May I ask how to deal with this PR next? What should I do?

And BTW, I think it belong to section integration instead of deployment, maybe we should add a new sidebar named integration to hold this or other content like that, WDTY @EricGao888 @zzzhangqi

move to dev/user_doc/guide/installation/integration ? @EricGao888 @zhongjiajie Is that okay?
or dev/user_doc/integration/rainbond.html first level menu?

I prefer dev/user_doc/integration/rainbond.html. WDYT @SbloodyS @zhongjiajie

And BTW, I think it belong to section integration instead of deployment, maybe we should add a new sidebar named integration to hold this or other content like that, WDTY @EricGao888 @zzzhangqi

move to dev/user_doc/guide/installation/integration ? @EricGao888 @zhongjiajie Is that okay?
or dev/user_doc/integration/rainbond.html first level menu?

I prefer dev/user_doc/integration/rainbond.html. WDYT @SbloodyS @zhongjiajie

I agree, I will modify according to dev/user_doc/integration/rainbond.html? @SbloodyS @zhongjiajie @EricGao888

How to deal with this PR next? @EricGao888 @SbloodyS @zhongjiajie

I have modified @EricGao888 , Please review

By adding different integrations with DS, it helps enrich the ecosystem. If there are no more comments on this PR, I will proceed to merge it. @SbloodyS @zhongjiajie

@zzzhangqi Thanks for contributing this to DS! Good job!

@SbloodyS Please optimize the commits log when merging PR.

@SbloodyS Please optimize the commits log when merging PR.

I'll take care of it next time. Thanks.


simp breaks on match with more than one "as" pattern

def f : Option Nat → Option Nat → Option Nat
  | l'@(some _), r'@(some _) => r'
  | l', r' => r'

example : (f l r) = r := by
  simp [f]

produces the following error:
application type mismatch
  h_1 (some val)
argument has type
  Option Nat
but function has type
  (val val_1 : Nat) → motive (some val) (some val_1)

This is subsumed by #1179, correct?


Taskqueue and Database slave nodes are no longer sent by tools

https://ocd.appscale.com:8080/job/Daily Build/3581/

Are these new methods used somewhere?

@jeanleonov The rest of the codebase uses the convention is_<rolename> frequently. The object was handling those requests with method_missing.


It is possible to get lost in the editor when changing the zoom level

What Happened
When using the block coding editor, it is possible to get lost, particularly when zooming as well as panning. If I find myself looking at a blank canvas, it is unclear what direction to pan in order to find my blocks again.
How to Reproduce
When using the pong_game example, use the mouse wheel zoom out a long way, then zoom in on an empty space.
Block Coding Plugin Version
v0.6.2
Godot Engine Version
v4.2.2.stable
Operating System
No response
Logs or command-line output
No response
Anything else?
No response

Fixed by the PR above. Will be in next release.


Fix format

Codecov Report

Merging #283 (00d1295) into master (b5c6b74) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #283   +/-   ##
=========================================
  Coverage     75.02%   75.02%
  Complexity      696      696
=========================================
  Files           110      110
  Lines          2102     2102
  Branches        250      250
=========================================
  Hits           1577     1577
  Misses          435      435
  Partials         90       90

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 b5c6b74...00d1295. Read the comment docs.


#7 Login Page is not opening in the Web View

#7 Login Page is not opening in the Web View
Originally posted by @akshay94659 in https://github.com/abinbabuabu/breview/issues/7#issuecomment-995428415

Will add the web view logic for login feature once it is fully working for mobile


Clientside Web Workers aren't served

Bug report
Describe the bug
When attempting to load web workers using webpack and worker-loader in a production app the worker chunk is built into .next/{BUILD_ID}.worker.js and .next/server/{BUILD_ID}.worker.js, but the client tries to load it from /_next/webpack/{BUILD_ID}.worker.js which isn't served.
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:

Clone https://github.com/bendman/nextjs-worker-example
Install and run the built site with yarn install && yarn build && yarn start
Navigate to the site. The logs will show a 404 error along the lines of:

GET http://localhost:3000/_next/webpack/7759d1859ec567640742.worker.js 404 (Not Found)

Expected behavior
The worker should load in its own chunk, and the page should show the following logs:

index.js:14 Host received: from Worker
worker.js:1 Worker received: from Host

System information

OS: macOS
Browser: Chrome
Version of Next.js: 6.1.1

Additional context
I've already tried solutions to a different chunk issue (https://github.com/zeit/next.js/issues/4642) with no positive results.
Also, this works fine in dev mode, just not when starting the built app.

I'm guessing you'll have to provide
name: 'static/[hash].worker.js'
And publicPath:
publicPath: '/_next/static'

Ah, that got me on the right track, thanks.  Here is the fix below, or you can see the updated repo with a working example. Your fix was close, I just had to remove the static/ from the publicPath to prevent it from looking at /_next/static/static/.
// next.config.js
module.exports = {
  webpack(config, options) {
    config.module.rules.push({
      test: /\.worker\.js$/,
      loader: 'worker-loader',
      // options: { inline: true }, // also works
      options: {
        name: 'static/[hash].worker.js',
        publicPath: '/_next/',
      },
    });
    return config
  }
}

I’d be up for having an official plugin in next-plugins for this, could you create it in github.com/zeit/next-plugins? That’d be super nice for future users 🙏🏻🙌🏻

Hi, I was trying to find a solution to a problem I got regarding web workers.
I'd like to reuse a web worker but I can't get it from the cache, instead it download it again with a 304 and I can't save few precious ms.
Basically how can I endup having the same behavior as in this sample and cache it in some way? : https://www.w3schools.com/html/tryit.asp?filename=tryhtml5_webworker (you'll trigger a worker fetch request by pressing start and stop worker multiple times)
Many thanks!

Ok after searching a bit I just discovered that in 'dev' max-age is 0.
All good then!

Hi, I'm trying to use this solution (+typescript) but I'm always getting 404, and it doesn't matter which workerLoaderOptions I pass, it always tries to load the worker from the same location.
This is my next.config.js file:
const withTypeScript = require('@zeit/next-typescript');
const withWebWorkers = require('@zeit/next-workers');

let config = {
  webpack: config => Object.assign(config, {
    target: 'electron-renderer',
  }),

  exportPathMap: async function () {
    return {
      '/home': { page: '/home' },
      '/about': { page: '/about' },
    };
  },

  workerLoaderOptions: {
    name: 'static/[hash].worker.js',
    publicPath: '/_next/static/',
  },
};

config = withTypeScript(config);
config = withWebWorkers(config);

module.exports = config;

As you can see, I tried changing the workerLoaderOptions.publicPath because the error is
GET http://localhost:8888/_next/b60848351c7f50d8f1a8.worker.js 404 (Not Found)

but even that, it doesn't change the location.
Generated files are

.next/b60848351c7f50d8f1a8.worker.js
.next/b60848351c7f50d8f1a8.worker.js.map

but nothing in .next/static
I even tried changing it to:
workerLoaderOptions: {
  name: 'static/WORKER.js', // the name here should be fixed instead of using the hash
  publicPath: '/_next/static/',
},

but again, the generated files and the loaded files are the same (is like it's not using the name and publicPath options?)
Any idea/advice?
System info:
OS: macOS
Electron version: 4.0.4
Version of Next.js: 8.0.1

@danikaze did you determine the issue? I have a very similar setup to yours and am experiencing the same thing. All pages show 404.

@danikaze @zachariahtimothy same issue on my end. Keep getting 404's and seem to be unable to get webpack to read/write worker files to .next/static/. Running into this on both the custom config above and the next.js workers plugin. Any ideas?

@joncursi I was able to get mine working using .js for worker. I tried using custom .ts config with webpack but got 404's no matter what. Note there is wonkiness with HMR causing a manual refresh when worker file changes. I believe this is a browser issue and not too big a deal.

Is there a fix for this? Getting same 404.

I succeeded!
but I don't know if it's correct.
i just hope that help you. good luck!
OS:window 10
"dependencies": {
"next": "^8.1.0"
"react": "^16.8.6"
"react-dom": "^16.8.6"
"worker-loader": "^2.0.0"
}
"devDependencies": {
"@zeit/next-typescript": "^1.1.1",
"ts-node": "^8.1.0",
"typescript": "^3.4.5"
}
// next.config.js
const withTypescript = require('@zeit/next-typescript');
module.exports = withTypescript({
  webpack(config, options) {
    // Begin: Web Worker 적용
    config.module.rules.push({
      test: /\.worker\.js$/,
      loader: 'worker-loader',
      options: {
        inline: true,
        name: 'static/[hash].worker.js',
        publicPath: '/_next/'
      }
    });
    // End: Web Worker 적용

    // Overcome webpack referencing `window` in chunks
    config.output.globalObject = `(typeof self !== 'undefined' ? self : this)`;

    return config;
  }
});

// src/webworker/types/index.d.ts
declare module 'worker-loader?name=static/[hash].worker.js!*' {
  class WebpackWorker extends Worker {
    constructor();
  }

  export default WebpackWorker;
}

// src/webworker/example.worker.ts
const ctx: Worker = self as any;

ctx.addEventListener('message', async (event) => {
  console.log('example.worker received 1:', event);
  ctx.postMessage({msgCode: 'S', msg: ''});
});

// src/components/MenuList.tsx
import MyWorker from 'worker-loader?name=static/[hash].worker.js!../webworker/example.worker';

class MenuList extends Component {
  render() {
    return
test!!

  }

  goReady = (strId: string) => () => {
    const worker = new MyWorker();
    worker.postMessage({aaa: 'aaaaa'});
    worker.addEventListener('message', this.onWorkerMessage );
  }

  onWorkerMessage = (event: any) => {
    console.log('onWorkerMessage', event);
  }
}


fix: update to eye v3.0.1

fix: update to eye v3.0.1

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

npm package (@latest dist-tag)
GitHub release
v4.0.1

Your semantic-release bot :package::rocket:


Network does not converge without prei-training

Hi, Chaminda, Thanks for your code! Nice work! I trained the ChangeFormer_v6 without loading the pre-trained files and the network did not converge on any dataset. It seems that the only choice is to load the pre-trained file, otherwise, it would not converge with very large losses. I notice that once using the pre-trained file, the network can perform well as expected. So, have you ever tried training ChangeFormer_v6 without pre-training? And what's the result? Did it converge very slowly or not converge? Thanks!

Hi @GeoZcx
Thank you for your interest in our work!
I tried to train the ChangeFormer without loading the pre-trained trained weights in the initial phase of the project and the network converged. However, in this case, the network converged a bit slow compared to the model initialized with pre-trained weights, so I always used pre-trained weights for my other experiments to save time. Even when I was training ChangeFormer for the DSIFN dataset, I used the pre-trained weights in LEVIRD-CD to get much faster convergence. Since you were seeing a very high loss value when you weren't using pre-trained weights, I recommend that you reduce the learning later by a factor of 10 or 100 so that the network slowly converges. Especially, if you are using the AdamW optimizer, I highly recommend that you use a very low learning rate compared to using Adam or SGD because AdamW has a very large boost term, so it requires a much lower learning rate. Also, using the pre-trained weight is very common when training transformer networks (i.e., non-local attention networks), so I recommend following the same trend in your research as well.
Let me know if you have further questions.
Best,
Chaminda.

Hi @GeoZcx
Also, one more thing I forgot to highlight in my previous answer. I have experienced improved performance when I was training my ChangeFormer with multi_scale-loss. Please make sure you have turned on this feature in the script when you are training the model.
Best,
Chaminda.


Automate UI testing win mac

Description of the PR

this is one extra PR to now merge into master

Testing

unit
integration
e2e
manual

- [ ] new unit tests created
- [x] all unit tests pass

- [ ] new integration tests created
- [x] all integration tests pass

- [ ] new e2e tests created
- [x] all e2e tests pass

- [ ] manual testing went well

Have you updated the TESTING.md or other relevant documentation on your branch?

[ ] Yes.
[ ] Not yet. I will do it next.
[x] Not relevant.

@jaakkonarhi is my hero! 🦸🏻


changed title to Alphabet triangle pattern

Why:
Closes #556
What's being changed: Title and description from Number triangle pattern --> Alphabet triangle pattern
Check off the following:

[x] I have reviewed my changes in staging (look for "Automatically generated comment" and click Modified to view your latest changes).
[x] For content changes, I have completed the self-review checklist.

Thanks @shrionit for contributing to this project 👍🏻


OIDC loading meta data fails due to path being stripped from identity-uri

Environment Details

Helidon Version: 2.4.0
Helidon SE
JDK version: JDK-17
OS: any
Docker version (if applicable):

Problem Description
An error is thrown due to failed lookup from .well-known/openid-configuration not existing.  The issue is this path should be appended to the full identity-uri from the config but currently its being appended to just the scheme and host portion.
Steps to reproduce
oidc:
...
identity-uri:  https://my-oidc.someplace.com/opidc/realm
Throws an exception with the following:
https://my-oidc.someplace.com/.well-known/openid-configuration can't be loaded.
The correct path should be:
https://my-oidc.someplace.com/opidc/realm/.well-known/openid-configuration
I believe this started with 2.4.0

Hi,
this is a blocker in my organization as we cannot upgrade helidon to version 2.4: is there any ETA?
*Ciao
Piero

Resolved for 2.x, only pending PR with forward port to 3.x


$care-gaps operation example doesn't work

Environment (please complete the following information):

6.10.0 (latest JPA Server)

Describe the bug
The steps documented in sec: <IP_ADDRESS>.1 don't work:
https://hapifhir.io/hapi-fhir/docs/clinical_reasoning/caregaps.html
Problem 1) The CaregapsPatientData.json in step 3, available here appears to be incorrect: https://github.com/hapifhir/hapi-fhir/blob/master/hapi-fhir-storage-cr/src/test/resources/CaregapsPatientData.json
The MeasureReport references:
"reference": "Procedure/end-to-end-EXM130-1"
But the actual Procedure has id "end-to-end-EXM130-2".
When you run $submit-data on this bundle it errors out because of the missing reference.
I manually corrected that.
Problem 2) Step 4 fails with error:
{
    "resourceType": "OperationOutcome",
    "issue": [
        {
            "severity": "error",
            "code": "processing",
            "diagnostics": "HAPI-2001: Resource Organization/default is not known"
        }
    ]
}

I stepped into the code to try to debug this, the exception is thrown from:
R4CareGapsService.validateConfiguration().

This line:
https://github.com/cqframework/clinical-reasoning/blob/3af4cbfa9c4966458a13144299951ad52b92391d/cqf-fhir-cr/src/main/java/org/opencds/cqf/fhir/cr/measure/r4/R4CareGapsService.java#L196
Resource configuredReporter = this.addConfiguredResource(Organization.class, this.myCareGapsProperties.getCareGapsReporter(), "care_gaps_reporter");

The CareGapsProperties instance has a defaulted value for CareGapsProperties.myCareGapsReporter of "default".
I don't see in the JPA Config (application.yaml) any example values to configure these properties.
Am I missing something?
@JPercival - FYI

For my problem 2, looking at the unit tests it looks like some properties are required: 		"hapi.fhir.cr.caregaps_section_author=Organization/alphora-author"
"hapi.fhir.cr.caregaps_reporter=Organization/alphora"
So could just be the documentation needs to be updated to note this.

I'll update the documentation as you suggested

I would also use this version of hapi-fhir-jpastarter, this was the official release that contained CR updates: https://github.com/hapifhir/hapi-fhir-jpaserver-starter/releases/tag/image%2Fv6.10.1


rename abi file

a nit for @kirkas

🟡 Heimdall Review Status

Requirement
Status
More Info

Reviews

🟡
0/1

Denominator calculation

Show calculation

1 if user is bot
0

1 if user is external
0

From .codeflow.yml

1

Additional review requirements

Show calculation

Max
0

0

From CODEOWNERS

0

Global minimum
0

Max

1

1

1 if commit is unverified
0

Sum
1


Podcasts Page: Image and Title Alignment

The title of the podcast should be left aligned with the second paragraph instead of pushed to the right. The podcast titles should also be 500 weight.

https://main--mammotome--hlxsites.hlx.page/us/en/about-us/news-media-category/podcasts

Green light from Kelsey and I!

That change looks great! Thank you!


toCurrency() returning wrong currency even with correct currentLocale()

I'm using the latest master which fixed the currentLocale() bug and on my tests it returns the correct locale (pt-Br). Nevertheless, when trying to use the method toCurrency() it shows the currency on the default Locale 'en' instead of the correct one 'pt-Br'.
Thanks.

Same here.
using I18n.toCurrency(10000) as well as I18n.l("currency", 10000) seems to ignore the locale and always returns US formatting.

Same problem. Currency and number formatting rely on the default locale, not the system one.
The workaround I currently use is to use toNumber / toCurrency with my own format settings:
render() {
    const currentLocale = I18n.currentLocale();
    const countryCode = currentLocale.split('-')[0];

    return (
      <View>
        <Text>{I18n.toNumber(1990.99, I18n.translations[countryCode].NUMBER_FORMAT)}</Text>
        <Text>{I18n.toNumber(1000, {...I18n.translations[countryCode].NUMBER_FORMAT, precision: 0})}</Text>
      </View>
    );
  }

Number formats are stored with other localization info:
I18n.translations = {
  ru: {
    greeting: 'Привет!',
    NUMBER_FORMAT: {
      precision: 2,
      separator: ',',
      delimiter: ' ',
      strip_insignificant_zeros: false,
    },
  },
  en: {
    greeting: 'Hi!',
    NUMBER_FORMAT: {
      precision: 2,
      delimiter: '.',
      separator: ',',
      strip_insignificant_zeros: false,
    },
  }
};

Yeah I added a new function as a workaround:
`//overwrite to Currency function
let newConvert = (number, precision) => {
return I18n.toCurrency(number, {
unit:I18n.t("currency"),
format:I18n.t("cuFormat"),
separator:I18n.t("cuSeparator"),
delimiter:I18n.t("cuDelimiter"),
precision: precision
})
}
I18n.cu = newConvert`
and added the values currency, cuFormat, cuSeparator, cuDelimiter to my language files.
Maybe its helpful for someone.

@zoontek Why was this issue closed? It is still present as of version 2.0.9

@andrejcesen Because it's an issue with i18n-js, tgis lib is just a connector to get the language of the device.

options = { unit: '€', delimiter: ',' , sign_first: false}
Only the Euro sign is rendered here, all other options are ignored.


replace intptr_t with isize

Signed-off-by: Ronald G. Minnich<EMAIL_ADDRESS>

I've tested this but you can too.


fix(bmr): filter btp messages for the destination bmc

Checklist:

[x] I have performed a self-review of my own code
[x] I have documented my code in accordance with the documentation guidelines
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] I have run the unit tests
[x] I only have one commit (if not, squash them into one commit).
[x] I have a descriptive commit message that adheres to the commit message guidelines

@MuhammedIrfan,
The test was failing because of a bug in the receiver.go Subscribe() method. You need to return _errCh instead of errCh. 44b6299 should resolve the issue.

Thank you @bbist


Followup fixups for PR #2.

This introduces a lot of small followup changes to
https://github.com/prometheus/docs/pull/2.
Some things are clear right/wrong spelling/grammar issues, while others
are a matter of style or taste.
Except in extreme cases, I didn't reflow the text aggressively to a
certain number of columns, in order to make it easier to spot
differences.
Let me know what you think.
Some reference links worth mentioning:
Compound adjectives:
http://www.grammar-monster.com/lessons/adjectives_compound_adjectives.htm
Run-on sentences:
http://grammar.ccc.commnet.edu/grammar/runons.htm
General tech-writing style guide (which I haven't actually looked at
much yet):
http://infobits.eu/tech-doc/style-guide/

@brian-brazil

LGTM


Register missing WebRTCDataChannelJS type

Rebased #55044 on the master branch as that PR was wrongly targeting 3.4.

Cherry-picked for 3.5.


flutter_svg package needs to be updated, causing build errors.

ERR : Because rave_flutter 0.0.9-alpha+1 depends on flutter_svg ^0.17.1 and no versions of rave_flutter match >0.0.9-alpha+1 <0.1.0, rave_flutter ^0.0.9-alpha+1 requires flutter_svg ^0.17.1.

    | So, because airvend depends on both flutter_svg ^0.18.0 and rave_flutter ^0.0.9-alpha+1, version solving failed.

I am getting this error also, would appreciate if this can be fixed as soon as possible.

The dependencies has been upgraded in #42. Please, can you update?

I am closing this issue since there's be no activity on it. Please, feel free to raise another one if the issue persists.


Upgrade to latest Google Cloud Java version 0.50.0

Version 0.50.0 contains the first GA version the Pub/Sub client library.

Also removed unused trace lib managed dependency.


move specs/docs which are now in readme's to the docs folder

point the readme's to the docs folder in stead
review all specs/docs (= issue #308)

point the readme's to the docs folder in stead

At least for nbdserver, all existing docs already exist also in the docs folder AFAIK. @robvanmieghem do thinks its useful to also have at least some important knowledge available in the module's README, but that doc is usually also available in the docs folder. Is that OK? Or do you really want all the docs only available in the docs folder?

point the readme's to the docs folder in stead

The 0-Disk consists of 3 sub-projects: NBDServer, TlogServer and zeroctl. All 3 have a README.md, as to provide some quick information. However, they all point already to the docs folder (see the bottom of all those readme files). So not sure what this issue is about. Could you perhaps clarify, as I might be misunderstanding something here?

Someone reading in docs folder should have all info or at least there need to be links from doc's folder intro docs to the readme's
my only goal is, it needs to be simple for people to find & read all information possible.

Will be resolved by improved docs issue #308.


Feature/custom event for 3rd party interaction #16

Fixes #16
This changeset introduces a custom event listener which allows the user to do async initialisation.
The user can dispatch a custom event named s3upload:init on the document, and optionally pass a CSS selector in the CustomEvent.details.
If passed, a custom selector will initialise S3Upload using that selector, if not, it will default to using .s3upload, which is the default selector used on DOMContentLoaded in the automatic global init.
An example of async init in action has also been added to the Example app, at /form/async/, so you can see a custom event dispatch with a custom selector in action.

Don't fully understand what this does, it's beyond my React-fu. If you like it, I like it.

@hugorodgerbrown no React involved, all it's doing is adding an event listener to the document so that you can do an init/re-init asynchronously, like after an AJAX content update or whatever.
I'll merge away in any case.


NFT minting not working from phantom and solflare

I am trying to mint the NFT using phantom but it's not working somehow. I have set phantom to devnet and i have enough Devnet SOL.
here is a demo explaining that the issue is
https://user-images.githubusercontent.com/62953475/220715719-dbb6032a-3921-46d9-9677-e71d5af71160.mp4

Pratik reported that Solflare is exhibiting the same behavior as well. I have not been able to reproduce on my end

Device: Samsung s20 FE Android 13

Not able to reproduce
Device: Realme 9 Android 13


Merge Kaelens Changes to main

including javadocs and comments, intents for a few pages and copyrights

No merge conflicts.  Merging with main.


bug(map-circle): Not show

I am trying to show maps circles but they are not showing on the map
Html code:
<google-map width="100%" [center]="center" [zoom]="zoom">
<map-circle [center]="circleCenter" [radius]="radius">

Component vars:
center: google.maps.LatLngLiteral = {lat: 24, lng: 12};
zoom = 4;
circleCenter: google.maps.LatLngLiteral = {lat: 24, lng: 12};
radius: 1000;
Angular:
"@angular/animations": "~10.0.14",
"@angular/cdk": "^10.1.3",
"@angular/common": "~10.0.14",
"@angular/compiler": "~10.0.14",
"@angular/core": "~10.0.14",
"@angular/google-maps": "^10.2.0",
Result:

@danieldflrss can you provide a reproduction on stackblitz?

@danieldflrss your problem is that you didn't actually initialize the radius to 1000, but you typed it as 1000. It should be radius = 1000 instead of radius: 1000. Also it's worth noting that 1000 is fairly tiny for the zoom level that you've set on the map so it's a little hard to see, but it's definitely there once you zoom in.


EventLogTarget truncates messages larger than the max message size

I noticed that EventLogTarget truncates messages when it reaches the max message size. Has it been considered to split the message and write the chunks to the event log?
This is the method in question:
https://github.com/NLog/NLog/blob/master/src/NLog/Targets/EventLogTarget.cs#L214

Hi,
We never considered that, because it's IMO a strange effect to create 2 events for 1 log message. Although, it's easy to implement.
Any way, this max size should be documented well.

I see your point about creating 2 events for 1 log message, specially if you are expecting log messages in a particular format like JSON and you do not get a properly formatted message.
We have been hit by this limitation with our homegrown logger and we are splitting the message. We care more about getting the entire message than getting two entries. I would think we are not the only ones. We have been talking about moving to something more robust and flexible like NLog and I particularly was testing long messages when I noticed they were being truncated.
You may ask what are we logging that is so large? We tend log web services responses (raw XML or JSON) in error scenarios.
I know I can overcome this behavior by inheriting from EventLogTarget and overriding the Write method, but I was wondering if you would be interested in making this an option of EventLogTarget that consumers could opt in to? I could help with a pull request.

I think it's nice of we create a "overflow"  option. With possible values (enum) : truncate,  create multiple events.
The big benefit is that the truncate is more transparent.
What do you think?

I like it. I'll work on the change. Do you think a third value "Ignore" as in ignore the log message altogether would be useful? I'm thinking of those scenarios where we wouldn't like to have incorrectly formatted entries in the logs. Maybe we are rigorously expecting XML or JSON in the logs.

I think Ignore is also useful (in some rare cases) :+1:

Closing as feature has been implemented and merged in #1041

Thanks!

docs: https://github.com/NLog/NLog/wiki/EventLog-target (up-to-date)


Request for OptimizelyClient to be an interface

Today OptimizelyClient is exposed directly as a struct. This doesn't allow users of the sdk to easily test integrations via tools like gomock or counterfeiter, as these tools are built around generating fake implementations of interfacing for mocking out in tests.
I considered just putting up a PR but, didn't for a couple reasons:

Would be a pity to put the PR together and be told "nope, we do not want to do that" :D

It is an API incompatible change. If you have something like the following, it would break on the ConfigManager line b/c interfaces don't have members (so the change would, at the least, have to change it to a call to ConfigManager()).

client := factory.Client(...)

client.ConfigManager.Whatever()

Does this seem like a viable change? Today we simply wrap calls to factory.Client() so that they return an interface we define in our own code, which is just an exact mirroring of the subset of the  OptimizelyClient methods we use, so that we can generate mocks on that interface for testing. This of course isn't a joy in terms of maintenance or boiler plate though... thus this request!

Thank you for raising this request! We are discussing it as a team and will get back to you in the coming days 😄

@codeferret1 thanks for your patience. We've discussed this internally and have decided not to provide one this close to the release date, especially since we have some beta versions out there and this would be a breaking change. We do think it can be valuable and will definitely consider for the next major version release. Will keep this open until then.


Bug adding hosts to host file

Hello,
I'm trying to add some host like this:
project.hosts.forEach(function (mapping) {
	hostile.set(mapping.ip, mapping.hostname, function (err) {
		if (err) {
			console.error(err)
		} else {
			console.log('Successfully added:', mapping.ip, mapping.hostname);
		}
	});
});

It outputs:
[09:01:27] Starting 'apply-hosts'...
Successfully added: <IP_ADDRESS> brian.example.com
Successfully added: <IP_ADDRESS> allan.example.com

but only brian.example.comis added to the host file. I'm running windows 8.1.

Duplicate of #9.


Command not found

This seems unclear to me. I ran the following command npm install -D chrome-extension-scripts and would expect the following commands to work, but the command doesn't' seem to exist.

$ chrome-extension run manifest.json -o ./build
-bash: chrome-extension: command not found

Either add node_modules/.bin to your path and use the command from project root or
use ./node_modules/.bin/chrome-extension instead of chrome-extension from project root.


Email search regex does not include +

https://github.com/gchq/CyberChef/blob/ec9dfd2918355f082589dd73b4b4ee3f99b5a11a/src/core/operations/ExtractEmailAddresses.mjs#L42
Some email providers accept emails with '+' eg<EMAIL_ADDRESS>. In such situation, email is sent to<EMAIL_ADDRESS>and allocated to a specific folder, automated reply etc..
The current regex would only match<EMAIL_ADDRESS>which is not the actual email of the recipient.
It is a rare occurrence but I thought I would throw it in for the good measure.
Alternative regex could be
\b\w[-+.\w]*@[-\w]+(?:\.[-\w]+)*\.[A-Z]{2,4}\b

Hi, I'm going to take a look at this if that's okay!


Delete beaker-electron.rb

Ref: https://github.com/caskroom/homebrew-cask/pull/16029

Merged as 0848cb514737d036c4a308ce5de53caf6626851c.


operation osd issues

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Test Server Env:
OS: Ubuntu 18.04.5 LTS ; Three server nodes ; Ceph version: octopus (stable)
ceph-ansible/group_vars (origin/stable-5.0)

Adding osd(s) tutorials
server's disk localtion maybe not different, i mean some server's root disk boot from /dev/sdb not /dev/sda；
how to configure devices for ceph osd within osds.yml in that situation;
example1
Specify the hard disk partition to create osd in new ceph cluster:
server1:
/dev/sdc
/dev/sdd

server2:
/dev/sdb
/dev/sdc

server3:
/dev/vdb
/dev/vdc

how to configure osds.yml,and which command execute it with ceph-ansible;

example2
if server1 add disk, then it will have /dev/sde, and wanna add /dev/sde in ceph cluster;
how to configure osds.yml, and and which command reconfigure it with ceph-ansible;

example3
if server1 need remove /dev/sdd, and this disk partition have been add in ceph cluster;
how to configure osds.yml, and and which command reconfigure it with ceph-ansible;

osds.yml device , is there have any chance to use as following configuraion；
devices:
  ## Description format : exmaple HOSTNAME: ["/dev/xx","/dev/xx"]
  ## example server1: ["/dev/sdc","/dev/sdd"], and server1 must add domain in /etc/hosts
  ## if HOSTNAME will have some issues with docker, then hostname could replace with ip address;
  ## example <IP_ADDRESS>: ["/dev/sdc","/dev/sdd"]
  server1: ["/dev/sdc","/dev/sdd"]
  server2: ["/dev/sdb","/dev/sdc"]
  server3: ["/dev/vdb","/dev/vdc"]

Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
https://docs.ceph.com/projects/ceph-ansible/en/latest/day-2/osds.html

Does ceph-ansible tutorials will add more system release support description,
ubuntu16 can't install ceph within (ceph-ansible/ (origin/stable-5.0))  that deault python3.5's issuse conflict with ansible,
but same confiugration could install in ubuntu18.
and more operation description will have any chance to add in tutorials?

ceph-ansible is good stuff, thank you for your sharing.

osds.yml device , is there have any chance to use as following configuraion；
devices:
  ## Description format : exmaple HOSTNAME: ["/dev/xx","/dev/xx"]
  ## example server1: ["/dev/sdc","/dev/sdd"], and server1 must add domain in /etc/hosts
  ## if HOSTNAME will have some issues with docker, then hostname could replace with ip address;
  ## example <IP_ADDRESS>: ["/dev/sdc","/dev/sdd"]
  server1: ["/dev/sdc","/dev/sdd"]
  server2: ["/dev/sdb","/dev/sdc"]
  server3: ["/dev/vdb","/dev/vdc"]

You should take a look to the ansible documentation about variable configuration per group vs host [1][2]
If you use the osds.yml file (group_vars) then the configuration is applied to ALL osd nodes and they should have the same devices layout.
If you don't have the same devices layout then you have to use the ansible host_vars

host_vars/server1.yml

devices:
  - /dev/sdc
  - /dev/sdd

host_vars/server2.yml

devices:
  - /dev/sdb
  - /dev/sdc

host_vars/server3.yml

devices:
  - /dev/vdb
  - /dev/vdc

Or alternatively set this configuration in the ansible inventory
[osds]
server1 devices="['/dev/sdc', '/dev/sdd']"
server2 devices="['/dev/sdb', '/dev/sdc']"
server3 devices="['/dev/vdb', '/dev/vdc']"

[1] https://docs.ansible.com/ansible/latest/user_guide/playbooks_variables.html#variable-precedence-where-should-i-put-a-variable
[2] https://docs.ansible.com/ansible/latest/user_guide/intro_inventory.html#splitting-out-vars


Question regarding 2-bit quantization

Hello,
Thank you for the amazing work and providing such a well-organized codebase.
I understand that 2-bit support is excluded from this codebase because of the significant degradation in performance (Issue #4), and I implemented 2-bit precision kernel on my own, thanks to the surprisingly intuitive implementation of the original code.
To verify my implementation, I compared the results with fake quantization results obtained with fake_pack.py (below snippet is part of the results.json)
    "anyprec-(Llama-2-7b-hf)-w8_orig2-gc1-c4_s100_blk512": {
        "ppl": {
            "2-bit:wikitext2": NaN,
            "2-bit:c4_new": 34.1552619934082,
            "2-bit:ptb_new_sliced": 38.83564376831055,
			...
        }
    },
    "fake_anyprec-p2-(Llama-2-7b-hf)-w8_orig2-gc1-c4_s100_blk512": {
        "ppl": {
            "None-bit:wikitext2": NaN,
            "None-bit:c4_new": 34.1552619934082,
            "None-bit:ptb_new_sliced": 38.83564376831055
        }
    },

You can find my implementation in the forked repo here. If there are any issues or missing details, I'd appreciate your feedback (it also fixes minor typo in README.md, please let me know if you want me to submit a pull-request).
You can reproduce the result by running python quantize.py --seed_precision 2 meta-llama/Llama-2-7b-hf in the forked repo.
My question is as follows:

Do you have any insights on why the 2-bit wikitext2 perplexity here doesn't match the reported performance of SqueezeLLM for Llama-2-7b? Specifically, Table F.10 of the SqueezeLLM paper shows that 2-bit perplexity for wikitext2 should be 35.49, yet the result here returns NaN. I used seed_precision as bits=2, which should correspond to SqueezeLLM's 2-bit performance.

I am aware that 2-bit quantization is beyond the scope of this codebase, but any insights into the cause of this discrepancy would be incredibly helpful for my research.
Thank you for your time.

I'm not the maintainer of this repo but happen to work on this.
NaN could be fixed by: https://github.com/fwtan/any-precision-llm/blob/4a8e34c26716e995b9746b9a21cc971060f5e2f5/any_precision/modules/AnyPrecisionLinear.py#L72
SqueezeLLM used fp32 activations so there were lower chances to overflow.
Here are the results of 2-bit llama 7b we got: eval_results.json

@fwtan Thank you so much for sharing your result.
I double-checked that clipping indeed remedies the underflow/overflow. Closing the issue for now.

Sharing the results before/after clipping for future people who might be interested in.
Before clipping:
  "anyprec-(Llama-2-7b-hf)-w8_orig2-gc1-c4_s100_blk512": {
    "ppl": {
      "c4_new:2-bit": 34.1552619934082,
      "c4_new:3-bit": 8.325156211853027,
      "c4_new:4-bit": 7.459658145904541,
      "c4_new:5-bit": 7.3085784912109375,
      "c4_new:6-bit": 7.273617744445801,
      "c4_new:7-bit": 7.2652082443237305,
      "c4_new:8-bit": 7.263840675354004,
      "ptb_new_sliced:2-bit": 38.83564376831055,
      "ptb_new_sliced:3-bit": 9.229948997497559,
      "ptb_new_sliced:4-bit": 8.345032691955566,
      "ptb_new_sliced:5-bit": 8.16357421875,
      "ptb_new_sliced:6-bit": 8.121023178100586,
      "ptb_new_sliced:7-bit": 8.114277839660645,
      "ptb_new_sliced:8-bit": 8.107175827026367,
      "wikitext2:2-bit": NaN,
      "wikitext2:3-bit": 6.240961074829102,
      "wikitext2:4-bit": 5.644721508026123,
      "wikitext2:5-bit": 5.517499923706055,
      "wikitext2:6-bit": 5.483019828796387,
      "wikitext2:7-bit": 5.474261283874512,
      "wikitext2:8-bit": 5.472561836242676
    }
  },

After clipping:
  "anyprec-(Llama-2-7b-hf)-w8_orig2-gc1-c4_s100_blk512": {
    "ppl": {
      "c4_new:2-bit": 34.1552619934082,
      "c4_new:3-bit": 8.325156211853027,
      "c4_new:4-bit": 7.459658145904541,
      "c4_new:5-bit": 7.3085784912109375,
      "c4_new:6-bit": 7.273617744445801,
      "c4_new:7-bit": 7.2652082443237305,
      "c4_new:8-bit": 7.263840675354004,
      "ptb_new_sliced:2-bit": 38.83564376831055,
      "ptb_new_sliced:3-bit": 9.229948997497559,
      "ptb_new_sliced:4-bit": 8.345032691955566,
      "ptb_new_sliced:5-bit": 8.16357421875,
      "ptb_new_sliced:6-bit": 8.121023178100586,
      "ptb_new_sliced:7-bit": 8.114277839660645,
      "ptb_new_sliced:8-bit": 8.107175827026367,
      "wikitext2:2-bit": 23.83866310119629,
      "wikitext2:3-bit": 6.240961074829102,
      "wikitext2:4-bit": 5.644721508026123,
      "wikitext2:5-bit": 5.517499923706055,
      "wikitext2:6-bit": 5.483019828796387,
      "wikitext2:7-bit": 5.474261283874512,
      "wikitext2:8-bit": 5.472561836242676
    }
  },

Seems like k-means clustering has bigger variance for 2-bit case. Increasing max_iter may be helpful.


Add charmcraft support

python3-dev because of cython problems.

Thanks for this commit.  Currently the CI building this charm uses charm tools to build since it's reactive.
This charm will likely soon go through an up-lift to ops rather than reactive -- in which event it will be built with charmcraft.  We can build off this work if you'd like

Yes, honestly the only reason for me to use charmcraft is that charm-tools is a bit wird about python versions and such.
Our build pipeline supports both too. But with charmcraft I'm a bit more sure it will still work in a year or so 😁
No need to take it upstream if it doesn't improve anything for you

@tbaumann is this charm one that you regularly build?

No ideally not. But I have been bitten in the past with charms that have become unbuildable after some time.
It takes a lot of time to workaround

If it helps i'll try to keep em building for you.
the previously releases are available at
https://charmhub.io/keepalived
and you can always fetch a specific channel using
juju download keepalived --channel=1.27/stable
juju deploy keepalived --channel=1.27/stable
juju refresh keepalived --channel=1.27/stable

We do soon hope to have this charm converted to ops -- but will likely maintain the charmtools builds since keeping the reactive layers inline for older releases (1.26, 1.25) requires charm building using local layers rather than the layer index since the charmcraft reactive plugin doesn't allow one to use alternate layer indexes/branches

Ah yes, I noticed the exact same problem today. 😅
No way to pass custom layer dirs variables to charm build.
Our workflow depends on us building our own charms. In case we need custom mods.
Also charmhub builds lack really useful versioning and changelogs.


.sh ext should not be used to set local ft

I think I have only ever seen .bash scripts in one project (https://github.com/golang/go/tree/master/src) almost all the bash scripts I've seen are named .sh and have bash in the shebang. Currently, neomake is treating bash shebanged files with .sh extensions as ft=sh instead of ft=bash. ext ==# 'sh' should not be used since it is common to write bash scripts with .sh extensions.
Expected behavior
neomake does not use ext ==# 'sh' in any of the tests, which allows shell scripts to be shellchecked in the mode specified in the shebang line.

Steps to reproduce

ensure shellcheck is used to check the following file named test.sh
#!/usr/bin/env bash

source somefile

shellcheck will complain about the use of source in a POSIX sh file.
Output of the ":verb NeomakeInfo" command

Neomake debug information
Async support: 1
Current filetype: sh
Enabled makers
For the current filetype (with :Neomake): ['sh', 'shellcheck']
NOTE: you can define g:neomake_sh_enabled_makers to configure it (or b:neomake_sh_enabled_makers).
For the project (with :Neomake!): []
NOTE: you can define g:neomake_enabled_makers to configure it.
Settings

shell: /usr/bin/zsh
shellcmdflag: -c
Windows: 0

:version

NVIM v0.2.0-66-g0c799a8
Build type: RelWithDebInfo
Compilation: /usr/bin/cc -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -Wconversion -O2 -g -DDISABLE_LOG -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wvla -fstack-protector-strong -fdiagnostics-color=auto -DINCLUDE_GENERATED_DECLARATIONS -DHAVE_CONFIG_H -D_GNU_SOURCE -I/home/manny/.cache/pacaur/neovim-git/src/neovim-git/build/config -I/home/manny/.cache/pacaur/neovim-git/src/neovim-git/src -I/usr/include -I/usr/include -I/usr/include -I/usr/include -I/usr/include -I/usr/include -I/usr/include -I/home/manny/.cache/pacaur/neovim-git/src/neovim-git/build/src/nvim/auto -I/home/manny/.cache/pacaur/neovim-git/src/neovim-git/build/include
Compiled by manny@manny

Optional features included (+) or not (-): +acl   +iconv    +jemalloc +tui
For differences from Vim, see :help vim-differences

   system vimrc file: "$VIM/sysinit.vim"
  fall-back for $VIM: "/usr/share/nvim"

:messages
"../../rc.sh" 12L, 223C

I have a local patch that removes the use of ext ==# 'sh' I can submit if this sounds like a good idea.

Yes, this seems to be caused by https://github.com/neomake/neomake/pull/777.
I agree that the shebang should take precedence, but just removing the ext ==# 'sh' might not be the correct solution.
/cc @mhinz

It's not setting the ft for me...
The let ft is a let l:ft, not set ft or let &ft (https://github.com/neomake/neomake/blob/4c4a2dd0623cdd6d34e0e00a1eab3c62d738da17/autoload/neomake/makers/ft/sh.vim#L19)
There is no "bash" filetype in vim and neovim by default -- they use the "sh" filetype with flags to cater to various shell types.
*.sh and *.bash should always be sh filetype. Anything else is user defined.

@mmlb
With what file do you get the behavior?
It would also help to actually run :let g:neomake_verbose = 3 | Neomake to see what is being done in :mess.

@davidosomething my ft=sh which is not the problem, it's the local var ft https://github.com/neomake/neomake/blob/41d6a5705bcb3b1b5dd4f2bdc7f81778cc5a11e7/autoload/neomake/makers/ft/sh.vim#L23 that is added to the shellcheck invocation that is a problem.
Neomake [6.714]: [1] Running makers: ['sh', 'shellcheck']                                                                                Neomake [6.715]: [1] Starting async job: ['/usr/bin/env', 'bash', '-n', '/home/manny/t.sh']                                                                                Neomake [6.718]: [1] Starting async job: ['shellcheck', '-fgcc', '-s', 'sh', '/home/manny/t.sh']                                                                                Neomake [6.722]: [1.4] exit: sh: 0                                                                                Neomake [6.723]: [1.4] sh: completed with exit code 0.                                                                                Neomake [6.723]: File-level errors cleaned in buffer 1                                                                                Neomake [6.724]: [1.5] stdout: shellcheck: ['/home/manny/t.sh:3:1: warning: In POSIX sh, ''source'' in place of ''.'' is undefined. [SC2039]', '/home/manny/t.sh:3:1: note: Not following: somefile was not specified as input (see shellcheck -x). [SC1091]', '']                                                                                Neomake [6.726]: [1.5] exit: shellcheck: 1                                                                                Neomake [6.727]: [1.5] shellcheck: processing 2 lines of output.                                                                                Neomake [6.728]: Placing sign: sign place 5000 line=3 name=neomake_warn buffer=1                                                                                Neomake [6.730]: [1.5] shellcheck: completed with exit code 1.

oh okay I understand
here's a concise description:
OBSERVED
ext .sh + shebang bash = shellcheck -s sh (neomake decided based on shebang getline())
EXPECTED
ext .sh + shebang bash = shellcheck (no -s flag, shellcheck will read shebang, using bash or ash or dash or zsh if it finds one, and assume bash if not since that is the shellcheck default)
That is the one and only case that should change
+@mhinz

@davidosomething no you're observed is wrong. neomake decided based on ext

^ edited, either way, preferred is to remove -s completely for .sh

Although shellcheck assumes the "bash dialect" if -s wasn't given, it will issue a warning about it nevertheless. Thus we'll always force if there's no valid shebang.
So, what about:
    if matchstr(getline(1), '\v^#!.*<%(sh|dash|bash|ksh)')
        " shellcheck reads the shebang by itself
    elseif ext ==# 'bash'
        let maker.args += ['-s', 'bash']
    elseif ext ==# 'ksh'
        let maker.args += ['-s', 'ksh']
    elseif ext ==# 'sh'
        if exists('g:is_sh')
            let maker.args += ['-s', 'sh']
        elseif exists('g:is_posix') || exists('g:is_kornshell')
            let maker.args += ['-s', 'ksh']
        else
            let maker.args += ['-s', 'bash']
        endif
    endif

why does is_posix default to korn shell? lgtm if theres a reason

ohh ksh is POSIX.2 compliant
lgtm

Okay, please see if the latest master works as expected.

+1 works for me

Thanks a lot!


Support persisting TableMetadata in the metastore

Description
This adds a new flag METADATA_CACHING_ENABLED which allows the catalog to store table metadata in the metastore and vend it from there when loadTable is called.
Entries are cached based on the metadata location. Currently, the cache is implemented as a "lazy" cache where entries are only loaded into the cache when loadTable is called. The entire metadata.json content is cached.
This is implemented through a new entity in Polaris called TABLE_METADATA that is treated as the child of a TABLE_LIKE.

Features not included in this PR:

Support for updating the cache when a table is updated
Support for invalidating cache entries in the background, rather than waiting for loadTable to be called
Structured storage for table metadata

I'm planning to follow up with at least item (1), but the goal is to structure things in a way that will allow us to implement (2) and (3) in the future as well.
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] Documentation update
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Existing tests vend table metadata correctly when caching is enabled.
Added a small test in BasePolarisCatalogTest to cover the basic semantics of caching
Manual testing with eclipselink -- I observed the entities getting created in Postgres and saw large metadata being cached:
db=# select length(internalproperties), substring(internalproperties, 1, 1000) from entities where id = 152;
...
 768691 | {"metadata_location":"file:/tmp/quickstart/ns/tn1731005976265/metadata/00000-e77a2576-5efa-4b7a-b948-121813d713f8.metadata.json","content":"{\"format ...

With MySQL, small metadata is persisted:
mysql> SELECT length(internalproperties), substring(internalproperties, 1, 1000) FROM ENTITIES WHERE id = (SELECT MAX(id) FROM ENTITIES WHERE typecode = 10);
. . .
8159 | {"metadata_location":"file:/tmp/quickstart/ns/t2/metadata/00000-64f975bd-c3a8-4069-bb56-f282003e9157.metadata.json","content":"{\"format-version\"

However large metadata may cause internalproperties to exceed the size limit and nothing will be cached. Calls still return safely.

This will potentially reduce a lot of I/O overhead! Thanks for working on it.

I think, we should have a design about how to handle table/view/udf metadata and its snapshots/versions and schemas/specs/etc and probably a vision how to deal with manifest list/file information.
Handling these metadata objects as "opaque blobs" is quite expensive (no database is made to handle such huge objects).
It would be nice to be have the information in a more structure way, but also efficiently accessible. Some use cases I can think of are:

For queries: just return the latest snapshot / just return one specific snapshot
Automatic metadata cleanup (remove unreferenced schema/spec/etc)

With this change, we exchange the (costly) round-trip to the object store with another (costly) round-trip to a database.

Actually, I think loading/saving table metadata should be transparently done, using a delegating code architecture.
Think: a (REST) resource asks for metadata "abc" using some interface IcebergMetadataStore (or so). There would be multiple implementations of that interface:

one that interacts with the actual object store
one that is implemented as a delegate to the one that interacts with the object store, but also provides a caching mechanism

That way the calling code does not need to care about caching at all, and testing would be quite isolated. Using such an interface with various implementations/delegates can also ease testing quite a bit.

It would be nice to be have the information in a more structure way, but also efficiently accessible.

Yes @snazy, I completely agree here. It's part of why I'm advocating for the loadTableV2 proposal in Iceberg.
Even for this workstream, I noted in the very beginning as a non-goal for this PR:

Structured storage for table metadata

I think it will be important to add in the future, but I think this PR is valuable as-is without this optimization.

I think, we can already experiment and reason about good approaches of how to "chunk the huge table/view/udf metadata blobs".
My concerns about overly increased heap pressure, especially when metadata becomes big/bigger/huge, still stand. We should really not rush things that have the potential to excessive over-use of resources.

However, it would help a lot, if different functionalities (think: persistence and cache) are abstracted and separated. So some REST resource implementation calls "loadMetadataOfThatTable()" on some interface - the first implementation is maybe a tracing facade, the next delegate is a caching layer, the next persistence metrics, and the next the actual persistence layer.

Unless I am missing something, this is "safe" if METADATA_CACHE_MAX_BYTES is set to a relatively low value, right?
In the absence of testing showing that there is measurable performance degradation due to churning large strings in the heap when METADATA_CACHE_MAX_BYTES is set to e.g. 10000, I posit that the performance is probably OK for now. Indeed, in the limited testing I have done, performance is actually much better compared to a solution that has no caching and always needs to go to object storage for the metadata.

when METADATA_CACHE_MAX_BYTES is set to e.g. 10000, I posit that the performance is probably OK for now.

Still, your approach re-serialized especially the big ones over and over again - and in fact: that is completely unbounded. To be clear: that's opening the door wider for a potential denial-of-service due to out-of-memory situations.

when METADATA_CACHE_MAX_BYTES is set to e.g. 10000, I posit that the performance is probably OK for now.

Still, your approach re-serialized especially the big ones over and over again - and in fact: that is completely unbounded. To be clear: that's opening the door wider for a potential denial-of-service due to out-of-memory situations.

Doesn't the catalog always have to do this regardless? We have to load the metadata.json from disk no matter what so the risk from unbounded json's is always present regardless of whether the Catalog also writes and reads a copy for itself.

Doesn't the catalog always have to do this regardless? We have to load the metadata.json from disk no matter what so the risk from unbounded json's is always present regardless of whether the Catalog also writes and reads a copy for itself.

The answer is actually that technically a catalog does not really have to materialize it in full in memory. It could technically stream it directly from the object store - or in chunks from another source.
@RussellSpitzer The bigger problem than materializing the big thing once is, that this change RE-serializes it again - and that is the real issue.

The answer is actually that technically a catalog does not really have to materialize it in full in memory. It could technically stream it directly from the object store - or in chunks from another source.

This is true, but we are not talking about what an arbitrary catalog technically has to do but what Polaris actually does do.
In the future I think we should optimize this with a structured schema in the metastore (perhaps that more closely matches the schema of the Java TableMetadata object) -- and when we do, we should optimize the cache as well.
The question is whether this future optimization is a blocker for adding caching on top of the current behavior.

@RussellSpitzer The bigger problem than materializing the big thing once is, that this change RE-serializes it again - and that is the real issue.

I don't think this is actually a big deal, especially if users can decided whether or not to use it. Users can potentially reduce their latency now for a cost of more memory usage and possible cpu cost. I honestly think most folks would want this now regardless of the current cost since I've seen several private implementations of REST catalogs that do this. I also probably would have it on by default.

@snazy sorry for all the pings. I took another look at your comments and the PR, and I identified one idea that I wanted to get your POV on.
I added this commit to bound the extra serde.
I don't love that this uses an exception to drive the flow control, but what do you think like an approach like this? Does this address your concerns around unbounded serde in the event that someone has a metadata.json which exceeds the configured limit?

I added this commit to bound the extra serde.
I am not in love with this exact implementation, but what do you think like an approach like this? Does this address your concerns around unbounded serde in the event that someone has a metadata.json which exceeds the configured limit?

Not sure - but the direction is correct.
However, I think there's a much bigger problem introduced by this PR: the permanent heap usage. Even if you bound each metadata to 1MB, that can accumulate to 100,000 * 1MB (~= 95GB) of permanent heap usage. With 10MB that's nearly 1TB of heap. Plus all the other attributes plus heap pressure during runtime. (100,000 entries is the hard coded limit in o.a.p.core.persistence.cache.EntityCache.)

Hi @snazy; I agree that the EntityCache is potentially a problem. I think it can be optimized pretty easily with a Weigher. Although the metastore caching is disabled by default, do you view this as a blocker by itself?
Indeed originally in older versions of this PR I had the metadata skip the EntityCache, but @dennishuo convinced me that in many cases it's quite useful to have the in-memory caching.

Yes, the heap usage leading to OOMs is a blocker.

Sounds good @snazy; please see #490 for a proposal on how we can limit the size of the EntityCache.


Create PROTOCOL.md

Draft the wire protocol spec for Twirp based on latest discussions. It reflects the existing Twirp wire spec, plus best practice from proto3, gRPC, HTTP, and JSON. The spec should be usable for developers to build clients and servers using Twirp wire protocol without much dependency.
Issue #, if available:
#71
Description of changes:
Write up the Twirp wire protocol.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Done.


Add helpers to assert a resource does not exist

There are some cases where we want to ensure a resource is not yet created by the operator (eg. No resources should be created in case the global secret does not exist). This adds the helper functions to assert that.
This also removes the unused AssertConfigMapExists. This function can be replaced by GetConfigMap.

this needs rebase after we fixed the circular dependency with https://github.com/openstack-k8s-operators/lib-common/pull/301

I've pushed https://github.com/openstack-k8s-operators/infra-operator/pull/86 to drop usage of AssertConfigMapExists from infra-operator(which can be merge independently)


reply to messge not working ? how to fix it  ?

reply to messge not working ? how to fix it  ?

WAPI.ReplyMessage(Store.Chat.models[0].msgs.models[Store.Chat.models[0].msgs.models.length - 1].id._serialized,'hi' ,{
linkPreview: null,
mentionedJidList: null,
quotedMsg: null,
quotedMsgAdminGroupJid: null
            } ) ;

it was working but now it doesnot working