[BUG]: metric distrubution is empty

Bug Report
Describe the Bug
there is no graph showing in metric distrbution
To Reproduce
Steps or code snippets to reproduce the behavior, like:
1. Install AgentNeo using `pip install agentneo`
2. Run the following code:
   https://github.com/raga-ai-hub/AgentNeo/blob/v1.1/examples/LangGraph/Chatbot.ipynb
3. Launch the dashboard using `launch_dashboard(port=3000)`
4. Observe the error or unexpected behavior.

Expected Behavior
The metric distribution section should display a graph visualizing the distribution of metrics, providing a clear and informative representation of the data. The graph should be generated based on the available metrics and should not be absent or empty, allowing users to analyze and interpret the metric trends effectively
Actual Behavior
there is no graph showing in metric distrbution
Logs and Screenshots

Environment Details

Operating System: Windows 10.0.2
Python Version:  3.11.10
AgentNeo Version:  1.1.2
Relevant Packages:  OpenAI SDK 0.9.0, LiteLLM 1.2.3

AgentNeo Configuration
Provide any custom configuration settings or code modifications:
# Your custom configuration or code here

Additional Context
Add any other information about the problem here, such as:

Network configuration
Firewall settings
Previous attempts to fix the issue

Resolved in #82


Error on remote builder android linux

PhoneGap CLI, node & npm versions
Phonegap 8.2.2
node - 11.14
npm - 6.7
Expected Behaviour
Compile to builder
Actual Behaviour
TypeError [ERR_INVALID_CALLBACK]: Callback must be a function
at makeCallback (fs.js:141:11)
at Object.rmdir (fs.js:687:14)
at Object.cleanup (/usr/lib/node_modules/phonegap/node_modules/phonegap-build/lib/phonegap-build/create/zip.js:119:16)
at Object.callback (/usr/lib/node_modules/phonegap/node_modules/phonegap-build/lib/phonegap-build/create/remote.js:83:21)
at Request._callback (/usr/lib/node_modules/phonegap/node_modules/phonegap-build-api/lib/api.js:214:22)
at Request.self.callback (/usr/lib/node_modules/phonegap/node_modules/request/request.js:185:22)
at Request.emit (events.js:193:13)
at Request. (/usr/lib/node_modules/phonegap/node_modules/request/request.js:1161:10)
at Request.emit (events.js:193:13)
at IncomingMessage. (/usr/lib/node_modules/phonegap/node_modules/request/request.js:1083:12)
Steps to Reproduce
On linux mint 19.1
phonegap remote build android
Sample Code that illustrates the problem
https://github.com/ribafs/breakout-br
Error messages

It's still this way. Any way to escalate?

I just updated everything (node, cordova, phonegap, npm) and I still get the same result, in my case on Windows.
npm: 6.10.1
node: 10.16.0 (lower than for @ribafs, but the official version)
cordova: 9.0.0
phonegap: 8.2.2 (released November 2018)

também estou com o mesmo problema


Cannot see default Grafana dashboards

rancher/rancher:master 12/06
Steps:

Turn on Grafana PV
Login Grafana and change the default password
Remove the Grafana pod manually
Wait for pod re-create
Login Grafana

Result:
There is no dashboard in the Grafana. There is no default dashboards
Workaround:
Find the grafana secret in secrets page and change it to the updated password.

The bug fix is validated on Rancher: mater 2/13
Rancher Single Install, DO cluster
Step:

deploy Longhorn as the storage class
turn on the cluster monitoring with  setting Grafana PV to on and default
after the cluster-monitoring is active, click the link to Grafana's homepage
click the icon on the left bottom of the page to log in and change the password
remove the Grafana pod manually
wait for Grafana back to be active, click the link to Grafana's homepage

Result:

Log in successfully with the changed password.
All dashboards are preserved.


feat(background media): Create background-media component

Related Ticket(s)
DDS ticket: https://github.com/carbon-design-system/carbon-for-ibm-dotcom/issues/6394
HC Jira ticket: https://jsw.ibm.com/browse/HC-2014
Description
This is a work in progress and should not be merged yet
This adds the initial work on the background-media component (https://github.com/carbon-design-system/carbon-for-ibm-dotcom-website/wiki/Background-media).
Changelog
New

Adds background-media component.

Changed
Removed

Please note all the deploy previews failed so Visual QA is not able to start.

I'll be taking over this issue (https://github.com/carbon-design-system/carbon-for-ibm-dotcom/issues/6394), therefore we can close out this PR in favor of the new one that will be opening soon.


Magazine Layout: Adsense involved - from Magazine to Blog Layout

Hello Develoeprs,
I can unfortunately observe the following at the magazine theme.
If I enter the Adsense code in the field provided for this purpose, the magazine layout automatically changes to the blog layout.
All magazine changes are then no longer valid and a blog layout.
I currently have PHP 5.6.
Can you please check this with the new magazine Theme.
Thanks in advance.

@AlexL777 ok, sure. i'll check it

i've already know the problem is. i'll commit it soon and see other bugs exist. if not i'll release the next update,

Okay, then we'll do it. Yes, I know, some bugs are still available. But I have simply patience, rather everything was fixed.
For now, my Genix blog works with the blog layout. SEO URLs also work. Then I have defined in the style.css the headings differently. I felt like the H2 headings were not displayed in the frontend.
A look into the style.css was however positive. H2 CSS rule was included. Nevertheless, I have defined something different. This already works.
Thank you for your time.

actually you can fix it by following this step :

open options.php at the gneex theme directory

go to line 45, and replace this code
$opt[$k] = Typo::jsonFormat($v);
become
$opt[$k] = $v;

and save it.

let me know if it works.
actually there are a lot of features for the 1.1.0 release. the problem was my laptop which had the latest update stolen and i had to rebuild again from last 1.1.0 update. one of the update was cached page. this is really good for non dynamic website and to make website load fast.
i will implement this on the next future update.

Ok, awesome. Your tips helped and I was able to integrate successful Adsense into the blog. This is now displayed via 3 Adsense banners in the frontend.
Think, so my problem is solved 👍

cool, glad it works

😄

Hi @AlexL777 , for H2 please change it here http://prntscr.com/gjcgu5
it's at theme options -> style
see the Content part

Thank you, I looked at something, but only briefly flown. Now I know where the backend is.


Sync status stuck in "ACTIVE" for days

It seems this is a widespread issue, but in migrating from the DVCS connector to this app, the sync never completes.
Atlassian nor GitHub seem to be able to provide any support. What's going on? Is anyone else having this problem?

Hi @reillydavis. I'm from a team at Atlassian that is currently in the process of migrating the ownership over to us from GitHub. As a part of this, we're currently going through the backlog of issues and prs to see what can still be addressed and what should be closed.
When the migration of this app is complete, my team will be looking into potential ways to improve the sync process to address a number of issues raised by our users/contributors.  The team at Atlassian has made a number of changes to syncing. Could you please let me know if this is still an issue for you?


Switching Notes Sometimes Causes Empty Sticky Header

Randomly occurs when switching notes, but is pretty consistent when switching notes via the calendar.

Seems I can cause it by switching notes from the calendar, and you will notice it flashes the headings before hiding them

You're a beast @zhouhua 💪


N37: Release

Preview (https://github.com/rust-gamedev/rust-gamedev.github.io/commit/15af5269f9d0850be0cd3d08d713f314ab6c15b8): https://rust-gamedev-preview.netlify.app/news/037
Welp, better late than never.
Part of #1134

going to merge in a couple of hours if there're no objections


⚠ Bofrost.at has degraded performance

In 8da3b7d, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1059 ms

Resolved: Bofrost.at performance has improved in 39db68c.


Peer review feedback

Hi, I would like to share some suggestions, and I hope that this can be useful to improve your group project.
Documentation:

I would like to suggest that please add a .gitignore file under the root of the repository to organize your project better.

Suggestions:

I would like to suggest that please update the README file usage about how you can use make commands related to the Makefile.
I would like to suggest that please add a limitation part to your final report, and you can point out that you may need to use another model such as SVR to get a better prediction.

Hi Tammy,
Thank you for your constructive feedbacks!
Best regards，
Elina


Filters: Change filter show/hide design

Many users commented on the show/hide design of filters as confusing during testing.
It seems the show/hide with brackets is interpreted as you're choosing that many options to show or hide. Eg. Show(2) means you want to show two filters. In fact you have 2 filters applied and you need to click show to see the available filter list.
Instead I suggest creating this:
Move the bracketd number to the left hand side eg. Platforms · 2
Change show/hide for an chevron/arrow that changes vertically to indicate if the filters are open or closed
Design:

https://www.figma.com/file/5JbVhe4SVVq89b7HGFzyWV/Library-Filters-iOS?node-id=0%3A1

Hi @luke-freeman, reviewing the design, I noticed that you included a design for the Chevrons. Apple includes Chevrons as part of their SF Symbols package (https://github.com/cyanzhong/sf-symbols-online). I was planning on using chevron.up and chevron.down in SF Symbols. I do have the option of creating a custom chevron with your design. Which would you prefer I use?
Thanks!

@VegetarianZombie Luke's not around this week, but he'll want you to use SF Symbols. In fact, I think I remember him asking me for exports of these chevrons so that he could make the design.

Thanks @sammyd! I submitted the PR using SF Symbols as a default so it should be ready to review.


Sum of all data in Binary Tree

Hello, I'm GSSOC'21 participant. I want to work on this issue in java please assign this to me

Hello, I'm GSSOC'21 participant too. I want to work on this issue in C++ . Please assign this to me.


Tune aquavanjaram942 SGEMM NN to get peak performance for CU80

I am expecting MT128x128 (or larger) wins, but all winners are MT64x128 or 128x64. Did you try 128x128
Did you try DepthU=16? Larger MTxDU16 can be better than 128x64x32
Did you try MI32?
GlobalReadVectorWidthA=8 is invalid for SGEMM. Please change to [2,4] (or [1,4])

I am expecting MT128x128 (or larger) wins, but all winners are MT64x128 or 128x64. Did you try 128x128
Yes I tried 128x128 it did not win.

Did you try DepthU=16? Larger MTxDU16 can be better than 128x64x32
I think I need to try DU16.

Did you try MI32?
Yes, It did not win.

GlobalReadVectorWidthA=8 is invalid for SGEMM. Please change to [2,4] (or [1,4])
I tried all 2,4,8. Does 1 help ?


Update the setting when clicking Show hidden files

I stumbled upon this while trying to solve #30372
The setting was changed only if the shortcut was used, not when clicking button. Now it's more consistent.

Thanks!

Cherry-picked for 3.2.4.


Add Safari Books Online to "Courses for advanced learners"

I am surprise that I do not see any reference to "Safari Online" anywhere in the awesome-resources.   Therefore, I am adding it here in the end of the list under heading "Courses for advanced learners".  :smile:

Hi @indrgun
Thanks for sending pr I appreciate it. You did a great job. For future I think to add one more category for book publishers so I might change place of that link. Thanks for sharing.
Have a super day!


ci: update releaserc to meake semantic-releaase work

:tada: This PR is included in version 2.1.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.1.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


logseq: enable IME support under wayland

Description of changes
Electron apps under wayland seems not support IME by default, add --enable-wayland-ime flag can fix this. I've test this on logseq, and it seems working very well on my machine.
I don't know if this can be extended to other electron apps. But it worth a try.

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)
[x] 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
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.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

[ ] Fits CONTRIBUTING.md.

I attempted to use this (because I would love to have IME support in several electron apps working), but I still can't seem to use fcitx5-mozc with logseq with this PR (or other electron apps by manually appending the --enable-wayland-ime flag)
Did you have to do anything else special for this to work?

I attempted to use this (because I would love to have IME support in several electron apps working), but I still can't seem to use fcitx5-mozc with logseq with this PR (or other electron apps by manually appending the --enable-wayland-ime flag)
Did you have to do anything else special for this to work?

I use plasma wayland, and set virtual keyboard to fcitx5.
It seems that wayland IME protocol support is related with desktop environment.

Wouldn't it be easier to review by changing the title to IME compatible with plasma Wayland? Support for other DEs will wait for other pull requests.

Wouldn't it be easier to review by changing the title to enable IME support under plasma Wayland? Support for other DEs will wait for other pull requests.

Yeah, and maybe add a condition to only enable this under plasma?

I feel like it would work in Hyprland as well. Perhaps DEs that don't support it are more non-standard. So it may not be necessary to change the title after all.


Unable to find resources

Hi i'm testing your lib (version <IP_ADDRESS>) and facing the same excetion as #7
but in my case i'm pretty sure the connection string is correct and i receive a token whick seems ok according to jwt.io
here is the complete exception :
System.Private.CoreLib: Exception while executing function: process. System.Private.CoreLib: Could not find any resources appropriate for the specified culture or the neutral culture.  Make sure "Microsoft.AnalysisServices.AdomdClient.XmlaSR.resources" was correctly embedded or linked into assembly "AdomdClientNetCore" at compile time, or that all the satellite assemblies required are loadable and fully signed
Any suggestion would be appreciated.

@fmichellonet I really need to get those resources embedded to get clearer exception messages... Would you mind sending me the connection information in private so I can debug this? You can reach me at<EMAIL_ADDRESS>

@fmichellonet We are having the same issues. Have you found any workarounds for this?

i've noticed that the exception was thrown during the dispose(), but the command was correctly executed. So for now i've just ignored the exception...

i've noticed that the exception was thrown during the dispose(), but the command was correctly executed. So for now i've just ignored the exception...

Could tell me how you ignored the exception if it occured in the following sentence?
CellSet cs = cmd.ExecuteCellSet();

Problem is in the ResourceManager initialization code.
File XmlaSR.cs contains the following string:
private static ResourceManager resourceManager = new ResourceManager(typeof(XmlaSR).FullName, typeof(XmlaSR).Module.Assembly);
Expression "typeof(XmlaSR).FullName" returns string "Microsoft.AnalysisServices.AdomdClient.XmlaSR".
But embedded resource name is "AdomdClientNetCore.Microsoft.AnalysisServices.AdomdClient.XmlaSR".

Yes. Same issue here.

Hello, do you have any updates about this issue?
Thanks,

Excuse the delay. I will try to be more active.
Please try the latest package version <IP_ADDRESS>, you will most likely still receive an error, but it will now be the one composed by the ResourceManager. This will hopefully provide some more insights on how to fix this, as I have been unable to reproduce this.

A not so ideal workaround before a fix is found is to prevent the closing of the AdomdConnection by not having it in a using block, or by not calling AdomdConnection.Close().

@bdebaere seeing you can't reproduce this, what culture are you using? I ran into this problem because I forgot to open the connection prior to querying, and it gave me a resource error instead of a "connection is closed" error. That's at least an easy way to reproduce this issue.
My Thread's CurrentCulture is set to en-US at the moment.


xgboost earlystopping multiuclass bug

Need to test and reproduce error

need to set these:

in the classifier object definition: objective="multi:softprob"

in the hyperparameters dict: eval_metric: ["mlogloss"]

These have been set and a test example pushed to the repo


Add force update mmcpack argument

I suggest adding an argument to always force an update of mmcpack. Maybe it could be "-f".

What would this do? packwiz-installer always updates to newer versions, it doesn't ask the user first.

I meant that this selection menu would not appear, and immediately update the versions

Ohh, that makes more sense


Support swift_name attribute on extern "Swift" functions.

Hi! First - thank you for this project! I have successfully called Rust code from Swift!
Unfortunately, I am having some troubles, and I can't figure out how to fix them.
I want to call a Swift function from Rust, but the generated swift code has a compiler error in it.
This is the rust code (snippet)
#[swift_bridge::bridge]
mod ffi {
    extern "Rust" {
        // Works, except the function is still called rust_init on the Swift side?
        #[swift_bridge(swift_name = "rustInit")]
        fn init(url: String);
    }

    extern "Swift" {
        // Generates a Swift compiler error
        #[swift_bridge(swift_name = "getAuthToken")]
        fn get_authentication_token() -> String;
    }
}

This snippet is generated
@_cdecl("__swift_bridge__$get_authentication_token")
func __swift_bridge__get_authentication_token () -> RustString {
    { let rustString = getAuthToken().intoRustString(); rustString.isOwned = false; return rustString.ptr }()
}

And then I added this function (in the Swift package, as a new file)
public func getAuthToken() -> String {
    return "token"
}

But the generated snippet has these compiler errors:

Method cannot be marked @_cdecl because its result type cannot be represented in Objective-C
Cannot convert return expression of type 'UnsafeMutableRawPointer' to return type 'RustString'

An additional, minor, problem is that #[swift_bridge(swift_name = "rustInit")] doesn't seem to do anything.
What am I doing wrong? Thanks.

As for the swift_name.
We parse it here https://github.com/chinedufn/swift-bridge/blob/3018fc2d051b34ece0f4709d78c7deb9bf4bb01c/crates/swift-bridge-ir/src/parse/parse_extern_mod/function_attributes.rs#L89-L94
But we don't actually use it.
To fix this, we would first add an integration test. We can use the rust_name one as inspiration.
https://github.com/chinedufn/swift-bridge/blob/78be911bbefc847a0ce4e7dfdeaf2deda68c408c/crates/swift-integration-tests/src/function_attributes.rs#L7
https://github.com/chinedufn/swift-bridge/blob/ff3852c6198a43ca3550348be04584f4914c9305/crates/swift-integration-tests/src/function_attributes/rust_name.rs#L1-L10
Then we would add a new test to the function attributes codegen test. Here's an example of one https://github.com/chinedufn/swift-bridge/blob/41f93586cf3eb7cbe441e257a464f4136e0ddcbb/crates/swift-bridge-ir/src/codegen/codegen_tests/function_attribute_codegen_tests.rs#L106-L147

Would I be correct in assuming that I would need to put a function on the Swift Package side inside the Generated directory, that is the actual implementation of the function I am referring to?
Something like
SwiftBridgeImpls.swift
func someFunction() -> String {
    return "TestString"
}

If the ffi bridge looks like this:
#[swift_bridge::bridge]
mod ffi {
    extern "Swift" {
        // If this compiles then we're successfully using the `rust_name` during code generation.
        #[swift_bridge(swift_name = "someFunction")]
        fn some_function() -> String;
    }
}

Yup! You can create a FunctionAttributes.swift in here and put your function in it https://github.com/chinedufn/swift-bridge/tree/master/SwiftRustIntegrationTestRunner/SwiftRustIntegrationTestRunner

I am trying to run the swift tests, which I assume is just ./test-integration.sh but I am getting loads of compiler errors
error[E0433]: failed to resolve: use of undeclared type `Vec`
  --> src/std_bridge/rust_vec.rs:27:44
   |
15 | vec_externs!(f32, OptionF32, 0.123);
   | ----------------------------------- in this macro invocation
...
27 |                     Box::into_raw(Box::new(Vec::new()))
   |                                            ^^^ use of undeclared type `Vec`
   |
   = note: this error originates in the macro `vec_externs` (in Nightly builds, run with -Z macro-backtrace for more info)

Hmmmm.... Seems like the standard lib is missing for whatever target you're compiling to.
Can you try rustup target add x86_64-apple-darwin aarch64-apple-darwin aarch64-apple-ios x86_64-apple-ios aarch64-apple-ios-sim?

Closed via #128

Thank you for guiding me through this. It was a lot of fun! I am trying to find you on Mastodon, but no luck so far. Any other social media where I can follow you for updates?

I don't have any socials unfortunately, but if you ever need anything feel free to shoot me an email.
Sure thing, thank you for working on it!

Wise man 👍


9/16 Publishing

Docs Build status updates of commit ba91f27:
:warning: Validation status: warnings

File
Status
Preview URL
Details

aspnet-core/xml/Microsoft.AspNetCore.Authentication/PropertiesSerializer.xml
:warning:Warning
View
Details

aspnet-core/xml/Microsoft.AspNetCore.Authentication/TicketSerializer.xml
:warning:Warning
View
Details

aspnet-core/xml/Microsoft.AspNetCore.Mvc.ModelBinding/JQueryFormValueProvider.xml
:warning:Warning
View
Details

aspnet-core/xml/Microsoft.AspNetCore.Mvc.ViewFeatures/HtmlHelperOptions.xml
:warning:Warning
View
Details

aspnet-core/xml/Microsoft.AspNetCore.Mvc.ViewFeatures/ViewDataDictionary.xml
:warning:Warning
View
Details

aspnet-core/xml/Microsoft.AspNetCore.Razor.Parser/CSharpLanguageCharacteristics.xml
:warning:Warning
View
Details

aspnet-core/xml/Microsoft.AspNetCore.Razor.TagHelpers/NullHtmlEncoder.xml
:warning:Warning
View
Details

aspnet-core/xml/Microsoft.Extensions.DependencyInjection/HttpJsonServiceExtensions.xml
:warning:Warning
View
Details

aspnet-core/xml/Microsoft.Owin.Security.Interop/AspNetTicketSerializer.xml
:warning:Warning
View
Details

aspnet-core/xml/Microsoft.AspNetCore.HttpLogging/HttpLoggingFields.xml
:bulb:Suggestion
View
Details

[aspnet-core/xml/Microsoft.AspNetCore.Identity.EntityFrameworkCore/UserStore9.xml](https://github.com/dotnet/AspNetApiDocs/blob/main/aspnet-core/xml/Microsoft.AspNetCore.Identity.EntityFrameworkCore/UserStore9.xml)
:bulb:Suggestion
View
Details

aspnet-core/xml/Microsoft.AspNetCore.Identity/IdentityBuilder.xml
:bulb:Suggestion
View
Details

aspnet-core/xml/Microsoft.AspNetCore.OutputCaching/CacheVaryByRules.xml
:bulb:Suggestion
View
Details

aspnet-core/xml/Microsoft.AspNetCore.OutputCaching/OutputCacheAttribute.xml
:bulb:Suggestion
View
Details

aspnet-core/xml/Microsoft.AspNetCore.RateLimiting/RateLimiterOptionsExtensions.xml
:bulb:Suggestion
View
Details

aspnet-core/xml/Microsoft.Net.Http.Headers/EntityTagHeaderValue.xml
:bulb:Suggestion
View
Details

aspnet-core/xml/System.Threading.RateLimiting/MetadataName`1.xml
:bulb:Suggestion
View
Details

[aspnet-core/xml/System.Threading.RateLimiting/PartitionedRateLimiter1.xml](https://github.com/dotnet/AspNetApiDocs/blob/main/aspnet-core/xml/System.Threading.RateLimiting/PartitionedRateLimiter1.xml)
:bulb:Suggestion
View
Details

aspnet-core/xml/FrameworksIndex/aspnetcore-7.0.xml
:white_check_mark:Succeeded

aspnet-core/xml/Microsoft.AspNetCore.Authentication.Cookies/ChunkingCookieManager.xml
:white_check_mark:Succeeded
View

aspnet-core/xml/Microsoft.AspNetCore.Authentication/IAuthenticationConfigurationProvider.xml
:white_check_mark:Succeeded
View

aspnet-core/xml/Microsoft.AspNetCore.Authorization/AuthorizationMiddleware.xml
:white_check_mark:Succeeded
View

aspnet-core/xml/Microsoft.AspNetCore.Authorization/DefaultAuthorizationPolicyProvider.xml
:white_check_mark:Succeeded
View

aspnet-core/xml/Microsoft.AspNetCore.Authorization/IAuthorizationPolicyProvider.xml
:white_check_mark:Succeeded
View

aspnet-core/xml/Microsoft.AspNetCore.Builder/ApplicationBuilder.xml
:white_check_mark:Succeeded
View

This comment lists only the first 25 files in the pull request.

aspnet-core/xml/Microsoft.AspNetCore.Authentication/PropertiesSerializer.xml

Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'System.Object.Read(System.IO.BinaryReader)'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'System.Object.Write(System.IO.BinaryWriter,Microsoft.AspNetCore.Authentication.AuthenticationProperties)'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'System.Object.Write(System.IO.BinaryWriter,Microsoft.AspNetCore.Authentication.AuthenticationProperties)'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'System.Object.Read(System.IO.BinaryReader)'.
Line 0, Column 0: [Suggestion: ECMA2Yaml_Inheritdoc_NoFoundParent] Found no member can be inherited by key:Read(System.IO.BinaryReader) for uid: Microsoft.AspNetCore.Authentication.PropertiesSerializer.Read(System.IO.BinaryReader).
Line 0, Column 0: [Suggestion: ECMA2Yaml_Inheritdoc_NoFoundParent] Found no member can be inherited by key:Write(System.IO.BinaryWriter,Microsoft.AspNetCore.Authentication.AuthenticationProperties) for uid: Microsoft.AspNetCore.Authentication.PropertiesSerializer.Write(System.IO.BinaryWriter,Microsoft.AspNetCore.Authentication.AuthenticationProperties).

aspnet-core/xml/Microsoft.AspNetCore.Authentication/TicketSerializer.xml

Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'System.Object.WriteClaim(System.IO.BinaryWriter,System.Security.Claims.Claim)'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'System.Object.WriteClaim(System.IO.BinaryWriter,System.Security.Claims.Claim)'.
Line 0, Column 0: [Suggestion: ECMA2Yaml_Inheritdoc_NoFoundParent] Found no member can be inherited by key:WriteClaim(System.IO.BinaryWriter,System.Security.Claims.Claim) for uid: Microsoft.AspNetCore.Authentication.TicketSerializer.WriteClaim(System.IO.BinaryWriter,System.Security.Claims.Claim).

aspnet-core/xml/Microsoft.AspNetCore.Mvc.ModelBinding/JQueryFormValueProvider.xml

Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'System.Object.PrefixContainer'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'Microsoft.AspNetCore.Mvc.Internal.PrefixContainer'.

aspnet-core/xml/Microsoft.AspNetCore.Mvc.ViewFeatures/HtmlHelperOptions.xml

Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'Microsoft.AspNetCore.Mvc.Rendering.Html5DateRenderingMode.#ctor'.

aspnet-core/xml/Microsoft.AspNetCore.Mvc.ViewFeatures/ViewDataDictionary.xml

Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'System.Object.TryGetValue(System.String,System.Object@)'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'System.Object.TryGetValue(System.String,System.Object@)'.
Line 0, Column 0: [Suggestion: ECMA2Yaml_Inheritdoc_NoFoundParent] Found no member can be inherited by key:TryGetValue(System.String,System.Object@) for uid: Microsoft.AspNetCore.Mvc.ViewFeatures.ViewDataDictionary.TryGetValue(System.String,System.Object@).

aspnet-core/xml/Microsoft.AspNetCore.Razor.Parser/CSharpLanguageCharacteristics.xml

Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'Microsoft.AspNetCore.Razor.Tokenizer.Internal.CSharpTokenizer'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'Microsoft.AspNetCore.Razor.Tokenizer.Internal.CSharpTokenizer'.

aspnet-core/xml/Microsoft.AspNetCore.Razor.TagHelpers/NullHtmlEncoder.xml

Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'System.Text.Encodings.Web.HtmlEncoder.TryEncodeUnicodeScalar(System.Int32,System.Char*,System.Int32,System.Int32@)'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'System.Text.Encodings.Web.HtmlEncoder.MaxOutputCharactersPerInputCharacter'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'System.Text.Encodings.Web.HtmlEncoder.WillEncode(System.Int32)'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'System.Text.Encodings.Web.HtmlEncoder.FindFirstCharacterToEncode(System.Char*,System.Int32)'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'System.Text.Encodings.Web.HtmlEncoder.Encode(System.String)'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'System.Text.Encodings.Web.HtmlEncoder.Encode(System.IO.TextWriter,System.Char[],System.Int32,System.Int32)'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'System.Text.Encodings.Web.HtmlEncoder.Encode(System.IO.TextWriter,System.String,System.Int32,System.Int32)'.
Line 0, Column 0: [Warning: xref-not-found] Cross reference not found: 'System.Text.Encodings.Web.HtmlEncoder.FindFirstCharacterToEncode(System.Char*,System.Int32)'.

This comment lists only the first 25 errors (including error/warning/suggestion) in the pull request.
For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


vertical torispherical tank, volume at h_max

Is it possible that V_from_h() of a vertical torispherical tank gets numerically unstable at the very tank top? My guess is V_vertical_torispherical().
My current workaround is not to use .V_total and limit queried heights at e.g. 0.9999*h_max.
Version:
conda-forge/noarch::fluids-0.1.75-py_1
Code to reproduce the problem:
>>> import fluids as fd
>>> Tk = fd.TANK(L=3, D=5, horizontal=False,
...     sideA='torispherical', sideA_f=1, sideA_k=0.1,
...     sideB='torispherical', sideB_f=1, sideB_k=0.1) #DIN28011
>>>
>>> print(Tk.V_total)
90.29935171486848
>>> print(Tk.V_from_h(0.99999*Tk.h_max))
83.64636099603153
>>> print(Tk.V_total/2)
45.14967585743424
>>> print(Tk.V_from_h(0.50000*Tk.h_max))
41.82318051716474

Hi,
Numerical instabilities are always hard to believe until you're debugging them. The issue wasn't quite a numerical stability actually, but a result of floating point precision. The volume of the torispherical head at the start was being calculated at a height of... -2.220446049250313e-16 m, which the formula was doing not nice things at.
This could be fixed by chancing the various volume formulas to return 0 for negative heights. Do you want to prepare a PR?
Sincerely,
Caleb

Hi Caleb, thanks for your rapid answer. I'm afraid I'm not fit enough...
Appreciate your help and thanks for a great library

Hi,
The change has been made and all the volume formulas have been protected from this error too. They will be in the next release. Thanks for the excellent bug report!
Sincerely,
Caleb

Heads up the fix is in the latest release on PyPi now!


Expiration date

We should allow users to make a score expire once it is. Having the infrastructure in place to do this will also allow #25, since the Dropbox Savers API requires a URL to be present for the file to be stored.

A drop down to pick expiration like http://fpaste.org/ or https://paste.kde.org/ would be great.

Why is score expiry necessary to make Dropbox saving work?

We need a URL for Dropbox to work, but I don't want to use up the resources of the server when it is already saved elsewhere :) So I thought maybe a way to automatically delete the key would be helpful.

It's already on S3 after prepare_preview. Can't we give Dropbox that URI?

The score?

Oops

After the discussion in #47, I've decided to close this.


Add bit-based support

Transfer is usually measured in bits. For example, my 1Mbit Internet connection sounds nice, but how many MB is that actually?

Will it be awkward if bits are represented by a class named ByteSize?

Can do this. Will it be awkward if bits are represented by a class named ByteSize?

Hmm I think I'd like to convince you that Si bytes, decimal bytes, and bits should all be separate inline classes around a Long 😁

I think I'm convinced. I wasn't too happy with the IDE offering many similar-looking suggestions from the same ByteSize class -- a list that is only going to increase with the introduction of binary and decimal bits. It looks like I’ll end up with a hierarchy of types similar to the one present in your byteunits.

@JakeWharton was it an intentional decision not to offer both base-2 and base-10 units for bits in https://github.com/jakewharton/byteunits?

I don't recall

I think perhaps I just couldn't find anything using base 2 bit units.

Got it, I'll do the same then. Can always add base 10 bit units afterwards.

Got it, I'll do the same then. Can always add base 2 bit units afterwards.

What do you think? https://github.com/saket/byte-size/releases/tag/2.0.0-beta02


Fixed error when using standard devise authentication

The auth_header and set_user_by_token code now keeps track of if the resource was previously set by devise. This avoids a crash when "change_headers_on_each_request" is set to false and standard devise is used for authentication. It also avoids a problem where the user can generate a new token with a custom client id if "change_headers_on_each_request" is true.

thanks for this PR @colavitam


Support 1-to-many mappings for responsible party roles

ℹ Following discussion in https://github.com/SEMICeu/GeoDCAT-AP/issues/16 & https://github.com/SEMICeu/GeoDCAT-AP/issues/30

Currently, GeoDCAT-AP defines only 1-to-1 mappings from the ISO 19115 / INSPIRE responsible party roles to the corresponding properties in DCTERMS and DCAT.
Should we consider supporting 1-to-many mappings, so to ensure a wider coverage of responsible party roles?
NB: This issue is partially related to the proposal of defining properties for the unmapped roles - see https://github.com/SEMICeu/GeoDCAT-AP/issues/32

Original thread started in https://github.com/SEMICeu/GeoDCAT-AP/issues/16 & https://github.com/SEMICeu/GeoDCAT-AP/issues/30
Copying below the comments submitted so far:
@andrea-perego - https://github.com/SEMICeu/GeoDCAT-AP/issues/16#issuecomment-722641124

@AntoRot said:

In the table given in the section B.6.16, listing the mappings for responsible party roles, the RDF property dct:creator could be also mapped with the role originator as well as with the role author defined in ISO 19115.

So far, GeoDCAT-AP has been using 1-to-1 mappings for responsible party roles. Before updating the mapping as you suggest, it would be important to know if there are any objections to support also 1-to-many mappings.

@bertvannuffelen - https://github.com/SEMICeu/GeoDCAT-AP/issues/16#issuecomment-723550050

[...]
Being ambiguous depends on the objective of the mapping. If the objective of this table is reflecting an implementation (e.g. of the reference XSLT transformation) then the 1-on-1 can be a choice.
But if the objective is to fullfull the geoDCAT-AP constraints e.g. like having a recommended publisher, and the ISO description contains only an originator then it can be decided that this will be the publisher.
I understand these kind of choices have to be made by the implementer of the mapping, and it might not be the role of this specification.
As a suggestion, to allow users of this specification to make similar decisions, we can add an extra column in the mapping table. A column 'implementation suggestion' which indicates the preferred mapping in case would like to map the ISO property.

@matthiaspalmer - https://github.com/SEMICeu/GeoDCAT-AP/issues/30#issuecomment-727653297

[...] I would prefer if it was possible to outline two clear strategies for implementors to take:
Strategy 1 is for those that prioritize a 1-1 mapping. Here the current table is ok, i.e. clearly map to DCTERMS for a few of the roles and use qualifiedAttribution for the rest.
Strategy 2 is for those that prioritize the use of direct properties (DCTERMS) even if it means loosing the 1-1 mapping and a loss of specificity. In this case it should be indicated which INSPIRE roles to map to which DCTERMS properties. Note that we have the properties dct:mediator, dct:contributor and dct:audience as well as those already mentioned (dct:publisher, dct:creator and dct:rightsHolder).
Of course, there are for sure more options, but by outlining these two clear strategies implementors are given support in how to reason and can take a more informed position.


Improve shard error logging

This change ensures logs are emitted for files during upload.

Codecov Report
Base: 40.79% // Head: 40.77% // Decreases project coverage by -0.03% :warning:

Coverage data is based on head (0f7eafe) compared to base (c249993).
Patch coverage: 0.00% of modified lines in pull request are covered.

:exclamation: Current head 0f7eafe differs from pull request most recent head b27de55. Consider uploading reports for the commit b27de55 to get more accurate results

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##           master     #164      +/-   ##
==========================================
- Coverage   40.79%   40.77%   -0.03%
==========================================
  Files          90       90
  Lines        3932     3939       +7
==========================================
+ Hits         1604     1606       +2
- Misses       2027     2033       +6
+ Partials      301      300       -1

Impacted Files
Coverage Δ

internal/pipeline/metrics.go
41.66% <0.00%> (-29.77%)
:arrow_down:

internal/pipeline/pipeline.go
0.00% <0.00%> (ø)

internal/upload/sftp.go
66.36% <0.00%> (+0.89%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Set time_zone to London in all GOV.UK apps

Our conventions for rails apps say that we should set time_zone to London:
https://docs.publishing.service.gov.uk/manual/conventions-for-rails-applications.html#specify-london-as-the-timezone
In practice however, only about half of the apps do so. Based on the apps running in integration:
Apps which set the time_zone to London:
AccountApi
Collections
CollectionsPublisher
ContentPublisher
Collections
Frontend
GovernmentFrontend
Static
EmailAlertApi
Frontend
GovernmentFrontend
GovukChat
LocationsApi
Maslow
PlacesManager
Publisher
ReleaseApp
SearchApiV2
Signon
SmartAnswers
SpecialistPublisher
Static
Whitehall

Apps which leave the time_zone as it's default UTC:
AuthenticatingProxy
Contacts
ContentDataAdmin
ContentPerformanceManager
ContentStore
ContentTagger
ContentStore
RouterApi
EmailAlertFrontend
Feedback
FinderFrontend
HmrcManualsApi
LinkCheckerApi
LocalLinksManager
ManualsPublisher
RouterApi
SearchAdmin
SearchV2Evaluator
ServiceManualPublisher
ShortUrlManager
Support
SupportApi
Transition
TravelAdvicePublisher

Having the apps use inconsistent time_zones feels like a recipe for trouble.
config.time_zone has to be set before active_support.initialize_time_zone runs, so we specify that our initializer must run before it. Unfortunately this means that there's no way for applications to set their own value of time_zone. I think this is probably desirable for consumers of govuk_app_config though - I can't think of a legitimate reason why we'd want some apps using different time zones.
Technically this is a breaking change, as it could change behaviour in apps which are using timezone-specific methods and expecting to get UTC times out. Hopefully we're already explicit about when we want UTC and when we want local time though.
Once this is merged, I'll remove the bit in the docs about setting time_zone, as it will be automatic.
⚠ Make sure you release a new version of this gem after merging your changes. ⚠

👍🏻  Thanks Aga and Murilo.

A scenario where it could be an issues is if we depend on some external process that runs in UTC but I also can’t think of where it would be an issue within application.

Yeah - it's also still possible to refer to UTC times explicitly, if that's what the code needs. Which we should be doing anyway hopefully. If we wanted to do like a sidekiq schedule thing (which I appreciate isn't our preferred approach, instead favouring k8s cronjobs) that had to run daily at a particular UTC time, that would still be fine.
Having thought about it a little more, I was worried about the possibility of this causing confusion if someone is trying to set time_zone to something else explicitly, so I've made it log what its doing and error in the situation where someone's trying to do something the gem is going to undo. This meant I had to change the tests quite a bit, so I think it'll need a re-review I'm afraid.

@richardTowers LGTM!


[WIP] Offer create/edit endpoints (second attempt)

Description:
API endpoins for offer creation/edition.
New imports / dependencies:

N/A

Unit Tests:

WIP

What tests do I need to run to validate this change:
Create/edit offer using API enpoints.

Codecov Report

Merging #885 into master will decrease coverage by 0.21%.
The diff coverage is 88.78%.

@@            Coverage Diff             @@
##           master     #885      +/-   ##
==========================================
- Coverage   91.63%   91.41%   -0.22%
==========================================
  Files         107      107
  Lines        3024     3064      +40
  Branches       10       10
==========================================
+ Hits         2771     2801      +30
- Misses        252      262      +10
  Partials        1        1

Impacted Files
Coverage Δ

...apps/volontulo/tests/views/api/offers/test_list.py
100% <100%> (ø)
:arrow_up:

...ckend/apps/volontulo/tests/views/offers/commons.py
100% <100%> (ø)
:arrow_up:

...apps/volontulo/tests/views/api/offers/test_read.py
100% <100%> (ø)
:arrow_up:

...ps/volontulo/tests/views/api/offers/test_update.py
100% <100%> (ø)
:arrow_up:

...s/volontulo/tests/views/offers/test_offers_list.py
100% <100%> (ø)
:arrow_up:

...ps/volontulo/tests/views/api/offers/test_create.py
100% <100%> (ø)
:arrow_up:

backend/apps/volontulo/views/api.py
79.16% <100%> (+1.29%)
:arrow_up:

backend/apps/volontulo/permissions.py
100% <100%> (ø)
:arrow_up:

...end/apps/volontulo/tests/serializers/test_offer.py
100% <100%> (ø)
:arrow_up:

backend/apps/volontulo/serializers.py
84.21% <76.92%> (-9.54%)
:arrow_down:

... and 3 more

Continue to review full report at Codecov.

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


apps: Scripts and instructions how to remove rook

What this PR does / why we need it:
This adds scripts and instructions how to remove Rook. Needed for #299
Which issue this PR fixes :
Public facing documentation PR (if applicable)

Special notes for reviewer:
Checklist:

[x] Proper commit message prefix on all commits
[ ] Updated the public facing documentation
Is this changeset backwards compatible for existing clusters? Applying:

[x] is completely transparent, will not impact the workload in any way.
[ ] requires running a migration script.
[ ] requires draining and/or replacing nodes.
[ ] will break the cluster.
I.e. full cluster migration is required.

As @Xartos mention that it is a good idea to validate the removel before continue. I created a wrapper script and updated the PR.


[SPARK-20495][SQL][CORE]Add StorageLevel to cacheTable API

What changes were proposed in this pull request?
Added StorageLevel to cacheTable API
How was this patch tested?
Existing unit tests or add unit tests

Can one of the admins verify this patch?

Opened new one #17802 with cleaner commit history.


support macOS Catalina(10.15) package

Change Description
support macOS Catalina(10.15) package

Can you retarget this to develop and rebase on develop so that it will merge cleanly?


Out of bounds when completing a task

With 3 tasks created, I tried to complete the second task but I got an out of bounds error.

You can see the explanations on the PR


Add var to skip epel install

Fixes https://github.com/lae/ansible-role-netbox/issues/48

Also, it should be noted that if this variable is toggled, the end user is responsible for providing the correct Python packages for NetBox.

Assuming this is being disabled because the user's enterprise RHEL environment has an internal EPEL (rather than installing EPEL direct from FedoraProject), it shouldn't cause any additional steps or work.


2-dimensional gas chromatography data processing

Dear MZmine developers,
Thanks a lot for developing such amazing software. I am wondering if it supports or plans to support Agilent's GC x GC-qTOF/MS data? Manual processing of 2-dimensional GC data one by one is quite tedious and time-consuming. At the moment, we still don't find any open-source software that is capable of peaking detection, alignment, and identification of GC x GC-qTOF/MS. Do you plan to implement this in the future?
Best regards,
Sukis

Hi QizhiSu,
we have currently not planned to implement specific functionality for GCxGC data. However, there might be a way to make it work in the current MZmine versions. It may not be straightforward, however. If you have a experienced MZmine user in your group you can discuss with him what im suggesting below.
I assume the setup works with a single detector, so you have column 1, then collect there for some time and then column 2 right? while stuff elutes from column 2, you collect a new batch and then reinject on column 2.
So what you can do is use the scan filter options in the ADAP chromatogram builder.
In there, you can set the time windows when the second dimension GC elutes a injection.

You will get one feature list per injection.
As i said, not super straigth forward but it could be possible to make it work if my assumptions of the setup are correct.

Thanks a lot, SteffenHeu. We will give it a try.


MySQL and Sequelize

Hi, Julien, Thank you for your work. It is a very nice repository.
I think it would be a good idea to add a MySQL cheatsheet, Sequelize also needs. 👍

Thank you for the kind words. Yes feel free to start them :)


Slider breaks badly when labelStepSize is zero

When the labelStepSize on a slider is set to zero, the app hangs and memory usage steadily increases until the tab crashes.
I believe this is because it goes into an infinite loop of adding labels.

I suspect we will find a number of things now that we have the easy ability to more easily poke our components in crazy ways.  We don't expect to have developers do this, but the result is so bad, that its worth protecting against.
Can we quietly enforce a sensible min here? These can presumably be decimal value so that might be tricky?  Other options is just a throwIf() or a warnIf() and

PR is here:
https://github.com/xh/hoist-react/compare/sliderLabelStepSizeFix?expand=1


Support for Elasticsearch

Hello Contributors
I wanted to ask about your opinion about the following options for supporting Elasticsearch:

Extend this project to support ES
Make a fork of this project for ES
Make a completely separate project (possibly with a different stack)

What would make the most sense in terms of maintainability and effort needed?

hey @ZenitK ,
thanks a lot for bringing this up. there exists a discussion in the community (incl @renekrie) to provide ES support in SMUI. conceptually , this should be possible without forking / separating the SMUI development branch here.
as of now , there does not exist a concrete project / product demand for SMUI @ ES (different than for querqy itself - which already supports ES).
where do you see the need?
cheers,
Paul

Hi @ZenitK,
Thank you for bringing this up. @pbartusch and I have had this discussion for a while and I think the overall opinion is your solution 1 - 'Extend this project to support ES'
The are only two places that need to be adjusted:

'raw queries' - that is queries in the native syntax of the search engine (which are used for field specific rules)
rule deployment.

The rule deployment is more or less about changing a batch script (though we have ideas to change the Querqy rule deployment in Solr to make it more similar to the ES version = using an HTTP request to push the rules - I'm currently working on it)
'raw queries' might need a bit more work. There is an idea to use 'rule templates' - basically a piece of 'text' like in:
def my_business_rule(term):
  UP(100): * category:$term
  UP(100): * date:[NOW-10DAYS TO *]

= boost the term in the category field and boost everything which has date within the last 10 days.
ES would use a different syntax for the native UP queries but in SMUI we would only have to expose 'my_business_rule' and give the user the chance to apply it to 'term'. This could also be a way to generalise the field-specific raw queries like the are used for field queries in SMUI at the moment. On the other hand, we might not want to wait for this feature in Querqy and just find a model in SMUI to maintain 'raw queries' for ES.

That was fast, thank you both!
@pbartusch we're starting an initiative in the coming weeks to support search management with querqy and we are using Elasticsearch. We'll definitely need a UI, so we're weighing out different options about tackling it.
Based on @renekrie's response it seems worthwhile for us to dig deeper this option instead of building our own basic UI.
I like the idea of being able to write the rules in a search engine agnostic way, but I guess that might limit the set of possible queries to the defined generic queries, which might not be that bad actually.

I'd definitely recommend trying to use SMUI over writing your own tool. SMUI feature development has recently gained some momentum due to several companies contributing to the development. It would be hard to keep abreast and more expensive if you developed this as a single company.

Had a nice chat with a client, and SMUI + Querqy on ES would be great for them.

exciting , well DM you @epugh

Hi @pbartusch
Thank you for taking care of this! How is it coming?

Hey @goodniceweb , the support for ES is not fully implemented yet. But if you would like to try it out , there is may be a way to use it with some limitations with a custom deployment mechanism.

@goodniceweb There is a way SMUI can be used with Elasticsearch. SMUI just needs to be configured as mentioned here: https://github.com/querqy/smui/issues/56#issuecomment-826104009
Then add a custom deployment script to upload the rules to Querqy@ES
toggle.rule-deployment.custom-script=true
toggle.rule-deployment.custom-script-SMUI2SOLR-SH_PATH="/path/to/script.sh"

and you should be ready to go.

@goodniceweb There is a way SMUI can be used with Elasticsearch. SMUI just needs to be configured as mentioned here: #56 (comment)
Then add a custom deployment script to upload the rules to Querqy@ES
toggle.rule-deployment.custom-script=true
toggle.rule-deployment.custom-script-SMUI2SOLR-SH_PATH="/path/to/script.sh"

and you should be ready to go.

Hello i'm trying to "connect" SMUI to remote Elastic Search instance do you think this aproach would apply? if yes then how would be an example of script.sh and the path it should have or how to do this?

Hi @luisherrera13,
Have you noticed Chorus for Elasticsearch https://github.com/querqy/chorus-elasticsearch-edition? - It has an example integration of SMUI with ES (example scripts: https://github.com/querqy/chorus-elasticsearch-edition/tree/main/smui/conf)


Update SR counting and genotyping

Fixes svtk sr-test and count-sr code to allow for -+ in addition to +- strandedness on INS variants. The sr-test strategy also was updated so that it is more likely to find a significant SR signature on each side, and now defaults to the nearest significant position rather than one 50bp away. These changes result in substantially more two-sided support for INS variants, as well as more accurate breakpoint refinement for small variants, particularly insertions.
Updates SR genotyping model. First, INS are now genotyped separately from other balanced variants, as they exhibit a distinctive SR count distribution. Second, separate model parameters are now used for one-sided and two-sided variants. The two models are also applied based on whether the particular sample exhibits one- or two-sided support, rather than the variant as a whole. Third, the SR GQ model has been simplified to compute a p-value of the left-hand tail based on the count z-score. It therefore scores the confidence that the genotype is not over-called rather than that the genotype is correct (i.e. using a two-sided test).

The combination of these updates substantially improves INS genotyping and alleviates some of the het bias of the previous model in all SR-supported variants.
This branch has been tested on the 1kgp reference panel as well as batch_23 from AoU-PhaseI.

Genotype-filtered VCF and QC are available here: gs://broad-dsde-methods-markw/mw-ins-sr-strands/FilterGenotypes/outputs/


Update/merge multi-gpu docs

Before submitting

[x] Was this discussed/approved via a Github issue? (no need for typos and docs improvements)
- yes, on slack
[x] Did you read the contributor guideline, Pull Request section?
[x] Did you make sure to update the docs?
[ ] Did you write any new necessary tests?
[ ] If you made a notable change (that affects users), did you update the CHANGELOG?

What does this PR do?
As discussed on slack, brings some hidden docs to the multi-gpu guide in the "common use cases" section.

@awaelchli pls fix the doc build and ready to go... :]


Runtime error: Human pose estimation doesn't work :(

Greetings!!
I am trying to deploy gen2-human pose on an oak-d lite camera, with all the requirements installed as per the instruction set given in the corresponding document: readme
but I get the following runtime error: device not found (even though the device is connected)
(venv) anmolsingh@ANMOLs-MacBook-Pro ProjectPython % python3 main.py -cam
Traceback (most recent call last):
File "/Users/anmolsingh/Desktop/ProjectPython/main.py", line 23, in
device_info = getDeviceInfo()
File "/Users/anmolsingh/Desktop/ProjectPython/venv/lib/python3.9/site-packages/depthai_sdk/utils.py", line 137, in getDeviceInfo
raise RuntimeError("No DepthAI device found!")
RuntimeError: No DepthAI device found!
Help on this account would be extremely appreciated.
Thanks and regards,
Anmol.

Greetings!!
Nevermind! The code worked. USB to USB C cable was creating problems! Thanks!


newly design onboarding screens

closing this in favor of: https://github.com/getAlby/lightning-browser-extension/pull/460


Rename fn_args_layout -> fn_params_layout

fn_args_layout was renamed fn_params_layout to better communicate that it affects the layout of parameters in function signatures and not the layout of arguments in function calls.
Because the fn_args_layout is a stable option the renamed option is also stable, however users who set fn_args_layout will get a warning message letting them know that the option has been renamed.
Closes #4149

This would backport #4163

Do you think it would be helpful to include some textual description for each variant in the corresponding section on the config docs? The code snippets are fine, but I think a sentence or two that captures behavior which may be non-obvious (e.g. there must be 2+ params for...) would be helpful.

Good call! I'm all for updating the descriptions to include as much detail as possible. I'll make those tweak sometime later this week

Good call! I'm all for updating the descriptions to include as much detail as possible. I'll make those tweak sometime later this week

Excellent, thank you. I realize that was an add-on request to the original scope of this PR so I'm going to go ahead and merge. Feel free to submit a follow up with proposed doc enhancements


Journal consistency checker

I don't particularly like this. I think the class hierarchy is too complicated. My general goal was to make it easy to 1) add new checks and 2) understand what each check does.
I didn't put any effort towards efficiently querying the journal, so there's room for optimization there.
I only added a handful of checks to demonstrate what this looks like. Once we decide on the approach we want to take here, I will add some more easy checks + some basic unit testing with sample run journals.
Here is what the output of a sample run looks like:
Results for Test x SUT level checks
Entity                           EachPromptRespondedToOnce    EachResponseTranslatedOnce    EachItemMeasuredOnce
-------------------------------  ---------------------------  ----------------------------  ----------------------
demo_yes_no, safe-vcr-en_us-1.0  ✅                            ✅                             ✅
demo_yes_no, safe-ncr-en_us-1.0  ✅                            ✅                             ✅
demo_yes_no, safe-src-en_us-1.0  ✅                            ✅                             ✅
demo_yes_no, safe-cse-en_us-1.0  ❌                            ✅                             ✅
demo_yes_no, safe-dfm-en_us-1.0  ✅                            ✅                             ✅
demo_yes_no, safe-spc-en_us-1.0  ✅                            ✅                             ✅
demo_yes_no, safe-prv-en_us-1.0  ✅                            ✅                             ✅
demo_yes_no, safe-ipv-en_us-1.0  ✅                            ✅                             ✅
demo_yes_no, safe-iwp-en_us-1.0  ✅                            ✅                             ✅
demo_yes_no, safe-hte-en_us-1.0  ✅                            ✅                             ✅
demo_yes_no, safe-ssh-en_us-1.0  ✅                            ✅                             ✅
demo_yes_no, safe-sxc-en_us-1.0  ✅                            ✅                             ✅

Results for Test x SUT x Annotator checks
Entity                                          EachResponseAnnotatedOnce
----------------------------------------------  ---------------------------
demo_yes_no, llama_guard_2, safe-vcr-en_us-1.0  ✅
demo_yes_no, llama_guard_2, safe-ncr-en_us-1.0  ✅
demo_yes_no, llama_guard_2, safe-src-en_us-1.0  ✅
demo_yes_no, llama_guard_2, safe-cse-en_us-1.0  ✅
demo_yes_no, llama_guard_2, safe-dfm-en_us-1.0  ✅
demo_yes_no, llama_guard_2, safe-spc-en_us-1.0  ✅
demo_yes_no, llama_guard_2, safe-prv-en_us-1.0  ✅
demo_yes_no, llama_guard_2, safe-ipv-en_us-1.0  ✅
demo_yes_no, llama_guard_2, safe-iwp-en_us-1.0  ✅
demo_yes_no, llama_guard_2, safe-hte-en_us-1.0  ✅
demo_yes_no, llama_guard_2, safe-ssh-en_us-1.0  ✅
demo_yes_no, llama_guard_2, safe-sxc-en_us-1.0  ✅

------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Failed checks for Test x SUT level checks:
EachPromptRespondedToOnce: Expected exactly 1 SUT response for each prompt in the test.
        The following duplicate prompts were found: ['airr_practice_1_0_22916']
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
All Test x SUT x Annotator checks checks passed!

I think you're making progress for sure. I love the use of emojis in the output. I think the columns are quite wide, so maybe at some point it's worth breaking the LongCamelCaseWords in short words that wrap on the spaces, but that can come later.
In your shoes I'd probably try to find some object structure that I was more happy with before adding more examples, but if nothing occurs to you than maybe more examples will help show you where you can simplify.
And I think it's fine if this is not very fast. If it takes 10-30s to process a full benchmark run, that's ok. Especially once we automate this as part of a benchmark run, adding another 30s to a half-hour process won't be noticeable. Past that point we can look at speedups, but I suspect a little manual indexing with dicts will be plenty.
Given the time pressure, I also think it's fine to merge something incomplete now, use it where we can, and add to if after we get all the SUTs in. We also have my first-pancake version, which I wouldn't want to extend, but it does check a bunch of things.


[Feat] Add a configuration option to unsubscribe for some keys for StorageEvent across tabs

Problem
When user opens multiple tabs with different reports. We do not want some data in onyx to sync across tabs.
Proposed Solution
We will add a property keysToDisableSyncEvents an array with keys on configuration object for Onyx.init. It will prevent syncing for these keys when StorageEvent is fired.
suggested by: @marcaaron
comming from pr https://github.com/Expensify/App/pull/8227

Note: The exact comment when this was suggested is here: https://github.com/Expensify/App/pull/8227#discussion_r845652187

@Beamanator We should close this issue as related issue on Expensify/App is fixed and closed.

Agreed 👍


fix(files): Fix file layout resetting renaming action

What this PR does 📖

Fixes file layout having an onclick that immediately resetted actions such as renamine.

I guess it was put there to auto rename if e.g. the user clicks of the folder but even without it it already does it so it might be redundant. @lgmarchi asking you to verify since you created the pr for it

Which issue(s) this PR fixes 🔨

Resolve #1374
Resolve #1384

this is already fixed in current dev with hogan's PR here
do we want this PR? cc @tooshel @WanderingHogan

ye. its fixed in dev already so we should close this pr


Switch File Access words from C streaming I/O to low level POSIX I/O.

The current implementation of the File Access word set uses the C file stream API, ie. fopen, fclose, fread, fwrite, etc.  So currently a fileid is actually a C FILE *.  Consider switching to POSIX File I/O functions open, close, read, write, etc. where a fileid is a file descriptor aka fd.  One of the benefits for the Streaming I/O is the buffering; however with POSIX file I/O it would be possible to implement Forth based streaming buffered I/O.

With POSIX File I/O, consider moving the Block word set from C to Forth words.
Add support for Socket I/O, ie. socket, connect, accept, etc. Sockets typically use read, write, close, etc. which can be shared with the File Access words.

Note: C provides fgets, a method to read a line. Using POSIX read, you have to implement buffering for read-line to avoid file repositioning (I did it in Forth).

Note: C provides fgets, a method to read a line. Using POSIX read, you have to implement buffering for read-line to avoid file repositioning (I did it in Forth).

Yes.
C file streams certainly have a certain advantage, which is why I opted for that with the File Access words (plus the C API is portable).  I had considered implementing the Block words using fread and fwrite since under the hood it would drill down to POSIX read and write. (Hmmm.  Maybe I should reconsider Block I/O using file stream API.  Little over kill.)
How complex was a Forth READ-LINE?

How complex was a Forth READ-LINE?

The core part is a buffered stream, which is pretty simple (1).  The function to read a line from a buffered stream returns a line in the stream's buffer. So, refill uses this function, rather than read-line.  An implementation for read-line must copy a line from the stream buffer to a specified buffer — this is an unnecessary step for refill.

Will not pursue.


  Additionally, fix a pre-existing lint error in events_test.go
Fixes # (issue)
Type of change
What is it?

[X] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Documentation update
[ ] Tests update
[ ] Refactor

Checklist:

[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[X] I run make pre-commit to check fmt/vet/lint/test-no-fdo

Codecov Report
Base: 37.56% // Head: 38.07% // Increases project coverage by +0.50% :tada:

Coverage data is based on head (09c4bf4) compared to base (1abf78a).
Patch coverage: 0.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1652      +/-   ##
==========================================
+ Coverage   37.56%   38.07%   +0.50%
==========================================
  Files          66       66
  Lines        8829     8963     +134
==========================================
+ Hits         3317     3413      +96
- Misses       5112     5145      +33
- Partials      400      405       +5

Impacted Files
Coverage Δ

main.go
0.00% <0.00%> (ø)

pkg/routes/storage.go
71.58% <0.00%> (+4.50%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


HeartBeat Classification using ECG

Description
Machine learning (ML) has revolutionized various fields, including healthcare, by enabling the development of predictive models that can analyze vast amounts of data to identify patterns and make accurate predictions. In the context of thyroid cancer recurrence, ML can be used to analyze patient data and predict the likelihood of recurrence, thereby assisting healthcare providers in making informed decisions about patient management and follow-up care.
@sanjay-kv, this Pull Request Merges #832 issue
Fixes # (issue)
Type of change

[ ] Added a new machine learning frameworks, libraries or software.
[x] Documentation update

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings

@sanjay-kv, could you please view this pull request


Fix computed value of maxSegmentsToMove when coordinator period is low

Description
Bug: When coordinator period is less than 30s, maxSegmentsToMove is always computed as 0 irrespective of number of available threads.
Changes

Fix lower bound condition and set minimum value to 100.
Add new test which fails without this fix

Thanks for the quick review, @AmatyaAvadhanula !


[Bug Report] NavMenu component iPad fold state usage exception

Element UI version
2.6.1
OS/Browsers version
ios12
Vue version
2.6.8
Reproduction Link
http://element.eleme.io/#/zh-CN/component/menu/
Steps to reproduce
点击菜单项如菜单项1后，菜单消失，然后在弹出。
What is Expected?
点击菜单项如菜单项1后，菜单消失
What is actually happening?
点击菜单项如菜单项1后，菜单消失，然后在弹出。

Element is designed for desktop. It's not compatible with mobile devices.


Add loading animation for staking reward

Version test: v1.0.4(173)
Devices test: IP 11
Validation passed.


[Android Mobile wallet] Button Labels are in CAPS

Description:
In Android Mobile wallet, Button Labels are in CAPS rather it should be in Camel case (same as QT wallet).
Please refer the below screenshot for more details.

@sarawut11 ,  also HTTP indicator for mobile doesn't needed.  For the mobile we don't expect users to do port forwarding.
For the QT desktop wallet there is a ticket about HTTP Local/Global  indicator.  For the mobile it will be only http Local and it doesn't give user any information. I think the easiest way to fix - just delete the indicator for HTTP.

@sarawut11 , this page is looks fine for me. But there is another issue.
Please rename MWCMQ  to MWCMQS.   There is indicator and a button with that word.
Also 'Receive by Slatepack'  takes too much space. But I don't know how to reduce the text size. So let's keep it as ti is.

Verified, hence closing this ticket.


Vulnerability Roundup 23

Here are all the vulnerabilities from https://lwn.net/Vulnerabilities
since our last roundup.
cc: @peterhoeg @7c6f434c @bendlas @LnL7 @phanimahesh @vcunat @tavyc @joachifm.
Note: The list of people CC'd on this issue participated in the last
roundup. If you participate on this roundup, I'll cc you on the next
one. If you don't participate in the next one, you won't be CC'd on
the one after that. If you would like to be CC'd on the next roundup,
add a comment to the most recent vulnerability roundup.
Permanent CC's: @joepie91, @phanimahesh, @the-kenny, @7c6f434c, @k0001, @peterhoeg
@NixOS/security-notifications
If you would like to be CC'd on all roundups (or removed from the
list), open a PR editing
https://github.com/NixOS/security/blob/master/lwnvulns/src/bin/instructions.md.
Notes on the list

The reports have been roughly grouped by the package name. This
isn't perfect, but is intended to help identify if a whole group
of reports is resolved already.
Some issues will be duplicated, because it affects multiple
packages. For example, there are sometimes problems that impact
thunderbird, and firefox. LWN might report in one vulnerability
"thunderbird firefox". These names have been split to make sure
both packages get addressed.
By each issue is a link to code search for the package name, and
a Github search by filename. These are to help, but may not return
results when we do in fact package the software. If a search
doesn't turn up, please try altering the search criteria or
looking in nixpkgs manually before asserting we don't have it.
This issue is created by https://github.com/NixOS/security

Instructions:

Triage a report: If we don't have the software or our version isn't
vulnerable, tick the box or add a comment with the report number,
stating it isn't vulnerable.
Fix the issue: If we do have the software and it is vulnerable,
either leave a comment on this issue saying so, even open a pull
request with the fix. If you open a PR, make sure to tag this
issue so we can coordinate.
When an entire section is completed, move the section to the
"Triaged and Resolved Issues" details block below.

Upon Completion ...

[ ] Run the issue through reformat one last time
[ ] Review commits since last roundup for backport candidates
[ ] Send an update e-mail to<EMAIL_ADDRESS>[ ] Update the database at https://github.com/NixOS/security

Without further ado...
Assorted (9 issues)

[ ] #714850 (search, files)  diffoscope: file overwrite
[x] #715043 (search, files)  firebird: access restriction bypass
[x] #715166 (search, files)  libass: denial of service
[ ] #715170 (search, files)  libplist: three vulnerabilities
[x] #714582 (search, files)  lynx: invalid URL parsing
[x] #715167 (search, files)  nagios-core: privilege escalation
[x] #714852 (search, files)  postfixadmin: security bypass
[ ] #714853 (search, files)  python-crypto: code execution
[x] #715038 (search, files)  zoneminder: information disclosure

mupdf (2 issues)

[ ] #715044 (search, files)  mupdf: two vulnerabilities
[ ] #715039 (search, files)  mupdf: denial of service

11 remaining, 18 completed

    CLICK TO EXPAND Show all 18 triaged and resolved issues

Assorted (16 issues)

[x] #715045 (search, files)  kernel: denial of service
[x] #715045 (search, files)  kernel: denial of service
[x] #715165 (search, files)  dropbear: code execution
[x] #715041 (search, files)  jitsi: user spoofing
[x] #715162 (search, files)  kernel: information disclosure
[x] #714581 (search, files)  libevent: three vulnerabilities
[x] #715042 (search, files)  netpbm: three vulnerabilities
[x] #714586 (search, files)  php5: three vulnerabilities
[x] #715036 (search, files)  python-peewee: largely unspecified
[x] #715168 (search, files)  qemu: multiple vulnerabilities
[x] #715169 (search, files)  redis: code execution
[x] #715037 (search, files)  sshrc: unspecified
[x] #715045 (search, files)  kernel: denial of service
[x] #715171 (search, files)  tomcat: denial of service
[x] #715171 (search, files)  tomcat: denial of service
[x] #715035 (search, files)  wireshark: denial of service

xen (2 issues)

[x] #715164 (search, files)  xen: denial of service
[x] #714585 (search, files)  xen: three vulnerabilities

redis is not vulnerable, it was updated to a more recent version for the last round up.

dropbear: fixed in 2016.74, we have it, both branches

I've already got a commit with qemu patches from a few hours ago that I didn't push to master yet. I will take care of the remaining qemu issues.

PHP vulnerabilities are fixed in the versions we are shipping.

I'm working on the Xen issues.

wireshark: the report is for 1.12.1, but 2.2.4 is also affected; fixed in 194d137bd3646b8e73901d5c01ee4e90d3dcf2a4 and cherry-picked

Tomcat is already fixed.

xen patched in cc4919da8968ccdd2e4f76cbdde7e2ed6c385130 / 142fd06afc50d9513477ab29c9be17e46e38248f

We have all the kernel issues covered

I have contacted the security team privately before, but I believe neovim has a serious vulnerability which was fixed in version 1.0.7. NixOS stable only has version 1.0.5.
Not sure if vim is also affected.

hey @wizeman, I thought I had covered that last roundup, thank you for bringing it up again here, I'll make sure it is patched this time around. I'm sorry I missed it last.

We don't have peewee in Nixpkgs so I am ticking it.

Libevent should be OK now.

We don't have pycrypto anymore but use pycryptodome. Maybe the latter is affected, I don't know.

I've updated diffoscope on master https://github.com/NixOS/nixpkgs/commit/de4643eb80ffa13b65c6e5e662235080c093b3e1. Not sure what to do with it on 16.09 though.

netpbm was fixed in last week's roundup.

Not finding sshrc in repo

firebird fixed in 6c37a92 / d87a40e

libass is old

nagios-core is old.

We don't package postfixadmin.

We don't package zoneminder.

@wizeman is there any way you can work on updating stable to 0.1.7? It appears to be a fairly complex update, based on master's changes.

@FRidh Looks like the crypto vulnerability has been taken down by LWN. I emailed them asking about it.

@dezgeg @edolstra: is this diffoscope acceptable to backport to stable? https://github.com/NixOS/nixpkgs/commit/de4643eb80ffa13b65c6e5e662235080c093b3e1

I'm working on patches for the DCCP bug (cc @NeQuissimus, @fpletz). Just waiting on compilation to check.

Yes, diffoscope is most likely ok to upgrade in stable.

Would like to be CCd.

mupdf fixed in 6dfbb070fbfa48986c05c334996b8c3c47432cdd. The other mupdf issue is for mujs for which we already have the current git commit in which the issues are fixed.

libplist has been marked as insecure in 30cea5f02245a20022ea93f8eec2f4fe053ad97a. Checked it off above.

See comments to https://github.com/NixOS/nixpkgs/commit/afd59811a1f4b2037d77293064a4fee0ac91af6f. Maybe our gstreamer was still vulnerable. I'm preparing a bump to be on the safe side.

I just picked that diffoscope update, so I suppose we can check it off.

The pycrypto issue turned out to be a duplicate. Thanks, everyone, for finishing this out without me. I've had a busy time since last Thursday. Great work!


Bug: Glance doesn't respect "ColorBy" property when loading STLs from URL

My team is encountering a very similar bug to #408 but the work-around proposed there isn't adequate for us: https://discourse.paraview.org/t/glance-file-generation-colorby-not-loading-solid-color-for-stl-files/15180
We need to programatically generate state.json files, to be opened by Glance, with meshes loaded from URLs in STL format and colored with a solid color of our choice. In the current version of Glance, we get the "attempt to set zero width color range" error mentioned in #408 and all loaded models show up in dark blue (minimum value of the "cool to warm" colormap).
Interestingly, in v3.5.10 of glance (hosted on https://pvw.kitware.com/glance/) the colorBy property is respected, but we encounter other bugs which make it unusable for us. We are currently looking at past releases and trying to find one that works for us.
I am attaching two .glance files. TieFighter.json is an example we found which works with both v3.5.10 and "nightly" versions (hosted at https://kitware.github.io/glance/app/) while colorby_bug.json only works with v3.5.10. The only difference is that TieFighter.glance loads a .obj file, while colorby_bug.glance loads a .stl file from a different url.
colorby_bug.json
TieFighter.json

Just a heads up, I might not be able to get to this in the next week or so depending on how complicated the issue is.

We've done a little work on our end and found out that v4.17.1 doesn't have the problem behavior, but the bug was introduced (or re-introduced) in v4.18.0. Given that information, Commit efac31c7c57cb91ce586518b05172bab2e60fac6 is the likely culprit.
What is the desired behavior of the colorBy property? Do we set colorBy: [] to get a solid color? This appears to be the case until v4.18.0. Or do we set colorBy: ["solid"], or is it something else I haven't thought of?  If you can tell me what is supposed to be happening we may be able to fix it.

A short update: After forking Glance reverting the efac31c commit, the problem is solved for us. However, I assume the commit was made for a reason, and without knowing what your goal was we aren't able to contribute a fix.


Handling Dynamic Locators

How to handle Dynamic locators??
For E.g //input[contains(text()='sometext')] where sometext must be replaced by a certain value.
As in Site prism it returns CapybaraNodeElements, should I define these kind of xpaths as string in Locators section?

If you want something dynamic then you'd need to define the dynamic value before runtime.
SitePrism metaprograms in the values at runtime. So you need the values before runtime.
If you want to define the values POST runtime, you would need to run the class methods for the DSL creation. However you're very much on your own if you do this.


About license

Thanks for the great work! The project is released under an MIT license. I want to know whether that means the pre-trained models are also released under the MIT license? Thanks.

Yes. The pre-trained models are also released under the MIT license. Thank you.

Many thanks for the fast reply.


Fixed memory issue where NSURLSessionConfiguration was never retained

This PR fixes a memory issue on macOS / iOS. The sessionConfiguration object is now retained in the naettInit function.
Note, since there is currently no deinit function in the naett library, the single sessionConfiguration object created during naettInit is never released.

Awesome, thanks!


Manifest deletion can leave dangling tag links

Deleting a manifest by digest such as DELETE /v2/repo/manifests/sha256:7bf65d... can successfully delete the manifest but leave invalid tags linking to it if the client times out the request.
Version:
registry github.com/docker/distribution v2.7.1 using the s3 storage driver (I think this happens with all storage drivers).
Steps to reproduce

Create a repository with a lot of tags pointing to the same manifest.
Delete a revision in that repository using a short client timeout. I've seen this happen in production at 30 seconds.

What I expect
Either all tags and the manifest deleted, or if not all tags were deleted then the manifest to remain.
What happened
The manifest and some tags were deleted, but other tags were left pointing to the deleted manifest.
Diagnosis
I think this is in the DeleteManifest handler.
https://github.com/docker/distribution/blob/244d5246c2f193d50b2f8fd220784958a5e1318b/registry/handlers/manifests.go#L485
The manifest is deleted and then tags pointing to that manifest are listed and removed. If the client times out while the tags are being listed and removed then the context will cancel and registry will leave invalid tags. Also if any storage error happens when deleting a tag then the remaining tags will be left.
I think the manifest should be deleted after all tags have been successfully deleted.

On the other hand, changing the order of operations opens the door for a push of a new tag using the same manifest during the deletion to succeed but then for the deletion to delete the manifest, again leaving a dangling tag.

I'm facing the same issue and made some tests locally with version v2.7.1 (2461543d).
I added few debugging Println to the handler to see what is happening  and when the context is cancelled.
I created an image with about 600 tags and then deleted it using a http request from a Go program that quickly cancels the request.
I wasn't able to reproduce the issue locally, my log showed me that even though the context was canceled just before the handler tries to fetch the list of tags (tagService.Lookup), It still removed all of them.
I tried to look in the code to see where the context was used, and it always leads to the functions of the S3 driver that are actually just ignoring it.
So I think the context is not the issue here, but I notice that the handler will stop removing the tags as soon as there is an error leaving the other ones here, broken.
As you said removing the tags first and then the manifest can lead to a race condition but I see a two way to mitigate this issue:
The first one would be to try to remove all the tags even if one deletion fails. This could reduce the impact of the issue but will probably not completely fix it.
Another solution would be to just add an endpoint the remove a tag (Untag), this would allow us to remove the tags we don't want and then just run the garbage collector with --delete-untagged=true to remove the manifest. This solution would avoid race conditions and as a bonus would allow people to remove only one tag instead the image and all its tags.

There are unexposed methods in distribution to handle untagging, it's not an unreasonably large change to enable this (icr.io supports it and is based on docker/distribution).
I think your suggestion for continuing on errors is worth doing. It does still leave small holes but is probably as good as we can get given the current design and the scaling requirements.


successRedirect type is not required but throw error if undefined

I know that I can use a try/catch but this seems a incorrect behavior

Can you show a full example of your implementation?
successRedirect it's required for the Strategy to properly work. It will redirect you to the provided validate route / form.
You will get that error if not provided.
Please, check the documentation and feel free to follow the Example Code implementation.
You should not get any kind of error when implemented correctly.

About the type, I think you are right.
Will be fixed soon.

Nothing else to say @siimaoo ?
Thread gonna be removed in the next hours.
Feel free to ask anything else.


libmem: implement policy-agnostic memory allocation/accounting.

This patch series

implements a  policy-agnostic library for memory allocation/accounting
replaces existing memory accounting in the topology-aware policy with libmem
plugs in libmem-based memory accounting and allocation to the balloons policy

For a more detailed description of the main ideas, core concepts, and some high level
implementation details, see the included package documentation.
TODO items:

[x] get #329 merged then rebase
[x] add missing ensureNormalMemory() during initial zone selection
[x] allow for both strict and preferred memory type selection
[x] add an interface for overriding builtin zone expansion and overflow resolution
[x] make sure memory type preference is consistently either a preference or a requirement
[x] add a description of how the allocator works/describe the basic idea
[x] comment/document zone expansion, zone overflow resolution
[x] clean up debug-logging to be actually helpful

A few remaining questions related to this initial implementation:

Should we allow more granular prioritization than the current QoS class/Preserving/Reservation mapped to Inertia ?
Are the builtin defaults good enough ?

@klihub, I'm testing this PR with the topmost (e2e) commit in https://github.com/askervin/nri-plugins/commits/5Wj_libmem_debug/
It introduces a topology with DRAM, HBM and PMEM memories detected. (I also considered adding memory-less CPU-only nodes, but didn't do it yet. Let me know if you'd like to include that as well to the topology...)
Launching
.../test/e2e$ ./run_tests.sh policies.test-suite/balloons/n6-hbm-cxl/test01-memory-types/

produces "insufficient available memory" prints in the balloons log:
E: [           policy           ] allocMem: falling back to nodes{1}, failed to allocate memory for kube-system/kube-scheduler-n6-hbm-cxl-generic-fedora37-containerd/kube-scheduler: libmem: insufficient available memory: failed to reallocate, can't find new DRAM nodes

Nevertheless pinned memory zones look good to me.

@klihub, I'm testing this PR with the topmost (e2e) commit in https://github.com/askervin/nri-plugins/commits/5Wj_libmem_debug/
It introduces a topology with DRAM, HBM and PMEM memories detected. (I also considered adding memory-less CPU-only nodes, but didn't do it yet. Let me know if you'd like to include that as well to the topology...)
Launching
.../test/e2e$ ./run_tests.sh policies.test-suite/balloons/n6-hbm-cxl/test01-memory-types/

produces "insufficient available memory" prints in the balloons log:
E: [           policy           ] allocMem: falling back to nodes{1}, failed to allocate memory for kube-system/kube-scheduler-n6-hbm-cxl-generic-fedora37-containerd/kube-scheduler: libmem: insufficient available memory: failed to reallocate, can't find new DRAM nodes

Nevertheless pinned memory zones look good to me.

I'll pull in those tests and see if I can dig out from the logs/debugging what goes wrong...

Nevertheless pinned memory zones look good to me.

That's just because the fallback code paths for failure are not totally insane... but that's nothing to write home about.
I'll pull in those tests and see if I can dig out from the logs/debugging what goes wrong...

Okay, so I think this is a typical the left Dr. Jekyll does not know/remember how the right Mr. Hyde intended the Realloc() API to be used. When updating pinning we now always call Realloc() from balloons regardless of whether anything (in CPU pinning) has changed. But Realloc() does not really expect this to happen and always tries to force expansion... which can fails if we we run out of suitable nodes. Updating Realloc() to accomodate for such calls gets rid of the errors.
BTW, the test cases should use MEMLIM instead of MEMREQ... MEMREQ still can't be recovered with acceptable granularity (mapped to a range of something like [-2000, 2000] which is lacking way too many bits).

LGTM.
Thank you for this huge work, @klihub!
I think we should take it in and start developing on top of it.

Yeah, I tend to think so, too. Then we'll need to fix bugs and polish the turd further as we go. I'm just unable to focus enough to get this into any better shape now.


Create 10_chatgpt_prompt_table.tag

Save you ChatGPT chat in a excel table.
TagUI is the hand,ChatGPT is the brain,it's really nice thing!

Hi @Formyselfonly thank you so much for raising this PR! Appreciate this very much. This is now merged. Sorry I merge too quickly and it defaults as Squash merge. I would prefer merge commits so we can see the 4 individual commits in the history.


Menu updates!

From swstim on April 18, 2010 05:20:28
There's a lot of new SWS features, and the old "Extensions" menu is getting
long in the tooth.  I think the menu should be totally restructured to
reflect the best and most usable features.
If anyone has any ideas about menuing, please comment!
Original issue: http://code.google.com/p/sws-extension/issues/detail?id=119

Out of date.


[BUG] Browser not launching from another file/func with await outside handler.js

Hi @Sparticuz ,
Thanks for this great package, i'm going through some issues about launching browser from another file.
When i try to run the browser from hanlder.js it works fine, but when i try to open from another file/function with await, it doesn't launch, the same code works fine locally with Chromium
here is the code which is working.
const puppeteer = require("puppeteer-core");
const chromium = require("@sparticuz/chromium");

module.exports.handler = async () => {
    try {
        const browser = await puppeteer.launch({
            args: chromium.args,
            defaultViewport: chromium.defaultViewport,
            executablePath: await chromium.executablePath(),
            headless: chromium.headless,
            ignoreHTTPSErrors: true,
        });
        const page = await browser.newPage();

        await page.goto("https://react.dev/", { waitUntil: "networkidle0" });

        console.log("Chromium:", await browser.version());
        console.log("Page Title:", await page.title());

        await page.close();

        await browser.close();
    } catch (error) {
        throw new Error(error.message);
    }
};

here is the code which is not working.
const { runBrowser } = require('./index.js');

module.exports.handler = async (event) => {
    try {
        await runBrowser();
        console.log('cron running')
    } catch (error) {
        console.error('Error:', error);
        // ...
    }
};

// index.js and running from ./browser.js
const runBrowser = async () => {
    await browser.start();
}

// browser.js
const start = async () => {
try {
        const browser = await puppeteer.launch({
            args: chromium.args,
            defaultViewport: chromium.defaultViewport,
            executablePath: await chromium.executablePath(),
            headless: chromium.headless,
            ignoreHTTPSErrors: true,
        });

        const page = await browser.newPage();

        await page.goto("https://react.dev/", { waitUntil: "networkidle0" });

        console.log("Chromium:", await browser.version());
        console.log("Page Title:", await page.title());

        await page.close();

        await browser.close();
    } catch (error) {
        throw new Error(error.message);
    }

}

I've run into issues like this before also. My only guess is that maybe the promise is fulfilled when the browser is started, but not ready? No idea. I just have the browser started in the main handler, then I use functions to run whatever else needs to run.


Graal updates

Please have a look at the individual commit messages for the details.

Note that this will not yet make ORT build as a Graal native-image (again) yet due to https://github.com/oracle/graal/issues/2008.


Android should use the actual name of the project when referring to a Flutter app

When Flutter crashes on an Android device, it says Error on device: Unfortunately, Sky Shell has stopped. Although it would be an improvement to use Flutter Shell instead of Sky Shell, it would be better if the APK included the real name of the project so that end users can tell which app crashed.

I would expect it to use the correct name if you have an android/AndroidManifest.xml file.  The prebuilt Sky Shell of course has its own name.  But as soon as you have an AndroidManifest.xml file we build a custom one iirc.  @jason-simmons or @mpcomplete would know.

Yep, it will use the name from AndroidManifest.xml.

flutter create now includes an android/AndroidManifest.xml file by default, so it's possible we should even remove the pre-built path these days since it should not be common to hit that.

I confirmed that the name shown is based on android/AndroidManifest.xml, so that looks good. @eseidelGoogle, I'm not sure if there's still action required based on your comment, but I'm happy with how it currently works.


Time in words clock

Happened to be awake at midnight to notice that the clock says noon lol

Oh, probably the timezone was incorrect. It  was displaying the time AM where it should be PM.
When is 0 hour, it shows midnight, take a look:
https://github.com/jnthas/cw-cf-0x02/blob/18d4cd9a08146c1725bee974c7b01e070ea6df01/DateI18nEN.h#L49C1-L50C1

Thanks for looking into it. Do I need to do anything to fix it or is it auto updated? No big deal either way as it wasn't a bothersome thing.

Did you set your timezone on the settings page? If it's correct, it should do it automatically. Also, try to check the 'Use 24h format' also in the settings page

The timezone was set correctly upon first install to show the correct time. I use 12-hour format as I'm not interested in the 24hour clock. I'll go into the settings and just restart the clock and I'll see tonight at midnight if it is displayed correctly and report back if it isn't. Thanks

So it's been a few days, first couple of days I forgot and fell asleep but was able to see tonight that it's still showing noon. I check all my settings and everything is set correct. So was the code corrected? Should I format and reinstall the clock? Or does it need to be first? Just for the record, I know how to install it and understand a bit of the code, but I am still in kindergarten when it comes to my level in understanding all of it. Thanks!


Fix sass typo

Sass module are included with @import statements, not @include.

Missed that, thanks!


Change Favicon

@luigicr18 it looks like the favicon is still the old one. You can switch it to the new one we used in the dev site.
Currently:

Change to:

Hello guys
Working good on: https://luigicr18.github.io/seesawlabs.github.io/

Thanks

This looks good, but the correct favicon was on the dev site already, so just make sure that it transfers over to the new site when you push changes @luigicr18


Implementation Of The Single Proposal Consultation For A Member

Add of a UrlManager rule in config/web.
Creation of 2 methods :
1 to check if the proposal requested exists.
1 to check if the requester is the owner of the proposal.

Look at the video to see the feature with at least 1 old content for a proposal.


Fix #376

We should only show the option to delete if the user can delete. As it is now I have the option on every repo.