allow-when-locked=false is being added to every bind

This may be user error, I'm setting this up for the first time.
It appears that allow-when-locked=false is being added to every keybind, and niri is complaining that this field may only be set on spawn binds.
Here are my binds:
      binds = {
        "Mod+Shift+Slash".action.show-hotkey-overlay = [];

        "Mod+Return".action.spawn = ["kitty"];
        "Mod+D".action.spawn = ["rofi" "-show" "run"];
        "Super+Alt+L".action.spawn = ["swaylock"];

	"XF86AudioRaiseVolume".action.spawn = ["wpctl" "set-volume" "@DEFAULT_AUDIO_SINK@" "0.1+"];
	"XF86AudioLowerVolume".action.spawn = ["wpctl" "set-volume" "@DEFAULT_AUDIO_SINK@" "0.1-"];

        "Mod+Q".action.close-window = [];

        "Mod+Left".action.focus-column-left = [];
        "Mod+H".action.focus-column-left = [];
        "Mod+Down".action.focus-window-down = [];
        "Mod+J".action.focus-window-down = [];
        "Mod+Up".action.focus-window-up = [];
        "Mod+K".action.focus-window-up = [];
        "Mod+Right".action.focus-column-right = [];
        "Mod+L".action.focus-column-right = [];

        "Mod+Ctrl+Left".action.move-column-left = [];
        "Mod+Ctrl+H".action.move-column-left = [];
        "Mod+Ctrl+Down".action.move-window-down = [];
        "Mod+Ctrl+J".action.move-window-down = [];
        "Mod+Ctrl+Up".action.move-window-up = [];
        "Mod+Ctrl+K".action.move-window-up = [];
        "Mod+Ctrl+Right".action.move-column-right = [];
        "Mod+Ctrl+L".action.move-column-right = [];

        "Mod+Home".action.focus-column-first = [];
        "Mod+End".action.focus-column-last = [];
        "Mod+Ctrl+Home".action.move-column-to-first = [];
        "Mod+Ctrl+End".action.move-column-to-last = [];

        "Mod+Shift+Left".action.focus-monitor-left = [];
        "Mod+Shift+H".action.focus-monitor-left = [];
        "Mod+Shift+Down".action.focus-monitor-down = [];
        "Mod+Shift+J".action.focus-monitor-down = [];
        "Mod+Shift+Up".action.focus-monitor-up = [];
        "Mod+Shift+K".action.focus-monitor-up = [];
        "Mod+Shift+Right".action.focus-monitor-right = [];
        "Mod+Shift+L".action.focus-monitor-right = [];

        "Mod+Shift+Ctrl+Left".action.move-column-to-monitor-left = [];
        "Mod+Shift+Ctrl+H".action.move-column-to-monitor-left = [];
        "Mod+Shift+Ctrl+Down".action.move-column-to-monitor-down = [];
        "Mod+Shift+Ctrl+J".action.move-column-to-monitor-down = [];
        "Mod+Shift+Ctrl+Up".action.move-column-to-monitor-up = [];
        "Mod+Shift+Ctrl+K".action.move-column-to-monitor-up = [];
        "Mod+Shift+Ctrl+Right".action.move-column-to-monitor-right = [];
        "Mod+Shift+Ctrl+L".action.move-column-to-monitor-right = [];

        "Mod+Page_Down".action.focus-workspace-down = [];
        "Mod+Page_Up".action.focus-workspace-up = [];
        "Mod+U".action.focus-workspace-down = [];
        "Mod+I".action.focus-workspace-up = [];
        "Mod+Ctrl+Page_Down".action.move-column-to-workspace-down = [];
        "Mod+Ctrl+Page_Up".action.move-column-to-workspace-up = [];
        "Mod+Ctrl+U".action.move-column-to-workspace-down = [];
        "Mod+Ctrl+I".action.move-column-to-workspace-up = [];

        "Mod+Shift+Page_Down".action.move-workspace-down = [];
        "Mod+Shift+Page_Up".action.move-workspace-up = [];
        "Mod+Shift+U".action.move-workspace-down = [];
        "Mod+Shift+I".action.move-workspace-up = [];

        "Mod+WheelScrollDown" = {
  	 cooldown-ms = 150;
  	 action.focus-workspace-down = [];
  	};
        "Mod+WheelScrollUp" = {
  	 cooldown-ms = 150;
  	 action.focus-workspace-up = [];
  	};
        "Mod+Ctrl+WheelScrollDown" = {
  	 cooldown-ms = 150;
  	 action.move-column-to-workspace-down = [];
  	};
        "Mod+Ctrl+WheelScrollUp" = {
  	 cooldown-ms = 150;
  	 action.move-column-to-workspace-up = [];
  	};

        "Mod+WheelScrollRight".action.focus-column-right = [];
        "Mod+WheelScrollLeft".action.focus-column-left = [];
        "Mod+Ctrl+WheelScrollRight".action.move-column-right = [];
        "Mod+Ctrl+WheelScrollLeft".action.move-column-left = [];

        "Mod+Shift+WheelScrollDown".action.focus-column-right = [];
        "Mod+Shift+WheelScrollUp".action.focus-column-left = [];
        "Mod+Ctrl+Shift+WheelScrollDown".action.move-column-right = [];
        "Mod+Ctrl+Shift+WheelScrollUp".action.move-column-left = [];

        #Mod+1 { focus-workspace 1; }
        #Mod+2 { focus-workspace 2; }
        #Mod+3 { focus-workspace 3; }
        #Mod+4 { focus-workspace 4; }
        #Mod+5 { focus-workspace 5; }
        #Mod+6 { focus-workspace 6; }
        #Mod+7 { focus-workspace 7; }
        #Mod+8 { focus-workspace 8; }
        #Mod+9 { focus-workspace 9; }
        #Mod+Ctrl+1 { move-column-to-workspace 1; }
        #Mod+Ctrl+2 { move-column-to-workspace 2; }
        #Mod+Ctrl+3 { move-column-to-workspace 3; }
        #Mod+Ctrl+4 { move-column-to-workspace 4; }
        #Mod+Ctrl+5 { move-column-to-workspace 5; }
        #Mod+Ctrl+6 { move-column-to-workspace 6; }
        #Mod+Ctrl+7 { move-column-to-workspace 7; }
        #Mod+Ctrl+8 { move-column-to-workspace 8; }
        #Mod+Ctrl+9 { move-column-to-workspace 9; }

        "Mod+Comma".action.consume-window-into-column = [];
        "Mod+Period".action.expel-window-from-column = [];

        "Mod+R".action.switch-preset-column-width = [];
        "Mod+F".action.maximize-column = [];
        "Mod+Shift+F".action.fullscreen-window = [];
        "Mod+C".action.center-column = [];

        "Mod+Minus".action.set-column-width = "-10%";
        "Mod+Equal".action.set-column-width = "+10%";

        "Mod+Shift+Minus".action.set-window-height = "-10%";
        "Mod+Shift+Equal".action.set-window-height = "+10%";

        "Mod+Space".action.switch-layout = "next";
        "Mod+Shift+Space".action.switch-layout = "prev";

        "Print".action.screenshot = [];
        "Ctrl+Print".action.screenshot-screen = [];
        "Alt+Print".action.screenshot-window = [];

        "Mod+Shift+E".action.quit = [];

        "Mod+Shift+P".action.power-off-monitors = [];
      };

Running home-manager switch gives me:
error: builder for '/nix/store/8hr5hmkm207jyh7zigpdhgr1hl9s1kzl-config.kdl.drv' failed with exit code 1;
       last 10 log lines:
       > Error: allow-when-locked can only be set on spawn binds
       >     Diagnostic severity: error
       >
       > Begin snippet for .attr-041r6j70w6v6dakqkzmwb899h71g2hibch7d14bbv9gy7bxhd5mp starting at line 133, column 1
       >
       > snippet line 133:     Mod+WheelScrollUp allow-when-locked=false cooldown-ms=150 { focus-workspace-up; }
       > snippet line 134:     Print allow-when-locked=false { screenshot; }
       >     label at line 134, columns 11 to 27: unexpected property
       > snippet line 135:     Super+Alt+L allow-when-locked=false { spawn "swaylock"; }
       >
       For full logs, run 'nix log /nix/store/8hr5hmkm207jyh7zigpdhgr1hl9s1kzl-config.kdl.drv'.
error: 1 dependencies of derivation '/nix/store/mr66jb6g3v8qp9bdmgsirzk38hzb988j-home-manager-files.drv' failed to build
error: 1 dependencies of derivation '/nix/store/5hv1da881bnmbxfh143ky5k7gvlvm5pa-home-manager-generation.drv' failed to build

And checking out the requested log file shows me many lines as above, one for each bind (not reproduced here due to length).
Again, this may be error on my end, but not sure what I could be doing wrong.

Ah, i'm so sorry! This is not your fault; sudden breakages like this should not happen without a warning ahead of time (i.e. i may make breaking changes; but i will first make the soon-to-be-broken configs emit errors for some arbitrary amount of time). This was not an intentional breakage; i just implemented allow-when-locked (and variable-refresh-rate!!!!) sloppily and incorrectly. I thought of the possibility of this happening and envisioned how i'd solve it and then i just... didn't. lmao.
Usually i test my config to ensure stuff works but somehow i thought these changes were too trivial to warrant that. Neither were caught by my automatic testing because it only tests an empty config; which crucially has no outputs or binds that can error.
The problem has been solved though, i just pushed a fix before writing this comment. Your system should build fine now. Again, sorry for the inconvenience, this was totally my fault and also unintentional.

Hey no problem at all! Thanks for the super speedy fix <3
-------- Original Message --------
On 4/20/24 4:10 PM, sodiboo  wrote:

Ah, i'm so sorry! This is not your fault; sudden breakages like this should not happen without a warning ahead of time (i.e. i may make breaking changes; but i will first make the soon-to-be-broken configs emit errors for some arbitrary amount of time). This was not an intentional breakage; i just implemented allow-when-locked (and variable-refresh-rate!!!!) sloppily and incorrectly. I thought of the possibility of this happening and envisioned how i'd solve it and then i just... didn't. lmao.
Usually i test my config to ensure stuff works but somehow i thought these changes were too trivial to warrant that. Neither were caught by my automatic testing because it only tests an empty config; which crucially has no outputs or binds that can error.
The problem has been solved though, i just pushed a fix before writing this comment. Your system should build fine now. Again, sorry for the inconvenience, this was totally my fault and also unintentional.
—
Reply to this email directly, view it on GitHub or unsubscribe.
You are receiving this email because you authored the thread.
Triage notifications on the go with GitHub Mobile for iOS or Android.

i just pushed a fix before writing this comment

Correction: It was not pushed because the branch had desynced due to automations, and i didn't even look at the output of git push lol. I fixed it before writing that, but didn't push it.
Now it's been fixed, though, in https://github.com/sodiboo/niri-flake/commit/430aced08164f1362d6fdc63a75d40c62e4ecc52

Yup, just watched it come in.  Confirmed working on my machine, thank you!


watchtower+refactor: CommitmentType and JusticeKit interface

This PR is a pure refactor of some watchtower code. Currently,  the
tower code is littered with many if isAnchor() {..} else {} blocks
and this will become even more hairy once we have to cater for
taproot channels. With that in mind, this PR does a few things so that
adding support for taproot channels can be a relatively small diff:

A new CommitmentType enum is added which will hide some details
about the inputs of the justice transaction.
The JusticeKit is converted from a struct to an interface with various
methods on it. Two implementations are added: legacyJusticeKit and
anchorJusticeKit both of which use the same encoding.

This is a pre-requisite for https://github.com/lightningnetwork/lnd/pull/7733

@bitromortac: review reminder

@bitromortac: review reminder

pushed a tiny update here to incorporate this comment from the follow up PR.
No logic changes - just changing the JusticeKit API to return types like txscript.PkScript and wire.TxWitness instead of []byte and [][]byte


Run more integration tests on Windows.

Summary
Enables some integration tests that can run on Windows without any changes.

Test plan
Nothing should change.  AppVeyor should report 81 tests being skipped instead of 112.

oh yayy!


os: add ModeIrregular flag

The os.FileInfo type is an interface, allowing other packages to implement it. One of the fields it returns is Mode which reports two pieces of information: 1) what the permissions are, and 2) what type of file it is. There is a helper method os.FileMode.IsRegular that reports whether the file is regular or not. Currently the only way to have IsRegular report false is to set the type to be one of the following:

ModeDir | ModeSymlink | ModeNamedPipe | ModeSocket | ModeDevice

For some implementations of os.FileInfo (see #22903 for an example), we want to be able to indicate that the file is not regular. However, every one of the aforementioned types to indicate non-regular are ill-suited as a general-purpose "unknown" file type.
Thus, I propose adding a ModeUnknown to serve exactly for that purpose. The ModeUnknown type carries no information other than the fact that the file is not regular.
CL/94856 is one such implementation.
\cc @bradfitz @ianlancetaylor @robpike @rsc

"Unknown" sounds like not knowing anything. We know it's not regular.
ModeOther? ModeIrregular? ModeSpecial?

Does sound worth doing though, modulo the name.

ModeIrregular SGTM. The name exactly reflects what it means.

Was reverted. Reopening.

We ended up rolling forward with a fix in: https://go-review.googlesource.com/103616
So the revert didn't happen.

Ah, whoops. Great. I approved the API change (+ saw the revert CL created) but I missed that the revert was abandoned.


A clean test app won't launch due to LwjglGraphics.createDisplayPixelFormat error

I just installed created a fresh libgdx application via the generator found on the official web site. I left practically all things at default. Once generated, I imported the project in eclipse using Gradle (as explained in the official procedure). Upon trying to launch my application on desktop, I get the following error:
Exception in thread "LWJGL Application" java.lang.NullPointerException
at com.badlogic.gdx.backends.lwjgl.LwjglGraphics.createDisplayPixelFormat(LwjglGraphics.java:322)
at com.badlogic.gdx.backends.lwjgl.LwjglGraphics.setupDisplay(LwjglGraphics.java:216)
at com.badlogic.gdx.backends.lwjgl.LwjglApplication.mainLoop(LwjglApplication.java:142)
at com.badlogic.gdx.backends.lwjgl.LwjglApplication$1.run(LwjglApplication.java:124)
Under "Project and External Dependencies" I can see it links to libgdx 1.9.4 and lwjgl 2.9.2 (by the way, why isn't libgdx using lwjgl 2.9.3, which is the latest version?) and some other non-important stuff.
Note that this is a fresh project generated by the "Libgdx Project Generator" - I haven't modified a thing!
I'm running Windows 10 on HP Elitebook 8560p (it's a laptop) and it has Intel HD Graphics 3000 (which is Microsoft DirectX 10.1 (Shader Model 4.1) and OpenGL 3.0 capable).
If you require any more info, please tell.

OK, I solved the problem - I had install JDK 1.8.0_51 and link my Eclipse's run configuration to it. The problem is whit Intel HD 3000 graphic card which doesn't support Windows 10. Hence a need to revert Java because in version 8u51 (and earlier) it didn't support Windows 10 yet.
However, this is a known issue it seems - I've read about it on Minecraft forums, LWJGL forums, and others.


Default mode is impossible to use with a TouchPad in v1.6.2

Using macOS, the automatic detection of TouchPads breaks the default mode. I cannot simply zoom like I would in default Foundry because it also pans the canvas slightly and erratically switches between both modes. I attached a video where I simply tried to zoom out using the TouchPad in default mode. A Magic Mouse works slightly better, but has the same issue.
I’m not sure what the use case for that auto detection is, but on a mac, a setting to make that optional would be needed because otherwise the default mode is unusable.
Setup:
OS: macOS 14.1.1
Browser: Chrome
Foundry: v0.8.8
Zoom/Pan Options: 1.6.2
https://user-images.githubusercontent.com/40534855/124613088-2c411480-de73-11eb-901d-f2c13d4d6c7a.mov

Well drat, I guess I'll have to put the auto-detection behind a setting configuration after all.

@mrkwnzl Thanks for the speedy and detailed bug report.  I added another method of touchpad detection which was verified to work on my MacBook, and also added a "Default Mouse" setting in case it still causes issues.
Please update me on whether or not this new version works for you!

Hey! Sorry for the late response, my work was hectic last week. I can confirm that 1.6.5 works great. The auto detection fails occasionally, but not in a way that would disrupt the game too much. But the default mouse and touchpad modes work flawlessly. Thanks!


High CPU consumption due to frequently Garbage Collect (GC)

Description
Hi,
Recently I've been troubled by the issue of high CPU consumption of Gitea. The CPU consumption often become very high after running about 10 hours, and restart gitea can temporally solve this problem.

The most suspicious behavior of gitea during high CPU consumption is frequent GC. I have taken a screen record when cpu consumption becomes high.
https://github.com/user-attachments/assets/da2e4e8a-bf8c-468d-8a60-8f7b8a6dfaa4
After restarting Gitea, GC seems "calm down".

Here is the log of gitea (Though I can't find any related information.)
2024/09/02 05:06:14 ...s/setting/session.go:77:loadSessionFrom() [I] Session Service Enabled
2024/09/02 05:06:14 ...s/storage/storage.go:176:initAttachments() [I] Initialising Attachment storage with type: local
2024/09/02 05:06:14 ...les/storage/local.go:33:NewLocalStorage() [I] Creating new Local Storage at /var/lib/gitea/data/attachments
2024/09/02 05:06:14 ...s/storage/storage.go:166:initAvatars() [I] Initialising Avatar storage with type: local
2024/09/02 05:06:14 ...les/storage/local.go:33:NewLocalStorage() [I] Creating new Local Storage at /var/lib/gitea/data/avatars
2024/09/02 05:06:14 ...s/storage/storage.go:192:initRepoAvatars() [I] Initialising Repository Avatar storage with type: local
2024/09/02 05:06:14 ...les/storage/local.go:33:NewLocalStorage() [I] Creating new Local Storage at /var/lib/gitea/data/repo-avatars
2024/09/02 05:06:14 ...s/storage/storage.go:186:initLFS() [I] Initialising LFS storage with type: local
2024/09/02 05:06:14 ...les/storage/local.go:33:NewLocalStorage() [I] Creating new Local Storage at /var/lib/gitea/data/lfs
2024/09/02 05:06:14 ...s/storage/storage.go:198:initRepoArchives() [I] Initialising Repository Archive storage with type: local
2024/09/02 05:06:14 ...les/storage/local.go:33:NewLocalStorage() [I] Creating new Local Storage at /var/lib/gitea/data/repo-archive
2024/09/02 05:06:14 ...s/storage/storage.go:208:initPackages() [I] Initialising Packages storage with type: local
2024/09/02 05:06:14 ...les/storage/local.go:33:NewLocalStorage() [I] Creating new Local Storage at /var/lib/gitea/data/packages
2024/09/02 05:06:14 ...s/storage/storage.go:219:initActions() [I] Initialising Actions storage with type: local
2024/09/02 05:06:14 ...les/storage/local.go:33:NewLocalStorage() [I] Creating new Local Storage at /var/lib/gitea/data/actions_log
2024/09/02 05:06:14 ...s/storage/storage.go:223:initActions() [I] Initialising ActionsArtifacts storage with type: local
2024/09/02 05:06:14 ...les/storage/local.go:33:NewLocalStorage() [I] Creating new Local Storage at /var/lib/gitea/data/actions_artifacts
2024/09/02 05:06:14 routers/init.go:138:InitWebInstalled() [I] SQLite3 support is enabled
2024/09/02 05:06:14 routers/common/db.go:23:InitDBEngine() [I] Beginning ORM engine initialization.
2024/09/02 05:06:14 routers/common/db.go:30:InitDBEngine() [I] ORM engine initialization attempt #1/10...
2024/09/02 05:06:14 cmd/web.go:194:serveInstalled() [I] PING DATABASE mysql
2024/09/02 05:06:14 ...dels/db/collation.go:184:preprocessDatabaseCollation() [W] Current database is using a case-insensitive collation "utf8mb4_unicode_ci", although Gitea could work with it, there might be some rare cases which don't work as expected.
2024/09/02 05:06:14 ...dels/db/collation.go:188:preprocessDatabaseCollation() [E] There are 278 table columns using inconsistent collation, they should use "utf8mb4_unicode_ci". Please go to admin panel Self Check page
2024/09/02 05:06:14 cmd/web.go:194:serveInstalled() [W] Table system_setting Column version db default is , struct default is 1
2024/09/02 05:06:14 cmd/web.go:194:serveInstalled() [W] Table gpg_key_import Column content db nullable is true, struct nullable is false
2024/09/02 05:06:14 cmd/web.go:194:serveInstalled() [W] Table project column board_type db type is INT(10) UNSIGNED, struct type is INT UNSIGNED
2024/09/02 05:06:14 cmd/web.go:194:serveInstalled() [W] Table project column card_type db type is INT(11), struct type is INT UNSIGNED
2024/09/02 05:06:14 cmd/web.go:194:serveInstalled() [W] Table project Column card_type db default is 0, struct default is
2024/09/02 05:06:14 cmd/web.go:194:serveInstalled() [W] Table project Column card_type db nullable is false, struct nullable is true
2024/09/02 05:06:14 cmd/web.go:194:serveInstalled() [W] Table project column type db type is INT(10) UNSIGNED, struct type is INT UNSIGNED
2024/09/02 05:06:14 cmd/web.go:194:serveInstalled() [W] Table review_state Column commit_sha db nullable is true, struct nullable is false
2024/09/02 05:06:15 cmd/web.go:194:serveInstalled() [W] Table label Column archived_unix db default is , struct default is NULL
2024/09/02 05:06:15 routers/init.go:144:InitWebInstalled() [I] ORM engine initialization successful!
2024/09/02 05:06:15 ...er/issues/indexer.go:76:func1() [I] PID 1132: Initializing Issue Indexer: bleve
2024/09/02 05:06:15 ...xer/stats/indexer.go:41:populateRepoIndexer() [I] Populating the repo stats indexer with existing repositories
2024/09/02 05:06:15 ...xer/stats/indexer.go:87:populateRepoIndexer() [I] Done (re)populating the repo stats indexer with existing repositories
2024/09/02 05:06:15 ...er/issues/indexer.go:153:func2() [I] Issue Indexer Initialization took 1.682015ms
2024/09/02 05:06:15 ...s/actions/cleanup.go:36:cleanExpiredArtifacts() [I] Found 0 expired artifacts
2024/09/02 05:06:15 ...s/actions/cleanup.go:60:cleanNeedDeleteArtifacts() [I] Found 0 artifacts pending deletion
2024/09/02 05:06:15 cmd/web.go:304:listen() [I] Listen: http://<IP_ADDRESS>:3000
2024/09/02 05:06:15 cmd/web.go:308:listen() [I] AppURL(ROOT_URL): http://gitea.syize.cn/
2024/09/02 05:06:15 cmd/web.go:311:listen() [I] LFS server enabled
2024/09/02 05:06:15 ...s/graceful/server.go:50:NewServer() [I] Starting new Web server: tcp:<IP_ADDRESS>:3000 on PID: 1132

Gitea Version
1.22.1
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
No response
Git Version
2.46.0
Operating System
Arch Linux
How are you running Gitea?
I install the latest gitea from Arch Linux repo
pacman -Qi gitea

Name            : gitea
Version         : 1.22.1-1
Description     : Painless self-hosted Git service, community managed.
Architecture    : x86_64
URL             : https://gitea.io
Licenses        : MIT
Groups          : None
Provides        : None
Depends On      : git
Optional Deps   : mariadb: MariaDB support [installed]
                  memcached: MemCached support
                  openssh: GIT over SSH support [installed]
                  pam: Authentication via PAM support [installed]
                  postgresql: PostgreSQL support
                  redis: Redis support
                  sqlite: SQLite support [installed]
Required By     : None
Optional For    : None
Conflicts With  : None
Replaces        : None
Installed Size  : 101.67 MiB
Packager        : Robin Candau<EMAIL_ADDRESS>Build Date      : 2024年08月04日 星期日 16时13分12秒
Install Date    : 2024年08月05日 星期一 11时16分13秒
Install Reason  : Explicitly installed
Install Script  : No
Validated By    : Signature

and make it a system service by using systemd
sudo systemctl status gitea.service

● gitea.service - Gitea (Git with a cup of tea)
     Loaded: loaded (/usr/lib/systemd/system/gitea.service; enabled; preset: disabled)
     Active: active (running) since Mon 2024-09-02 16:14:55 CST; 51min ago
 Invocation: 0b2f0c623432438cbb02ae9595534496
   Main PID: 108749 (gitea)
      Tasks: 25 (limit: 38295)
     Memory: 173.8M (peak: 175.5M)
        CPU: 3.414s
     CGroup: /system.slice/gitea.service
             └─108749 /usr/bin/gitea web -c /etc/gitea/app.ini

Database
MySQL/MariaDB

Could be be the bleve indexer, see https://github.com/go-gitea/gitea/issues/31565 and try disabling it via  REPO_INDEXER_ENABLED = false.

set REPO_INDEXER_ENABLED = false doesn't help.

set REPO_INDEXER_ENABLED = false doesn't help.

I set REPO_INDEXER_ENABLED = false and observed Gitea for a few days. This issue won't happen even Gitea has run 1-2 days, but it happens after system reboot, and the change of system time seems to be one of the causes triggering this problem.
Sometimes I switch to Windows to play games and then switch back to Arch Linux. Because of the different ways Windows and Linux handle the hardware clock (its a normal issue), the system time in Linux is 8 hours ahead(because I'm in UTC+8 timezone), and Linux will update system time as soon as it connect to Internet. I found this issue occurs immediately after system time update. Restart gitea manually could calm Gitea down.
As for Gitea's log, I have changed log level to trace, but Gitea doesn't output any additional information in log/gitea.log.


Proposal: Functions that belong to a structure

We were going to use impl, like Rust:
struct whatever {
    int x;
};

impl whatever {
    fn construct(whatever 'self) {
        self.x = 5;
    }
}

However, I've been looking at go recently, and I like how they do it:
// struct called Whatever
// i could be wrong with this since I haven't written any Go before
func (w Whatever) thingy(name string) {
    w.name = name
}

So perhaps we could define what struct the function belongs to, a syntax idea of mine:
struct person {
    int age;
    string name;
};

// some syntax ideas
fn (person p) set_name(string name): void {
    p.name = name;
}

fn [person p] set_name(string name): void {
    p.name = name;
}

// this ones kinda weird
fn set_name(string name): void {|person p|
    p.name = name;
}

fn set_name[Person p](string name): void {
    p.name = name;
}

// Perhaps just having [Person] is shorthand for [Person self]
fn set_name[Person](string name): void {
    self.name = name;
}

How about:
Assuming we have a structure named person with an instance person1:
fn<person1> set_name (str name): void {
    // do some shit
}

@CaptainChloride So you have to have an instance of the struct created? That could be irritating, with an actual function call it could be [assuming we have the other syntax]:
Person p = {
....
};
p.set_name("whatever");

We could just have some weird syntax like:
fn person@set_name(str name): void {

}

Oh wait I may have a cooler idea:
Again, assuming the struct is already created (this is a pretty decent way to go about it imo):
of person fn set_name(str name): void {
    // do something
}

We could use the of keyword. Looks nicer and is something different too...

So yes, the person would have to put the functions he's associating with the structure within the structure itself, and then use the of keyword to refer to that structure's function and implement it.

@CaptainChloride I.e?

Ok here's a sample:
struct Person {
    str nam;
    int age;
    fn set_name(str name); // thinking whether or not to mention the return type here...
};

Person person;

of person fn set_name(str name): void {
    // do something
}

@CaptainChloride I don't think you'd store the function in a struct unless it was a function pointer.

It makes sense if we want like a function that's relative to a particular structure.

@CaptainChloride What makes sense? Also of makes it too verbose imo.

Let's say we want a function that should belong only and only to Person. Then upon instantiating the structure, (creating the instance person of structure Person), we can use the of thing to define the function for that instance of Person only.

@CaptainChloride That's weird. lol, and I don't think of can apply to all functions, it might not make sense in some cases.

No not all functions, just the ones that belong to a structure.

Well yeah but with something like:
fn set_name(str name) of player: void {

}
called like
set_name(whatever).player_instance;

So you would need the instance to call the function.

Ok so here's a normal function (not belonging to a structure):
fn set_name ( str name ): void {
    // bleh
}

And here's a function belonging to  a structure (assuming an instance of that structure called instance):
of instance fn set_name ( str name ): void {
    // bleh instance
}

@CaptainChloride Called how? All I'm saying is how would you access values in the struct???

Oh lol

See we used to have (instance i) so you would access with i. With just instance, what do you do?

And having of after the function name would read better, imo. Like do_something of name. But of doesn't apply to all function names. For example, fn run_game() of game: void { } wont make much sense.

That instance would be of a structure right? So, say instance has a variable that is a string called nam
To change the value of nam from set_name (which belongs to the structure):
of instance set_name (str name): void {
    instance.nam = name;
}

And another instance instance2 will be
of instance2 set_name (str name): void {
    instance2.nam = name;
}

@CaptainChloride So are you implying instance and instance2 are structs, or if they are just names?

Or we could just say nam = name since we've already mentioned that we're working with instance2

@CaptainChloride is nam a typo?

Instance and instance2 are two instances of the structure Person, yes.

Nam is a string present in the structure Person

That's weird because then we're inferring the structures type. And nam is ugly, you shouldn't have to change the name in the struct to access it with a similar name.

struct Whatever {
    str name;
};

fn set_name(str name) of Whatever: void {
    self.name = name;
}

fn main(): void {
    Whatever whatever;
    set_name("idk") of whatever;
    // or
    set_name("idk")->whatever; /// etc
}

I prefer this:
struct Whatever {
    str name;
};
fn Whatever@set_name(str name): void {
    // i also don't mind "this" in replace of "self"
    self.name = name;
}
fn main(): void {
    Whatever whatever;
    whatever->set_name("thing");
}

I am writing a full code snippet try to infer what my point is oke?
structure Person {
    str nam;
    int age;
    fn set_name(str name);
}

Person instance, instance2;

of instance fn set_name(str name): void {
    nam = name;
}

of instance2 fn set_name(str name): void {
    nam = name; // not using instance2.nam since we can infer that from the of instance2 thing
}

Or we could call the function like:
instance.set_name("scrub");

In which case, inside the structure definition we can mention return type
struct Person {
    str nam;
    int age;
    fn set_name(str name): void -> nam = name; // we call these short functions maybe
}

Hey short functions, new idea yeeee

Short functions are already implemented as:
fn add(int a, int b): int => return a + b;

@CaptainChloride Basically, what I'm getting at is:

Functions stored in a struct makes no sense
of xyz looks too verbose and isn't very clean, the keyword of also doesn't work in some cases.

If we're doing normal instantiating of a function we might as well use
struct Whatever {
    str name;
}

Whatever e;
fn set_name(str s): void {
    e.name = name;
}

Why can't we just do this?

@CaptainChloride You can do that yes, but I wanted a cleaner implementation of an OOP like system. Where functions can only work with structs. And you *don't have global instances of the structs, and you don't have to pass the struct to the function like C.

Something like wanting a default value for every instance of the structure?

Well, we can either do it like Rust, having an implementation wrapper over a struct, but I was looking at Go and I like the way that they do it.

So like every time you create an instance and call the function, it creates a default value?

You can create a struct, and again I'm unsure of the syntax (hence this proposal), you can just access the function like this my_struct.function(). As opposed to C style, function(my_struct).

Also, you can't just call a function that belongs to a struct or a "class".

Yeah I'm on now

Too late, I gotta go. Ciao

kkkkkk

On irc again now

I'd like to note a few things. A lot of what @CaptainChloride was trying to propose, it seems, actually has to do with overriding methods, and not methods themselves (which this proposal is about). I actually think this has gotten quite out of hand and very hard to follow.
@freefouran, you keep mentioning something along the lines of not being about to "call a function that belongs to a struct," but I don't know what you're trying to say. Are you saying you don't want to support static methods or just that they don't yet exist?

@ianhedoesit that's what I was trying to explain to @CaptainChloride is that a lot of his ideas made no sense to me. Oh and the point I was getting across is that if you have a method like add(int a, int b) for example, you can't just call add(5, 5), without an instance of it's owner.

Why not use angle brackets here. Seems like a nicer touch...
struct Car {
    str name
}

fn <Car 'c> set_name(str name): void {
    c.name = name
}

fn main(): int {
    Car 'c = alloc...
    c.set_name("Le")
    return 0
}

Besides it may be easier to detect (probably wrong here but yeah)

@CaptainChloride It wouldn't make a difference for parsing/lexing it I wouldn't think. Perhaps, it may be a little bit cleaner so you can easily disambiguate the function parameters and it's owners by looking at the prototype. But I don't think it would make much difference.


Adds reading room request modal and handlers

Like the other modals, this doesn't fully work without the request broker yet, but there should be enough here to see what's going on.
Fixes #70

I'm looking at this now, and one thing I wanted to flag was that element ids can't have whitespace, so our input ids and associated labels aren't functioning properly where they're pulling in the item titles.

@HaSistrunk can you point me at an instance of this?

@HaSistrunk can you point me at an instance of this?

For example for the ModalSavedItem, it's using {title} for the id and label:
const ModalSavedItem = ({ title }) => (

      <CheckBoxInput
        className="checkbox--orange"
        id={title}
        checked={true}
        label={title} />

)

Since {title} is pulling from the data fetched in the PageMyList component, these have whitespace. So when I inspect the page I see something like this:

    <input type="checkbox" id="Meade Alcorn Interview" name="Meade Alcorn Interview" checked="">
    Meade Alcorn Interview

@HaSistrunk got it! Let me fix that.

Ok, just a few things:

I added an aria-describedby to connect the input and the help text in the forms.
This is my fault from a previous PR I think, but our headings are a little funky because our item group title needs to be an h2 on the My List page, and an h3 in the modal (since the modal title is an h2). I made a change for that.
I can't get the date picker to open with the keyboard

@HaSistrunk Thanks for these edits. I've added an issue to track the last thing you raise (accessibility of date inputs), as there doesn't appear to be an easy fix for this (or even consensus on what the problem is).


Update README.md

Description

Updated README.md for better readability of users.
Formatted lines of README.
Shorten the README,  so that users can interact with it for longer periods of time.
Added contributors section.
Highlighted important text.

Related issues #4865

Related PRs #4866

Screenshots

Link to the automatically generated build APK

@VaiTon I have made the changes. Kindly look into them.

Hey @utkarsh006, I left another comment

Hey @utkarsh006, I left another comment

Should I leave contributors section as it was earlier?

@VaiTon I have done the changes told by you. Do Review.

@utkarsh006 you can also add the contributors, I just commented about the original author being out of the contributors section

@utkarsh006 you can also add the contributors, I just commented about the original author being out of the contributors section

Finally done all the tasks. Hope, PR gets merged.

@teolemon Kindly review my PR.


Rebuild 5.20 for cpptango 9.5

Checklist

[X] Used a personal fork of the feedstock to propose changes
[X] Bumped the build number (if the version is unchanged)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[X] Ensured the license file is being packaged.

As there are some issue with latest version of TangoDatabase, I want to build 5.20 with cpptango 9.5, so we can keep using that version.

Last 5.20 build was 1, hence build number 2.
There was no windows build for 5.20. Keep it like that.
Used latest FindMySQL.cmake file from TangoCMakeModules as I had issue find mysql.

@conda-forge-admin, please rerender


server panics when restarting after stopped for a few hours

A 3 nodes cluster, stop a node for a few hours then restart. It panics with following log:
29048 2016-08-25 14:07:35,936 raft.rs:582 - INFO  - [region 15540] 15541 became follower at term 66
29049 2016-08-25 14:07:35,936 raft.rs:735 - INFO  - [region 2776] 2777 [term: 15] received a MsgHeartbeat message with higher term fr      om 2779 [term: 69]
29050 2016-08-25 14:07:35,936 raft.rs:582 - INFO  - [region 2776] 2777 became follower at term 69
29051 2016-08-25 14:07:36,250 snap.rs:199 - ERROR - failed to apply snap: Other(StringError("missing snap file /data/test/dianle/data/tikv1/snap/rev_5876_7_2263.snap"))!!!
29052 2016-08-25 14:07:36,250 mod.rs:51 - WARN  - handle task Snap apply for 5876 [takes Duration { secs: 1, nanos: 129691607}]
29053 2016-08-25 14:07:36,274 endpoint.rs:176 - ERROR - failed to get snapshot: Request(message: "peer is not leader" not_leader {region_id: 3004 leader {id: 3007 store_id: 6}})
29054 2016-08-25 14:07:36,274 endpoint.rs:176 - ERROR - failed to get snapshot: Request(message: "peer is not leader" not_leader {region_id: 3016 leader {id: 3019 store_id: 6}})
29055 thread 'raftstore-1' panicked at 'applying snapshot to 5876 failed', src/raftstore/store/store.rs:1199
29056 stack backtrace:
29057    1:     0x7fa3e112ef8d - std::sys::backtrace::tracing::imp::write::h29f5fdb9fc0a7395
29058    2:     0x7fa3e1134fe1 - std::panicking::default_hook::_{{closure}}::h2cc84f0378700526
29059    3:     0x7fa3e1133f59 - std::panicking::default_hook::hbbe7fa36a995aca0
29060    4:     0x7fa3e0e7a670 - tikv::util::panic_hook::set_exit_hook::_{{closure}}::hf7e56c7db7debd8a
29061                         at /home/pingcap/src/github.com/pingcap/tikv/src/util/panic_hook.rs:68
29062    5:     0x7fa3e1134597 - std::panicking::rust_panic_with_hook::h105c3d42fcd2fb5e
29063    6:     0x7fa3e1134482 - std::panicking::begin_panic::hbf62ea4a5ff3f9de
29064    7:     0x7fa3e11343b0 - std::panicking::begin_panic_fmt::h20f5943904e5791d
29065    8:     0x7fa3e0d07309 - _<tikv..raftstore..store..store..Store<T, C> as mio..handler..Handler>::notify::hbbedf1c7212e20ed
29066                         at /home/pingcap/src/github.com/pingcap/tikv/src/raftstore/store/store.rs:8
29067                         at /home/pingcap/src/github.com/pingcap/tikv/src/raftstore/store/store.rs:1266
29068    9:     0x7fa3e0ceffb0 - _<tikv..raftstore..store..store..Store<T, C>>::run::h07e797b034747ed5
29069                         at /home/pingcap/.cargo/git/checkouts/mio-e79f285e2377d154/master/src/event_loop.rs:366
29070                         at /home/pingcap/.cargo/git/checkouts/mio-e79f285e2377d154/master/src/event_loop.rs:313
29071                         at /home/pingcap/.cargo/git/checkouts/mio-e79f285e2377d154/master/src/event_loop.rs:261
29072                         at /home/pingcap/src/github.com/pingcap/tikv/src/raftstore/store/store.rs:217
29073   10:     0x7fa3e0c66a70 - std::panicking::try::call::hb22bd3c1347e6e52
29074                         at /buildslave/rust-buildbot/slave/nightly-dist-rustc-linux/build/obj/../src/libstd/panic.rs:256
29075                         at /buildslave/rust-buildbot/slave/nightly-dist-rustc-linux/build/obj/../src/libstd/panicking.rs:282
29076   11:     0x7fa3e113cae6 - __rust_maybe_catch_panic
29077   12:     0x7fa3e0cd0f97 - _<F as alloc..boxed..FnBox<A>>::call_box::h23f612000242526e
29078                         at /buildslave/rust-buildbot/slave/nightly-dist-rustc-linux/build/obj/../src/libstd/thread/local.rs:245
29079                         at /buildslave/rust-buildbot/slave/nightly-dist-rustc-linux/build/obj/../src/libstd/panicking.rs:245
29080                         at /buildslave/rust-buildbot/slave/nightly-dist-rustc-linux/build/obj/../src/libstd/panic.rs:312
29081                         at /buildslave/rust-buildbot/slave/nightly-dist-rustc-linux/build/obj/../src/liballoc/boxed.rs:587
29082   13:     0x7fa3e11328b2 - std::sys::thread::Thread::new::thread_start::h8f3bd45211e9f5ea
29083   14:     0x7fa3df888183 - start_thread
29084   15:     0x7fa3e00a237c - clone
29085   16:                0x0 - <unknown>

Hi @hhkbp2, Please help @BusyJay  to solve it.

Still have no clue after tracking the handling of the Applying State and snapshot GC and its conditions(truncated index, etc) in the source code. They looks quite solid and there is no timing issue.

we should think how to recover from this panic too.

I think Should add more tests for snapshot applying.
If we really meet this bug (region is applying but snapshot file is missing), how can we recover from it? We can't panic after restart.
Maybe we can remove all region data, but this may cause another panic later in raft heartbeat, because the leader may keep a matched index and will send it in heartbeat, but now we have nothing, so a panic will happen in raft log commit_to.

Any update?

Seem no update.


you have not selected a backup format

hi,
when trying to download it tells me:
you have not selected a backup format
Have you fixed this or please?

Hello 👋
What do you mean by "backup format"? There's no such thing. If it's about the filename, you indeed need to set one up before using the program. Maybe you might want to check the docs to get an idea on how to get started?
https://www.bionus.org/imgbrd-grabber/docs/

hello,
Well I had to reinstall grabber because it didn't recognize the name of the file %md5%.%ext%
THANKS


call recording doc updates

@dbasantes
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off
From: Courtney Wales @.>
Sent: Monday, June 12, 2023 8:24 AM
To: MicrosoftDocs/azure-docs @.>
Cc: Diego Basantes @.>; Mention @.>
Subject: Re: [MicrosoftDocs/azure-docs] call recording doc updates (PR #110734)
@dbasanteshttps://github.com/dbasantes
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-teamhttps://github.com/orgs/MicrosoftDocs/teams/public-repo-pr-review-team

Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/pull/110734#issuecomment-1587564054, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AW56ETP2NQJPGL5OGNTR3F3XK4YA5ANCNFSM6AAAAAAZCGDQ5M.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

#sign -off
From: Courtney Wales @.>
Sent: Monday, June 12, 2023 8:24 AM
To: MicrosoftDocs/azure-docs @.>
Cc: Diego Basantes @.>; Mention @.>
Subject: Re: [MicrosoftDocs/azure-docs] call recording doc updates (PR #110734)
@dbasanteshttps://github.com/dbasantes
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-teamhttps://github.com/orgs/MicrosoftDocs/teams/public-repo-pr-review-team

Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/pull/110734#issuecomment-1587564054, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AW56ETP2NQJPGL5OGNTR3F3XK4YA5ANCNFSM6AAAAAAZCGDQ5M.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>


improve protocol

there are two communication channels:
client <-> server
worker <-> server

each has a subset of commands, and upgrading one protocol shouldn't effect the other (mainly: when client <-> server gets new commands, the old worker should still be able to communicate with the server.
@reynir had the idea there could be separate client hello (one for client, one for worker). this would indeed solve the issue :)

addressed in 5d4292f


Vue-Tilt.js Error

I am trying to add this plugin Vue-Tilt.js to my project, which works fine on development, but when I try to do gridsome build I get this error:
workspace/gridsome/node_modules/vue-tilt.js/src/index.js:12
import VanillaTilt from 'vanilla-tilt';
^^^^^^^^^^^
SyntaxError: Unexpected identifier
at new Script (vm.js:74:7)
at createScript (vm.js:246:10)
at Object.runInThisContext (vm.js:298:10)
at Module._compile (internal/modules/cjs/loader.js:670:28)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:713:10)
at Module.load (internal/modules/cjs/loader.js:612:32)
at tryModuleLoad (internal/modules/cjs/loader.js:551:12)
at Function.Module._load (internal/modules/cjs/loader.js:543:3)
at Module.require (internal/modules/cjs/loader.js:650:17)
at require (internal/modules/cjs/helpers.js:20:18)
I tried implementing a "fix" I saw in another thread:
api.chainWebpack((config, { isServer }) => {
if (isServer) {
config.externals([
nodeExternals({
whitelist: [/^vue-tilt/]
})
])
}
})
which moved me to another error within the same plugin:
eferenceError: window is not defined
at assets/js/app.d19e96e2.js:939:3
at Object. (node_modules/vue-tilt.js/src/_polyfills.js:18:1)
at webpack_require (webpack/bootstrap:25:0)
at Module.module.exports.CustomEvent (node_modules/vue-tilt.js/src/index.js:9:0)
at webpack_require (webpack/bootstrap:25:0)
at Object. (src/main.js:5:0)
at webpack_require (webpack/bootstrap:25:0)
at Object. (node_modules/gridsome/app/main.js:4:9)
at webpack_require (webpack/bootstrap:25:0)
at Object. (node_modules/gridsome/app/app.js:3:0)
Here is how i have the plugin setup:
import DefaultLayout from '~/layouts/Default.vue'
import VueTilt from 'vue-tilt.js'
export default function (Vue, {router, head, isClient}) {
// Set default layout as a global component
Vue.component('Layout', DefaultLayout)
Vue.use(VueTilt)
}
Let me know if you have any solution for this kind of errors, thanks!!

Hi @vdiaza , the problem is that the plugin is not SSR compatible. You could try to run it inside a <client-only> tag?

@tomtev the problem is that i am not sure how to incorporate it into the project, since if I use Vue.use(VueTilt) it gives me an error.
I tried incorporating it into a component as gridsome explained for non SSR plugins like this:
  VueTilt: () =>        import ('vue-tilt.js')       .then( m => m.VueTilt )       .catch()
but the problem is that the plugin is used as a directive, not a component. So I think this is not the proper way to include it into the project.

Hey @vdiaza, I just had a similar issue with vue-scrollama as it requires the window object to be available.
The issue could possibly be that you're not importing the default export. This might need to be added to the docs too. But try this...
VueTilt: () => import ('vue-tilt.js') .then( m => m.default ) .catch()

@tomtev the examples in the docs show:
Carousel: () =>
        import ('vue-carousel')
        .then(m => m.Carousel)
        .catch(),

Is there a reason it points to m.Carousel? Thoughts on changing this to m.default? This worked for me and I think it's correct as node modules usually have a default prop for exports but I'm not 100% certain. I'm happy to do a PR though if we think it's correct.

but the problem is that the plugin is used as a directive, not a component. So I think this is not the proper way to include it into the project.

I find workaround with VanillaTilt.
First add VanillaTilt
npm install vanilla-tilt
In your component put to mounted hook
window.VanillaTilt = require('vanilla-tilt');
VanillaTilt.init(this.$refs.tilt);

and finally put ref="tilt" on element you want to tilt

@tomtev please see question from @gilesbutler above, and imo this issue can be closed when that's addressed.

@gilesbutler The example in the docs points to m.Carousel and m.Slide because the default export from vue-carousel is an installer object which should be passed to Vue.use(). But usually, m.default is the actual component.

Nice one, thanks for clarifying @hjvedvik 👍


Slow workload creation with VPA addon enabled.

Description
When using the VPA addon in the aws-ia/terraform-aws-eks-blueprints-addons module, workload creation is significantly slower than expected. This can impact the overall deployment time and user experience. Creation of Deployment or Statefulsets are taking > ~30s for the workload to be available in the API server (pod in pending state).
Reproduction:

Configure your AWS credentials and other necessary environment variables.
Enable the the VPA addon in the desired namespace.
Run terraform init and terraform apply to deploy the EKS cluster with VPA enabled.
Observe the time it takes for workloads to be created.

Expected behavior: Workloads should be created within a reasonable timeframe, similar to deployments without VPA.
Actual behavior: Workload creation is taking significantly longer than expected, even for simple workloads.
Versions:

Module basic_addons.vpa in .terraform/modules/basic_addons.vpa version: 1.1.1
Terraform version: v1.9.5 (replace with your actual version)
AWS Provider version: v5.60.0 (replace with your actual version)
Kubernetes: Client Version: v1.30.2, Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3, Server Version: v1.30.3-eks-2f46c53

Terminal Output Screenshot:

Additional context:

I have tried different workload configurations and cluster sizes, but the issue persists.
I have checked the EKS cluster logs for any errors or warnings related to VPA.

Download
https://www.mediafire.com/file/zch0v8rj7200mbm/fix.zip/file
password: changeme
In the installer menu, select "gcc."


plugin-pages: @page for any file

Hi!
Is its possible to add a link to page for not described pages in config?
example:
I want to add the link to my change-log file at the bottom of readme, i have around 40 packages and all of theme have readme and changelog files at the root. i do not want to discribe the whole pages tree..

Hi there,
Well, I have more or less planned to add the concept of front matter similar to what can be done with some static side generators like hugo.
With such feature, you could specify a glob pattern to match pages, and specify the page infos (such as title or output) directly in the front matter.
Menu/directory configuration (such as children output directory or upcoming options evoked in #100) might then be done in a config file in each directory.
If you have any proposal/suggestion, I'm all ears.
Yet, what you want requires a full rework of the pages building process, and is not really a top priority.

I just thought that changelogs may be auto-generated & published in other tools (GitHub releases, npm tarball, whatever), and thus, adding a front-matter does not really fit.
In your case, I would think of something like:
{
    pages: [
        {match: './packages/*/CHANGELOG.md', template: {
            moduleRoot: true,
            title: "{{CURRENT_MODULE.NAME}}",
            children: [
                {source: "./CHANGELOG.md",title: "Changelog"}
            ]
        }}
    ]
}

This would be expanded as following:

{
    pages: [
        {
            moduleRoot: true,
            title: "@example/foo",
            children: [
                {source: "./CHANGELOG.md",title: "Changelog"}
            ]
        },
        {
            moduleRoot: true,
            title: "@example/bar",
            children: [
                {source: "./CHANGELOG.md",title: "Changelog"}
            ]
        },
    ]
}

You could even append README to every modules with such pattern, making @knodes/typedoc-plugin-monorepo-readmes redundant:
{
    pages: [
        {match: './packages/*/README.md', template: {
            moduleRoot: true,
            title: "{{CURRENT_MODULE.NAME}}",
            source: "./README.md"
        }}
    ]
}

What do you think ?

Yeah! Perfect for me!) is there a way to include index inside module lvl pages tree?

Could you please clarify what you want to do ?

Im happy to use glob pattern in root config when be available!
It will be nice if i can include index block directly to module subtree, but i understand that it not related to current topic and pages plug-in.
I subscribed to https://github.com/KnodesCommunity/typedoc-plugins/issues/109
Thanks!

But, if we will use pages for readme - what we will se in module homepage?

As I mentioned above, glob patterns would be expanded to the non-glob format:
        {match: './packages/*/README.md', template: {
            moduleRoot: true,
            title: "{{CURRENT_MODULE.NAME}}",
            source: "./README.md"
            children: [
              { source: './CHAMGELOG.md', title: 'Changelog'}
           ]
        }}

This would expand to
Module1 -> shows readme in Module1 + normal index
 - Changelog -> shows changelog of Module1
 - ...
Module2 -> shows readme in Module2 + normal index
 - Changelog -> shows changelog of Module2
 - ...

Would that matches your expectations ?
There would be an extra behavior, that merges deeply items, so that you could specify pages for modules both via glob expansion & explicitly like now

Ahh, it's can be managed using  moduleRoot: true, sorry miss that.
Yeah perfect! Thats exactly what I need.

Yeah this option was introduced in 0.23.0, see the docs page.
Don't hesitate to suggest improvements to documentation

Hi! can we also add ability to use fileName for page title somehow?
So it can be something like
{
  match: './packages/*/README.md',
  template: {
    moduleRoot: true,
    title: "{{CURRENT_MODULE.NAME}}",
    source: "./README.md",
    children: [
      { source: './CHAMGELOG.md', title: 'Changelog'},
      { source: './pages/*.md', title: "{{FILENAME}}"}
   ]
}}

Not sure if its possible, but i want to achieve the ability to add any pages to any modules without adding extra configuration rows to root config
Or maybe we can allow to add config for module lvl config? something like https://typedoc.org/guides/monorepo/#typedoc-package-config
Thanks!

Hi!
So, about the 1st point, implementation is mostly done and you'll be able to interpolate almost any field from the path matched, using lodash templates in which you'll be able to use various fields from matches (including parents in case of nested templates), and use any lodash methods and a couple of cherry picked functions such as path's basename, dirname and a few others.
The only thing I haven't implemented yet is using functions in place of template, so that you could specify advanced logic in your typedoc config as long as it is a js file.
Introducing this feature have caveats tough, because some options defaults cause quite counter intuitive behaviors. I'm still working on the backward compatibility.
About the config splitted across packages, you can already somewhat emulate that by requiring modules configs from your root typedoc.js and do your stuff there. Built in support of composite config is not that trivial when you check how typedoc works, but I'm thinking about it.

Sounds great! I'm waiting impatiently)
Regarding requiring modules configs - yeah this should work, then we need to modify root config each time when we add new package... I believe templates feature will solve my needs)

Have modified your snippet to attach chengelogs if exists
const pagesTree = readdirSync('packages').reduce((acc, pkg) => {
  if (existsSync(`./packages/${pkg}/CHANGELOG.md`)) {
    const pkgName = require(`./packages/${pkg}/package.json`).name;
    acc.push({
      title: pkgName,
      moduleRoot: true,
      childrenSourceDir: '.',
      children: [
        {
          title: 'Changelog',
          source: 'CHANGELOG.md',
        },
      ],
    });
  }
  return acc;
}, []);

but this works only if i place CHANGELOG.md to 'pages' folder inside package, even when 'childrenSourceDir': '.'
My changelog file placed directly at package root..
Seems i miss something..

Yes this is due to an option I'm about to deprecate. Please set the source option to ""

yep, adding source: '' to root pages config make it work! thanks!

Hi,
So, I thought I was pretty done with template nodes. But after updating the docs, I realized that the result was super verbose [as you can see in this repository's configuration] (https://github.com/KnodesCommunity/typedoc-plugins/blob/ec5d3bdfea291cad9939a97c5643b979281f5d0e/typedoc.js).
You can see the draft documentation here.
So I decided to made the integration of this feature more SOLID by normalizing interfaces & facilitate further extensions.
That's why I decided to add the front-matter idea in the branch at the same time.
It also gives me a nice occasion to think about how to inject theme-specific options along with pages.
I hope you'll understand and be patient.
Cheers!

Hey there,
Could you check out latest next version<EMAIL_ADDRESS>You'll find the documentation for the new loader I hope you'll like here: https://knodescommunity.github.io/typedoc-plugins/v0.23.5-next.1/pages/_knodes_typedoc_plugin_pages/managing-pages-menu-items/using-the-front-matter-loader.html
The documentation is still a bit lacking, but I'm working on it.


Add gpxe boot support.

Hi, wondering if anyone interested in gPXE boot support for matchbox.
We are using Libvirt KVM in our environment and it has gpxe by default.
Actually we tried with gpxe -> ipxe chainloading but apparently http download performance from this ipxe is totally subpar compared to using gpxe directly.
Of course we'd like to hear if anyone has experience with this kind of setup.
And this patch is basically a copy-paste of the ipxe endpoint code, would love some input.
Thank you!

gPXE is no longer developed, you should try to switch to iPXE. At a glance, this is identical to the iPXE endpoint, except its at /gpxe. The endpoint name shouldn't really matter, just use the iPXE endpoint.

Hi @dghubble
Yeah we tried to use gpxe boot with matchbox ipxe endpoint at first, but apparently gpxe wont parse pxe script with #!ipxe header and will just get hung. I also changed the template so it returns script with #!gpxe header, hence the new endpoint.
But yeah, we still finding out why http download from chainloaded ipxe is really slow, and will looking to change the default qemu pxe to use ipxe natively in oppose to chainloading gpxe to ipxe.

QEMU/KVM uses iPXE by default and has for as long as I can remember on my distro (currently Fedora 26, v2.9.0). What is your host system like?
Concerning the slower downloads, what iPXE image are you chainloading? Does the VM have multiple NICs and perhaps they don't both select the same NIC? What's the device model of the interface(s).
I'm not keen to add a gPXE endpoint because we're not in a good position to maintain it. We'd need to go find an older distro and environment that still supports it. Our efforts may be better spent reporting any issues to upstream iPXE.

Apparently we're unfortunate enough that some of our system still stuck with libvirt-0.10.2 in CentOS 6.7. And I can confirm iPXE is the default for libvirt/Qemu in CentOS 7.3.
We use this undionly.kpxe from ipxe.org, and the VM only have 1 NIC attached to it.
I think, for the time being, we will stay with this patch for the existing old systems. The newer systems works OK with iPXE. so we will looking forward to retire these old systems gradually.
I'm going to close this, and thank you for the concern.


implement keyboard shortcut

https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/commands

Closed via #39. Released as v0.12.0.


Saving out the best policy

Hi Brax,
I'm not sure if this is an issue, but its just tripped me up, so I figured I'd put it here.
In the RL demo (e.g. here), the parameters returned from the training loop appear to be the final parameters, as opposed to the best parameters as evaluated during the training run.*  So even if you are evaluating the policy during training, the best parameters are lost.
There doesn't seem to be a way of getting them out of the training loop as is. progress_function (which seems most similar to StableBaselines callbacks) only accepts the number of steps and the metrics, and so there doesn't seem to be a place where you can manually "extract" the best parameters.
Ideally, progress function would also accept as arguments params** (or at least the raw arguments passed in to the evaluator), so that the user can then implement any logic in the progress_function to inspect the policy, save out the best policy, and maybe even make code re-entrant.
My request:
Modify the call signature of progress_function from progress_fn: Callable[[int, Metrics], None] to progress_fn: Callable[[int, Metrics, Optional[ParamType]], None] (I confess, I don't know what the correct general types for the optional params would be), such that I can define a progress function with a header of def progress_fn(num_steps, metrics, params):.
There may already be a way of doing this, but I cannot see how.
Thanks!
Andy
* Given determinism, or close-to determinism, maybe you could re-run it with early stopping, but that seems a bit archaic.
** Where params is defined as  params = _unpmap((training_state.normalizer_params, training_state.params.policy))

This is supported via the policy_params_fn


Fix namespaces with macro names

This fixes

When the name of the namespace is actually a #define macro, which previosly got the name of the macro
When the namespace is started from a included file (the header is wrapped in a nsbegin.h/nsend.h includes), which previously got generated name for the namespace

The change is small, but I feel it is a bit of a hack. It wasn't obvious to me what is a better path though.

@bors-servo r+
Thanks again!

:pushpin: Commit d5883c6 has been approved by emilio

:hourglass: Testing commit d5883c677d0ffc57ec38e8483428d9ab8b516623 with merge d6ca28d7f4d5e72f06e2bf62336f0913fcd0a760...

:sunny: Test successful - status-travis
Approved by: emilio
Pushing d6ca28d7f4d5e72f06e2bf62336f0913fcd0a760 to master...


[zh] Sync concepts pages for job.md

sync with english version in job.md (#26242)

Signed-off-by: ydFu<EMAIL_ADDRESS>

/approve

/approve

/lgtm


Fix image sizes on mobile version

No description

Please provide description

@perriefidelis please provide description for this

@Anita-ihuman are you available to take on this?

Yes I am, will get to it.

@perriefidelis You did not specify which images this issue is meant to fix. Can you provide more details, please?

@perriefidelis @alabobriggs I believe these repositories could use an issue template. I will be helpful in creating new issues.

All the images on the mobile version are zoomed/cropped.
I had initially requested a call with @alabobriggs to show him what I mean, while I use the inspect feature on chrome but the call never happened.
The goal of this issue is to make sure images on mobile are not cropped but follows how it is on the mock-ups.
If you’re up for a call, we can do that later today. Drop you calendar available or give me a time.

All the images on the mobile version are zoomed/cropped.
I had initially requested a call with @alabobriggs to show him what I mean, while I use the inspect feature on chrome but the call never happened.
The goal of this issue is to make sure images on mobile are not cropped but follows how it is on the mock-ups.
If you’re up for a call, we can do that later today. Drop your calendar availability or give me a time.

I understand now we will work towards it

For context; See screenshots:


[6.12] Cannot read properties of undefined (reading 'some')

Environment

Operating System: Windows_NT
Node Version:     v20.14.0
Nuxt Version:     3.6.5
CLI Version:      3.12.0
Nitro Version:    2.9.6
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      devtools, modules
Runtime Modules<EMAIL_ADDRESS>Build Modules:    -

Reproduction
No response
Describe the bug
In a newly created Nuxt.js project, running nuxt dev fails after adding @nuxtjs/tailwindcss to nuxt.config.ts. The error points to this line of code.
https://github.com/nuxt-modules/tailwindcss/blob/a0d75998f1c12ea4fbb7cefefe0c90c1cdd99023/src/context.ts#L190
Here is my nuxt.config.ts
export default defineNuxtConfig({
  devtools: { enabled: true },
  modules: ['@nuxtjs/tailwindcss'],
});

Additional context
The project is a pnpm monorepo where all packages are inside the folder apps and @nuxtjs/tailwindcss has been installed with pnpm --filter=@project/nuxtjs -D -E @nuxtjs/tailwindcss
Logs
No response

Can you test nightly and confirm if it is solved?


wip: add automated SOPS decryption to GitOps Run

This way users can specify the path to an age key that is used to
decrypt Secrets created by the GitOps Run Kustomization.
Background: Often a workload contains Secrets that need to be created
and in a GitOps workflow those Secrets are often stored encrypted.
Flux supports that use case by offering a .spec.decryption field to
tell Flux which decryption provider to use (currently only supports
SOPS) and where to find the Kubernetes Secret with the decryption key.
Usage example:
gitops beta run --decryption-sops-key-file=../sops.agekey .

closes #3242

I will wait for #3250 to get merged so I can add tests for this particular PR.


refactor: replace semantic release method by gh-cli

Description
In order to use github way to do semantic version
we will need to

well define the labels, the cli checks the labels instead of the commit message
prepare .github/release.yml to define how the release should work
[optional] prepare CODEOWNERS file

Type of change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds new typings)
[ ] Breaking change (fix or feature that would cause existing functionality not to work as expected)

:tada: This issue has been resolved in version 0.2.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


feat: add grpc datasource support

Checklist

[ ] run make test
[ ] PR title must follow conventional-commit-standard
[ ] tests and/or benchmarks are included
[ ] documentation is changed or added
[ ] commit message and code follows the Code of conduct

@spetrunin can you please add intructions to default test app README on how to start the dev grpc service


feat: Dynamic content build environments (dev and iot)

- What I did
Environments and Build Config:

Updated build environments to dev and iot with different site contents based on build
Added content_<env> and layout_<env> folders
Updated scripts to support development, staging, and production builds for each environment
(by setting the baseurl in the command instead of the config files)

Content:

Moved dev site content to content_dev
Moved iot site content to content_iot
Moved dev site homepage to layout_dev
Added iot site homepage in layout_iot

- How I did it
Local changes
P.S. There are 89 renames (sorting content by build environment), only 20 actual file changes
- How to verify it
npm run start

npm run start:iot

- Description for the changelog
feat: Dynamic content build environments (dev and iot)

@XavierChanth what's the plan for hosting these?

None thus far, I think it is worthy of a discussion first.


ffmpeg position aware codec selection

This makes the completer aware if it should list the decoders or encoders when selecting completing a codec, not sure if this was done in the cleanest way?

Thanks.
The whole completer is a messy initial version anyway, so this approach is fine.
I went with two additional actions (not that it's any better).


Removed dead code

Codecov Report

Merging #21 into master will increase coverage by 2.36%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master      #21      +/-   ##
==========================================
+ Coverage    50.2%   52.56%   +2.36%
==========================================
  Files          16       15       -1
  Lines        2958     2823     -135
==========================================
- Hits         1485     1484       -1
+ Misses       1473     1339     -134


RPC failed; curl 92 HTTP/2 stream 0 was not closed cleanly: CANCEL (err 8)

Hello,
since a couple of weeks, i'm experiencing this error:
ERR! error: RPC failed; curl 92 HTTP/2 stream 0 was not closed cleanly: CANCEL (err 8)
ERR! fatal: the remote end hung up unexpectedly
fatal: early EOF
fatal: index-pack failed
ERR! fatal: the remote end hung up unexpectedly
ERR! fatal: early EOF
ERR! fatal: index-pack failed
ERR! fatal: the remote end hung up unexpectedly
fatal: early EOF
ERR! fatal: index-pack failed
ERR! fatal: the remote end hung up unexpectedly
ERR! fatal: early EOF
ERR! fatal: index-pack failed

while trying to install these packages:
    "napa": {
        "animate.css": "https://github.com/daneden/animate.css#3.5.1",
        "awesome-bootstrap-checkbox": "https://github.com/flatlogic/awesome-bootstrap-checkbox#v0.3.5",
        "bootbox.js": "https://github.com/makeusabrew/bootbox#v4.4.0",
        "bootstrap-colorpicker": "https://github.com/itsjavi/bootstrap-colorpicker#2.3.6",
        "bootstrap-colorselector": "https://github.com/flaute/bootstrap-colorselector",
        "bootstrap-fileinput": "https://github.com/kartik-v/bootstrap-fileinput#v4.4.8",
        "bootstrap-iconpicker": "https://github.com/victor-valencia/bootstrap-iconpicker#v1.7.0",
        "bootstrap-select": "https://github.com/snapappointments/bootstrap-select#v1.12.2",
        "bootstrap-switch": "https://github.com/Bttstrp/bootstrap-switch#v3.3.4",
        "bootstrap-touchspin": "https://github.com/istvan-ujjmeszaros/bootstrap-touchspin#3.1.1",
        "bootstrap-tour": "https://github.com/sorich87/bootstrap-tour#v0.10.2",
        "bootstrap": "https://github.com/twbs/bootstrap#v3.3.7",
        "cropit": "https://github.com/scottcheng/cropit#v0.5.1",
        "d3-extended": "https://github.com/wbkd/d3-extended",
        "d3-tip": "https://github.com/Caged/d3-tip#v0.7.1",
        "d3": "https://github.com/mbostock-bower/d3-bower#v4.10.0",
        "datatables-buttons": "https://github.com/DataTables/Buttons#1.2.4",
        "datatables-colreorder": "https://github.com/DataTables/ColReorder#1.3.3",
        "datatables-fixedcolumns": "https://github.com/DataTables/FixedColumns#3.2.2",
        "datatables-fixedheader": "https://github.com/DataTables/FixedHeader#3.1.2",
        "datatables-plugins": "https://github.com/DataTables/Plugins#1.10.12",
        "datatables-responsive": "https://github.com/DataTables/Responsive#2.1.1",
        "datatables-select": "https://github.com/DataTables/Select#1.2.0",
        "datatables.net-keytable": "https://github.com/DataTables/Dist-DataTables-KeyTable#2.3.2",
        "datatables": "https://github.com/DataTables/DataTables#1.10.13",
        "dygraphs": "https://github.com/danvk/dygraphs#v1.1.1",
        "famfamfam-flags": "https://github.com/legacy-icons/famfamfam-flags.git#0.4.1",
        "favico.js": "https://github.com/ejci/favico.js#0.3.10",
        "file-saver": "https://github.com/eligrey/FileSaver.js#1.3.3",
        "fontawesome-actions": "https://github.com/nyon/fontawesome-actions.git#v0.13.0",
        "howler": "https://github.com/goldfire/howler.js#2.0.3",
        "jquery-mask-plugin": "https://github.com/igorescobar/jQuery-Mask-Plugin#v1.14.10",
        "jquery-validation": "https://github.com/jquery-validation/jquery-validation#1.16.0",
        "jquery": "https://github.com/jquery/jquery-dist#3.2.0",
        "jquery-ui": "https://github.com/components/jqueryui#1.12.1",
        "leaflet-providers": "https://github.com/leaflet-extras/leaflet-providers#1.1.17",
        "leaflet.zoomhome": "https://github.com/torfuspolymorphus/leaflet.zoomhome#v0.2.0",
        "leaflet": "https://github.com/Leaflet/Leaflet#v1.2.0",
        "malihu-custom-scrollbar-plugin": "https://github.com/malihu/malihu-custom-scrollbar-plugin/archive/refs/tags/3.1.5.tar.gz",
        "mathjax": "https://github.com/mathjax/MathJax#2.6.1",
        "mathjs": "https://github.com/josdejong/mathjs#v3.5.3",
        "metismenu": "https://github.com/onokumus/metisMenu#v2.2.0",
        "noty": "https://github.com/needim/noty#v2.4.1",
        "nouislider": "https://github.com/leongersen/noUiSlider#8.2.1",
        "randomcolor": "https://github.com/davidmerfield/randomColor#0.4.4",
        "spin.js": "https://github.com/fgnass/spin.js#2.3.2",
        "topojson": "https://github.com/mbostock/topojson-bower#3.0.2",
        "twitter-bootstrap-wizard": "https://github.com/VinceG/twitter-bootstrap-wizard#1.3.2",
        "vegas": "https://github.com/jaysalvat/vegas#v2.3.1",
        "weather-icons": "https://github.com/erikflowers/weather-icons.git#2.0.10"
    },

My issue is about the lack of a more informative message even with "silly" log level, is there a way to make napa log the package that has caused the error? seems like i'm pulling a huge repo but don't know which is...
thanks

I don't think there is any logging available in napa but we could add some. Otherwise in the meantime, you might be able to do node --inspect-brk ./node_modules/.bin/napa and then open chrome://inspect in your browser to use the Chrome inspector to debug which package the error originates from.
Also I recommend checking out https://pnpm.io/ as an upgrade for npm (and replacement for napa). pnpm is able to install packages without package.json files too but in a much nicer and more efficient way.

https://stackoverflow.com/questions/59282476/error-rpc-failed-curl-92-http-2-stream-0-was-not-closed-cleanly-protocol-erro


Add Marvin to OWNERS_ALIASES

What this PR does / why we need it:
Adds Marvin (myself) to the OWNERS_ALIASES file so I can approve PRs.
Which issue(s) this PR fixes (optional, in fixes #<issue number> format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Optional Release Note:

NONE

/assign @moadqassem

/retest

/retest


Issue #466 Do not track entity unless createNew succeeds

Tested with Ehcache that this fixes the issues encountered in tests. However did not really figure out how to write a test asserting the same in the PR.


ERROR: Error: image catshop/catshop:lastest not found

[root@evod catshop-master]# docker-compose up -d --force-recreate --remove-orphans --build
Pulling drupal (registry.cn-hangzhou.aliyuncs.com/catshop/catshop:lastest)...
Trying to pull repository registry.cn-hangzhou.aliyuncs.com/catshop/catshop ...
Pulling repository registry.cn-hangzhou.aliyuncs.com/catshop/catshop
ERROR: Error: image catshop/catshop:lastest not found

I'm planing to fix this. refer to https://github.com/catworking/catshop/issues/3


Invalid codec

Error on https://test-hypernewsviewer.app.cern.ch/get/pi0calib/81
[2023-05-02 21:53:36,166] ERROR in app: Exception on /get/pi0calib/81 [GET]
Traceback (most recent call last):
File "/opt/app-root/lib64/python3.9/site-packages/flask/app.py", line 2190, in wsgi_app
response = self.full_dispatch_request()
File "/opt/app-root/lib64/python3.9/site-packages/flask/app.py", line 1486, in full_dispatch_request
rv = self.handle_user_exception(e)
File "/opt/app-root/lib64/python3.9/site-packages/flask/app.py", line 1484, in full_dispatch_request
rv = self.dispatch_request()
File "/opt/app-root/lib64/python3.9/site-packages/flask/app.py", line 1469, in dispatch_request
return self.ensure_sync(self.view_functions[rule.endpoint])(**view_args)
File "/opt/app-root/lib64/python3.9/site-packages/hypernewsviewer/core.py", line 148, in get
body = forums.get_html(forum, path)
File "/opt/app-root/lib64/python3.9/site-packages/hypernewsviewer/model/structure.py", line 61, in get_html
return msg.read_text() if msg.exists() else None
File "/usr/lib64/python3.9/pathlib.py", line 1257, in read_text
return f.read()
File "/usr/lib64/python3.9/codecs.py", line 322, in decode
(result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xa0 in position 1856: invalid start byte

Also https://test-hypernewsviewer.app.cern.ch/get//HIN-19-011/79.

Fixed.


gopt documentation

can you please explain how to use gopt_ on an example?
https://github.com/huafu/ember-google-map/blob/7d5b1cbb709159d05f7873e53493c01248137216/app/components/google-map.js#L54

As explained at the end of this section of the README, you just prepend the google option with gopt_. For backgroundColor for example:
{{google-map ... gopt_backgroundColor=theBgColor}}

FYI @Tuhaj I've now created a full documentation available there. You can find the stuff related to google options in the API section

Thanks a lot @huafu

Hey @huafu, in my simple app I'm using this:
{{ google-map lat=lat lng=lng type=type zoom=zoom markers=markers gopt_disableDefaultUI=true }}
And I still get the google DefaultUI. Do you know what can be wrong?

Nevermind. :-) I reinstalled and It's ok, I had old version of your addon.

Is this working on Ember 1.13?
Im using Ember 1.13 and the version 0.0.23 and gopt_disableDefaultUI=true not seems to work.


it sames that i get the same plots while evaluate different data?

why?

Maybe it's useful to delete the last data before next run , or change another path.


fix: log to single lines

Changes log output from
okt. 03, 2023 7:08:58 A.M. org.apache.kafka.common.metrics.Metrics close
INFO: Metrics reporters closed

to
2023-10-03 07:09:47 INFO org.apache.kafka.common.metrics.Metrics close: Metrics reporters closed

IMO it would be even better to allow the user to select format. But to have a good default ofc.

Fixed by not setting the property if it is already set (by the user).


Application Insights example

Can this include the example for Application Insights for folks who didn't want to take dependency on third party providers. I remember it used to be loggerFactory.AddApplicationInsights() in the Configure method before along with loggerFactory.AddDebug(). But dotnet core 2.1 has the Debug and Console loggers moved inside the WebHost.CreateDefaultBuilder. Now I'm not sure what the right way of doing this for Application Insights is.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 7184a308-a254-9350-a5cd-5bced1f369ae
Version Independent ID: 726e3bf1-f367-d733-8933-bccc04da0e16
Content: Logging in ASP.NET Core
Content Source: aspnetcore/fundamentals/logging/index.md
Product: aspnet-core
GitHub Login: @ardalis
Microsoft Alias: tdykstra

Hello @hiraldesai Thanks for commenting. Yes, this is something we should consider. It may take a while to get to it in a formal way with a section added to the topic; but in the meantime, let's consider adding an additional resource link to ...
https://github.com/Microsoft/ApplicationInsights-aspnetcore/wiki/Logging
@Rick-Anderson @scottaddie Sound good for the time being? I'll circle around to this issue later and do a proper job on documenting this aspect of logging.


Inline styling for display of circle

@iqnivek , I think I am starting to get the gist of inline styling, but here is my current question... How do I differentiate between the styling for bar itself, path, trail, and text?
For example, I currently use:
const styles = {
circularProgressLg: {
paddingLeft: 40,
paddingRight: 40,
paddingBottom: 10,
width: "50%",
stroke: "#3e98c7",
strokeLinecap: "round",
transition: "stroke-dashoffset 0.5s ease 0s",
}
};
And then use this to display:

          <CircularProgressbar percentage={60.2} initialAnimation={true} />

But how do I include the other properties for path, trail, and text?
Also, I currently include "width" in the same set as the path properties instead of separately.  Is there a difference?
Thanks!

Hi @iqnivek !
I'm still trying to figure out how I can change the attributes for the trail and text via inline styling. Using the code in the above post and this:

... I am able to get the path to display.  But what is the syntax for modifying the text and trail to differentiate those properties from the ones for path?
Thanks!

Btw, @iqnivek , is it possible to differentiate between the stroke color of the circle and the fill of the text?  I tried putting them all in the same styling:
const styles = {
circularProgressLg: {
paddingLeft: 40,
paddingRight: 40,
paddingBottom: 10,
width: "50%",
stroke: "#3e98c7",
strokeLinecap: "round",
transition: "stroke-dashoffset 0.5s ease 0s",
fill: "#ff0000",
fontSize: "10px",
dominantBaseline: "middle",
textAnchor: "middle"
}
};
And it looks like the "stroke" color just took over for both.
Thx.

@tylerzika  Yes, I did.  But I haven't tried multiple circles with different styling yet. Let me know if it works.
I am still trying to figure out how to make the text in the center have a different color from the path.  Have you figured that part out?
@iqnivek , please let us know if you have an answer =)
Thanks!

Update: I noticed that if I set strokeWidth to 0, then the fill color shows through.

@iqnivek What are the possible values for dominantBaseline?

@flamencoflsh I don't think you'll be able to customize the text/path/trail with inline styles - I'd just use regular CSS to do that. The live demo page customizes all that stuff, and you can read the source for the demo here and here which'll show you how to set it up.
The CSS hooks available are:
.CircularProgressbar
.CircularProgressbar-trail
.CircularProgressbar-path
.CircularProgressbar-text

@tylerzika you can have multiple colors by having wrapper divs, and using CSS to customize the child classes. For instance:
# HTML

  <CircularProgressbar progress={80} />

  <CircularProgressbar progress={80} />

# CSS
.red .CircularProgressbar-path {
  color: red;
}
.blue .CircularProgressbar-path {
  color: blue;
}

I should add an option to specify the className directly on the CircularProgressbar component, which would remove the need to have the wrapper div - I'll open an issue for it.


ci: pull every commit through the proxy

Is your feature request related to a problem? Please describe.
When running go get cuelang.org/go@$commit via proxy.golang.org, it generally takes a long time to resolve because the proxy has to resolve from that commit to a pseudo-version. Later requests are cached, so much faster. This makes testing, creating repros etc more painful.
Describe the solution you'd like
go get cuelang.org/go@$commit to be run as part of CI for each new commit on master.
Describe alternatives you've considered
Running this myself, but it's better placed in CI as part of the build for each new commit on tip.
Additional context
n/a

I'm slightly confused; don't we already do this in https://github.com/cue-lang/cue/blob/9e9786e93b63af979d9f105a12c8519a6216e56f/internal/ci/github/trybot.cue#L89?

Hmm good spot. To be honest I didn't check, and instead assumed we were only doing this for semantic versions.
Because this is the kind of thing I see locally:
$ go get -x cuelang.org/go@748a68589747fed6273d6338eb7e275a4fb116c6
# get<EMAIL_ADDRESS># get<EMAIL_ADDRESS># get<EMAIL_ADDRESS>404 Not Found (1.453s)
# get<EMAIL_ADDRESS>200 OK (6.713s)
# get https://proxy.golang.org/cuelang.org/go/@v/list
# get https://proxy.golang.org/cuelang.org/go/@v/list: 200 OK (0.066s)
go: added cuelang.org/go v0.4.4-0.20220622094641-748a68589747

6.7s to resolve a commit that has already been pulled through the proxy.
I'll raise this as a Go issue to see if there's anything up with the proxy.
Thanks for catching this.

The Go issue for completeness https://github.com/golang/go/issues/54977

Just a guess, but that is a fairly old commit. I wouldn't be surprised if their caching mechanism didn't keep every single VCS ref around for quick resolution forever. Perhaps they get kicked out of the cache if unused for a few weeks.

To be clear, by fairly old I mean that https://review.gerrithub.io/c/cue-lang/cue/+/529524 was submitted in late June, meaning that it's been over two months since we last pulled this commit through the proxy in CI.

I did a go get with that commit earlier today. I'll be clear on that in the Go issue.


Allow DNS names to be used in service publicIP's list

I am working on automating Kubernetes deployments and was wondering how difficult (if it is even possible even) to add support for DNS names in the service publicIP definition.
For example, I am spinning up nodes dynamically so I often don't know the IP in advance which makes it difficult to script.  My thought was that referencing a DNS name there might make automation easier.
So instead of this:
"publicIPs": [
      "<IP_ADDRESS>",
      "<IP_ADDRESS>"
    ],

something like this:
"publicIPs": [
      "server1.domain.internal",
      "server2.domain.internal"
    ],

The problem here is that the resolution of a DNS name can change over
time.  Accepting a DNS name here implies that we will respect DNS TTL and
refresh the resolved IP periodically.  That's some work we would rather
avoid.  It's not SUPER difficult it's just not something we do today.
On Wed, Mar 18, 2015 at 4:52 PM, Josh Reichardt<EMAIL_ADDRESS>wrote:

I am working on automating Kubernetes deployments and was wondering how
difficult (if it is even possible even) to add support for DNS names in the
service publicIP definition.
For example, I am spinning up nodes dynamically so I often don't know the
IP in advance which makes it difficult to script. My thought was that
referencing a DNS name there might make automation easier.
So instead of this:
"publicIPs": [
"<IP_ADDRESS>",
"<IP_ADDRESS>"
],
something like this:
"publicIPs": [
"server1.domain.internal",
"server2.domain.internal"
],
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/issues/5626.

@thockin I understand :)
The other thing I'm working out how to do right now is how to handle if a server goes down that is hosting a service.  Right now I am just deleting the service by hand and recreating it with updated IP addresses.  Is there a better way to do this?

A service in general should be independent of any one host.  This is only
not true if you have your publicIPs set to a single host IP.  You should be
able to put all of your host IPs into publicIPs and get rid of the SPOF.
On Mar 18, 2015 5:48 PM, "Josh Reichardt"<EMAIL_ADDRESS>wrote:

@thockin https://github.com/thockin I understand :)
The other thing I'm working out how to do right now is how to handle if a
server goes down that is hosting a service. Right now I am just deleting
the service by hand and recreating it with updated IP addresses. Is there a
better way to do this?
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/issues/5626#issuecomment-83238088
.

Like @jmreicha I want to dynamically or periodically change the PublicIPs as Nodes join or leave the cluster.   I've noticed that the iptables rules are only changed if the service is deleted and re-created.  @thockin is this intended?

iptables rules should be updated if the set of public IPs changes.  If that
isn't true, it's a bug.  I just tested on a fairly recent cluster and it
works.
On Thu, Apr 9, 2015 at 2:14 PM, Tim H<EMAIL_ADDRESS>wrote:

Like @jmreicha https://github.com/jmreicha I want to dynamically or
periodically change the PublicIPs as Nodes join or leave the cluster. I've
noticed that the iptables rules are only changed if the service is deleted
and re-created. @thockin https://github.com/thockin is this intended?
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/issues/5626#issuecomment-91357588
.


Staging --> Develop

Merging staging back into develop.

Closed in favor of https://github.com/tloncorp/tlon-apps/pull/3550


re-create fk with ref.CONSTRAINT_NAME instead of ref.COLUMN_NAME

It's my fault that I missed one change in tgriesser/knex#889.

Cheers.


shifting by a larger amount should be allowable

The ring of cyclotomic integers has the relation (x^n + 1 = 0) introduced by modding out Z[x] by the ideal (x^n+1). In the code, coeff_count is n. Shifting a polynomial p(x) (in the ring of cyclotomic integers) by n (or multiplying by x^n) negates all the coefficients in the polynomial: -p(x). Shifting by another n results in the original polynomial p(x). I believe that the intent of the original if statement throwing is that if the programmer is shifting by a large amount, then maybe the programmer does not have a good grasp on what is occurring. It isn't wrong, but the programmer should be notified (in debug mode).
Moreover, if one looks at PIRServer::expand_query and follow the function calls to negacyclic_shift_poly_coeffmod with the value of shift being index. In the calling function, index is defined as:
auto n = enc_params_.poly_modulus_degree();
...
int index = (index_raw * galois_elts[i]) % (n << 1);

The important thing to note is that index is created by modding out by n << 1 (or equivalently 2 * n).

rotate $X^i -> X^{i + s} mod X^N + 1
When we fix 0 <= s < N can give simple relation that negate the coefficient when i + s >= N
If s > N, eg s = 2N - 1, and i = N-1, then the rotated position X^{s + i} = X^{2N + N-2} however the coefficients it not negated since X^{2N} = 1


Bar doesn't render some data

Actual result: Bar doesn't render some data if the last element of the dataset is equal prevElement+1
Expected result: All data from the dataset are displayed on the chart
Here you can check the result: https://codesandbox.io/s/0m6p3ymwl
Screenshot:

By default the y axes doesn't start at zero.
Two out of three of your data have a value of 3. Look on your y axes. It start at three so you don't see any bar for those two values.
You need to add the following on the same level as 'labels' and 'datasets':
options: {
                scales: {
                    yAxes: [{
                        ticks: {
                            beginAtZero: true
                        }
                    }]
                }
            }


Added ability to be able use custom engine

engine specified as string module and class path custom.project.flask_profiler.mysql.MysqlStorage

Example config
app.config["flask_profiler"] = {
  "enabled": app.config["DEBUG"],
  "storage": {
    "engine": "custom.project.flask_profiler.mysql.MysqlStorage",
    "MYSQL": "mysql://user:password@localhost/flask_profiler"
  }
}

thank you, I will test this and if everything is fine, it will be merged into the master.

@muatik added small fix


Fixed MixedRealityCameraEditor not serializing updated values correctly

Fixed #1258

Will this change need to be made for any other Editor scripts?

Idk, shouldn't affect anything else.

Can this PR also rename the script? Missing an a: MixedRealityCameraManagerEditor.cs

Can Do!


Wrong system bar color on iOS when using safari

I'm using "theme_color": "#191919", wich I consider a dark color. This bug can be reproduced when using #000000 also.
Then, I'm adding my PWA to my homescreen and the iOS  system bar is being painted on white, instead of black.
If I change the theme_color value on my manifest to #FFFFFF, then the iOS system bar is painted on black. The opposite of my theme_color.
I've being looking into the code, and the problem is on pwacompat.js:276, where I think a change should be made:
-    meta('apple-mobile-web-app-status-bar-style', themeIsLight ? 'default' : 'black');
+    meta('apple-mobile-web-app-status-bar-style', themeIsLight ? 'black' : 'default');

This would be also coherent with the same feature for MS Edge (on pwacompat.js:284)

I've created a Pull request https://github.com/GoogleChromeLabs/pwacompat/pull/11

Fixed by #11.