[Error] Please enter your api key, go to https://codegpt.co/ for more information.

Can you please refactor your code and communicate better errors? I'm getting this even though I've set-up my API key.

Same here :(

Yeah I don't get it except for it may be an IDE issue.  I think updating to the latest VS Code may fix it, but not on Codium ... at least on a Mac.

did you updated the extension ?

My understanding is that some 3rd party dependencies cannot be open-sourced  with some plugins, and they can only be released for VS Code.  Actually I think it's some of the code MS included in it, now that I'm remembering ... probably a little of both.
The developer can confirm this?  I know they released it for some other IDEs, but I'm thinking Codium might be a special case being built off VS Code?

Codegpt office extension is in vscode only. It uses an vscode encripted storage to store the api keys, maybe in your os you need to send special permissions ?

Thank you so much, that's just what I needed to hear.  The developer should be able to close at least one ticket, and should probably should add the clarification in bold somewhere.

same issue, and using vs code

@adepeuf , which version, what platform, and is it the exact issue and error message?

VS CODE:
Version: 1.73.0 (system setup)
Commit: 8fa188b2b301d36553cbc9ce1b0a146ccb93351f
Date: 2022-11-01T15:34:06.111Z
Electron: 19.0.17
Chromium: 102.0.5005.167
Node.js: 16.14.2
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.22621
Sandboxed: No
CODE GPT extension: v2.1.6

@adepeuf Your problem is wrong VS Code version, please update to the latest version. 1.78.

@adepeuf Your problem is wrong VS Code version, please update to the latest version. 1.78.

works with 1.78, thank you

what is my api ?😒

Version: 1.79.1 (user setup)
Commit: 4cb974a7aed77a74c7813bdccd99ee0d04901215
Date: 2023-06-12T16:14:05.102Z
Electron: 22.5.7
Chromium: 108.0.5359.215
Node.js: 16.17.1
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19044
I still receiving the following message after entering my api key:
[[Error] Please enter your api key, go to https://codegpt.co/ for more information.]
I need help please

I think I got the same problem. I'm using VScodium 1.80 and codeGPT 2.1.9. Whenever I set the API key, it seems it was set correctly. After restart of VScodium, the chat sidebar says I should set my API key (even though I did before).
I tried this several times and with different workflows. Other extensions (like Gitlab) is able to store API keys successfully.
Here's the log, that is thrown by this extension (not sure whether it is related):
2023-07-12 14:02:22.569 [error] TypeError: Cannot read properties of null (reading 'webview')
    at /.../.vscode-oss/extensions/danielsanmedium.dscodegpt-2.1.10-universal/src/extension.js:447:30
    at e.ExtHostCommands._executeContributedCommand (/usr/share/codium/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:99:72243)
    at e.ExtHostCommands.$executeContributedCommand (/usr/share/codium/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:99:73232)
    at t._doInvokeHandler (/usr/share/codium/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:111:14416)
    at t._invokeHandler (/usr/share/codium/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:111:14098)
    at t._receiveRequest (/usr/share/codium/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:111:12856)
    at t._receiveOneMessage (/usr/share/codium/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:111:11555)
    at i.value (/usr/share/codium/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:111:9662)
    at b._deliver (/usr/share/codium/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:60:2465)
    at b.fire (/usr/share/codium/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:60:2784)
    at fire (/usr/share/codium/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:76:16556)
    at i.value (/usr/share/codium/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:127:36590)
    at b._deliver (/usr/share/codium/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:60:2465)
    at b.fire (/usr/share/codium/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:60:2784)
    at fire (/usr/share/codium/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:76:16556)
    at MessagePortMain.<anonymous> (/usr/share/codium/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:127:34667)
    at MessagePortMain.emit (node:events:513:28)
    at Object.MessagePortMain._internalPort.emit (node:electron/js2c/utility_init:2:367) codegpt.askCodeGPT {"value":"DanielSanMedium.dscodegpt","_lower":"danielsanmedium.dscodegpt"}

The problem seems to stem from ChatSidebarProvider, lines 58 onwards.
The const apiKey is filled with:
{"_actual":null,"_actualOk":null,"_actualErr":null,"_hasValue":false,"_value":null,"_hasErr":false,"_err":null}

which is not an API key. I guess something is wrong with the context variable...

In my Mac Ventura  i enter the API Key and I don’t receive any error but when I use the chat e receive a empty response

Can any one help me please

The problem seems to stem from ChatSidebarProvider, lines 58 onwards. The const apiKey is filled with:
{"_actual":null,"_actualOk":null,"_actualErr":null,"_hasValue":false,"_value":null,"_hasErr":false,"_err":null}

which is not an API key. This stems from the fact that context.secrets.get() is an async function, but there is no await.  Later the result of the promise is accessed with apiKey.g, which fails. Simple fix: make _update an async function and await for the api key. Use apiKey only, not apiKey.g These changes fixed the plugin for me in VScodium. I'm uncertain whether this change breaks anything else....

 Created a gist with those changes. Confirmed it's working for OpenAI on an M2 Macbook Pro running VSCodium v1.81.0
https://gist.github.com/silentsilas/c11acff9d65d04f40920ddb782d17195

Hello
After the update to 1.81 it works, thanks
Com os melhores cumprimentos | Best regards
[Image]
Tiago Silva Costa | MSc
Chief Executive Officer
Skype: tiagocostanuno
Tlm: +351 917 269 041 , +351 918 069 762
http://virtualcare.pthttps://virtualcare.pt
UPTEC Asprela I, Rua Alfredo Allen, 461 | 4200-135 Porto
From: Silas @.>
Date: Friday, 4 August 2023 at 20:36
To: davila7/code-gpt-docs @.>
Cc: Tiago Silva-Costa @.>, Comment @.>
Subject: Re: [davila7/code-gpt-docs] [Error] Please enter your api key, go to https://codegpt.co/ for more information. (Issue #142)
The problem seems to stem from ChatSidebarProvider, lines 58 onwards. The const apiKey is filled with:
{"_actual":null,"_actualOk":null,"_actualErr":null,"_hasValue":false,"_value":null,"_hasErr":false,"_err":null}
which is not an API key. This stems from the fact that context.secrets.get() is an async function, but there is no await.  Later the result of the promise is accessed with apiKey.g, which fails. Simple fix: make _update an async function and await for the api key. Use apiKey only, not apiKey.g These changes fixed the plugin for me in VScodium. I'm uncertain whether this change breaks anything else....
 Created a gist with those changes. Confirmed it's working for OpenAI on an M2 Macbook Pro running VSCodium v1.81.0
https://gist.github.com/silentsilas/c11acff9d65d04f40920ddb782d17195
—
Reply to this email directly, view it on GitHubhttps://github.com/davila7/code-gpt-docs/issues/142#issuecomment-1666083101, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AEE2F7D4CRINTIHYRRZ2MDTXTVFK5ANCNFSM6AAAAAAXW3TQEY.
You are receiving this because you commented.Message ID: @.***>


[🚀esl-footnotes]: request to have support of the anchor relationship between note and footnote for print version

As an ESL Footnotes consumer, I want to have an anchor presented for the note that references automatic footnote records for the purpose of having navigation between notes and footnotes presented in a print version of the page.
Scope:
Add optional (to discuss) ability to transform the esl-note element to contain an anchor a presented for the print version to navigate to the footnote record.
API: TBD by @dshovchko
Assumptions:

It is ok to have this behavior enabled by default

:tada: This issue has been resolved in version 4.9.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Uncaught ImagickException in detectQualityOfJpg

See: https://github.com/rosell-dk/webp-express/issues/111

fixed in last commit


Tracking - updated event tracking

https://docs.google.com/spreadsheets/d/1NPZ-NtmFwJhW0v1bgmdSz8X7MbGmsJOa70Hi_po-cKo/edit#gid=1439640141

@ashachaf I need to add the one tagged as "To implement" right ?


Use org.codehaus.mojo:build-helper-maven-plugin to generate static app descriptors

for deploying them to artifactory and host there

LGTM, changing path to stream-apps-kafka-maven etc. on merge and removing extra files under spring-cloud-stream-app-descriptor/src/main/resources/META-INF/1.0.0.BUILD-SNAPSHOT

Merged as commit 6aa4786e77e20095d7c1d7b53c6fee178b7dacdf


support css pseudo-selectors in page object

Hi Cheezy,
Right now, I'm facing an issue where an Image is loaded, which is implemented through a Pseduo-selectors like :before, :after inside div element like below,
APGAR SCore
:before

    Nisi aut id maiores enim delectus. Adipisci provident culpa. Et dolores et et. Qui corporis sed autx

On inspecting that pseudo element in chrome, i found that it is in CSS styles under background with url.
Is there any way to identify the pseudo-selectors or their CSS attributes?

Seems the only way to work with pseudo-elements is using javascript. Check an example below:
https://davidwalsh.name/pseudo-element

For now, the JavaScript approach will need to be used. We can implement something here, if/when Watir adds support.


🚀 Feature: Add npm version badge to README.md (and template)

Bug Report Checklist

[X] I have tried restarting my IDE and the issue persists.
[X] I have pulled the latest main branch of the repository.
[X] I have searched for related issues and found none that matched my issue.

Overview
I don't remember why I didn't add a README.md badge that includes the npm version:
https://shields.io/badges/endpoint-badge

Additional Info
In addition to adding this in the repo's README.md, it'll need to be added to the templating used for setting up other repos. Search files for readme (case insensitive) in their title to see where that's done.

Hi @JoshuaKGoldberg, I can fix this issue. You can assign it to me.

@rj2704 I don't use any assignment/claiming processes in this repo - and just realized it's not documented! See #741 (filed just now). Thanks!


[release-1.19] Fix wrong socket type for extra addresses in QUIC listeners

Manual cherry-pick of #48334
To help us figure out who should review this PR, please put an X in all the areas that this PR affects.

[ ] Ambient
[ ] Configuration Infrastructure
[ ] Docs
[ ] Dual Stack
[ ] Installation
[x] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

Please check any characteristics that apply to this pull request.

[ ] Does not have any user-facing changes.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all


API design

I am looking through the code and I am curious about some of the API choices made:

Why is Sha1 not an affine type
Sha1::digest could take self by value and produce a Digest. This let's the type system prevent mistakes where one reuses the Sha1 without also resetting.
I'm not sure if it's useful anywhere to produce a digest and not reset/be done with the Sha1 state.
Sha1::reset is not necessary, to reset a variable simply overwrite it with Sha1::new(). The compiler will optimize this as efficient as using a reset method but with benefit of type safety.

Why doesn't Digest just store the bytes in the correct endianness?
This would clean up the as_bytes() API to just return a &[u8] making multiple calls more efficient, both API wise and performance wise.

Implement Debug which dumps internal state and reserve Display on Digest for actually displaying the bytes as expected.

I understand that changing API is a big commitment and there may be no desire to do so as the code has existed for a long time already. That said I am willing to make the changes and pull request them.
Any thoughts?

I would like to endorse my version of sha1 which was derived from rust-crypto. I believe it addresses all issues your mentioned, except Debug. (which I don't think is necessary for the working digest states)
I hope one day it will be published under sha1 name, as readme states:

This might go away in the future if rust-crypto or some libraries like that split into smaller parts.
But unfortunately mitsuhiko didn't give a clear answer to my request.

@newpavlov i replied to an email you sent that I will not replace this crate with a widely different one. You are free to publish rust-crypto-sha1 etc.

@CasualX to answer the questions:

I'm not sure if it's useful anywhere to produce a digest and not reset/be done with the Sha1 state.

I don't see a reason why one would want to restrict this functionality. I have written code that requires this in the past. Likewise I am not sure what the point is in removing reset now that it already exists. I'm not in for breaking APIs again just to annoy people.

Why doesn't Digest just store the bytes in the correct endianness?

I don't think there is a reason to this other than that some of the changes that made it work without stdlib changed the implementation to be based this way.

Implement Debug which dumps internal state and reserve Display on Digest for actually displaying the bytes as expected.

Works for me, i would accept patches for this.

@mitsuhiko
In the only reply you've sent me you only said that it will depend on compatibility and that I should send pull request, after that zero reaction. If you are not planning to cooperate in any way at least change readme so it will not confuse others.

@newpavlov I am not sure what exactly you want from me other than complete surrender of the crate here. I already mentioned before that I do not like the idea that rust-crypto crates are not prefixed with rust-crypto or something because it means you will for all eternity to achieve consistency need to get crates from people that are named after hash algorithms etc.
There is already a lot of code that depends on this crate and replacing this crate with a completely different one is not something I think is a reasonable step forward.
Not sure what you want in the README. If people are looking for rust crypto they will find it.

@mitsuhiko
I am not insisting on surrounding crate by any means. I've created PR with code I had because you asked me to do so. Actually you implementation even seems to be superior to rust-crypto's in terms of performance. I was asking you if you are willing to change your crate so it will be in sync with other hash crates, so essentially it means using Digest trait, no_std capability and optional use of crypto-tests for testing and benchmarking. Yes, doing so will introduce several dependencies, but all of them will be quite small and written in pure Rust, so thanks to Cargo end user will face only a minor API change.
Argument about dependent code looks like fallacy to me. We have semver exactly for such kind of situations. All users who don't want or unable to update their code to a new API will continue to use sha1 v0.2 as nothing happened.
Also I am not insisting on transferring crate ownership (though I think it would be reasonable if in case of cooperation you'll give a write access to RustCrypto admins, so it will be possible to publish updates in your absence) and on closing this repository. I can mirror code to RustCrypto and your repository can stay as the main one. (though it will be certainly inconvenient and confusing for potential contributors)
Regarding readme, I was talking about removing this part:

This might go away in the future if rust-crypto or some libraries like that split into smaller parts.

I'm going to close this issue as I'm unable to do something with it.

@mitsuhiko Is this still the same until now? This crate seemed unmaintained as it have no commit since 2018.


Prepare all the changes for v2.14

Checklist

[x] Commits are signed with Developer Certificate of Origin (DCO - learn more)

/run-e2e internal

/run-e2e internal


[build]: Setup dependabot

Create configuration file for dependabot

Are you sure @dependabot is fully enabled on this repository ?

It's not yet.


Uncaught SyntaxError

Hi.
When I include any JS file other than en_bcv_parser.min.js (even with the non-minified English file), I get this error in the JS console:

I am doing
<script src="js/it_bcv_parser.js"></script>
<script>
        var bcv = new bcv_parser;
        var b = bcv.parse("Numeri 23:19");
        alert(b.osis());
</script>

(and similar with other languages).
PS: thanks for opensourcing this, it's really useful.

It looks like the file isn't being interpreted as UTF-8. If you change your script tag to read:
<script src="js/it_bcv_parser.js" charset="UTF-8"></script>
Does that fix it?
I'm of two minds about including raw UTF-8 characters in the Javascript files--on one hand, it saves bandwidth, but on the other, it can lead to inconsistencies like this. Minifying the file, as you note, solves the problem by always using \uxxxx escaped characters.

@openbibleinfo Yeah, good call. That does fix it. So it's either that, or I'll just minify the JS file I need to use. I am guessing you are not thinking to include minified versions of all JS files? ;)

Since the minified files are derived directly from the js files, I wasn't planning on providing them for all the languages, no. Sorry. :)

No worries ;)


Assets page updated build

Currently this PR is dependent on

[ ] #95 will need to be rebased to this after merge

This PR will have resolved a couple more issues

[ ] resolve #90
[ ] resolve #71

Close in favor of #111


Add string:split()

Changes:

Adds string.split to the string table so it can be used as a method

Fixes #191

Coverage decreased (-0.002%) to 98.018% when pulling 1beb4b2bb8e518acc6a8171c809662762faf357d on Validark:patch-1 into a69e24573aac6104d0f071e8c6d7583dd2dfae1b on LPGhatguy:master.

This causes string.split to leak outside of the actual Roblox environment! Ideally, any changes we make to existing Lua APIs should be isolated to inside the habitat if possible to minimize side effects of Lemur being run.
Instead of assigning it here, we should see if there are any tricks we can use to make callers inside the environment use our fake string table as the fallback table for strings. I know that debug.setmetatable can accomplish this globally, which is not ideal.

While I understand your sentiment, this is a highly improbable hypothetical. A user could just as easily overwrite all the string functions before running Lemur, and then get upset when Lemur (and every other library ever which deals with strings at all) breaks. I would point out that this project is for testing Roblox code. In Roblox, you cannot overwrite members of the default math/string namespaces. Nobody using this would ever dream of doing so. We are already assuming we know what byte/sub/find do. At most, a developer could reasonably wrap the original function and make it print something to the console before returning the results of the built-in function. Unless you can think of a hack, or plan on running Lemur in a separate VM, this is really not a big deal and can be easily documented with a one-line heads up. It is more important to have this work than trying to not expose string.split globally. It's perfectly fine to expose it globally in this case.


⚠ ClamAV has degraded performance

In bdd6758, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 202 ms

Resolved: ClamAV performance has improved in 3168a32 after 33 minutes.


SaintCoinach.Cmd "rawexd": "Export of QuestDefineClient failed: Unable to read beyond the end of the stream."

Since FFXIV Patch 6.3 (game version 2<IP_ADDRESS>0.0000), I've been getting an error from SaintCoinach.Cmd when I use the rawexd command: "Export of QuestDefineClient failed: Unable to read beyond the end of the stream.":
C:\saintcoinach>SaintCoinach.Cmd.exe "C:\Program Files (x86)\SquareEnix\FINAL FANTASY XIV - A Realm Reborn"
Game version: 2<IP_ADDRESS>0.0000
Definition version: 2<IP_ADDRESS>0.0000
SaintCoinach.Cmd (Version <IP_ADDRESS>)
> rawexd
Export of QuestDefineClient failed: Unable to read beyond the end of the stream.
6687 files exported, 1 failed

I first discovered this behaviour on Linux with WINE, but before reporting I verified that it also occurs on a regular Windows 10 installation on a different computer - and that's where the transcript above is from.
I'm using the latest binary release of SaintCoinach as of the time of writing (based on commit bdd2ef2).
Prior to patch 6.3, this was working without any issues, so it's quite recent.
If you need any more information, please let me know!

I have the exact same error with "exd" and "sql" commands, changing langage ("en" or "fr") doesn't help.

This looks like a bug in XivString.Decode, but the issue seems to be intermittent. I was trying to debug the issue, but it disappeared after 5 or so attempts. I'll try again later today to see if I can replicate the issue.

Cause of the issue:
Header file exist for the the file, (exh exists)
Data file does not exist (exd does not exist)
I personally don't know c very well so I cannot fix this, however we are not missing out on much as there is no actual data there.

My real problem with this bug is that it stops the sql command unlike the exd command which ignores the file.
I don't know if it possible to make sql treatment skip missing data files ?


Add project level jest config (for WallabyJS)

This PR adds a project-level jest config. I've added this so that the WallabyJS extension will work with our project. The extension requires a license but you can

get a free 2 week trial
qualify for an OSS license (which is free)

A demo of the product is here.
Mentioned in Slack here.
Demo
https://user-images.githubusercontent.com/37993418/216473103-7b36b882-07c3-403d-932e-db0f590f7705.mov

I think this would be useful!
Also, I'm liking the page Wallaby shows when clicking the extension:
https://user-images.githubusercontent.com/3683420/216625667-01e34418-6c29-4c92-b174-ff601e6cc18e.mov
I'm pretty sure it would help users find things and debug their setup if we did something like this.


multiline output

I would like to have the following output for ansiweather -f 3:
 Rzeszów forecast:
- Fri Jul 15: 23/14 °C
- Sat Jul 16: 23/11 °C
- Sun Jul 17: 21/9 °C

I tried using dashes:\\n\033[34m- in the config, but the output is:
 Rzeszów forecast: Fri Jul 15: 23/14 °C
- Sat Jul 16: 23/11 °C
- Sun Jul 17: 21/9 °C

Try to set following in .ansiweatherrc:
forecast_text:forecast:\n\r
delimiter:\033[35m
This is a bit odd but works if you can live without delimiters.


Title grapper

Function to fetch title of a youtube video, usefully for queueing up multiple tracks and getting there repective titles.

if you still need the code here is what I made for my another resource but I am not really planning to add this.
function getNameFromURL(URL, cb){
    if(getYoutubeUrlId(URL) === "")
	{
        var audioPlayer = new Howl({
                src: [URL],
                loop: false,
                html5: true,
                autoplay: true,
                volume: 0.0,
                format: ['mp3'],
                onplay: function(){
                    cb(editString(URL), audioPlayer._duration);
                    audioPlayer.pause();
                    audioPlayer.stop();
                    audioPlayer.unload();
                },
        });
    }
    else
    {
		var test = new YT.Player("trash",
        {
            height: '0',
            width: '0',
            videoId: getYoutubeUrlId(URL),
            events:
            {
                'onReady': function(event){
                    cb(event.target.getVideoData().title, test.getDuration());
                    test.stopVideo();
                    test.destroy();
                },
            }
        });
    }
}

getNameFromURL("https://www.youtube.com/watch?v=-wZR_q3_4Ag", function(name, timestamp){
    console.log(name);
});


Autostart on Centos 6

I installed Gogs on my Centos 6 machine using the "binary" guide.
I created a git user and did all the steps. I also added the gogs startup script (from https://github.com/gogits/gogs/blob/master/scripts/init/centos/gogs) to my /etc/init.d folder and added the startup script to my startup sequence using chkconfig --add gogs. The script is listed as S85gogs in:

/etc/rc2.d
/etc/rc3.d
/etc/rc4.d
/etc/rc5.d

I tested my configuration using sudo service gogs start, which starts the gogs service properly and it is reachable through my proxy in apache (yay!).
After that I rebooted my machine to see if it started automatically, but it is not auto starting. The boot.log shows that gogs starts correctly:
Starting Gogs Go Git Service: ^[[60G[^[[0;32m  OK  ^[[0;39m]
But the gogs service is still unavailable. Also a sudo service gogs status shows that my gogs service is stopped.
I have the feeling this is a permissions problem, but I can't seem to find out why. My gogs permissions are -rwxr-xr-x.  1 root root  1774 Mar 26 11:33 gogs. These are the same as the other services running at my system.
One minor detail, when my git user tries to start the service, I get the following message, not sure this is related to the problem or just because the user isn't tied to any group.
$ service gogs start
Starting Gogs Go Git Service: runuser: cannot set groups: Operation not permitted
                                                           [FAILED]

Hi, I'm not sure this is the reason Gogs fails to start :+1:

Starting Gogs Go Git Service: runuser: cannot set groups: Operation not permitted

Maybe you need to use sudo service gogs start for this.
For reboot, do you have any log from log/gogs.log? There should be some error message if Gogs itself refuse to start.

Also from some search, it might be a SELinux issue: http://unix.stackexchange.com/questions/80066/postgresql-service-start-issues

Yup, sudo service gogs start does work. I mentioned this in my original post.
The logs in the /log folder do show an error indeed. It seems that my MySQL server isn't started before my gogs service is started. There is a mysqld script in init.d, but it doesn't have an on in my chkconfig --list. Maybe this is because it is started by Plesk (which is installed on my server too).
Damn, I wish I knew more about this on Centos.

Right, does init has something like require a service to start before this one? Like systemd.

BTW, I'm using CentOS 7 with systemd and it works well for weeks so far.

Upgrading is something I had in mind for a couple of weeks now, but I am hosting a couple of sites and I do need Plesk to keep everything organized. Not sure an upgrade will go so well.
In other news, the gogs init.d script does have this:
### BEGIN INIT INFO
# Provides:          gogs
# Required-Start:    $remote_fs $syslog
# Required-Stop:     $remote_fs $syslog
# Default-Start:     2 3 4 5
# Default-Stop:      0 1 6
# Short-Description: Start gogs at boot time.
# Description:       Control gogs.
### END INIT INFO

I wonder if I can do something with the "Required-Start" from this.

Required-Start looks the right way to try.
PS: my point isn't CenOS 7, but systemd, if you would consider to switch to it. I'm not pro on this kind of thing but at least I got working solution :eyes:

Ah yes, well I will try to fiddle with the Required-Start.
As I read it, systemd is only for Centos 7?

Oops, my bad... that's so sad!

No problem, it seems solved now. I downgraded the priority from 85 to 99 and that fixed it. My Plesk control panel also had the priority 85 and that is now started before gogs.
Awesome! Thanks for the pointers!

No problem, my pleasure!


RTM NuGet package?

Hi,
it seems that you have the RTM code already in GitHub but the package is not available via NuGet yet - could you publish it? Thanks!
Regards,
-Timo

Yes, I migrated to RTM, because I could no longer compile RC2.
I can't push just yet, because I have a few breaking changes on my local branch to merge before v1.0.
I could publish some kind of 0.9.7 pre-release, if you really need to or I will publish it anyway on sunday if I can't make all of my changes.

OK, no rush. "When it's done" (or Sunday) sounds good. :)


Add warning for RHEL 8

According to
RedHat's site:

Docker is not supported in RHEL 8.

This needs to be prominently displayed so that users of the docker-compose YAML files choose an appropriate platform.

Pull requests

https://github.com/Senzing/docker-compose-demo/pull/196
https://github.com/Senzing/docker-compose-demo/pull/197


Quick Mention

Plugin Link
https://betterdiscord.app/plugin/QuickMention
Notes
There is no button in the message hover menu, it's just a blank button.
I think this is the same plugin from Vencord, that I'm using... not sure though
Vencord Plugin:
https://gist.github.com/Vendicated/8696cde7b92548064a3ae92ead84d033#QuickMention

I'm unable to replicate this. Is this still an issue?

I'm unable to replicate this. Is this still an issue?

Yes, I have attached a screenshot, I don't know if it's the same plugin as on Vencord... have you tried the one built into vencord?

Related comment: https://github.com/TakosThings/Fluent-Discord/issues/223#issuecomment-1500216539


Add a "Close Unmodified editors" (according to Git) action

There's a "Close Saved" option here, but it just closes all files that are not dirty. Some editors like IntelliJ have a "Close all unmodified" action that closes all files that have not been modified according to git. This is useful after navigating through a bunch of files and then wanting to close all those that aren't related to current changes you're making.

This came up at https://github.com/Dart-Code/Dart-Code/issues/4248 but since VS Code has built-in Git support and this isn't language-specific, it feels like something better added natively.
(Similarly, an "Open modified files" that opens all modified files according to Git could often by useful).

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

:slightly_frowning_face: In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.
Happy Coding!


Separate styles for multiple instances of a module

Is it possible to specify separate styles for multiple instances of a module?
I ask because I have two modules network#wireless and network#wired and I want the CSS selector network#disconnected to applied to the first module but not the second one.

Done in b554094c7e7d47415f91f11cec5976b5d05b9ada
In your css file you can do something like this:
#network.wireless {
	...
}
#network.wired {
	...
}


Flow 0.93: EVERYTHING is a "dynamic-export" issue all of a sudden

Flow version: 0.93
Configuration contains
[lints]
all=error

Expected behavior
No or a few errors.
Actual behavior
From zero to 21350 errors going from Flow 0.92.1 to 0.93, and ALL of them are from "dynamic-export" for a very well-maintained project with "very clean Flow types" (spent a lot of time on it and religiously update and improve everything) with just about 6,000 lines of code. I only use any for a few type casts, when Flow does not understand something. There are no other any apart from that handful(!) of type casts. I also don't use Function or Object since it was deprecated. I don't have a single "stand alone" any, only as part of type casts, so it does not propagate anywhere.
Example:
Error ┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈┈ test/chum-sync-alice-test.js:27:1

Dynamic function type [1] unsafely appears in exported ProcessComResponse [2].
This can cause importing modules to lose type coverage! (dynamic-export)

     test/chum-sync-alice-test.js
      24│     data?: mixed
      25│ |};
      26│
 [2]  27│ export type ProcessComResponse = {|
      28│     id: number,
      29│     data?: mixed,
      30│     error?: Error
      31│ |};
      32│ */
      33│
      34│ const chai = require('chai');

     /tmp/flow/flowlib_3d06aeae/core.js
 [1] 445│     static captureStackTrace(target: Object, constructor?: Function): void;

This error message does not make any sense!
None of the 21350 errors makes any sense. None of those are even close to looking suspicious or being errors.
This new "dynamic-export" check reports every single item in the entire code base! And it complains about issues with the built-in lib definitions, not even about the code.
Here is an example that shows that Flow reports its own library (where the any is located):
Error --------------------------------------------------------------------- src/access.js:279:23

Dynamic explicit 'any' [1] unsafely appears in exported async function [2]. This can cause
importing modules to lose type coverage! (`dynamic-export`)

   src/access.js:279:23
   279| export async function createObjects (
                              ^^^^^^^^^^^^^

References:
   /tmp/flow/flowlib_3d06aeae/core.js:697:91
   697|     map(callback: (currentValue: number, index: number, array: this) => number, thisArg?: any): this;
                                                                                ^^^ [1]
   src/access.js:279:14
                     v-----------------------
   279| export async function createObjects (
   280|     WriteStorage: WriteStorageApi,
   281|     accessRequests: Array<SetAccessParam>
   282| ): Promise<Array<VersionedObjectResult<AccessObj | IdAccessObj>>> {
        ----------------------------------------------------------------^ [2]

The createObjects function on my side of the code has a single array.map(someDate => someFunction(someData)) statement whose result is returned and no any anywhere, it all has concrete types.
Workaround
After adding dynamic-export=off to the [lints] section of .flowconfig all 21350 errors are gone.

cc @dsainati1

Hi. I'm sorry you've been having trouble with the new lint. This is in fact working as intended, but I can see how it is confusing. What's going on here is that the types you're exporting are defined in our libdefs to include any. In your first example, for instance, the type Error is defined in core.js to have the static function static captureStackTrace(target: Object, constructor?: Function): void, so you are implicitly exporting an any type here. The intention was not for this new lint to be enabled for all the files in a codebase, as it is quite noisy as you have seen. Rather we hoped that users would turn it on on a per-file or even per-line basis using flowlint comments where they wanted to be especially sure that no any types were exported from files. I will update the documentation to reflect this.

@dsainati1 dynamic-export still is working wrong, it seems.

Hmm this second example definitely is wrong. I will look into this and get back to you.

I think the lint is complaining because we implicitly model this types as any. Unfortunately the new version just released, but I will try to get the fix for this into the next one. In the mean time, I'd just say turn this off.

@dsainati1 Can we exclude this lint from the "all" setting?

Yeah I am working on a couple of improvements to the lint; and will include that as one of them.

Okay the referenced issue should fix the issue with being unable to export functions and classes; as far as the libdefs triggering the lint; I'm collecting data on this at the moment. It's possible we want this behavior in some scenarios.

Are there any plans to disable this by default (as part of [lints] all=error)?
In our experience, any flow-typed library will trigger tons of these issues.

I think it's pretty confusing for all=error to not actually set all the lints to be errors, so I don't know that we would want to ignore it as part of that setting. I do recognize though that the lint is difficult to use at the moment and I have some in progress work to make it less noisy (and hopefully easier to enable).

I think it's pretty confusing for all=error to not actually set all the lints to be errors

There is some reasonable precedent for this. -Wall, for example, does not treat all warnings as errors. There is -Wall -Wextra for that, but even that does not treat 100% of warnings as errors.
Clang has a non-standard -Weverything flag, but admonishes users to never actually use it, explaining that it is designed for implementors only.
I think it's fair to imagine "all" as an alias for "all the lints that are reasonable to enable at once."

This was addressed in 91a49518d6053880b8b162a7a1a5aa5962ed4ea4, which will come out shortly with v0.98


chore(deps): update dependency prettier to v2.7

Description
I also ran pnpm run format, no files affected 👍
Additional context

What is the purpose of this pull request?

[ ] Bug fix
[ ] New Feature
[ ] Documentation update
[x] Other

Before submitting the PR, please make sure you do the following

[x] Read the Contributing Guidelines.
[x] Read the Pull Request Guidelines and follow the Commit Convention.
[x] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[x] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[ ] Ideally, include relevant tests that fail without this PR but pass with it.

current CI errors are not related


ControlNet Unit 10. but In the ps plugin there is only one ControlNet ?

ControlNet Unit 10. but In the ps plugin there is only one ControlNet ? v1.2.4

This one doesn't work

For your first issue, I believe it has to do with localization since you are using the Chinese interface. I will push an update to fix this soon.
Can you provide more information on how you are using the interrogate button? Also, please post the error message you receive from Auto1111’s cmd. Make sure that you are using the rectangular marquee tool to make a selection before clicking on the interrogate button.

For your first issue, I believe it has to do with localization since you are using the Chinese interface. I will push an update to fix this soon.
Can you provide more information on how you are using the interrogate button? Also, please post the error message you receive from Auto1111’s cmd. Make sure that you are using the rectangular marquee tool to make a selection before clicking on the interrogate button.

After clicking the interrogate button, Auto1111's cmd does not have any information prompt, only the ps plug-in progress bar is going, very slow, to 100% is stuck, as if there is no API call just the first part of the progress bar change, Auto1111's cmd can not have any information output

@XiaoCC, could you please visit this link: http://<IP_ADDRESS>:7860/config ? After the page has completely loaded, save the file as config.json and upload it. I'll check to see if it has the right controlnet settings.

@XiaoCC, could you please visit this link: http://<IP_ADDRESS>:7860/config ? After the page has completely loaded, save the file as config.json and upload it. I'll check to see if it has the right controlnet settings.

config.json.zip

The selected lora cannot be unselected

Yes I've checked your config file, everything seems right, this is where the plugin gets the value from the config:
What happens when you click on the Refresh button? Does it refresh the ControlNet tab?

The selected lora cannot be unselected

Yes, that's Intended, selecting a lora will just add it to the prompt. but let’s try to stay focused on the first issue in this post.
👌

https://github.com/AbdullahAlfaraj/Auto-Photoshop-StableDiffusion-Plugin/assets/7299222/dc64908c-968d-42be-bbc1-aab337e0d30f

https://github.com/AbdullahAlfaraj/Auto-Photoshop-StableDiffusion-Plugin/assets/7299222/0403dbf5-e51c-43c5-91ac-545b2b3da9b9
click on the Refresh button ,can refresh the ControlNet tab

click on the Refresh button ,Auto1111's cmd output

There is a null
click on the Refresh button ,Auto1111's cmd output

Maybe the UI is initialized to read the config when the config is not yet loaded (50M) remote sd-url slow to download the config?

getControlNetMaxModelsNum() -->  catch

This interface also has （ "control_net_max_models_num": 10,）.
Responses are very small

This interface also has a.
Responses are very small

I changed these 2 things and now it loads properly

@XiaoCC, nice work! I think you might be using an extension that exposes the settings through the /state endpoint since I don’t see that particular endpoint in my Auto1111. If the issue is in requesting the config file, then it also means your hi-res fix upscaler menu should be empty on your end.
These were written months ago before having an easy way to access them through the API. I will try to get rid of this dependency by the next update.

@XiaoCC, nice work! I think you might be using an extension that exposes the settings through the /state endpoint since I don’t see that particular endpoint in my Auto1111. If the issue is in requesting the config file, then it also means your hi-res fix upscaler menu should be empty on your end. These were written months ago before having an easy way to access them through the API. I will try to get rid of this dependency by the next update.

my hi-res fix upscaler menu empty
I had to add the list to the code first
I didn't find the right interface to get the list
The previous error was because the /config data was too large
The request was not complete every time
So catch

The list is composed from latent upscalers list + the output of this end points.
http://<IP_ADDRESS>:7860/docs#/default/get_upscalers_sdapi_v1_upscalers_get

I use the stable diffusion modified by 秋葉aaaki
I have the interface /state/config.json


Added Coverage Action

JaCoCo Test Coverage Summary Statistics

Coverage Type
Coverage

Coverage:
16.63%

Branches:
28.76%

Code Coverage Summary [using JaCoCo]

Coverage Type
Coverage

Coverage:
16.63%

Branches:
28.76%


[Change Request] Include .ini files for ALT sound packages

Right now they are ignored but delivered with some packages.
Maybe skipping them is not a good idea.

Fixed with 3.6.0


[FEATURE] Training accuracy

Hello,
When using timm with and without data augmentation and on different datasets (Imagenet, Cifar ...) with different models (ConvMixer, ConvNext ...) I end up having a lower test loss than train one. Furthermore, I added a train accuracy metric to compare both train and test accuracies and I have a much higher test accuracy than train one. Is it planned to add an official train accuracy measurement on timm ?  Can I send a pull request for that even though I might not have implemented it in a rigorous way ?
Thank you.

Train accuracy isn't very useful with heavy augmentation and regularization, what insight would it provide that the loss doesn't?

Thank you for your answer. I agree that train loss could be sufficient although it costs nothing to have training accuracy, but that doesn't answer why train loss is higher than test one in timm. Could you give us a hint ?

@K-H-Ismail train potentially includes smoothing or other regularization, and train augmentations often results in heavily modified, ie 'challenging' images so it makes sense that train accuracy is often lower and loss can be much higher than validation, the goal is to get a good validation accuracy.


fix: fix expansion order for fn-like macros and attributes in token descending

Second attempt(now with a test 🎉).
Fixes https://github.com/rust-analyzer/rust-analyzer/issues/10115

bors r+


fix: peer dependency warning

Fixed npm WARN ng-pick-datetime requires a peer of<EMAIL_ADDRESS>but none is installed.

@dintecomfl I've implemented this on this fork: https://github.com/danielmoncada/date-time-picker


[Question] How can I investigate server properties?

Thanks for your package, which I found at the tutorial https://www.freecodecamp.org/news/cjn-how-to-connect-your-microsoft-sql-server-docker-container-with-azure-data-studio/.
How can I execute the following statement found at https://docs.microsoft.com/fr-fr/sql/linux/quickstart-install-connect-docker?view=sql-server-ver15&pivots=cs1-bash ?
SELECT @@SERVERNAME,
    SERVERPROPERTY('ComputerNamePhysicalNetBIOS'),
    SERVERPROPERTY('MachineName'),
    SERVERPROPERTY('ServerName')

I tried putting this at one line
SELECT @@SERVERNAME, SERVERPROPERTY('ComputerNamePhysicalNetBIOS')

but I got
Error: Incorrect syntax near the keyword 'SELECT'.

If select statements against tables are working then it's possible the underlying library being used does not support reading server variables.


Possible to support CoffeeScript varargs?

Hey Bruno,
We'd like to apply have a wrapper function that works with different numbers of arguments — and takes the callback last. We can use apply_ to call the inner function dynamically, which is nice, but I'm not able to figure out how to declare this wrapper function in a way that works with Streamline.
Ideally, we could achieve it with CoffeeScript's varargs (splats):
wrapper = (args..., _) ->
    original.apply_ _, @, arguments

Streamline unfortunately rejects this, because the compiled JS is invalid today:
wrapper = function() {
  var args, _, _i;
  args = 2 <= arguments.length ? __slice.call(arguments, 0, _i = arguments.length - 1) : (_i = 0, []), _ = arguments[_i++];
  return original.apply_(_, this, arguments);
};

Do you think it'd be possible/easy to support this compilation? Thank you as always!
Edit: I should also say that we'd of course have some logic inside the wrapper function, e.g. try-catching the original.apply_.
/cc @ryanwe @chanadian @gasi

This is tricky. The following works:
wrapper = (fn) ->
	() ->
		args = Array.prototype.slice.call arguments, 0, arguments.length - 1
		args.splice 0, 0, arguments[arguments.length - 1]
		fn.apply this, args

foo = wrapper (_, a1, a2) ->
    console.log 'arguments=', arguments, 'a1=' + a1, 'a2=' + a2
    setTimeout _, 1
    console.log 'done'

foo 'test1', 'test2', 'test3', _

Ideally we should be able to write
foo = (args..., _) ->
    # foo body

But this requires a change to the streamline transform. It needs to recognize the special pattern that the CS compiler generates for splats. I can give it a try.

Given what we arrived at in #258, this feature request is less important for us.
It'd still be awesome to have at some point, but don't feel like you need to prioritize this.
Thanks Bruno!

Since the wrapping case is solved btw, here is a more straightforward test case:
echo = console.log

foo = (things..., _) ->
    echo 'foo: beginning'

    for thing in things
        setTimeout _, 1
        echo 'foo:', thing

    echo 'foo: done'

var echo, foo,
  __slice = [].slice;

echo = console.log;

foo = function() {
  var thing, things, _, _i, _j, _len;
  things = 2 <= arguments.length ? __slice.call(arguments, 0, _i = arguments.length - 1) : (_i = 0, []), _ = arguments[_i++];
  echo('foo: beginning');
  for (_j = 0, _len = things.length; _j < _len; _j++) {
    thing = things[_j];
    setTimeout(_, 1);
    echo('foo:', thing);
  }
  return echo('foo: done');
};


Clicking the link under "Next Steps" sends me to the 1.1 docs for the Windows quickstart

Is there a link that would keep someone going through the docs on the v1.2 version of the docs?  Perhaps direct to the quickstart on Linux

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

ID: ef994221-bfeb-9aa0-4ee1-5a264b4d921f
Version Independent ID: 51f776a0-4460-90d8-80de-5c444ca0adff
Content: What is Azure IoT Edge
Content Source: articles/iot-edge/about-iot-edge.md
Service: iot-edge
GitHub Login: @kgremban
Microsoft Alias: kgremban

@kgremban fyi

Thanks for the feedback! We are currently investigating and will update you shortly.

The page  or the content is not available for the 1.2 version. So the 'Next Steps' is redirecting to default 1.1 version page.

Under 1.2 version , we only have Quickstart for Linux Device.

@micahl Satish is right in that there's no 1.2 version of the Windows quickstart to link to, so readers are forced into the 1.1 version of the docs. However, what I can do is update the Overview next steps to point to both quickstarts, so those who choose the Linux link will maintain their 1.2 view.

Thanks, @kgremban.  That sounds like a good approach.


Cannot change Tab if embedded in Accordion

On ipywidgets master:
If a Tab widget is a child of an Accordion widget, switching between tabs by clicking does not work:
from ipywidgets import Accordion, Box, Tab
t = Tab([Box(), Box()])
Accordion([t])

Changing tabs programmatically (t.selected_index = 1) still works as expected.

The problem is that we are not using phosphor to attach accordion children: https://github.com/ipython/ipywidgets/blob/master/jupyter-js-widgets/src/widget_selectioncontainer.ts#L152.
Working on it...

This is the subject of #983.

This now works in master.


can't add to an existing table

When trying to add another batch, with vectors, to an existing table, I get this error:
from flupy import flu
import numpy as np
from tqdm import tqdm

batch_size = 50

# Convert DataFrame to list of tuples
data = list(new_df[['id', 'content', 'metadata']].itertuples(index=False, name=None))

# Define the starting record index
start_index = 0

# Adjust the data list to start from the desired record
data = data[start_index:]

uploaded_rows = 0

# Iterate over the dataset in chunks
for chunk_ix, chunk in enumerate(tqdm(flu(data).chunk(batch_size))):

    records: List[Tuple[str, np.ndarray, Dict]] = []

    # Extract ids, contents, and metadata from the chunk
    ids, contents, metadatas = zip(*chunk)

    # Create embeddings for the current chunk
    embedding_chunk = co.embed(texts=contents, input_type="search_document", model="embed-english-v3.0").embeddings
    #embedding_chunk = embeddings.embed_documents(contents)
    # Enumerate the embeddings and create a record to insert into the database
    for row_ix, (id, content, embedding, metadata) in enumerate(zip(ids, contents, embedding_chunk, metadatas)):

        # Prepare the record with id, embedding, and metadata
        records.append((id, embedding, metadata))

    # Perform upsert operation for the current batch
    docs.upsert(records)

    # Update the count of uploaded rows
    uploaded_rows += len(records)

print(f"Total uploaded rows: {uploaded_rows}")

12 frames
InvalidColumnReference: there is no unique or exclusion constraint matching the ON CONFLICT specification

The above exception was the direct cause of the following exception:

ProgrammingError                          Traceback (most recent call last)
[/usr/local/lib/python3.10/dist-packages/sqlalchemy/engine/default.py](https://localhost:8080/#) in do_execute(self, cursor, statement, parameters, context)
    920
    921     def do_execute(self, cursor, statement, parameters, context=None):
--> 922         cursor.execute(statement, parameters)
    923
    924     def do_execute_no_params(self, cursor, statement, context=None):

ProgrammingError: (psycopg2.errors.InvalidColumnReference) there is no unique or exclusion constraint matching the ON CONFLICT specification

works fine if i send it into a new table. appreciate any advice how to resolve it. thanks!

i have a table with vectors created with vecs first, in one go. but every time when try to add new vectors later to the same table i get this error. i normally circumvent this issue by creating a new table and then merging the old with the new one.

when try to add new vectors later to the same table i get this error.

Are you adding the new vectors using the vecs client?
which version of vecs are you using?

Could you please put together a minimal reproducible example so I can try to track down what's going wrong?

yes. adding new vectors with a vecs client, the same code, to the table earlier created also with vecs client.
0.4.2
DB_CONNECTION = "postgresql://<>"

# create vector store client
vx = vecs.create_client(DB_CONNECTION)

docs = vx.get_or_create_collection(name="table_name", dimension=1024)

this is my dataframe that i then convert into a list and upsert
id | content | metadata
-- | -- | --
4855723_1 | This opinion is subject to administrative corr... | {'opinion_id': '4855723_1', 'date_filed': '202...
4858139_1 | UNPUBLISHED UNITED STATES COURT OF APPEALS FOR... | {'opinion_id': '4858139_1', 'date_filed': '202...
4858757_1 | NOT PRECEDENTIAL UNITED STATES COURT OF APPEAL... | {'opinion_id': '4858757_1', 'date_filed': '202...
4858757_2 | constitutes a “conviction” under 21 U.S.C. § 8... | {'opinion_id': '4858757_2', 'date_filed': '202...
4858757_3 | his conviction for a crime that an intervening... | {'opinion_id': '4858757_3', 'date_filed': '202...

here is my upsert code:
from typing import List, Dict, Tuple
from flupy import flu
import numpy as np
from tqdm import tqdm

batch_size = 50

# Convert DataFrame to list of tuples
data = list(new_df[['id', 'content', 'metadata']].itertuples(index=False, name=None))

# Define the starting record index
start_index = 0

# Adjust the data list to start from the desired record
data = data[start_index:]

uploaded_rows = 0

# Iterate over the dataset in chunks
for chunk_ix, chunk in enumerate(tqdm(flu(data).chunk(batch_size))):

    records: List[Tuple[str, np.ndarray, Dict]] = []

    # Extract ids, contents, and metadata from the chunk
    ids, contents, metadatas = zip(*chunk)

    # Create embeddings for the current chunk
    embedding_chunk = co.embed(texts=contents, input_type="search_document", model="embed-english-v3.0").embeddings
    #embedding_chunk = embeddings.embed_documents(contents)
    # Enumerate the embeddings and create a record to insert into the database
    for row_ix, (id, content, embedding, metadata) in enumerate(zip(ids, contents, embedding_chunk, metadatas)):

        # Prepare the record with id, embedding, and metadata
        records.append((id, embedding, metadata))

    # Perform upsert operation for the current batch
    docs.upsert(records)

    # Update the count of uploaded rows
    uploaded_rows += len(records)

print(f"Total uploaded rows: {uploaded_rows}")

let me know if you need anything else.
vecs library is great, simple and robust. thanks for making it. this is where i deployed it helpmefindcase.com

this slipped off my todo somehow, sorry!
Are you still experiencing this error or did you get it resolved

what i ended up doing is deleting the old index (hnsw), adding new rows, and then re-indexing again.


"adding profile for Nitya Narasimhan"

Docs Build status updates of commit cf4aaaa:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

advocates/media/profiles/nitya-narasimhan.png
:white_check_mark:Succeeded
View

advocates/nitya-narasimhan.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 2f049ef:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

advocates/media/profiles/nitya-narasimhan.png
:white_check_mark:Succeeded
View

advocates/nitya-narasimhan.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Add Coverity scan for static code analysis

I'm using BouncyCastle in my C# project (https://github.com/Pro/dkim-exchange) in combination with Coverity (http://www.coverity.com/, free for open source) to test my code for flaws and problems. Coverity did find about 150 problems in the BouncyCastle code (i.e., race conditions, integer overflows, infinite loops, bad bit shift operations, null dereferences, ...).
I would suggest that you submit your builds to Coverity to have some (static) code checking.
If you need help setting it up just write here or look at my project, especially:
https://github.com/Pro/dkim-exchange/blob/master/coverity_build.bat
and
https://github.com/Pro/dkim-exchange/blob/master/travis.proj

Thanks, we'll take a look.


Playground hangs with Unexpected token '<', "<!DOCTYPE "... is not valid JSON

I've been experiencing frequent hangs in the Playground, especially when I try to run tests, rustfmt, generate a share link, or run a program.
I'm not sure if anyone else has noticed this issue, but it's been happening for a while now, and I wanted to bring it to your attention. As of now, the Playground has hung again, and I'm unable to do anything.
PS: the code I am running on the playground compiles on my machine though.
https://github.com/user-attachments/assets/b3730c40-0540-4946-a23c-c693279c2eee

still doesn't work 😩

seems to work now - thank you

Again starting to see the error, but it's a bit different this time

I am also experiencing this today. sounds awkward since I am visiting some shared Url that used to work before.


Adding in Amazon Linux 2023

Fixes issue #105
Added in the capability to deploy Amazon Linux 2023.
This required making adjustments for 2023 not having cron installed by defualt.

/do-e2e-tests

/do-e2e-tests


Added a WrappedTokenUnsealer - fixes #8

This allows users to unseal Gatekeeper with a token created and stored with Vault response wrapping, by providing the temp token which wraps the stored token. Implements the functionality asked for here https://github.com/ChannelMeter/vault-gatekeeper-mesos/issues/8 without removing the Cubbyhole unseal method.

Awesome, mind if I add you to a contributors section in the readme?

That'd be great, go for it


Rancher panic if helm release secret is empty

see #37023

Closing, because the pull-request is based on a wrong commit


[Stdlib] Multisig module and service

Two modules related to multi-party proposing and authorizing of events.
MultiSig: A multi-authentication module/framework for triggering arbitrary actions with n-of-m authentication.

[x] Account Brick: need to brick the authkey to prevent the sponsor of the account from making changes.
[x] Initialize Governance of signatures, thresholds, and withdraw capability
[x] Lazy events can be triggered my the last voter to cross threshold. Can return a withdraw capability.
[x] Updating governance is just an instance of a MultiSig Action. Using the PropGov type.
[x] Tranasctional tests

MultiSigPayment: An implementation of the MultiSig authorization. Non-custodial multisig implementation for payments.

[x] Imports MultiSig, and creates the initialization and handler for payments.
[x] Types and logic are isolated, tally returns if passed, and withdraw capability.
[x] Is a Root Security service, and has billing enabled. Expose to Epoch Boundary.
[x] Transactional Tests

Because of deep refactor to VoteLib the commits are included here: https://github.com/0LNetworkCommunity/libra/pull/1249


Spread tests for tutorial

Overview

This PR creates a testable tutorial, in a similar fashion as it is done in rockcraft and charmcraft, using spread and sphinx. For that, it uses two plugins in sphinx, one to parse Markdown and one to build into Markdown, so it should work with discourse.
The tutorial had to be adapted to use env variables instead of just place holders. The scripts used were copied from the project charmcraft.
As src-docs is not used in NetBox (as the code is really in paas-charm), the src-docs directory was reused for it.
Rationale

Juju Events Changes

Module Changes

Library Changes

Checklist

[x] The charm style guide was applied
[x] The contributing guide was applied
[x] The changes are compliant with ISD054 - Manging Charm Complexity
[x] The documentation is generated using src-docs
[x] The documentation for charmhub is updated.
[x] The PR is tagged with appropriate label (urgent, trivial, complex)

I like the use of markdown instead of rst and it seems that we can include the code anyway so perhaps we use markdown at least in our docs?

I think if everything is displayed correctly in discourse (pending to see), we can use this for all our charms.


Advancement Pre Requirements + Ability Score Improvement

Something else that could be added together with the features made by arbron on pull request #1627
Are the option to better accommodate classes like the Warlock and it's Eldritch Invocations  since some of them require certain levels such as "Ascendant Step" which requires 9th level some that require a certain Pact Boon such as "Aspect of the Moon" which requires the "Pact of the Tome", some can even ask for a mix of both, they can also ask for cantrips (But it's just mostly if not only Eldritch Blast), so requirements of levels and features would be neat, cantrips/spells requirements would be a nice extra, definitely not something really needed tho.
And also have Ability Score Improvement feature built in, just like the Hit Points are built in
Sadly unlike arbron I can't really code so I can't actually contribute besides just giving a suggestion, but hopefully this also gets added :)

Actually, you can select another totem in this case, see the text:
At 6th level, you gain a magical benefit based on the totem animal of your choice. You can choose the same animal you selected at 3rd level **or a different one.**

It would be useful for Warlock Invocations, which can require a certain level in the class and/or a specific Pact Boon

Actually, you can select another totem in this case, see the text:
At 6th level, you gain a magical benefit based on the totem animal of your choice. You can choose the same animal you selected at 3rd level or a different one.

That was my bad :p I said it mostly out of my memory after chatting about the it with MaxPat over Foundry's discord and also some other people, but yeah there are still certain features that require a certain level and some that require a certain other choice still, some that require certain levels such as "Ascendant Step" which requires 9th level some that require a certain Pact Boon such as "Aspect of the Moon" which requires the "Pact of the Tome", and some that even go as far as requiring a mix of both, Boon and Levels, some even ask for a specific cantrip (Most if not all of them ask only for Eldritch Blas tho), so the point still stands, just not an ideal example :d

It would be useful for Warlock Invocations, which can require a certain level in the class and/or a specific Pact Boon

Some also have requirements like Maddening Hex from XTE:
Prerequisites: 5th level; Hex spell or a warlock feature that curses.
Depending on the warlock subclass, it can also fulfill the prereq depending on how its set up.

At least level prerequisites are now covered, and the ASI advancement also exists now. Additional prerequisite requirements are covered by the linked issue.


[WIP]: file existence macros

Assumes that contents of test.yaml are:
exists:
    site_packages:
        - numpy
    lib:
        - libcurl
    include:
        - xtensor
        - xtensor.hpp
        - xtensor/xarray.hpp
    bin:
        - f2py
        - f2py3
        - curl-config
    cmake_find:
        - xtensor
    pkg_config:
        - xtensor
    file:
        - ssl/cacert.pem
        - ssl/misc
    glob:
        - doc/**/Copyright.txt

Things to consider:
-- setting return code as non-zero when test fails
-- more platform specific checks

for libraries, we should also check the name with prefix (e.g. if you put:
library:
- curl

it should check for libcurl, too.

@wolfv According to the snippet posted in the first comment of this PR, I assumed that one would enter libcurl in the lib key only. Are we expecting just curl instead?


kata-pkgsync: Add OBS to Packagecloud sync tool

Add kata-pkgsync as the OBS to Packagecloud sync tool.
Fixes: #506

/cc @jcvenegas @jodh-intel

Thanks @jodh-intel  for taking the time to review. I am going to address those points.
Here's an extract of output. You can follow up with a PR if you see improvements to this :)
›$ ./kata-pkgsync -delete config-mine.yaml
INFO[0000] Retrieving list of available files            Packagecloud repo=katacontainers/testing
 12 / 12 [======================================================================================] 8s
INFO[0008] Retrieving packages info                      OBS project="home:katacontainers:releases:x86_64:master"
 88 / 88 [=====================================================================================] 40s
INFO[0049] Found 88 packages                             OBS project="home:katacontainers:releases:x86_64:master"
INFO[0049] Downloading from OBS (1 files)                pkg=kata-containers-image repo=xUbuntu_18.04
 1 / 1 [================================================================================] 100.00% 5s
INFO[0054] Uploading to Packagecloud (1 files)           distro=ubuntu/bionic pkg=kata-containers-image
INFO[0083] Downloading from OBS (1 files)                pkg=ksm-throttler repo=xUbuntu_18.04
 1 / 1 [================================================================================] 100.00% 2s
INFO[0086] Uploading to Packagecloud (1 files)           distro=ubuntu/bionic pkg=ksm-throttler
INFO[0091] Downloading from OBS (2 files)                pkg=linux-container repo=xUbuntu_18.04
 2 / 2 [================================================================================] 100.00% 2s
INFO[0093] Uploading to Packagecloud (2 files)           distro=ubuntu/bionic pkg=linux-container

[---- CUT ----]

INFO[0958] Uploading to Packagecloud (2 files)           distro=debian/stretch pkg=shim
WARN[0965] Repo not supported by Packagecloud            OBS Repo=CentOS_7 package=kata-containers-image
WARN[0965] Repo not supported by Packagecloud            OBS Repo=CentOS_7 package=ksm-throttler
WARN[0965] Repo not supported by Packagecloud            OBS Repo=CentOS_7 package=linux-container
WARN[0965] Repo not supported by Packagecloud            OBS Repo=CentOS_7 package=proxy
WARN[0965] Repo not supported by Packagecloud            OBS Repo=CentOS_7 package=qemu-lite
WARN[0965] Repo not supported by Packagecloud            OBS Repo=CentOS_7 package=qemu-vanilla
WARN[0965] Repo not supported by Packagecloud            OBS Repo=CentOS_7 package=runtime
WARN[0965] Repo not supported by Packagecloud            OBS Repo=CentOS_7 package=shim
INFO[0965] Sucessfully transferred 119 files             OBS project="home:katacontainers:releases:x86_64:master" Packagecloud Repo=katacontainers/testing
INFO[0965] Retrieving packages info                      OBS project="home:katacontainers:releases:x86_64:stable-1.5"
 88 / 88 [=====================================================================================] 35s
INFO[1000] Found 88 packages                             OBS project="home:katacontainers:releases:x86_64:stable-1.5"
INFO[1000] All 1 files already on Packagecloud           OBS Repo=xUbuntu_18.04 package=kata-containers-image
INFO[1000] All 1 files already on Packagecloud           OBS Repo=xUbuntu_18.04 package=ksm-throttler
INFO[1000] All 2 files already on Packagecloud           OBS Repo=xUbuntu_18.04 package=linux-container

[---- CUT ----]

INFO[1035] All 1 files already on Packagecloud           OBS Repo=Debian_9 package=qemu-lite
INFO[1035] All 1 files already on Packagecloud           OBS Repo=Debian_9 package=qemu-vanilla
INFO[1035] All 2 files already on Packagecloud           OBS Repo=Debian_9 package=runtime
INFO[1035] All 2 files already on Packagecloud           OBS Repo=Debian_9 package=shim
WARN[1035] Repo not supported by Packagecloud            OBS Repo=CentOS_7 package=kata-containers-image
WARN[1035] Repo not supported by Packagecloud            OBS Repo=CentOS_7 package=ksm-throttler
WARN[1035] Repo not supported by Packagecloud            OBS Repo=CentOS_7 package=linux-container
WARN[1035] Repo not supported by Packagecloud            OBS Repo=CentOS_7 package=proxy
WARN[1035] Repo not supported by Packagecloud            OBS Repo=CentOS_7 package=qemu-lite
WARN[1035] Repo not supported by Packagecloud            OBS Repo=CentOS_7 package=qemu-vanilla
WARN[1035] Repo not supported by Packagecloud            OBS Repo=CentOS_7 package=runtime
WARN[1035] Repo not supported by Packagecloud            OBS Repo=CentOS_7 package=shim
INFO[1035] Sucessfully transferred 0 files               OBS project="home:katacontainers:releases:x86_64:stable-1.6" Packagecloud Repo=katacontainers/testing
INFO[1035] Finding and deleting Packagecloud files not published on OBS  Repo=katacontainers/testing
 360 / 360 [===========================================================================] 100.00% 34s
INFO[1069] Deleted 119 files                             Packagecloud Repo=katacontainers/testing

Thanks @jodh-intel @jcvenegas
I did a first round of updates based on your reviews. Please take another look when possible.

Rebased and pushed all changes.
It would also be interesting to set up a CI task to at least build this.

@marcov - agreed. But can't you just modify the .ci/ files and the Makefile in this repo to do that?

@marcov - one other thing; this PR is going to race with #516 (so we might need to coordinate) but we need a reference to your new cmd/kata-pkgsync/README.md in this repo. If this lands overnight, I'll add it on #516...

One final thing - do you need to remove the "[DNM]" now?

Thanks again @jodh-intel . I added a make target for this and included it in .ci/test.sh
Let's see if this works
/test

Ok it made it. I just found a small thing to correct in the Makefile, not worth opening another PR. So let's
/test
again

All green!
@kata-containers/packaging - can we get some more eyes on this please? Would be great to get this landed ;)

Re-ping @kata-containers/packaging :smile:


Equipping an item doesn't close interfaces

Interface should be closed in EquipItemMessageReader

I'm taking a look at this one for you now!

Just opened a PR, I think I did what you were asking but if not I can work on it some more


bug: Coinbase funds are not spendable in zebra regtest mode.

What happened?
I expected to see this happen:
Funds received from mining rewards should be spendable by the wallet as is the case when using zcashd.
Instead, this happened:
Any transactions containing coinbase funds are rejected by zebra.
The following error is returned in zingolib's (wallet) log :
2024-12-11T23:49:16.858270Z ERROR zingolib::utils::txid: server returned invalid txid Invalid character 'i' at position 2
The following error is returned in zebrad's log:
2024-12-11T23:49:16.857789Z  INFO zebra_rpc::server::rpc_call_compatibility: RPC error: Server error: failed to validate tx: WtxId("private"), error: transaction did not pass consensus validation: transaction uses an incorrect consensus branch id in call: method = "sendrawtransaction", params = Array([String("050000800a27a726b4d0d6c2000000008e00000002e81f75bc5edf9c3500b28dd23ac213efd9deb602ed6...
What were you doing when the issue happened?
Order of operations in test:

Launch Zebra (regtest mode).
Launch Lightwalletd.
Launch Zingolib client.
Generate 101 blocks.
Shield Funds to Orchard.
Generate 100 Blocks.
Send Shielded Funds.

A test showing this behaviour  (lightwalletd_zebrad_basic_send) can be found here:  [https://github.com/idky137/zcash-local-net/blob/fcd0298ffb876570224de6dc2acdd44f7d3f205f/tests/integration.rs#L385].
Similar tests using Zcashd and Zaino can be found in the same file for comparison.
Zebra logs
2024-12-11T23:48:20.890119Z  INFO zebrad::components::tracing::component: started tracing component filter="info" TRACING_STATIC_MAX_LEVEL=LevelFilter::INFO LOG_STATIC_MAX_LEVEL=Info
2024-12-11T23:48:20.890129Z  INFO zebrad::components::tracing::component: set 'tracing.progress_bar ="summary"' in zebrad.toml to activate progress bars
2024-12-11T23:48:20.890130Z  INFO zebrad::application: Diagnostic Metadata:
version: 2.1.0+3.g568b25e
Zcash network: Regtest
running state version: 26.0.0
initial disk state version: creating.new.database
features: default,getblocktemplate_rpcs,howudoin,indicatif,progress_bar,release_max_level_info
branch: main
git commit: 568b25e
commit timestamp: 2024-12-11T16:29:44.000000000Z
target triple: x86_64-unknown-linux-gnu
rust compiler: 1.82.0
rust release date: 2024-10-15
optimization level: 3
debug checks: false
2024-12-11T23:48:20.890131Z  INFO zebrad::application: loaded zebrad config config_path=Some("/tmp/.tmp3XLNTp/zebrad.toml") config=ZebradConfig { consensus: Config { checkpoint_sync: true }, metrics: Config { endpoint_addr: None }, network: Config { listen_addr: <IP_ADDRESS>:24306, external_addr: None, network: Regtest { activation_heights: {Height(0): Genesis, Height(1): Nu6} }, initial_mainnet_peers: {"dnsseed.z.cash:8233", "dnsseed.str4d.xyz:8233", "mainnet.seeder.zfnd.org:8233", "mainnet.is.yolo.money:8233"}, initial_testnet_peers: {"dnsseed.testnet.z.cash:18233", "testnet.seeder.zfnd.org:18233", "testnet.is.yolo.money:18233"}, cache_dir: IsEnabled(false), peerset_initial_target_size: 25, crawl_new_peer_interval: 61s, max_connections_per_ip: 1 }, state: Config { cache_dir: "/tmp/.tmpSoBCc7", ephemeral: false, delete_old_database: true, debug_stop_at_height: None, debug_validity_check_interval: None }, tracing: Config { inner: InnerConfig { use_color: true, force_use_color: false, filter: None, buffer_limit: 128000, endpoint_addr: None, flamegraph: None, progress_bar: None, log_file: None, use_journald: false } }, sync: Config { download_concurrency_limit: 50, checkpoint_verify_concurrency_limit: 1000, full_verify_concurrency_limit: 20, parallel_cpu_threads: 0 }, mempool: Config { tx_cost_limit: 80000000, eviction_memory_time: 3600s, debug_enable_at_height: None }, rpc: Config { listen_addr: Some(<IP_ADDRESS>:20163), indexer_listen_addr: None, parallel_cpu_threads: 0, debug_force_finished_sync: false, cookie_dir: "/tmp/.tmpSoBCc7", enable_cookie_auth: false }, mining: Config { miner_address: Some(TransparentAddress { network_kind: Testnet, pub_key_hash: "17a95184b6b158dcb8d576fc182d9b7f14377d04" }), extra_coinbase_data: None, debug_like_zcashd: true } }
2024-12-11T23:48:20.890169Z  INFO {zebrad="568b25e" net="Regtest"}: zebrad::application: initialized rayon thread pool for CPU-bound tasks num_threads=16
2024-12-11T23:48:20.891453Z  INFO {zebrad="568b25e" net="Regtest"}: zebrad::commands::start: Starting zebrad
2024-12-11T23:48:20.891501Z  INFO {zebrad="568b25e" net="Regtest"}: zebrad::commands::start: initializing node state
2024-12-11T23:48:20.891531Z  INFO {zebrad="568b25e" net="Regtest"}: zebrad::commands::start: opening database, this may take a few minutes
2024-12-11T23:48:20.891626Z  WARN zebra_state::service::finalized_state::disk_db: could not canonicalize "/tmp/.tmpSoBCc7/state/v25/regtest": No such file or directory (os error 2)
2024-12-11T23:48:20.891638Z  INFO zebra_state::service::finalized_state::disk_format::upgrade: creating new database with the current format running_version=26.0.0
2024-12-11T23:48:20.891900Z  INFO zebra_state::service::finalized_state::disk_db: the open file limit is high enough for Zebra current_limit=1048576 min_limit=512 ideal_limit=1024
2024-12-11T23:48:20.922525Z  INFO zebra_state::service::finalized_state::disk_db: Opened Zebra state cache at /tmp/.tmpSoBCc7/state/v26/regtest
2024-12-11T23:48:20.922572Z  INFO zebra_state::service::finalized_state: loaded Zebra state cache tip=None
2024-12-11T23:48:20.922627Z  INFO zebra_state::service: starting legacy chain check
2024-12-11T23:48:20.922634Z  INFO zebra_state::service: cached state consensus branch is valid: no legacy chain found
2024-12-11T23:48:20.922681Z  INFO {zebrad="568b25e" net="Regtest"}: zebrad::commands::start: logging database metrics on startup
2024-12-11T23:48:20.922704Z  INFO zebra_state::service::finalized_state::disk_format::upgrade: marked database format as newly created running_version=26.0.0 disk_version=26.0.0
2024-12-11T23:48:20.922751Z  INFO {zebrad="568b25e" net="Regtest"}: zebra_state::service::finalized_state::disk_db: the open file limit is high enough for Zebra current_limit=1048576 min_limit=512 ideal_limit=1024
2024-12-11T23:48:20.923494Z  INFO zebra_state::service::finalized_state::disk_format::upgrade: database format is valid running_version=26.0.0 inital_disk_version=None
2024-12-11T23:48:20.923559Z  INFO {zebrad="568b25e" net="Regtest"}: zebra_state::service::finalized_state::disk_db: Total Database Disk Size: 0 B
2024-12-11T23:48:20.923570Z  INFO {zebrad="568b25e" net="Regtest"}: zebra_state::service::finalized_state::disk_db: Total Live Data Disk Size: 0 B
2024-12-11T23:48:20.923573Z  INFO {zebrad="568b25e" net="Regtest"}: zebra_state::service::finalized_state::disk_db: Total Database Memory Size: 49.2 KB
2024-12-11T23:48:20.923604Z  INFO {zebrad="568b25e" net="Regtest"}: zebrad::commands::start: initializing network
2024-12-11T23:48:20.923640Z  INFO {zebrad="568b25e" net="Regtest"}:open_listener{addr=<IP_ADDRESS>:24306}: zebra_network::peer_set::initialize: Trying to open Zcash protocol endpoint at <IP_ADDRESS>:24306...
2024-12-11T23:48:20.923680Z  INFO {zebrad="568b25e" net="Regtest"}:open_listener{addr=<IP_ADDRESS>:24306}: zebra_network::peer_set::initialize: Opened Zcash protocol endpoint at <IP_ADDRESS>:24306
2024-12-11T23:48:20.923716Z  INFO {zebrad="568b25e" net="Regtest"}: zebra_network::address_book_updater: starting the address book updater
2024-12-11T23:48:20.923886Z  INFO {zebrad="568b25e" net="Regtest"}:add_initial_peers: zebra_network::peer_set::initialize: connecting to initial peer set ipv4_peer_count=0 ipv6_peer_count=0
2024-12-11T23:48:20.923892Z  INFO {zebrad="568b25e" net="Regtest"}:add_initial_peers: zebra_network::peer_set::initialize: finished connecting to initial seed and disk cache peers handshake_success_total=0 handshake_error_total=0 outbound_connections=0
2024-12-11T23:48:20.923921Z  INFO {zebrad="568b25e" net="Regtest"}: zebra_network::peer_set::initialize: sending initial request for peers active_initial_peer_count=0
2024-12-11T23:48:20.923932Z  INFO {zebrad="568b25e" net="Regtest"}: zebrad::commands::start: initializing verifiers
2024-12-11T23:48:20.923938Z  INFO {zebrad="568b25e" net="Regtest"}:crawl_and_dial{new_peer_interval=61s}: zebra_network::peer_set::initialize: starting the peer address crawler crawl_new_peer_interval=61s outbound_connections=0
2024-12-11T23:48:20.923960Z  INFO {zebrad="568b25e" net="Regtest"}:init{config=Config { checkpoint_sync: true } network=Regtest { activation_heights: {Height(0): Genesis, Height(1): Nu6} }}: zebra_consensus::router: starting state checkpoint validation
2024-12-11T23:48:20.924109Z  INFO {zebrad="568b25e" net="Regtest"}:init{config=Config { checkpoint_sync: true } network=Regtest { activation_heights: {Height(0): Genesis, Height(1): Nu6} }}: zebra_consensus::router: initializing block verifier router tip=None max_checkpoint_height=Height(0)
2024-12-11T23:48:20.924115Z  INFO {zebrad="568b25e" net="Regtest"}: zebrad::commands::start: initializing syncer
2024-12-11T23:48:20.924135Z  INFO {zebrad="568b25e" net="Regtest"}: zebrad::commands::start: initializing mempool
2024-12-11T23:48:20.924143Z  INFO {zebrad="568b25e" net="Regtest"}: zebrad::commands::start: fully initializing inbound peer request handler
2024-12-11T23:48:20.924145Z  INFO {zebrad="568b25e" net="Regtest"}: zebrad::commands::start: spawning RPC server
2024-12-11T23:48:20.924148Z  INFO {zebrad="568b25e" net="Regtest"}: zebra_rpc::server: Trying to open RPC endpoint at <IP_ADDRESS>:20163...
2024-12-11T23:48:20.924190Z  INFO {zebrad="568b25e" net="Regtest"}:init{config=Config { checkpoint_sync: true } network=Regtest { activation_heights: {Height(0): Genesis, Height(1): Nu6} }}: zebra_consensus::router: state is not fully synced yet, remaining checkpoints will be verified during syncing
2024-12-11T23:48:20.924194Z  INFO {zebrad="568b25e" net="Regtest"}:init{config=Config { checkpoint_sync: true } network=Regtest { activation_heights: {Height(0): Genesis, Height(1): Nu6} }}: zebra_consensus::router: finished state checkpoint validation
2024-12-11T23:48:20.969673Z  INFO {zebrad="568b25e" net="Regtest"}: zebra_rpc::server: Opened RPC endpoint at <IP_ADDRESS>:20163
2024-12-11T23:48:20.969766Z  INFO {zebrad="568b25e" net="Regtest"}: zebrad::commands::start: spawning block gossip task
2024-12-11T23:48:20.969779Z  INFO {zebrad="568b25e" net="Regtest"}: zebrad::commands::start: spawning mempool queue checker task
2024-12-11T23:48:20.969782Z  INFO {zebrad="568b25e" net="Regtest"}: zebrad::commands::start: spawning mempool transaction gossip task
2024-12-11T23:48:20.969785Z  INFO {zebrad="568b25e" net="Regtest"}: zebrad::commands::start: spawning delete old databases task
2024-12-11T23:48:20.969794Z  INFO {zebrad="568b25e" net="Regtest"}: zebrad::commands::start: spawning progress logging task
2024-12-11T23:48:20.969797Z  INFO {zebrad="568b25e" net="Regtest"}: zebrad::commands::start: spawning end of support checking task
2024-12-11T23:48:20.969796Z  INFO {zebrad="568b25e" net="Regtest"}: zebrad::components::sync::gossip: initializing block gossip task
2024-12-11T23:48:20.969807Z  INFO {zebrad="568b25e" net="Regtest"}: zebrad::components::mempool::queue_checker: initializing mempool queue checker task
2024-12-11T23:48:20.969811Z  INFO {zebrad="568b25e" net="Regtest"}: zebrad::commands::start: spawning mempool crawler task
2024-12-11T23:48:20.969804Z  INFO {zebrad="568b25e" net="Regtest"}: zebra_state::config: checking for old database versions db_kind="state"
2024-12-11T23:48:20.969815Z  INFO {zebrad="568b25e" net="Regtest"}: zebrad::commands::start: spawning syncer task
2024-12-11T23:48:20.969824Z  INFO {zebrad="568b25e" net="Regtest"}: zebrad::components::mempool::gossip: initializing transaction gossip task
2024-12-11T23:48:20.969829Z  INFO {zebrad="568b25e" net="Regtest"}: zebrad::components::sync::end_of_support: Starting end of support task
2024-12-11T23:48:20.969833Z  INFO {zebrad="568b25e" net="Regtest"}: zebrad::components::mempool::crawler: initializing mempool crawler task
2024-12-11T23:48:20.969852Z  INFO {zebrad="568b25e" net="Regtest"}: zebrad::components::sync::progress: initial sync is waiting to download the genesis block sync_percent=0.000 % current_height=None
2024-12-11T23:48:20.969893Z  INFO {zebrad="568b25e" net="Regtest"}: zebra_state::config: finished old database version cleanup task
2024-12-11T23:48:20.969946Z  INFO {zebrad="568b25e" net="Regtest"}:checkpoint: zebra_consensus::checkpoint: verified checkpoint range block_count=1 current_range=(Unbounded, Included(Height(0)))
2024-12-11T23:48:20.969954Z  INFO {zebrad="568b25e" net="Regtest"}:checkpoint: zebra_consensus::checkpoint: verified final checkpoint: starting full validation final_checkpoint_height=Height(0)
2024-12-11T23:48:21.028391Z  INFO {zebrad="568b25e" net="Regtest"}: zebrad::commands::start: spawned initial Zebra tasks
2024-12-11T23:48:25.971215Z  INFO {zebrad="568b25e" net="Regtest"}: zebrad::components::mempool: enabling mempool for debugging best_tip_height=Height(0) enable_at_height=Height(0)
2024-12-11T23:48:25.971232Z  INFO {zebrad="568b25e" net="Regtest"}: zebrad::components::mempool: activating mempool: Zebra is close to the tip tip_height=Height(0)
2024-12-11T23:48:30.970630Z  INFO {zebrad="568b25e" net="Regtest"}: zebrad::components::sync::end_of_support: Release always valid in Testnet
2024-12-11T23:48:36.038926Z  INFO zebra_rpc::methods::get_block_template_rpcs: submit block accepted block_hash=block::Hash("6095670f4d9a72fec27443be51da4b330db4a494be5dac413d27e4a412bacae2") block_height="1"
2024-12-11T23:48:40.975585Z  INFO {zebrad="568b25e" net="Regtest"}: zebrad::components::mempool: resetting mempool: switched best chain, skipped blocks, or activated network upgrade tip_height=Height(1)
2024-12-11T23:48:40.975613Z  INFO {zebrad="568b25e" net="Regtest"}: zebrad::components::mempool: enabling mempool for debugging best_tip_height=Height(1) enable_at_height=Height(0)
2024-12-11T23:48:40.975616Z  INFO {zebrad="568b25e" net="Regtest"}: zebrad::components::mempool: activating mempool: Zebra is close to the tip tip_height=Height(1)
2024-12-11T23:48:40.975620Z  INFO {zebrad="568b25e" net="Regtest"}: zebrad::components::mempool: re-verifying mempool transactions after a chain fork transactions=0
2024-12-11T23:48:41.374330Z  INFO zebra_rpc::methods::get_block_template_rpcs: submit block accepted block_hash=block::Hash("437372d8a9bf638b459b59a952fdf35b5f92784dfb98d064403c3c059fb55dff") block_height="2"

...

2024-12-11T23:48:41.493397Z  INFO zebra_rpc::methods::get_block_template_rpcs: submit block accepted block_hash=block::Hash("e71a1ecb1b59f04ebd56bc17d17a27130ab119efb3c50dccd8886bba033a49ba") block_height="101"
2024-12-11T23:49:16.857789Z  INFO zebra_rpc::server::rpc_call_compatibility: RPC error: Server error: failed to validate tx: WtxId("private"), error: transaction did not pass consensus validation: transaction uses an incorrect consensus branch id in call: method = "sendrawtransaction", params = Array([String("050000800a27a726b4d0d6c2000000008e00000002e81f75bc5edf9c3500b28dd23ac213efd9deb602ed6...
2024-12-11T23:49:16.862062Z  INFO zebra_rpc::methods::get_block_template_rpcs: submit block accepted block_hash=block::Hash("fe0cc6e73aac675f18043227db81a989371db0ad3ff1d68adbadd3b1a556dc3f") block_height="102"

...

2024-12-11T23:49:16.995450Z  INFO zebra_rpc::methods::get_block_template_rpcs: submit block accepted block_hash=block::Hash("34ce6b843cdce4624ae16ab2f78fc0f37e9077ce03f1bab8df45b71b44c0d48a") block_height="201"

Thank you for running a regtest zebrad 2.1.0+3.g568b25e node!
You're helping to strengthen the network and contributing to a social good :)

Zebra Version
zebrad 2.1.0
Which operating systems does the issue happen on?

[x] Linux
[ ] macOS
[ ] Windows
[ ] Other OS

OS details
Linux works 6.1.0-28-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.119-1 (2024-11-22) x86_64 GNU/Linux
Additional information
Before [https://github.com/ZcashFoundation/zebra/pull/9063] merged a different error was being hit where any block containing  transactions spending coinbase funds were rejected. This is no longer the case but the transaction withing the blocks still are.
*NOTE: When the same test is run with Zaino instead of Lightwalletd the Following Error is returned by Zaino:
called Result::unwrap()on anErrvalue: CompleteAndBroadcast(Broadcast(Broadcast("Send Error: status: Internal, message: \"Error: JsonRPC Client Error: Error: Serialization/Deserialization Error: missing fieldresult at line 1 column 202\", details: [], metadata: MetadataMap { headers: {\"content-type\": \"application/grpc\", \"date\": \"Fri, 06 Dec 2024 15:36:08 GMT\", \"content-length\": \"0\"} }")))

Transparent outputs in transactions spending coinbase inputs is now allowed on Regtest in https://github.com/ZcashFoundation/zebra/pull/9085, but the logs would indicate that the rejected transactions are using the wrong consensus branch id. Switching from NU6 to NU5 or NU5 to NU6 could be a quick fix.

Thanks for looking into this. One of our wallet devs will have a look at this this week.
Its interesting that this works for zcashd but not zebrad though, but maybe there are stronger tx acceptance rules in zebrad?

Hey,
I think we may have solved this, I'm not sure 100% what it was exactly but there was a part of zcash-local-net that had not been updated for. Im still running tests but so far everything is looking good.
I'm sorry if you have wasted time looking into this for us.
I think it has possibly highlighted some bugs in other codebases though.
We have run this test using lwd-zcashd, lwd-zebrad, zaino-zcashd and zaino-zebrad and found the following behaviour:

zcashd accepts the tx where zebrad does not.
lwd does not pick up on the rejected tx from zebra, but it returns an incorrect txid which the wallet then discards.
zaino picks up the rejected tx but returns the underlying server error instead of converting it to a tonic status.

I will post this in the discord as it seams less to do with zebra, and will be adding a fix for zaino's bad behaviour.


Update microsoft-365-business-faqs.md

fixed typo

@Sirkkuw - Can you please assist to check, approve and merge the content of this PR?
Thank you.


IMPORTANT: fix unfriendly user interface for var specs

I think our new var_specs interface is unnacceptably unfriendly to new users.
Old situation
https://github.com/sodascience/metasyn/blob/516772381741339cf409d4cc13ccbe2f094f4b2d/examples/basic_example.py#L3
https://github.com/sodascience/metasyn/blob/516772381741339cf409d4cc13ccbe2f094f4b2d/examples/basic_example.py#L23-L26
https://github.com/sodascience/metasyn/blob/516772381741339cf409d4cc13ccbe2f094f4b2d/examples/basic_example.py#L29
Current situation
https://github.com/sodascience/metasyn/blob/73c78813144b2a85043eda0e01d9ac774d0fbdab/examples/basic_example.py#L3-L5
https://github.com/sodascience/metasyn/blob/73c78813144b2a85043eda0e01d9ac774d0fbdab/examples/basic_example.py#L25-L28
https://github.com/sodascience/metasyn/blob/73c78813144b2a85043eda0e01d9ac774d0fbdab/examples/basic_example.py#L36
Options
We need to give starting users more simplicity.
Options:

Write conversion method from dict to list of varconfigs that gets called automatically
Export varconfig in metasyn so you only need one import line AND unnest varconfig / distributionspec so we don't need to ALSO import DistributionSpec. It's really too nested now for users.

Let's discuss how to fix this

There is no technical problem here:
MetaFrame.fit_dataframe(df, var_specs=[{"name": "PassengerId", "dist_spec": {"unique": True}}])

Should give the same results. So it's more how we want to present it in the tutorial. Personally I prefer the import route, because it is more explicit in what actually happens and less chance to mess up something in the dictionary (by misspelling). Unnesting could be an option, but I kind of do feel the nesting makes sense..

@qubixes and I just had a brainstorm and we propose about the following UI (ignore the ugly type annotations included for our memory):

from metasyn import MetaFrame, VarSpec as VS, demo_dataframe
from metasyn.distribution import MultinoulliDistribution, PoissonDistribution
from metasyn.privacy import BasicPrivacy
from metasyncontrib.disclosure import DisclosurePrivacy

my_df = demo_dataframe("fruit")
not_sensitive = BasicPrivacy()
my_var_specs = [
    VS("ID", distribution="uniform", unique=True),
    VS("fruits", distribution=MultinoulliDistribution),
    VS("B", privacy=not_sensitive, unique=False),
    VS("cars", privacy=not_sensitive),
    VS("newcolumn", distribution=PoissonDistribution(1), data_free=True),
]

mf = MetaFrame.fit_dataframe(
    df: DataFrame = my_df,
    var_specs: List[VarSpec] | Path | str | MetaConfig | None = my_var_specs,
    privacy: BasePrivacy | dict | None = DisclosurePrivacy(n_avg=11),
    n_rows: int | None = None,
    dist_providers: list[str] | None = None
)

@Samuwhale we'll discuss this next week, if you have any thoughts in the meantime let us know

This looks really nice, looking forward to hearing more on monday!


Add .ci-operator.yaml file

This will allow us to manage build root image from the repo.
This is a prerequisite for https://github.com/openshift/release/pull/31146

/approve
/lgtm


⚠ Bofrost.at has degraded performance

In 9fbe386, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1703 ms

Resolved: Bofrost.at performance has improved in 6e86483 after 7 minutes.


PHP7 support for for exception handling

Looking for guidance here as it appears this might cause some issues with upgrades to php7. I've done some research and it seems most people are adding in Thowable and others are adding in a hack based off of php version. Any thoughts?
Fatal error: Uncaught TypeError: Argument 1 passed to handler_exception() must be an instance of Exception, instance of Error given in /www/bb-load.php:33 Stack trace: #0 [internal function]: handler_exception(Object(Error)) #1 {main} thrown in /www/bb-load.php on line 33

I am really dissapointed in boxbilling that is has been abandoned. I have no time to start fixing the issues and make my system work properly, and I have hundreds of customers in boxbilling... I cant even port to WHMCS wich is 10 times more professional, I cant do anything... nice job BOXSHIT.

How to resolve the issue?


Buttons inside 'Popovers' are not clickable even after activating the 'interactive' property.

Not only the interactive prop.. some of the controls are not working..
Example : trigger, interactive, hide_on_click, etc..
Issue : Re-rendering is not happening while changing controls

@soyef-bit Issue fixed.. please check it..


[bug] setMinSize will change window position in windows

Describe the bug
setMinSize will change window position in windows
Reproduction
in js api,
import { LogicalSize, getCurrent } from '@tauri-apps/api/window';
const currentWindow = getCurrent();
currentWindow.setMinSize(new LogicalSize(1280, 860));

Expected behavior
Window size and position won't change.
Full tauri info output
[✔] Environment
    - OS: Windows 10.0.17763 X64
    ✔ WebView2: 123.0.2420.97
    ✔ MSVC:
        - Visual Studio Community 2022
        - Visual Studio ���ɹ��� 2022
    ✔ rustc: 1.76.0 (07dca489a 2024-02-04)
    ✔ cargo: 1.76.0 (c84b36747 2024-01-18)
    ✔ rustup: 1.26.0 (5af9b9484 2023-04-05)
    ✔ Rust toolchain: stable-x86_64-pc-windows-msvc (environment override by RUSTUP_TOOLCHAIN)
    - node: 18.17.0
    - pnpm: 8.15.4
    - npm: 9.6.7

[-] Packages
    - tauri [RUST]: 1.6.1
    - tauri-build [RUST]: 1.5.1
    - wry [RUST]: 0.24.7
    - tao [RUST]: 0.16.8
    - tauri-cli [RUST]: 1.5.10
    - @tauri-apps/api : not installed!
    - @tauri-apps/cli [NPM]: 1.5.10 (outdated, latest: 1.5.11)

[-] App
    - build-type: bundle
    - CSP: unset
    - distDir: build/dist
    - devPath: http://localhost:3000/

Stack trace
No response
Additional context
No response

I can't seem to reproduce this, can you show a video of the problem?


Warning with ngc compiler

Hi, with the new major version i got this warning message popping up if using the ngc compiler.
WARNING in ./~/angular-pipes/src/index.js
Cannot find SourceMap 'index.js.map': Error: Can't resolve './index.js.map' in '/home/tsm/Sites/deploy-fe/node_modules/angular-pipes/src'
 @ ./src/app/shared/modules/shared.module.ts 9:22-46
 @ ./src/compiled/src/app/app.module.ngfactory.ts
 @ ./src/main.browser.aot.ts

version used: "angular-pipes": "^5.0.9",

That's weird, I just installed the package I have the .map file in the src folder. Could you paste me your directory structure / files under node_modules/angular-pipes ?

Ok, nevermind, it looks like js files are missing. I'll look into it.

I just published 5.0.10. It should work.

it does, thx


BUG: stats.rv_histograms.rvs does not behave as other rvs methods

Describe your issue.
stats.histogram is implemented quite differently from other distributions. It is a subclass of rv_continuos, while the others are instances of rv_continuos. This creates problem when calling the rvs method.
Reproducing Code Example
from scipy import stats

h = stats.rv_histogram((np.random.uniform(0, 1, 99), np.linspace(0, 1, 100)))
h.rvs(100)    # this returns one number
h.rvs(size=100)  # this returns 100 numbers are expected
h().rvs(100)  # this returns 100 numbers as expected

This is very different from other distributions.
 These two do the same thing:
from scipy import stats
import numpy as np

h = stats.rv_histogram((np.random.uniform(0, 1, 99), np.linspace(0, 1, 100)))

h.rvs(size=100, random_state=1)
h().rvs(size=100, random_state=1)

yes, I know. My problem is that this is very different from other distributions
n = stats.norm()
n.rvs(100)

It gets difficult to follow the conversation when you are editing the original post, please put additional comments in successive posts.
The behaviour is not really any different to the other distributions:
n = stats.norm()
n.rvs(100)  #  100 numbers
stats.norm.rvs(100)  #  1 number. This is the equivalent of the h.rvs() you're concerned about

When doing things like
n = stats.norm()
h = stats.rv_histogram((np.random.uniform(0, 1, 99), np.linspace(0, 1, 100)))

the user think "Hey, I have instantiated two objects representing a random variable, they should behave in the same way". They don't.

stats.norm() is not an rv_continuous, it's an rv_frozen instance. When one freezes distributions that means that all their shape parameters are encapsulated in the object. Only stats.norm is an rv_continuous instance.

stats.norm is equivalent to rv_histogram(). Both are instances of rv_continuous. To get multiple random variates out of both you have to call nh.rvs(size=100), not nh.rvs(100). This is because the rvs method of an rv_continuous instance uses *args to describe the shape of the non-frozen distribution, so it's neccessary to provide the size keyword.
stats.norm() is equivalent to rv_histogram()(), both are rv_frozen instances. To get random variates out of both you can do nh.rvs(size=100) or nh.rvs(100).

What is not clear is why rv_histogram is implemented in a different way than all the other distributions

Because it has to accept data in its creation.
h = rv_histogram((d1, d2))().rvs(100) would look funny.

right, but I am not sure why it cannot be
h = rv_histogram((d1, d2)).rvs(100)

sorry to bother you with this. My real problem is that I am trying to implement a new distribution and I have exactly the same issue. I will tag you in the pull request.

If you're wanting to contribute the distribution to scipy it's worth asking on the scipy-dev mailing list about your proposed addition. That will gauge support for adding it to the code base. For example, in the past we've had people want to add a distribution, but it was already present, but just parameterised in a slightly different way.
A good place to start for looking at distribution information is https://docs.scipy.org/doc/scipy/reference/generated/scipy.stats.rv_continuous.html#scipy.stats.rv_continuous.


version number is per kaf-139

https://mesosphere.atlassian.net/browse/KAF-139

@kensipe: This looks fine, but all the checks failed?  What's up with that?

@gabrielhartmann not sure what was going on... rebased, double checked.  ready to go.

@kensipe: Can you figure out how to rerun checks.  Not comfortable merging with big red Xs.