defmt-test: Exit with semihosting exit

This PR makes probe-rs detect exit as successfully. Basically the same as https://github.com/knurling-rs/app-template/pull/71.

LGTM. Can you post a log from a test run?

probe-run does print ERROR the program panicked instead of Error: CPU halted unexpectedly.. Which I think is better. But I feel this is a separate topic of "Make probe-rs detect panics".

@jonathanpallant Can I merge?

I have to say that the probe-run backtrace actually looks better.
probe-run:
ERROR panicked at src/lib.rs:25:5:
OMG!!!
└─ panic_probe::print_defmt::print @ /home/urhengulas/.cargo/git/checkouts/defmt-7f5b74b4e6ff55d4/e36e12a/firmware/panic-probe/src/lib.rs:104
────────────────────────────────────────────────────────────────────────────────
stack backtrace:
   0: HardFaultTrampoline
      <exception entry>
   1: lib::inline::__udf
        at ./asm/inline.rs:181:5
   2: __udf
        at ./asm/lib.rs:51:17
   3: cortex_m::asm::udf
        at /home/urhengulas/.cargo/registry/src/index.crates.io-6f17d22bba15001f/cortex-m-0.7.7/src/asm.rs:43:5
   4: panic_probe::hard_fault
        at /home/urhengulas/.cargo/git/checkouts/defmt-7f5b74b4e6ff55d4/e36e12a/firmware/panic-probe/src/lib.rs:86:5
   5: rust_begin_unwind
        at /home/urhengulas/.cargo/git/checkouts/defmt-7f5b74b4e6ff55d4/e36e12a/firmware/panic-probe/src/lib.rs:54:9
   6: core::panicking::panic_fmt
        at /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/core/src/panicking.rs:67:14
   7: krate::abc
        at src/lib.rs:25:5
   8: main
        at tests/integration.rs:8:1
   9: Reset
(HOST) ERROR the program panicked

probe-rs
ERROR panicked at src/lib.rs:25:5:
OMG!!!
└─ panic_probe::print_defmt::print @ /home/urhengulas/.cargo/git/checkouts/defmt-7f5b74b4e6ff55d4/e36e12a/firmware/panic-probe/src/lib.rs:104
Frame 0: exp_u128 @ 0x00001bfc
Frame 1: __udf @ 0x00000b8c inline
       ./asm/lib.rs:48:1
Frame 2: __udf @ 0x0000000000000b8c
       ./asm/lib.rs:51:17
Frame 3: udf @ 0x00000410 inline
       /home/urhengulas/.cargo/registry/src/index.crates.io-6f17d22bba15001f/cortex-m-0.7.7/src/asm.rs:43:5
Frame 4: hard_fault @ 0x000000000000040c
       /home/urhengulas/.cargo/git/checkouts/defmt-7f5b74b4e6ff55d4/e36e12a/firmware/panic-probe/src/lib.rs:86:5
Frame 5: panic @ 0x000003f6
       /home/urhengulas/.cargo/git/checkouts/defmt-7f5b74b4e6ff55d4/e36e12a/firmware/panic-probe/src/lib.rs:54:9
Frame 6: exp_u128 @ 0x00000d1a
       /rustc/cc66ad468955717ab92600c770da8c1601a4ff33/library/core/src/num/bignum.rs:195:17
Frame 7: abc @ 0x00000372
       /home/urhengulas/Documents/github.com/knurling-rs/krate/src/lib.rs:25:5
Frame 8: __defmt_test_entry @ 0x000002ac
       /home/urhengulas/Documents/github.com/knurling-rs/krate/tests/integration.rs:8:1
Frame 9: fmt @ 0x0000013c
Frame 10: fmt @ 0x0000013c
Error: CPU halted unexpectedly.

@jonathanpallant Can I merge?

I will just go ahead.


i want to add bubble, selection and insertion sort in java.

Please include a small description or summary of the issue here.
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Additional context
Add any other context or screenshots about the feature request here.
Languages

[ ] Python
[ ] Java
[ ] C
[ ] C++

please assign me this

@manviiguptaa assigned to add selection and insertion sort in Java


Duplicated completion items

Applies To

[x] Notebooks (.ipynb files)
[x] Interactive Window and/or Cell Scripts (.py files with #%% markers)

What happened?

repro steps

create a cell
type import os
run the cell
create a cell after the first cell
type os. <= completion here

repro for both notebook and interactive window
VS Code Version
1.94.2
Jupyter Extension Version
v2024.10.2024100401
Jupyter logs
No response
Coding Language and Runtime Version
No response
Language Extension Version (if applicable)
No response
Anaconda Version (if applicable)
No response
Running Jupyter locally or remotely?
None

@heejaechang I do not see any duplicates in the screenshot

@rchiodo Is it fixed in v2024.11.2?

The fix for this wouldn't be in Pylance. It would be in the jupyter extension.

I had tried the Jupyter v2024.11.2024102401 (pre-release), issue still.

I'm using 2024.11.2024111901 and it doesn't seem to repro for me:

@rchiodo I found it depends on Python version, I can reproduce on 3.10.12, could you try it?

You might be on VS code stable. I'm using VS code insiders. Jupyter may have updated their required VS code version so the latest only works on insiders.
I can repro with Python 3.10 too:

@DonJayamanne you may need something different based on the results returned from ipykernel. Older versions must have had different completions.

Steps to repro

Install Python 3.10
Install pylance
Install the latest version of ipykernel
Run a cell containing the text import os
In the next cell type the text os.path.abs at this point we should get completions for abspath and there should be just one item, instead of two.

@rchiodo Found that the label * abspath is what was causing the issue, I.e. the prefix *
Hopefully the new fix should work.


Add documentation for commenting

Developer facing documentation around integrating custom widgets has been left for now, as we should create more public utility functions for the commenting API and stabilize it before documenting it.

question: given our slow move to using Markdown in docs, does it make sense to add new documentation in reStructuredText ?


.NET sample code generates proxy-related error response

Expected Behaviour
The sample code is supposed to build a JWT object and then pass it in an Adobe API call to get back an "access token".
Actual Behaviour
Such API calls are failing with a response.ErrorMessage of "The remote server returned an error: (407) Proxy Authentication Required."
However, from that error message, I can't tell if the "remote server" is referring to the ims-na1.adobelogin.com site (to which I'm sending the request) or if it's referring to some proxy server of my own company (which might be blocking the request before it even leaves my company's internal network).
Reproduce Scenario (including but not limited to)
Use the sample code to make the API call.
NOTE:  I successfully get an Access Token when I copy-paste my Adobe API Project's private key into the GUI box provided for such testing at https://developer.adobe.com/console/projects/374378/4566206088344859311/apis/AdobeIOManagementAPISDK/details.
Steps to Reproduce

Prepare the requisite Adobe API "Project" (e.g., https://developer.adobe.com/console/projects/374378/4566206088344859311/overview)
Use that project to provide the necessary arguments for (using the sample code to make a) REST API call ... leveraging an older version of the RestSharp open source library (e.g., v106.13.0) due to another issue (https://github.com/AdobeDocs/adobe-dev-console/issues/50)

Platform and Version
Windows 10 running Microsoft Visual Studio 2019.
Sample Code that illustrates the problem
Current code leveraging an older version of the RestSharp library (e.g., v106.13.0).
Logs taken while reproducing problem
n/a

I was able to resolve this issue by adding the following additional code:
            const string proxyAddress = "http://proxy.jpmchase.net:8443";
...and then changing this existing code:
var client = new RestClient("https://ims-na1.adobelogin.com/ims/exchange/jwt/");
...to this instead:
var client = new RestClient("https://ims-na1.adobelogin.com/ims/exchange/jwt/")
{
Proxy = new WebProxy(proxyAddress)
};
Since most companies (and surely all large companies) have a proxy server, I strongly recommend you add such code to your sample code (after changing the JPMC-specific proxy server address to something generic, obviously).

Hello, seems like this issue relates to sample code provided for the deprecated Service Account (JWT) credentials. We are no longer enhancing the documentation surrounding the deprecated credentials.


Error importing custom control -- index.ts is not a module

Unable to build the project due to the following import errors.
[12:27:29] Error - [tsc] src/controls/PropertyPaneContinentSelector/PropertyPaneContentSelector.ts(14,8): error TS2306: File '.../HelloWorldWP-new/src/controls/PropertyPaneContinentSelector/index.ts' is not a module.
[12:27:29] Error - [tsc] src/webparts/helloWorld/HelloWorldWebPart.ts(22,8): error TS2306: File '.../HelloWorldWP-new/src/controls/PropertyPaneContinentSelector/index.ts' is not a module.
[12:27:29] Error - 'tsc' sub task errored after 5.74 s
exited with code 2
Note that when hovering over the import path './' the word 'index' is appended.

My bad. Not all opened files had been saved. :$
And thanks very much for these updated tutorials!


Support prometheus emitter

Description
modify helm chart to support scraping from prometheus automatically
Relates to Issue 13530
prometheus emitter metric is scraped by prometheus

Key changed/added classes in this PR

change helm chart

add pods annotation
expose port to scrap from prometheus

This PR has:

[x] been self-reviewed.

[ ] using the concurrency checklist (Remove this item if the PR doesn't have any relation to concurrency.)

[ ] added documentation for new or modified features or behaviors.
[ ] a release note entry in the PR description.
[ ] added Javadocs for most classes and all non-trivial methods. Linked related entities via Javadoc links.
[ ] added or updated version, license, or notice information in licenses.yaml
[ ] added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
[ ] added unit tests or modified existing tests to cover new code paths, ensuring the threshold for code coverage is met.
[ ] added integration tests.
[ ] been tested in a test Druid cluster.

@kfaraz
Is there something wrong or needs to be corrected?
plz check this

Hi, @jaegwonseo , thanks for your patience! We have been a little occupied with the upcoming release of Druid 25. I will try to get this reviewed soon.

@jaegwonseo - The changes look good to me. can you resolve the conflicts so I can merge this PR?

@abhishekagarwal87 i resolve conflict. plz check this

@abhishekagarwal87
i just change k8s config
is it related with this error? build fail link

I will merge this soon.

thank you @jaegwonseo for your contribution.


feat(release): Update SDK to support VPC API generated on 2022-07-12

Signed-off-by: Deepak Selvakumar<EMAIL_ADDRESS>Finished tests in 1.863522s, 155.0827 tests/s, 125.0321 assertions/s.
Slowest tests:
0.041123s test_list_vpn_servers#VpcV1Test
0.040365s test_create_load_balancer_pool_member#VpcV1Test
0.037274s test_update_load_balancer_listener_policy_rule#VpcV1Test
0.027857s test_list_subnets#VpcV1Test
0.021277s test_get_vpn_server_client#VpcV1Test
0.019260s test_list_vpc_routing_table_routes#VpcV1Test
0.011762s test_list_backup_policy_plans#VpcV1Test
0.011162s test_update_image#VpcV1Test
0.010869s test_delete_load_balancer_listener_policy#VpcV1Test
0.010401s test_remove_vpn_gateway_connection_peer_cidr#VpcV1Test
289 tests, 233 assertions, 0 failures, 0 errors, 0 skips
Finished in 1.86440s
289 tests, 233 assertions, 0 failures, 0 errors, 0 skips
Writing HTML reports to /Users/deepakselvakumar/Documents/GitHub/Public/vpc-ruby-sdk/test/html_reports
Coverage report generated for Minitest to /Users/deepakselvakumar/Documents/GitHub/Public/vpc-ruby-sdk/coverage. 3558 / 3855 LOC (92.3%) covered.
/usr/local/Cellar/ruby/3.0.3/bin/ruby -w -I"lib:test" -I"/usr/local/lib/ruby/gems/3.0.0/gems/rake-12.3.3/lib" "/usr/local/lib/ruby/gems/3.0.0/gems/rake-12.3.3/lib/rake/rake_test_loader.rb" "test/integration/vpc_v1.rb"
Running tests with run options --seed 14835:
Started with run options --seed 14835
Emptying /Users/deepakselvakumar/Documents/GitHub/Public/vpc-ruby-sdk/test/html_reports
VpcV1Test
S  test_missing_credentials_skip_integration                       SKIP (0.00s)
Finished tests in 0.001630s, 613.4968 tests/s, 0.0000 assertions/s.
Skipped:
VpcV1Test#test_missing_credentials_skip_integration [/Users/deepakselvakumar/Documents/GitHub/Public/vpc-ruby-sdk/test/integration/vpc_v1.rb:30]:
Skip VPC integration tests because credentials have not been provided
Slowest tests:
0.000055s test_missing_credentials_skip_integration#VpcV1Test
1 tests, 0 assertions, 0 failures, 0 errors, 1 skips
Finished in 0.00178s
1 tests, 0 assertions, 0 failures, 0 errors, 1 skips

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


Add category to warning

Background
For my project, I'm using rembg in order to remove background for images in a AWS lambda function. This library is using PyMatting to implement Alpha Matting which depends on numba. But, since _multiprocessing.SemLock is not implemented when running on AWS Lambda, I get a warning every time the lambda function runs. This pollutes the function logs
Workaround
Since

I cannot control what Amazon offers
I actually don't use Alpha Matting, so this warning is irrelevant for my use case

I would like to silence this specific warning using warnings.simplefilter
Solution
In order to support silencing this specific warning and not everything, I have added the category parameter to the warnings.warn call. Hopefully, this is the proper class for this warning, but if needed, another warning class can be added

Thanks for the patch, I'm not sure about the use of NumbaParallelSafetyWarning, its intended use is for warning about problems that might occur in a parallel region, e.g. race conditions. https://github.com/numba/numba/blob/a4664180ddc91e4c8a37dd06324f4e229a76df91/numba/core/errors.py#L62-L66
This does make me wonder if there is a more appropriate warning than just the standard NumbaWarning and I'm not sure there is. Use of this "base class" of warning would probably help a warnings filter, but the regex string match on the message would also need to be used (such a regex match might also work against the existing code base too?). Would changing the warning type to that still help with your use case @kkokkoros ?

Hello @stuartarchibald and thanks for the quick review!

Would changing the warning type to that still help with your use case @kkokkoros

Yes of course it would, I just couldn't think of any good name since I don't have much experience with numba internals. If you can propose a better name, I could add a new NumbaWarning subclass

Hello @stuartarchibald and thanks for the quick review!

Would changing the warning type to that still help with your use case @kkokkoros

Yes of course it would, I just couldn't think of any good name since I don't have much experience with numba internals. If you can propose a better name, I could add a new NumbaWarning subclass

How about adding a class NumbaSystemWarning to numba.core.errors and then using that in the warning category? There's numerous warning classes defined in that module already for reference. Thanks!


authorize not returning succes nor failure

Description:
In the completion handler, neither .success nor .failure is being run. The app redirects correctly to the callback URL with all the tokens in the url.
let oauthswift = OAuth2Swift(
    consumerKey:    "4556fff9f1404f0a8aeb3b0944a0f512",
    consumerSecret: "125742a471294976bd01d794031b1a6b",
    authorizeUrl:   "https://accounts.spotify.com/en/authorize",
    responseType:   "token"
)
self.oauthswift = oauthswift

var loginView = (NSStoryboard(name: "Main", bundle: nil).instantiateController(withIdentifier: "SpotifyLoginVC") as? NSViewController)!
ShowPopover.showPopover(popView: loginView, mainView: statusBarItem.button!, behaviour: .transient, side: .maxY)
oauthswift.authorizeURLHandler = loginView as! OAuthSwiftURLHandlerType

let handle = oauthswift.authorize(
    withCallbackURL: URL(string: "https://zandew.github.io/")!,
    scope: "user-library-modify",
    state:"test12345") { result in
        switch result {
        case .success(let (credential, response, parameters)):
            print("SUCCESS")
        case .failure(let error):
            print("FAIL")
    }
}

Also, is there a better way then instantiate the loginView? If I do oauthswift.authorizeURLHandler = loginView(), the webView becomes nil.
This is the view controller with the webkit
class SpotifyLoginVC: NSViewController, OAuthSwiftURLHandlerType {

    @IBOutlet weak var webView: WKWebView!

    override func viewDidLoad() {
        super.viewDidLoad()
        // Do view setup here.
    }

    func handle(_ myURL: URL) {
        let req: URLRequest = URLRequest(url: myURL)
        self.webView.load(req)
    }

}

OAuth Provider? (Twitter, Github, ..):
OAuth Version:

[ ] Version 1
[x ] Version 2

OS (Please fill the version) :

[] iOS :
[x ] OSX :
[ ] TVOS :
[ ] WatchOS  :

Installation method:

[ ] Carthage
[x ] CocoaPods
[ ] Swift Package Manager
[ ] Manually

Library version:

[ x] head
[ ] v2.1.0
[ ] v2.0.0
[ ] v1.4.1
[ ] other: (Please fill in the version you are using.)

Xcode version:

[] 11.4 (Swift 5.2)

[ ] 11.x (Swift 5.1)

[ ] 10.x (Swift 5.0)

[ x] other: (Please fill in the version you are using.)
Xcode 11.5

[ x] objective c

its nil because this not yet loaded. It must be presented OR you have create the link with the outlet in storyboard

What do you mean by the code I used to manage my personal website? In this project, I don't reference it anywhere else.

So why did you put this website as callback url?
The callback url is used to return you the oquth token; so the provider will call this url and you must call handle function with it
You can use url scheme as explained in readme or wiki OR you have a web view and a delegate to monitor all url browsed in webview
See demo app

I am trying to implement the webview method, is the handle function you are talking about the one I created in SpotifyLoginVC?

I got what I wanted using this tutorial http://fusionblender.net/build-macos-app-spotify-connectivity-swift/, but neither of the cases are still being run.

A lot of code for nothing in this tutorial... but if it could help

thanks for the heads up, i'm currently slowly but surely removing all the unnecessary bits


Migrate from godep to modules and bump k8s version to 1.14

This PR migrates the dependency management system from godep to modules and bumps the k8s version to 1.14.
Kubernetes is now using modules. See this k8s KEP. NPD is still using vendoring with modules.
The side effect of using golang modules is that it requires go 1.11+ to build node-problem-detector afterwards.

Still work in progress.

This is ready for review.
/assign @andyxning
/assign @Random-Liu

/retest pull-npd-test

/cc @xueweiz

/test pull-npd-test

/retest

Note that I didn't bump versions of the following:
	k8s.io/api v0.0.0-20180127130940-acf347b865f2
	k8s.io/apimachinery v0.0.0-20180126010752-19e3f5aa3adc
	k8s.io/client-go v0.0.0-20180103015815-9389c055a838
	k8s.io/heapster v0.0.0-20180704153620-b25f8a16208f

I tried to bump their versions to latest. But it seems that make test will complain. I dig deeper and it is actually go vet's problem. Somehow go vet tries to check the imported vendor code, which I thought it should not do. I spent some time on it, but didn't figure out a workaround. I decide it does not worth more time to bump those packages, because they work fine now. We can look into them later when needed.

/lgtm

/test pull-npd-test

Seems flakes.
/test pull-npd-test


AppBar brightness: Brightness.light won't change status bar's color on iOS dark mode

My app's AppBar has a white background. When on Dark Theme in iOS, after settings brightness: Brightness.light, the status bar's text won't change color and will stand white.
The print below shows the white text over the white AppBar

Should I change the app's color scheme to fit iOS' Dark Theme or is this a legit bug?

flutter doctor -v

[✓] Flutter (Channel master, v1.10.6-pre.49, on Mac OS X 10.14.6 18G95, locale pt-BR)
    • Flutter version 1.10.6-pre.49 at /Volumes/Repos/flutter
    • Framework revision 81e693a7fe (4 hours ago), 2019-09-24 12:38:45 -0700
    • Engine revision b875c7a5ff
    • Dart version 2.6.0 (build 2.6.0-dev.0.0 7c1821c4aa)

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
    • Android SDK at /Users/edgar/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-29, build-tools 29.0.2
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.0)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.0, Build version 11A420a
    • CocoaPods version 1.7.5

[!] Android Studio (version 3.5)
    • Android Studio at /Applications/Android Studio.app/Contents
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)

[✓] VS Code (version 1.38.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.4.1

[✓] Connected device (1 available)
    • iPhone de Edgar • 00008020-000D54182E90003A • ios • iOS 13.1

! Doctor found issues in 1 category.

Duplicate of #41067

Thanks! - Closing as duplicate of #41067


Background Image is repeative.

assign me

Hey, @SauravMukherjee44 Background image is repeating.

Have a look.

Hey, @SauravMukherjee44 Yeah image is not repeating but the footer is not at the bottom.


match progress indicator for android and iOS

a quick patch for matching output of the progress indicator for Android and iOS

LGTM


Silence TSAN w.r.t. SCHEDULER pointer on shutdown

Scope & Purpose
This is a backport of https://github.com/arangodb/arangodb/pull/20056 .
This addresses https://arangodb.atlassian.net/browse/BTS-1671.
It is to silence TSAN in some shutdown cases in RTA.
There is a global pointer called SchedulerFeature::SCHEDULER. On
shutdown, we set this pointer to nullptr in the
SchedulerFeature::unprepare method. In various other places, we read out
the pointer.
The logic of ApplicationFeatures should ensure that nobody will read
the pointer out after the SchedulerFeature has run its unprepare
method. Sometimes the TSAN sanitizer cannot recognize this indirect
synchronization and complains about reads that have happened before the
write there, but are not officially inter-thread synchronized. We use
atomic references in some places to silence TSAN.

[*] :hankey: Bugfix

Checklist

[*] :book: CHANGELOG entry made
[*] Backports

[*] Backport for 3.11: This is it.

Related Information

[*] GitHub issue / Jira ticket: https://arangodb.atlassian.net/browse/BTS-1671
[*] Devel PR: https://github.com/arangodb/arangodb/pull/20056

[x] https://jenkins.arangodb.biz/view/PR/job/arangodb-matrix-pr/32032/


[Bug] Classes incorrectly fail to fulfill requirements.

Observed Behavior
Courses that should fulfill certain requirements fail to do so. Specifically, Government courses that are listed as successfully fulfilling a requirement do not add to the total number of fulfilled requirements and additionally is not automatically categorized into Completed Requirements.
A screenshot is attached below. Courseplan correctly identifies the courses as being able to fulfill the requirement, however, does not correctly add to the number of total Introductory Government Courses.
Additionally, the credits from Phil 1950 are not added to the total credits of Government Coursework.

Expected Behavior
Introductory Government Courses should have its total requirements at 2/2. Additionally, it should be located in Completed Requirements rather than Ongoing Requirements.
Credits towards Government Coursework should be at 4/28.
Steps to Reproduce
Add a Government Major to your profile.
Add any class that fulfills the Introductory Government Courses requirement.
This issue report was made on Monday Jan 23 at 3:55 PM, however, has been an ongoing issue for a few days now.

Thanks for bringing this to our attention! This is likely caused by a known issue where we calculate requirement fulfillment too conservatively. Essentially, if a course can fulfill multiple requirements, we are unsure which to choose and decide it counts for nothing. A fix is in progress and should be released within the coming month.

This seems to actually just be an issue with my account. Trying it on a friend's account seems to work. My entire Courseplan is actually bugged, it seems. My progress is not saved after leaving or reloading the page, and nothing is correctly added to credit counts. This seems to have been caused by removing a major. I've just added back the old major and most of my problems seem to have been fixed. I will open a new Issue regarding this larger problem later.


Improve StatusBar/Header Behavior

Replaces #2629.
Motivation
While working on adding support for iPhoneX/iOS11 I saw incorrect behavior with the header. Currently, when a device goes to landscape mode the status bar is hidden (as expected) but the header component height stays the same. This can be seen in the following GIF.

Test Plan
Install react-navigation from spencercarli/react-navigation#improve-status-bar-behavior2 into the NavigationPlayground example and spin your device around. You should see the following behavior.

@dantman my guess is the fact that the navbar height on iphone should be different in landscape was previously simply ignored, maybe also because it wasn't that big of a problem, and maybe because someone knew that the old way it was implemented worked on the ipad.
Indeed, this is now a bug. Question is, should simply revert this commit for now, or try to fix this by finding some way of decreasing the height only when the status bar is hidden? I don't know an api which provides this information..?

@dantman my guess is the fact that the navbar height on iphone should be different in landscape was previously simply ignored, maybe also because it wasn't that big of a problem, and maybe because someone knew that the old way it was implemented worked on the ipad.

I do believe this is a permanent change for iOS 11. It's really inconsistent on when I get it before iOS 11, but I do sometimes get a visible status bar and a reported status bar height from iOS in landscape mode.
iPhone X - iOS 11:

iPhone 7 Plus - iOS 10:

iPhone 6 Plus - iOS 9:

@dantman sorry, I previously wrote "...navbar height on iphone should be different in landscape..." which is overly simplified. The accurate way to put it is "navbar height on iphone should be different under some conditions." Now, what are those conditions? THB, I'm not knowledgeable of native ios development so I'd appreciate if someone could shed some light on this (maybe it has to do with size classes?).
Now, my hypothesis is that the navbar height is smaller when the status bar is hidden, and greater when statusbar is shown (which is not the same as being/not being in landscape mode). Please correct if somebody thinks this is wrong. I'll try to find out in the mean time if that works.

I gave it a try, and it seems it'll work. I also noticed this PR in rn-core, so I'll try to write it in a way that will not require much editing when it is merged.

Now, my hypothesis is that the navbar height is smaller when the status bar is hidden, and greater when statusbar is shown (which is not the same as being/not being in landscape mode). Please correct me if somebody thinks this is wrong. I'll try to find out in the mean time if that works (it should, imo).

Yes, the statusbar height does accurately reflect whether the status bar is shown, baring rare API glitches. The key being that iOS has its own internal patterns for deciding whether it wants to show the status bar in landscape or not.
For example the status bar was hid most of the time when I opened the app and then rotated the simulator to landscape, but was visible most of the time if I opened the app while in landscape mode. There may be a bunch of different conditions based on things like what orientation you open the app in and whether the app was already running.


Recognize long comments.

If you write code like this:
/*
 * Blah blah 2.0
 *
 * Licensed under cake.
 */

It's converted to the following.
#
# * Blah blah 2.0
# *
# * Licensed under cake.
#

My proposal would be convert it to this, which doesn't have needless stars (and is specificially parsed by CoffeeScript 1.7.0 to create nice JavaScript output).
###
# Blah blah 2.0
#
# Licensed under cake.
###

fixed in v2.0.0


Using dynamic env launcher instead of pre build image

Remove make image stage, and use dynamic launcher for excalidraw.
The forked excalidraw feature is https://github.com/alswl/excalidraw/pull/5
The solution is

using window.env instead of process.env
using launcher.py to launch app, the Python script will update window.env values.

related to

https://github.com/alswl/excalidraw-collaboration/issues/7

block

https://github.com/alswl/excalidraw-collaboration/issues/32

Solve https://github.com/alswl/excalidraw-collaboration/issues/7
unblock  https://github.com/alswl/excalidraw-collaboration/issues/32


Update chartjs.component.ts

Fix docs as appropriate

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


No "exports" main defined in<EMAIL_ADDRESS>

We use typodoc inside docusaurus via https://github.com/milesj/docusaurus-plugin-typedoc-api, and the latest update of typedoc broke our pipelines, probably because of adoption of this new package. Did a quick search, and its most likely because that package is ESM, and I am honestly puzzled that you were previously depending on shiki which was also ESM, but typedoc is not, right? I checked the original shiki exports field but it looks quite similar, not sure what exactly this is about.
Error:  Error: Unable to build website for locale en.
    at tryToBuildLocale (/home/runner/work/mikro-orm/mikro-orm/docs/node_modules/@docusaurus/core/lib/commands/build/build.js:78:15)
    at async /home/runner/work/mikro-orm/mikro-orm/docs/node_modules/@docusaurus/core/lib/commands/build/build.js:34:9
    ... 4 lines matching cause stack trace ...
    at async file:///home/runner/work/mikro-orm/mikro-orm/docs/node_modules/@docusaurus/core/bin/docusaurus.mjs:44:3 {
  [cause]: Error: Docusaurus could not load module at path "/home/runner/work/mikro-orm/mikro-orm/docs/node_modules/docusaurus-plugin-typedoc-api/lib/index.js"
  Cause: No "exports" main defined in<EMAIL_ADDRESS>      at loadFreshModule (/home/runner/work/mikro-orm/mikro-orm/docs/node_modules/@docusaurus/utils/lib/moduleUtils.js:36:15)
      at normalizePluginConfig (/home/runner/work/mikro-orm/mikro-orm/docs/node_modules/@docusaurus/core/lib/server/plugins/configs.js:44:65)
      at /home/runner/work/mikro-orm/mikro-orm/docs/node_modules/@docusaurus/core/lib/server/plugins/configs.js:98:60
      at Array.map (<anonymous>)
      at loadPluginConfigs (/home/runner/work/mikro-orm/mikro-orm/docs/node_modules/@docusaurus/core/lib/server/plugins/configs.js:98:38)
      at async initPlugins (/home/runner/work/mikro-orm/mikro-orm/docs/node_modules/@docusaurus/core/lib/server/plugins/init.js:127:27)
      at async /home/runner/work/mikro-orm/mikro-orm/docs/node_modules/@docusaurus/core/lib/server/plugins/plugins.js:137:36
      at async loadSite (/home/runner/work/mikro-orm/mikro-orm/docs/node_modules/@docusaurus/core/lib/server/site.js:144:45)
      at async buildLocale (/home/runner/work/mikro-orm/mikro-orm/docs/node_modules/@docusaurus/core/lib/commands/build/buildLocale.js:28:18)
      at async runBuildLocaleTask (/home/runner/work/mikro-orm/mikro-orm/docs/node_modules/@docusaurus/core/lib/commands/build/build.js:93:5)
      at async /home/runner/work/mikro-orm/mikro-orm/docs/node_modules/@docusaurus/core/lib/commands/build/build.js:74:13
      at async tryToBuildLocale (/home/runner/work/mikro-orm/mikro-orm/docs/node_modules/@docusaurus/core/lib/commands/build/build.js:70:9)
      at async /home/runner/work/mikro-orm/mikro-orm/docs/node_modules/@docusaurus/core/lib/commands/build/build.js:34:9
      at async mapAsyncSequential (/home/runner/work/mikro-orm/mikro-orm/docs/node_modules/@docusaurus/utils/lib/jsUtils.js:21:24)
      at async Command.build (/home/runner/work/mikro-orm/mikro-orm/docs/node_modules/@docusaurus/core/lib/commands/build/build.js:[33](https://github.com/mikro-orm/mikro-orm/actions/runs/12075851011/job/33676312701?pr=6259#step:9:38):5)
      at async Promise.all (index 0)
      at async runCLI (/home/runner/work/mikro-orm/mikro-orm/docs/node_modules/@docusaurus/core/lib/commands/cli.js:56:5)
      at async file:///home/runner/work/mikro-orm/mikro-orm/docs/node_modules/@docusaurus/core/bin/docusaurus.mjs:44:3 {
    [cause]: Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: No "exports" main defined in<EMAIL_ADDRESS>        at exportsNotFound (node:internal/modules/esm/resolve:296:10)
        at packageExportsResolve (node:internal/modules/esm/resolve:586:13)
        at resolveExports (node:internal/modules/cjs/loader:640:36)
        at Function._findPath (node:internal/modules/cjs/loader:748:31)
        at Function._resolveFilename (node:internal/modules/cjs/loader:12[35](https://github.com/mikro-orm/mikro-orm/actions/runs/12075851011/job/33676312701?pr=6259#step:9:40):27)
        at Function.resolve (node:internal/modules/helpers:151:19)
        at _resolve (/home/runner/work/mikro-orm/mikro-orm/docs/node_modules/jiti/dist/jiti.js:1:241814)
        at jiti (/home/runner/work/mikro-orm/mikro-orm/docs/node_modules/jiti/dist/jiti.js:1:244531)
        at /home/runner/work/mikro-orm/mikro-orm/docs/node_modules/typedoc/dist/lib/utils/highlighter.js:1:554
        at evalModule (/home/runner/work/mikro-orm/mikro-orm/docs/node_modules/jiti/dist/jiti.js:1:247313)
        at jiti (/home/runner/work/mikro-orm/mikro-orm/docs/node_modules/jiti/dist/jiti.js:1:245241)
        at /home/runner/work/mikro-orm/mikro-orm/docs/node_modules/typedoc/dist/lib/utils/options/sources/typedoc.js:10:20
        at evalModule (/home/runner/work/mikro-orm/mikro-orm/docs/node_modules/jiti/dist/jiti.js:1:247313)
        at jiti (/home/runner/work/mikro-orm/mikro-orm/docs/node_modules/jiti/dist/jiti.js:1:245241)
        at /home/runner/work/mikro-orm/mikro-orm/docs/node_modules/typedoc/dist/lib/utils/options/sources/index.js:1:282
        at evalModule (/home/runner/work/mikro-orm/mikro-orm/docs/node_modules/jiti/dist/jiti.js:1:247313)
        at jiti (/home/runner/work/mikro-orm/mikro-orm/docs/node_modules/jiti/dist/jiti.js:1:245241)
        at /home/runner/work/mikro-orm/mikro-orm/docs/node_modules/typedoc/dist/lib/utils/options/options.js:5:14
        at evalModule (/home/runner/work/mikro-orm/mikro-orm/docs/node_modules/jiti/dist/jiti.js:1:247313)
        at jiti (/home/runner/work/mikro-orm/mikro-orm/docs/node_modules/jiti/dist/jiti.js:1:245241)
        at /home/runner/work/mikro-orm/mikro-orm/docs/node_modules/typedoc/dist/lib/utils/options/index.js:1:1479
        at evalModule (/home/runner/work/mikro-orm/mikro-orm/docs/node_modules/jiti/dist/jiti.js:1:247313)
        at jiti (/home/runner/work/mikro-orm/mikro-orm/docs/node_modules/jiti/dist/jiti.js:1:245241)
        at /home/runner/work/mikro-orm/mikro-orm/docs/node_modules/typedoc/dist/lib/utils/index.js:10:14
        at evalModule (/home/runner/work/mikro-orm/mikro-orm/docs/node_modules/jiti/dist/jiti.js:1:247313)
        at jiti (/home/runner/work/mikro-orm/mikro-orm/docs/node_modules/jiti/dist/jiti.js:1:245241)
        at /home/runner/work/mikro-orm/mikro-orm/docs/node_modules/typedoc/dist/lib/models/comments/comment.js:35:14
        at evalModule (/home/runner/work/mikro-orm/mikro-orm/docs/node_modules/jiti/dist/jiti.js:1:247313)
        at jiti (/home/runner/work/mikro-orm/mikro-orm/docs/node_modules/jiti/dist/jiti.js:1:245241)
        at /home/runner/work/mikro-orm/mikro-orm/docs/node_modules/typedoc/dist/lib/models/reflections/abstract.js:35:16
        at evalModule (/home/runner/work/mikro-orm/mikro-orm/docs/node_modules/jiti/dist/jiti.js:1:247313)
        at jiti (/home/runner/work/mikro-orm/mikro-orm/docs/node_modules/jiti/dist/jiti.js:1:245241)
        at /home/runner/work/mikro-orm/mikro-orm/docs/node_modules/typedoc/dist/lib/models/reflections/index.js:1:2263
        at evalModule (/home/runner/work/mikro-orm/mikro-orm/docs/node_modules/jiti/dist/jiti.js:1:247313)
        at jiti (/home/runner/work/mikro-orm/mikro-orm/docs/node_modules/jiti/dist/jiti.js:1:245241)
        at /home/runner/work/mikro-orm/mikro-orm/docs/node_modules/typedoc/dist/lib/models/index.js:1:151
        at evalModule (/home/runner/work/mikro-orm/mikro-orm/docs/node_modules/jiti/dist/jiti.js:1:247313)
        at jiti (/home/runner/work/mikro-orm/mikro-orm/docs/node_modules/jiti/dist/jiti.js:1:245241)
        at /home/runner/work/mikro-orm/mikro-orm/docs/node_modules/typedoc/dist/lib/serialization/deserializer.js:2:14
        at evalModule (/home/runner/work/mikro-orm/mikro-orm/docs/node_modules/jiti/dist/jiti.js:1:247313)
        at jiti (/home/runner/work/mikro-orm/mikro-orm/docs/node_modules/jiti/dist/jiti.js:1:245241)
        at /home/runner/work/mikro-orm/mikro-orm/docs/node_modules/typedoc/dist/lib/serialization/index.js:1:550
        at evalModule (/home/runner/work/mikro-orm/mikro-orm/docs/node_modules/jiti/dist/jiti.js:1:247313)
        at jiti (/home/runner/work/mikro-orm/mikro-orm/docs/node_modules/jiti/dist/jiti.js:1:245241)
        at /home/runner/work/mikro-orm/mikro-orm/docs/node_modules/typedoc/dist/lib/application.js:[37](https://github.com/mikro-orm/mikro-orm/actions/runs/12075851011/job/33676312701?pr=6259#step:9:42):14
        at evalModule (/home/runner/work/mikro-orm/mikro-orm/docs/node_modules/jiti/dist/jiti.js:1:247313)
        at jiti (/home/runner/work/mikro-orm/mikro-orm/docs/node_modules/jiti/dist/jiti.js:1:245241)
        at /home/runner/work/mikro-orm/mikro-orm/docs/node_modules/typedoc/dist/index.js:4:20
        at evalModule (/home/runner/work/mikro-orm/mikro-orm/docs/node_modules/jiti/dist/jiti.js:1:247313)
        at jiti (/home/runner/work/mikro-orm/mikro-orm/docs/node_modules/jiti/dist/jiti.js:1:2452[41](https://github.com/mikro-orm/mikro-orm/actions/runs/12075851011/job/33676312701?pr=6259#step:9:46)) {
      code: 'ERR_PACKAGE_PATH_NOT_EXPORTED'
    }
  }
}

Thank you! My only issue is that I want to test the build works via PR checks and I need to run them on older node versions too, but it's fine to run the docs check only on node 22 I guess, so not really a problem if it's just about that.
Btw, I am not saying you should remove it from changelog, just that you should maybe highlight it on other places too, since moving to ESM only is quite a big deal for downstream. I have no issues with that move itself, I plan to do it with my packages too during next year, the time is now given the unflagged require(esm) which will land to node 20 too at some point.

require(esm) is in Node 20.17

I meant the unflagging

Closing this as this package can now be required


frontend

hello, i want to contribute to the project (frontend part) and i want to know why there is two frontend folders Kibbah and kofta :) thank you

Kibbeh is the new frontend, we're transitioning from CRA to next.js and getting a new design,


Kafka script should be consistent with Shell Style Guide

Kafka script is working well, however it's not following the Shell Style Guide
The whole initialization script has rather complex logic and it should have main function. This will allow to easily extend script logic with additional components.
Error handling could be done in much more descriptive way.
There are several bash enhancement that could be added to script.

PR was merged and issue #200 was created.
I will close this issue then.


Update provenance_format.md

Add section headers to group fields.
Remove version specific heading. We should add "since v1.1" or similar tags to new fields (or "deprecated/removed in v1.1" for removed fields)?

I made a couple of suggestions, curious to read what you think.

SG


Unable to load state history; Updating sensor took longer than the scheduled update interval

Home Assistant release with the issue:
0.78
Last working Home Assistant release (if known):
0.77.3
Operating environment (Hass.io/Docker/Windows/etc.):
Linux raspberrypi 4.14.62-v7+ #1134 SMP Tue Aug 14 17:10:10 BST 2018 armv7l GNU/Linux
Component/platform:
Multiple
Description of problem:
Since updating to 0.78, I've had the following happen twice:

When I click on an item in the UI to see state history, it just says "Loading state history" and never loads
If I log out of HA and attempt to log back in, it just hangs.  It never logs in.  No error messages are shown
My logs start filling up with the following every 30 seconds:

2018-09-19 06:31:40 ERROR (MainThread) [homeassistant.components.sensor.wunderground] Error fetching WUnderground data: TimeoutError()
2018-09-19 06:31:41 WARNING (MainThread) [homeassistant.components.binary_sensor] Updating command_line binary_sensor took longer than the scheduled update interval 0:05:00
2018-09-19 06:31:42 WARNING (MainThread) [homeassistant.components.sensor] Updating systemmonitor sensor took longer than the scheduled update interval 0:05:00
2018-09-19 06:31:42 WARNING (MainThread) [homeassistant.components.binary_sensor] Updating ping binary_sensor took longer than the scheduled update interval 0:05:00
2018-09-19 06:31:42 WARNING (MainThread) [homeassistant.components.switch] Updating command_line switch took longer than the scheduled update interval 0:05:00
2018-09-19 06:31:42 WARNING (MainThread) [homeassistant.components.media_player] Updating onkyo media_player took longer than the scheduled update interval 0:00:10
2018-09-19 06:31:52 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.comed_total_5_minute_price is taking over 10 seconds
2018-09-19 06:31:52 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.comed_total_current_hour_average_price is taking over 10 seconds
2018-09-19 06:31:52 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.comed_current_hour_average_price is taking over 10 seconds
2018-09-19 06:31:52 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.comed_5_minute_price is taking over 10 seconds
2018-09-19 06:31:52 WARNING (MainThread) [homeassistant.components.media_player] Updating onkyo media_player took longer than the scheduled update interval 0:00:10
2018-09-19 06:32:03 WARNING (MainThread) [homeassistant.components.sensor] Updating nut sensor took longer than the scheduled update interval 0:00:30
2018-09-19 06:32:03 WARNING (MainThread) [homeassistant.components.camera] Updating nest camera took longer than the scheduled update interval 0:00:30
2018-09-19 06:32:03 WARNING (MainThread) [homeassistant.components.media_player] Updating onkyo media_player took longer than the scheduled update interval 0:00:10
2018-09-19 06:32:04 WARNING (MainThread) [homeassistant.components.sensor] Updating sql sensor took longer than the scheduled update interval 0:00:30
2018-09-19 06:32:05 WARNING (MainThread) [homeassistant.components.switch] Updating tplink switch took longer than the scheduled update interval 0:00:30
2018-09-19 06:32:05 WARNING (MainThread) [homeassistant.components.sensor] Updating ios sensor took longer than the scheduled update interval 0:00:30
2018-09-19 06:32:14 WARNING (MainThread) [homeassistant.components.media_player] Updating onkyo media_player took longer than the scheduled update interval 0:00:10
2018-09-19 06:32:25 WARNING (MainThread) [homeassistant.components.media_player] Updating onkyo media_player took longer than the scheduled update interval 0:00:10

It appears that any sensors that talk to remote servers stop updating
When I look back through the logs to find the first occurrence of warnings or errors, this is the first thing I see, and nothing else seems out of the ordinary:

2018-09-18 09:25:10 WARNING (MainThread) [homeassistant.components.switch.wemo] Lost connection to Office Light
2018-09-18 09:25:13 WARNING (MainThread) [homeassistant.components.switch] Updating wemo switch       took longer than the scheduled update interval 0:00:10

This has happened twice now.  After the first time, I had to restart HA and everything seemed fine after that.  Then it happened again about 13 hours later.

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
I don't think posting my entire config here would be helpful but can post if requested.  Nothing has changed in my config recently.
I should also add that my MiFlora sensor stopped working with 0.78 (see #16700), and I see this in the logs every 3 minutes:
2018-09-19 06:26:13 INFO (MainThread) [homeassistant.components.sensor] Setting up sensor.miflora
2018-09-19 06:26:23 ERROR (MainThread) [homeassistant.components.sensor.miflora] Unable to connect to XX:XX:XX:XX:XX:XX
2018-09-19 06:26:23 WARNING (MainThread) [homeassistant.components.sensor] Platform miflora not ready yet. Retrying in 180 seconds.

Sins 0.81 ive seen this beign a problem again with loggs filling upp.

Is this with telnet or ssh?

Seeing the same issue crop up for a couple of sensors I created to track running time on devices, see below an example of Log file, specifically, "Update of sensor.total_running_time_compressor is taking over 10 seconds" (my environment details after log entry):
2019-03-10 16:07:57 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.total_running_time_compressor is taking over 10 seconds
2019-03-10 16:08:28 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.total_running_time_compressor is taking over 10 seconds
2019-03-10 16:08:49 WARNING (MainThread) [homeassistant.components.sensor] Updating history_stats sensor took longer than the scheduled update interval 0:00:30
2019-03-10 16:08:55 INFO (SyncWorker_15) [pyicloud.base] Authenticating as<EMAIL_ADDRESS>2019-03-10 16:08:55 INFO (SyncWorker_15) [pyicloud.base] Authentication completed successfully
2019-03-10 16:09:32 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.total_running_time_compressor is taking over 10 seconds
2019-03-10 16:09:55 INFO (SyncWorker_7) [pyicloud.base] Authenticating as<EMAIL_ADDRESS>2019-03-10 16:09:56 INFO (SyncWorker_7) [pyicloud.base] Authentication completed successfully
2019-03-10 16:10:02 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.total_running_time_compressor is taking over 10 seconds
2019-03-10 16:10:30 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.total_running_time_compressor is taking over 10 seconds
2019-03-10 16:10:47 INFO (MainThread) [homeassistant.components.http.view] Serving /api/ to <IP_ADDRESS> (auth: True)
2019-03-10 16:10:55 INFO (SyncWorker_7) [pyicloud.base] Authenticating as<EMAIL_ADDRESS>2019-03-10 16:10:55 INFO (SyncWorker_7) [pyicloud.base] Authentication completed successfully
2019-03-10 16:11:03 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.total_running_time_compressor is taking over 10 seconds
2019-03-10 16:11:30 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.total_running_time_compressor is taking over 10 seconds
Hassio Environment - Running on RPI

arch
aarch64

dev
false

docker
true

hassio
true

os_name
Linux

python_version
3.7.2

timezone
America/New_York

version
0.89.1

virtualenv
false


Fix refs consolidation for union models

Fixes #5660
Summary
Consolidating refs after a union schema was created
Explanation
I get approximately the next call chart
flowchart TD
    A["self._union_schema()"] -->B["self.generate_schema()"]
    B --> C["self._generate_schema_from_property()"]
    C --> D["BaseModel.__get_pydantic_core_schema__()"]

https://github.com/pydantic/pydantic/blob/9c1b9804ef4db1a7c22532ee9a6d9168961db1f5/pydantic/_internal/_generate_schema.py#L606-L618
https://github.com/pydantic/pydantic/blob/9c1b9804ef4db1a7c22532ee9a6d9168961db1f5/pydantic/main.py#L264-L265
self.generate_schema(arg) returns already prepared schema from cls.__pydantic_core_schema__ and this is the problem. The schema of SecondModel doesn't know anything about FirstModel.
Checklist

[X] Unit tests for the changes exist
[x] Tests pass on CI and coverage remains at 100%
[ ] Documentation reflects the changes where applicable
[ ] changes/<pull request or issue id>-<github username>.md file added describing change
(see changes/README.md for details)
[X] My PR is ready to review, please add a comment including the phrase "please review" to assign reviewers

Selected Reviewer: @adriangb

please review

@adriangb
I described the problem in some detail in the commentary on the issue when I did my research: https://github.com/pydantic/pydantic/issues/5660#issuecomment-1533443836
In short:
For the next structure
class Nested(BaseModel):
    pass

class SomeData(BaseModel):
    nested1: Nested

class FirstModel(BaseModel):
    nested2: Nested
    data: SomeData

class SecondModel(BaseModel):
    id: int
    some_data: SomeData

AnalyzedType(FirstModel | SecondModel)

we get an error:
# pydantic_core._pydantic_core.SchemaError: Error building "union" validator:
# SchemaError: Error building "model" validator:
# SchemaError: Error building "typed-dict" validator:
# SchemaError: Field "some_data":
# SchemaError: Error building "default" validator:
# SchemaError: Error building "nullable" validator:
# SchemaError: Error building "model" validator:
# SchemaError: Error building "typed-dict" validator:
# SchemaError: Field "some_user":
# SchemaError: Error building "default" validator:
# SchemaError: Error building "nullable" validator:
# SchemaError: Duplicate ref: `__main__.Nested:94251265397456`.

Since the resulting model has two Nested model declarations (once in FirstModel and once in SecondModel)

If you are interested I'm implementing a client for Discord and have the next model structure
class IntegrationApplication(BaseModel):
    ...
    bot: User | None = None

class DiscordIntegration(BaseModel):
    ...
    application: IntegrationApplication | None = None
    ...
    model_config = ConfigDict(undefined_types_warning=False)

class GeneralIntegration(BaseModel):
    ...
    user: User
    application: IntegrationApplication | None = None
    ...
    model_config = ConfigDict(undefined_types_warning=False)

IntegrationVariants = Annotated[GeneralIntegration | DiscordIntegration, Field(discriminator='type')]

_IntegrationVariantListValidator = AnalyzedType(list[IntegrationVariants])

I get the error:
    _IntegrationVariantListValidator = AnalyzedType(list[IntegrationVariants])
.venv/lib/python3.11/site-packages/pydantic/analyzed_type.py:111: in __init__
    validator = SchemaValidator(core_schema, core_config)
E   pydantic_core._pydantic_core.SchemaError: Error building "list" validator:
E     SchemaError: Error building "tagged-union" validator:
E     SchemaError: Error building "model" validator:
E     SchemaError: Error building "typed-dict" validator:
E     SchemaError: Field "application":
E     SchemaError: Error building "default" validator:
E     SchemaError: Error building "nullable" validator:
E     SchemaError: Error building "model" validator:
E     SchemaError: Error building "typed-dict" validator:
E     SchemaError: Field "bot":
E     SchemaError: Error building "default" validator:
E     SchemaError: Error building "nullable" validator:
E     SchemaError: Duplicate ref: `client.models.users.User:94892781223600`

I'm glad I can return to work on my project soon because this problem has been a blocker.
Thank you for your work :fire:

@adriangb Oh, and also, it would be great if you could add a tag for non-priority issues to help newcomers join the project


PR for osprarrow branch

PR to archive the osprarrow branch.

superseded by the way arrows would be rendered in current OSPRay


Disable Mail Release

Hi,
Is there an option to disable/hide the option for mail release ?

As far as I understand https://github.com/mailhog/MailHog/blob/master/docs/CONFIG.md this is not yet possible - but we'd love to see this config option added as a new feature.
Use case would be: If a customer uses MailHog to verify the application that we develop for this customer sends out proper e-mails, those mails could potentially be addressed to real end-users. In case they get accidentally sent out, this would cause discussions and troubles we'd like to avoid.
Or in other words: We don't need the feature to release mails - so we'd like to configure MailHog in a way, that this feature cannot be used accidentally.


LVM Storage info always shows zero space used

Required information

Distribution: Ubuntu
Distribution version: 16.04.5 LTS
The output of "lxc info" or if that fails:
lxc_info.txt

Kernel version: 4.4.0-151-generic
LXC version: 3.0.3
LXD version: 3.0.3
Storage backend in use: LVM

Issue description
LVM Storage info always shows zero space used
Steps to reproduce

Create an LVM thinpool storage
Launch a container on LVM storage
Check storage usage using "lxc storage info "
Reported "space used" is 0B, as per attached
lxc_storage_info.txt

Information to attach

[ ] Any relevant kernel output (dmesg)
[X] Container log (lxc info NAME --show-log)
lxc_info_show-log.txt
[X] Container configuration (lxc config show NAME --expanded)
lxc_config_show_expanded.txt
[ ] Main daemon log (at /var/log/lxd/lxd.log or /var/snap/lxd/common/lxd/logs/lxd.log)
[ ] Output of the client with --debug
[X] Output of the daemon with --debug (alternatively output of lxc monitor while reproducing the issue)
lxc_monitor.txt
Actual LVM Storage Usage: lvs.txt

Recreated this issue
lxc storage info lvmpool
info:
  description: ""
  driver: lvm
  name: lvmpool
  space used: 0B
  total space: 43.00GB
used by:
  containers:
  - c3
  images:
  - 1ee31e5f12f654209c22b55e61b8c25f05f7e8a6435a2fa827243bebc4ce719d

@stgraber there is a comment in the code about this already:
https://github.com/lxc/lxd/blob/master/lxd/storage_lvm.go#L2181-L2182
// Thinpools will always report zero free space so no use in calculating
// a used count. It'll be useless information for the user.

This is true, for the volume group,as 100% of it is allocated to the thinpool LV.
sudo vgs  -o vg_name,lv_name,data_percent,vg_free,lv_size,vg_size,vg_free
  VG      LV                                                                      Data%  VFree LSize  VSize  VFree
  lvmpool LXDThinPool                                                             2.42      0  38.04g 40.04g    0

However in principle some sort of usage value could perhaps be derived from looking at the thinpool LV and its LSize and data usage % value. This would only represent how many blocks had been allocated to thin volumes, not whether they are actually used by the file system (and they are not normally released by the OS unless fstrim is run).
What do you think?

@tomponline agreed that we won't get useful data from LVM itself, but we could report the disk usage by looking at Path() so long as it's mounted, effectively reporting the filesystem data instead of the LVM data.
So effectively the same logic we have for the dir backend, but returning 0 if Path() isn't mounted.

@stgraber I just created a dir pool to test that and it shows some weird figures:
lxc storage create dirpool dir
lxc init ubuntu:18.04 c1 -s dirpool

lxc storage ls
sudo du -h /var/lib/lxd/storage-pools/dirpool
685M
lxc storage info dirpool
info:
  description: ""
  driver: dir
  name: dirpool
  space used: 125.43GB
  total space: 234.69GB
used by:
  containers:
  - c4

I'm a bit confused where those figures come from, I assumed they were the equivalent output of df for my "/" mount.
It comes from here: https://github.com/lxc/lxd/blob/60dc9b769ac3377d0aa2ab6d90e2921e6a05b417/lxd/storage_utils.go#L366-L383
But my "/" is only 219GB in size and 117GB free. Its ext4.
df -h
/dev/sda2                   219G  117G   91G  57% /

For LVM, I would then need mount each container's LV that use that storage pool and run the equivalent process in order to get total usage for the storage pool. Is that what you meant?

@stgraber Ah, so I think its to do with the different way df calculates space,taking into account space reserved for root user. https://stackoverflow.com/questions/4965355/converting-statvfs-to-percentage-free-correctly

Could also be a GiB vs GB issue, most tools report GiB, we report GB.
In any case, the values you're seeing for your dir pool look reasonable enough.
And I know that when you have project quotas enabled we report the proper per-container data, so that logic must be called properly in that case, the only real difference with LVM is that we'll want to ensure that the mount is present, if it got ripped out for some reason, then 0 is better than showing the host disk usage.


Shortened routes

Proposal for web interface: /users/ -> /u/, /pastes/ -> /p/
I don't believe this should be necessary for API routes.

Reminds me of Reddit :+1:

Whoops, meant to mention this issue in https://github.com/jkcclemens/paste/commit/1fe6f5e668616f07be34084173130c3887b123f3.
Sneakily snuck this change in. Will update staging soon.

Nothing seems to have crashed and burned now that this is on production.


cert-manager generates invalid ingress spec when renewing cert

Describe the bug:
My cert-manager configuration has successfully issued new certificates about three months ago (same kubernetes config across several deployments), but has failed to renew.  I'm seeing

Error preparing issuer for certificate ingress-controller/root-url-tls: Ingress.extensions "certificate-challenge-ingress" is invalid: spec: Invalid value: []extensions.IngressRule(nil): either backend or rules must be specified

when cert-manager is attempting to renew a cert.  The certificate spec is
spec:
  acme:
    config:
    - domains:
      - dustin.taskcluster-dev.net
      http01:
        ingress: certificate-challenge-ingress
  commonName: dustin.taskcluster-dev.net
  issuerRef:
    kind: ClusterIssuer
    name: letsencrypt-issuer
  secretName: taskcluster-ingress-tls-secret

and the certificate-challenge-ingress has
spec:
  rules:
  - http:
      paths:
      - backend:
          serviceName: default-http-backend
          servicePort: 80
        path: /not-used
  - host: dustin.taskcluster-dev.net
    http:
      paths:
      - backend:
          serviceName: cm-acme-http-solver-dx2cq
          servicePort: 8089
        path: /.well-known/acme-challenge/..mumble..
  tls:
  - hosts:
    - dustin.taskcluster-dev.net
    secretName: taskcluster-ingress-tls-secret

notably, spec.rules exists.  So I can't make heads or tails of the error message -- I assume that cert-manager is modifying the ingress, and in the process creating an invalid spec?
Expected behaviour:
Certificate should be renewed automatically.
Environment details::

Kubernetes version:

Client Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.7", GitCommit:"0c38c362511b20a098d7cd855f1314dad92c2780", GitTreeState:"clean", BuildDate:"2018-08-20T10:09:03Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"10+", GitVersion:"v1.10.7-gke.11", GitCommit:"fa90543563c9cfafca69128ce8cd9ecd5941940f", GitTreeState:"clean", BuildDate:"2018-11-08T20:22:21Z", GoVersion:"go1.9.3b4", Compiler:"gc", Platform:"linux/amd64"}

Cloud-provider/provisioner: GKE
cert-manager version: v0.5.0
Install method: static manifests based on the v0.5.0 helm manifests

/kind bug

There's been improvements to ingress-shim as part of v0.6 - could you try this with the latest v0.6.1 release and report back?

Upgrading to 0.6.0 seemed to help -- sorry, I should have come back to close tihs.


Error solving QPSUT03 problem

Hello! I face issue solving the following test problem with qpax solver.
Here is a script to reproduce:
import jax.numpy as np

from qpax import solve_qp

# Defining the problem data using JAX numpy arrays
P = np.array([[122.0, 59.0, 39.0, 9.0], [59.0, 95.0, 48.0, 24.0], [39.0, 48.0, 26.0, 19.0], [9.0, 24.0, 19.0, 90.0]])

q = np.array([66.0, 93.0, 47.0, 11.0])

# No equality constraints
A = np.array([]).reshape(0, 4)  # No equality constraint matrix
b = np.array([])  # No equality constraint vector

G = np.array(
    [
        [-1.0, -0.0, -0.0, -0.0],
        [-0.0, -1.0, -0.0, -0.0],
        [-0.0, -0.0, -1.0, -0.0],
        [-0.0, -0.0, -0.0, -1.0],
        [1.0, 0.0, 0.0, 0.0],
        [0.0, 1.0, 0.0, 0.0],
        [0.0, 0.0, 1.0, 0.0],
        [0.0, 0.0, 0.0, 1.0],
    ]
)

h = np.array([np.inf, 0.4, np.inf, 1.0, np.inf, np.inf, 0.5, 1.0])

# Solving the QP
x = solve_qp(P, q, A, b, G, h)[0]

# Check that answer is not nan
assert not np.isnan(
    x
).any(), "Solution contains NaN values, expected [0.18143455,  0.00843864, -2.35442995,  0.35443034]"

Same issue as https://github.com/kevin-tracy/qpax/issues/4

Fixed with https://github.com/kevin-tracy/qpax/commit/2cbd04e984ff30844be3601642240a054b886bac


Error retrieving content from Next and Previous Buttons in multi-language docs

Have you read the Contributing Guidelines on issues?

[X] I have read the Contributing Guidelines on issues.

Prerequisites

[X] I'm using the latest version of Docusaurus.
[X] I have tried the npm run clear or yarn clear command.
[X] I have tried rm -rf node_modules yarn.lock package-lock.json and re-installing packages.
[X] I have tried creating a repro with https://new.docusaurus.io.
[X] I have read the console error message carefully (if applicable).

Description
There are some problems in getting languages in a multilingual Docusaurus. My page has 2 languages: vi-VN and en-US. I configured the sidebar to automatically generate and use category.json and It looks like this :

This is the directory structure :

However, when running the project, I noticed that the next and previous suction in the vi-VN language version took the label of the category.json file of the original language (en-US), this is the image
It seems that the Docusaurus docs site also has this problem

Reproducible demo
https://docusaurus.io/zh-CN/docs/i18n/git
Steps to reproduce
Regarding the error pattern, I think you can see it clearly as long as you visit the official docusaurus page.
Expected behavior
I would expect that the male page content displayed in the next and back buttons would display the correct content in the current language instead of just the original language.
Actual behavior

I tried changing the content of the category.json file of the original language and it's confusing that the Content displayed at the 2 buttons is according to the original language (This happens when using category.json to set up the sidebar automatically and the next or previous page is the summary of the category )
Your environment

Public source code:
Public site URL:
Docusaurus version used:
Environment name and version (e.g. Chrome 89, Node.js 16.4):
Operating system and version (e.g. Ubuntu 20.04.2 LTS):

Self-service

[ ] I'd be willing to fix this bug myself.

Duplicate of https://github.com/facebook/docusaurus/issues/8996
Unfortunately we don't have support for localizing category.json files.
However it remains possible to handle through our write-translations CLI.
Example: https://docusaurus.io/ko/docs/configuration


0% CPU usage on docker container

Pulse Version
1.0.0-beta5
Laravel Version
10.x (latest)
PHP Version
8.2 (latest)
Livewire Version
3
Database Driver & Version
Postgresql 16 on docker container
Description
In a dockerized environment Laravel Pulse always reports 0% CPU usage.
Steps To Reproduce
create a laravel project using Laravel Sail and check the CPU usage.

Ok, I checked the source and found that pulse uses the top command to check the CPU usage.
The top command in my containers reports 0% CPU usage.
I use Alpine Linux as the base image.

It looks like this may be a limitation within top, that prevents it from being able to properly read CPU usage of virtualized resources. https://github.com/moby/moby/issues/26113

It looks like this may be a limitation within top, that prevents it from being able to properly read CPU usage of virtualized resources. moby/moby#26113

I didn't test this on other base images like Ubuntu but using mpstat I can get the CPU usage in my container.

/etc/os-release host machine
PRETTY_NAME="Ubuntu 22.04.3 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.3 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=jammy

/etc/os-release container
NAME="Alpine Linux"
ID=alpine
VERSION_ID=3.18.5
PRETTY_NAME="Alpine Linux v3.18"
HOME_URL="https://alpinelinux.org/"
BUG_REPORT_URL="https://gitlab.alpinelinux.org/alpine/aports/-/issues"

Interesting - that output is formatted quite differently from what we're expecting. Most notably, the CPU line begins with "CPU:" but Pulse is expecting it to begin with "%Cpu(s):".
Here's the output from top on my Linux laptop:
➜  ~ top -bn1
top - 08:48:45 up 3 days, 15:20,  2 users,  load average: 1.69, 1.36, 1.22
Tasks: 579 total,   1 running, 573 sleeping,   0 stopped,   5 zombie
%Cpu(s):  9.1 us,  4.5 sy,  0.0 ni, 86.4 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st
MiB Mem :  31737.7 total,   1337.3 free,  17214.1 used,  15534.1 buff/cache
MiB Swap:   8192.0 total,   7779.7 free,    412.2 used.  14523.6 avail Mem

    PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND

What version of top do you have?
On my host machine I have:
➜  ~ top -V
top from procps-ng 4.0.3

And in my Sail (Ubuntu) container I have:
sail@57830d912d37:/var/www/html$ top -v
  procps-ng 3.3.17

Interestingly, they both have a different CLI option for getting the version, but both follow the same format for the CPU line.
I'm guessing your version of top probably isn't the procps-ng version but rather an entirely different implementation that Alpine has chosen. The output looks more similar to the implementation Darwin ships with, although interestingly yours still supports the -bn1 flags.

@jessarcher yes the alpine uses BusyBox 1.36.1 for top command.

Hi @ariaieboy, I've created #236, which updates the parsing of the top output to hopefully work for both versions of top on Linux.

@jessarcher Can we have this in a tagged release so I can test it on my instances?

v1.0.0-beta8 has just been tagged.


Error on npm run build and after deployment

I'm getting this error when I run npm run build

When I continue with the next steps I get this error after deployment in GMail

sam here, please we need clarity


Fix login with oauth2 sometimes return could not find a matching session for this request

Try to fix #27033
#5551

Try to fix #27033

I do not see how it fixes 27033

OK. This is a mistake. The real problem is users visiting a Gitea address which is not the one they input in the GitHub oauth2 application forms.


Add an empty pg_catalog.pg_locks table

Resolves https://github.com/crate/crate/issues/11726
Checklist

[x] Added an entry in CHANGES.txt for user facing changes
[x] Updated documentation & sql_features table for user facing changes
[x] Touched code is covered by tests
[x] CLA is signed
[x] This does not contain breaking changes, or if it does:

It is released within a major release
It is recorded in CHANGES.txt
It was marked as deprecated in an earlier release if possible
You've thought about the consequences and other components are adapted
(E.g. AdminUI)

non reproducible
./gradlew :server:test -Dtests.seed=EC1043CBFEE710ED -Dtests.class=io.crate.expression.scalar.AgeFunctionTest -Dtests.method="test_2_arguments_positive" -Dtests.locale=en-GD -Dtests.timezone=Africa/Asmera
retest this please


Fix color gradient

Needs rebase on top of https://github.com/inveniosoftware/invenio-app-rdm/pull/141


Correct resource type for host event

@vincent99 fixed the resourceType for host event. Here is the event rancher generates:
{
	"id": "2d2f91e1-022f-480b-a9dc-1bc7527e41a2",
	"name": "state.change",
	"replyTo": null,
	"resourceId": "1",
	"resourceType": "host",
	"publisher": null,
	"transitioning": null,
	"transitioningMessage": null,
	"transitioningInternalMessage": null,
	"previousIds": null,
	"previousNames": null,
	"data": {
		"info": {
			"cpuInfo": {
				"count": 1,
				"cpuCoresPercentages": [2.245],
				"loadAvg": [0.04, 0.06, 0.05],
				"mhz": 2800.0,
				"modelName": "Intel(R) Core(TM) i5-4308U CPU @ 2.80GHz"
			},
			"memoryInfo": {
				"memTotal": 2002.578,
				"swapTotal": 1403.301,
				"cached": 435.219,
				"swapCached": 0.0,
				"swapFree": 1403.301,
				"memAvailable": 1671.758,
				"memFree": 1303.137,
				"inactive": 181.582,
				"active": 440.715,
				"buffers": 70.211
			},
			"osInfo": {
				"kernelVersion": "4.1.18-boot2docker",
				"operatingSystem": "Boot2Docker 1.10.2 (TCL 6.4.1); master : 611be10 - Mon Feb 22 22:47:06 UTC 2016",
				"dockerVersion": "Docker version 1.10.2, build c3959b1"
			},
			"diskInfo": {
				"mountPoints": {
					"/dev/sda1": {
						"total": 200505.266,
						"free": 167672.449,
						"used": 32832.816,
						"percentUsed": 16.38
					}
				},
				"dockerStorageDriverStatus": {
					"Dirs": "322",
					"Dirperm1 Supported": "true",
					"Backing Filesystem": "extfs",
					"Root Dir": "/mnt/sda1/var/lib/docker/aufs"
				},
				"dockerStorageDriver": "aufs",
				"fileSystems": {
					"/dev/sda1": {
						"capacity": 200505.266
					}
				}
			}
		},
		"accountId": 5
	},
	"time":<PHONE_NUMBER>148,
	"timeoutMillis": null,
	"transitioningProgress": null,
	"context": null
}

not sure how to check what event UI receives, and why you saw it as null. This field should never come as null as I always put accountId to the data

https://github.com/rancher/rancher/issues/3523

@vincent99 double checked that the UI receives not-null-data event as well. May be it was null before due to unknown resource type


API design for membership dashboard and frame generation using APIs

@xprilion Do assign me this issue.

Framework
Flask
Authentication

Google OAuth2.0 and flask-login

Generating Frames

Python Imaging Library

Databases

Firebase

APIs

Endpoints
Methods
Description

/login
POST
redirect to Google Accounts page to login

/login/callback
GET
callback after successful login

/save
POST
saving the generated frame (protected route)

/savedframes
GET
to get the saved frames

/frames
POST
to generate the frames  (request body not yet designed)


Repeating taps have delay ?

Hi
I'm trying now the library and I found (sorry or at least I can't figure out) , if I want the user to double tap or tap very quickly one after another (because is not working for me) how this can be achieved and still the material effect to be there.
Can you hep with this please.
Thanks in advance.

Alright, I've just enabled the user interaction during the material animation, so now you'll be able to tap the button as quick as you like :P
Thanks for your suggestion. (Don't forget pod update)

Thanks Very Much :)

No problem. Thanks for supporting.


Refactor FITS reader

It seems to me that there is memory leak, since graph of the memory of the big analysis looks strange.
For now, code looks like this:
def from_fits(filename: str) -> Iterator[Tuple[Particles, ScalarQuantity]]:
    hdul = fits.open(filename, memmap=True)

    for frame in range(len(hdul) - 1):
        table: BinTableHDU = hdul[frame + 1]
        number_of_particles = len(table.data[list(fields.keys())[0]])

        timestamp = table.header["TIME"] | units.Myr
        particles = Particles(number_of_particles)

        for (key, val) in fields.items():
            if val is not None:
                setattr(particles, key, table.data[key] | val)
            else:
                try:
                    data = np.array(table.data[key], dtype=np.float64)
                except KeyError:
                    continue
                setattr(particles, key, data)

        yield particles, timestamp

Want to try several changes and look how it affects memory consumption of the process. Results would be in this ticket.

Using psrecord library to look at the memory graph.

First of all, the hdul is never closed. I do not think that this affects memory consumption in any significant way but it is good to eliminate this first.
Second, memmap parameter seems to be True by default. Should try removing all of the parameters and use simple fits.open(filename) method.
Also, there is lazy_load_hdus parameter. It is also True by default but it is worth trying it and see if anything changes. It would be more rational to set it to False and see if consumption of the memory increases.
Another point is that in the loop I count len(hdul) which is incredibly slow since it goes over the whole file at once. Not sure if there is any caching but I probably shpuld iterate over the elements without counting of the length (since it is useless anyway).

Added
    hdul.close()

to the end of the function. Seems to me that nothing changed. Leaving it that way, closing file is never redundant.

Stopped using len() of the HDUTable. Same, nothing changed.
Code
def from_fits(filename: str) -> Iterator[Tuple[Particles, ScalarQuantity]]:
    """
    Loads snapshots from the FITS file where each HDU stores binary table with one timestamp.
    """
    hdul = fits.open(filename, memmap=True)

    first = True

    for table in hdul:
        if first:
            # skipping first HDU; it is required by the FITS specification.
            first = False
            continue

        number_of_particles = len(table.data[list(fields.keys())[0]])

        timestamp = table.header["TIME"] | units.Myr
        particles = Particles(number_of_particles)

        for (key, val) in fields.items():
            if val is not None:
                setattr(particles, key, table.data[key] | val)
            else:
                try:
                    data = np.array(table.data[key], dtype=np.float64)
                except KeyError:
                    continue
                setattr(particles, key, data)

        yield particles, timestamp

    hdul.close()

Memory graph:

Changed
hdul = fits.open(filename, memmap=True)

to
hdul = fits.open(filename)

Still no effect:

hdul = fits.open(filename, lazy_load_hdus=False)

Still no effect. Will try to do same thing with True.

hdul = fits.open(filename, lazy_load_hdus=True)

Maybe it is not because of FITS reading after all.

hdul = fits.open(filename, memmap=False)

Nope

Though overall memory consuption peak is lower trhan it was. Not sufficient though.

Added
        del particles
        del table

after the yield statement. Still nothin'.

Garbage collector time I guess.

Finally. Added this after each iteration:
gc.collect()

This seems to make the whole thing much better (without even compromising the time):

It is strange, though, that memory gap is about 1.5 GB while snapshot takes about 42 MB. Something is wrong.
This still does not mean that the problem was in the FITS reader, maybe this garbage collection just collects a lot of other things apart from FITS remnants.
Memory still goes upwards though.

Next step would be to inspect which task (if it is task) creates these memory leaks. Need to gradually decreas number of components in the simulation during tests.
But that is the story for another time (#148).

analysis1.txt
analysis2.txt
analysis3.txt
analysis4.txt
analysis5.txt
analysis6.txt
analysis7.txt
analysis8.txt
analysis9.txt


COM-289: Refactor theming of Rte in /admin-rte

Styling of  Rte in /admin-rte is refactored.
Video of Rte:

https://github.com/vivid-planet/comet/assets/122883866/6496ca9e-8697-4caf-afae-53d9c7fc4a8c

Video of disabled Rte:

https://github.com/vivid-planet/comet/assets/122883866/28563d3f-5ae4-4e5a-82a2-f5b0ace65ea8

[ ] Add changeset (if necessary)

@andrearutrecht please resolve the conflicts


[loc][Query][TypeScript] Localizability of strings

Hi,
please help localization team to answer question from translator.
In case translator is not sure about context/meaning/localizability of string we raise a question to Core team.
Thanks in advance for the reply

Id
File Name Live Page Extended
String Resource ID
Full Source String
Query:
Answer:

48,867
LanguageService\TypeScriptVisualStudio\bin\Release\localize\ENU\diagnosticMessages.generated.json
0;   "_0_can_only_be_imported_by_using_import_1_require_2_or_a_default_import_2616"
'{0}' can only be imported by   using 'import {1} = require({2})' or a default import.
Is "import {1} =   require({2}" translatable or is it code?

48,898
LanguageService\TypeScriptVisualStudio\bin\Release\localize\ENU\diagnosticMessages.generated.json
0;   "export_Asterisk_does_not_re_export_a_default_1195"
'export *' does not re-export a   default.
Please explain in detail what   you mean by "a default". Default what?          This may be perfectly clear to a programmer who deals with something like   this every day, but we have to actually make a phrase that will sound   sufficiently clear to a user in our language. So we need some reference as to   what exactly is going on here.

48,970
x86\Tools\DotNetAsync\localize\ENU\DotNetAsync.ScriptResources.resx
".resx", 0;   "TaskCallerActivityLabel"
[Task in]
does it mean "the range   where task exists"?

48,978
LanguageService\TypeScriptVisualStudio\bin\Release\localize\ENU\diagnosticMessages.generated.json
0;   "Its_element_type_0_is_not_a_valid_JSX_element_2789"
Its element type '{0}' is not a   valid JSX element.
Its = whose? What does 'It'   refer to here?          Affected ResourceIDs:     0; "Its_element_type_0_is_not_a_valid_JSX_element_2789"     0; "Its_instance_type_0_is_not_a_valid_JSX_element_2788"     0; "Its_return_type_0_is_not_a_valid_JSX_element_2787"

49,093
LanguageService\TypeScriptVisualStudio\bin\Release\localize\ENU\diagnosticMessages.generated.json
0;   "Remove_all_incorrect_body_block_braces_95115"
Remove all incorrect body block   braces
what does body block braces   mean? is it the same as block body braces?

49,097
LanguageService\TypeScriptVisualStudio\bin\Release\localize\ENU\diagnosticMessages.generated.json
0;   "Remove_all_incorrect_body_block_braces_95115"
Remove all incorrect body block   braces
what does body block braces   mean? is it the same as block body braces?

49,098
LanguageService\TypeScriptVisualStudio\bin\Release\localize\ENU\diagnosticMessages.generated.json
0;   "Remove_all_incorrect_body_block_braces_95115"
Remove all incorrect body block   braces
what does body block braces   mean? is it the same as block body braces?

49,099
LanguageService\TypeScriptVisualStudio\bin\Release\localize\ENU\diagnosticMessages.generated.json
0;   "Remove_block_body_braces_95112"
Remove block body braces
what does body block braces   mean? is it the same as block body braces?

49,101
LanguageService\TypeScriptVisualStudio\bin\Release\localize\ENU\diagnosticMessages.generated.json
0;   "Remove_block_body_braces_95112"
Remove block body braces
what does body block braces   mean? is it the same as block body braces?

Some answers

Id
File Name Live Page Extended
String Resource ID
Full Source String
Query:
Answer:

48,867
LanguageService\TypeScriptVisualStudio\bin\Release\localize\ENU\diagnosticMessages.generated.json
0;   "_0_can_only_be_imported_by_using_import_1_require_2_or_a_default_import_2616"
'{0}' can only be imported by   using 'import {1} = require({2})' or a default import.
Is "import {1} =   require({2}" translatable or is it code?
It is code

48,898
LanguageService\TypeScriptVisualStudio\bin\Release\localize\ENU\diagnosticMessages.generated.json
0;   "export_Asterisk_does_not_re_export_a_default_1195"
'export *' does not re-export a   default.
Please explain in detail what   you mean by "a default". Default what?          This may be perfectly clear to a programmer who deals with something like   this every day, but we have to actually make a phrase that will sound   sufficiently clear to a user in our language. So we need some reference as to   what exactly is going on here.
There is a notion of a "default export". We may change this to 'export *' does not re-export default exports.

48,978
LanguageService\TypeScriptVisualStudio\bin\Release\localize\ENU\diagnosticMessages.generated.json
0;   "Its_element_type_0_is_not_a_valid_JSX_element_2789"
Its element type '{0}' is not a   valid JSX element.
Its = whose? What does 'It'   refer to here?          Affected ResourceIDs:     0; "Its_element_type_0_is_not_a_valid_JSX_element_2789"     0; "Its_instance_type_0_is_not_a_valid_JSX_element_2788"     0; "Its_return_type_0_is_not_a_valid_JSX_element_2787"

49,093
This is an elaboration for using an identifier as a JSX component. It follows on from 'Foo' cannot be used as a JSX component. See more here: https://github.com/microsoft/TypeScript/blob/1f56ab02f064ec45df5ae8747f620a2c070a61f1/tests/baselines/reference/jsxComponentTypeErrors.errors.txt#L17-L18

49,093
LanguageService\TypeScriptVisualStudio\bin\Release\localize\ENU\diagnosticMessages.generated.json
0;   "Remove_all_incorrect_body_block_braces_95115"
Remove all incorrect body block   braces
what does body block braces   mean? is it the same as block body braces?
Yes, I think that is a typo we'll have to correct. https://github.com/microsoft/TypeScript/issues/38225

49,097
LanguageService\TypeScriptVisualStudio\bin\Release\localize\ENU\diagnosticMessages.generated.json
0;   "Remove_all_incorrect_body_block_braces_95115"
Remove all incorrect body block   braces
what does body block braces   mean? is it the same as block body braces?
Yes, I think that is a typo we'll have to correct. https://github.com/microsoft/TypeScript/issues/38225

49,098
LanguageService\TypeScriptVisualStudio\bin\Release\localize\ENU\diagnosticMessages.generated.json
0;   "Remove_all_incorrect_body_block_braces_95115"
Remove all incorrect body block   braces
what does body block braces   mean? is it the same as block body braces?
Yes, I think that is a typo we'll have to correct. https://github.com/microsoft/TypeScript/issues/38225

49,099
LanguageService\TypeScriptVisualStudio\bin\Release\localize\ENU\diagnosticMessages.generated.json
0;   "Remove_block_body_braces_95112"
Remove block body braces
what does body block braces   mean? is it the same as block body braces?

49,101
Yes, I think that is a typo we'll have to correct. https://github.com/microsoft/TypeScript/issues/38225LanguageService\TypeScriptVisualStudio\bin\Release\localize\ENU\diagnosticMessages.generated.json
0;   "Remove_block_body_braces_95112"
Remove block body braces
what does body block braces   mean? is it the same as block body braces?
Yes, I think that is a typo we'll have to correct. https://github.com/microsoft/TypeScript/issues/38225

I need clarification from @minestarks on 48,970.

Please skip 48,970 - this file is not supposed to be localized for this repo, it seems to have gotten mixed into the artifacts by accident somehow.

Thank you


More settings

@kazu-yamamoto this adds a Settings object for the client, in the same way that the server does. A few remarks:

I've moved ../Settings.hs to ../Server/Settings.hs, to avoid confusion with ../Client/Settings.hs
I noticed that the server settings has a few fields prefixed with settings and a few with setting. I didn't change that, but stuck with settings for the fields that I added.
I didn't change any defaults; most importantly, settingsValidateCert defaults to False, which is what you had in your code too. I am not sure if this is the right default (shouldn't clients validate server certificates by default..?) but since you had that as the default, I kept that default. The other default I wasn't sure about is settingsAddrInfoFlags, which I default to [AI_ADDRCONFIG, AI_NUMERICHOST, AI_NUMERICSERV], which is what you had, but again, not sure if this is the right default for all clients.
You are using runTCPServer from network-run but you are not using runTCPClient; I'm sure you have good reasons for doing that, but I was getting some threads being killed in my test suite; I did some comparison between what you're doing here and what runTCPClient does, and I think the crucial difference is that you're using close whereas network-run uses gclose; I've now copied the definition of gclose to http2-tls (it's not exported from network-run), and we're using that instead now.
I have not added any configuration options to runH2C.
I deleted the Show and Eq instance from (Server.)Settings, because it now contains a function. I'm not sure if that is a problem or not.

As always, if there is anything here that you think I should do differently, let me know! :)

This closes #1 btw.

I noticed that the server settings has a few fields prefixed with settings and a few with setting. I didn't change that, but stuck with settings for the fields that I added.

Nice catch! These are typos. May I ask you to fix them?

I didn't change any defaults; most importantly, settingsValidateCert defaults to False, which is what you had in your code too. I am not sure if this is the right default (shouldn't clients validate server certificates by default..?) but since you had that as the default, I kept that default.

This is my bad. Let's turn it into True.

The other default I wasn't sure about is settingsAddrInfoFlags, which I default to [AI_ADDRCONFIG, AI_NUMERICHOST, AI_NUMERICSERV], which is what you had, but again, not sure if this is the right default for all clients.

I don't have strong opinions on this.

If you want to write default values in its document, please use the doctest style.
This ensures consistency of the values and the document.

ou are using runTCPServer from network-run but you are not using runTCPClient; I'm sure you have good reasons for doing that, but I was getting some threads being killed in my test suite; I did some comparison between what you're doing here and what runTCPClient does, and I think the crucial difference is that you're using close whereas network-run uses gclose; I've now copied the definition of gclose to http2-tls (it's not exported from network-run), and we're using that instead now.

I don't remember anything! If you wish, it's OK to use runTCPClient.

Which is more convenient, passing addr/port/etc as function arguments (as the current code) OR adding such fields into Settings?

Nice catch! These are typos. May I ask you to fix them?

Yup, will do.

This is my bad. Let's turn it into True.

Ok.

I don't have strong opinions on this.

Then I think the empty list is probably a better default.

If you want to write default values in its document, please use the doctest style, if possible.

Ok, can do. I deleted that because there is no Show instance anymore due to embedded function. But I can fake it :)

I don't remember anything! If you wish, it's OK to use runTCPClient.

Haha :) Ok, I can give that a go, not sure how important it is. I will try and let you know. It might be better for consistency I guess.

Which is more convenient, passing addr/port/etc as function arguments (as the current code) OR adding such fields into Settings?

The way I see it, Settings are parameters that users may or may not want to change, and have reasonable defaults; address/port/etc. are not in that category. So I think the current split is reasonable?

If you want to write default values in its document, please use the doctest style, if possible.

Ok, can do. I deleted that because there is no Show instance anymore due to embedded function. But I can fake it :)

I'm talking about each field. You don't have to make Sttteings itself as an instance of Show.

The way I see it, Settings are parameters that users may or may not want to change, and have reasonable defaults; address/port/etc. are not in that category. So I think the current split is reasonable?

OK!

I'm talking about each field. You don't have to make Sttteings itself as an instance of Show.

Great minds think alike, that's precisely what I did now :) I've also tested it with cabal-docspec, just to be sure (it will fail for the fields where there is no Show instance, of course).

Haha :) Ok, I can give that [runTCPClient] a go, not sure how important it is. I will try and let you know. It might be better for consistency I guess.

Perhaps the reason you didn't do this is that runTCPClient doesn't allow you to specify any AddrFlag at all. We can leave it for now.
I've pushed one commit for each of the other changes that we discussed. I think this PR is now ready.

Merged. Thank you for your contribution!

Yes, doctest will fail due to the missing Show instances. I guess we can make them not be doctest examples?

Oh, I see you did that already, sorry :)


Fix request render for model loading

A user brought to our attention that in request render mode, renders are being triggered when then are not needed.
As demonstrated in this Sandcastle, the FPS counter continues to display the running FPS. In request render mode, assuming no other operation are happening like camera movement, the FPS counter should display N/A, indicating no new frames are being rendered.
The cause was Model.js, which should only require rendering new frames when loading or processing resources.

Thanks for the pull request @ggetz!

:heavy_check_mark: Signed CLA found.
:grey_question: CHANGES.md was not updated.

If this change updates the public API in any way, please add a bullet point to CHANGES.md.

:grey_question: Unit tests were not updated.

Make sure you've updated tests to reflect your changes, added tests for any new code, and ran the code coverage tool.

Reviewers, don't forget to make sure that:

[ ] Cesium Viewer works.
[ ] Works in 2D/CV.


Inconsistency in displaying logs from stern

Note: this issue was imported from https://github.com/wercker/stern/issues/144, but it was originally created by iamshreeram...
Hi, I'm using below to template -
stern --template '{{.Message}} ({{.Namespace}}/{{color .PodColor .PodName}})' maerts-app -n maerts -o raw --tail 1

Below is the logging
(maerts/2020-07-17 19:20:02,857:INFO:==> On commit: [TopicPartition{topic=prod_app_logs_dfw,partition=0,offset=39364593977,error=None}]
prod-maerts-app-metrics-dum-fix-03-6968cccf7d-8fsv9/prod-maerts-app-metrics-dum-fix-03)%7|1595013602.606|METADATA|09a92702-c7de-11ea-958f-0e5631c8666f#consumer-1| [thrd:main]: <IP_ADDRESS>:9092/5:   Broker #3/4: <IP_ADDRESS>:9092 NodeId 3
(maerts/prod-maerts-app-metrics-dum-fix-03-6968cccf7d-8fsv9/prod-maerts-app-metrics-dum-fix-03)prod-maerts-app-metrics-dum) (maerts/2020-07-17 19:20:02,813:INFO:==> Processed 3 Msgs in 0.13 seconds - 22.85 Msgs/s - 0.0006 MB/s
(maerts/prod-maerts-app-metrics-dum-7d7769cdb5-rtf6b/prod-maerts-app-metrics-dum)prod-maerts-app-metrics-dum-8677c6ff5c-xqm2x/prod-maerts-app-metrics-dum)2020-07-17 19:20:02,832:INFO:==> On commit: [TopicPartition{topic=prod_app_logs_cdc,partition=17,offset=22356383411,error=None}]

My application logs starts with timestamp 2020-07-17 19:20:02,857:==>.
In the first line of log, I don't see the pod or container information.
In the second line, namespace is not available but just container and pod details.
Third line looks good.
Logs are inconsistent. Is there any issue with the switches I'm using or something with with stern itself.

To start a new line, you need to add \n.
stern --template '{{.Message}} ({{.Namespace}}/{{color .PodColor .PodName}})\n' maerts-app -n maerts -o raw --tail 1
```


Grpc: Print binding address

Codecov Report

Merging #606 (8a9e1e4) into main (9fabb42) will decrease coverage by 0.0%.
The diff coverage is 0.0%.

@@           Coverage Diff           @@
##            main    #606     +/-   ##
=======================================
- Coverage    9.3%    9.3%   -0.0%
=======================================
  Files         32      32
  Lines      10621   10622      +1
=======================================
  Hits         987     987
- Misses      9634    9635      +1

Impacted Files
Coverage Δ

src/grpcd/runtime.rs
0.0% <0.0%> (ø)

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 9fabb42...8a9e1e4. Read the comment docs.


Anaconda/pip package compatability issues

I am trying to run this package on my PC. However, I found there are some issues with the compatibility of dependent packages. Can anyone share me with the requirements.yml or requirements.txt by using
pip freeze > frozen-requirements.txt
or
conda env export > requirements.yml
?
Thanks!

I don't know if this helps but I was able to install all the modules in requirements.txt by first installing the following using,
conda install --file requirements.txt with just the following in the requirements.txt.
h5py
shapely
tqdm
pyyaml
mayavi
rtree
scipy
matplotlib

Then I installed the remaining using pip install except for PySide. I was able to install PySide2 though using pip install PySide2.
I couldn't test the code since I have Cuda 11 preinstalled on my device and I have errors coming from TensorFlow :/


bug: Starknet space creation show as failed while tx went through

I've just created a space on Starknet mainnet, in the UI it show that the tx failed but when I look at the tx it looks good. Something is wrong, we should fix this.

Here is the tx:
https://starkscan.co/tx/0x25162bbc4d8d073b51e09070fe83a0b5236881c8d5b5fa4f6972e33933c9b81
Here is the space:
https://snapshot.box/#/sn:0x009fedaf0d7a480d21a27683b0965c0f8ded35b3f1cac39827a25a06a8a682a4

@bonustrack this can happen if request in watchForTransaction fails. For example it used to happen if I used default Infura API key and it ended up being rate limited. Right now it should only happen if request failed 20 times.
What do you think the behaviour should be?
I'm thinking, we should have following failure scenarios, everything else would keep retrying.

We get receipt for transaction and we see it has REVERTED status.
We fail to get receipt for 20 times (in case transaction got dropped by the node somehow), unrelated failures (rate limits, API issues won't count and we would just keep repeating).


Switch to using the buildProject function in Jenkinsfile [WIP]

I'm reasonably sure that the Jenkins build for gds-sso is already broken (see [1]), but maybe this will help.
1: https://ci.integration.publishing.service.gov.uk/job/gds-sso/job/test-branch/1/console

I'm reasonably sure that the Jenkins build for gds-sso is already broken (see [1]), but maybe this will help.

Turns out to be reasonably unrelated, but updating the combustion gem fixes the issue.


2.0 Attachments in auto upgraded DB from 1.x is not accessible through getBlob()

Attachment data from 1.x does not contain "@type" with "blob". So getBlob() does not work.
    {attach1={digest=sha1-P1i5kI/sosq745/9BDR7kEghKps=, length=7, stub=true, revpos=2, content_type=text/plain}}

from Jens:

The new plan is that CBL will recognize an _attachments property and treat dictionaries inside it as blobs. For compatibility with pre-existing documents, and docs replicated (via SG) from 1.x or CouchDB/PouchDB.

Ref: https://github.com/couchbase/couchbase-lite-android/blob/feature/2.0/android/CouchbaseLite/src/androidTest/java/com/couchbase/lite/MigrationTest.java#L81-L87

I believe this should be fixed in lite-core.

from jens

This is intentional. We can't insert the "@type" property because it would modify the revision -- but revisions are immutable.
You'll need to modify Couchbase Lite to recognize this as a blob even without that property.

@borrrden and @pasin Can we discuss the solution when Jim is back?

Everything under _attachments are a blob.
1.x -> /_attachments/photo.png
2.0 -> Docoument.getDictionary("_attachments").getBlob("photo.png")

What needs to be fixed in CBL is that getting a sub-property of "_attachments" should return a Blob object.
@pasin says he doesn't think this is implemented in iOS either.


split into three objects: HanyuPinyin and ToneMarks and TonelessPinyin

Similar to, break up into two separate objects:

https://github.com/pffy/javascript-hanyupinyin
https://github.com/pffy/javascript-tonemarks

googlescript-hanyupinyin
googlescript-tonemarks

both objects should have an empty constructor.

added another object: TonelessPinyin

https://github.com/pffy/pffy/blob/master/obj/lang/TonelessPinyin.md

ok, toneless pinyin for official signage, good idea
running tests now...

v5 tests passed. :+1:
--QA


Broken colors in terminal

Expected behavior
Normal awesomeness from lsd command.
Actual behavior

I am using oh-my-zsh but I have the same behaviour in a bash shell as well.

My lsd version is 0.16.0.

I am not able to reproduce this any more.


Make the Command class macroable

This PR makes the Command class macroable, making in easy to add custom functionality like in https://github.com/laravel/framework/pull/22351.
:octocat:

yah, I thought the point of Macroables was so we could change code that wasn't in userland?


script can not work at ubuntu server 16.04

script can not work at ubuntu server 16.04, install failed

Very useful report.