[Tooltip]: content styles reset when open state changes given content is always mounted and forceVisible is true

Describe the bug
If you pass forceVisible: true and always keep the content mounted, whenever $open changes, the content styles reset (top: auto; left: auto) and quickly go back to the trigger's position.
https://github.com/melt-ui/melt-ui/assets/53095479/ce93277a-6ecd-4d95-9a9e-35bf5cfdec8c
Reproduction
https://github.com/anatolzak/melt-ui-tooltip-content-floating-styles-overriding-bug
https://melt-ui-tooltip-content-floating-styles-overriding-bug.vercel.app/
Logs
No response
System Info
System:
    OS: macOS 14.3
    CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
    Memory: 608.16 MB / 32.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 18.15.0 - ~/.nvm/versions/node/v18.15.0/bin/node
    Yarn: 1.22.19 - ~/.nvm/versions/node/v20.9.0/bin/yarn
    npm: 9.5.0 - ~/.nvm/versions/node/v18.15.0/bin/npm
    pnpm: 8.11.0 - /usr/local/bin/pnpm
    bun: 1.0.22 - ~/.bun/bin/bun
  Browsers:
    Brave Browser: <IP_ADDRESS>
    Chrome: 120.0.6099.109
    Edge: 114.0.1823.82
    Safari: 17.3
  npmPackages:
    @sveltejs/kit: ^2.0.0 => 2.5.0
    svelte: ^4.2.9 => 4.2.9

Severity
annoyance

@mcmxcdev what is the melt-ui version you are using?
you might be experiencing this issue https://github.com/melt-ui/melt-ui/issues/1005 that got fixed recently

@mcmxcdev what is the melt-ui version you are using? you might be experiencing this issue #1005 that got fixed recently

I upgraded to latest just before making this issue comment. I think my issue is actually more related to the fact that the popover closes and then the tooltip loses its anchor point, so I might just need to disable closeOnOutsideClick for popover.

@mcmxcdev your issue is actually a different one that what this one was about.
I just created and reproduced your issue. https://github.com/melt-ui/melt-ui/issues/1036

@mcmxcdev your issue is actually a different one that what this one was about. I just created and reproduced your issue. #1036

Thanks man, really appreciate it! Gonna follow the new issue you opened.


Add metric logging tests

🚀 Feature

Add tests to validate, that the metrics are returned in the correct format so they can be easily logged.
Motivation

It became evident here, that there are no tests validating whether the returned metrics can be properly logged and are implemented according to the documentation.
Pitch

Add some tests to check if log or log_dict work with the metrics without causing any errors.
Alternatives

Annoying validation by hand.
Additional context

Hello, I am not sure about how to log non scalars with log_dict() for instance:
test_m = MetricCollection(
            {
                'Accuracy': Accuracy(num_classes=4, average=None, mdmc_average= None)
})
# raises an error
log_dict(test_m)


Fix: Ledger error when registering nym after multi-ledger switch

resolve #2473

Built an Askar only ACA-Py 0.11.0-pr2496-pre0 prerelease image for this PR; ACA-Py 0.11.0-pr2496-pre0

same for me @esune. code makes sense and looks ok to me. can we get someone from the traction team to attempt reproducing this error using this code?
something like this in poetry...
aries-cloudagent = { git = "https://github.com/hyperledger/aries-cloudagent-python", rev = "ee67a59a3a84fcc1f87c59d65aef28202ffad99c" }

same for me @esune. code makes sense and looks ok to me. can we get someone from the traction team to attempt reproducing this error using this code?
something like this in poetry...
aries-cloudagent = { git = "https://github.com/hyperledger/aries-cloudagent-python", rev = "ee67a59a3a84fcc1f87c59d65aef28202ffad99c" }

@shaangill025 mentioned he is still getting an error during stand-up this morning so we might want to wait for an update from him regarding further testing

OBE -- this continues to be an issue that we want to address but will probably need to start fresh.
@esune voluntold to write us a note in the docs for 1.0.0


No red highlight for too big asset in request monitoring

Describe the bug
In new feature request monitoring, we've got option to choose max size of assets and if they're bigger - they are listed with some highlight. Currently there is no red highlight for biggest asset that is too big. Check screenshot (first file is too big here).

IMPORTANT: After discussion we understood, that currently request monitoring only checks all assets total size and is basing on it. We agreed that checking max size for each specific item would also be good improvement for this feature. Additional code is being added to request monitoring. When functionality of checking maxSize for items will be implemented on backend, we only need to uncomment the code and this should work.


⚠ Avatar API Endpoint has degraded performance

In 7a3c285, Avatar API Endpoint (https://avatar.roblox.com/v1/avatar-rules) experienced degraded performance:

HTTP code: 200
Response time: 4514 ms

Resolved: Avatar API Endpoint performance has improved in 18d3ef2 after 11 minutes.


Disable PowerShell logo by default or make it easy to disable

Add an option to easily disable all sorts of logos or unnecessary information printed by the shells on start. I would even prefer this to be the default setting or there could be a global setting to disable the logos.
This could be applied to PowerShell or any other supported shells.
I like the classic Command Prompt's way:
Microsoft Windows [Version 10.0.19041.388]
(c) 2020 Microsoft Corporation. All rights reserved.

C:\Users>

https://stackoverflow.com/questions/59671389/suppress-try-the-new-cross-platform-powershell-https-aka-ms-pscore6
https://stackoverflow.com/questions/48262269/how-to-i-remove-the-powershell-start-text
It isn't really that necessary to spam the users with:
PowerShell 7.0.3
Copyright (c) Microsoft Corporation. All rights reserved.

https://aka.ms/powershell
Type 'help' to get help.

PS C:\Users>

Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

Try the new cross-platform PowerShell https://aka.ms/pscore6

PS C:\WINDOWS\system32>

This is not really what a terminal can/should do. We have just the right explanation for this.
https://github.com/microsoft/terminal/blob/master/doc/Niksa.md#whats-the-difference-between-a-shell-and-a-terminal

@skyline75489 The terminal provides startup options to the shell like working directory. It also detects and configures them. If you are providing a GUI for settings.json, why not provide that option in the GUI?

This is under complete control of the Powershell team. If you don't want to see it, raise an issue on their repo. https://github.com/powershell/powershell. But likely there's already an issue so give it a thumbs up instead.

Yep, the other posters in this thread are correct.
You could even pass -NoLogo to the commandline yourself if you wanted.


clojure: install man pages

Motivation for this change
The Clojure distribution tarball has man pages, so let's install them.
Also move makeWrapper to nativeBuildInputs.
Things done

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

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

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

thanks @danieldk !


Fix/reassign reviewer with conflicts

1.changed the way that reviewers dropdown is rendered.
Existing code is rendering reviewers dropdown for all papers with the same dropdown options(all reviewers) on page load. Changed to render in click event of "Show reviewers" anchor tag by loading edges to filter out the reviewers which have conflict with the clicked paper.
2. add a test case in test_double_blind_conference.py
the setup in this test case has in total 3 reviewers and 1 paper for the area chair<EMAIL_ADDRESS>1 of the reviewers has conflict with the paper. The test verifies that the reassign reviewers dropdown for the area chair has 2 options instead of 3 (1 reviewer with conflict is filtered out).
*please note that updateReviewerContainer method in areachairWebfield.js is also invoked when area chair reassign and unassign reviewers.

found during testing that when reviewers section of multiple papers are expanded and collapsed, reassign reviewer textbox/dropdown/button can be removed from dom mistakenly.
This error happened because the value of $addReviewerContainer object is updated only assigned when updateReviewerContainer() method is called so it can be out of sync with actual user behavior.
Will try $addReviewerContainer or change the behavior of children removal of $addReviewerContainer

found another issue during fixing the $addReviewerContainer issue above.
It looks like the noteId can contain - so when splitting by dash instead of taking the 1st element, need to do a pop and then join with -. also change the removal of # by substring instead of replacement.

above errors are corrected in 27a9b7b

I still see a number of places where you are using => functions, as well as template strings (also an ES6 feature). Please make sure you are using proper spacing around operators also.

@xkopenreview you need to remove the arrow functions before I can merge this PR. They are not supported by all the browsers.

changed fat arrow to function calls.
will try if it's possible to have ie to run es6

Maybe you didn't push your changes because I'm still seeing the arrow functions.

Maybe you didn't push your changes because I'm still seeing the arrow functions.

arrow functions are removed in commit 34195a4.
which lines do you see arrow functions? I did a search in areachairwebfield.js and can't find any

comments are addressed in commit cffdf25


Daikin Altherma MT: indoor temperature always 20°C

The indoor temperature is constantly reported as 20°C, which is definitely not correct (or sometimes it is, though ☺). Not that I really need that data, however I just wondered whether that is something only I am seeing or some other "hidden" problem behind that (and maybe other data is off or not current, too, then?)

do you have the internal probe and/or madoka?

No, don‘t have a Madoka. What would this reading be? I thought the temperature of the room  where the indoor unit is located (while Madoka would deliver the temperature of a heated room…)? Maybe I was just confused by the constant 20 degrees — would have expected 0 if it would be the reading of some external probe…

is simply the default value in the absence of a makoda probe or probe

That clears it. Thanks @simonebortolin


Fix #2100

Description
Add .. to ignore the missing field when handling the relevant swarm event.
This should fix the related issue listed below. However, I'm still unsure why the error is not caught during build phase. Maybe the libp2p dependency is locked to some older version? It didn't seem like it when I was going through the .toml files but maybe I missed something.

Related issue
Fixes #2100

Tests

[ ] Yes
[ ] No, because they aren't needed
[x] No, because I need help

Tried running the test, but it was taking too long and I think it started hanging here:
test providers::fork::state::tests::test_get_nonce has been running for over 60 seconds

Added to documentation?

[ ] README.md
[ ] Dojo Book
[x] No documentation needed

A very minor fix was made that shouldn't need documentation
Checklist

[ ] I've formatted my code (scripts/prettier.sh, scripts/rust_fmt.sh, scripts/cairo_fmt.sh)
[ ] I've linted my code (scripts/clippy.sh, scripts/docs.sh)
[ ] I've commented my code
[ ] I've requested a review after addressing the comments

Thanks for the issue @elton-cs! Yeah, I think it's not a fixed version and they release some new API that may break the semver. I had the same issue trying to bump some stuff on a test branch.
@Larkooo the field in question is connection_id, perhaps we may use it in the future though.

Will close fixed by f6d721246c3fb9a7598fe1cb6591998f3d7094d5. Do appreciate the feedback @elton-cs. 🫡


docUrl in def analyse_generaæ_documents() is slightly wrong - for me at least

The url should be:
"https://github.com/Azure-Samples/cognitive-services-REST-api-samples/blob/master/curl/form-recognizer/sample-layout.pdf"
Not this:
"https://raw.githubusercontent.com/Azure-Samples/cognitive-services-REST-api-samples/master/curl/form-recognizer/sample-layout.pdf"
This works for me.
Dokumentoplysninger
⚠ Undlad at redigere denne sektion. Det er påkrævet til docs.microsoft.com ➟ GitHub-problemlinkning.

ID: b94fc7c6-174c-4e54-d6a9-555cb0f11057
Version Independent ID: 87e95656-6e98-7e29-74ac-2bb287e54711
Content: Quickstart: Form Recognizer Python SDK (beta) - Azure Applied AI Services
Content Source: articles/applied-ai-services/form-recognizer/quickstarts/try-v3-python-sdk.md
Service: applied-ai-services
Sub-service: forms-recognizer
GitHub Login: @laujan
Microsoft Alias: lajanuar

Oh -- dissregard this. I tried to see the .pdf in the browser.


Fix Background image in "08-profile-card" project while testing responsive.

Fix the Background image of the "08-profile-card" project for the mobile version because background images disappeared when the webpage ran on mobile devices.

assign me this issue

@beRajeevKumar  Kindly assign me this issue

Hi @beRajeevKumar, hope you are doing well. I am very interested in solving this issue as I have good grasp on css and html. Please assign me this issue.

@beRajeevKumar  i have raised a pr please revie it and let me know if it needs any changes


[4.0.0-rc-2] Plugin Visits Stats does not work

The plugin counts visits and views that do not occur.

Could you provide a test case? I've check it seems to work correctly on my setup. Maybe the views count is higher than exprected because all the pages opened on the admin section are considered too?

Maybe the views count is higher than exprected because all the pages opened on the admin section are considered too?

This could may be cause the high numbers.

I couldn't reproduce the issue.
The only place I call addVisitor() is from the hook siteBodyEnd.
https://github.com/bludit/bludit/blob/main/bl-plugins/visits-stats/plugin.php#L118

Sorry, no idea was it was... Everything seems to work fine.


Update virtual-machines-windows-create-vm-generalized.md

Fix typos.

Hi @alexandair, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
We will now validate the agreement and then real humans will evaluate your PR.
TTYL, AZPRBOT;

@alexandair : Thanks for your contribution to the Azure documentation! The author, @cynthn, has been notified to review your proposed change.

#sign-off @alexandair thank you for fixing that!


Runtime for mama_ldscores.py

I have been running the following script (with approx 1TB RAM), and I have seen no progress in more than 36 hours. Is this normal or am I doing something wrong?

Read list of 69066 individuals from ./ukb_EUR_AFR_CSA_EAS_maf0.01_info0.8.fam
Read list of 9557064 SNPs from ./ukb_EUR_AFR_CSA_EAS_maf0.01_info0.8.bim
There are 0 SNPs in the merged .bim file without identified source of ancestry groups. These variants are dropped in the LD score estimation.
<><><<>><><><><><><><><><><><><><><><>
Read list of 9557065 SNPs to include from ukb_EUR_AFR_CSA_EAS_maf0.01_info0.8_ld.snplist
Read list of 9557065 SNPs to include from ukb_EUR_AFR_CSA_EAS_maf0.01_info0.8_ld.snplist.AFR
Read list of 9557065 SNPs to include from ukb_EUR_AFR_CSA_EAS_maf0.01_info0.8_ld.snplist.CSA
Read list of 9557065 SNPs to include from ukb_EUR_AFR_CSA_EAS_maf0.01_info0.8_ld.snplist.EAS
Read list of 9557065 SNPs to include from ukb_EUR_AFR_CSA_EAS_maf0.01_info0.8_ld.snplist.EUR
Read list of 7577 individuals to include from ukb_EUR_AFR_CSA_EAS_maf0.01_info0.8_ld.indlist.AFR
Read list of 9056 individuals to include from ukb_EUR_AFR_CSA_EAS_maf0.01_info0.8_ld.indlist.CSA
Read list of 2436 individuals to include from ukb_EUR_AFR_CSA_EAS_maf0.01_info0.8_ld.indlist.EAS
Read list of 50001 individuals to include from ukb_EUR_AFR_CSA_EAS_maf0.01_info0.8_ld.indlist.EUR

<><><<>><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
Estimating LD Score.
Reading genotypes from ./ukb_EUR_AFR_CSA_EAS_maf0.01_info0.8.bed for LD estimation based on AFR-AFR
After filtering, 7576 individuals remain
After filtering, 9557059 SNPs remain
Begin calculating LD scores based on AFR-AFR
After filtering, 7576 individuals remain
After filtering, 9557059 SNPs remain

Hey @samkleeman1,
Just wanted to let you know we're still working on this. We really apologize for the trouble. Have there been any updates on your end?

No updates from my end, just waiting to hear about a fix

From: ggoldman1 @.>
Sent: Friday, May 14, 2021 4:15:35 PM
To: JonJala/mama @.>
Cc: samkleeman1 @.>; Mention @.>
Subject: Re: [JonJala/mama] Runtime for mama_ldscores.py (#15)
Hey @samkleeman1https://github.com/samkleeman1,
Just wanted to let you know we're still working on this. We really apologize for the trouble. Have there been any updates on your end?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/JonJala/mama/issues/15#issuecomment-841478231, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AET2KEELQZMQR5PJ5QEEOB3TNWAGPANCNFSM44PFGYGQ.

Hi Sam,
Just to keep you updated. We noticed some interesting behavior where a comparably sized sample from 1000 Genomes ran very reasonably on chromosome 22 over three populations (12 minutes in total). I was able to replicate your slow runtime on a sample of UKB data we have internally. We're working to get to the bottom of this behavior. Thanks again for your patience.
Grant

Hi Grant,
Thanks so much for looking into this. We are very keen to use the package. If you are able to provide references covering EUR AFR and CSA populations from UKB or 1G then we would not need to generate any references ourselves.
Sam

From: ggoldman1 @.>
Sent: Friday, May 21, 2021 5:48:13 PM
To: JonJala/mama @.>
Cc: samkleeman1 @.>; Mention @.>
Subject: Re: [JonJala/mama] Runtime for mama_ldscores.py (#15)
Hi Sam,
Just to keep you updated. We noticed some interesting behavior where a comparably sized sample from 1000 Genomes ran very reasonably on chromosome 22 over three populations (12 minutes in total). I was able to replicate your slow runtime on a sample of UKB data we have internally. We're working to get to the bottom of this behavior. Thanks again for your patience.
Grant
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/JonJala/mama/issues/15#issuecomment-846279375, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AET2KEDSMG5JCBODY3UNK6DTO3IJ3ANCNFSM44PFGYGQ.

Of course! We're excited that you're interested. Either way we need to resolve this UKB issue. The reference I've been working with is AFR-EAS-EUR, corresponding to the simulation and empirical application in the paper. So I don't think this is exactly what you need. However, if you have 1kG data handy I'd be curious to see if the performance is more reasonable for you.

Hi Grant and Jon,
I am having similar issues with the ldscores computation as well.
I did notice that there is a NUMEXPR_MAX_THREADS option that I can’t seem to find how to modify in the scripts (I was hoping to push the multi-threading so a larger number to speed things up more). Is there a --flag that could modify this parameter?
Right now the script is detecting the total cores that I have (44 cores) - but then defaulting it to 8 cores. If we have got control over the multi-threading it might help make the computation faster.

Hi, Max -
When you say there's a NUMEXPR_MAX_THREADS option, what is that a part of?
Googling around, there looks to be an environment variable of that name
that NumExpr, a Python extension library that Pandas and Numpy can use will
examine when trying to determine the maximum for numbers of threads...is
that what you mean?  If it's an environment variable, you could try just
setting that before running, though I don't believe we explicitly pull in
NumExpr at this time.
We haven't experimented with or tested multi-threaded options a ton yet,
and definitely not to the level of releasing a change for everyone, but
we'll try to work on some optimizations like that.
Also, when you say you are having some LD score computation issues, what
data sources are you using?  Currently it sounds like 1000G produces much
faster results than UKB.  Are you using either of those two, or are you
using alternate sources for your data?  It might help us pinpoint what
differences in the data might be contributing to the problem.
Thanks,

Jon

On Tue, May 25, 2021 at 11:12 AM Max Lam @.***> wrote:

Hi Grant and Jon,
I am having similar issues with the ldscores computation as well.
I did notice that there is a NUMEXPR_MAX_THREADS option that I can’t seem
to find how to modify in the scripts (I was hoping to push the
multi-threading so a larger number to speed things up more). Is there a
--flag that could modify this parameter?
Right now the script is detecting the total cores that I have (44 cores) -
but then defaulting it to 8 cores. If we have got control over the
multi-threading it might help make the computation faster.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/JonJala/mama/issues/15#issuecomment-847947050, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/APIOF57DZGKSVRRWOADOSWTTPO44DANCNFSM44PFGYGQ
.

Hi Grant,
I had the same performance issue with SAS and EUR data. With nearly 800 samples the program nearly full day to calculate the LDscore for chromosome 22.
For test purposes I tried GCTAs LDscore (https://cnsgenomics.com/software/gcta/#ComputingLDscores) implementation with 5 threads and it took 1 second to complete the score calculation for chromosome 22 with same number of subjects. The scores were comparable across MAMA and GCTA. Can you implement the LDSC calculations via GCTA, that can be called by MAMA if user is interested in fast calculations of LDscores?
I had one another minor issue also with MAMA. The program gave error when the IIDs in the fam files were numeric. It was not able to match IIDs to subject index file. When I made IIDs alphanumeric by adding a alphabet prefix, the program worked fine.
Thanks,
Manav

Hi @kapoormanav @samkleeman1
So I think the issue causing this slow runtime is somewhat trivial and mostly just an oversight. I think the issue is that you are specifying your window size (ie one of the --ld-wind-* flags) in a unit that isn't present in the .bim file. For example, my UKB data doesn't report SNP positions in centimorgans, so specifying --ld-wind-cm 1 will cause the runtime issue (and I assume produce incorrect results).
First, can you confirm that the third column in your .bim file is all 0's and you are specifying the window size in centimorgans? If so, you can try to fill in the missing cm data (it seems like from https://www.biostars.org/p/52820/ you can get this data from UCSC Genome Browser), or, alternatively, approximate the centimorgan position with 1000 kilobases (use the --ld-wind-kb 1000 flag). Obviously the latter will only work if you have the bp position in your .bim file.
I think this should take care of it -- once you implement this could you post here to let us know if it's resolved? Also, @kapoormanav I will open a PR for this issue merging the tables together. Thanks to you and @samkleeman1 for raising it, we appreciate it!

Hi Grant,
Yes, the CM column is set to 0 in my bim file. Thanks for the link to update the CM positions. I will update it and let you know if the problem persists.
Thanks a lot!

Thanks!


add 'winpty' support when available

Hello,
Some Python scripts need to access the underlying OS, like using redirections. These interactions go through TTY interface. On MinGW, these interactions/interfaces are called 'winpty'. => use them when available (harmless on platform *NIX platforms)
OS: Windows
env: MinGW
I rebuilt the windows-curses and overwrite the built-in Python ncurses libraries.
When calling:

make/ninja menuconfig

You get an "Redirection is not supported" error.
kconfig python script uses curses to draw in the console. As in MinGW, the default TTY is not an interactive one, cbreak() fails. To overcome this "lack", you must use pdcurses. To make the redirection work, you must call Python on top of the winpty interface.
This proposed patch looks for winpty and, if installed, use it when calling 1 one the 3 Kconfig targets (menuconfig guiconfig hardenconfig). This should be harmless on system without winpty installed: *NIX ones

MinGW is not officially supported, and it takes a much larger effort to truly support building Zephyr under MinGW.
This has been discussed in various places, for example like here: https://github.com/zephyrproject-rtos/zephyr/issues/45383#issuecomment-1118672615
This might look like a small addition, but the main issue / risk I see is that we might end-up with several small adjustments like this but without a proper plan / path to fully support MinGW.
How will this code behave for users who might have MinGW and winpty installed, but is otherwise building using windows command-line ?
I have a windows setup, but not a mingw / winpty, so I can't test or verify.
Based on description I found of winpty, then afaict it should also be possible for the user to directly specify the use of winpty when running ninja (or make), like this:
$ winpty ninja menuconfig

which again means one can use the alias feature, like this:
$ alias menuconfig="winpty ninja menuconfig"

and then just run menuconfig.
So far I see no good arguments on just this single patch, but opinions from others are more than welcome.

Hello @tejlmand,

MinGW is not officially supported, and it takes a much larger effort to truly support building Zephyr under MinGW.
This has been discussed in various places, for example like here: https://github.com/zephyrproject-rtos/zephyr/issues/45383#issuecomment-1118672615

Yes, as in my comment, everything is working fine now. I'm working with it for almost 2 years now and I didn't see any problems. Only a limitation on 'make menuconfig' because of curses/tty.

How will this code behave for users who might have MinGW and winpty installed, but is otherwise building using windows command-line ?

I just tried it. cmake.exe installed in MS Windows does not find winpty.exe (because it is not installed in MS Windows, but in MinGW). So, it will be harmless for these users. Also, I did not test all environments (I do not have MacOS for example)
$ winpty ninja menuconfig
Yes, this does work but this is more a workaround. Doing this will fix the issue for one user, not all of them. Someone who does not know about winpty might never get it to work...

Yes, as in my https://github.com/zephyrproject-rtos/zephyr/pull/45392#issuecomment-1980884316, everything is working fine now.

Thanks for the reference, and great to hear that it actually is working, although care must be taken.
If you want, then perhaps a page here: https://github.com/zephyrproject-rtos/zephyr/discussions/categories/show-and-tell would be good for others.
I think that's the second best, compared to being officially supported.

I just tried it. cmake.exe installed in MS Windows does not find winpty.exe

Thanks for verifying.


Monitor not working

Thanks for the tool.
I have mac pro 2008 and installed mojave using http://osxdaily.com/2018/09/27/run-macos-mojave-unsupported-mac-dosdude-patch/
I have installed latest driver using the update tool and it installed 3<IP_ADDRESS>.40.113
Now mac sees my zotac GT 710 graphics card
Chipset Model:	NVIDIA GeForce GT 710
Type:	GPU
Bus:	PCIe
Slot:	Slot-1
PCIe Lane Width:	x8
VRAM (Dynamic, Max):	1023 MB
Vendor:	NVIDIA (0x10de)
Device ID:	0x128b
Revision ID:	0x00a1
ROM Revision:	VBIOS 80.28.a6.00.10
The only issue is that whatever monitor I connect to it (VGA or DVI) it is not seen at all, I had to boot from ATI Radeon HD 2600 to view my monitor and If I removed the ATI and left the nvidia alone and reboot, mojava won't boot.
Any clues?
Thanks in advance.

nvidia-update is just an installer for drivers, not a driver in itself.  The issue you are having is related to nvidia and Apple having a spat, with the end result being that there are no working nvidia web drivers for Mojave.
https://www.forbes.com/sites/marcochiappetta/2018/12/11/apple-turns-its-back-on-customers-and-nvidia-with-macos-mojave/1

Thanks for the prompt response.
Any idea if it drivers wok with High Sierra or not on old mac pro 2008?


[#147] PathExplorer delete key pattern

Closes #147
Delete all the (key, value) pair where the key matches the regular expression pattern.

Added a new SAD command delete-ke for that: scout delete-key "pattern"

Codecov Report

Merging #149 (acc8db3) into develop (84f637b) will increase coverage by 0.53%.
The diff coverage is 100.00%.

@@             Coverage Diff             @@
##           develop     #149      +/-   ##
===========================================
+ Coverage    80.17%   80.71%   +0.53%
===========================================
  Files           31       31
  Lines         1806     1846      +40
===========================================
+ Hits          1448     1490      +42
+ Misses         358      356       -2

Impacted Files
Coverage Δ

...es/Scout/Definitions/PathExplorer+Extensions.swift
66.66% <100.00%> (+0.66%)
:arrow_up:

...rialization/PathExplorerSerialization+Delete.swift
99.39% <100.00%> (+0.12%)
:arrow_up:

...t/Implementations/XML/PathExplorerXML+Delete.swift
100.00% <100.00%> (ø)

...es/Scout/Implementations/XML/PathExplorerXML.swift
59.21% <0.00%> (+1.31%)
:arrow_up:

Sources/Scout/Definitions/Path.swift
83.56% <0.00%> (+1.36%)
:arrow_up:

Continue to review full report at Codecov.

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

Codecov Report

Merging #149 (acc8db3) into develop (84f637b) will increase coverage by 0.53%.
The diff coverage is 100.00%.

@@             Coverage Diff             @@
##           develop     #149      +/-   ##
===========================================
+ Coverage    80.17%   80.71%   +0.53%
===========================================
  Files           31       31
  Lines         1806     1846      +40
===========================================
+ Hits          1448     1490      +42
+ Misses         358      356       -2

Impacted Files
Coverage Δ

...es/Scout/Definitions/PathExplorer+Extensions.swift
66.66% <100.00%> (+0.66%)
:arrow_up:

...rialization/PathExplorerSerialization+Delete.swift
99.39% <100.00%> (+0.12%)
:arrow_up:

...t/Implementations/XML/PathExplorerXML+Delete.swift
100.00% <100.00%> (ø)

...es/Scout/Implementations/XML/PathExplorerXML.swift
59.21% <0.00%> (+1.31%)
:arrow_up:

Sources/Scout/Definitions/Path.swift
83.56% <0.00%> (+1.36%)
:arrow_up:

Continue to review full report at Codecov.

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


FEATURE: Added Now Playing Movies and Top Rated Movies and Upcoming Movies

Added some features that I need for my project. Thank you for the awesome package!

Thanks for the contribution @DannyCamenisch 👍🏻


Update speech-usage.rst

if sample.stream.closed:
AttributeError: 'NoneType' object has no attribute 'closed'

according to this. doc needs change

Thanks @FCtj! You're right. I'm not sure if I can merge without you on the CLA, so I'll close this PR and make a new one real quick.

I signed it!


TypeScript wrapper class cannot run in browser

ton-emulator dependency is not browser friendly
await SampleTactContract.fromInit(Address.parse("EQCD39VS5jcptHL8vMjEXrzGaRcCVYto7HUn4bpAOg8xqB2N"));

Uncaught ReferenceError: __dirname is not defined
    at node_modules/ton-emulator/dist/bindings/EmulatorBindings.js (EmulatorBindings.js:19:30)
    at __require2 (chunk-IPKTAYBB.js?v=530909c9:18:50)
    at node_modules/ton-emulator/dist/emulator/ContractSystem.js (ContractSystem.js:17:28)
    at __require2 (chunk-IPKTAYBB.js?v=530909c9:18:50)
    at node_modules/ton-emulator/dist/index.js (index.js:5:24)

Fixed in 0.10.0


Generate v17.1.6 Release

Could you generate the files needed to create v17.1.6 NuGet packages? Any update to publishing the source code to generate the .nuspec files?

Actually, 17.1.7 would be even better. Thanks in advance.

@ericmschmidt Both v17.1.6 and v17.1.7 are now available.

v17.1.7 - https://github.com/caioproiete/DevExpress-NuGet/releases/tag/v17.1.7
v17.1.6 - https://github.com/caioproiete/DevExpress-NuGet/releases/tag/v17.1.6

Thank you. This project has been extremely helpful with our applications.


You havent updated to swift 3 yet

I use your pods and it is still using swift 2. When I use your development branch it causes an error that MiniKeychain is not found. please update your cocoapods

Fixed.


object-c to swift

object-c can work well. but when I embed it in my swift's code with bridge head file, setBlockOnCentralManagerDidUpdateState is the only delegate function that babyBluetooth can invoke.
could you give me some advice to make BabyBluetooth work success in my swift project?
I love babyBluetooth with lazing and clearing use

as you see , BabyBluetooth make by objc,and feather of methor by serial need a special syntax which by set parameter of return to block ,like this :
- (BabyBluetooth *(^)()) scanForPeripherals;

this syntax is bad for swift ,that's why you not work in swift project。
Babybluetooth-swift programming is on the schedule and it will done in few month ,you can watch repo in there :  Babybluetooth-swift


EMail host is required for SSO self registration

Please verify that this bug has NOT been raised before.

[X] I checked and didn't find a similar issue

Describe the bug*
The CustomSocialAccountAdapter extends the RegistratonMixin which overrides the is_open_for_signup method. In my opinion, the check performed in the function should not be the intended behavior for Social Accounts.
Steps to Reproduce

Configure a social account for your inventree instance
Make sure no email host is configured
Try to sign in for the first time with a social account user and experience the "Sign in Closed" page.

Expected behaviour
In my opinion, it should not be required to configure an email host in order to enable SocialAccount self registration.
My personal use case:
I am currently running InvenTree on my local machine and played around with the OpenID config. It took me forever to figure out why my social login did not work. I finally solved it by specifying a dummy value INVENTREE_EMAIL_HOST = localhost.
Do you think it is possible to disable the email host check if a social account is used?
Deployment Method

[X] Docker
[ ] Bare metal

Version Information
Master branch
Relevant log output
No response

This is on purpose, you can lock yourself out of your instance if you have no way to reset your password. For that, you need an email provider.

I understand that this is the case for a instance using the integrated authentication, but this should not be an issue with Social Accounts as there is always the provider of the corresponding social account which is responsible for resetting the password. Also, as an admin I always have the ability to generate a new admin account using the CLI if the social account provider was misconfigured and must be changed

Providers go down and ppl. lose access to external accounts for a multitude of reasons. If you only have 5 users on your private instance you can go into the CLI and change stuff easily. Once you deploy in a larger org those kinds of access get harder because of compliance and security concerns.
I would really like to not remove the mail requirement - InvenTree is unable to communicate reset instructions with the user once they lock themself out. We can add some warning to the console output if you find it confusing.

We can add some warning to the console output if you find it confusing.

Additionally, there should be some obvious message in the UI if a certain feature is disabled because of some other setting (i.e. mail not being setup)

In general I agree that we should not remove the email requirement here. We can improve the docs around this, but the email will stay

Once you deploy in a larger org those kinds of access get harder because of compliance and security concerns.

I did not think about large scale deployments, I agree on your point keeping the mail

We can add some warning

Additionally, there should be some obvious message in the UI

That would be great! Do you want me to create a PR adding the console warning and documentation, or do you want to implement it yourself? Not sure if I'd be able to figure out and display the error in the UI though, this would require me to take another look.

A contribution would be wonderful @p-fruck
I think the best place to start would be in the global settings here. You can also add a warning in form of a print statement in the settings.py where we check for email settings.


Size Badge

Hey @RocktimSaikia
I was wondering if I can contribute by adding a simple size badge.

@pagalprogrammer Sure. Since you are only suggesting a new badge request. I would suggest only sticking and making changes to the /util.js and not changing other parts of the code since I'm still optimizing and experimenting with some new features in another branch. Anyway, then I'm assigning this to you.

As assigned, I have added two size badges.

Repo Size
Code Size

I have also modified readme.md accordingly.
Refer to #5


MI-12343 Hack around StackOverflow to allow us to keep the "cache more" change

https://grantadesign.atlassian.net/browse/MI-12343

Wrong branch


going forward + question

Hi Hugo, this project rocks i'm having lot of fun, this is the best AI based audio tool available right now, at least for what i'm looking for.
Would like to share where i'm going from this awesome project..
i've made an app in c# that takes care of keeping loops overtime and send generation presets to gradio like you did with unloop, losing hours just listening to generations and i'm making tons of brand new audio loops too!!
working also on a vst plug-in that send generated wavs into daw combined with demucs for separation, made also a very primitive liveset using 3 c# apps simultaneously in realtime and sending demucsed streams to vst -> reaktor and mixing them, what a blast!!
Not sure if there's interest on what i'm doing, i may share the projects but i'm nothing special with coding, i just know how to use chatgpt properly :)
this is the c# app

this is the liveset setup using vst + bidule + reaktor (+ ipad and midi controller)

https://github.com/hugofloresgarcia/vampnet/assets/23511425/bbcf54ae-136b-4d60-aafa-3055eff58c2f

now for the question, is there a way to start a new training and make a bigger size model ?
is it an easy task ? i mean i have no idea what i have to change in the code to set model size for training like 2x or 3x bigger, i only did (huge) fine-tunings till now. would like to test starting training from scratch and making a bigger model too to see what happens :)
thanks a lot!

Hi @tig3rmast3r,
This is insane!! I wanted to say this looks and sounds super cool!
Would love to hear a full AI techno set done with this tool if you'd have one to share!
I'm really happy to see vampnet in a full creative interface like this one.
Training from scratch requires a large dataset (50k hours of audio, more or less), and enough GPUs to fit a batch size of ~32 for the duration of audio context you'd like to train for.  You can have a look a the settings used to train the model in conf/vampnet.yml.

Hi Hugo,
glad you liked it, i played with that a lot but never found the time to do a good recording, i'm planning to make a youtube video sooner or later.
About the training, i've already carefully selected 10k+ chunks that should be like 28 hours, is a very personal model as it includes most of my discography for the first 30%, i've used it already for this project as fine-tuning.
I did around 300 ephocs for fine-tuning (batch_size*iterations/n. of chunks), with an rtx 4090 it took around 90 hours total (70 coarse+ 20 c2f) i stopped at 300 because the learning rate was dropping very quickly.
i've already had a look to the vampnet.conf, what is the parameter that define the model size ?
is just VampNet.embedding_dim: 1280 ?
i mean if i want to make a double size pth just doubling this value is enough or do i have to adjust something else ?
i guess that as the model is aimed for just techno/tec-house 28 hours may be enough...

yeah, doubling that value could work. You could also try changing the number of layers and heads, though that might require a bit more finetuning to get it working.

is it normal that training with identical parameters and dataset on linux gives different results than windows?
i'm telling this because i trained a model for a few days and i'm still getting very bad results, i run for 334600 iters with batch 3, that is 100 epochs as i have 10038 chunks.
i used linux with torch.compile with pytorch 2.1.2 and 118, i did the same with c2f.
i used embedding 1914, head 22 and layers 22, while for c2f i lowered to 1800,20,20.
it's still far from being good so i'm wondering if there's someting wrong in linux, like for example is wrongly reading the wav files.
So for testing purpouses i did a quick training with a few chunks and i did the same in windows so the models should be identical and i've discovered that linux ones are usually missing higher frequencies like they are pitched down, i've attached 2 wavs generated with same seed without mask. I will do more tests in windows with longer train but it looks there's something wrong on my linux setup.
How can i make sure it's reading files correctly? they are all wavs mono 16bit pcm 44100hz.
I'm sure Windows is ok cause i did many fine-tunings and they sounds great.
note that i don't use torch.compile in windows as is not available and i'm on pytorch 2.1.0 but i tried even pytorch 2.3.0 in linux with cuda 12.1 and the models appears almost identical to 2.1.2 with 11.8.
do you have any clue ?
here's the test wavs.zip comparison between the linux and windows trainings.
thanks

i def have a problem in linux
did a longer training tonight in windows with same values as linux.
this is only 10 epochs for coarse + 20 for c2f,  versus 100 + 100 from linux.
now i got what i was expecting, would like to sort out my linux issue so i can rent a runpod for the training, any idea would be really appreciated. thanks
i attached 2 examples, one pair without mask, same seed, and another pair with mask with another seed.
testwav.zip

i did a quick test and looks that the problem is with torch.compile command.
removing torch.compile from train.py solved the problem in linux.
Do you have a specific combination of pytorch and cuda that you have tested with torch.compile and you know it's working ?
i tested so far:
2.1.2 with cu11.8 = bad training
2.3.0 with cu12.1 = bad training
2.2.0 with cu12.1 = error (missing 1 required positional argument: 'dim')
hope this helps

i've finally found a working combination, honestly i haven't find the root issue but i can use linux now!
i tried both home and i'm actually training on vast.ai with 4x 4090, no issues so far (not using torch.compile but at least multi gpu is working too)
I got a pip list for pc and tried to make it as much similar as possible in linux, also i downgraded pytorch to 2.0.1 cu118 even if i'm using 2.1.2 cu118 in windows.
downgrading pytorch btw was not enough, while alignment between pc modules versions and linux ones did the trick.
i have attached below some txts so maybe it can helps identify the issue:

pip list from working pc configuration python 3.11.4
conda list from working ubuntu22.04 config with python 3.11.4
conda list from not working ubuntu22.04 config with python 3.9

as i have destroyed all the runpod i cannot get conda list from other not working config but i had many more combinations.
note that using python 3.11.4 i'm not able to launch gradio as madmom throws an error even when installing from source (it works only in windows and probably on mac os).
Fortunately it looks that madmom is not used during training (or at least it works)
I attached also a python script that compares the 2 conda list (the one that is working that i have posted against the one created on the new server) and creates a requirements file to quickly align versions.
i've used this trick on a clean machine on vast.ai and it works.
hopefully you will find the root cause so we can define the version during pip install -e ./vampnet (or update the code to work with the latest version of whatever it is)
just for the sake of sharing here's the code to configure a fresh ubuntu installation/container to get it working:
#go to workspace if you are not already
cd workspace
wget https://repo.anaconda.com/miniconda/Miniconda3-latest-Linux-x86_64.sh -O /workspace/Miniconda3-latest-Linux-x86_64.sh
echo 'export PATH="/workspace/miniconda/bin:$PATH"' >> ~/.bashrc
source ~/.bashrc
conda init bash
source ~/.bashrc
conda create -n vampnet python=3.11.4
conda activate vampnet
conda install pytorch==2.0.1 torchvision==0.15.2 torchaudio==2.0.2 pytorch-cuda=11.8 -c pytorch -c nvidia
pip install cython
#install build essentials if not present, some containers has it already
apt install build-essential
git clone https://github.com/CPJKU/madmom
cd madmom
pip install .
cd ../
git clone https://github.com/hugofloresgarcia/vampnet.git
pip install -e ./vampnet
#comparing and aligning modules
conda list
#save conda list in a file and call it linux_new
#upload compare.py and linux_working into workspace
python compare.py
pip install -r requirements_to_update.txt
#optional? replace "torch.compile" with "" in train.py to remove torch.compile task
#you will need to download all the required pth (at least codec.pth, don't know if it needs wavebeat.pth too for training)
Here's the zip condalists.zip
Lastly, while i was testing i've found the time to report some "TimeToTrain" values, it may help finding the perfect server to train and save some (or a lot) of $$
Here are all the tested server:

model
ram
cuda
tensor
freq
tdp
gpu
batch
time to train
fp32bench
vastai tflops
vastai dlp min
vastai dlp max
NOTE

RTX 4090
24
16384
512
2235
450
4
16
178
82,58
327,00
260,00
350,00

H100 80 smx5
80
16896
528
1590
700
1
16
224
66,91
107,00
580,00
684,00

RTX 4000 ADA
20
6144
192
1500
130
6
18
241
26,73

RTX 4090
24
16384
512
2235
450
2
6
264
82,58
162,00
175,00
212,00

L40
48
18176
568
735
300
2
12
290
90,52
144,00
231,00
231,00

RTX A4000
16
6144
192
735
140
8
16
295
19,17

RTX 6000 ADA
48
18176
568
915
300
1
6
450
91,06
81,00
135,00
135,00
Multi-gpu not working

RTX 4000 ADA sff
20
6144
192
720
70
4
8
513
19,17
41,00
31,00
42,00

RTX A5000 (SFF?)
24
6144
192
900
150
6
18
545
19,35

strange model with 150w tdp and lower perfs

RTX A5000
24
8192
256
1170
230
2
6
572
27,77
55,00
55,00
69,00

A100 80 PCIe
80
6192
432
1065
300
1
16
600
19,49
31,00
170,00
260,00

RTX 3090
24
10496
328
1395
350
2
6
930
35,58
71,00
75,00
90,00
low performance node, need retest

Tesla V100 PCIe
16
5120
640
937
250
6
12
1420
16,32
25,00
34,00
40,00
uses only 20% Watt


Added yara_version to the specification

Gives the ability for a user to specify the minimum Yara version for a rule.

Hello BitsOfBinary,
We are just about to release a new version with some new features. We will be including this idea as "minimum_yara" using the existing valid_version function. This will allow for a larger range of potentially valid version numbers than your implementation.
We will be including a your contribution in the release notes.

We have just merged the feature_yaramultirulefiles into master as you can see above. I will be setting up the release now. As mentioned above we included this idea as "minimum_yara". Thank you for the contribution and we hope you find this project helpful.

Brilliant, thank you for implementing my suggestion :)


normalize column names for Redshift

This fixes an error with column names when using RedShift, issue is detailed here https://github.com/apache/incubator-superset/issues/5308.

Codecov Report

Merging #5337 into master will decrease coverage by <.01%.
The diff coverage is 50%.

@@            Coverage Diff             @@
##           master    #5337      +/-   ##
==========================================
- Coverage   61.33%   61.33%   -0.01%
==========================================
  Files         369      369
  Lines       23484    23486       +2
  Branches     2713     2713
==========================================
+ Hits        14405    14406       +1
- Misses       9067     9068       +1
  Partials       12       12

Impacted Files
Coverage Δ

superset/db_engine_specs.py
54.27% <50%> (-0.02%)
:arrow_down:

Continue to review full report at Codecov.

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

@mistercrunch  did this make it through to the new releases? I do not believe I see them in 26.2 and 26.3?

Ah gotcha @mistercrunch thanks, I'm pretty new to this. I have been doing this workaround but just wanted to know more about the process. Many thanks


Dashboards with instant filtering showing stale results

Dashboards with instant filters sometimes show stale results after the filters have been changed.
How to reproduce the bug
Note: This bug might need a big dataset to reproduce. I have tried a few example datasets but they seem too small to reproduce the issue.

Create a dashboard with a filter box, and make sure the filter box has instant filtering checked and it allows to select multiple values
Add any chart in the same dashboard and make sure the filter does change the result of the other chart (Big number is easier to observe)
Select a value from the filter box
Select another value from the filter box.
Remove the value selected from step 4.
Repeating step 4 and 5. Eventually the chart added in step 2 shows the results without the filter value selected from step4, even though that filter value is selected.

Expected results
Dashboard showing results showing results reflecting current filters.
Actual results
Dashboard showing stale results not reflecting the current filters.
Screenshots
We have screenshots with bigger dataset, however, the data is confidential and I can't share it here.
Environment
(please complete the following information):

browser type and version: Chrome Version 105.0.5195.125 (Not browser specific)
superset version: Superset 2.0.0
python version: 3.8
node.js version: not specific to node.js version
any feature flags active: N/A

Checklist
Make sure to follow these steps before submitting your issue - thank you!

[ ] I have checked the superset logs for python stacktraces and included it here as text if there are any.
[X] I have reproduced the issue with at least the latest released version of superset.
[X] I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context
Add any other context about the problem here.

By the way, we can reproduce this in our production environment with presto as the query engine.

Pinging @kgabryje @michael-s-molina @stephenLYZ in case they happen to have any insights here.

Working as expected.
Screenshots
1.without giving the filter values

2.After add the filter value

3.Add another value from filter

4.remove the filter value recently added

Hopefully, based on the above comment, this is likely fixed by now. It is pretty out of date if not. If people are still encountering this in current versions (3.x) please open a new Issue, a PR to address the problem, or at least give us updated context so we can re-open and reproduce this Issue.


More Controls on Mini-Player

An action overflow on the mini-player could bring users some more functionality like adding to playlists or starting a radio for an specific song. This is great for us who use google play music for music discovery. Adding to my offline sync'ed android playlis from the mini-player would save a ton of work!
The menu could be the same as this on the main interface!

+1 for this :+1:


GEOMESA-1188 Configurable interval for z3 dates

Note: stacks on top of #971, please consider only last commit(s).
Signed-off-by: Emilio Lahr-Vivaz<EMAIL_ADDRESS>

needs rebase

Looks good to me once the other PR goes through.

@elahrvivaz can you check the rebase and make sure this is still clean for merge.

@jahhulbert-ccri rebased again, thanks


Not finding libparquet-dev 1.3.1 for debian/ubuntu in the repositories

Hi!
I see you've updated your build tree to build 1.3.1, but I cannot find 1.3.1 in the repository. Is this intentional? :)

I've uploaded packages for apache-parquet-cpp 1.4.0-rc1.


Components pointing to a non-existant resource fails pipeline silently

This can be reproduced with the following:
version: v2

deployments:
  mailslurper:
    image: docker.io/tyleraldrich/mailslurper:latest
    command:
      - sh
      - -c
      - |
        apk update
        apk add wget
        wget https://github.com/stedolan/jq/releases/download/jq-1.6/jq-linux64
        mv jq-linux64 /usr/local/bin/jq
        chmod +x /usr/local/bin/jq
        tmpfile=$(mktemp)
        jq '.wwwPublicURL="${{ ingresses.mailslurper.url }}" | .servicePublicURL="${{ ingresses.mailslurper-api.url }}"' config.json > "$tmpfile"
        mv "$tmpfile" config.json
        ./mailslurper

services:
  mailslurper:
    deployment: mailslurper
    port: 8080
  # mailslurper-api:
  #  deployment: mailslurper
  #  port: 8085

ingresses:
  mailslurper:
    service: mailslurper
  # mailslurper-api:
  #  service: mailslurper-api

Using this component yaml, which has commented out services.mailslurper-api and ingresses.mailslurper-api, but has a command that still references ${{ ingresses.mailslurper-api.url }}, you can deploy this pipeline without errors but the pipeline will finish (allegedly successfully) without applying all the steps.
It eventually reaches a point where it needs the ingresses.mailslurper-api to finish before proceeding, but that doesn't exist, so getNextStep returns nothing and the pipeline "succeeds". Instead, the pipeline should fail because a reference to a resource that doesn't exist in the graph is present.

Update: It looks like this issue was actually fixed at some point between when I first saw it and now. Running this with the latest main pulled correctly throws an error:
~/code/architect/arcctl (100-circles*) » arcctl deploy tyleraldrich/mailslurper:latest --environment gcp-serverless-env -i mailslurper:main -i mailslurper-api:api -v
Error: tyleraldrich/mailslurper/ingressRule/mailslurper-api is missing from the pipeline, but required by tyleraldrich/mailslurper/deployment/mailslurper-blue


Update 3 0 0alpha2

@conda-forge-admin, please rerender

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Closing this in favor of #25


Fix incorrect workaround for pure Y (X) rotations in XYZ (YXZ) conven…

…tion.
Fixes #10352.

This of course doesn't fix the problem regarding the non-uniqueness of polar decomposition, which makes it impossible to change scaling without changing rotation part, vice versa.
The behavior of Spatial::set_scale was changed in #7438, where I introduced polar decomposition in Basis::get_scale and Basis::get_rotation (because earlier behavior wasn't mathematically correct in general). So Spatial::set_scale in 2.x and 3.x does different things.
I'll remove (or at least unexport to GDScript) Basis::set_scale and Basis::set_rotation, which I introduced in #8277 in a later PR, and their get_ counterparts need some thinking as well.

oh, nice, fixes makes a lot more sense than what I did
On Mon, Aug 21, 2017 at 7:54 PM, Rémi Verschelde<EMAIL_ADDRESS>wrote:

Merged #10415 https://github.com/godotengine/godot/pull/10415.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/pull/10415#event-1214960759, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AF-Z21w0RPeU1iIbgmraeAdtwLcsutQvks5sagq7gaJpZM4O7Hkc
.

Clarification for others: this simply checks whether we have a simple rotation around the Y (X) axis (there should be 4 zeroes and a single 1), and proceeds to extract the rotation angle.


feat: Implement features.suse_default_stack.enabled

This PR uses #965 as the base, so that PR should be reviewed/merged first.
It switches the default_stack from cflinuxfs3 to sle15.
Fixes #948.
This is a new version of #960, which was merged without testing, and later reverted.
https://github.com/cloudfoundry-incubator/kubecf/pull/945#issuecomment-635624549 specifies the expected functionality:
Diego

suse_buildpacks=false and suse_default_stack=false

SUSE buildpacks are not installed, but the SUSE rootfs still is. We can discuss if the rootfs should be removed as well in the future, but in v2.2.x it has to stay for backwards compatibility.
However, buildpacks can be added back later via cf create-buildpack, but stacks cannot, so maybe both stacks should always be available.

suse_buildpacks=true and suse_default_stack=false (current default)

SUSE buildpacks would be installed, but not used by default because the default stack remains cflinuxfs3.

suse_buildpacks=false and suse_default_stack=true

This doesn't make much sense because a stack without buildpacks doesn't work. I would suggest to throw an error because the probability of user error is very high in this case.

suse_buildpacks=true and suse_default_stack=true (default in v2.3+)

SUSE buildpacks installed and used by default.
Eirini

suse_buildpacks=false and suse_default_stack=false

Not supported because there is no cflinuxfs3 Eirini image. Throws an error.

suse_buildpacks=true and suse_default_stack=false (current default)

Not supported because there is no cflinuxfs3 Eirini image. In v2.2.x it silently makes the SUSE stack the default. In v2.3+ it should throw an error.

suse_buildpacks=false and suse_default_stack=true

This doesn't make much sense because a stack without buildpacks doesn't work. I would suggest to throw an error because the probability of user error is very high in this case.

suse_buildpacks=true and suse_default_stack=true (default in v2.3+)

SUSE buildpacks installed and used by default.

I don't see suse_default_stack in values.yaml.

Thanks for catching that. It was in the original PR https://github.com/cloudfoundry-incubator/kubecf/pull/960 but must have gotten lost in the rebasing. I've put it back and amended the commit.

Also, I don't think we should call it suse_default_stack.
It should be default_stack with a set of acceptable values - some folks want to add a red hat stack (can't find the slack conversation anymore).

I do agree with that. Unfortunately we only support 2 hard-coded stacks right now, and adding additional stacks is not possible without some complicated ops files.
I do want us to parameterize additional stack support in the future, but it will require reorganizing the current structure of defining releases in values.yaml and making things like feature.suse_buildpacks more generic as well.
So for the current point in time I think features.suse_default_stack works well as a companion to features.suse_buildpacks. Without it being SUSE stack specific, the particular failure checks would also not make much sense.
We can migrate suse_default_stack and suse_buildpacks to a more generic configuration at a later point in time.

I believe the main conditions of @viovanov's review have been met. We'll need a feature item to expand past 2 stacks since there will be substantial changes needed in quarks to prepare for it, which shouldn't hold up the current needs for kubecf.


Dryrun for pipeline

Add the nextflow stub feature for pieplien dry runs

[ ] update viash
[ ] add to documents

It should work using Viash >0.6.1 (I think) by adding -stub to your command.


Remove stable rapidsai conda channel (non-release jobs)

This PR tests the removal of the rapidsai conda channel. PR should not be merged.

Closing, see https://github.com/rapidsai/gha-tools/pull/102#issuecomment-2048005971

Closing, see https://github.com/rapidsai/gha-tools/pull/102#issuecomment-2048005971


EndToEnd Example with helm chart

Describe the solution you'd like
Create a full end to end example base on to BanzaiCloud logging-operator helm chart, with nginx and S3 storage backend.

https://github.com/banzaicloud/logging-operator/pull/77


Better arcs

Adding padAngle, padRadius and cornerRadius to the Arcs to use the full potential of the d3 arc generator
renaming the innerArc prop on PieArcProps as it is misleading (breaking change)
Add new story to show the usage
PieChart to FC
Do not merge
PR Checklist
Please check if your PR fulfills the following requirements:

[ ] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?
[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

What is the current behavior?

Issue Number: N/A
What is the new behavior?
Corner radius

padAngle + padRadius + corner radius

Full Arc features: https://github.com/d3/d3-shape#arcs
Does this PR introduce a breaking change?
[x] Yes possibly
[ ] No

This is only a discussion right now, but naming the arc function innerArc is just bad
Other information

sorry for the amalgamation of various things, I promise to do better next time, feel free to merge now


fix pillow constrains on previous napari releases

Checklist

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

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Comes from https://github.com/conda-forge/napari-feedstock/pull/33#discussion_r786978980
@conda-forge/napari
python show_diff.py

Downloading: https://conda.anaconda.org/conda-forge/noarch/repodata_from_packages.json.bz2
Downloading: https://conda.anaconda.org/conda-forge/noarch/repodata.json.bz2
noarch::napari-0.3.7-py_0.tar.bz2
-    "pillow",
+    "pillow !=7.1.0,!=7.1.1",
noarch::napari-0.3.8-py_0.tar.bz2
-    "pillow",
+    "pillow !=7.1.0,!=7.1.1",
noarch::napari-0.4.0-pyhd8ed1ab_0.tar.bz2
-    "pillow",
+    "pillow !=7.1.0,!=7.1.1",
noarch::napari-0.4.10-pyhd8ed1ab_0.tar.bz2
-    "pillow",
+    "pillow !=7.1.0,!=7.1.1",
noarch::napari-0.4.11-pyhd8ed1ab_0.tar.bz2
-    "pillow",
+    "pillow !=7.1.0,!=7.1.1",
noarch::napari-0.4.12-pyhd8ed1ab_0.tar.bz2
-    "pillow",
+    "pillow !=7.1.0,!=7.1.1",
noarch::napari-0.4.2-pyhd8ed1ab_0.tar.bz2
-    "pillow",
+    "pillow !=7.1.0,!=7.1.1",
noarch::napari-0.4.3-pyhd8ed1ab_0.tar.bz2
-    "pillow",
+    "pillow !=7.1.0,!=7.1.1",
noarch::napari-0.4.4-pyhd8ed1ab_0.tar.bz2
-    "pillow",
+    "pillow !=7.1.0,!=7.1.1",
noarch::napari-0.4.5-pyhd8ed1ab_0.tar.bz2
-    "pillow",
+    "pillow !=7.1.0,!=7.1.1",
noarch::napari-0.4.6-pyhd8ed1ab_0.tar.bz2
-    "pillow",
+    "pillow !=7.1.0,!=7.1.1",
noarch::napari-0.4.7-pyhd8ed1ab_0.tar.bz2
-    "pillow",
+    "pillow !=7.1.0,!=7.1.1",
noarch::napari-0.4.8-pyhd8ed1ab_0.tar.bz2
-    "pillow",
+    "pillow !=7.1.0,!=7.1.1",
noarch::napari-0.4.9-pyhd8ed1ab_0.tar.bz2
-    "pillow",
+    "pillow !=7.1.0,!=7.1.1",
Downloading: https://conda.anaconda.org/conda-forge/linux-64/repodata_from_packages.json.bz2
Downloading: https://conda.anaconda.org/conda-forge/linux-64/repodata.json.bz2
linux-64::h5utils-1.13.1-mpi_mpich_h88c8ee5_1012.tar.bz2
-    "mpich >=3.4,<3.5.0a0",
+    "mpich >=3.4,<4.0.0a0",
linux-64::h5utils-1.13.1-mpi_mpich_ha777a55_1012.tar.bz2
-    "mpich >=3.4,<3.5.0a0",
+    "mpich >=3.4,<4.0.0a0",
Downloading: https://conda.anaconda.org/conda-forge/linux-armv7l/repodata_from_packages.json.bz2
Downloading: https://conda.anaconda.org/conda-forge/linux-armv7l/repodata.json.bz2
Downloading: https://conda.anaconda.org/conda-forge/linux-aarch64/repodata_from_packages.json.bz2
Downloading: https://conda.anaconda.org/conda-forge/linux-aarch64/repodata.json.bz2
Downloading: https://conda.anaconda.org/conda-forge/linux-ppc64le/repodata_from_packages.json.bz2
Downloading: https://conda.anaconda.org/conda-forge/linux-ppc64le/repodata.json.bz2
Downloading: https://conda.anaconda.org/conda-forge/osx-64/repodata_from_packages.json.bz2
Downloading: https://conda.anaconda.org/conda-forge/osx-64/repodata.json.bz2
osx-64::h5utils-1.13.1-mpi_mpich_h99bf298_1012.tar.bz2
-    "mpich >=3.4,<3.5.0a0",
+    "mpich >=3.4,<4.0.0a0",
osx-64::h5utils-1.13.1-mpi_mpich_hab242fb_1012.tar.bz2
-    "mpich >=3.4,<3.5.0a0",
+    "mpich >=3.4,<4.0.0a0",
Downloading: https://conda.anaconda.org/conda-forge/osx-arm64/repodata_from_packages.json.bz2
Downloading: https://conda.anaconda.org/conda-forge/osx-arm64/repodata.json.bz2
Downloading: https://conda.anaconda.org/conda-forge/win-32/repodata_from_packages.json.bz2
Downloading: https://conda.anaconda.org/conda-forge/win-32/repodata.json.bz2
Downloading: https://conda.anaconda.org/conda-forge/win-64/repodata_from_packages.json.bz2
Downloading: https://conda.anaconda.org/conda-forge/win-64/repodata.json.bz2

Can anybody at @conda-forge/core tell me if I am doing this right? It looks ok but you never know :D

LGTM!

Thanks!!


feat: Add TextAnalyze transformer to add support for Text Analytics /analyze endpoint

The Text Analytics /analyze endpoint  provides a way to perform multiple tasks in a single API call (good for high-throughput scenarios)

[X] Add TextAnalyze
[X] Restructure results to be by document, then by task
[x] Add options for defining which tasks to perform
[x] Add sample notebook

/azp run

Codecov Report

Merging #1267 (5cb9f77) into master (175fbc5) will decrease coverage by 75.73%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master   #1267       +/-   ##
==========================================
- Coverage   83.13%   7.39%   -75.74%
==========================================
  Files         300     248       -52
  Lines       13699   12138     -1561
  Branches      660     669        +9
==========================================
- Hits        11389     898    -10491
- Misses       2310   11240     +8930

Impacted Files
Coverage Δ

...re/synapse/ml/cognitive/CognitiveServiceBase.scala
0.00% <0.00%> (-76.34%)
:arrow_down:

...ft/azure/synapse/ml/cognitive/ComputerVision.scala
0.00% <0.00%> (-78.58%)
:arrow_down:

...oft/azure/synapse/ml/cognitive/TextAnalytics.scala
0.00% <0.00%> (-86.34%)
:arrow_down:

...re/synapse/ml/cognitive/TextAnalyticsSchemas.scala
0.00% <0.00%> (-100.00%)
:arrow_down:

...m/src/main/scala/com/microsoft/lightgbm/SWIG.scala
0.00% <0.00%> (-100.00%)
:arrow_down:

...ain/scala/org/apache/spark/ml/param/MapParam.scala
0.00% <0.00%> (-100.00%)
:arrow_down:

...cala/org/apache/spark/ml/param/DataTypeParam.scala
0.00% <0.00%> (-100.00%)
:arrow_down:

...ala/org/apache/spark/ml/param/ByteArrayParam.scala
0.00% <0.00%> (-100.00%)
:arrow_down:

...ala/org/apache/spark/ml/param/EvaluatorParam.scala
0.00% <0.00%> (-100.00%)
:arrow_down:

...la/org/apache/spark/ml/param/ParamSpaceParam.scala
0.00% <0.00%> (-100.00%)
:arrow_down:

... and 273 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 175fbc5...5cb9f77.


[Tracking/Action] Repair: how broken Kubernetes workloads lead to higher emissions

(ticket is part of sustainable k8s practices project work)
Description
What is the carbon cost of leaving broken workloads to run on Kubernetes? What is the untapped potential of making sure workloads repair themselves better, or that broken workloads aren't allowed to run for a long time? Is there a good "Kubernetes hygiene" around repairing workloads that can lead to lowering a cluster's carbon cost?
Outcome
A recommendation in our working document that helps the reader make a choice on how to repair their workloads, with an effort estimation (small, medium, large). Optional extra reading material with extra context if the reader's interested.
To-Do

[x] add relevant labels to this issue when possible,
[ ] research if this is a worthy recommendation,
[ ] if yes, write a recommendation,
[ ] share it for review, implement feedback.

Comments

Only public cloud is in scope here.
I'm gonna work on writing this recommendation. 🙂

@mkorbi I'd love your input on this issue description, do you feel this captures the fullness of what we talked about?
(cc @JacobValdemar)

Just an update that I did start working on this and should hopefully have a draft by the end of the week.

@mkorbi thanks for extra context. So there are two repair paths:

the ones internal to Kubernetes:

can we make any gains by setting a specific restartPolicy?
liveness and readiness checks: we cat make sure the liveness checks we define for Pods are actually measuring what we think they are
something else?

the ones where we need to have a good understanding that liveness/readiness checks are not enough and we should rather use external metrics that can alert us about broken workloads:

use request rate and latency metrics exposed by the ingress (for example nginx) together with resource usage metrics to hint at unhealthy ratios
other use cases:

running outdated or misconfigured software

I would argue choices around programming language / outdated software is outside of the scope of this project in its first run, since if I remember correctly we agreed to not cross the Pod barrier.
Does this make sense?

I wrote a high-level introduction to this in the working document. It's difficult for me to gauge if the level of detail is ok. The next step will be describing examples.
The challenge for me here is that it's quite difficult to be specific about carbon cost since workloads can be very different, so I am hoping to provide a few high-level examples.
This is very, very much a work in progress so all feedback is more than welcome, good or bad. 🙂

[...] Does this make sense?

&

[...] This is very, very much a work in progress so all feedback is more than welcome, good or bad. 🙂

cc @mkorbi @saiyam1814

I will have a look
Founder, Kubesimplify
https://saiyampathak.com/youtube
https://www.linkedin.com/in/saiyampathak/
https://twitter.com/saiyampathak
On Sun, 16 Jun 2024 at 4:58 PM, Leonard Vincent Simon Pahlke <
@.***> wrote:

[...] Does this make sense?
&
[...] This is very, very much a work in progress so all feedback is more
than welcome, good or bad. 🙂
cc @mkorbi https://github.com/mkorbi @saiyam1814
https://github.com/saiyam1814
—
Reply to this email directly, view it on GitHub
https://github.com/cncf/tag-env-sustainability/issues/365#issuecomment-2171449464,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB6PRIVRYJG6T63ZGVKN45TZHVZFTAVCNFSM6AAAAABFVBZKUGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNZRGQ2DSNBWGQ
.
You are receiving this because you were mentioned.Message ID:
@.***>


Converts src to ES6

Overview
Modernizes the source code by converting to ES6 and using Babel es2015 (loose mode) to transpile to ES5. Also replaces jshint with eslint.

Merging to master?

Oops, fixed! I also need to merge in changes from Dev.

Just rebase onto lastest dev

@drkibitz Not sure I follow. Can you explain?

The comment was made before the _tick method was actually meant to be bound, the commit to change to an ES6 class was what made it make no sense, this change just fixes that commit's functionality. The comment is basically saying, this is an internal closure because Function.bind is still slow, but now it's bound using Function.bind. It doesn't make sense. Either remove the comment or don't use Function.bind. Keep in mind, yes, it is almost 2 years, later and Function.bind is still slow.

@drkibitz Cool, I think I address your concern. Is that okay with you?

@bigtimebuddy in that case :+1:


[ci skip] adding user @j-rivero

Hi! This is the friendly automated conda-forge-webservice.
I've added user @j-rivero as instructed in #7.
Merge this PR to add the user. Please do not rerender this PR or change it in any way. It has [ci skip] in the commit message to avoid pushing a new build and so the build configuration in the feedstock should not be changed.
Please contact conda-forge/core to have this PR merged, if the maintainer is unresponsive.
Fixes #7

@wolfv can you look into this PR? Thanks!


'policy.fromFieldPath: Required': spec.xxx: no such field

What happened?
So, we added the function-cel-filter after initially trying to use it embedded in function-patch-and-transform. Now, we're facing an issue where using function-cel-filter to filter resources causes required patches to fail in function-patch-and-transform, resulting in the XR getting READY: False.
Does anyone have an idea for a workaround for this behavior?
kubectl get xinit
NAME                     CROSSPLANE     SYNCED   READY   COMPOSITION               AGE
space-seed-j29p9-j8fq5   v1.15.2-up.1   True     False   xinit.spaces.upbound.io   13m

  Warning  ComposeResources         4m57s (x14 over 10m)  defined/compositeresourcedefinition.apiextensions.crossplane.io  Pipeline step "patch-and-transform": not adding new composed resource "external-dns-irsa" to desired state because "CombineFromComposite" patch at index 2 has 'policy.fromFieldPath: Required': spec.parameters.operators.externaldns: no such field

How can we reproduce it?

What environment did it happen in?
Function version:

Are you saying a patch from a required field fails if the CEL filter function prevents the required field from existing (e.g. by filtering the resource)? Or something else?

I filter resources using cel-filter, but this runs after P&T. This causes P&T to fail because some filtered resources have required fields that are not available.

let me add an reproducer


Construction Error Recovery

When application is bootstrapped and instances get constructed and injected the construction might throw an exception and fail. Such problem would propagate upwards and fail the whole bootstrapping process. Sometimes this is not what maintainers would want to happen - instead if would be preferable having the part fail to bootstrap (and cause runtime errors later on where the part was supposed to be used) but have the whole bootstrapping complete successful.
For this to work the container needs to be aware if and where exceptions during construction should be recovered and instead injected as null or with some other default.

maybe it could expect failure as a specific 'ambiguous' state containing the known missing or conflicting data.  a user could then interactively resolve these dynamically either through code changes or a UI with autogenerated widgets to help disambiguate to valid models.  maybe something like this already exists in the code, i didnt look carefully but this issue is the closest thing.  ive been wanting a smart dynamic DI container that works like that and silk seems capable of it

@automenta I'm not sure if silk container is what you are looking for. It is intentionally not dynamic in the sense that the full mapping must be given at bootstrapping. No mappings can be added or removed later on. That does not mean that it cannot show behaviour that occurs to be dynamic, just like the described error recovery, but such behaviour would need to be mapped before hand and not on the basis of how the bootstrapping went so far. This is so the container stays predictable for the developers. Because of this design a wide range of mappings are supported that give very detailed control over when a mapping applies.
The idea with the error recovery was that I could extend the types of mapping adding a FALLBACK type that would specifically be used when another mapping that usually would be used fails to construct the instance.

yes it would involve a loss of predictability - the reasons are better explained in these incomplete prototypes:
https://github.com/automenta/objenome
https://github.com/automenta/objenome_prototype
:joystick:

The first thing that comes to mind reading automated assembly is require & provide in silk. These are mapping types. Provide "says", look I know how to provide X so ask me if that is what is needed while require expresses the need of a particular component, e.g. X where X can be narrowed by java relevant properties like the interface it implements, the package, parent or target instance. This allows to build loosely coupled modules that assemble together without knowing each other based on the contracts used to bind them together.
Now, is there any particular scenario you want to solve that you want me to comment on?

After looking at your example it might be that you are mostly just looking for the way bundles and modules work in silk where you can describe assembly locally and later compose apps by composing module descriptions. The only difference is that everything is deterministic in silk. Its like functional programming where you describe how you want your universe to be defined. Silk then makes that happen.

it makes sense to use the deterministic components you refer to for a non-deterministic API...  unless there's a benefit to representing the non-deterministic parameters (if any) in the same model as the deterministic configuration. ex: to allow changes between determinstic and non-deterministic (which is the approach in my prototypes).
mainly i was wondering if you or anyone else have interest in something like this semi-wired state that can be iteratively disambiguated (or re-ambiguated).  ex: as abstract branch point for non-interactive program evolution, objective optimization, etc.. or as a GUI form generator for prompting a user for providable data.
if theres anything i can explain ill be glad to otherwise this is not urgent
thanks

in general. but the two incomplete prototypes i linked to could be considered a proof of the concept

I am afraid you're kind of asking the wrong person. I made silk because of the unpredictable, deeply frustrating and limited nature of existing DI containers. Having a semi-wired state must be somewhere on the opposite end of what I would want to have.
Maybe Paul Phillips has some useful advice for you https://youtu.be/TS1lpKBMkgg?t=1701

thanks for clarifying your opinion.  this advice isnt relevant to the use cases i'm interested in

Take it as general advice on design. It kind of always applies.

        Multitainer g = new Multitainer();
        g.any(Part.class, of(Part0.class, Part1.class, PartN.class));
        g.any(OtherPart.class, of(OtherPart0.class, OhterPart1.class));
        g.is("floatField", in(0, 3.14159));
        Objenome o = g.random(Machine.class);
        Machine m = o.get(Machine.class);

this doesnt build a specific solution but a space of solutions that a search process can sample from.  silk seems flexible enough that if it doesnt already somehow support these semantics in its metamodel, it could be extended to. but the same is true for nearly every other dynamic DI framework.

Yes, you could add a few bits and practically be there. Do you want advice on how to modify silk?

Deleted a conversation that was off-topic for this issue.

This can be done in a similar way optionals are working. However, for arrays that are composed of many resources one would like to recover/skip those that fail getting just those that succeed injected.
interface Obtainable<T> {
  T obtain();
}

Should T be an 1-dimensional array type it tries to resolve resources for that element type and assembles the array from those succeeding.

Resolved by adding Obtainable as a installable core feature in #120. Similar error recovery mechanisms equally can be build in user space.


Feature addition

Hey Miguel,
Further to my comment on twitter, I thought an additional feature would be helpful if you had the time to implement it. The request is to add in an intermediate glyph function as in the space centre, so one might view all diacritics between certain strings. This function would provide  the ability to add a single space in between each glyph also, some times when diacritics very close together I find it hard to judge their justification. Thank you providing such a crucial part of my workflow!
Best,
Dave

@FosterType I've just pushed some changes (version 1.2.0) that allow increasing the glyphs' side bearings, and therefore the space between adjacent glyphs.
Being able to insert glyphs between the accented glyphs will come next.

Hey Miguel,
Thanks for integrating the idea so quickly, this will be a big help.
Dave
Dave Foster · Type & Lettering
+61 (0)404 228 086 · fostertype.com
Twitter http://twitter.com/fostertype · Instagram
http://instagram.com/fostertype · Facebook
http://facebook.com/fostertype
Sydney, Australia
On 21 October 2015 at 09:22, Miguel Sousa<EMAIL_ADDRESS>wrote:

@FosterType https://github.com/FosterType I've just pushed some changes
(version 1.2.0) that allow increasing the glyphs' side bearings, and
therefore the space between adjacent glyphs.
Being able to insert glyphs between the accented glyphs will come next.
—
Reply to this email directly or view it on GitHub
https://github.com/adobe-type-tools/robofont-extensions/issues/5#issuecomment-149719848
.

Insertion of extra glyphs is now supported. Enjoy!

Massively helpful addition mate cheers!
Sent from my iPhone

On 25 Oct 2015, at 4:41 pm, Miguel Sousa<EMAIL_ADDRESS>wrote:
Insertion of extra glyphs is now supported. Enjoy!
—
Reply to this email directly or view it on GitHub.


Rx expander destroys audio when FM

Rx expander destroys audio when FM. Just enable RX or TX/RX in menu 31 and listen to FM station.

I can't find an fm stations to listen too at the moment where I live.
But yes it will sound bad, the TX station needs to enable TX TX/RX mode it there end. They need to match to use the compander.

Modulation should not impact compander. There should not be any difference between AM or FM because clear audio is processed independly in used modulation.

Hi. Yesterday I enabled TX+RX Compander in my two UV-K5s running your last firmware release.  I did a quick test talking each other on FM  2 meter band, and the result was the same as if no compander was set in TX:  received audio was super weak, hardly audible, as if volume had set to 0.  Then I just set compander to none, and voilá, perfect communication.  I think something could is wrong with this compander...

Yes, audio on FM is completly unusable when compander is used. On AM works in RX mode. I did not checked audio quality when TX or TX/RX is used on AM

I'm under the impression the compander doesn't apply to AM at all, only FM, as I hear no difference between options when listening to a local airport. I confirm I hear no audio on my modded K5(8) when transmitting from my stock 5R+ with RX compander enabled, regardless of what ratio I choose in code.
I don't think it's a software bug though, perhaps a hardware limitation.

Compander works in audio , not on modulated RF. So has to work in the same way on AM and FM.

The compander menu setting no longer appears for me, despite setting its flag to 1. I can't test any local changes.


Add snapshot dockerfiles

We need the snapshot images to be built by the CI too...

/lgtm
/approve
release-4.0 branch needs them too i guess

/lgtm


Retag Page HTML/CSS

@jmw0057 can you also include a picture of what it looks like?

This looks an works great Jenny!

LGTM


CORE-6858 Uniqueness checker error handling refinement

Summary
This PR makes improvements to the uniqueness checker error handling logic. Prior to this change, the uniqueness checker did not have a way of meaningfully communicating "exceptional" errors back to the client, i.e. errors that are not for business reasons such as double spend attempts, time window out of bounds etc.
In reality, there will always be some scenarios where the uniqueness checker needs to handle unexpected exceptions. This PR changes the behavior of the uniqueness checker so that:

Expected failures continue to return a UniquenessCheckResponse with a specific failure result type
Unexpected failures, i.e. exceptions that cannot be caught and handled gracefully by the uniqueness checker will now be mapped to a new UniquenessCheckResultUnhandledExceptionAvro object

In practice, the new object will not be returned to the client; the uniqueness message processor will instead convert such messages into a platform error result on the external events response, and will forward an ExceptionEnvelope with the error details. All other result types will continue to return success results (indicating the operation was successfully processed, as opposed to the transaction itself being successful).
Testing
New unit and message bus integration tests have been added to verify the expected behavior. At present, there is no easy way to force an exception to be raised reliably in integration tests, so the message bus integration tests use a customised fake backing store that can be made to throw an exception on demand.
It is likely that following implementation of dynamic uniqueness DB support (in a subsequent PR), it will be possible to force exceptions to be thrown by specifying a holding identity that does not have an associated uniqueness DB, which will remove the need for the customised fake object.

LGTM


Adding docker compose + windows compatiblity

Hi this pull request had the primary goal of adding a docker compose file, because i needed one for myself anyways.
I also added dos2unix into the Dockerfile, since it resolves some problems with git+windows+wsl+docker.
If you want to review that change separately I could create another pr for you.
Kind Regards
Lukas

Is  there any further action required from my side, or is this pr considered unnecessary ?


Rewrite getcallerpc() and getcallstack() in assembler.

__builtin_return_address() kills the build with a warning when called with an argument greater than 0.

Spring cleaning - closing old issues


fix: check buffer valid before set diagnostic

The error happens when deleting the buffer.

Thanks for the PR :+1:


fix growable negative keys

Pyarrow creates dictionary keys with negative integers, that are masked out by the validity bitmap.
This PR fixes conversion from those negative integers to usize, they are mapped to 0, and that is ok, because the values are masked.
Related downstream issue: https://github.com/pola-rs/polars/issues/1686
Additionally the scalar API also read masked out values, so was incorrect.

It indeed can take a while before it is fixed in pyarrow, as pyarrow 6.0.0 is released a few days ago.

wow, this looks like a vulnerability to me on the c++ side. if someone accesses those keys, they may read out of bounds if they do not check bounds (which some implementations do). I think this should be addressed in the pyarrow implementation: dictionary keys and offset deltas should never be negative. I think that our implementation is correct: it is the user responsibility to ensure that the keys are positive, even if the type is a signed integer (for JVM reasons).
I will follow up on this on the Arrow side.

What do you think about a temporary patch? ^_^. Before a new pyarrow is shipped to all pandas code that uses this, I guess that will take some months. :see_no_evil:


First pass refactor - June 2022 - O'Cathail, C

I've had a first pass at a refactor of the code.

Path module  from pathlib library implemented instead of using os module to improve code readability. Cuts down on complex os.path.joins and other complex os implementations. Import of os module removed due to no longer being called.
Code reformatted using black. Stylistic choice but enforces a standard of readability.
Updated --directory argument to a required=True.

Script runs but extensive testing not yet completed. Suggest testing on wide range of test submissions that work on previous versions to ensure pathlib implementation correctly mimics all os.* implementations.

Thanks for the changes in the code. I have tested the changes, and submissions seem to work fine. Before you merging with main, please can you make the following changes:

Please can you add '.DS_Store' to the .gitignore file, and also remove it from the PR, so that it doesn't get included in the final merge.
Check the comments that I will leave/have left in the code block for the script and update accordingly.
Just out of curiosity was there a specific reason for making --directory a required argument?

Many thanks!


Delete dataframes

This PR contains the delete dataframe feature. The data owner(s) is the only user allowed to delete dataframes. Other users that attempt to perform a deletion are rejected.
The API is as follows: client.polars.delete_df(identifier). The server returns nothing if successful.
I chose this API as opposed to the save API of rdf.save() because the owner might want to simply list dfs and use that list to delete dataframes without retrieveing each as FetchableLazyFrames.

I don't agree with the API choice as list_dfs returns FetchableLazyFrames

Don't merge this yet because it has it's own version of verify owner that Laura has done in her PR. I will alter it to match hers.


[stable/kube-ops-view] Upgraded to 0.11.

What this PR does / why we need it:
New release.
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[X] DCO signed
[X] Chart Version bumped

/lgtm

@jpds thanks, LGTM

I'm not using Helm myself, but apparently RBAC is something to address: https://github.com/hjacobs/kube-ops-view/issues/225

/assign
/ok-to-test

/lgtm
thanks for contributing!


fix(typography): add correct optional class names for h1-h6

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Namplate distance

Is there a way to increase Namplate view distance beyound 41?

Yes. This value is also hardcoded, so you'll have to change it with the --nameplatedistance parameter when running the patcher.


[Bug]: StreamingResponse class constructor not accepting keyword arguments

Bug Description
For context, I'm using python 3.8 in a fastapi endpoint that streams to a react frontend.
Instantiating the StreamingResponse class object works fine if you only pass in a response_gen object as a positional argument, as shown in your documentation examples.
Python throws a TypeError if you pass the argument as keyword argument as follows:
streaming_response = StreamingResponse(
        response_gen=query_engine.query(user_input).response_gen,
        extra_info={"source_url": source_url}
        )

Error message:
streaming_response = StreamingResponse(
TypeError: __init__() got an unexpected keyword argument 'response_gen'

This also occurs for extra_info, if you pass response_gen as positional, and extra_info as keyword argument as follows:
streaming_response = StreamingResponse(
        query_engine.query(user_input).response_gen,
        extra_info={"source_url": source_url}
        )

Error message:
TypeError: __init__() got an unexpected keyword argument 'extra_info'

I can't find a syntax related cause for this. The @dataclass decorator provides an automatically generated init() method, but it seems to not like keyword arguments. According to python docs, keyword args should be fine for dataclass constructors.
I've also tried just passing everything as a positional argument, but there's a separate issue where source_nodes won't take a list of nodes, as the documentation would suggest. So I need to pass extra_info as a keyword argument.
Version
0.6.20
Steps to Reproduce
This setup assumes an index has already been built and stored in a directory.
This is part of a fastapi endpoint, but this script-style setup should explain what I'm doing sufficiently.
setup LLM
llm_predictor = LLMPredictor(llm=ChatOpenAI(model_name="gpt-3.5-turbo", streaming=True))
service_context = ServiceContext.from_defaults(llm_predictor=llm_predictor)
rebuild storage context
storage_context = StorageContext.from_defaults(persist_dir="/some/data/directory")
load index
index = load_index_from_storage(storage_context, service_context=service_context)
query the index
query_engine = index.as_query_engine(
streaming=True,
similarity_top_k=1
)
use user input to retrieve nodes
retriever = index.as_retriever()
nodes = retriever.retrieve(user_input)
create the response streaming object
I'm using a custom method (not shown here) to get the source_url
streaming_response = StreamingResponse(
response_gen=query_engine.query(user_input).response_gen,
extra_info={"source_url": source_url}
)
pass the response stream to frontend GUI
return streaming_response
Relevant Logs/Tracbacks
ERROR:    Exception in ASGI application
Traceback (most recent call last):
  File "pve1/lib/python3.8/site-packages/uvicorn/protocols/http/h11_impl.py", line 428, in run_asgi
    result = await app(  # type: ignore[func-returns-value]
  File "pve1/lib/python3.8/site-packages/uvicorn/middleware/proxy_headers.py", line 78, in __call__
    return await self.app(scope, receive, send)
  File "pve1/lib/python3.8/site-packages/fastapi/applications.py", line 276, in __call__
    await super().__call__(scope, receive, send)
  File "pve1/lib/python3.8/site-packages/starlette/applications.py", line 122, in __call__
    await self.middleware_stack(scope, receive, send)
  File "pve1/lib/python3.8/site-packages/starlette/middleware/errors.py", line 184, in __call__
    raise exc
  File "pve1/lib/python3.8/site-packages/starlette/middleware/errors.py", line 162, in __call__
    await self.app(scope, receive, _send)
  File "pve1/lib/python3.8/site-packages/starlette/middleware/cors.py", line 92, in __call__
    await self.simple_response(scope, receive, send, request_headers=headers)
  File "pve1/lib/python3.8/site-packages/starlette/middleware/cors.py", line 147, in simple_response
    await self.app(scope, receive, send)
  File "pve1/lib/python3.8/site-packages/starlette/middleware/exceptions.py", line 79, in __call__
    raise exc
  File "pve1/lib/python3.8/site-packages/starlette/middleware/exceptions.py", line 68, in __call__
    await self.app(scope, receive, sender)
  File "pve1/lib/python3.8/site-packages/fastapi/middleware/asyncexitstack.py", line 21, in __call__
    raise e
  File "pve1/lib/python3.8/site-packages/fastapi/middleware/asyncexitstack.py", line 18, in __call__
    await self.app(scope, receive, send)
  File "pve1/lib/python3.8/site-packages/starlette/routing.py", line 718, in __call__
    await route.handle(scope, receive, send)
  File "pve1/lib/python3.8/site-packages/starlette/routing.py", line 276, in handle
    await self.app(scope, receive, send)
  File "pve1/lib/python3.8/site-packages/starlette/routing.py", line 66, in app
    response = await func(request)
  File "pve1/lib/python3.8/site-packages/fastapi/routing.py", line 237, in app
    raw_response = await run_endpoint_function(
  File "pve1/lib/python3.8/site-packages/fastapi/routing.py", line 163, in run_endpoint_function
    return await dependant.call(**values)
  File "/my/chatbot/app/backend/main.py", line 298, in sse_endpoint
    streaming_response = StreamingResponse(
TypeError: __init__() got an unexpected keyword argument 'response_gen'

Okay, so you can safely disregard this entire issue.
I was importing fastAPI's StreamingResponse and trying to use LlamaIndex's StreamingResponse.
Didn't realize there was a naming conflict there.


Change cost field to be whole integers only

Is your feature request related to a problem? Please describe.
Using the Buy/Sell modifier slider results in fractional values for Cost....for instance, 3.45 gold coin.  For me, this is a level unneeded detail and I worry that it may impact other systems/modules functioning correctly.
Describe the solution you'd like
I would like to see the cost of items rounded to the nearest integer.
Describe alternatives you've considered
Perhaps this is a module setting option, either whole integers or fractional values.  Fractional values may be desired in 'modern' or realistic settings.

As a follow-up question, which roleplaying system are you using this module in?

I am using the SWADE system


Dark Theme Toggler

Describe the solution you'd like
A clear and concise description of what you want to happen.
Make dark theme for this project using Javascript.

hey, I am taking up this issue!  assign me

hey, I am taking up this issue! assign me

Go for it @anjali1102

@anjali1102 any update ?

I will give PR by today. Can you add [ crossWoc, difficulty level ]  labels on this issue?

@anjali1102 any update ?

Dark theme mode is to be only on main page only or it should be applicable on project pages too? @urvashi-code1255

Dark theme mode is to be only on main page only or it should be applicable on project pages too? @urvashi-code1255

Hi @anjali just make it for main website for now!


Be more explicit with 'page' and 'pageSize' accepted values

Closed: pagination params have been removed for now for other reasons.