Allow audio from other apps to continue playing

Use case
I have a video player, using the video_player package, in my app. Whenever a video plays, even if I call setVolume(0.0) before initializing the player, any other audio playing on the device stops.
Proposal
In iOS and Android there are individually ways to declare that your player or even your whole app does not use sound at all, or at least declare that mixing audio is okay. I would love for there to be a way to declare this for flutter apps.
More
I have a StackOverflow question about this, but there haven't been many ideas: https://stackoverflow.com/questions/63984586/how-to-disable-audio-capabilities-for-entire-app.

Hi @banool
Is your proposal to integrate this feature into the video_player plugin?
Can you point to some Android/iOS documentation that shows that this proposal is possible?
Thank you

These settings make it that other audio will keep playing:
In iOS:
try AVAudioSession.sharedInstance().setCategory(
    AVAudioSession.Category.playback,
    mode: AVAudioSession.Mode.default,
    options: [
        AVAudioSession.CategoryOptions.ambient
    ]
)

From here: https://developer.apple.com/documentation/avfoundation/avaudiosession/category.
In Android I can't find how to do it, but I can keep looking.

@banool Is this feature what you are looking for https://github.com/flutter/plugins/pull/2939/files#diff-6b5d92ec170999804dfe2d546ff7162ad2812754fb454d172854a21512b0be66R272 ?

@recastrodiaz I will experiment and see if this does the trick.

Awesome yeah that does the trick, thanks!


Unable to customize DIC services since 2.0

In 1.x, I was able to redefine Deptrac internal services and do practically any customization needed, but since 2.x, deptrac first loads my depfile and then loads its services.php. This breaks any customizaation as I cannot redefine your default services. I understand that adjusting internal stuff is risky and may break in future, but at least I was able to do it somehow. Now I cannot.

This is solved with the release 2.0.3 I think.

@janedbal thanks for your contribution.


Make default client accept gzip and deflate

Make default client accept gzip and deflate
Expose default-client-options so they can be used in custom client creation

Also adding a default Accept: */* would be good as some servers seem to depend on it.

@borkdude if we add Accept: */* as a default, we dont need to add the gzip and deflate right? The decompress interceptors handle it anyways right?

I think the acceptance of encodings is done like this:
(http/get "https://api.stackexchange.com/2.2/sites"
  {:headers {"Accept-Encoding" ["gzip" "deflate"]}})

Ah okay, was confused with the Accept header. Will add these as well.

For the Accept and Accept-Encoding headers, should the provided ones override the defaults or be merged? Since its a array that we need to send?

How I would do it: for a custom client, it uses no options, but the default-client-options should also exposed, so you can pick / merge from those

but when the user uses a default client, the opts provided by the user should be merged into the default-options and then sent? if yes, should it be a deep merge?

Probably yes...

The deep merge seems a bit non-trivial i think, have to deal with a value or a vec of values for these headers and the key could either be a keyword or a string. If you have a suggestion for an deep merge that could handle this, gladly accepted or was thinking to merge only the top level keys. i.e. if the :headers is provided, we would merge the maps from the provided one into the default one and not the value of each of the headers too. Thoughts?

Accept and Accept-Encoding from the provided map would take preference.

curl seems to behave like that:
$ curl https://httpbin.org/get
{
  "args": {},
  "headers": {
    "Accept": "*/*",
    "Host": "httpbin.org",
    "User-Agent": "curl/7.85.0",
    "X-Amzn-Trace-Id": "Root=1-63b9a195-1ee2bec474f1555f3bbf0615"
  },
  "origin": "<IP_ADDRESS>",
  "url": "https://httpbin.org/get"
}

$ curl -H "accept:foo" https://httpbin.org/get
{
  "args": {},
  "headers": {
    "Accept": "foo",
    "Host": "httpbin.org",
    "User-Agent": "curl/7.85.0",
    "X-Amzn-Trace-Id": "Root=1-63b9a1ab-42465b72355fe29626716a5d"
  },
  "origin": "<IP_ADDRESS>",
  "url": "https://httpbin.org/get"
}

Fixed on main branch


Quick attempt to address Django 1.9 issues with the early loading of template tags

Fixes #478. I'm not sure this is the best method of fixing the problem, but as the template tag in question seems to inherit from a class from jinja2, it can't be addressed as easily/cleanly as the issue in django-extensions here: https://github.com/django-extensions/django-extensions/issues/705.

I prefer do something like this:
try:
    from jinja2 import nodes, TemplateSyntaxError
    from jinja2.ext import Extension
except:
    Extension = object

django 1.9 is out. Any idea how to handle this? ping @cyberdelia

It's a bit too extreme to disable most of the code when jinja2 si not present, so I took another route, see #514.
Thanks a lot for taking the time to try to fix it :bowtie:


Yvess/add multistate example gce 839

Description:
Adds an example Jupyter notebook and utility functions for multistate discrimination.
Checklist:

[ ] Add tests for the change to show correct behavior.
[ ] Add or update relevant docs, code and examples.
[ ] Update CHANGELOG.rst with relevant information and add the issue number.
[ ] Add .. versionchanged:: where necessary.

@markheik : I kind of like the suggestion to group the Jupyter notebook together with the CSV file in a folder.
The only concern I have is that it kind of breaks the existing flat structure, where all the Jupyter notebooks are in the same folder. This might be an issue for some tooling such as the script generate_notebooks.sh. Thus, I prefer to leave this decision up to you and @tobiasah .

I kind of like the suggestion to group the Jupyter notebook together with the CSV file in a folder.
The only concern I have is that it kind of breaks the existing flat structure, where all the Jupyter notebooks are in the same folder. This might be an issue for some tooling such as the script generate_notebooks.sh. Thus, I prefer to leave this decision up to you and @tobiasah .

Let's just leave it how it is for now. We can change it later if needed.


build: remove unused platform support

This PR removes support for unused platforms.
Currently I just deleted the ios folder and removed it from version control, as none of us are actually building Gibsonify for iOS. I was thinking of doing the same for macos and web, but since we use these versions in the development process, even though we could have them locally and not checked into version control, if we needed to hard reset from origin at some point, we could lose some local configuration, so I decided to not delete these. If we wanted to disable support for them in the future, this outlines the steps.

Looks good - am for trying to remove macos and web support too

@sshazril would you suggest I remove both macos and web in this PR too?

Looks good - am for trying to remove macos and web support too

@sshazril would you suggest I remove both macos and web in this PR too?

I'd say it's not a priority with the other things we have on the to-do list but you're welcome to if you'd like.

Looks good - am for trying to remove macos and web support too

@sshazril would you suggest I remove both macos and web in this PR too?

I'd say it's not a priority with the other things we have on the to-do list but you're welcome to if you'd like.

Done 😊


@override is not detected when re-exported

https://github.com/astral-sh/ruff/issues/3910 is great! However, it does not work for me when re-exporting override:
override.py
__all__ = ["override"]
from typing_extensions import override

bug.py
from override import override

@override
def BAD_FUN() -> None:
    pass

ruff bug.py --select N802 --isolated
Python 3.11.4, ruff 0.0.275

Output:
bug.py:5:5: N802 Function name `BAD_FUN` should be lowercase

Can you try marking your override module via typing-modules?


Support for mixed SASS and SCSS projects

My project uses SASS, but consumes bourbon, which uses SCSS. Since I have to set the indentedSyntax flag for the full build, it seems that I can't currently use both.

@bcherny I have encountered the same problem. As much as I hate to admit it, I have had to deal with it impromptu and implemented a hack. But it's a neat hack :)
var	gulp = require("gulp"),
	sass = require("gulp-sass");

var sassSource = "css/source";
var options = {
	sass: { style: "nested", indentedSyntax: true },
	scss: { style: "nested" }
};

function compileSass (extension) {
	gulp.src(sassSource + "/include.sass") // This can also be include.scss
		.pipe(sass(options[extension]))
		.pipe(gulp.dest("css"));
}

gulp.task("sass", function () { compileSass("sass"); });
gulp.task("scss", function () { compileSass("scss"); });

gulp.task("default", function () {
	gulp.watch(sassSource + "/**/*.sass", ["sass"]);
	gulp.watch(sassSource + "/**/*.scss", ["scss"]);
});

While sass syntax is supposed to have feature parity with scss my feeling is that edge cases will be way more frequent in sass syntax. That being said, I believe this is related to the compiler itself (libsass) and not with gulp-sass.
Maybe @dlmanning can confirm this.

We could use the file extension to pass https://github.com/sass/node-sass#indentedsyntax on a per-file basis I suppose

It seems like this is solved directly by node-sass/libsass in the next version, can you (@bcherny or @slavomirvojacek ) try the 2.x branch of gulp-sass and report on #222  of any bugs happening relating to that?

Resolved by #222


About Pinocchio code generation

Dear @plancherb1,
Thanks for sharing this set of benchmarks.
I wonder why your are not also comparing with Pinocchio code gen support, which can be up to 10 times faster than standard CPU compiled code?
Best,
Justin

Hi Justin,
Correct me if I did it wrong but I did try to use only the codegen for all
of my timing. If you look at the file I used for timing
https://github.com/robot-acceleration/GRiDBenchmarks/blob/main/timePinocchio.cpp
I only used the standard functions to set up variables and to do print
based testing of values. It should be all codegen for timing. I also built
using the pinnochio3-preview branch as I assumed that would be the fastest,
most up-to-date version of the code. And for multi threading I put together
a small threading wrapper which I found outperformed threadpools and
std::threads to make sure the CPU timing was as fast as I knew how to get
it. Do let me know if there is a way to have Pinocchio run faster. I’d be
more than happy to update it and my apologies if I did something wrong with
the codegen!
Best,
Brian
On Sat, Sep 18, 2021 at 7:33 AM Justin Carpentier @.***>
wrote:

Dear @plancherb1 https://github.com/plancherb1,
Thanks for sharing this set of benchmarks.
I wonder why your are not also comparing with Pinocchio code gen support,
which can be up to 10 times faster than standard CPU compiled code?
Best,
Justin
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/robot-acceleration/GRiDBenchmarks/issues/1, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AA75GTZOKLP22LMVS555VCTUCR2HNANCNFSM5EJDV4NQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Thanks, Brian for the quick answer.
I was looking at your paper, and this was not clear when reading it. Thanks for the clarification.
Reading your code, I can observe that you have a lot of allocation when performing the matrix/vector multiplication which will affect drastically the performances. You should use the noalias keywords especially in these lines:
https://github.com/robot-acceleration/GRiDBenchmarks/blob/50365b648a2d714bce15dd59bf043ec3769f5d8e/timePinocchio.cpp#L134-L135
In addition, https://github.com/robot-acceleration/GRiDBenchmarks/blob/50365b648a2d714bce15dd59bf043ec3769f5d8e/timePinocchio.cpp#L41-L44
performs so computations that might be avoided if you were using a dedicated pass which assumes a zero-wise acceleration using the Eigen::VectorXd:Zero() expression. I do think it would be more efficient to use a dedicated implementation of the CodeGen using NLE function.
I think this line is not correct:
https://github.com/robot-acceleration/GRiDBenchmarks/blob/50365b648a2d714bce15dd59bf043ec3769f5d8e/timePinocchio.cpp#L213
as it assumes that you don't have any quaternion part in your configuration vector, which is not the case with ATLAS for instance.
Concerning your thread, why this choice while OpenMP could do the same?
I think the size of your binaries may affect the performances. I would split the tests into several independent files to increase the performance. For instance, I do not know the impact of these lines:
https://github.com/robot-acceleration/GRiDBenchmarks/blob/50365b648a2d714bce15dd59bf043ec3769f5d8e/timePinocchio.cpp#L198-L203
and how much it will perform several loading. It should be check at some point.
Finally, we are preparing the support for codegen on GPU on Pinocchio. It will be interesting to compare with your setup.

Similarly to what nvcc does with Cuda, I will try to also use the vectorization of your CPU (march=native at least).
This is not the case here. Additionally, I've realized that the matrices order matters a lot.
You should use the same matrix ordering as the default one used in Pinocchio to speed up the computations. I do think with all the previous remarks, you should obtain better performances with CPU pipelines.

Thanks for all of the feedback I will try to get that incorporated soon! Also I'd love to talk to you about / help contribute with GPU Pinocchio -- I'm not experienced with your codegen tools -- but would love to help however I can (also if you have some good pointers for getting up to speed on CppAD and CppADCodegen do send them my way). I am very curious to see how they perform on the GPU. I wonder if they can optimize for multi-gpu threads within a single computation or just across computations.
A couple of followups below to make sure I understand all of your suggestions correctly so I can implement:

For the noAlias() are you suggesting that those lines (and similar lines for qdd) simply be replaced by dqdd_dqs[k].noAlias() = -(minv_code_gen->Minv)*(rnea_derivatives_code_gen->dtau_dq);
What do you mean by "a dedicated implementation of the CodeGen using NLE function"? Do you mean constructing a new codegen function which does not take in a qdd? I can try but could then definitely use some pointers on how to use those codegen tools then for sure lol
In these comparisons I did not use a floating base and so I believe that therefore in Pinocchio you do not have a quaternion to worry about. Also I did try to run codegen with a floating base (and a correct quaternion input) using Pinocchio and got a whole lot of segfaults (this may have been fixed in the past month since I pulled and/or I may have done something wrong but/and heads up on that -- I was actually going to send you a note this weekend now that I got the paper out) and so I didn't push to implement and test it for GRiD either (that's on my list for the next few weeks). I do think moving to floating base should change up both timings a bit and am curious to benchmark GRiD vs. your floating base codegen once I have both working.
I didn't use OpenMP because I did some testing about a year ago and my implementation beat the standard threadpool and so I just stuck with what I knew to previously be faster to try to give your code as fair of a test as possible (and if you recall there was a weird error building Pinocchio with OpenMP when I was trying to build). I should probably check back with the most recent version of OpenMP to see if that has changed. I believe the reason for the previous performance win is that in the way that I use my implementation, each thread is continuously hitting the same memory locations in the q, qd, and result arrays and so it leads to better cache performance.
I also did the multiple initializations of the code_gen objects because my hope was that the runtime would allocate different CPUs for different threads and then I didn't want them having to access serially the same object residing in the memory of the first core (or having to try to ensure cache coherence across cores) to run the codegen and I was also worried it might lead to concurrency bugs. If you think I should have all the threads hit the same object I can try that too.
Am I using a different matrix ordering? I don't think I changed things away from default?

Thanks again for all the feedback! I do want to be as fair as possible and honestly was wildly impressed with the speed of codegen on a single computation. It really made me work a lot harder to get wins on the GPU lol :)

I suggest having a private discussion after I'm back from holidays (until October, 4th).

* For the `noAlias()` are you suggesting that those lines (and similar lines for qdd) simply be replaced by `dqdd_dqs[k].noAlias() = -(minv_code_gen->Minv)*(rnea_derivatives_code_gen->dtau_dq);`

Yes, with noalias.
For the best performances, Minv should be row major as left operand while dtau_dq should be col major.
In the current implementation, Minv is col major because it was just used for bench, not to be used as an operand.

* I didn't use OpenMP because I did some testing about a year ago and my implementation beat the standard threadpool and so I just stuck with what I knew to previously be faster to try to give your code as fair of a test as possible (and if you recall there was a weird error building Pinocchio with OpenMP when I was trying to build). I should probably check back with the most recent version of OpenMP to see if that has changed. I believe the reason for the previous performance win is that in the way that I use my implementation, each thread is continuously hitting the same memory locations in the q, qd, and result arrays and so it leads to better cache performance.

Sounds interesting, it would be nice to explore it a bit more to understand why your implementation can be faster than OpenMP.
OpenMP works perfectly with Pinocchio (at least Mac and Linux).

Sounds great lets definitely re-connect when you are back, and I'll try to make some of those changes in the meantime.
Does it make the most sense for you to just send me an email when you are back and settled back in and we can find a time to chat? If that works for you I'm<EMAIL_ADDRESS>Alternatively happy to work to calendar something now!
Enjoy your vacation!


How can i remove my account from your website?????

Hi, i want to remove my account, how  can i do it?

Hi @flufli , thank you for the issue, we need to implement this functionality.


Comment cleanup

This is a coarse cleanup of commented code in make_watertight as requested by @gonuke after the update to the new MOAB 4.9.0 header conventions.

Have a look when you get a chance @makeclean & @gonuke

Thanks @Pshriwise - removing code is a real contribution!

Thanks @Pshriwise - removing code is a real contribution!


Develop and test CQL logic for eGFR calculation

Dave will write an email to Dave Dorr to validate the approach and determine due date for testing


spring-boot build

Hello
code: https://github.com/PlumpMath/gurupoo
When attempting to generate the 'mvn2nix-lock.json' file using the
'mvn2nix > mvn2nix-lock.json' command, an error occurred.
As a workaround, the
mvn2nix --goals clean > mvn2nix-lock.json
command was used to successfully generate the file.
This is a very simple Spring project that can be executed using 'mvn spring-boot:run' without any involvement of Nix, and accessed via 'localhost:8080/hello?name=helloworld'.
To generate a JAR file, the commands 'mvn clean package spring-boot:repackage' or 'mvn clean install spring-boot:repackage' (without 'clean') can be used.
However, attempting to build the project using Nix results in an error.
Thanks.

solve.

When I tried building it in user mode with nix-build, I got this error on NixOS.
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[FATAL] Non-resolvable parent POM for plumpmath:gurupoo:0.0.1-SNAPSHOT: Could not transfer artifact org.springframework.boot:spring-boot-starter-parent:pom:2.7.11 from/to central (https://repo.maven.apache.org/maven2): transfer failed for https://repo.maven.apache.org/maven2/org/springframework/boot/spring-boot-starter-parent/2.7.11/spring-boot-starter-parent-2.7.11.pom and 'parent.relativePath' points at no local POM @ line 5, column 11
 @
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR]   The project plumpmath:gurupoo:0.0.1-SNAPSHOT (/build/source/pom.xml) has 1 error
[ERROR]     Non-resolvable parent POM for plumpmath:gurupoo:0.0.1-SNAPSHOT: Could not transfer artifact org.springframework.boot:spring-boot-starter-parent:pom:2.7.11 from/to central (https://repo.maven.apache.org/maven2): transfer failed for https://repo.maven.apache.org/maven2/org/springframework/boot/spring-boot-starter-parent/2.7.11/spring-boot-starter-parent-2.7.11.pom and 'parent.relativePath' points at no local POM @ line 5, column 11: Unknown host repo.maven.apache.org: Temporary failure in name resolution -> [Help 2]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
[ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException

error: builder for '/nix/store/xnajxhhb3lf7g4mgibqmbh5zld62rj7g-gurupoo-0.0.1-SNAPSHOT.drv' failed with exit code 1;
       last 10 log lines:
       > [ERROR]   The project plumpmath:gurupoo:0.0.1-SNAPSHOT (/build/source/pom.xml) has 1 error
       > [ERROR]     Non-resolvable parent POM for plumpmath:gurupoo:0.0.1-SNAPSHOT: Could not transfer artifact org.springframework.boot:spring-boot-starter-parent:pom:2.7.11 from/to central (https://repo.maven.apache.org/maven2): transfer failed for https://repo.maven.apache.org/maven2/org/springframework/boot/spring-boot-starter-parent/2.7.11/spring-boot-starter-parent-2.7.11.pom and 'parent.relativePath' points at no local POM @ line 5, column 11: Unknown host repo.maven.apache.org: Temporary failure in name resolution -> [Help 2]
       > [ERROR]
       > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
       > [ERROR] Re-run Maven using the -X switch to enable full debug logging.
       > [ERROR]
       > [ERROR] For more information about the errors and possible solutions, please read the following articles:
       > [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
       > [ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
       >
       For full logs, run 'nix log /nix/store/xnajxhhb3lf7g4mgibqmbh5zld62rj7g-gurupoo-0.0.1-SNAPSHOT.drv'.

https://discourse.nixos.org/t/help-packaging-a-java-application/32326/5


fix for TIKA-3400 contributed by kamaci

@tballison I've updated the PR. Checks fail due to MP4ParserTest.java:101. I don't get same exception at my local environment. Do you have any idea about the reason?

I was just able to replicate that in Java 11 on a Mac.  ubuntu w Java 8 passes... Ugh... I pushed a simple fix for now.

@tballison is there anything left to do for this PR?


Settings dialog not scaled properly on HiDPI displays

The Mozc settings dialog looks like this and is not resizable:

I'm using the mozc-ut package from the Arch User Repository (slightly patched to build 453df28947459f2730643fbeea665448d8d1d86e) with a 15.5" 3K display.

Thank you for reporting this issue.  We are aware of this issue, and we plan to address this kind of issues as a part of our Qt 5 migration (#327).  For now I'm going to close this one since we don't plan to address this in our Qt 4 version of mozc_tool.  Please subscribe #327 if you are interested in the progress on our Qt 5 migration.
Just FYI, this is not specific to Linux version.

Google Japanese Input Help Forum - WindowsのDPIスケーリング
Google Japanese Input Help Forum - Windowsのhigh DPIモードへの対応

Seems that Qt project plans to introduce cross-platform HiDPI support in Qt 5.6, which is going to be shipped soon.


Use @mixin instead of @extend

New syntax:

.parent {
     // Declare grid with modifiers
    @include g(center, middle);
}

.child {
   // Declare grid-item with width / responsive widths
  @include i(1/2, lap 1/3, desk 1/4);

  // Include push/pull (same arg-syntax as i)
  @include push(desk 2/5);
}

Contents:

Concise & precise new syntax
By default light wrapper around flexbox
Cleaner margin / padding-approach
Remove standalone version
Use DRYed mixins in favor of extends - much smarter and better traceable output css
Infinite columns / ratio-based
Embrace the *-selector for some modifiers. Modern browsers can handle it well
Remove visibility-classes

Todo:

[x]  Update Readme
[x] Write Tests
[x] Code Cleanup & Comments
[x] Crossbrowser Tests

Boom! :+1:


Can't run individual test methods from IntelliJ

For tests with method variations it seems like you can't run an individual test from IntelliJ, only all the tests in a class.

java.lang.Exception: No tests found matching Method multiple(com.squareup.burst.MethodTest) from org.junit.internal.requests.ClassRequest@2e26c3a1
at org.junit.internal.requests.FilterRequest.getRunner(FilterRequest.java:35)
at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:41)
at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:211)
at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:67)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at com.intellij.rt.execution.application.AppMain.main(AppMain.java:134)

Haven't really thought about if there's a fix or if it even matters.

I'm unable to run an individual test case from the latest Android Studio when I have @RunWith(BurstJUnit4::class) on the test class. (Burst v1.2.0). When I comment out that annotation (and whichever test(s) need Burst), then I can run individual test methods again.
This was definitely observed on Android Studio 4.0.2 and 4.1. I thought I'd seen this behavior prior to Android Studio 4.0 as well, but I hadn't considered the connection to Burst so I didn't test that at the time.
This is mainly significant when I'm trying to debug test runs after refactoring a class.


Fix RSS URLs treated as internal

Emily noticed that RSS URLs are treated as internal atm. This fixes that.
Test post: https://bsky.app/profile/emily.bsky.social/post/3kn52xdg3cc2a

Work on web but on native it's giving useOpenLink the value /profile/haileyok.com/rss. We might need a router update for this too (I guess could also just prepend https://bsky.app if the url starts with / but that doesn't feel good)

@haileyok I think it's OK to prepend the host, since we DO want RSS links to open in a browser. Right?
But we do need some sort of router update to handle Safari trying to link the user back to the app, which results in a 404.

Okay yea, that should be fine. As for the Safari issue, yea the router is probably trying to push to the same relative path I think...maybe the router should just push to the profile page in that case?

Yeah I think just route to profile is fine. Not sure what else we could do since iOS will try to universal link to the app for those URLs 🤔

Okay, this might be a solution. We can modify the router to allow for an array of possible paths rather than a single one.
That being said, now need to make sure that the Go server is handling /rss for us before we even hit the router. Going to build and see.

Okay yea, this works. The go server handles the RSS on its own:
	// profile RSS feed (DID not handle)
	e.GET("/profile/:ident/rss", server.WebProfileRSS)

The router will still catch /rss here though on native since the deeplink goes to bluesky:// instead of the Go server. Might be useful to have multiple routes for another reason in the future anyway.


App::FilterEvent(wxEvent& e) should not use many ifs

This greatly slows the application, as each message is checked against 20 or more ifs

For now I am closing this issue as now events are processed faster. Later we could use array for mouse events in order to speedup their processing


Minimal API Authorization example not working

Trying the Authorization example and got an error.
Example:
using Microsoft.AspNetCore.Authorization;

var builder = WebApplication.CreateBuilder(args);
builder.Services.AddAuthorization(o => o.AddPolicy("AdminsOnly",
                                  b => b.RequireClaim("admin", "true")));
var app = builder.Build();
app.UseAuthorization();
app.MapGet("/auth", [Authorize] () => "This endpoint requires authorization.");
app.Run();

Exception:
System.InvalidOperationException: No service for type 'Microsoft.AspNetCore.Authentication.IAuthenticationService' has been registered.
   at Microsoft.Extensions.DependencyInjection.ServiceProviderServiceExtensions.GetRequiredService(IServiceProvider provider, Type serviceType)
   at Microsoft.Extensions.DependencyInjection.ServiceProviderServiceExtensions.GetRequiredService[T](IServiceProvider provider)
   at Microsoft.AspNetCore.Authentication.AuthenticationHttpContextExtensions.ChallengeAsync(HttpContext context, String scheme, AuthenticationProperties properties)
   at Microsoft.AspNetCore.Authentication.AuthenticationHttpContextExtensions.ChallengeAsync(HttpContext context)
   at Microsoft.AspNetCore.Authorization.Policy.AuthorizationMiddlewareResultHandler.HandleAsync(RequestDelegate next, HttpContext context, AuthorizationPolicy policy, PolicyAuthorizationResult authorizeResult)
   at Microsoft.AspNetCore.Authorization.AuthorizationMiddleware.Invoke(HttpContext context)
   at Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware.Invoke(HttpContext context)

Using .NET6.0

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

ID: b09824ab-b051-75a1-13b7-b0e281cc46e0
Version Independent ID: b09824ab-b051-75a1-13b7-b0e281cc46e0
Content: Minimal APIs overview
Content Source: aspnetcore/fundamentals/minimal-apis.md
Product: aspnet-core
Technology: aspnetcore-fundamentals
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

I was just showing the endpoint syntax but I should have shown a complete example
using Microsoft.AspNetCore.Authorization;
using Microsoft.AspNetCore.Identity;
using Microsoft.EntityFrameworkCore;
using WebRPauth.Data;

var builder = WebApplication.CreateBuilder(args);
builder.Services.AddAuthorization(o => o.AddPolicy("AdminsOnly",
                                  b => b.RequireClaim("admin", "true")));

var connectionString = builder.Configuration.GetConnectionString("DefaultConnection");
builder.Services.AddDbContext<ApplicationDbContext>(options =>
    options.UseSqlServer(connectionString));
builder.Services.AddDatabaseDeveloperPageExceptionFilter();

builder.Services.AddDefaultIdentity<IdentityUser>(options => options.SignIn.RequireConfirmedAccount = true)
    .AddEntityFrameworkStores<ApplicationDbContext>();

var app = builder.Build();

app.UseAuthorization();

app.MapGet("/auth", [Authorize] () => "This endpoint requires authorization.");
app.MapGet("/", () => "This endpoint doesn't require authorization.");

app.Run();


docs(restructure): restructure content -> more readable

Description
This PR doesn't change the content (at least I hope so) but it restructures the documentation in a way, that it is more readable (at least from my perspective) ⇾ Of course, everybody can have here his/her opinion.
If you don't like the change, let's just delete it.

split README.md in several files
make them more readable
not content was replaced, just restructured

Pre-review checks
Please ensure to do as many of the following checks as possible, before asking for committer review:

[X] DEPENDENCIES are up-to-date. Dash license tool. Committers can open IP issues for restricted libs.
[X] Copyright and license header are present on all affected files

Not sure about the failed check. Did I something wrong?

Not sure about the failed check. Did I something wrong?

won't be an issue anymore once you move everything into the docs directory on root level, see https://github.com/eclipse-tractusx/tractus-x-umbrella/blob/main/.github/workflows/helm-checks.yaml#L25

@evegufy  let's give it a second try :)

Hey @stephanbcbauer.
The work and the restructuring done are incredible, everything is much more readable and orderly, especially for users who enter for the first time and want to know the repository.

Hopefully, I managed all the changes ...  it's difficult to keep the overview @mgarciaLKS @evegufy


whats the 39 for ?

Not really an issue , this is an awesome plugin ! never knew you could do so much , with so little , one question , what the 39 in the code for ?
https://github.com/sbstjn/timesheet.js/blob/master/source/javascripts/timesheet.js#L35
On the above line i mean.
Thank you.

The portion of the line is:
Math.round((cur.end-cur.start)/1000/60/60/24/39)

That takes the time in MS, and then divides by 1000 (seconds), 60 (Minutes), 60 (hours), 24 (days), and 39 (months???)
39 is in the place where days in a month should go, but it doesn't make sense. I think this could be a bug.


complication to run function to v studio

Does this occur consistently?
Repro steps:

Action: azureFunctions.deploy
Error type: Error
Error Message: The remote runtime "powershell" for function app "Weslin" does not match your local runtime "node".
Version: 1.0.1
OS: win32
OS Release: 10.0.18363
Product: Visual Studio Code
Product Version: 1.51.1
Language: en

Call Stack
extension.bundle.js:451:397799extension.bundle.js:451:397799
extension.bundle.js:451:397297extension.bundle.js:451:397297
a extension.bundle.js:451:396983
verifyVersionAndLanguage extension.bundle.js:451:397515
Object.<anonymous> extension.bundle.js:451:398520
fulfilled extension.bundle.js:451:397051
processTicksAndRejections task_queues.js:94:5

Hi @bbiayi10
What runtime is your function project?  The remote and local runtimes don't match.  If your project is node, you should create a node.js function app.


Multiple file compile without error and without json

Can't seem to compile multiple json files into one object. Wish I could post files but it stops after first two files and doesn't give an error. Issue is resolved when merge is set to false and files are separated into objects. "This is still very useable though"

It loads only 2 files at a time and then degrades gracefully without any errors or messages. All json files have been parsed using https://jsonformatter.curiousconcept.com/

Should be fixed now, i had read wrong how the merge library worked and thought it would merge more then one file at a time


Error when running demo.py: No module named '_ext'

Can you explain what this import is doing in path_nms.py?
from _ext import nms
It's preventing me from running the demo script.  I'm using Python 3.6.

Did you follow the fourth step of https://github.com/ruotianluo/pytorch-faster-rcnn#installation ?

Yes, it seems to run fine, here is the output:
Including CUDA code. /home/leow/pytorch-faster-rcnn/lib/nms generating /tmp/tmpyk65xa34/_nms.c running build_ext building '_nms' extension creating home creating home/leow creating home/leow/pytorch-faster-rcnn creating home/leow/pytorch-faster-rcnn/lib creating home/leow/pytorch-faster-rcnn/lib/nms creating home/leow/pytorch-faster-rcnn/lib/nms/src gcc -pthread -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -DWITH_CUDA -I/home/leow/anaconda3/lib/python3.6/site-packages/torch/utils/ffi/../../lib/include -I/home/leow/anaconda3/lib/python3.6/site-packages/torch/utils/ffi/../../lib/include/TH -I/home/leow/anaconda3/lib/python3.6/site-packages/torch/utils/ffi/../../lib/include/THC -I/usr/local/cuda/include -I/home/leow/anaconda3/include/python3.6m -c _nms.c -o ./_nms.o gcc -pthread -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -DWITH_CUDA -I/home/leow/anaconda3/lib/python3.6/site-packages/torch/utils/ffi/../../lib/include -I/home/leow/anaconda3/lib/python3.6/site-packages/torch/utils/ffi/../../lib/include/TH -I/home/leow/anaconda3/lib/python3.6/site-packages/torch/utils/ffi/../../lib/include/THC -I/usr/local/cuda/include -I/home/leow/anaconda3/include/python3.6m -c /home/leow/pytorch-faster-rcnn/lib/nms/src/nms.c -o ./home/leow/pytorch-faster-rcnn/lib/nms/src/nms.o In file included from /home/leow/anaconda3/lib/python3.6/site-packages/torch/utils/ffi/../../lib/include/TH/TH.h:4:0,                  from /home/leow/pytorch-faster-rcnn/lib/nms/src/nms.c:1: /home/leow/pytorch-faster-rcnn/lib/nms/src/nms.c: In function ‘cpu_nms’: /home/leow/pytorch-faster-rcnn/lib/nms/src/nms.c:7:42: warning: passing argument 1 of ‘THLongTensor_isContiguous’ from incompatible pointer type [-Wincompatible-pointer-types]      THArgCheck(THLongTensor_isContiguous(boxes), 2, "boxes must be contiguous");                                           ^ /home/leow/anaconda3/lib/python3.6/site-packages/torch/utils/ffi/../../lib/include/TH/THGeneral.h:78:35: note: in definition of macro ‘THArgCheck’    _THArgCheck(__FILE__, __LINE__, __VA_ARGS__);                       \                                    ^ /home/leow/anaconda3/lib/python3.6/site-packages/torch/utils/ffi/../../lib/include/TH/THTensor.h:8:39: note: expected ‘const THLongTensor * {aka const struct THLongTensor *}’ but argument is of type ‘THFloatTensor * {aka struct THFloatTensor *}’  #define THTensor_(NAME)   TH_CONCAT_4(TH,Real,Tensor_,NAME)                                        ^ /home/leow/anaconda3/lib/python3.6/site-packages/torch/utils/ffi/../../lib/include/TH/THGeneral.h:116:37: note: in definition of macro ‘TH_CONCAT_4_EXPAND’  #define TH_CONCAT_4_EXPAND(x,y,z,w) x ## y ## z ## w                                      ^ /home/leow/anaconda3/lib/python3.6/site-packages/torch/utils/ffi/../../lib/include/TH/THTensor.h:8:27: note: in expansion of macro ‘TH_CONCAT_4’  #define THTensor_(NAME)   TH_CONCAT_4(TH,Real,Tensor_,NAME)                            ^ /home/leow/anaconda3/lib/python3.6/site-packages/torch/utils/ffi/../../lib/include/TH/generic/THTensor.h:115:12: note: in expansion of macro ‘THTensor_’  TH_API int THTensor_(isContiguous)(const THTensor *self);             ^ /home/leow/pytorch-faster-rcnn/lib/nms/src/nms.c:9:42: warning: passing argument 1 of ‘THLongTensor_isContiguous’ from incompatible pointer type [-Wincompatible-pointer-types]      THArgCheck(THLongTensor_isContiguous(areas), 4, "areas must be contiguous");                                           ^ /home/leow/anaconda3/lib/python3.6/site-packages/torch/utils/ffi/../../lib/include/TH/THGeneral.h:78:35: note: in definition of macro ‘THArgCheck’    _THArgCheck(__FILE__, __LINE__, __VA_ARGS__);                       \                                    ^ /home/leow/anaconda3/lib/python3.6/site-packages/torch/utils/ffi/../../lib/include/TH/THTensor.h:8:39: note: expected ‘const THLongTensor * {aka const struct THLongTensor *}’ but argument is of type ‘THFloatTensor * {aka struct THFloatTensor *}’  #define THTensor_(NAME)   TH_CONCAT_4(TH,Real,Tensor_,NAME)                                        ^ /home/leow/anaconda3/lib/python3.6/site-packages/torch/utils/ffi/../../lib/include/TH/THGeneral.h:116:37: note: in definition of macro ‘TH_CONCAT_4_EXPAND’  #define TH_CONCAT_4_EXPAND(x,y,z,w) x ## y ## z ## w                                      ^ /home/leow/anaconda3/lib/python3.6/site-packages/torch/utils/ffi/../../lib/include/TH/THTensor.h:8:27: note: in expansion of macro ‘TH_CONCAT_4’  #define THTensor_(NAME)   TH_CONCAT_4(TH,Real,Tensor_,NAME)                            ^ /home/leow/anaconda3/lib/python3.6/site-packages/torch/utils/ffi/../../lib/include/TH/generic/THTensor.h:115:12: note: in expansion of macro ‘THTensor_’  TH_API int THTensor_(isContiguous)(const THTensor *self);             ^ gcc -pthread -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -DWITH_CUDA -I/home/leow/anaconda3/lib/python3.6/site-packages/torch/utils/ffi/../../lib/include -I/home/leow/anaconda3/lib/python3.6/site-packages/torch/utils/ffi/../../lib/include/TH -I/home/leow/anaconda3/lib/python3.6/site-packages/torch/utils/ffi/../../lib/include/THC -I/usr/local/cuda/include -I/home/leow/anaconda3/include/python3.6m -c /home/leow/pytorch-faster-rcnn/lib/nms/src/nms_cuda.c -o ./home/leow/pytorch-faster-rcnn/lib/nms/src/nms_cuda.o /home/leow/pytorch-faster-rcnn/lib/nms/src/nms_cuda.c: In function ‘gpu_nms’: /home/leow/pytorch-faster-rcnn/lib/nms/src/nms_cuda.c:29:35: warning: initialization from incompatible pointer type [-Wincompatible-pointer-types]    unsigned long long* mask_flat = THCudaLongTensor_data(state, mask);                                    ^ /home/leow/pytorch-faster-rcnn/lib/nms/src/nms_cuda.c:37:40: warning: initialization from incompatible pointer type [-Wincompatible-pointer-types]    unsigned long long * mask_cpu_flat = THLongTensor_data(mask_cpu);                                         ^ /home/leow/pytorch-faster-rcnn/lib/nms/src/nms_cuda.c:40:39: warning: initialization from incompatible pointer type [-Wincompatible-pointer-types]    unsigned long long* remv_cpu_flat = THLongTensor_data(remv_cpu);                                        ^ /home/leow/pytorch-faster-rcnn/lib/nms/src/nms_cuda.c:23:7: warning: unused variable ‘boxes_dim’ [-Wunused-variable]    int boxes_dim = THCudaTensor_size(state, boxes, 1);        ^ gcc -pthread -shared -L/home/leow/anaconda3/lib -Wl,-rpath=/home/leow/anaconda3/lib,--no-as-needed ./_nms.o ./home/leow/pytorch-faster-rcnn/lib/nms/src/nms.o ./home/leow/pytorch-faster-rcnn/lib/nms/src/nms_cuda.o /home/leow/pytorch-faster-rcnn/lib/nms/src/cuda/nms_kernel.cu.o -L/home/leow/anaconda3/lib -lpython3.6m -o ./_nms.so

I guess it's because I'm running under python 2.7.
Try:
from ._ext import nms

Yes, the directory imports are different in 3.6. That fix worked for the issue.


Audit dependencies

Fixes #173
Proposed Changes

Remove rooks dependency and use regular useEffect again
Remove unused dev dependencies
Sort keys in package.json blocks
Remove unused test streams helper
Change TS output location to avoid duplicated index.d.ts on build
Update and apply a security audit to remaining dependencies

Additional Notes (optional)
N / A

@jamesrweb I was wondering if this PR can go directly to the main?

@yevdyko its based on the other branch so sadly not. Merging now since you approved. 😊


Geometry Typing Fixes

Fixes #6117

Codecov Report

Merging #6118 into dev will increase coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##              dev    #6118      +/-   ##
==========================================
+ Coverage   70.91%   70.92%   +<.01%
==========================================
  Files         209      209
  Lines       10657    10657
==========================================
+ Hits         7557     7558       +1
+ Misses       3100     3099       -1

Impacted Files
Coverage Δ

packages/core/src/geometry/Geometry.js
41.35% <ø> (ø)
:arrow_up:

packages/ticker/src/Ticker.js
87.59% <0%> (+0.77%)
:arrow_up:

Continue to review full report at Codecov.

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


[New Feature] Upgrade Apache Airflow to latest version 2.10.3

The latest version of Apache Airflow is 2.10.3. This includes a fix for this issue (from 2.10.1):
https://github.com/apache/airflow/issues/41563

Upgrade was successful, even if the issue above was not the source of the test failures.


Disable flaky tests.

@navina @prateekm
Please take a look, when you get a chance.

@shanthoosh ready to merge?

@shanthoosh @vjagadish1989 can you please revert this? Not sure why this PR contains (unreviewed) async commit feature documentation.

@vjagadish1989 @prateekm
There's a open PR #177 under review which contains async commit documentation.
Not sure, how this commit(Adding async commit documentation) ended up in this list. My bad. Can you please revert it.


Parsed date is considered invalid

Description of the Issue and Steps to Reproduce:
Parsing the date "Thu Nov 2 23:42:48 2017+0000" with format "ddd MMM D HH:mm:ss YYYYZZ" and strict set to true will return an invalid date.
Possible causes:

Bug in moments date parsing.
(More likely) I'm using the wrong format string, but I swear I've double and triple checked it with the docs.

const date = moment("Thu Nov 2 23:42:48 2017+0000", "ddd MMM D HH:mm:ss YYYYZZ", true).locale('en');
console.log(date.isValid()); // Outputs false

Please include the values of all variables used.
See code.
Environment:
Chrome 62 on macOS, Firefox 57 on Ubuntu.
moment version 2.19.2
Other information that may be helpful:

The time zone setting of the machine the code is running on
macOS: GMT+0100
Ubuntu: GMT+0100
The time and date at which the code was run
Thursday Nov 16 around 9:30 am.
Other libraries in use (TypeScript, Immutable.js, etc)
React, webpack, babel, et al.

If you are reporting an issue, please run the following code in the environment you are using and include the output:
console.log( (new Date()).toString())
console.log((new Date()).toLocaleString())
console.log( (new Date()).getTimezoneOffset())
console.log( navigator.userAgent)
console.log(moment.version)
VM63:1 Thu Nov 16 2017 09:38:34 GMT+0100 (CET)
VM63:2 2017-11-16 09:38:34
VM63:3 -60
VM63:4 Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36
VM63:5 Uncaught ReferenceError: moment is not defined
    at <anonymous>:5:13

(Moment is used as a module, so it is not available in the global scope, version is 2.19.2)

See #4227


App sorting order in launcher

Is there a way to sort the installed apps they appear in when in the launcher?
It also might be possible to write an app for that so the sortorder could be adjusted directly on the watch or even better enhance the settings app for this. Would someone be interested in something like that, besides me?
My naive approach would be something like this:

add a subsetting in the settings app for app sortorder
there list all installed apps with sortorder let jsonObj = require("Storage").readJSON("app.info", "r");
make sortorder adjustable (like LCD brightness) jsonObj.sortorder = -5;
save changed sortorder for app require("Storage").writeJSON("app.info", jsonObj);

Thanks in advance for your feedback.

Right now there's no way to specify it via UI, but as you noted there is a sortorder field. I think that'd be a really neat addition.
I guess the only issue is upgrading apps would likely change the sort order. To work around that I guess it could be implemented in the App Loader?
For on-watch, if you create a file called foobar.settings.js then the Settings menu will pick it up (under 'App/Widget Settings') so that'd be a really easy way to add the option for people if they wanted it.

Thank you for your feedback!
Could you elaborate what you mean by implementing it in the app loader? What would that change in terms of the upgrading issue?
Also, could you please point me to the part of the documentation where I can read up on the usage of the foobar.settings.js file? Is this a kind of plug-and-play mechanism to add a submenu in the settings-app for the sorting functionality I suggested?
Again, thanks for your feedback and also all the work you do on Espruino. You're amazing!

Hi!

Could you elaborate what you mean by implementing it in the app loader?

I mean have a menu in https://banglejs.com/apps/
That's mean that the app loader could be aware of a change in sort order for apps, and would know to change the sortorder field on any new app.info files it uploaded.

where I can read up on the usage of the foobar.settings.js

https://github.com/espruino/BangleApps#adding-configuration-to-the-settings-menu

Is this a kind of plug-and-play mechanism to add a submenu in the settings-app for the sorting functionality I suggested?

Yep, that's right :)

Thanks for the quick response.

I mean have a menu in https://banglejs.com/apps/
That's mean that the app loader could be aware of a change in sort order for apps, and would know to change the sortorder field on any new app.info files it uploaded.

Now I get what you mean, I've confused the app loader with the app launcher.

Is this a kind of plug-and-play mechanism to add a submenu in the settings-app for the sorting functionality I suggested?

Yep, that's right :)

Ok then this will be my starting point. Thanks again.
One last question: would a pull request to the settings app be a good idea to publish the foobar.settings.js-version when done or what would you propose in order to make it publicly available for the bangle.js community?

I'd just add another 'app'. Just an entry in apps.json mentioning your settings.js file should do it - but if you have any troubles let me know and I can sort that bit out

Thinking about the right place for this I think it might fit better into the existing "App Manager" App https://github.com/espruino/BangleApps/tree/master/apps/files
I think I'll add a submenu there so the "Settings" app won't be clogged even more. My watch is already running near RAM max. capacity when using the "Settings" app.

I finally found the time, so please see this pull request


Refactor the docker yml to adapt to both HA and standalone installation

Currently the docker-compose yml file different between HA installation and standalone installation.
We should use a single template to create the docker-compose file for both installation.

vmware/harbor #3197

Set it to low priority as we'll focus on tile/chart to provide HA.


Gitea 1.20 leaking resources

Description
After upgrade from 1.19 to 1.20 we noticed that at one point (about twice a day) Gitea would become unstable and would not accept git push anymore and would fail with:
.ers/web/repo/http.go:485:serviceRPC() [E] Fail to serve RPC(upload-pack) in /srv/git/repositories/xxx/web.git: exit status 128 - error: git upload-pack: git-pack-objects died with error

We could not pinpoint exact cause of what is reason for this as in one point it was that it can not create process that was failing at linux syscall level.
Our temporary fix to get it stable again was by disabling /user/events websocket endpoint at reverse proxy level. This does help but of course on degradation of UX.
At peak times we have about 50 users using it simultaneously so it's not that high number.
If anyone has any ideas on where to look to pinpoint the source of problem let me know :)
Gitea Version
1.20
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
No response
Git Version
2.25.1
Operating System
Ubuntu 20.04
How are you running Gitea?
From binary using systemd
Database
PostgreSQL

/user/events websocket

It's not websocket, it's still EventSource 😆

Yes, it's a wild guess, hard to tell what's the real source for the problem but that what helped. There was no such problems with 1.19, nothing else has changed - nor user count or nor behavior

Might need to pprof it. Maybe we already expose a endpoint for it? If not, that might be a nice opt-in debug feature.

I also found a similar problem when closing Gitea
2023/08/23 13:24:09 ...eful/manager_unix.go:195:handleSignals() [W] PID 15167. Received SIGINT. Shutting down...
2023/08/23 13:24:09 ...eb/routing/logger.go:102:func1() [I] router: completed GET /user/events for <IP_ADDRESS>:55673, 200 OK in 21726747.0ms @ events/events.go:18(events.Events)
2023/08/23 13:24:09 ...eb/routing/logger.go:102:func1() [I] router: completed GET /user/events for <IP_ADDRESS>:55703, 200 OK in 21725337.4ms @ events/events.go:18(events.Events)
2023/08/23 13:24:09 ...eb/routing/logger.go:102:func1() [I] router: completed GET /user/events for <IP_ADDRESS>:53478, 200 OK in 23888501.5ms @ events/events.go:18(events.Events)
2023/08/23 13:24:09 ...eb/routing/logger.go:102:func1() [I] router: completed GET /user/events for <IP_ADDRESS>:53447, 200 OK in 23891926.5ms @ events/events.go:18(events.Events)
2023/08/23 13:24:09 ...eb/routing/logger.go:102:func1() [I] router: completed GET /user/events for <IP_ADDRESS>:55843, 200 OK in 21714246.7ms @ events/events.go:18(events.Events)
2023/08/23 13:24:09 ...eb/routing/logger.go:102:func1() [I] router: completed GET /user/events for <IP_ADDRESS>:55815, 200 OK in 21716689.5ms @ events/events.go:18(events.Events)
2023/08/23 13:24:09 ...eb/routing/logger.go:102:func1() [I] router: completed GET /user/events for <IP_ADDRESS>:55626, 200 OK in 21746951.8ms @ events/events.go:18(events.Events)
2023/08/23 13:24:09 ...eb/routing/logger.go:102:func1() [I] router: completed GET /user/events for <IP_ADDRESS>:55596, 200 OK in 21747738.2ms @ events/events.go:18(events.Events)
2023/08/23 13:24:09 ...eb/routing/logger.go:102:func1() [I] router: completed GET /user/events for <IP_ADDRESS>:55565, 200 OK in 21748612.8ms @ events/events.go:18(events.Events)
2023/08/23 13:24:09 ...eb/routing/logger.go:102:func1() [I] router: completed GET /user/events for <IP_ADDRESS>:55758, 200 OK in 21722494.1ms @ events/events.go:18(events.Events)
2023/08/23 13:24:09 ...eb/routing/logger.go:102:func1() [I] router: completed GET /user/events for <IP_ADDRESS>:53545, 200 OK in 23883790.2ms @ events/events.go:18(events.Events)
2023/08/23 13:24:09 ...eb/routing/logger.go:102:func1() [I] router: completed GET /user/events for <IP_ADDRESS>:53575, 200 OK in 23882836.3ms @ events/events.go:18(events.Events)
2023/08/23 13:24:09 ...eb/routing/logger.go:102:func1() [I] router: completed GET /user/events for <IP_ADDRESS>:55730, 200 OK in 21724003.3ms @ events/events.go:18(events.Events)
2023/08/23 13:24:09 ...eful/server_hooks.go:46:doShutdown() [I] PID: 15167 Listener ([::]:3000) closed.
2023/08/23 13:24:09 ...eb/routing/logger.go:102:func1() [I] router: completed GET /user/events for <IP_ADDRESS>:53514, 200 OK in 23884622.5ms @ events/events.go:18(events.Events)
2023/08/23 13:24:09 ...eb/routing/logger.go:102:func1() [I] router: completed GET /user/events for <IP_ADDRESS>:53637, 200 OK in 23881324.9ms @ events/events.go:18(events.Events)
2023/08/23 13:24:09 ...eb/routing/logger.go:102:func1() [I] router: completed GET /user/events for <IP_ADDRESS>:55786, 200 OK in 21720757.0ms @ events/events.go:18(events.Events)
2023/08/23 13:24:09 ...eb/routing/logger.go:102:func1() [I] router: completed GET /user/events for <IP_ADDRESS>:53606, 200 OK in 23881950.5ms @ events/events.go:18(events.Events)
2023/08/23 13:24:09 cmd/web.go:355:listen() [I] HTTP Listener: <IP_ADDRESS>:3000 Closed
2023/08/23 13:24:09 .../graceful/manager.go:168:doHammerTime() [W] Setting Hammer condition

even after disabling /user/events endpoint in reverse proxy we still experience problem few times a week when gitea will stop accepting git push'es and throw errors and only thing that helps to get it back working is gitea restart
runtime/cgo: pthread_create failed: Resource temporarily unavailable
SIGABRT: abort
PC=0x297d4d7 m=0 sigcode=18446744073709551610

goroutine 0 [idle]:
runtime: g 0: unknown pc 0x297d4d7
stack: frame={sp:0x7ffd921887e0, fp:0x0} stack=[0x7ffd9198a0a0,0x7ffd921890b0)
0x00007ffd921886e0: 0x0000000000000000 0x0000000000000000
0x00007ffd921886f0: 0x0000000000000000 0x0000000000000000
0x00007ffd92188700: 0x0000000000000000 0x0000000000000000
0x00007ffd92188710: 0x0000000000000000 0x0000000000000000
0x00007ffd92188720: 0x0000000000000000 0x0000000000000000
0x00007ffd92188730: 0x0000000000000000 0x0000000000000000
0x00007ffd92188740: 0x0000000000000000 0x0000000000000000
0x00007ffd92188750: 0x0000000000000000 0x0000000000000000
0x00007ffd92188760: 0x00007ffd92188830 0x000000000045d409 <runtime.pcvalue+0x0000000000000209>
0x00007ffd92188770: 0x00000000052270ac 0x0000000000000000
0x00007ffd92188780: 0x0000000000000000 0x0000000000000000
0x00007ffd92188790: 0x0000000000000000 0x0000000000000000
0x00007ffd921887a0: 0x0000000200000000 0x0000000000000000
0x00007ffd921887b0: 0x0000000000440634 <runtime.main+0x00000000000000b4> 0x00000000004407b1 <runtime.main+0x0000000000000231>
0x00007ffd921887c0: 0x00000000006a8d04 <encoding/gob.(*Encoder).encodeSingle.func1+0x0000000000000004> 0x00000000006a8d04 <encoding/gob.(*Encoder).encodeSingle.func1+0x0000000000000004>
0x00007ffd921887d0: 0x0000000000000000 0x0000000000000000
0x00007ffd921887e0: <0x0000000000000000 0x00000000006bfcd0 <github.com/yuin/goldmark/util.init+0x0000000000004090>
0x00007ffd921887f0: 0x0000000000016fc8 0x0000000000000000
0x00007ffd92188800: 0x00000000052270ac 0x0000000000000000
0x00007ffd92188810: 0x0000000000000000 0x00000000052100e0
0x00007ffd92188820: 0x0000000005984118 0x00000000063aebe0
0x00007ffd92188830: 0x00007ffd92188870 0x000000000045ded0 <runtime.pcdatavalue+0x0000000000000050>
0x00007ffd92188840: 0x0000000005984118 0x00000000063aebe0
0x00007ffd92188850: 0x0000000000016fc8 0x0000000000440745 <runtime.main+0x00000000000001c5>
0x00007ffd92188860: 0xfffffffe7fffffff 0xffffffffffffffff
0x00007ffd92188870: 0xffffffffffffffff 0xffffffffffffffff
0x00007ffd92188880: 0xffffffffffffffff 0xffffffffffffffff
0x00007ffd92188890: 0xffffffffffffffff 0xffffffffffffffff
0x00007ffd921888a0: 0xffffffffffffffff 0xffffffffffffffff
0x00007ffd921888b0: 0xffffffffffffffff 0xffffffffffffffff
0x00007ffd921888c0: 0xffffffffffffffff 0xffffffffffffffff
0x00007ffd921888d0: 0xffffffffffffffff 0xffffffffffffffff
runtime: g 0: unknown pc 0x297d4d7
stack: frame={sp:0x7ffd921887e0, fp:0x0} stack=[0x7ffd9198a0a0,0x7ffd921890b0)
0x00007ffd921886e0: 0x0000000000000000 0x0000000000000000
0x00007ffd921886f0: 0x0000000000000000 0x0000000000000000
0x00007ffd92188700: 0x0000000000000000 0x0000000000000000
0x00007ffd92188710: 0x0000000000000000 0x0000000000000000
0x00007ffd92188720: 0x0000000000000000 0x0000000000000000
0x00007ffd92188730: 0x0000000000000000 0x0000000000000000
0x00007ffd92188740: 0x0000000000000000 0x0000000000000000
0x00007ffd92188750: 0x0000000000000000 0x0000000000000000
0x00007ffd92188760: 0x00007ffd92188830 0x000000000045d409 <runtime.pcvalue+0x0000000000000209>
0x00007ffd92188770: 0x00000000052270ac 0x0000000000000000
0x00007ffd92188780: 0x0000000000000000 0x0000000000000000
0x00007ffd92188790: 0x0000000000000000 0x0000000000000000
0x00007ffd921887a0: 0x0000000200000000 0x0000000000000000
0x00007ffd921887b0: 0x0000000000440634 <runtime.main+0x00000000000000b4> 0x00000000004407b1 <runtime.main+0x0000000000000231>
0x00007ffd921887c0: 0x00000000006a8d04 <encoding/gob.(*Encoder).encodeSingle.func1+0x0000000000000004> 0x00000000006a8d04 <encoding/gob.(*Encoder).encodeSingle.func1+0x0000000000000004>
0x00007ffd921887d0: 0x0000000000000000 0x0000000000000000
0x00007ffd921887e0: <0x0000000000000000 0x00000000006bfcd0 <github.com/yuin/goldmark/util.init+0x0000000000004090>
0x00007ffd921887f0: 0x0000000000016fc8 0x0000000000000000
0x00007ffd92188800: 0x00000000052270ac 0x0000000000000000
0x00007ffd92188810: 0x0000000000000000 0x00000000052100e0
0x00007ffd92188820: 0x0000000005984118 0x00000000063aebe0
0x00007ffd92188830: 0x00007ffd92188870 0x000000000045ded0 <runtime.pcdatavalue+0x0000000000000050>
0x00007ffd92188840: 0x0000000005984118 0x00000000063aebe0
0x00007ffd92188850: 0x0000000000016fc8 0x0000000000440745 <runtime.main+0x00000000000001c5>
0x00007ffd92188860: 0xfffffffe7fffffff 0xffffffffffffffff
0x00007ffd92188870: 0xffffffffffffffff 0xffffffffffffffff
0x00007ffd92188880: 0xffffffffffffffff 0xffffffffffffffff
0x00007ffd92188890: 0xffffffffffffffff 0xffffffffffffffff
0x00007ffd921888a0: 0xffffffffffffffff 0xffffffffffffffff
0x00007ffd921888b0: 0xffffffffffffffff 0xffffffffffffffff
0x00007ffd921888c0: 0xffffffffffffffff 0xffffffffffffffff
0x00007ffd921888d0: 0xffffffffffffffff 0xffffffffffffffff

goroutine 1 [runnable, locked to thread]:
runtime.mapassign_faststr(0x2d29820?, 0xc0002221b0?, {0x31be26d, 0x3})
/usr/local/go/src/runtime/map_faststr.go:203 +0x3f4 fp=0xc000214f50 sp=0xc000214f48 pc=0x418c34
github.com/go-enry/go-enry/v2/data.init()
/go/pkg/mod/github.com/go-enry/go-enry/v2@v2.8.4/data/frequencies.go:605 +0x812ae fp=0xc00021f730 sp=0xc000214f50 pc=0xd09ece
runtime.doInit(0x637e720)
/usr/local/go/src/runtime/proc.go:6525 +0x126 fp=0xc00021f860 sp=0xc00021f730 pc=0x44dec6
runtime.doInit(0x638b740)
/usr/local/go/src/runtime/proc.go:6502 +0x71 fp=0xc00021f990 sp=0xc00021f860 pc=0x44de11
runtime.doInit(0x637bb60)
/usr/local/go/src/runtime/proc.go:6502 +0x71 fp=0xc00021fac0 sp=0xc00021f990 pc=0x44de11
runtime.doInit(0x63a79e0)
/usr/local/go/src/runtime/proc.go:6502 +0x71 fp=0xc00021fbf0 sp=0xc00021fac0 pc=0x44de11
runtime.doInit(0x6395d00)
/usr/local/go/src/runtime/proc.go:6502 +0x71 fp=0xc00021fd20 sp=0xc00021fbf0 pc=0x44de11
runtime.doInit(0x63b3340)
/usr/local/go/src/runtime/proc.go:6502 +0x71 fp=0xc00021fe50 sp=0xc00021fd20 pc=0x44de11
runtime.doInit(0x6390740)
/usr/local/go/src/runtime/proc.go:6502 +0x71 fp=0xc00021ff80 sp=0xc00021fe50 pc=0x44de11
runtime.main()
/usr/local/go/src/runtime/proc.go:233 +0x1c6 fp=0xc00021ffe0 sp=0xc00021ff80 pc=0x440746
runtime.goexit()
/usr/local/go/src/runtime/asm_amd64.s:1598 +0x1 fp=0xc00021ffe8 sp=0xc00021ffe0 pc=0x475381

goroutine 2 [force gc (idle)]:
runtime.gopark(0x0?, 0x0?, 0x0?, 0x0?, 0x0?)
/usr/local/go/src/runtime/proc.go:381 +0xd6 fp=0xc000084fb0 sp=0xc000084f90 pc=0x440bb6
runtime.goparkunlock(...)
/usr/local/go/src/runtime/proc.go:387
runtime.forcegchelper()
/usr/local/go/src/runtime/proc.go:305 +0xb0 fp=0xc000084fe0 sp=0xc000084fb0 pc=0x4409f0
runtime.goexit()
/usr/local/go/src/runtime/asm_amd64.s:1598 +0x1 fp=0xc000084fe8 sp=0xc000084fe0 pc=0x475381
created by runtime.init.6
/usr/local/go/src/runtime/proc.go:293 +0x25

goroutine 3 [GC sweep wait]:
runtime.gopark(0x1?, 0x0?, 0x0?, 0x0?, 0x0?)
/usr/local/go/src/runtime/proc.go:381 +0xd6 fp=0xc000085780 sp=0xc000085760 pc=0x440bb6
runtime.goparkunlock(...)
/usr/local/go/src/runtime/proc.go:387
runtime.bgsweep(0x0?)
/usr/local/go/src/runtime/mgcsweep.go:319 +0xde fp=0xc0000857c8 sp=0xc000085780 pc=0x42ac3e
runtime.gcenable.func1()
/usr/local/go/src/runtime/mgc.go:178 +0x26 fp=0xc0000857e0 sp=0xc0000857c8 pc=0x41fe86
runtime.goexit()
/usr/local/go/src/runtime/asm_amd64.s:1598 +0x1 fp=0xc0000857e8 sp=0xc0000857e0 pc=0x475381
created by runtime.gcenable
/usr/local/go/src/runtime/mgc.go:178 +0x6b

goroutine 4 [GC scavenge wait]:
runtime.gopark(0xc000060150?, 0x4597ab0?, 0x0?, 0x0?, 0x0?)
/usr/local/go/src/runtime/proc.go:381 +0xd6 fp=0xc000085f70 sp=0xc000085f50 pc=0x440bb6
runtime.goparkunlock(...)
/usr/local/go/src/runtime/proc.go:387
runtime.(*scavengerState).park(0x6599820)
/usr/local/go/src/runtime/mgcscavenge.go:400 +0x53 fp=0xc000085fa0 sp=0xc000085f70 pc=0x428af3
runtime.bgscavenge(0x0?)
/usr/local/go/src/runtime/mgcscavenge.go:633 +0x65 fp=0xc000085fc8 sp=0xc000085fa0 pc=0x4290e5
runtime.gcenable.func2()
/usr/local/go/src/runtime/mgc.go:179 +0x26 fp=0xc000085fe0 sp=0xc000085fc8 pc=0x41fe26
runtime.goexit()
/usr/local/go/src/runtime/asm_amd64.s:1598 +0x1 fp=0xc000085fe8 sp=0xc000085fe0 pc=0x475381
created by runtime.gcenable
/usr/local/go/src/runtime/mgc.go:179 +0xaa

goroutine 5 [finalizer wait]:
runtime.gopark(0x1a0?, 0x659b3a0?, 0x60?, 0x78?, 0xc000084770?)
/usr/local/go/src/runtime/proc.go:381 +0xd6 fp=0xc000084628 sp=0xc000084608 pc=0x440bb6
runtime.runfinq()
/usr/local/go/src/runtime/mfinal.go:193 +0x107 fp=0xc0000847e0 sp=0xc000084628 pc=0x41eec7
runtime.goexit()
/usr/local/go/src/runtime/asm_amd64.s:1598 +0x1 fp=0xc0000847e8 sp=0xc0000847e0 pc=0x475381
created by runtime.createfing
/usr/local/go/src/runtime/mfinal.go:163 +0x45

goroutine 6 [select]:
runtime.gopark(0xc000092e60?, 0x2?, 0x88?, 0x9b?, 0xc000092db4?)
/usr/local/go/src/runtime/proc.go:381 +0xd6 fp=0xc000092be0 sp=0xc000092bc0 pc=0x440bb6
runtime.selectgo(0xc000092e60, 0xc000092db0, 0x0?, 0x0, 0x0?, 0x1)
/usr/local/go/src/runtime/select.go:327 +0x7be fp=0xc000092d20 sp=0xc000092be0 pc=0x45125e
code.gitea.io/gitea/modules/log.(*EventWriterBaseImpl).Run(0xc0000ae8a0, {0x45c6a50, 0xc0000a56e0})
/source/modules/log/event_writer_base.go:81 +0x2e9 fp=0xc000092f48 sp=0xc000092d20 pc=0x84eee9
code.gitea.io/gitea/modules/log.(*eventWriterConsole).Run(0x45c6a50?, {0x45c6a50?, 0xc0000a56e0?})
<autogenerated>:1 +0x2f fp=0xc000092f70 sp=0xc000092f48 pc=0x8580cf
code.gitea.io/gitea/modules/log.eventWriterStartGo.func1()
/source/modules/log/event_writer_base.go:157 +0xb1 fp=0xc000092fe0 sp=0xc000092f70 pc=0x84f7b1
runtime.goexit()
/usr/local/go/src/runtime/asm_amd64.s:1598 +0x1 fp=0xc000092fe8 sp=0xc000092fe0 pc=0x475381
created by code.gitea.io/gitea/modules/log.eventWriterStartGo
/source/modules/log/event_writer_base.go:153 +0x1c5

goroutine 7 [GC worker (idle)]:
runtime.gopark(0x0?, 0x0?, 0x0?, 0x0?, 0x0?)
/usr/local/go/src/runtime/proc.go:381 +0xd6 fp=0xc000086f50 sp=0xc000086f30 pc=0x440bb6
runtime.gcBgMarkWorker()
/usr/local/go/src/runtime/mgc.go:1275 +0xf1 fp=0xc000086fe0 sp=0xc000086f50 pc=0x421bf1
runtime.goexit()
/usr/local/go/src/runtime/asm_amd64.s:1598 +0x1 fp=0xc000086fe8 sp=0xc000086fe0 pc=0x475381
created by runtime.gcBgMarkStartWorkers
/usr/local/go/src/runtime/mgc.go:1199 +0x25

goroutine 18 [GC worker (idle)]:
runtime.gopark(0xe061282d97646?, 0xc0000a56e0?, 0xd0?, 0x67?, 0x84f7b1?)
/usr/local/go/src/runtime/proc.go:381 +0xd6 fp=0xc000086750 sp=0xc000086730 pc=0x440bb6
runtime.gcBgMarkWorker()
/usr/local/go/src/runtime/mgc.go:1275 +0xf1 fp=0xc0000867e0 sp=0xc000086750 pc=0x421bf1
runtime.goexit()
/usr/local/go/src/runtime/asm_amd64.s:1598 +0x1 fp=0xc0000867e8 sp=0xc0000867e0 pc=0x475381
created by runtime.gcBgMarkStartWorkers
/usr/local/go/src/runtime/mgc.go:1199 +0x25

goroutine 34 [GC worker (idle)]:
runtime.gopark(0xe061282d9ab99?, 0x0?, 0x0?, 0x0?, 0x0?)
/usr/local/go/src/runtime/proc.go:381 +0xd6 fp=0xc000080750 sp=0xc000080730 pc=0x440bb6
runtime.gcBgMarkWorker()
/usr/local/go/src/runtime/mgc.go:1275 +0xf1 fp=0xc0000807e0 sp=0xc000080750 pc=0x421bf1
runtime.goexit()
/usr/local/go/src/runtime/asm_amd64.s:1598 +0x1 fp=0xc0000807e8 sp=0xc0000807e0 pc=0x475381
created by runtime.gcBgMarkStartWorkers
/usr/local/go/src/runtime/mgc.go:1199 +0x25

goroutine 19 [GC worker (idle)]:
runtime.gopark(0xe061282daeaff?, 0x0?, 0x0?, 0x0?, 0x0?)
/usr/local/go/src/runtime/proc.go:381 +0xd6 fp=0xc00011a750 sp=0xc00011a730 pc=0x440bb6
runtime.gcBgMarkWorker()
/usr/local/go/src/runtime/mgc.go:1275 +0xf1 fp=0xc00011a7e0 sp=0xc00011a750 pc=0x421bf1
runtime.goexit()
/usr/local/go/src/runtime/asm_amd64.s:1598 +0x1 fp=0xc00011a7e8 sp=0xc00011a7e0 pc=0x475381
created by runtime.gcBgMarkStartWorkers
/usr/local/go/src/runtime/mgc.go:1199 +0x25

goroutine 35 [GC worker (idle)]:
runtime.gopark(0x65e1c00?, 0x1?, 0xe7?, 0x5c?, 0x0?)
/usr/local/go/src/runtime/proc.go:381 +0xd6 fp=0xc000080f50 sp=0xc000080f30 pc=0x440bb6
runtime.gcBgMarkWorker()
/usr/local/go/src/runtime/mgc.go:1275 +0xf1 fp=0xc000080fe0 sp=0xc000080f50 pc=0x421bf1
runtime.goexit()
/usr/local/go/src/runtime/asm_amd64.s:1598 +0x1 fp=0xc000080fe8 sp=0xc000080fe0 pc=0x475381
created by runtime.gcBgMarkStartWorkers
/usr/local/go/src/runtime/mgc.go:1199 +0x25

goroutine 8 [GC mark termination]:
runtime.systemstack_switch()
/usr/local/go/src/runtime/asm_amd64.s:463 fp=0xc0000876f0 sp=0xc0000876e8 pc=0x473160
runtime.gcMarkDone()
/usr/local/go/src/runtime/mgc.go:807 +0xff fp=0xc000087750 sp=0xc0000876f0 pc=0x4209df
runtime.gcBgMarkWorker()
/usr/local/go/src/runtime/mgc.go:1407 +0x345 fp=0xc0000877e0 sp=0xc000087750 pc=0x421e45
runtime.goexit()
/usr/local/go/src/runtime/asm_amd64.s:1598 +0x1 fp=0xc0000877e8 sp=0xc0000877e0 pc=0x475381
created by runtime.gcBgMarkStartWorkers
/usr/local/go/src/runtime/mgc.go:1199 +0x25

goroutine 20 [GC worker (idle)]:
runtime.gopark(0xe061282d98af4?, 0x1?, 0xbe?, 0x5d?, 0x0?)
/usr/local/go/src/runtime/proc.go:381 +0xd6 fp=0xc00011af50 sp=0xc00011af30 pc=0x440bb6
runtime.gcBgMarkWorker()
/usr/local/go/src/runtime/mgc.go:1275 +0xf1 fp=0xc00011afe0 sp=0xc00011af50 pc=0x421bf1
runtime.goexit()
/usr/local/go/src/runtime/asm_amd64.s:1598 +0x1 fp=0xc00011afe8 sp=0xc00011afe0 pc=0x475381
created by runtime.gcBgMarkStartWorkers
/usr/local/go/src/runtime/mgc.go:1199 +0x25

goroutine 36 [GC worker (idle)]:
runtime.gopark(0xe061282d04052?, 0x3?, 0xa0?, 0xd7?, 0x0?)
/usr/local/go/src/runtime/proc.go:381 +0xd6 fp=0xc000081750 sp=0xc000081730 pc=0x440bb6
runtime.gcBgMarkWorker()
/usr/local/go/src/runtime/mgc.go:1275 +0xf1 fp=0xc0000817e0 sp=0xc000081750 pc=0x421bf1
runtime.goexit()
/usr/local/go/src/runtime/asm_amd64.s:1598 +0x1 fp=0xc0000817e8 sp=0xc0000817e0 pc=0x475381
created by runtime.gcBgMarkStartWorkers
/usr/local/go/src/runtime/mgc.go:1199 +0x25

rax 0x0
rbx 0x636d2f8
rcx 0x297d4d7
rdx 0x0
rdi 0x2
rsi 0x7ffd921887e0
rbp 0x4c4fd1e
rsp 0x7ffd921887e0
r8 0x0
r9 0x7ffd921887e0
r10 0x8
r11 0x246
r12 0x71421a0
r13 0x20
r14 0x659aa20
r15 0x1
rip 0x297d4d7
rflags 0x246
cs 0x33
fs 0x0
gs 0x0

The error about pthread_create failed: Resource temporarily unavailable normally means that you are trying to create too many threads.
Take a look at how many thread numbers are allowed for this linux machine
cat /proc/sys/kernel/threads-max

And change it to a greater number if the memory is enough.
echo 100000 > /proc/sys/kernel/threads-max

You could also have a monitor record for the thread's number.

already checked that, does not seems anything out of ordinary:
$ cat /proc/sys/kernel/threads-max
127248
# Gitea process thead count:
$ ps -o nlwp 447125
NLWP
  65
# All processes thread count:
$ ps -eo nlwp | tail -n +2 | awk '{ num_threads += $1 } END { print num_threads }'
351

Maybe you can use Prometheus & Grafana to track the thread number.

will try to enable processes monitoring in node_exporter

Problem happened again sooner than expected.
Thread/process count is not the problem, memory usage is
Looks like on push on ~600MB repo gitea process memory usage spikes at least +4GB and it does not recover from that and only restart of gitea process helps:

A pprof snapshot from admin ui should give some info on the memory allocations.

admin ui pprof allows downloading only cpu profile but not memory profile

Not sure what admin pprof does, but this should work:
https://github.com/go-gitea/gitea/blob/e5ec57cd608a81be6e0a6b897b165e9b322ceab4/custom/conf/app.example.ini#L289-L295

thing is this that it's not easily reproducible and I don't know what impact enabling this is on production system as it could take days/weeks before problem happens

Not an expert but I think the pprof webserver has no real perf impact until you actually take snapshots.

I couldn't reproduce this on my local machine. I have tested main and release/v1.20 for pushing linux repository via http/ssh. The memory has almost no change when pushing.
Do you have any git hooks or web hooks on that repository?

it has only woodpecker and slack/mattermost webhooks, no special githooks used on this instance

Maybe you can try disable code indexer temporarily for some days to take a look whether it's the problem.

Feel free to provide more clues by #28596 (and it has been backported to 1.21)


[Enhancement] Separate remote database operation from domain module.

Separate remote database operation from domain module.
Right now our remote data queries are placed in domain module, so migrate those into data module and make sure data layer work with domain logic.

can you assign me this issue?

Can I work on this assignment...? @Vishwajith-Shettigar

Yes you can .
On Thu, Oct 3, 2024, 11:07 AM DevSahil12 @.***> wrote:

Can I work on this assignment...? @Vishwajith-Shettigar
https://github.com/Vishwajith-Shettigar
—
Reply to this email directly, view it on GitHub
https://github.com/Vishwajith-Shettigar/NextGen/issues/35#issuecomment-2390565283,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASEE6XMZQX72GFFH6YWY5P3ZZTJYRAVCNFSM6AAAAABPHBM7AOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJQGU3DKMRYGM
.
 Maybe link the file/files? Did not get what needs to be changed

You can see we are doing firebase operations on domain module, which doesn't align with clean architecture pattern, so migrate all firebase operations to data module but keep some logics in domain module.

@rubenquadros, You can see that we're currently performing Firebase operations in the domain module, which doesn't align with the clean architecture pattern. Therefore, migrate all Firebase operations to the data module while retaining some of the logic in the domain module.


Meteor <IP_ADDRESS> - mongo error when using index

I just updated to Meteor <IP_ADDRESS> and am getting the following error:
MongoError: Index with pattern: { name: 1 } already exists with different options

It worked with <IP_ADDRESS> ...
I looked in the History.md what happened for <IP_ADDRESS> but there is nothing that would be related to this. Probably something under the hood is happening here.
This is where the error occurs:
at [object Object].MongoConnection._ensureIndex (packages/mongo/mongo_driver.js:790:1)
at packages/aldeed_collection2/packages/aldeed_collection2.js:77:1

Could you please tell me how you fixed it?

I am having similar problem right now - please share how you fixed it, thanks!

Same here! Please share.


remove getInitContainer from odo

Signed-off-by: Stephanie<EMAIL_ADDRESS>What type of PR is this?
/kind cleanup
What does this PR do / why we need it:
This PR removes GetPreStartInitContainers from odo util:

should use generator from library to get initcontainers
odo currently does not support PreStart and apply commands
https://github.com/openshift/odo/blob/a54cfd86da993560768c7aae1a8fd1a1c017b833/pkg/devfile/validate/events.go#L5-L14

Which issue(s) this PR fixes:
Fixes #?
PR acceptance criteria:

[ ] Unit test

[ ] Integration test

[ ] Documentation

[ ] Update changelog

[ ] I have read the test guidelines

How to test changes / Special notes to the reviewer:

@kadel Can you help adding /approve label to this PR?

/approve


Multiple movies with same year error

When multiple movies in the timeline (> 2) have the same year, not every gap works correctly

fixed


Creating scene with trigger does not match any of the allowed types

I tried to create a empty scene and it works well when triggers and actions are empty. But I can't create a scene with assigned trigger.
Using this code:
trigger = Trigger(id="b55c75ec-829c-4623-a167-0b537569c9e2_1", type="device",triggered_at=datetime.now(), disabled=False)
action = Action(id="b55c75ec-829c-4623-a167-0b537569c9e2_1", type="device", disabled=False)
dirigera_hub.create_scene(info=Info(name="ha_dir-pla_test_test1_test2", icon=Icon.SCENES_CLEAN_SPARKLES), triggers=[trigger], actions=[action])

I getting error:
Traceback (most recent call last):
  File "/Users/slajob/git/dirigera_local/shortcut-somrig.py", line 24, in <module>
    dirigera_hub.create_scene(info=Info(name="ha_dir-pla_test_test1_test2", icon=Icon.SCENES_CLEAN_SPARKLES), triggers=[trigger], actions=[action])
  File "/Users/slajob/git/dirigera_local/venv/lib/python3.9/site-packages/dirigera/hub/hub.py", line 421, in create_scene
    response_dict = self.post(
  File "/Users/slajob/git/dirigera_local/venv/lib/python3.9/site-packages/dirigera/hub/hub.py", line 132, in post
    response.raise_for_status()
  File "/Users/slajob/git/dirigera_local/venv/lib/python3.9/site-packages/requests/models.py", line 1021, in raise_for_status
    raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 400 Client Error: Bad Request for url: https://<IP_ADDRESS>:8443/v1/scenes/
{"error":"Error","message":"\"triggers[0]\" does not match any of the allowed types"}

Have you ever tried creating scene with trigger assigned?

@Leggin @slajob I managed to create a scene with a controller trigger in https://github.com/Leggin/dirigera/pull/74.

Thanks you two!


opcua client support

🚀 Feature Request
Relevant Package

 This feature request is for DeviceService
Description

I did not find opcua device service in edgexfoundry docs.
Recomment opcua client feature can be added to edgex device service.
Opcua is very important in manufacturing industry.
Describe the solution you'd like
 None. Just met edgexfoundry the first day.
Describe alternatives you've considered
 gopcua

@NieYanzhai   can refer https://github.com/edgego/device-opcua-go

Currently we have Device OPC-UA in the holding area https://github.com/edgexfoundry-holding/device-opcua-go to interact with the OPC-UA devices.
Closing this issue as no activity since 2011.


Cannot resolve module 'buffertools'

$ webpack
Hash: fa21190dc85f7f306103
Version: webpack 1.12.14
Time: 4517ms
                   Asset    Size  Chunks             Chunk Names
personalDataComponent.js  890 kB       0  [emitted]  personalDataComponent
    + 194 hidden modules

WARNING in /var/www/promo/~/react-jsonschema-form/~/deeper/index.js
Module not found: Error: Cannot resolve module 'buffertools' in /var/www/promo/node_modules/react-jsonschema-form/node_modules/deeper
 @ /var/www/promo/~/react-jsonschema-form/~/deeper/index.js 14:21-43

Probably due to the fact that the module tries to require buffertools but fails?
try {
  deeper.fastEqual = require('buffertools').equals
} catch (e) {
  // whoops, nobody told buffertools it wasn't installed
}

Most definitely an issue for people using bundlers like browserify or webpack, aka ~95% of the frontend developers community :)
Shooting in the dark here, but I wonder if something like global["require"]("buffertools") or similar hack would prevent bundlers to parse the statement at compilation time? (yeah, that's ugly anyway)


Change CRD to none-namespaced

issue: https://github.com/harvester/harvester/issues/582

@futuretea does either node driver or the terraform provider use the clusterNetwork or nodeNetwork resource?

@futuretea does either node driver or the terraform provider use the clusterNetwork or nodeNetwork resource?

clusterNetwork  was used by terraform provider

dependency: https://github.com/harvester/harvester/issues/923


AS3 deployment fails - Error 500 AsyncContext timeout

Environment

Application Services Version: f5-appsvcs-3.43.0-2.noarch
BIG-IP Version: BIG-IP <IP_ADDRESS> Build 0.0.5 Point Release 1

Summary
AS3 declaration deployment fails with config save failure / timeout.
Steps To Reproduce
Steps to reproduce the behavior:

Submit any declaration

Observe the following error response:

{
  "code": 500,
  "declarationFullId": "48aa4a3e-9af1-45b9-8e28-70dc2293077c",
  "message": "failed to save BIG-IP config (GET ***localhost:8100/mgmt/tm/task/sys/config/1692867713201884 checking config save status response=500 body=\n\n<meta http-equiv=\"Content-Type\" content=\"text/html;charset=ISO-8859-1\"/>\n<title>Error 500 AsyncContext timeout</title>\n\n
HTTP ERROR 500 AsyncContext timeout
\n
\n
URI:	/mgmt/tm/task/sys/config/1692867713201884
\n
STATUS:	500
\n
MESSAGE:	AsyncContext timeout
\n
SERVLET:	com.f5.rest.app.RestServerServlet-11f39f9
\n
\n
Powered by Jetty:// 9.4.49.v20220914
\n\n\n\n)"
}

Expected Behavior
The declaration to be deployed and saved successfully
Actual Behavior
The declaration is indeed deployed (but we don't know for sure without checking the actual config), but the config save fails which makes our pipieline fail as well, including that of course it's not saved which could be a big issue incase reboot occurs.
The failure is intermittent and can work one day, while the next day it doesn't. Now lately it's issues all the time. For those declarations it doesn't even take long to deploy (1-2 minutes) and they're not complicated at all. It makes no difference on what's deployed.
Before minor upgrade to <IP_ADDRESS> we had the same issue but the error message was different (not HTML with that "AsyncContext timeout").

Thanks @oakh1 for reaching out. In order to prioritize and understand the issue better, please reach out to us at<EMAIL_ADDRESS>

@sunitharonan I have the same/very similar issue (on v16.1.4, AS3 3.47.0rc) and opened some days ago a Support case 00460665. Note: the timeout settings (sys db) on the system follow the AS3 best-practices document => the 3 values have been changed from 60 to 180
[{'code': 422, 'message': 'declaration failed', 'response': 'GET http://admin:XXXXXX@localhost:8100/mgmt/tm/task/cli/script/1693226757164034 checking cli script status response=500 body=\\n\\n<meta http-equiv=\"Content-Type\" content=\"text/html;charset=ISO-8859-1\"/>\\n<title>Error 500 AsyncContext timeout</title>\\n\\n
HTTP ERROR 500 AsyncContext timeout
\\n
\\n
URI:	/mgmt/tm/task/cli/script/1693226757164034
\\n
STATUS:	500
\\n
MESSAGE:	AsyncContext timeout
\\n
SERVLET:	com.f5.rest.app.RestServerServlet-51cdd8a
\\n
\\n
Powered by Jetty:// 9.4.49.v20220914
\\n\\n\\n\\n', 'host': 'localhost', 'tenant': 'APIm', 'runTime': 59686}]"

Hi, we digged a bit more into this issue and even increasing timeout wouldn't work in this case as we have already tried it. We believe it is a Big Ip product side issue as it is working fine on 15.1.8. We referred this case to Big IP team as AS3 is working as intended. Closing this case.


Scapy keeps throwing error for Circular Import

hi,
I am trying to run scapy on windows 10. I installed it using pip install scapy.
But it keeps giving me error

Any help is appreciated

Hi, this issue tracker is for issues with the codebase behind https://pypi.org itself, not the projects hosted on PyPI.
You should report this issue to the tracker for the project in question instead.


Slider-handle: wrong value for 'right' property

Based on : https://github.com/DesignRevision/shards-ui/blob/master/src/scss/_variables.scss#L946
23 px / 2 = 11.5 px

@ZsharE Awesome! Thanks for your contribution! We'll include this in the 3.0.0 version.


Fix description when locked by system

Fix the lock description when lock is set only by system (i.e. locked = True in the model's code)

Please check the following:

[x] Do the tests still pass?[^1]
[ ] Does the code comply with the style guide?

[ ] Run make lint from the Wagtail root.

[ ] For Python changes: Have you added tests to cover the new/fixed behaviour?
[ ] For front-end changes: Did you test on all of Wagtail’s supported environments?[^2]

[ ] Please list the exact browser and operating system versions you tested:
[ ] Please list which assistive technologies [^3] you tested:

[ ] For new features: Has the documentation been updated accordingly?

Please describe additional details for testing this change.
[^1]: Development Testing
[^2]: Browser and device support
[^3]: Accessibility Target

Thanks, nice find. I've kicked off the CI.

Merged in 5dcf8e4a2795ce95a10164bdc2f0521c8367abf7
@SebCorbin I've added you as "Sébastien Corbin" to the contributors list. Do shout if you want that changed


Weird loop that runs forever

Details

Project URL: http://sqlalchemy.readthedocs.io/en/latest/

Expected Result
See the doc of sqlalchemy
Actual Result
A redirect and loop forever.
curl -L http://sqlalchemy.readthedocs.io/en/latest

<link rel="canonical" href="http://sqlalchemy.readthedocs.io/en/latest/" />

<link rel="stylesheet" href="https://media.readthedocs.org/css/readthedocs-doc-embed.css" type="text/css" />

Hopefully redirecting to http://sqlalchemy.readthedocs.io/en/latest/ !

Replicated. Thanks for logging.

I have gone through the source code of the documentation and it seems that its should redirect to the canonical_url. Which is the project url. So it become a infinity loop over there. For more information, you can see  #2267 and #1916

@hvnsweeting the hacky way implemented by the project should work. Can you check with the maintainer if they have set the Canonical Domain the in the project settings?
cc: @zzzeek

Please implement #2267.  #2267 was opened eighteen months ago and it has received no response whatsoever from any maintainers.   It is not fair that RTD provides no way whatsoever to leave once one has their userbase going there and the hack I made is completely stupid and doesn't work very well.
I added the canonical URL and the redirect is still not working.   I dont have time to constantly chase down RTD bugs (which is why I've moved off of it).

seems like it works now, perhaps it was caching.   but still.   #2267.  so simple.

@hvnsweeting,  After @zzzeek added the canonical url, I have tested it and it seems to be working now. Can you please check and close the issue if that fixed?

@zzzeek I will try to discuss with the maintainers to find a resolution of the issues.

so simple

Contributions welcome!

It redirected me to http://docs.sqlalchemy.org/en/latest/ now, seems worked. Thank you all.


Add websocket support

closed after opening another P.R. to merge into same named branch, allowing us to keep main tracking the upstream


Idiomatic Show instance for lazy lists

This pull request changes the output of show for Data.List.Lazy.Types.List and Data.List.Lazy.Types.NonEmptyList from this:
> Data.List.Lazy.fromFoldable [0, 1]
fromStrict ((Cons 0 (Cons 1 Nil)))

> Data.List.Lazy.NonEmpty.fromFoldable [0, 1]
(Just (NonEmptyList (defer \_ -> (NonEmpty 0 fromStrict ((Cons 1 Nil))))))

to that:
> Data.List.Lazy.fromFoldable [0, 1]
(defer \_ -> 0 : (defer \_ -> 1 : (defer \_ -> Nil)))

> Data.List.Lazy.NonEmpty.fromFoldable [0, 1]
(Just (NonEmptyList (defer \_ -> (NonEmpty 0 (defer \_ -> 1 : (defer \_ -> Nil))))))

Alternatively, we could show (fromFoldable […]) but this makes the output of show less similar:
> Data.List.Lazy.fromFoldable [0, 1]
(fromFoldable [1,0])

> Data.List.Lazy.NonEmpty.fromFoldable [0, 1]
(Just (NonEmptyList (defer \_ -> (NonEmpty 0 (fromFoldable [1])))))

Close https://github.com/purescript/purescript-lists/issues/122.

While this is technically code that does indeed work, I'm not sure how useful it is as a Show instance since it's very much not compact. It's very difficult to see what the values are in the midst of all the other noise (and parens, which will quickly get out of hand). I feel like it kind of misses the forest for the trees as far as helping someone see what's actually in the list.

While this is technically code that does indeed work, I'm not sure how useful it is as a Show instance since it's very much not compact. It's very difficult to see what the values are in the midst of all the other noise (and parens, which will quickly get out of hand). I feel like it kind of misses the forest for the trees as far as helping someone see what's actually in the list.

I feel like it kind of misses the forest for the trees as far as helping someone see what's actually in the list.

Seems like this would be less of a dilemma if we adopted debugged.

I feel like it kind of misses the forest for the trees as far as helping someone see what's actually in the list.

Seems like this would be less of a dilemma if we adopted debugged.

I personally think fromFoldable is the way to go for this.

I personally think fromFoldable is the way to go for this.

I still want to adopt debugged in core, but in any case I think we should continue providing Show instances for the foreseeable future.

I still want to adopt debugged in core, but in any case I think we should continue providing Show instances for the foreseeable future.

Let's use fromFoldable. Who's going to do the work?

Let's use fromFoldable. Who's going to do the work?

I'll come back to this once I'm done with the compiler releases notes. I'll never get them done if I find other ways to spend m'y PureScript budget 😬

I'll come back to this once I'm done with the compiler releases notes. I'll never get them done if I find other ways to spend m'y PureScript budget 😬

Does this PR only need these two changes?
-- adding parenthesis around `Step`'s `Cons` case
instance showStep :: Show a => Show (Step a) where
  show Nil = "Nil"
  show (Cons x xs) = "(" <> show x <> " : " <> show xs <> ")"

-- using the 'fromFoldable' approach:
instance showList :: Show a => Show (List a) where
  show ls = "fromFoldable [" <> print (step ls) <> "]"
    where
    print Nil = ""
    print (Cons x xs') = show x <> go (step xs')

    go Nil = ""
    go (Cons x xs') = ", " <> show x

Does this PR only need these two changes?
-- adding parenthesis around `Step`'s `Cons` case
instance showStep :: Show a => Show (Step a) where
  show Nil = "Nil"
  show (Cons x xs) = "(" <> show x <> " : " <> show xs <> ")"

-- using the 'fromFoldable' approach:
instance showList :: Show a => Show (List a) where
  show ls = "fromFoldable [" <> print (step ls) <> "]"
    where
    print Nil = ""
    print (Cons x xs') = show x <> go (step xs')

    go Nil = ""
    go (Cons x xs') = ", " <> show x

@kl0tl Mind if I push the changes I mentioned above here? If that's all we need to do, then we can get this PR merged.

@kl0tl Mind if I push the changes I mentioned above here? If that's all we need to do, then we can get this PR merged.

I pushed a patch based on your suggestion! Here’s the output of show for Data.List.Lazy.Types.List, Data.List.Lazy.Types.Step and Data.List.Lazy.Types.NonEmptyList:
> Data.List.Lazy.fromFoldable [0, 1, 2]
(fromFoldable [0,1,2])

> Data.List.Lazy.NonEmpty.fromFoldable [0, 1, 2]
(Just (NonEmptyList (defer \_ -> (NonEmpty 0 (fromFoldable [1,2])))))

> Data.List.Lazy.step (Data.List.Lazy.fromFoldable [0, 1, 2])
(0 : (fromFoldable [1,2]))

I pushed a patch based on your suggestion! Here’s the output of show for Data.List.Lazy.Types.List, Data.List.Lazy.Types.Step and Data.List.Lazy.Types.NonEmptyList:
> Data.List.Lazy.fromFoldable [0, 1, 2]
(fromFoldable [0,1,2])

> Data.List.Lazy.NonEmpty.fromFoldable [0, 1, 2]
(Just (NonEmptyList (defer \_ -> (NonEmpty 0 (fromFoldable [1,2])))))

> Data.List.Lazy.step (Data.List.Lazy.fromFoldable [0, 1, 2])
(0 : (fromFoldable [1,2]))

I also opened https://github.com/purescript/purescript-ordered-collections/pull/46 for consistency, so that we display arrays instead of lists when showing (non empty) sets.

I also opened https://github.com/purescript/purescript-ordered-collections/pull/46 for consistency, so that we display arrays instead of lists when showing (non empty) sets.

Any other feedback before we merge this?


Consider using nginx-unprivileged

Problem Statement
When deploying VMClarity with the current helm chart to a more restrictive Kubernetes environment, some components fail.
Especially the UI won't work, as the normal nginx image is used, which requires the usage of the root user or lots of adaptions (emptyDir Mount, high port, ...), which are currently not configurable via the helm chart.
Proposed Solution
I'd see two solutions:

Allow more flexibility in the helm chart, e.g. configuring the port of the UI Service, additional volume mounts for emptyDir etc.

Use a secure-by-default approach and use images like nginx-unprivileged and activate the podSecurityContext / containerSecurityContext for UI etc. per default (currently: enabled: false)

Alternatives Considered
There is no alternative to security ;)
Additional Context
n/a

Implemented


handle constraints on indirect dependencies

if I have this requirements.in
virtualenv

and this requirements.txt
distlib==0.3.8
    # via virtualenv
filelock==3.8.0
    # via virtualenv
platformdirs==2.6.2
    # via virtualenv
virtualenv==20.16.5

then pip-compile requirements.in and uv pip compile requirements.in -o requirements.txt do the same thing (no functional changes to the txt file) so everything is great
if I add this constraints.txt
filelock==3.8.0

and rm requirements.txt, then pip-compile requirements.in -c constraints.txt produces
distlib==0.3.8
    # via virtualenv
filelock==3.8.0
    # via
    #   -c constraints.txt
    #   virtualenv
platformdirs==3.11.0
    # via virtualenv
virtualenv==20.21.1

pip-compile picked the last version of virtualenv that supported the old filelock (20.22.0 requires filelock>=3.11)
however,
$ uv pip compile requirements.in -c constraints.txt -v
[...]
        0.008705s   3ms DEBUG uv_resolver::resolver Searching for a compatible version of virtualenv (*)
        0.008872s   4ms DEBUG uv_resolver::resolver Selecting: virtualenv==20.25.0 (virtualenv-20.25.0-py3-none-any.whl)
   uv_resolver::resolver::get_dependencies package=virtualenv, version=20.25.0
     uv_resolver::resolver::distributions_wait package_id=virtualenv-20.25.0
              0.009378s   0ms DEBUG uv_client::cached_client Found fresh response for: https://files.pythonhosted.org/packages/83/22/54b1180756d2d6194bcafb7425d437c3034c4bff92129c3e1e633079e2c4/virtualenv-20.25.0-py3-none-any.whl
error: There are conflicting versions for `filelock`: `filelock>=3.12.2, <4` does not intersect with `filelock==3.8.0`

Interesting, thank you for the clear report!

Ah yeah, ok, I see the issue here.

Have a fix but needs a few more test cases.

Hit this as well in my experimentation if you want another real-world case.  A one-liner repro:
# Doesn't work
uv pip compile <(printf '%s\n' 'psycopg[c]>=3') -c <(printf '%s\n' 'psycopg==3.1.13' 'psycopg-c==3.1.13')

# Works
uv pip compile <(printf '%s\n' 'psycopg[c]>=3') -o <(printf '%s\n' 'psycopg==3.1.13' 'psycopg-c==3.1.13')

Thank you! I'm hoping to fix it today.

Should be fixed in v0.1.7 (out now).


kubernetes/client: add Apply method

Codecov Report

Merging #21 (f0e0cff) into master (434bbd1) will decrease coverage by 7.43%.
The diff coverage is 93.18%.

@@            Coverage Diff             @@
##           master      #21      +/-   ##
==========================================
- Coverage   79.24%   71.82%   -7.43%
==========================================
  Files           7        9       +2
  Lines         212      291      +79
==========================================
+ Hits          168      209      +41
- Misses         38       75      +37
- Partials        6        7       +1

Files
Coverage Δ

kubernetes/client/apply.go
93.18% <93.18%> (ø)

... and 1 file with indirect coverage changes


Move newbranch to standalone package

As title.

blocked by #9664

@guillep2k done.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@f99c3e4). Click here to learn what that means.
The diff coverage is 46.93%.

@@            Coverage Diff            @@
##             master    #9627   +/-   ##
=========================================
  Coverage          ?   42.29%
=========================================
  Files             ?      599
  Lines             ?    78324
  Branches          ?        0
=========================================
  Hits              ?    33128
  Misses            ?    41142
  Partials          ?     4054

Impacted Files
Coverage Δ

modules/auth/admin.go
0% <ø> (ø)

models/migrations/migrations.go
1.3% <ø> (ø)

models/repo_generate.go
10.41% <ø> (ø)

modules/repository/repo.go
26.28% <0%> (ø)

routers/admin/orgs.go
0% <0%> (ø)

models/lfs.go
17.27% <0%> (ø)

modules/migrations/gitea.go
7.96% <0%> (ø)

routers/admin/users.go
28.69% <0%> (ø)

services/mirror/mirror.go
18.75% <0%> (ø)

models/migrations/v121.go
0% <0%> (ø)

... and 29 more

Continue to review full report at Codecov.

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