Handle figures with multiple subplots

Currently haven't even tried this.
I originally thought you could just use a list of axes objects, get the leftmost and rightmost bounds, find the adjustment needed, divide by ncols, then adjust each one. It's not quite that simple though. Need to look more at how fig.tight_layout et al. work internally. Using subplots_adjust directly may be the way to go, possibly in combination with some of the functions in the matplotlib.tight_layout module.

Resolved by #4 which needs review, possibly packaging?


[PDI-14699] Encrypted passwords do not work in Salesforce / IBM WebSp…

…here MQ steps

@pamval, @pedrofvteixeira , could you run WM on this PR?

http://<IP_ADDRESS>:8080/job/wingman-osgi/93/

Build Commands:
Build:

ant -Dtestreports.dir=bin/reports/unit-test -Djunit.jvmargs=-XX:PermSize=256m -f plugins/salesforce/build.xml clean-all resolve jacoco && ant -Dpentaho.coding.standards.version=1.0.4 -Dtestreports.dir=bin/reports/integration-test -Djunit.jvmargs=-XX:PermSize=256m -f plugins/salesforce/build.xml jacoco-integration checkstyle publish-local

Cleanup:
rm -r ~/.ivy2/local || echo no publish local to remove
Changed files:
plugins/salesforce/src/org/pentaho/di/trans/steps/salesforceinput/SalesforceConnection.java
plugins/salesforce/test-src/org/pentaho/di/trans/steps/salesforceinput/SalesforceConnectionIT.java
plugins/salesforce/test-src/org/pentaho/di/trans/steps/salesforceinput/SalesforceConnectionTest.java
Unit test coverage change:
org.pentaho.di.trans.steps.salesforceinput.SalesforceConnection:

Branch Change :  + 4.05%
Complexity Change :  + 7.24%
Instruction Change :  + 7.67%
Line Change :  + 11.12%
Method Change :  + 16.23%

Integration test coverage change:
org.pentaho.di.trans.steps.salesforceinput.SalesforceConnection:

Branch New Coverage : 4.86%
Complexity New Coverage : 8.38%
Instruction New Coverage : 11.46%
Line New Coverage : 17.54%
Method New Coverage : 27.27%

@bmorrise, The wingman did not found any problem. Could you please review it?


H

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

Hi!  Im Github App / Bot!  Thanks for submitting issue!  This issue is now on status 'triage'  Note: In this account is owner too.


tput: No value for $TERM and no -T specified

on Linux Mint 19 Cinnamon
to reproduce:
from simple_term_menu import TerminalMenu
 terminal_menu = TerminalMenu(["entry 1", "entry 2", "entry 3"])
 terminal_menu.show()

tput: No value for $TERM and no -T specified
line 3, in
terminal_menu = TerminalMenu(["entry 1", "entry 2", "entry 3"])
very new to python and programing so forgive me if this is easily fixed

Hey @error13 and welcome to Python programming!
The TERM variable is usually set by your terminal emulator and is used by tput to generate the correct control codes for things like cursor movement, text formatting and others. Which terminal emulator do you use?

Terminator

As a first workaround you could call Python like this:
TERM=xterm-256color python

But I don't know why this is necessary for your setup. I will fetch Linux Mint 19 and try to run simple-term-menu with Terminator.

I cannot reproduce your problem on a fresh Linux Mint 19 Cinnamon in Terminator :disappointed:.

interesting... i did manage to get the code to run correctly  with the work around.  TERM=xterm-256color python. i will have to try it in a virtualBox  running a different version of mint. and see what happens. its not a bug on your part. so  thank you for your help!  its a very nice program


RemovePage in Navigation crash

Xamarin.Android Version : <IP_ADDRESS>
Operating System & Version: Windows 8.1
Support Libraries Version: 25.3.1
Describe your Issue:
After upgrading the various Xamarin.Android.XXXX packages from 23.3.0 to 25.3.1 with NuGet, an app will crash when using Page.Navigation.RemovePage (for example to remove the page below the top page on the stack) and then Page.Navigation.AsyncPop().
Steps to Reproduce (with link to sample solution if possible):

Add three pages in navigation stasck
Remove one of them with RemovePage method
Call PopAsync method

Expected Results
You will be returned to page 1
Actual Results
The app crashes

I also have the same problem

You would want to support this on the Xamarin.Forms bugzilla as it doesn't pertain to the support libraries.


replace ReferenceValue with Self in Value

Returning Self instead of ReferenceValue to lower the complexity

Codecov Report
All modified lines are covered by tests :white_check_mark:

Comparison is base (6097235) 94.01% compared to head (e44a6bf) 94.01%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2210   +/-   ##
=======================================
  Coverage   94.01%   94.01%
=======================================
  Files         327      327
  Lines       65020    65013    -7
=======================================
- Hits        61131    61125    -6
+ Misses       3889     3888    -1

Files
Coverage Δ

src/core/json_utils.rs
98.14% <100.00%> (ø)

src/fastfield/writer.rs
92.80% <100.00%> (ø)

src/schema/document/de.rs
71.18% <100.00%> (ø)

src/schema/document/existing_type_impls.rs
23.14% <100.00%> (-3.41%)
:arrow_down:

src/schema/document/mod.rs
89.92% <100.00%> (-0.08%)
:arrow_down:

src/schema/document/owned_value.rs
89.44% <100.00%> (-0.04%)
:arrow_down:

src/schema/document/se.rs
90.68% <100.00%> (ø)

src/schema/document/value.rs
28.97% <ø> (ø)

... and 1 file with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Add automation for sonobuoy conformance test

Add an ability to run sonobuoy using ansible playbook.

Make it available to be run when provided with kubeconfig.

Upload results to aws bucket before running cleanup.

Completed as part of rancher validation test suite.


Multiple Labels

Is it currently possible to have multiple labels in a derived struct? Something like
#[derive(Debug, Clone, Deserialize, Serialize, Node, ToSchema)]
#[names("Person", "Investor")]
pub struct Person {
    #[id]
    pub name: String,
    pub description: String,
}

?

No not currently. There could be another attribute macro like in your example above. I'd be interested in that :)

This is now in the main branch and should be released later today.
#[derive(Node)]
#[labels("Person", "Investor")]
pub struct Person {
    #[id]
    pub name: String,
    pub description: String,
}

The attribute only comes into scope for Nodes, but the associated getter function, labels() is on both Nodes and Relations. For relations it's always an array with one element, the relationship type.


ModuleNotFoundError: No module named 'Crypto'

Uninstalled and reinstalled the scraper, now it gives me this error message when I try to run it

pip install pycryptodome

Yeah this issue was very weird
I think I may have been able to fix it by reseting the requirments file
check 2.7.8

pip install pycryptodome

Tells me that the requirement is already satisfied and still gives me the same error when I try to run the program

Okay it seems maybe your enviroment has issue
Try running these commands
pip3 uninstall crypto
pip3 uninstall pycrypto
pip3 install pycryptodome


perf: improvement the performance of calculating scroll offset

perf: improvement the performance of calculating scroll offset

Pull Request Test Coverage Report for Build 882393971

0 of 7 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.03%) to 2.118%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/useVirtual.ts
0
7
0.0%

Totals

Change from base Build 881705574:
-0.03%

Covered Lines:
7

Relevant Lines:
262

💛  - Coveralls


Event handler with modifier and no callback doesn't typecheck

If you do e.g. @keydown.space.prevent (notice the lack of ="someCallback"), you get this error Type 'undefined' is not assignable to type '((...payload: unknown[]) => void) | ((...args: any) => void)'. Having an event handler that only has a modifier and no callback is legal and useful, so it shouldn't give an error.

@keydown.space.prevent do not report error for me, please provide a repro case.

Seems like it happens on Vue components but not native HTML elements: https://github.com/henribru/volar-event-handler-repo

Fixed in 0.25.5.


Fixed #32124 -- Added per-view opt-out for APPEND_SLASH behavior.

Hey @jdufresne — This is ref your #13134 for ticket-31747.
It's just the first part but the idea is to allow individual views to opt-out of APPEND_SLASH. This is for people who want the URL normalisation (so they don't want to just set APPEND_SLASH = False) but also have a sensitive_view that they want to exclude.
Phase 2 would then be to combine it with your patch in #13134, to allow an sensitive_admin_view to equally be hidden from a staff-member that wasn't meant to be allow to discover the URL, via enumerating admin URLs. (Non-staff members already handled by your patch.) For situations where that's not sufficient, I'd say folks just have to set APPEND_SLASH = False.
Hopefully this kind of thing would satisfy all the considerations. What do you think? Thanks!

With _should_append_slash I had in mind do_not_call_in_templates but I realize that's not got an underscore. So we can rename (or use a decorator, or...)

cc. @adamchainz this was the adjustment I was thinking about that we were talking about last week.
The return value for is_valid_path() would be -> Union[ResolverMatch, Literal[False]]. It's crying out to be an Optional[ResolverMatch], but that would be a bigger refactoring.
Anyhoo...

Updated with a new decorator based approach.


[Bug]: The SSL connection could not be established when installing the sumatrapdf

Prerequisites

[X] I have written a descriptive issue title.
[X] I have searched all issues/PRs to ensure it has not already been reported or fixed.
[X] I have verified that I am using the latest version of Scoop and corresponding bucket.

Package Name
sumatrapdf
Expected/Current Behaviour
When i want to insall sumatrapdf:
scoop install sumatrapdf
WARN  Purging previous failed installation of sumatrapdf.
ERROR 'sumatrapdf' isn't installed correctly.
Removing older version (3.4.6).
'sumatrapdf' was uninstalled.
Installing 'sumatrapdf' (3.4.6) [64bit] from extras bucket
The SSL connection could not be established, see inner exception.
URL https://files.sumatrapdfreader.org/file/kjk-files/software/sumatrapdf/rel/3.4.6/SumatraPDF-3.4.6-64.zip is not valid

Steps to Reproduce
scoop install sumatrapdf

Possible Solution
it might be a ssl problem, but i don't know how to fix it.
Scoop and Buckets Version
scoop --version
Current Scoop version:
v0.3.1 - Released at 2022-11-15

'dorado' bucket:
e2d2da19 (HEAD -> master, origin/master, origin/HEAD) jianyingpro: Update to version <IP_ADDRESS>91, fix checkver

'extras' bucket:
dbb4df8f8 (HEAD -> master, origin/master, origin/HEAD) twitchdownloader: Update to version 1.53.5

'java' bucket:
54652ba7 (HEAD -> master, origin/master, origin/HEAD) temurin8-nightly-jre: Update to version 8.0.402-2.0.202311201855

'main' bucket:
f229c99c0 (HEAD -> master, origin/master, origin/HEAD) twitchdownloader-cli: Update to version 1.53.5

'nerd-fonts' bucket:
6fd8de6 (HEAD -> master, origin/master, origin/HEAD) Monaspace-NF(,-Mono,-Propo): Add version 3.1.0 (#270)

'nirsoft' bucket:
604c906 (HEAD -> master, origin/master, origin/HEAD) Updated BrowsingHistoryView, ChromeHistoryView, DataProtectionDecryptor, ExtPassword, PingInfoView, USBDeview

'nonportable' bucket:
d3fa3f6 (HEAD -> master, origin/master, origin/HEAD) 10x-np: Update to version 1.0.96

'php' bucket:
a996045 (HEAD -> master, origin/master, origin/HEAD) php8.2: Update to version 8.2.12

'sysinternals' bucket:
692e651 (HEAD -> main, origin/main, origin/HEAD<EMAIL_ADDRESS>Fix hash (Closes #15)

'versions' bucket:
34b25e9cd (HEAD -> master, origin/master, origin/HEAD) vscode-insiders: Update to version 1.85.0-insider+1700629523671

Scoop Config
scoop config

last_update                     : 2023/11/22 19:30:22
aria2-enabled                   : False
aria2-min-split-size            : 1M
aria2-split                     : 16
aria2-max-connection-per-server : 16
scoop_branch                    : master
scoop_repo                      : https://github.com/ScoopInstaller/Scoop

PowerShell Version
Name                           Value
----                           -----
PSVersion                      7.3.9
PSEdition                      Core
GitCommitId                    7.3.9
OS                             Microsoft Windows 10.0.19045
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Additional Softwares
No response

12251


cleanup: removes redundant bg color settings

Removes redundant background color settings for sections that contain container settings

@jeremyagabriel  done


Directory listing generation should be faster

Today this takes ~15 minutes which is quite long and with the current approach will only grow.
There are two incremental steps here:

We should only be generating an index for the "current upload"; not for the whole bucket. This is probably relatively easy and would be enough for quite a while.
Stop generating indices at upload and generate them client-side via a custom 404 page.

Context:

https://github.com/rust-lang/rust-central-station/blob/edbd48a4306b57b0029375cc62c28b0fcc130f1c/Dockerfile#L70-L78
"it's for things like https://static.rust-lang.org/dist/2018-06-26/index.html"
discussion: https://discordapp.com/channels/442252698964721669/443148319431065610/463408362139156520

This should no longer run on deploys so I'm closing the issue


Documentation to upgrade APEX

Most people who use this project aren't DBAs and don't know how to upgrade APEX.
Should there be an upgrade documentation?

Related to #99.
Pretty much I think for free users, you need to backup all apps and workspaces, also config in internal workspace, then uninstall and reinstall. I worked briefly on this in a project I called daxul, but probably needs some more love - bit experimental with the config export / import.

What do you mean "free user"?
So there's no way around a complete reinstall for a patch?

I believe @tschf is referring to Oracle XE users. Patch releases are only downloadable through MOS. You need to have a support contract with Oracle.

What do you mean "free user"?

I believe @tschf is referring to Oracle XE users. Patch releases are only downloadable through MOS.

Yes, exactly this. There is no way for me, as in independent developer, to get access to the patch sets. So, the only way for me to upgrade APEX would be drop it and re-install the latest version.
Of course, there are also people who use XE that do have a support contract (through work) and do have access to MOS. Maybe you're thinking of some docs for that scenario (where they can get the patch sets).

Closing this in favour of 99.


can cpuprofiler can used to attach to a runing process with pid?

can cpuprofiler can used to attach to a runing process with pid?

No. But you can link-to or preload libprofiler.so and activate profiling at runtime via either API or via sending signal as documented (see CPUPROFILESIGNAL).


Add interaction count to the IOC model

The IOC model already has a times_seen property that counts on how many extraction processes an IOC was extracted. But that does not represent the actual number of the attacker's interactions with the honeypot. But this information might also be valuable in some scenarios.

To make it easier to distinguish between them, maybe we could rename times_seen in something like attack_count and name the new property interaction_count?

agree, there is also the number_of_days_seen parameter that is similar and maybe this could stay the same.
In django, a data migration would be required for such change. At the same time, all the other references in the code should be updated

I need to read up on the data migration subject, but I'll give it a try.

Should we maybe keep the old field name in the API for compatibility?

which API are you referring to?

I'm referring to the feeds API. For example for someone who regularly retrieves /api/feeds/all/all/recent.json from some GreedyBear instance, renaming a property of the JSON object may break their process. That's why I thought about keeping the old field name in the current feeds API.

you mean whether they have some client doing computation on that field and expecting it, right?
Well yeah that's possible but we could also add that as a breaking change and make a new major release.
Another option could be to leave that feed like that as you mentioned and then possibly create new feeds with the additional data that you added.

I think I'd prefer the second option. I will revert renaming the field in the JSON feed in #407 and then create a PR for a feeds API v2 later.

After renaming it back at some places I changed my mind. I think this will become too confusing when the same value is called times_seen in half of the places and attack_count in the other half. Let's add it as a breaking change in a major version together with a reworked feeds API. Do you agree? Sorry for the back and forth.

np yes let's go through that


PHOENIX-7026 : Validate LAST_DDL_TIMESTAMP for write requests

Need to rethink the approach here. Validating metadata on the write path in the execute phase might be too early since there can be arbitrary number of executes for different tables before client calls commit and we might end up creating mutations using old metadata.


Add CI to prevent none used depends from being added not detected

In this PR https://github.com/sigp/discv5/pull/176 2 dependencies were added which aren't used. We should probably have a CI test to detect this. I am not sure if that is possible but I will look into it. This tastes like something a CI should detect

we can add udeps. I'll do that

I already did it

so sad


Support --log-uri in exec subcommand

This PR adds --log-uri flag for exec
sudo ctr t exec --log-uri="file:///tmp/1.txt" ...
Signed-off-by: Maksym Pavlenko<EMAIL_ADDRESS>

Codecov Report

Merging #3384 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #3384   +/-   ##
=======================================
  Coverage   45.05%   45.05%
=======================================
  Files         113      113
  Lines       12563    12563
=======================================
  Hits         5660     5660
  Misses       6049     6049
  Partials      854      854

Flag
Coverage Δ

#linux
48.98% <ø> (ø)
:arrow_up:

#windows
40.27% <ø> (ø)
: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 6617def...6b59b42. Read the comment docs.

Codecov Report

Merging #3384 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #3384   +/-   ##
=======================================
  Coverage   45.05%   45.05%
=======================================
  Files         113      113
  Lines       12563    12563
=======================================
  Hits         5660     5660
  Misses       6049     6049
  Partials      854      854

Flag
Coverage Δ

#linux
48.98% <ø> (ø)
:arrow_up:

#windows
40.27% <ø> (ø)
: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 6617def...6b59b42. Read the comment docs.

LGTM


Track object creation (and texture update) stack trace

Also expose tracked textures in the extension info call.
Thanks for the tool! Was super helpful in tracking down memory leaks we had in our Babylon.js project.
Note: webgl-memory.js release version is not updated.

Thanks! This seems like a good idea. I think though that, rather than specialize textures, it could just add the stacks to all resources.

Ok, I changed it so there's a new extension API function, ext.getResourcesInfo. You pass it a WebGL type. Example
const textures = ext.getResourcesInfo(WebGLTexture);

This way you can pass in anything WebGLBuffer, WebGLProgram, WebGLRenderbuffer, WebGLTransformFeeback, etc...
Notice it's not a string.


CMake Support

It would be great if dependencies using CMake were supported.
I would like to crosscompile git2go, which has libgit2 (which uses CMake) as a dependency.

+1, same case as above - I'm trying to cross compile a program with libgit2 statically linked.
CMake support would be really appreciated!

#63

I'd gladly accept PRs ;)

I tried it, but I can't seem to make it work. I cloned the repo and changed the process in build-debs.sh to use cmake. I have really no idea how to create the docker images myself. Every time I tried it, it would still pull the images from the docker repo and thus ignoring my changes D:

I'm trying to cross compile git2go as well. I was able to successfully build a small test project that uses git2go to both linux and windows from my mac by setting up modified docker containers that include a cross compiled version of libgit2. I laid out the commands here: https://github.com/jallwine/xgo-git2go-docker-image
It's a starting point.


CRRAutilityP_invP typo

Hello,
There is a small inconsistency/typo in the definition CRRAutilityP_invP. The argument in the function call is labeled u but in the parameter list it is labeled uP. As the argument is the marginal utility value, it should be uP everywhere if I understand correctly?

Yeah, this is a documentation error.  Will fix.


how to export and connect to a skill from consumer bot/documentation not updated

## Describe the bug
new release of bot composer 1.3.0 is done due to which few things have changed.
I was trying to export a skill bot and connect to that bot within another bot
by following documentation https://docs.microsoft.com/en-us/composer/how-to-export-a-skill.
Problem: how to connect to a skill ? and what is the difference between  skill endpoint and skill host end points?
Changes observed :
1)skill host endpoint  previously used to be like  http://localhost:3983/api/messages now changed to  http://localhost:3980/api/skills
2) there used to be a skill section in UI where we can connect to another skill  using skill manifest json file of a sill bot as mentioned in the documentation
https://docs.microsoft.com/en-us/composer/how-to-connect-to-a-skill
now how do i proceed further?

Version : bot composer 1.3.0 (released yesterday)
OS

[ ] Windows

To Reproduce
i have created 2 bots and generated manifest for skill bot and tried to use it in the consumer bot
with recent changes i don't find any place where i could use skill manifest json of a bot  as a skill in any  consumer bot.
documentation https://docs.microsoft.com/en-us/composer/how-to-connect-to-a-skill  says : Still on the Skills page, select + Connect to a new skill on the upper left corner of the toolbar to show the Add a skill windows."
now the problem is how to move forward from this step within bot composer 1.3.0?  i am unable to select " skill dialog name" and  "skill end point".

skills section in the left panel has been replaced with project settings
QUESTIONS :
1)as the 1.3.0 release is few hours old  i  would highly appreciate  some quick guidance  over here how to use a skill bot in another consumer bot.
2)is there any alternative to export skill as a manifest  for bot to bot conversation?  we need some quick solution to this problem
can anyone of the team help us in this regard?
@zhixzhan

Hi, FYI. The docs for Composer 1.3 release will be updated and published soon.

FYI. Composer docs just got published to live: https://docs.microsoft.com/en-us/composer/
Thanks!

Thanks @zxyanliu.
@Samirun most skill related UX are moving to this contextual menu, please try it and feel free to ping me.

@Samirun FYI. These are the skill-related docs you may find helpful:
https://docs.microsoft.com/en-us/composer/how-to-export-a-skill
https://docs.microsoft.com/en-us/composer/how-to-connect-to-a-skill
To provide accurate content, we will do docs patch releases in the coming few days.
Thanks again for your feedback!

great! really appreciate for the shared docs. thanks for the quick support.

@Samirun Thank you for using Composer! We really appreciate your feedback.

@zxyanliu  how to get manifest url for a  remote skill? or at least how to construct it? i think we also need documentation for this.

Hi, FYI. I am working on the content you guys requested on the docs patch releases.

FYI. I replied in another thread with content you may find helpful.
https://github.com/microsoft/BotFramework-Composer/issues/5350#issuecomment-747834390

Hi @Samirun Did you get it to work? Please let us know if you have further issues with this.

yeah it worked.No issues as of now. thanks

Thanks for the update and thanks again for your feedback!
I am closing this issue now because it has been addressed with updates to the documentation.
Thank you!


Powershell from-source build misses "ref" directory

Prerequisites

[X] Write a descriptive title.
[X] Make sure you are able to repro it on the latest released version
[X] Search the existing issues.
[X] Refer to the FAQ.
[X] Refer to Differences between Windows PowerShell 5.1 and PowerShell.

Steps to reproduce
Looks like some packages have to have the ref directory in the powershell home
($PSHOME is set to /usr/share/pwsh-7.3).
Here is an example of importing PowerShellGet, this complains about missfing ref.

Here importing PSDesiredStateConfiguration fails completely:

Also the Alpine package seems to have similar PSHOME contents, no ref directory, see: https://pkgs.alpinelinux.org/contents?repo=community&page=1&arch=x86_64&branch=edge&name=powershell
Expected behavior
Powershell build scripts copy or link to the location of required assemblies,
and so using those modules work.
Or use current runtime assemblies when the package is not "self-contained".
Actual behavior
While attempting to import PSDesiredStateConfiguration it fails to import fully, see below error.
Error details
While importing PSDesiredStateConfiguration:
Add-Type: Could not find a part of the path '/usr/share/pwsh-7.3/ref'.
Import-Module: The specified module
'/home/xy/.local/share/powershell/Modules/PSDesiredStateConfiguration/2.0.6/helpers/DscResourceInfo.psm1' was not
loaded because no valid module file was found in any module directory.

Environment data
PSVersionTable:

Name                           Value
----                           -----
PSVersion                      7.3.3
PSEdition                      Core
GitCommitId                    7.3.3
OS                             Linux 6.1.12-gentoo-magentalane-2023.02.21 #5 SMP PREEMPT_DYNAMIC Mon Feb 20 23:50:…
Platform                       Unix
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

And the runtime:
.NET SDK:
 Version:   7.0.201
 Commit:    68f2d7e7a3

Środowisko uruchomieniowe:
 OS Name:     gentoo
 OS Version:  2.13
 OS Platform: Linux
 RID:         linux-x64
 Base Path:   /opt/dotnet-sdk-bin-7.0/sdk/7.0.201/

Host:
  Version:      7.0.3
  Architecture: x64
  Commit:       0a2bda10e8

.NET SDKs installed:
  7.0.201 [/opt/dotnet-sdk-bin-7.0/sdk]

.NET runtimes installed:
  Microsoft.AspNetCore.App 7.0.3 [/opt/dotnet-sdk-bin-7.0/shared/Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 7.0.3 [/opt/dotnet-sdk-bin-7.0/shared/Microsoft.NETCore.App]

The modules listed above are imported correctly if I link .NET SDK's Microsoft.NETCore.App to the ref dir ln -fs /opt/dotnet-sdk-bin-7.0/shared/Microsoft.NETCore.App/7.0.3 /usr/share/pwsh-7.3/ref


Bump Tenacity Version

:rocket:
This description was created by Ellipsis for commit e914a6a2d6cd90d111d3a4869f5e927c5f7aa2e5

Summary:
Updated tenacity version in pyproject.toml to ^8.4.1 for compatibility with latest features and fixes.
Key points:

Updated tenacity version in pyproject.toml from ^8.2.3 to ^8.4.1.
Ensures compatibility with the latest features and fixes in tenacity.

Generated with :heart: by ellipsis.dev

This resolves #766


Add C# compat members for 4.2 changes

Since we're entering feature freeze and it's unlikely we will break compatibility anymore before the release, I think it's now a good time to look at all the breaking changes we made from 4.1 to 4.2.
This PR adds back C# members that were removed and therefore no longer generated, in order to prevent breaking compatibility. Since we don't have a system to add compatibility properties or signals, these still have to be added manually to C#.
Not every breaking change can be avoided, I have compiled a list like I did for 4.1 so we can get started on the Upgrading from Godot 4.1 to Godot 4.2 article:

godot-4.2-break-compat.rst
The list assumes this PR will be merged.

Thanks!


HA configuration?

I realize that that gitea was probably not engineered for concurrent access by multiple frontends on different servers - however,

if I had a common database backend
and hosted the repos on a networked filesystem
and could guarantee that no two frontends would update the same repo at the same time
then do you think it would be feasible to have multiple gitea instances running concurrently without corrupting?

Currently, Gitea cannot guarantee that. It's safety on a single machine.

@lunny Ok, thanks for letting me know for certain


MWPW-159555 Add support for lana-sample query param

The lana-sample query param will override any sample rate defined elsewhere.  Setting it to "100" will force lana to send everything to splunk.
Resolves: MWPW-159555
Test URLs:

Before: https://main--milo--adobecom.hlx.page/?martech=off
After: https://mwpw-159555--milo--adobecom.hlx.page/?martech=off

Hi @chrischrischris can you provide some guidance on how testing should be performed for this change?
thank you

Seems the new unit test is failing - ❌ LANA > The lana-sample query param overrides existing sampleRate

@thedoc31 The parseInt handles the sanitization of the input.  If the lana-sample param is invalid it will be NaN and the next line will ignore it:
const sampleRateParam = parseInt(new URL(window.location).searchParams.get('lana-sample'), 10);
const sampleRate = sampleRateParam || (o.errorType === 'i' ? o.implicitSampleRate : o.sampleRate);

It's fine if the param is negative or a gigantic number.  Negative will behave like 0, anything over 100 behaves like 100.


"Buffer too small, skipping audio rendering"

https://github.com/agourlay/ruxguitar/blob/21de214cc7b22944e1545ad5d13272d3282d7467/src/audio/midi_player.rs#L308-L311
I added some logging statements, and found out that left.len() and right.len() are 2205, while channel_len is 4704 -- this is true for any .gp5 file (like the Demo v5.gp5) and any soundfont. I don't know much about MIDI rendering, so what are the typical values for each length? What information can I provide to better help debug this error?
I'm running on Arch Linux, with alsa-lib installed (which provides /usr/lib/libasound.so).
Thanks for undertaking this project, by the way; I've always wanted to have a go at writing a GP5 player but never found the time/motivation!

Thank you for the report and the kind words :+1:
Can you please try this branch https://github.com/agourlay/ruxguitar/pull/15 to investigate this issue.
I would like to know how it sounds and what is logged :)

@hejops ping just in case you missed the notification :)

My bad, I've been a bit swamped with other work lately; I'll look into this tomorrow!

Here are the logs from playing Demo v5.gp5:
$ cargo run -- --file test-files/Demo\ v5.gp5
[2024-09-19T05:17:59Z INFO  ruxguitar::audio::midi_player] Toggle audio stream
[2024-09-19T05:18:00Z WARN  ruxguitar::audio::midi_player] Audio output stream config: StreamConfig { channels: 2, sample_rate: SampleRate(44100), buffer_size: Default } (2 channels, 44100 Hz)
[2024-09-19T05:18:00Z INFO  ruxguitar::audio::midi_player] Buffer too small 2205<4704
[2024-09-19T05:18:54Z INFO  ruxguitar::audio::midi_player] Tempo changed to 120
[2024-09-19T05:19:02Z INFO  ruxguitar::audio::midi_player] Tempo changed to 165

(PS: See https://github.com/hejops/ruxguitar/commit/9b2d470f156114fc60810efaa8309db30d9327ec for how/why I added the --file cli argument)
Could the lack of output have something to do with alsa and/or pulseaudio? It seems that ruxguitar output is not being detected in pulseaudio; for example, playing audio in Firefox or mpv can typically be observed through pactl by using something like:
$ pactl list | grep module-stream-restore.id
                module-stream-restore.id = "sink-input-by-application-name:Firefox"
                module-stream-restore.id = "sink-input-by-application-name:mpv Media Player"

But playing a file in ruxguitar produces no output.
$ pactl list | grep ruxguitar

I haven't had to fiddle with alsa in a long time (or pulseaudio for that matter), so maybe I'm missing something obvious.

Thanks for sharing the logs :+1:
It seems the output stream is properly created so it is very weird that you have no sounds indeed.
FYI I am using Pipewire and Alsa and when running:
$ pactl list | grep ruxguitar

I get:
Client #721
        Driver: PipeWire
        Owner Module: 2
        Properties:
                pipewire.protocol = "protocol-native"
                pipewire.sec.socket = "pipewire-0"
                pipewire.sec.pid = "3436"
                pipewire.sec.uid = "1000"
                pipewire.sec.gid = "1000"
                pipewire.sec.label = "unconfined"
                module.id = "2"
                object.id = "79"
                object.serial = "721"
                client.api = "pipewire-pulse"
                pulse.server.type = "unix"
                application.name = "ALSA plug-in [ruxguitar]"
                application.process.id = "211737"
                application.process.user = "agourlay"
                application.process.host = "agourlay-thinkpad"
                application.process.binary = "ruxguitar"
                application.language = "C"
                window.x11.display = ":0.0"
                application.process.machine_id = "374a11792ee84724a58ed2202bbb6619"
                application.process.session_id = "c2"
                config.name = "pipewire-pulse.conf"
                cpu.max-align = "32"
                default.clock.rate = "48000"
                default.clock.quantum = "1024"
                default.clock.min-quantum = "32"
                default.clock.max-quantum = "2048"
                default.clock.quantum-limit = "8192"
                default.clock.quantum-floor = "4"
                default.video.width = "640"
                default.video.height = "480"
                default.video.rate.num = "25"
                default.video.rate.denom = "1"
                log.level = "2"
                clock.power-of-two-quantum = "true"
                link.max-buffers = "64"
                mem.warn-mlock = "false"
                mem.allow-mlock = "true"
                settings.check-quantum = "false"
                settings.check-rate = "false"
                core.version = "1.0.5"
                core.name = "pipewire-agourlay-3436"
                pipewire.access = "unrestricted"

However, looking at the docs for the cpal crate that I am using, it does not seem to mention supporting PulseAudio though.
Currently, supported hosts include:

    Linux (via ALSA or JACK)

See tracking issue https://github.com/RustAudio/cpal/issues/259
Is it possible for you to use Pipewire?

Thanks for investigating. On replacing pulseaudio with pipewire-pulse, cpal panics at device.default_output_config() because it cannot find any device:
[2024-09-20T04:35:41Z INFO  ruxguitar::audio::midi_player] Toggle audio stream
ALSA lib pcm_dmix.c:1000:(snd_pcm_dmix_open) unable to open slave
thread 'main' panicked at src/audio/midi_player.rs:213:49:
called `Result::unwrap()` on an `Err` value: DeviceNotAvailable
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

I've added submitted a PR to avoid panicking in such a situation, feel free to merge it if you think it looks good. :smiley:
I'll be sure to give it another try when I get some better speakers in the (hopefully) near future!

fixed in 0.3.1


Add recipes for fine-tuning models with Together AI

We already have recipes for fine-tuning models with OpenAI and Fireworks. See here.
We want similar recipes for other providers, including Together AI. We'll need two recipes: metrics and demonstrations. These can be two separate incremental PRs.

Per discussion in #391, @DebmalyaSen34 wants to tackle this issue.

@GabrielBianconi I want to solve this issue


Update symengine hash

updated SymEngine hash (to one with support for Piecewise in LambdaDoubleVisitor)
... added a test thereof
Added Piecewise to __init__.py, and a few others:

Contains, Interval, ccode

Updated tests to use imports from symengine.lib.symengine_wrapper less extensively.

I also added imports of:
And, Or, Not, Nand, Nor, Xor, Xnor
to __init__.py, not sure about those: do we want them "exported" by default?

Let's ignore sage failure for now


XmlFormatter.CommandLine.dll not signed

Just a suggestion. The Dll can be blocked by those that block unsigned Dlls. Whitelisting on file hash will work but if you update the dll a new hash would have to be generated.

Thanks for the info. I myself have not come across an issue where this is the case. I assume one would want to whitelist VSCode folder to be ignored by AntiVirus if that's what is blocking it. What would be a solution for this?

XmlFormatter.dll is also affected by this as well.  Yeah either the person would have to trust the directory that the dlls reside in. Though it looks like the folder name contains the version of the software so that would change per version. Or you can sign the dlls when you compile them. Though you may have to pay for that or see if you can self-sign the dlls. Though I'm not an expert on signing code for external user support.

Thank you 😄  I will check it out.

Though it looks like the folder name contains the version of the software so that would change per version.

By the way one can use wild-carded paths to be whilte-listed or the whole VS Code extensions folder.

It is not high priority. There are a lot of applications which require you to whitelist on anti-virus.
Its open source and free software. Assuming we have to pay for getting certificate signing it can be done if there is some sponsorship I will keep it in mind and implement it if feasible with low cost in coming months.

Closing as not planned now.


How we can get Backend Code

Sir,
Please give me documentation and backend code. how to host video

This repo is for the Android project and data is from a local data source which you can replace by your own backend API.  Currently, I am not thinking about developing a backend solution for it.


Added  Exercises API

Please don't open multiple PRs for same thing.
You can always add the details in the previous PR.


position of "annotated gene" on pub pages when multiple rows

here would it be better if cdc2 was next to the GO ID (row above)

for the  MF and process where cut3 is a target

The above example no longer exists becasue the extension is only on the MF term now.
Here is a better e.g:

maybe the simplest resolution here is just to remove all of the grey lines between  ontology terms?
Then, even though there is a slight display difference between things which form on a single row vs. multiple rows wrt where the gene ID is placed wrt to the term, it probably won't matter because it will be immediately much clearer which things belong together?
thoughts?

as this is term detail page
current thinking is   always GO ID and term,
with genes underneath.
The processes etc will be a bit longer, but it will look neater and it will remove a column

We'll keep this on the radar if all the critical stuff is done....

I'll close this, it isn't bothering me....


Fix migrate

Maybe it's me, but I can't make the flask-migrate work. When I try and use it, it comes up with a keyerror['migrate'].
I think it's because the Migrate object isn't initiated and then isn't registered. This PR does those two things.
I don't love the solution, because I'm importing the app into extensions and it seems inelegant but everything seems to work OK now.

Perfect! I really love this project, its been super helpful!

Fixed with 76d9c6d
Credit in commit :)


BlockAction payload not showing value as valid option

(Filling out the following with as much detail as you can provide will help us solve your issue sooner.)
Reproducible in:
(Paste the output of)
"slack/bolt": "^3.12.2",

Node.js runtime version
v16.17.0
OS info
ProductName:		macOS
ProductVersion:		13.2.1
BuildVersion:		        22D68
Darwin Kernel Version 22.3.0: Mon Jan 30 20:38:37 PST 2023; root:xnu-8792.81.3~2/RELEASE_ARM64_T6000
Steps to reproduce:
When having the bot listen for an accessory block action response, the TS is off about the response payload.

Create a message with this block (taken from slacks block builder)

{
	"blocks": [
		{
			"type": "header",
			"text": {
				"type": "plain_text",
				"text": "Here's what you can do with Project Tracker:"
			}
		},
		{
			"type": "context",
			"elements": [
				{
					"type": "image",
					"image_url": "https://api.slack.com/img/blocks/bkb_template_images/placeholder.png",
					"alt_text": "placeholder"
				}
			]
		},
		{
			"type": "section",
			"text": {
				"type": "mrkdwn",
				"text": "This is a section block with a button."
			},
			"accessory": {
				"type": "button",
				"text": {
					"type": "plain_text",
					"text": "Click Me",
					"emoji": true
				},
				"value": "click_me_123",
				"action_id": "button-action"
			}
		}
	]
}

Click the accessory button on the bot's message.
Try to parse the result

app.action(
  "button-action",
  async ({ body, ack, say, payload, action }) => {
    // Acknowledge the action
    const value = payload.value;
    // OR
    const value = body.actions[0].value // <-- to get this you have to set the type to "block_actions"
    await ack();
    await say(
<EMAIL_ADDRESS>clicked the button to release ${value}`
    );
  }
);

Expected result:
able to get the value prop off of payload.value or body.actions[0].value
Actual result:

Payload from Slack Block builder

When I've logger.info("payload", payload) in the app.
Ignore the differnce in values, this was my personal values.

Requirements
For general questions/issues about Slack API platform or its server-side, could you submit questions at https://my.slack.com/help/requests/new instead. :bow:
Please read the Contributing guidelines and Code of Conduct before creating this issue or pull request. By submitting, you are agreeing to those rules.

Hi, @CoryWritesCode! Thanks for submitting this issue.
I was able to reproduce this error message you received by adding a TypeScript type checker on top of an existing Bolt JS app. However, prior to adding the type checker, the code was running smoothly and I was able to access the button value with no issue.
I believe this error is being thrown because the payload param expected could be a type of: DialogSubmitAction | WorkflowStepEdit | BlockElementAction | InteractiveAction, which feels like expected behavior in the actions handler since payload could correspond to an action of any of those types.
In terms of workaround - if you need to continue using the type checker, you could add some sort of ignore statement for that line (ex:  // @ts-ignore). However, if you're building in JS, unless you absolutely need it, I recommend potentially getting rid of that type checker since it may create some unintended side effects such as that error message. I hope this helps and let me know if there are any further questions!


Fix list item dash/plus tokens

Previously strings such your-great-feature or
your+great+feature would have been detected
as list items.

hi,
i m not 100% clear about how tokenizer works; but i can pass the test and fix issues with inlined dashed/plused content (if i can say).
Hope that works on your end too!


operator vfunction-server-operator (v2.3.594)

New operator bundle
Name: vfunction-server-operator
Version: v2.3.594
Certification project: 5f64dc1e0a4d06443d2818ad
Test result URL: https://catalog.redhat.com/api/containers/v1/projects/certification/test-results/id/61917043d115ef379a598e5e
Test logs URL: https://catalog.redhat.com/api/containers/v1/projects/certification/artifacts/id/61917042d6b39d004292bad1

Hi,
I'm sure 100% that my ci tests passed okay (even 3 times...) on my local OpenShift cluster with the most updated operator-ci-pipeline.yml and tasks from the operator-pipelines repo.
I did have some issues with timeout exceeding on both ScorecardBasicSpecCheck & ScorecardOlmSuiteCheck before I updated. (I couldn't access the test result URL nor the logs URL from above to see the exact errors for this run - to be sure they are the same, though)
Before starting the long journey of opening a support case for this, I just wanted to make sure that the errors are not on your end because the tests cluster is not updated correctly? Could you please verify that tests can pass at all now for ScorecardBasicSpecCheck & ScorecardOlmSuiteCheck on your testing cluster?
Thanks.

Now I could also see in the logs that both ScorecardBasicSpecCheck and ScorecardOlmSuiteCheck failed on the 30 seconds timeout (as I expected and mentioned in my previous comment).
As I also mentioned - I had this error too until I pulled a new version from operator-pipelines and applied all pipelines and tasks on the OpenShift cluster.
From the last Perflight.log:
time="2021-11-15T13:58:35Z" level=info msg="running check: ScorecardBasicSpecCheck"
time="2021-11-15T13:58:35Z" level=debug msg="Running operator-sdk scorecard check for quay.io/operator-pipeline-prod/vfunction-server-operator:v2.3.594"
time="2021-11-15T13:58:35Z" level=debug msg="--selector=[test=basic-check-spec-test]"
time="2021-11-15T13:58:35Z" level=trace msg="running scorecard with the following invocation[operator-sdk scorecard --output json --selector=test=basic-check-spec-test --kubeconfig /tmp/kubeconfig-3421170286 --namespace default --service-account default --config /tmp/scorecard-test-config-3472466720.yaml --verbose /tmp/preflight-3179944778/fs]"
time="2021-11-15T13:59:05Z" level=error msg="stdout: "
time="2021-11-15T13:59:05Z" level=error msg="stderr: time="2021-11-15T13:58:35Z" level=debug msg="Debug logging is set"\nError: error running tests context deadline exceeded\nUsage:\n  operator-sdk scorecard [flags]\n\nFlags:\n  -c, --config string            path to scorecard config file\n  -h, --help                     help for scorecard\n      --kubeconfig string        kubeconfig path\n  -L, --list                     Option to enable listing which tests are run\n  -n, --namespace string         namespace to run the test images in\n  -o, --output string            Output format for results. Valid values: text, json, xunit (default "text")\n  -l, --selector string          label selector to determine which tests are run\n  -s, --service-account string   Service account to use for tests (default "default")\n  -x, --skip-cleanup             Disable resource cleanup after tests are run\n  -b, --storage-image string     Storage image to be used by the Scorecard pod (default "docker.io/library/busybox@sha256:c71cb4f7e8ececaffb34037c2637dc86820e4185100e18b4d02d613a9bd772af")\n  -t, --test-output string       Test output directory. (default "test-output")\n  -u, --untar-image string       Untar image to be used by the Scorecard pod (default "registry.access.redhat.com/ubi8@sha256:910f6bc0b5ae9b555eb91b88d28d568099b060088616eba2867b07ab6ea457c7")\n  -w, --wait-time duration       seconds to wait for tests to complete. Example: 35s (default 30s)\n\nGlobal Flags:\n      --plugins strings   plugin keys to be used for this subcommand execution\n      --verbose           Enable verbose logging\n\ntime="2021-11-15T13:59:05Z" level=fatal msg="error running tests context deadline exceeded"\n"
time="2021-11-15T13:59:05Z" level=info msg="check completed: ScorecardBasicSpecCheck" ERROR="failed to run operator-sdk scorecard: exit status 1" result="failed to run operator-sdk scorecard: exit status 1"
time="2021-11-15T13:59:05Z" level=info msg="running check: ScorecardOlmSuiteCheck"
time="2021-11-15T13:59:05Z" level=debug msg="Running operator-sdk scorecard Check for quay.io/operator-pipeline-prod/vfunction-server-operator:v2.3.594"
time="2021-11-15T13:59:05Z" level=debug msg="--selector=[suite=olm]"
time="2021-11-15T13:59:05Z" level=trace msg="running scorecard with the following invocation[operator-sdk scorecard --output json --selector=suite=olm --kubeconfig /tmp/kubeconfig-3421170286 --namespace default --service-account default --config /tmp/scorecard-test-config-2813129432.yaml --verbose /tmp/preflight-3179944778/fs]"
time="2021-11-15T13:59:36Z" level=error msg="stdout: "
time="2021-11-15T13:59:36Z" level=error msg="stderr: time="2021-11-15T13:59:05Z" level=debug msg="Debug logging is set"\nError: error running tests context deadline exceeded\nUsage:\n  operator-sdk scorecard [flags]\n\nFlags:\n  -c, --config string            path to scorecard config file\n  -h, --help                     help for scorecard\n      --kubeconfig string        kubeconfig path\n  -L, --list                     Option to enable listing which tests are run\n  -n, --namespace string         namespace to run the test images in\n  -o, --output string            Output format for results. Valid values: text, json, xunit (default "text")\n  -l, --selector string          label selector to determine which tests are run\n  -s, --service-account string   Service account to use for tests (default "default")\n  -x, --skip-cleanup             Disable resource cleanup after tests are run\n  -b, --storage-image string     Storage image to be used by the Scorecard pod (default "docker.io/library/busybox@sha256:c71cb4f7e8ececaffb34037c2637dc86820e4185100e18b4d02d613a9bd772af")\n  -t, --test-output string       Test output directory. (default "test-output")\n  -u, --untar-image string       Untar image to be used by the Scorecard pod (default "registry.access.redhat.com/ubi8@sha256:910f6bc0b5ae9b555eb91b88d28d568099b060088616eba2867b07ab6ea457c7")\n  -w, --wait-time duration       seconds to wait for tests to complete. Example: 35s (default 30s)\n\nGlobal Flags:\n      --plugins strings   plugin keys to be used for this subcommand execution\n      --verbose           Enable verbose logging\n\ntime="2021-11-15T13:59:36Z" level=fatal msg="error running tests context deadline exceeded"\n"
time="2021-11-15T13:59:36Z" level=info msg="check completed: ScorecardOlmSuiteCheck" ERROR="failed to run operator-sdk scorecard: exit status 1" result="failed to run operator-sdk scorecard: exit status 1"

Thank you.  We are looking into this on our side.

Hi,
Any news regarding this?
Thanks.


flaky tests

Summary:
some tests of the matrix exponential seem to fail under random circumstances.
Description:
The tests
test/unit/math/rev/mat/fun/matrix_exp_pade_test.cpp:139
test/unit/math/rev/mat/fun/matrix_exp_test.cpp

fail once in a while with very small tolerance violations.
Reproducible Steps:
Very hard. It happens sometimes on Jenkins.
Current Output:
Not well defined.
Expected Output:
The tests should be deterministic-ally ok if nothing changed.
Additional Information:
Provide any additional information here.
Current Version:
develop

fixed with #901


Scan all StartMenuInternet registry entries

It's been suggested before, and now, this would also help address #22.
Before doing the regular search, get all StartMenuInternet registry entries, and inspect their names. For each, normalize the name (like "Google Chrome Canary" or "Firefox Developer Edition") to a name and channel.
Usually (if installed with defaults) this is enough to detect multiple versions of a browser and differentiate channels.
Tasks:

[ ] When #26 is done, add an option to registry stream to recurse
[ ] Back here, use this new ability to read StartMenuInternet

Found different avenues for channel differentiation. And performance-wise, there is no benefit anymore, maybe even a cost.


Add Errorf function

Hi there, it would be handy to have an Errorf function to make it easy to parameterize errors, alternatively we could have NewError and InternalError take args ...interface{} and then pass that to Sprintf in the function.
If you're open to this I can make a PR.

Thanks for the suggestion. That helper would be handy.
However, the errors package tries to be minimal by design. This ensures simplicity and performance.
Projects are encouraged to build their own error utils with their own constructors and wrappers. For example:
package errorutil

func TwirpErrorf(code twirp.ErrorCode, format string, a ...interface{}) {
    return twirp.NewError(code, fmt.Sprintf(format, a...))
}


'simple_library.nt' not present in the examples directory for it to be accessed by 'getting_started.ipynb' file

While running the file 'getting_started.ipynb' which is present in the 'examples' folder, I encountered an error while executing the 3rd cell:
doc.read('simple_library.nt')

It turns out the file 'simple_library.nt' is not present in the 'examples' folder. The file 'simple_library.nt' is present in '/test/resources' folder. There are two simples fix to this issue:
(i) Add the file 'simple_library.nt' file to the examples folder. OR
(ii) Changing the third cell from
doc.read('simple_library.nt')

to
doc.read(os.path.join('..', 'test', 'resources', 'simple_library.nt'))

The os library is already imported in the first cell of the python notebook.
I can create a pull request with either of the solutions @jakebeal. Thank You.

I like the second option better. It would better yet if it used pathlib.Path rather than os.path.join, which can look something like: doc.read(Path.cwd().parent / 'test' / 'resources' / 'simple_library.nt')

Understood, thanks a lot.

I'm terribly sorry it has taken so long to merge this PR. Thanks for submitting!


fixed the defencing of the rbd lock

Locking was working fine for me. The cleanup code however was throwing an exception when attempting to remove the lock. The code reads in a json file left in the /rbd.json folder and then attempts to decode this into a rbdCleaner{*rbd} which doesn't support the field and later throws a 'divide by zero exception' due to size being zero (i.e. nothing as been reread)  ...a typo perhaps on the struct? ... Either way, changing the rbdCleaner to a rbdBuilder allows use to decode the file and successfully release the lock.
https://github.com/GoogleCloudPlatform/kubernetes/issues/12481

cc @rootfs @markturansky

@k8s-bot ok to test

@gambol99 thanks!

As a side note, looks like the original PR (https://github.com/GoogleCloudPlatform/kubernetes/pull/10563) added the fields into the rbd{} ... but was later removed in (https://github.com/GoogleCloudPlatform/kubernetes/commit/72e899e1b585d7f43eef17feb2dfdaa648dd9843) ...

@gambol99 right, a rbd e2e should catch this problem.


Add Translate From English support

Describe your suggested feature
Now only have cn jp kr latin
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] I have updated the app to version 0.17.0.
[X] I will fill out all of the requested information in this form.

I join this request, it is easier to find extensions in English than from one with raw

I support this petition, there should be an option to translate from English to another language


rizin: add patch to build with tree-sitter 0.20.9

Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Hi, just to let you know, Rizin 0.7.1 version was released with many quality of life changes, along with corresponding Cutter 2.3.4 release:

https://github.com/rizinorg/rizin/releases/tag/v0.7.1
https://github.com/rizinorg/rizin/releases/tag/v0.7.0
https://github.com/rizinorg/cutter/releases/tag/v2.3.4
https://github.com/rizinorg/cutter/releases/tag/v2.3.3

The bump is here: https://github.com/NixOS/nixpkgs/pull/293264


Please add a charm action to run the upload_assets console command

Enhancement Proposal
Hi
It's possible for a charmed deploy using S3 integration to enter a state where the generated HTML references S3-hosted files that don't exist - see #208.
Currently the least painful workaround is to get a discourse console session on a pod, and run bundle exec rails s3:upload_assets.
This enhancement proposal is a request for a charm action to perform the above, and ideally to confirm a successful upload.

@javierdelapuente Please have a look and create a ticket in the backlog if necessary.

Closing, @barryprice , please comment if this is still necessary.


double-beep: Blacklist biogenics\W*keto

double-beep requests the blacklist of the keyword biogenics\W*keto. See the MS search here and the Stack Exchange search here.

biogenics\W*keto has been seen in 18 true positives, 0 false positives, and 0 NAAs.

Approved by tripleee in Charcoal HQ


Refactor another ~100 package from python-packages.nix -> python-modules

Things done
All have been tested to build and is ready for merge
Strictly moving package to python-modules. Did not attempt to upgrade package unless it added python 3 support or was broken. Also converted fetch... to fetchPypi to make future upgrades easier. All packages have been tested in sandbox mode to build properly.
As of the last edit there are ~332 remaining packages to move.
grep "buildPythonPackage" python-packages.nix | wc
    332    1706   13716

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

[X] NixOS
[ ] macOS
[ ] other Linux distributions

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

Sorry, I broke this by splitting slixmpp in #48545

e08ab90  should be squashed

@lheckemann no worries I will rebase it. I appreciate you letting me know. @FRidh my git fu is not quite good enough and I was being lazy when I made those commits. I will learn how to properly split that commit and merge into the appropriate commit.

@FRidh I have learned just how powerful rebasing can be. I have removed all (2) of the commits that "patched" typos I made in the previous commit. Thanks for the feedback and ready to merge.

Good job.

25 more packges -> python-modules. All tested.

@costrouc Thank you for this work! @FRidh is encouraging me to start updating Python packages semi-automatically with r-ryantm/nixpkgs-update and it cannot update the packages in python-modules.nix (because it won't update things in a file with multiple fetchers), so this work you are doing should help keep Python packages more up to date!

 I was aware of your bot and someone told me that it could only work with fetchPypi and being in python-modules. To me it seems like automation is an important step in the growth of nix. Otherwise small package updates will consume too much of our time. I have a bit more free time for the next month and my goal is to really cleanup the python packages in nix.

The good news is that soon (next few years) python projects will start declaring their dependencies in a static file pyproject.toml. This will make life much easier for updating packages.

pyproject.toml will probably still need some time to establish. At the moment I don't see how c-extension can be packed this way.

As far as I know, nixpkgs-update doesn't need the derivation to use fetchPypi. In fact, here is one using fetchFromGitHub: https://github.com/NixOS/nixpkgs/pull/49037/files

@ryantm what fetch... does it work with? In some cases packages released through pypi do not contain tests which make upgrades more dangerous (not knowing if something breaks). Makes me want to favor fetchFromGitHub, fetchFromGitLab, etc. What are your thoughts?

@costrouc As long as the fetcher is written in some way that it gets modified by changing the version string somewhere in the file, and the hash for it is somewhere in the file, and nix-prefetch-url works,  it should work. So, all the main fetchers work, but sometimes expressions are formatted in a way that doesn't works, for example, the rev might not be based on the version, or fetchgit is using the commit sha.
As for what to do for python things, I want to defer to @FRidh. I'm not familiar with the Python ecosystem.

pyproject.toml will probably still need some time to establish. At the moment I don't see how c-extension can be build using this.

pyproject.toml will specify that setuptools will be used as build system, and from there on everything is the same as it is now. It's a step in the right direction, giving access to dependencies in a easier way. However, we still have to do the hardest part: dependency resolution across the whole package set.


Support new wallet permissions

Wallet authentication is changing with the v2 api of the wallet. We need to support this.
Possible split:

[ ] desktop wallet work to show dialogs (key to expose etc..)
[ ] 3rd party trading app changes for authentication with the wallet

Note: review the connect-vega-wallet labeled issues before starting this work

https://www.figma.com/file/W8SV56AAtXpRoQJDQW9ZYt/Vega-Wallet?node-id=1640%3A93621

Consider closing this issue and brining in issues with connect-vega-wallet labeled items as these are the same


use dynamic trampoline for all getters and setters

This is an extension to the "trampoline" changes made in #2705 to re-use a single trampoline for all #[getter]s (and similar for all #[setters]). It works by setting the currently-unused closure member of the ffi::PyGetSetDef structure to point at a new struct GetSetDefClosure which contains function pointers to the getter / setter implementations.
A universal trampoline for all getter, for example, then works by reading the actual getter implementation out of the GetSetDefClosure.
Advantages of doing this:

Very minimal simplification to the macro code / generated code size. It made a 4.4% reduction to test_getter_setter generated size, which is an exaggerated result as most code will probably have lots of bulk that isn't just the macro code.

Disadvantages:

Additional level of complexity in the getter and setter trampolines and accompanying code.
To keep the GetSetDefClosure objects alive, I've added them to the static LazyTypeObject inner.
Very slight performance overhead at runtime (shouldn't be more than an additional pointer read). It's so slight I couldn't measure it.

Overall I'm happy to either merge or close this based on what reviewers think!

Ok, I've pushed a commit which removes the use of unreachable_unchecked. It does this by moving the logic constructing the getters & setters into a builder / enum in create_type_object.rs, and picking an appropriate trampoline / closure pair inside match arms.
I've added some TODO where we could add some validation that only one #[getter] per property etc, which can be a future PR.

To keep the GetSetDefClosure objects alive, I've added them to the static LazyTypeObject inner.

I think this is no longer a disadvantage, as I've added the "name" and "doc" members to this too, which addresses an older TODO to avoid naively leaking those things.

bors r+


Transform Plugins with enforce: 'pre' break stack traces

Describe the bug
I am developing Vite plugin that performs some transformations on the source files of our tests. Since introducing this plugin, I have noticed that stack traces for errors in our tests no longer work as expected.
Working with some publicly-available packages and messing with their configuration, I was able to determine the source of the error: it seems like plugins that transform file contents that run with enforce: 'pre' will break the stack traces of errors in the tests.
In the attached reproduction project, I have added the official @rollup/plugin-strip since it works very similar to my own plugin under-the-hood (and can show the same problem).
If I apply that plugin normally -- where enforce is not set at all -- and cause an error in my tests, I see exactly where the exception took place.

If I explicitly set enforce: 'pre' on the plugin and run the tests again, however, the pointer to exactly where the error happened disappears. In this case, there's no pointer at all, but in longer files it sometimes shows a pointer to the incorrect location instead. I think it has to do with some kind of source-map offset being applied that, in this case with a small test, ends up outside the bounds of the file altogether, resulting in no pointer at all

Reproduction
https://stackblitz.com/edit/vitest-dev-vitest-7jynzx?file=vite.config.ts
In the vite.config.ts the enforce: 'pre' configuration can be commented out to demonstrate the affect of the issue; without it, the exception shows the correct pointer to the error. With the line present, though, that pointer breaks.
System Info
  System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 16.14.2 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 7.17.0 - /usr/local/bin/npm
  npmPackages:
    @vitest/ui: latest => 0.29.2
    vite: latest => 4.1.4
    vitest: latest => 0.29.2

Used Package Manager
npm
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Plugins are responsible for providing correct source maps.


$this->getModelIndex() returns null

When running php artisan mapping:run the $this->getModelIndex() returns null. Should by default it return the index specified within the config?
Tracing it back to the model, within the Searchable trait there is no default value returned if not available. Can you not just return config('plastic.index')?
/**
     * Get the model elastic index if available.
     *
     * @return mixed
     */
    public function getDocumentIndex()
    {
        // if a custom index is defined use it else return null
        if (isset($this->documentIndex) and !empty($this->documentIndex)) {
            return $this->documentIndex;
        }

        return config('plastic.index');
    }

After digging deeper, I am closing because the mapping migrations assume that the indexes have already been created and setup. Therefore, the getModelIndex should return null as is, not to have any unintended consequences.


Add Bogoliubov transform

Summary
Adds a circuit to perform the Bogoliubov transform.
Details and comments
Uses the Givens rotation strategy to implement a general single-particle basis-change, which can either conserve particle number or not. The circuits are similar to the ones used to prepare Slater determinants and fermionic Gaussian states, but those ones are optimized for state preparation from a computational basis state, while the Bogoliubov transform performs the general unitary transformation.
References:
arXiv:1711.05395
arXiv:1603.08788

Test failures seem unrelated.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

177 of 186 (95.16%)  changed or added relevant lines in 9 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.1%) to 84.858%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

qiskit_nature/circuit/library/primitives/bogoliubov_transform.py
88
90
97.78%

qiskit_nature/utils/linalg.py
63
70
90.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.1%

Covered Lines:
9622

Relevant Lines:
11339

💛  - Coveralls

As this adds a new feature, as well as introduces utils  with functions we are making public, this needs a release note too.

The test failure is due to https://github.com/Qiskit/qiskit-nature/issues/686. It can be worked around by manually editing the notebook file but that quickly becomes tedious.

#686 has been closed without being addressed. There's no point in my fixing the notebook kernel until it has been finalized. So I need you to first approve this PR, and then I will fix the notebook, and then it can be merged.

@mrossinek @woodsp-ibm I've addressed all your comments. Is there anything else? Again, I can fix the notebook-related CI failure once this PR is approved.

It seems fine to me. As far as I can see all that I was discussing with you has been resolved now. The only last observation I might have is for the release note where it says

See the "Quadratic Hamiltonians and Slater determinants" tutorial for a demonstration of how to use this class

where it might be a nice improvement for the reader were that to be a link to the tutorial itself, E.g this is one there now https://qiskit.org/documentation/nature/tutorials/10_lattice_models.html that you can base the link on. Since release_notes is in nature folder you may be able to do a relative url i.e. tutorials/11_quadratic_....minants.html which could be seen to work in the docs built here ahead of them being published.

@woodsp-ibm I've added think. Could you approve the PR now?

The link should reference the .html file that is the result of the docs creation, and what is published out there on qiskit.org, not the original notebook itself (FYI: Each html is built out with a reference back to the notebook in github here so users can go get that if they want)

@woodsp-ibm I tested that the link works in the locally built docs, so sphinx must be handling it nicely.


Slicer crashes unexpectedly on BoneReconstructionPlanner

During the workflow, some times (around 70% of the times for me) when you press any of these buttons:

"Create cylinders from fiducial list and fibula surgical guide base"
"Create cylinders from fiducial list and mandible surgical guide base"

And less frequently (20% of the times for me) when you press any of these buttons:

"Create miter boxes from fibula planes"
"Create saw boxes from first and last mandible planes"

Slicer will unavoidably crash and close without warning.
This buggy behavior is difficult to fix because right now we have no way of reliably reproducing it.
If you as a user find a series of steps to make it happen 100% of times we can solve it surely: Please comment here how to do it (or paste the link to a saved state that lets you crash Slicer easily)
Thanks for using BRP

Solved


proxychains-ng: init at 4.15

Motivation for this change
Add proxychains-ng which is more maintained than proxychains.
Ref to #67688, which is stale.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all packages 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/)
21.11 Release Notes (or backporting 21.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 137541 run on x86_64-linux 1

1 package built:

proxychains-ng

@ofborg eval


docs(storage-resize-images): clear paths examples

fixes: #1245

closing in favour of https://github.com/firebase/extensions/pull/1373


this happens...

karlkras:~/workspace $ sudo pecl install xdebug
Warning: Invalid argument supplied for foreach() in Command.php on line 249
Warning: Invalid argument supplied for foreach() in /usr/share/php/PEAR/Command.php on line 249
Warning: Invalid argument supplied for foreach() in Command.php on line 249
Warning: Invalid argument supplied for foreach() in /usr/share/php/PEAR/Command.php on line 249
Warning: Invalid argument supplied for foreach() in Command.php on line 249
Warning: Invalid argument supplied for foreach() in /usr/share/php/PEAR/Command.php on line 249
Warning: Invalid argument supplied for foreach() in Command.php on line 249
Warning: Invalid argument supplied for foreach() in /usr/share/php/PEAR/Command.php on line 249
Warning: Invalid argument supplied for foreach() in Command.php on line 249
Warning: Invalid argument supplied for foreach() in /usr/share/php/PEAR/Command.php on line 249
Warning: Invalid argument supplied for foreach() in Command.php on line 249
Warning: Invalid argument supplied for foreach() in /usr/share/php/PEAR/Command.php on line 249
Warning: Invalid argument supplied for foreach() in Command.php on line 249
Warning: Invalid argument supplied for foreach() in /usr/share/php/PEAR/Command.php on line 249
Warning: Invalid argument supplied for foreach() in Command.php on line 249
Warning: Invalid argument supplied for foreach() in /usr/share/php/PEAR/Command.php on line 249
Warning: Invalid argument supplied for foreach() in Command.php on line 249
Warning: Invalid argument supplied for foreach() in /usr/share/php/PEAR/Command.php on line 249
Warning: Invalid argument supplied for foreach() in Command.php on line 249
Warning: Invalid argument supplied for foreach() in /usr/share/php/PEAR/Command.php on line 249
Warning: Invalid argument supplied for foreach() in Command.php on line 249
Warning: Invalid argument supplied for foreach() in /usr/share/php/PEAR/Command.php on line 249
Notice: Undefined index: honorsbaseinstall in Role.php on line 173
Notice: Undefined index: honorsbaseinstall in Role.php on line 173
Notice: Undefined index: honorsbaseinstall in Role.php on line 173
Notice: Undefined index: honorsbaseinstall in Role.php on line 173
Notice: Undefined index: honorsbaseinstall in Role.php on line 173
Notice: Undefined index: honorsbaseinstall in Role.php on line 173
Notice: Undefined index: honorsbaseinstall in Role.php on line 173
Notice: Undefined index: honorsbaseinstall in Role.php on line 173
Notice: Undefined index: honorsbaseinstall in Role.php on line 173
Notice: Undefined index: honorsbaseinstall in Role.php on line 173
Notice: Undefined index: installable in Role.php on line 139
Notice: Undefined index: installable in Role.php on line 139
Notice: Undefined index: installable in Role.php on line 139
Notice: Undefined index: installable in Role.php on line 139
Notice: Undefined index: installable in Role.php on line 139
Notice: Undefined index: installable in Role.php on line 139
Notice: Undefined index: installable in Role.php on line 139
Notice: Undefined index: installable in Role.php on line 139
Notice: Undefined index: installable in Role.php on line 139
Notice: Undefined index: installable in Role.php on line 139
Notice: Undefined index: phpfile in Role.php on line 204
Notice: Undefined index: phpfile in Role.php on line 204
Notice: Undefined index: phpfile in Role.php on line 204
Notice: Undefined index: phpfile in Role.php on line 204
Notice: Undefined index: phpfile in Role.php on line 204
Notice: Undefined index: phpfile in Role.php on line 204
Notice: Undefined index: phpfile in Role.php on line 204
Notice: Undefined index: phpfile in Role.php on line 204
Notice: Undefined index: phpfile in Role.php on line 204
Notice: Undefined index: phpfile in Role.php on line 204
Notice: Undefined index: config_vars in Role.php on line 46
Notice: Undefined index: config_vars in Role.php on line 46
Notice: Undefined index: config_vars in Role.php on line 46
Notice: Undefined index: config_vars in Role.php on line 46
Notice: Undefined index: config_vars in Role.php on line 46
Notice: Undefined index: config_vars in Role.php on line 46
Notice: Undefined index: config_vars in Role.php on line 46
Notice: Undefined index: config_vars in Role.php on line 46
Notice: Undefined index: config_vars in Role.php on line 46
Notice: Undefined index: config_vars in Role.php on line 46
Warning: Invalid argument supplied for foreach() in PEAR/Command.php on line 249
Warning: Invalid argument supplied for foreach() in /usr/share/php/PEAR/Command.php on line 249
Warning: Invalid argument supplied for foreach() in PEAR/Command.php on line 249
Warning: Invalid argument supplied for foreach() in /usr/share/php/PEAR/Command.php on line 249
Warning: Invalid argument supplied for foreach() in PEAR/Command.php on line 249
Warning: Invalid argument supplied for foreach() in /usr/share/php/PEAR/Command.php on line 249
Warning: Invalid argument supplied for foreach() in PEAR/Command.php on line 249
Warning: Invalid argument supplied for foreach() in /usr/share/php/PEAR/Command.php on line 249
Warning: Invalid argument supplied for foreach() in PEAR/Command.php on line 249
Warning: Invalid argument supplied for foreach() in /usr/share/php/PEAR/Command.php on line 249
Warning: Invalid argument supplied for foreach() in PEAR/Command.php on line 249
Warning: Invalid argument supplied for foreach() in /usr/share/php/PEAR/Command.php on line 249
Warning: Invalid argument supplied for foreach() in PEAR/Command.php on line 249
Warning: Invalid argument supplied for foreach() in /usr/share/php/PEAR/Command.php on line 249
Warning: Invalid argument supplied for foreach() in PEAR/Command.php on line 249
Warning: Invalid argument supplied for foreach() in /usr/share/php/PEAR/Command.php on line 249
Warning: Invalid argument supplied for foreach() in PEAR/Command.php on line 249
Warning: Invalid argument supplied for foreach() in /usr/share/php/PEAR/Command.php on line 249
Warning: Invalid argument supplied for foreach() in PEAR/Command.php on line 249
Warning: Invalid argument supplied for foreach() in /usr/share/php/PEAR/Command.php on line 249
Warning: Invalid argument supplied for foreach() in PEAR/Command.php on line 249
Warning: Invalid argument supplied for foreach() in /usr/share/php/PEAR/Command.php on line 249
XML Extension not found
karlkras:~/workspace $

You can try this:  sudo apt-get install php-xdebug


Domain range includes. Fixes #389

Addressing issue #389

Closed by mistake: meant to merge and close.

We concluded in the gist issue review meeting that addition of annotations is a minor change because it is an addition. Created new issue #488 to document this.


Update Dropdown for custom items and improved trigger setup

Description
This PR makes the following additions to Dropdown in Rails:

Adds a SageDropdownTrigger component

This sustains existing functionality with no regressions but buttresses what is possible for select types
Deprecation effort can begin to tidy up uses of the trigger_type: "select" and instead to use the new trigger: { type: "select", label: "...", value: "" } syntax and thus further reduce manual sage classes and tighten reliability.
Deprecation effort can begin to update existing dropdowns and place the existing triggers that are directly inside content slots to instead be mapped specifically to the sage_dropdown_trigger content slot.
Follow up will switch the component.content to instead contain panel content rather than needing the sage_dropdown_custom_panel slot.

Adds a SageDropdownItem component

This preserves all existing functionality while strengthening the internal composition of Dropdown to use this component.
This also now allows for safer construction of custom dropdown items by using a manual loop through an array of items to format content inside the content of SageDropdownItem.
A new sage_dropdown_items slot is also added to make this affordance easy to use.

@monkeypox8 Thanks! Hopefully this is also set up for a refactor/deprecation of the following:

Trigger for select variant: now built in so places this is manually added can be updated.
Trigger otherwise now can be placed in a new slot sage_drodpdown_trigger as a first step. After all dropdowns are adjusted to use this slot we can then look into using the default component.content to provide panel contents if desired.
Cases where custom element content is sent through the items' value property can be refactored to use the new templating approach with sage_dropdown_items slot and a loop of SageDropdownItems.

@philschanely are you able to add the react version of the new components props or is that out of scope for this task?

@QuintonJason React affordance added and ready for review :)


Bump playwright version

We should bump our playwright version soon to get the latest changes

As a note for post-FF testing: we must test this with the service after we release it to make sure everything is working fine on the deployed cloud env.


Dragging a plugin block near a blank text block may delete the plugin

Hi there,
We've come across the following bug when we try and set the layout of an Ory Editor when we try and drag a plugin block against a blank Text block occasionally the black guideline will not appear and releasing the mouse will delete the dragged block. This does not occur when the Text Block has content in it.
Here's a gif of it happening:

Hm, that is very strange

Which browser is this? I tried reproducing it on FF and chrome at http://editor.ory.am with no luck.

This happened on Chrome v61.0.3163.100 on OSX, I've been able to replicate it after messing around with it for a little it takes some time but once it happens in the session it can be replicated reliably.

Do you have redux devtools installed? If not, please install them and try to connect to the store. It would help to see what actions are triggered.
Also, is there some console output? Maybe this is a dupe of #472

If you're unable to connect redux dev tools, try to add a listener to the redux store manually. This can be achieved with (new Editor()).store.subscribe() see here.

No console output but I'll take a look with the Redux dev tools today.

The CELL_INSERT_BELOW action fires however it appears that the plugin being dropped disappears from state.

Ok that's weird, can you show the payload of CELL_INSERT_BELOW? My guess is that we're trying to drop it over an ID that doesn't exist.


support setop in plan module

close #9

Codecov Report

Merging #10 (aa432d5) into main (7e46a87) will increase coverage by 0.01%.
The diff coverage is 90.00%.

:exclamation: Current head aa432d5 differs from pull request most recent head 982913c. Consider uploading reports for the commit 982913c to get more accurate results

@@            Coverage Diff             @@
##             main      #10      +/-   ##
==========================================
+ Coverage   89.48%   89.50%   +0.01%
==========================================
  Files          36       36
  Lines        6438     6469      +31
==========================================
+ Hits         5761     5790      +29
- Misses        677      679       +2

Impacted Files
Coverage Δ

xngin-plan/src/op.rs
75.60% <66.66%> (-0.05%)
:arrow_down:

xngin-plan/src/builder.rs
80.30% <96.42%> (+0.49%)
:arrow_up:

xngin-plan/src/builder/tests.rs
95.30% <100.00%> (+0.30%)
:arrow_up:

xngin-plan/src/explain.rs
85.41% <100.00%> (+0.15%)
: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 7e46a87...982913c. Read the comment docs.


[refactor] remove MetaVarMatcher

⭐ Suggestion
We don't need another concept of MetaVarMatcher in constraints, a rule is pretty good fit.
💻 Use Cases
rule:
  pattern: $A($B)
constraints:
  A:
    regex: get
    kind: method_call

fixed via beb6f50e936809071e6bacae2c854aefa8e46d11


OPCPublisher accessing raw.githubusercontent.com hardcoded, but should not

Describe the bug
The OPCPublisher module seems to have hardcoded the raw.githubusercontent.com FQDN. This means deploying the module as 3rd party module on an IoT device running Azure IoT Edge 1.4 runtime will result in an invocation of raw.githubusercontent.com. This in turn implies that firewalls need be whitelisted for this FQDN. This may not be an issue in a homenetwork, but it is a security issue corporate IT infrastructure. Selling IoT devices to other companies that run Azure IoT Edge and require raw.githubusercontent.com to be whitelisted is a thorn in a security practitioner's side. This is not only an effective security issue, but also a marketing-security issue. The only Azure IoT Edge module of our solution that does require that FQDN is the OPCPublisher.
Remark: This may not by everyone considered a "bug". Some may say this is a feature (improvement), some may say this is a security vulnerability (as it is security relevant in context of deployment and its implications on IT infrastructure). I fully understand, please move it then into the approriate category.
To Reproduce
Steps to reproduce the behavior:

Install Azure IoT Edge & Docker
Install/deploy OPCPublisher 2.9
Check the remote FQDN that have been accessed

Expected behavior
There is no access to raw.githubusercontent.com. There could be, for example. mcr.microsoft.com, this would be acceptable.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: Windows
Browser Edge
Version122.0.2365.92 (Official build) (64-bit)

Do you know what happens if it is not whitelisted? Can you provide the error that you see then? I am not aware of anything needing this access and the only area where I think it could be the case is e.g. a license file in a consumed nuget but even there I am not sure why and when that would be triggered.

All what we see is that once the OPCPublisher is being deployed, there will be some traffic to that FQDN. What exactly its doing, we dont know. In any case - even if no impact - it will raise eyebrows from security guys in corporate IT seing that its "probed". The impact we dont know exactly, we can try to test that for you and come back to you.

What command line options did you use? Also, what tool did you use to find the call out?  I have tried wireshark and fiddler and could not repro.


ISPN-13134 ArithmeticException: / by zero in ClusterPublisherManagerImpl

https://issues.redhat.com/browse/ISPN-13134

Retry if no remaining segment has an owner
(possible in a scattered cache)
Batch size per target (targetBatchSize) should be never be greater
than the requested batch size

Btw the changes are causing failures at https://github.com/infinispan/infinispan/blob/main/core/src/main/java/org/infinispan/reactive/publisher/impl/PublisherHandler.java#L585
Guessing the code was assuming the original batch sizing and needs to be tweaked somewhere :)

Btw the changes are causing failures at https://github.com/infinispan/infinispan/blob/main/core/src/main/java/org/infinispan/reactive/publisher/impl/PublisherHandler.java#L585

Oops, sorry I missed all those failures!

Guessing the code was assuming the original batch sizing and needs to be tweaked somewhere :)

I believe you are right, and this comment suggests an assumption of batchSize > 1
https://github.com/infinispan/infinispan/blob/7206596b4a0258d0b8f1a20d78259e7f270a81ec/core/src/main/java/org/infinispan/reactive/publisher/impl/PublisherHandler.java#L333
I'm not sure if the "so we will return batchSize + 1" part is correct, the comment on the futureResponse field says it could actually contain 2 entries:
https://github.com/infinispan/infinispan/blob/7206596b4a0258d0b8f1a20d78259e7f270a81ec/core/src/main/java/org/infinispan/reactive/publisher/impl/PublisherHandler.java#L203
I have tried to ignore the assert when batchSize == 0 (see 02bd086bf6), but it didn't work 100%: I'm getting a ClassCastException in testObjFlatMapIterator, because the publisher is using KeyPublisherState, but all the responses are PublisherResponse (instead of KeyPublisherResponse). I'm not sure why this has never happened before, it doesn't seem to be related to the batch size change at all.
I have also considered requiring that batchSize >= 2 and then ensuring that also targetBatchSize >= 2 to preserve the old assumptions, although like I said I'm not sure the ClassCastException I'm getting now is really new or only new to the test.
To go off-topic again (you must now be wondering if I actually want to get this merged!), have you considered putting the segment completion notifications inline with the values, as items of the publisher? The preloading complicates the logic here quite a bit, and it seems to be needed only in order to synchronize the items of the publisher with the segment completion notifications.

I found the problem: because I allowed merging with an incomplete response, mergeResponses() can be called again on the same responses.
KeyPublisherState.mergeResponses() assumes the inputs are KeyPublisherResponse, but returns a PublisherResponse, so the second call fails with a ClassCastException.
I made a mistake when I said "all the responses are PublisherResponse": KeyPublisherResponse.toString() says the wrong type, but the type of the 2nd publisher was correct.

I added another commit that just skips merging responses if the publisher is not yet complete, and it works fine.
I would have preferred to remove the merging altogether and simplify the code instead of adding more complexity, but I couldn't get it to work.

Integrated into main, thanks @danberindei !

To go off-topic again (you must now be wondering if I actually want to get this merged!), have you considered putting the segment completion notifications inline with the values, as items of the publisher? The preloading complicates the logic here quite a bit, and it seems to be needed only in order to synchronize the items of the publisher with the segment completion notifications.

I tried to do that before, however there was a problem with the boundary iirc. I wrote this a long time ago now so I don't recall tbh.


Error:Get available generators script executes with errors:

Hello
I have just installed Rials 5 with ruby 2.3. I have added this gem like this:
gem 'rails_admin', github: 'sferik/rails_admin
When I run bundle install command, I get that kind of error:
Error:Get available generators script executes with errors:
Error:D:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/actionpack-   5.0.0/lib/action_dispatch/middleware/stack.rb:108:in `assert_index': No such middleware to insert after: ActionDispatch::ParamsParser (RuntimeError)
Error:	from D:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/actionpack-5.0.0/lib/action_dispatch/middleware/stack.rb:80:in `insert_after'
Error:	from D:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/railties-5.0.0/lib/rails/configuration.rb:69:in `block in merge_into'
Error:	from D:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/railties-5.0.0/lib/rails/configuration.rb:68:in `each'
Error:	from D:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/railties-5.0.0/lib/rails/configuration.rb:68:in `merge_into'
Error:	from D:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/railties-5.0.0/lib/rails/engine.rb:507:in `block in app'
Error:	from D:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/railties-5.0.0/lib/rails/engine.rb:504:in `synchronize'
Error:	from D:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/railties-5.0.0/lib/rails/engine.rb:504:in `app'
Error:	from D:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/railties-5.0.0/lib/rails/application/finisher.rb:37:in `block in <module:Finisher>'
Error:	from D:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/railties-5.0.0/lib/rails/initializable.rb:30:in `instance_exec'
Error:	from D:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/railties-5.0.0/lib/rails/initializable.rb:30:in `run'
Error:	from D:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/railties-5.0.0/lib/rails/initializable.rb:55:in `block in run_initializers'
Error:	from D:/Ruby23-x64/lib/ruby/2.3.0/tsort.rb:228:in `block in tsort_each'
Error:	from D:/Ruby23-x64/lib/ruby/2.3.0/tsort.rb:350:in `block (2 levels) in each_strongly_connected_component'
Error:	from D:/Ruby23-x64/lib/ruby/2.3.0/tsort.rb:431:in `each_strongly_connected_component_from'
Error:	from D:/Ruby23-x64/lib/ruby/2.3.0/tsort.rb:349:in `block in each_strongly_connected_component'
Error:	from D:/Ruby23-x64/lib/ruby/2.3.0/tsort.rb:347:in `each'
Error:	from D:/Ruby23-x64/lib/ruby/2.3.0/tsort.rb:347:in `call'
Error:	from D:/Ruby23-x64/lib/ruby/2.3.0/tsort.rb:347:in `each_strongly_connected_component'
Error:	from D:/Ruby23-x64/lib/ruby/2.3.0/tsort.rb:226:in `tsort_each'
Error:	from D:/Ruby23-x64/lib/ruby/2.3.0/tsort.rb:205:in `tsort_each'
Error:	from D:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/railties-5.0.0/lib/rails/initializable.rb:54:in ` `run_initializers'
Error:	from D:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/railties-5.0.0/lib/rails/application.rb:352:in `initialize!'
Error:	from D:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/railties-5.0.0/lib/rails/application.rb:328:in `require'
Error:	from D:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/railties-5.0.0/lib/rails/application.rb:328:in `require_environment!'
Error:	from D:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/railties-5.0.0/lib/rails/commands/commands_tasks.rb:157:in `require_application_and_environment!'
Error:	from D:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/railties-5.0.0/lib/rails/commands/commands_tasks.rb:143:in `generate_or_destroy'
Error:	from D:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/railties-5.0.0/lib/rails/commands/commands_tasks.rb:60:in `generate'
Error:	from D:/Ruby23-x64/lib/ruby/gems/2.3.0/gems/railties-5.0.0/lib/rails/commands/commands_tasks.rb:49:in `run_command!'

Currently there's no official remotipart release with support for Rails 5.
You have to point my fork
gem 'remotipart', github: 'mshibuya/remotipart'

as described in Installation section of README.
https://github.com/sferik/rails_admin#installation


Is it worth having hash implementations?

Not really a bug-report, but just some food-for-thought if you weren't aware (and my apologies if you were).
One thing I've had a lot of success with is writing a sha256 hash like this:
https://github.com/hookedin/hookedin-lib/blob/0d5b3287fa192692c23bb261f92b0b75e4f3dc84/src/util/browser-crypto/sha256.ts
as well as provide a node.js version with the same signature:
https://github.com/hookedin/hookedin-lib/blob/0d5b3287fa192692c23bb261f92b0b75e4f3dc84/src/util/node-crypto/sha256.ts
and then in the package.json  tell it to switch files depending if it's included in the browser or not:
https://github.com/hookedin/hookedin-lib/blob/0d5b3287fa192692c23bb261f92b0b75e4f3dc84/package.json#L30
It's also worth noting there's no browser crypto for ripemd, so that's another annoyance.

Thanks for opening an issue! This is a great question – and your solution is definitely the best option for a lot of projects. (Related, this is something I've changed my mind on a lot over time.)
Ultimately, the reason this project provides WASM implementations of those methods is to allow for complete portability (see the Design Goals):
3. portable – All code should work on every platform (no Node.js bindings or separate browser versions)
By writing code in a completely portable way, we ensure all of our code is maximally reliable – if different platforms run different code paths, bugs may be present in path but not the other. By using the exact same code across platforms, we also reduce downstream build configuration complexity: e.g. these WASM methods can easily work in a new Deno project without modification.
You can see some other interesting stats in the blog post I wrote about these WASM hashing functions. Here's the most interesting part to me:

The WebAssembly implementations are up to 4x faster than the built-in Node.js implementations (especially for smaller inputs), and easily outperform the pure JavaScript implementation (between 2x and 20x, depending on the use case).
WebAssembly is also remarkably consistent — while other implementations rise and fall in the rankings based on workload, the WebAssembly implementations perform fairly consistently in all cases.

Thanks for the issue! I'm going to close it for now, but please feel free to continue discussing below.


Issue6 verify pojo execution order

Coverage remained the same at 92.34% when pulling 411e84255b0d2a7afdc85f2f174f3fbb83964a12 on issue6_verify_pojo_execution_order into 879549b971fcc28d74b9be8a08badeed000ce46b on master.

Coverage remained the same at 92.34% when pulling 411e84255b0d2a7afdc85f2f174f3fbb83964a12 on issue6_verify_pojo_execution_order into 879549b971fcc28d74b9be8a08badeed000ce46b on master.


Add slot props & check slot

Hello, can you add some more context? I would love to help with this.