text:
Bug: Music Assistant cannot play music in HASS.Agent media player

Describe the bug
I am trying to make Music Assistant play music to my HASS.Agent media player but it simply doesn't work.
To Reproduce

Install Music Assistant
Import Media Player in Music Assistant using Home Assistant Player Provider
Try to play some music
Nothing happens

Expected behavior
To work :)
Screenshots
N/A
Misc info (please complete the following information):

Windows build (ideally screenshot/info of winver.exe output):

Windows' UI language: Portuguese Brazil
HASS.Agent version: 2.1.0

Please check what's applicable (multiple answers possible):

[x] Installed via installer
[ ] Installed manually
[x] Problem occurs in HASS.Agent
[ ] Problem occurs in Satellite Service

Additional context
The same issue doesn't happen to other speakers imported from Home Assistant.
Logs
2024-12-24 15:59:18.272 -03:00 [ERR] [STORAGE] Error while downloading file!
Remote URI: http://192.168.1.10:8097/flow/media_player.felipe_desktop/e5d84c5e0b6f4c99b565d59b76aadd2a.mp3?ts=1735066600
Local file: C:\Users\felip\AppData\Local\HASS.Agent\Client\cache\audio\20241224155639_8210808a.mp3
Error: The response ended prematurely.
2024-12-24 15:59:18.272 -03:00 [ERR] [STORAGE] Error while downloading file!
Remote URI: http://192.168.1.10:8097/flow/media_player.felipe_desktop/29e657e16d334ab6b3eaa322e22617f1.mp3?ts=1735066579
Local file: C:\Users\felip\AppData\Local\HASS.Agent\Client\cache\audio\20241224155617_590cff46.mp3
Error: The response ended prematurely.
2024-12-24 15:59:18.272 -03:00 [ERR] [STORAGE] Error while downloading file!
Remote URI: http://192.168.1.10:8097/flow/media_player.felipe_desktop/29e657e16d334ab6b3eaa322e22617f1.mp3?ts=1735066446
Local file: C:\Users\felip\AppData\Local\HASS.Agent\Client\cache\audio\20241224155405_b232b4bf.mp3
Error: The response ended prematurely.
2024-12-24 15:59:18.272 -03:00 [ERR] [STORAGE] Error while downloading file!
Remote URI: http://192.168.1.10:8097/flow/media_player.felipe_desktop/e5d84c5e0b6f4c99b565d59b76aadd2a.mp3?ts=1735066598
Local file: C:\Users\felip\AppData\Local\HASS.Agent\Client\cache\audio\20241224155638_878fddca.mp3
Error: The response ended prematurely.
2024-12-24 15:59:18.272 -03:00 [ERR] [STORAGE] Error while downloading file!
Remote URI: http://192.168.1.10:8097/flow/media_player.felipe_desktop/29e657e16d334ab6b3eaa322e22617f1.mp3?ts=1735066597
Local file: C:\Users\felip\AppData\Local\HASS.Agent\Client\cache\audio\20241224155636_f58ebbeb.mp3
Error: The response ended prematurely.

Fun thing, if I shut the Music Assistant server down, the music it was trying to play starts playing lol.

Fun thing, if I shut the Music Assistant server down, the music it was trying to play starts playing lol.

Same here, judging from the log and the partial audio clip after shutting down MASS, it seems somehow stuck in one of the streaming chunks. After killing the server the agent just plays what it received, which in my case varies between 20 sec and 1 min. I remember it was working in October so maybe MASS break something in the update?

Seems like the agent is trying to buffer the audio to local when playing from an HTTP link. I tried to remove the following lines (which let the MediaPlayer to simply stream the audio from the URL instead of downloading it to local first) and recompile, seems like it's working for now but I don't really know why.
https://github.com/hass-agent/HASS.Agent/blob/c75e2b9978bf73a084508c61deac5b2c934850f7/src/HASS.Agent/HASS.Agent/Media/MediaManager.cs#L397-L409
Also seems like the stream mode in MASS player settings must be set to "No content length" (which is the default):

Maybe HASS.Agent can detect when the stream is being sent with no content length and avoid buffering in such case?

Maybe HASS.Agent can detect when the stream is being sent with no content length and avoid buffering in such case?

I believe the content length is referring to the HTTP header which we need to send the request first to check. Maybe when media URL received we can do a HEAD request to prefetch the headers and check if Content-Length is present?

Looks like I'll finally have the incentive to install Music Assistant :D
Interesting that Music Assistant won't send the full file, unless something changed as whc2001 mentioned and now it operates only on streams (pure speculation tho)
Thanks for the report, I'll try to install it, do some testing and find a way to fix it.

This is going to be an interesting journey I see.
I replicated this + noticed an interesting behaviour, if I play 2 items via MASS none play at the beginning and then after some time the first one starts to play. What is more interesting, when trying to use the media url in the browser I always get
404 (Unknown Queue item: a44a7fb82c274fcdae6bb89b2d4fc2b4)

This is going to be an interesting journey I see.
I replicated this + noticed an interesting behaviour, if I play 2 items via MASS none play at the beginning and then after some time the first one starts to play. What is more interesting, when trying to use the media url in the browser I always get
404 (Unknown Queue item: a44a7fb82c274fcdae6bb89b2d4fc2b4)

The "Unknown Queue Item" error is because MASS detected non-playing state after a short period (which it assumes playback already finished), and removed the song from the queue. You can try the following which is rather interesting to me:

Turn on extended logging in agent
Use a text editor with auto following function (like VSCode) to open the most recent agent log
Start playing a song from MASS, the log should refresh the URL of that song
IMMEDIATELY click the link to open with your browser (otherwise it will timeout and be removed)
The song starts playing in the browser, the agent picks up the media session and it appears everything is normal as if the agent itself is playing the song

That's how I pinpointed that the problem is actually at the built-in player logic of the agent

I was writing this commend while you posted yours :D
You're quite correct, I was fast enough one time and it started playing.
I have a sneaky suspicion that if we'd wait long enough if not other items are in the queue (duration of the music file - which would cause the MASS to close the stream) the file would play in HASS.Agent.

So, good news and bad news.
Good: I was able to ducktape (for now of course) a crude logic that differentiates between a "file" and "stream" based on the content length properly (MASS doesn't provide it, I assume since it's stream), with that fix it works as expected
Bad: if you queue more than 1 media, MASS uses the same stream, i.e. HASS.Agent has no idea that the media changed
This is not consistent though since the http stream cannot be "sought" - track 1 going to 2 on it's own means no new stream, the first is reused but you scrolling to the end of track 1 means that new stream (new in terms of partice, URI stays the same) is created and request sent to HASS.Agent.

Thanks! I tried the "Force content length" option in MASS player settings and seems like it's sending a content length of 1728000000, not sure what it means but it seems pretty consistent. Also seems like there is an option to enable ICY metadata embedding into the stream, so maybe that can be ultilized to signal media changing? (Although I think for that the current implementation of the player would require a vastly change)

authors: amadeo-alex felipecrs whc2001


text:
Password BruteForce Error

[>] Wordlist    :> wlist.txt
[>] ProxyStatus :> [OFF]
[~] Brute ForceATTACK: Enabled [~]
[1] Trying Password[ {123456789} ]
[!] Error: a bytes-like object is required, not 'str'
[1] Trying Password[ {password} ]
[!] Error: a bytes-like object is required, not 'str'
[1] Trying Password[ {football} ]
[!] Error: a bytes-like object is required, not 'str'
[1] Trying Password[ {iloveyousomuch} ]
[!] Error: a bytes-like object is required, not 'str'
[1] Trying Password[ {fuckyou123} ]
[!] Error: a bytes-like object is required, not 'str'
[1] Trying Password[ {1234567} ]
[!] Error: a bytes-like object is required, not 'str'
[1] Trying Password[ {iloveyou} ]
[!] Error: a bytes-like object is required, not 'str'
[1] Trying Password[ {qwertyuiop} ]
[!] Error: a bytes-like object is required, not 'str'
[1] Trying Password[ {123456} ]
[!] Error: a bytes-like object is required, not 'str'
[1] Trying Password[ {password} ]
[!] Error: a bytes-like object is required, not 'str'
[1] Trying Password[ {12345678} ]
[!] Error: a bytes-like object is required, not 'str'
[1] Trying Password[ {qwerty} ]

HI, Please mention your environment specification.

source: gharchive/issue

repo: hassan-tahir/Faceboom

license: MIT

license_type: permissive

license_source: github-api


text:
Can't embed to iFrame

Problem/Motivation
By default, Uptime Kume doesn't allow being embedded in an iframe. Because of that, it cannot be added to the Home Assistant sidebar.
Expected behavior
Being able to access it from the sidebar
Actual behavior
Doesn't work
Steps to reproduce

(How can someone else make/see it happen)

Proposed changes
A UPTIME_KUMA_DISABLE_FRAME_SAMEORIGIN environment variable can be set to allow embedding in an iframe.

Can this ticket be re-opened? I'd like to know if @marciogranzotto proposed solution would work to have uptime kuma in HA sidebar

Can this ticket be re-opened? I'd like to know if @marciogranzotto proposed solution would work to have uptime kuma in HA sidebar

yes, I'm using my fork as a local add-on on my instance

authors: DavidJuanes marciogranzotto

repo: hassio-addons/addon-uptime-kuma


text:
Enable shellcheck linting in CI

Modify https://github.com/hasura/smooth-checkout-buildkite-plugin/blob/main/.github/workflows/lint.yml to install and run shell check

Maybe introduce a makefile that enables us to run make lint and make test. This could be used in CI and also in the README instructions.

repo: hasura/smooth-checkout-buildkite-plugin


text:
🛑 Git Server is down

In d3a7224, Git Server (https://git.arash-hatami.ir) was down:

HTTP code: 504
Response time: 15626 ms

Resolved: Git Server is back up in 32ddb36 after 9 minutes.


text:
🛑 Comment Server is down

In 5648e45, Comment Server (https://nikas.arash-hatami.ir) was down:

HTTP code: 502
Response time: 3549 ms

Resolved: Comment Server is back up in 2dac4f1.


text:
[Bug] Replan not triggered if the current rollouts reach the goal

Describtion
If the current rollouts can reach the goal, replanning will not be triggered. Thus some collision will happen while there are obstacles between ego and goal.
Required infomation:

ROS melodic (Ubuntu 18.04)
Autoware 1.15 + Openplanner 2.5
Simluator: LGSVL
Planner: op_global_planner + op_local_planner
Controller: pure_pursuit + twist_filter

Possible Root Cause and Solution
Root Cause
In src/autoware/common/op_planner/src/DecisionMaker.cpp, preCalcPrams->bFinalLocalTrajectory is used to judge if current local path can reach the goal, and while preCalcPrams->bFinalLocalTrajectory is true, replan won't be triggered.
Possible Solution
Disable preCalcPrams->bFinalLocalTrajectory, making the replan continue to be triggered after the point where the local path could reach the goal.
To be specific,  update line 380-387 in DecisionMaker.cpp to:
if(m_Path.size() > 0 && m_TotalOriginalPaths.size() > 0)
{
	double d_between_ends = hypot(m_TotalOriginalPaths.at(m_iCurrentTotalPathId).back().pos.y - m_Path.back().pos.y, m_TotalOriginalPaths.at(m_iCurrentTotalPathId).back().pos.x - m_Path.back().pos.x);
	if(d_between_ends < m_params.pathDensity)
	{
		// pValues->bFinalLocalTrajectory = true;
	}
}

Demostration Video
Video to demonstrate this hazard: https://youtu.be/F5UjRHmLVUE
In this scenario, ego won't select a better trajectory to avoid the truck since the replan is not triggered. This scenario was tested more than 10 times and the collision always happened.
After applying the patch above, the collision won't happend (tested more than 10 times and none of them involved the collision). Video: https://youtu.be/6uezdQ3w2FU
@hatem-darweesh

Thank you for contributing to OpenPlanner.
This a know design decision, for some projects we want to disable avoidance in the last section. But follow should work.
In your video the ego vehicle stopped, but it got hit by the truck.
You can fix it in your version.
Or add a hyper parameter in op_common_param that enable and disable this feature. If so, please submit a pull request.

Thanks for your reply !
I will try to find a better solution.

@blabla-my
consider this scenario:
The goal position is actually a bus stop, so you want to bus to stop exactly in the stopping location.
if the avoidance is enabled the bus may stop in the middle of the road if there is another bus or car stopping before or at the bus stop.

Thanks! This is a very nice case to understand why you say that no replan in last section is a design.

However, I think it's better for ego to have some ability to avoid, but not too strong ability.
For your example, I think the second should preserve its ability to slightly adjust its pose for avoidance, but not go over the first bus to reach goal.

It is an application dependent feature. So everyone can customize accordingly

It is an application dependent feature. So everyone can customize accordingly
@hatem-darweesh Hi  Hatem, I've introduced a new hyperparameter that offers users greater flexibility in configuring this feature. I've submitted a pull request for your review and eagerly await your response. Thank you!
https://github.com/hatem-darweesh/common/pull/18
https://github.com/hatem-darweesh/core_planning/pull/17

authors: AV-Security blabla-my hatem-darweesh


text:
はてなブログ独自の書き方をスニペットとして提供する

画像のキャプションや横並びなどは、WebUIでは自動で挿入されるが、独自classやtitle属性などが含まれており外部エディタで手書きするのは困難。
そこでスニペットを提供し、利用しやすくしたい。

ありがとうございます！マージします

source: gharchive/pull-request


text:
redirect helper and other minor changes

Hi hatzel, nice crate!
I've added a simple helper method for redirecting on response (see https://github.com/hatzel/actix-web-flash/issues/1).
I also made a couple other minor, unsolicited changes:

Defined an "empty" const Tm, so that a time would not have to be parsed on every expiration. I would need to double check, but I think this evaluates to something like "1900-01-01", so it should work fine.
Removed the Future::wait lines. I don't know enough about actix-web's internals to know if these were actually safe, but they were making me nervous.

Great changes, especially the not waiting for the future. Thanks!
I'd love it if you could split those up into separate commits with somewhat descriptive messages (maybe one each for time object, redirect and proper future handling), otherwise I'll do to it when I have the time :)

I split the commits up and took care to preserver your authorship of the commits. Thanks again! Had to do it on anther branch though (obviously can't force push to yours).

Sorry, I didn't get around to this! Thanks!

authors: hatzel kardeiz

repo: hatzel/actix-web-flash


text:
fix(windows)!: remove deprecated platform

Since Windows platoform has been marked as deprecated this PR removes the deprecated platform
How Has This Been Tested?
Ran cordova plugin add

@seamlink-aalves I think there are few other places in the repo that was missed.
E.g.

.eslintrc.yml
plugin.xml<description>Enable receiving push notifications on Android, iOS and Windows devices. Android uses Firebase Cloud Messaging. iOS uses Apple APNS Notifications. Windows uses Microsoft WNS Notifications.</description>

docs\API.md
docs\EXAMPLES.md
docs\PAYLOAD.md
spec\index.spec.js

If you can remove all or modify sentences to exclude Windows that would be good.
You should be able to find all references by using windows as the search keyword..
The only place that should not be removed is from .github\workflows\ci.yml... This is just to tests if there is any issues using  windows as a development environment. Not related to the Cordova-Windows platform.

Hi @erisu, I've removed the remaing windows platform references.

authors: erisu seamlink-aalves

repo: havesource/cordova-plugin-push


text:
Grid类bug

Grid类下的recursiveJoin方法有一句static::recursiveJoin($joins, $k)，具体意义不明，会导致部分页面死循环，注释掉就正常了

仔细研究了一下，应该是341行的判断出的问题。把==改成===或者全转换成字符串应该就正常了

c0e035a 已经修复

authors: Hahawillll hawind

repo: hawind/gdoo


text:
clean up yaml

This is a PR that doesn't change any functionality - but it does clean up the yaml config files. There are lots of trivial changes here (we had some weird spacing/indentation in many values and quoted things we didn't need to) - just doing this all at once to make the yaml files more consistent and will avoid irrelevant diffs later if this gets fixed little by little. Just do it all now in this PR. Similar PR was done to the server-side configs in commons.

see also https://github.com/hawkular/hawkular-commons/pull/196

repo: hawkular/hawkular-agent

license_source: bigquery


text:
[POC][WIP] [TurnBackNow!] [BewareOfDog!]

@lucasponce This is a total POC just to look at and talk around.  I figured I'd look at RxJava and see what it may be able to do.  As this stands it does work, the i-tests pass.  If I understand things it will currently do filtering (if necessary, not necessary when sent from metrics) and then return the the caller and do the rest async.

Take this for what it is worth, but in my experience trying to learn something like RxJava which is both functional and reactive is a lot more difficult when you mix it with imperative, non-reactive code. In fact it won't surprise me if you find it to be little more than an obstruction. Start with something small like a method that fetches some records from the database, applies some transformations, fetches related data, etc, and try to implement it using only Rx operators. It will probably take you a while :) You will likely end up code that is much more concise than the imperative version.

Take this for what it is worth, but in my experience trying to learn something like RxJava which is both functional and reactive is a lot more difficult when you mix it with imperative, non-reactive code.

I don't really disagree.  But we're certainly not going to replace existing, working code just for something shiny.  And we're likely not going to use Rx here, either.  But, given the provider/consumer scenario here, I thought it was worth giving it a try as a potential entry point.  And honestly I wanted to just play with it a bit.   It did drop in fairly seamlessly and the async handoff is natural.
But I imply from your comment that you think it's likely a bad idea for use here.

I am not necessarily suggesting that it is a bad idea here. While I think RxJava and reactive/functional is great, it is difficult to grasp, and mixing with imperative, non-reactive code may not help with making a good first impression.
I definitely do not think it is a bad idea to use here :)

I don't have anything against RxJava, Spring, Netty, Vertx to cite some examples of Java APIs.
My comment was more related to the point that in Java EE some of those frameworks can overlaps resources and pattern that are available in Wildfly and Java EE.

I was going to avoid starting a debate, but what the hell, it's Friday :)  I haven't used Spring in a long time so I won't comment on it. RxJava, Netty, and Vertx have something in common that separates them from JEE. They are libraries, not frameworks which require you to write and run your code in some container or managed environment. Why do I care about this particular fact? One main reason - testing. Testing RxJava code is easy. In Hawkular Metrics we can easily write tests directly against our service layer which I think this is important to have and do. I do not see the same in Alerts, and I imagine that is at least partly due to the fact that it is not easy to test JEE/EJB code. Arquillian can/maybe/sorta/kinda make things easier if/when you actually get it set up and working. Suffice it to say Arquillian brings with it a steep investment.
I disagree about how much WildFly/JEE offers for a Cassandra based application such as Hawkular Metrics/Alerts. JEE offers a lot in terms of resource management for RDBMS, but it offers none of that for Cassandra. In fact, the DataStax driver handles all aspects of resource management.
Cassandra does not have transactions, which are one of the biggest selling points of EJB. On that basis alone, I do not a good reason for using EJB with Cassandra. I suppose one could argue that with EJB you have container managed concurrency. Once again, there is no need for it whatsoever since the Cassandra driver is async. If you use the asyc APIs and make your code async, there is a lot less need for thread pools.
Async code requires less resources and offers better performance. There isn't anything in WildFly/JEE to help with writing and building async code. There is stuff in Java 8 like CompletableFuture, but the driver predates Java 8 and was implemented using Guava's Futures. Guava's ListenableFuture is a major improvement over plain Futures, but there are still plenty of shortcomings. In Metrics we have found RxJava to be a much better fit. If we were to rewrite Metrics without RxJava using more imperative code, we would likely have at least twice as much code as we do now. No thanks.
Reactive streams are coming in Java 9 which means we will probably see them in JEE at some point, like 4 or 5 years down the road :)

I'm going to close this PR, although the discussion is good.  Thanks @jsanda for your feedback!  We will keep an eye on Rx, particularly where we may be able to introduce it in a botton-up use-case.  For now I expect we will not drop this paradigm into the middle of the mix.

authors: jsanda jshaughn

repo: hawkular/hawkular-alerts


text:
Method for generating tokens for capabilities?

We need to determine how the kernel will generate tokens to represent capabilities. These are essentially key pairs. Of course, it's necessary to generate capability tokens securely, necessitating some kind of crypto inside the kernel. However, we also want to be able to both generate and verify them quickly, since I suspect both generating and checking capability tokens will become a bottleneck – since it has to happen every time a syscall is performed.
I think we'll want to incorporate some run-specific entropy sources in the capability generation algorithm, to protect against attacks where malicious code saves a legitimately-granted capability for later use, when it is no longer granted that capability.

@twisted-pear, any thoughts?

Ok, as for the capabilities themselves: Do we really want to implement caps as keys that we check as opposed to "some datastructure the kernel keeps on behalf of a userland process"? Aside from the mentioned performance problems we also run into things like:

Are we ok with a process arbitrarily sharing it's capabilities? Or how do we prevent that?
How do we prevent accidental leakage? Timing side-channels etc.
What about freshness of the tokens? Are they valid forever?
I suspect that you have already looked into capability systems (i haven't) so maybe there are simple answers to these concerns,

The second part is about entropy. Yes, we need an entropy pool in the kernel that is capable to provide us with good randomness. IIRC there are tried and true constructs for such systems where you have a way to seed and regularly reseed such a pool and also check if it has bees seeded at least once and where things like forward-/backward-secrecy are already considered. I'd have to dig through some crypto literature but the names I remember are "Yarrow" and "Fortuna" I think. Not sure if these are still state of the art or if there are now better ways to do it.
Incidentally, using such a system will probably require some sort of cipher or hash function, so it might be prudent to implement a small crypto lib first that gives us access to say AES and SHA-3 primitives.
End braindump.

I suspect that you have already looked into capability systems (i haven't) so maybe there are simple answers to these concerns,

I've done a little research, but not nearly enough. This is far enough in the future that it's just something I was thinking about.

Do we really want to implement caps as keys that we check as opposed to "some datastructure the kernel keeps on behalf of a userland process"?

I had originally wanted the process to own half of a keypair, but that might be massively over-engineered and just having the kernel do all the bookkeeping could be a better solution.

• Are we ok with a process arbitrarily sharing it's capabilities? Or how do we prevent that?

Not sure. I'm thinking that caps are granted to specific processes and can't be shared. There might be some kind of sharing rules for child processes? This is its' own design issue I think.

• What about freshness of the tokens? Are they valid forever?
Hmm. I think caps definitely can't outlive the lifetime of a process, not sure if they need to be refreshed within its lifespan? I think if the caps are granular enough, it should be reasonable to let a process keep a cap once it's granted once...

Probably a good starting place for further research is "how does seL4 do it"...

The thing is if we use keys like you suggested, what is to stop a process from giving its key to another process, write it to disk, send it over network etc?
The freshness thing is kinda related to this. We'd need to invalidate keys once a process terminates, but if we already do that kind of bookkeeping...

The thing is if we use keys like you suggested, what is to stop a process from giving its key to another process, write it to disk, send it over network etc?

My initial thought was some kind of hash function involving the process's PID and the key. I'm not sure how practical that is or if there's some kind of attack based on having a predictable PID. Just a shower thought at this point.

Having the kernel do all the bookkeeping may end up being a more workable solution. I just find the  elegance of handing out capability objects that bundle together permission & behaviour to be really appealing.

Hmm – and this is probably a terrible idea, just something that popped into my head – what if requesting a cap got you back a sort of kernel mode thunk? Like the kernel basically JITs you a binary blob that performs whatever syscall you wanted...

a quick glance at the seL4 FAQ would suggest that they actually have the kernel do the bookkeeping for caps and don't rely on crypto...

hmmm, but that would allow you to place arbitrary executable stuff in kernel mem, right?

it sounds like an invitation for jit spraying but maybe i'm wrong

a quick glance at the seL4 FAQ would suggest that they actually have the kernel do the bookkeeping for caps and don't rely on crypto...

I'm getting the sense that's probably the right way to go...which is a shame, crypto is fun.

hmmm, but that would allow you to place arbitrary executable stuff in kernel mem, right?

it sounds like an invitation for jit spraying but maybe i'm wrong

I did say this was a bad idea, didn't I? :P There's also the issue that pulling this off would take some black magic with address spaces.

nevertheless, the kernel is the only place where you can implement an entropy pool and it's something very useful for a lot of other things

yeah we definitely should have a nice source of randomness in kernel space regardless.

authors: hawkw twisted-pear

repo: hawkw/sos-kernel


text:
High memory usage

I run gulp-favicons with these options:
gulp.src('icon.png')
.pipe(favicons({
        appName: 'My App',
        display: 'standalone',
        orientation: 'portrait',
        version: '1.0.0',
        path: 'favicons/',
        url: 'http://example.com/,
        html: 'index.html',
        replace: true,
        icons: {
            android: true,
            appleIcon: true,
            appleStartup: true,
            coast: true,
            favicons: true,
            firefox: true,
            opengraph: true,
            twitter: true,
            windows: true,
            yandex: true
        }
    }))

icon.png has 2048x2048 size.
My machine has 2GB memory and 2GB swap. Favicons generation takes 40 seconds and often fails because there is no free memory and system kills the process.
Why memory consumption is so high and what optimizations could I apply?

@mxl Your image should be a maximum of 1500x1500 - the size of the OpenGraph image. Anything above that is overkill. Other than that, I have no idea. Perhaps there are code optimisations to be done.

Got the same issue just now. When the favicon generation starts, memory fills up really fast and process is killed by the kernel. icon.png is 1024x1024, tried online & offline generation.

Not sure there's much I can do about it. I get around this on my remote SSD with 2GB of RAM by creating a massive swapfile. Online generation is done on the RFG servers so it's a valid workaround but you get a slightly different result. Not sure what I can do about this for now, it's just a memory-intense module.

Looks like an issue with Jimp https://github.com/oliver-moran/jimp/issues/153

authors: LeZuse haydenbleasel mbardelmeijer mxl

repo: haydenbleasel/favicons

license: mit


text:
Error: Duplicate typename: Another type with name Type already exists.

Can't change the code while changing my code showing Error: Duplicate typename: Another type with name Type already exists. I'm using vite for development with vite-plugin-node

Can you try adding the following to your vite config?
ssr: {
   noExternal: ['@pothos/core']
}

Can you try adding the following to your vite config?
ssr: {
   noExternal: ['@pothos/core']
}

that didn't work either. But i did managed to do so. I imported all my types to a file, then i imported that file in my schema.ts as normal import "./imports" but also added an import("./imports") to my builder.ts file and that worked for me. :-)

This workaround might also help: https://github.com/hayes/pothos/issues/49#issuecomment-836056530
Need to write some docs on how to set up vite, I don't have much personal experience with that yet.

thank you 😄  but i managed to fix my problems.

that didn't work either. But i did managed to do so. I imported all my types to a file, then i imported that file in my schema.ts as normal import "./imports" but also added an import("./imports") to my builder.ts file and that worked for me. :-)

That makes sense, I think the solution I linked to above is effectively the same thing.  Glad its working for you!

repo: hayes/pothos

license: ISC


text:
[Core UI] FormGroup

https://developer.mozilla.org/en-US/docs/Web/HTML/Element/fieldset
@pawelklasa we need the design

@pawelklasa What was the idea of this component? Maybe it's an outdated issue?

authors: aigoncharov fantkolja

repo: hazelcast/hive


text:
tylr - the most amazing project I've ever seen!

Hi everyone.
idea

I believe that tylr's graphical interface is very innovative. What I'm going to talk about here is different, unique and strange.
Lately I've been getting involved a lot with open projects - of all types and sizes. And of different types of audience and purpose or scope.
One thing that has always caught my attention is version control: git.

why?

I use git version control a lot to manage each of these open projects that I talked about initially, but... one of my problems with git is its complex commands for an end user like me. There are no great GUIs for git. I'm thinking of using tylr for git.
One of the things that caught my attention is the idea of how tylr is made. One crazy idea I had was to create a git client with a block interface instead of typing commands.

how?

In my idea it would be possible to use git as a block with tylr.
I've been developing an idea of a version control made from blocks of code and related to a database.
My idea is to make life easier for developers by creating something as innovative as git. One of the ideas that I consider to be good is to use the graphical interface of tylr to manage the version control.

example?

img-description: My idea would be to have positional version control, with that in mind we have a versioned dictionary of words in any programming language for any open project. So, as we can see in the conceptual image we have a code block in tylr to control the software version.
source-code
Here we have a positional version control generated by tylr - we know words or code snippet has been removed, added.
0-43:h3
45-139:p
1185-1191:em

What do you think of this idea? What do you think of this idea of a command-block interface?

@codehangen thanks for the feedback!
I'm not entirely clear what your git proposal is getting at but we're working on making tylr more ready for experimenting with by making it into an editor generator.

authors: codehangen cyrus-

repo: hazelgrove/tylr


text:
how the ListModelView can work with 'filters' query parameter?

when get the list view, the query parameter filters must be blank ,or it says "Input should be None".

sorry, i find another releated issue. close it.

@hbakri i am sorry, but the releated PR seem doesn't release or publish.

Hi @horizon365! Thanks for raising this issue, I apologize for the inconvenience caused by the bug.
You're correct that the current version (0.4.1) doesn't include the fix. I had addressed this in a previous PR a long time ago but mistakenly held back the changes for a major release instead of releasing them promptly.
The good news is that version 1.0, releasing this weekend, will include this fix along with a lot of other improvements and features! 🙌
As a workaround, you can use explicit None values for the query parameter filters when fetching the list view in Django Ninja's API docs.

repo: hbakri/django-ninja-crud


text:
Lesson 1 comments

"enriched by immunoprecipitation from cross-linked cells"
Consider defining more clearly what you mean as this is a bit jargon-y. Perhaps this would be clear from the lectures though.
"Test your antibody with the use of a Western blot"
I've never done a Western, but this sentence and the following one seem a bit vague as to what one should be looking for.
"Check a few regions by qPCR to confirm that the enrichment worked."
Also, this could be more clear. Something like "expected immunoprecipated regions"?
"TSSs you could design primers against the promoter "
Maybe too nitpick, but I am a bit confused by the use of "against" here. Are you using it in the context of adjacent or in the context of encompassing?
IgG control section is unclear. I don't fully understand what this is. Is this DNA added to the sample at some point? If so, when is this added? What is this non-nuclear antigen?
Quality Control, Input Control, Replicates and Sequencing Considerations lack any figures. Some figures would likely improve readability. First, it breaks up the wall of text, which is already somewhat achieved by bullets and is great. Second, it just helps the reader visualize exactly what you are trying to show.
Define Narrow vs. Broad peak profiles.

"NOTE on pooling to increase the amount of starting material. Is it okay? Under what circumstances?"
Need to add wording here.

"NOTE on pooling to increase the amount of starting material. Is it okay? Under what circumstances?"
Need to add wording here.

Getting @sjhosui  thoughts on this and will fill in the text

Made a few edits -
added a link to Western blots rather than explaining it.
reworded the PCR text a bit

edited IgG control, @Gammerdinger  let me know your thoughts

repo: hbctraining/Intro-to-ChIPseq-flipped


text:
Reduce emulator CPU usage

Changing the SDL user input detection from poll to wait significantly reduces the emulators CPU usage.
I don't know if there was a reason why poll was chosen initially but wait seems to work fine.

Tested looks good

authors: Nikolas-S SumolX

repo: hd-zero/hdzero-goggle


text:
Add base error display alongside existing errors

#1466

Thanks a lot. Sorry, I am a beginner.. Is there somewhere an article on how to include this in my project master branch?
Thanks a lot
Fabrizio

@fabriziobertoglio1987 You should be able to do a git pull on
https://github.com/bluefalcon26/simple_form.git:addBaseErrorDisplay

Ok, thanks a lot. I will search for instruction on github to do a pull. I never have done one ..
Thanks
Fabrizio

@bluefalcon26 Thank you for the pull request 😄 . Could you rebase it with the master branch?
I don't see problems in adding it in the generator, @rafaelfranca any thoughts?

Is this pull request the reason why there are two "duplicate" lines?
<%= f.error_notification %>
<%= f.error_notification message: f.object.errors[:base].to_sentence if f.object.errors[:base].present? %>

What is the reason for having this duplication?

Is this pull request the reason why there are two "duplicate" lines?
<%= f.error_notification %>
<%= f.error_notification message: f.object.errors[:base].to_sentence if f.object.errors[:base].present? %>

What is the reason for having this duplication?

f.error_notification <> f.object.errors[:base]
The second line adds error details if they are present. In your case, are you getting error details in the first line, or are you getting two error lines without details?

@bluefalcon26 Thanks for the reply. Does f.error_notification alone display only a fixed message defined in YML (e.g. There are some errors) or it may include the specific runtime errors on some occasions? I'm tempted to remove the first f.error_notification since the errors are already displayed nicely below each field.

Go ahead, it's possible things have changed since I was working with this
and it may be superceded. Only thing I would say is before you do, double
check the interaction on nested forms. It's been a long time but I seem to
recall that being part of the rationale for my original pull request.
Daniel
On Thu, Jan 13, 2022, 18:39 Marco Colli @.***> wrote:

@bluefalcon26 https://github.com/bluefalcon26 Thanks for the reply.
Does f.error_notification alone display only a fixed message defined in
YML (e.g. There are some errors) or it may include the specific runtime
errors on some occasions? I'm tempted to remove the first
f.error_notification since the errors are already displayed nicely below
each field.
—
Reply to this email directly, view it on GitHub
https://github.com/heartcombo/simple_form/pull/1465#issuecomment-1012617026,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABIZQOYW3I7TB6TAPKTVIWDUV5PBRANCNFSM4DA55O4A
.
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.
You are receiving this because you were mentioned.Message ID:
@.***>


text:
fix: DEV-2146: Lock rect VideoRectangle

Hi @juliosgarbi!
This PR was created in response to a PRs in upstream repo:

https://github.com/heartexlabs/label-studio-frontend/pull/758

/frontend build lsf master

/frontend build lsf master

/frontend build lsf fb-dev-2146

authors: juliosgarbi robot-ci-heartex

repo: heartexlabs/label-studio


text:
cmake, doc: Update build-osx.md

Following the instructions on a fresh install revealed a few inaccuracies.

@pablomartin4btc
Thank you for fixing the docs!
How about https://github.com/hebasto/bitcoin/commit/8f492874f92810771bd6ba0b4ed33833fe2a3315, which is more concise and does not assume autodetection of the sqlite package?
Feel free to grab it, if you agree.

Feel free to grab it, if you agree.

Yeah, it makes sense, thanks!

repo: hebasto/bitcoin


text:
Cube map is black!

I'm trying to make a Cube map from raymarched scene but It is black!
https://docs.unity3d.com/ScriptReference/Camera.RenderToCubemap.html
https://lmhpoly.com/how-to-generate-the-environment-cubemap-in-unity/

If you use RaymarchingRenderer, please replace it with a large-scale cube which uses the same distance function (please refer to Mod World for VR as an example or the No lighting with RaymarchingRenderer in forward path section in readme). RaymarchingRenderer uses CommandBuffer to render raymarched objects but this does not affect the camera created by RenderCubemapWizard.

thanks it works like charm I could make a cube map!
can you explain what you used to fix this issue because I have same issue in this shader:
https://github.com/Flafla2/Generic-Raymarch-Unity

Generic-Raymarch-Unity uses ImageEffect to render raymarch objects. The cameras which create a cubemap doesn't use ImageEffect to get clear images (please think about that bloom or depth-of-field shouldn't be used for these images). On the other hand, The above method of uRaymarching uses just polygons to render raymarch objects. So cubemap cameras can see these objects.
To fix this problem in Generic-Raymarch-Unity, you have to customize the shader to use a full-screen quad mesh to render raymarched objects instead of ImageEffect.

authors: hecomi smkplus

repo: hecomi/uRaymarching


text:
Update ECOSYSTEM and ROADMAP

This PR updates the ECOSYSTEM guide and the ROADMAP.

Nice clear docs :+1:

authors: dhardy hecrj

repo: hecrj/iced


text:
Missing include parameter

Until now, the include parameter of the API, which serves for including special data formats, may not be used.
I will open a PR which would add this feature, if you're interested.

Hello,
I am not using this package anymore, but please submit a pull request.
Please be careful about php and guzzle version constrain (I saw your previous PR which included return types and a new guzzle version, i think it should not).

authors: dikastes hedii

repo: hedii/zotero-api


text:
Could you please explain connect-timeout and read-write timeout?

Could you please explain in more detail connect-timeout and read-write timeout ?
Specific context:
suppose I'm trying to proxy a TCP connection that's supposed to be long-lived and receive only rather occasional keepalives (like android GMS service's "heartbeat" which often beats like once 10 minutes or so) and don't expect to roam that much
Which value should I increase, if any?

connect-timeout: The maximum waiting time that from the beginning of connecting to the remote host to the successful establishment of the connection.
read-write-timrout: After the connection is established, the maximum idle time without transmission in both directions.

Which value should I increase, if any?

read-write-timeout

Thanks!

authors: LindaFerum heiher


text:
Generieren deaktivieren, wenn Images referenziert werden, die noch nicht hochgeladen sind

Sinnvollerweise sollte der Backend-Service beim Laden der Details gleich prüfen, ob alle referenzierten Images bereits hochgeladen sind. Dann könnte ein GrafikStatus-Array mit in die Details aufgenommen werden und so die GUI gesteuert.

Falls nicht, dann Warnung anzeigen mit den fehlenden Image-Pfaden.


text:
Azure IoT Hub "Error Not Connected"

Describe the bug
Azure IoT Hub is not connecting in Integrations.
The integration message is as follows:
{
"category": "uplink",
"description": "Error: not_connected",
"device_id": "e429da00-b945-4a6b-b376-225ad295ff34",
"device_name": "netvox_sn201600012",
"id": "f7218861-ccd1-4196-b323-3fb83cb59ae5",
"inserted_at": "2022-02-25T09:33:34",
"organization_id": "a8dfd2a1-e0a6-46a5-8a72-8da583bec2ce",
"reported_at": "1645781614052",
"reported_at_naive": "2022-02-25T09:33:34",
"router_uuid": "d5fa956c-2b93-4711-8cbe-5aa78f196397",
"sub_category": "uplink_integration_req",
"updated_at": "2022-02-25T09:33:34"
}
To Reproduce
Configure integration for Azure IoT hub. See pictures for my flow.
Expected behavior
Integration to work as expected prior to console v2.2.2 release
Device Info (please complete the following information):
-Prod
-76549ca0-1b54-4e10-9ba3-0416660aa456
-All devices
-Every few minutes
-Au
-Alert Pear Tiger
Additional context
Raising this new bug report as mentioned by @michaeldjeffrey here https://github.com/helium/router/issues/625
Screenshots

The IoT integration is working again! What occurred?

@EnrSal glad to hear it!
@DavidDeeds could you check your integration again and verify things are working for you as well?
There is/was an ongoing issue with our container manager (quay) where the new 2022.02.17.1 was unpullable through the tag production. The last deploy was "successful" in that it couldn't pull and rolled back to the last image it had access to.
During looking into this I noticed some integrations had incorrect Hub Names and malformed tokens.
This has been added: https://github.com/helium/console/issues/1061
And we're talking about what better error reporting for mqtt type connections.

Yes! Confirmed working now - thanks so much!!!

authors: DavidDeeds EnrSal michaeldjeffrey

repo: helium/router


text:
Simpler Get() Pattern

It would be nice to have .Get() functionality that takes in something like an XPath as an input and returns the right struct with the data populated. Or alternatively, to have native accessors generated.
For example:
worksheet person {
1:address address
2:pets    []pet
}

worksheet address {
1:line string
2:zip  string
3:city city
}

worksheet pet {
1:name string
}

It would be nice if I just wanted city to say: ws.Get("person.address.city")or perhaps have it codegen to something like ws.Person().Address().City(). The latter option would let use also iterate over fields a bit more succintly:
for _, pet := ws.Person().Pets() {
  print(pet.Name())
}

@pratikprasad How do you suggest handling undefined? In your example ws.Person() could be either undefined or an instance of a person worksheet. For .Pets(), slices would be empty if nothing was ever appended, so this would work nicely.
The codegen route is consistent with accessors provided by protos or thrift and make sense to me in this context.

authors: pascallouisperez pratikprasad

repo: helloeave/worksheets


text:
ccaa的网页端口6080在哪更换？

是ngix还是apache搭建的呢？在哪个文件夹下，小鸡被墙了，不方便查找。。请教一下大佬。

用的是Caddy，这个问题参考帮助文档：管理 & 维护 - 文件说明可解决。

我在Caddy里更改了端口为80，或者其他端口，都无法访问，只能是6080的时候才可以访问。
------------------ 原始邮件 ------------------
发件人: "Mr.zou"notifications@github.com;
发送时间: 2019年6月5日(星期三) 下午5:23
收件人: "helloxz/ccaa"ccaa@noreply.github.com;
抄送: "Trojan Knife"376686131@qq.com; "Author"author@noreply.github.com;
主题: Re: [helloxz/ccaa] ccaa的网页端口6080在哪更换？ (#10)
用的是Caddy，这个问题参考帮助文档：管理&维护-文件说明可解决。
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub , or mute the thread .

修改端口后需要重启ccaa：ccaa restart
检查80端口是否被其它进程占用：netstat -apn|grep '80'
设置了新端口，记得你服务器的防火墙、安全组将对应端口放行

谢谢大佬，忘记关防火墙了，OK
------------------ 原始邮件 ------------------
发件人: "Mr.zou"notifications@github.com;
发送时间: 2019年6月5日(星期三) 晚上11:48
收件人: "helloxz/ccaa"ccaa@noreply.github.com;
抄送: "Trojan Knife"376686131@qq.com; "Author"author@noreply.github.com;
主题: Re: [helloxz/ccaa] ccaa的网页端口6080在哪更换？ (#10)
修改端口后需要重启ccaa：ccaa restart
检查80端口是否被其它进程占用：netstat -apn|grep '80'
设置了新端口，记得你服务器的防火墙、安全组将对应端口放行
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub , or mute the thread .

authors: helloxz sjkgames

repo: helloxz/ccaa


text:
[stable/nginx-ingress] high availability / production configuration

Version of Helm and Kubernetes:
helm 2.14.x, k8s 1.13.x, latest nginx-ingress (1.13.x)
The default configuration of nginx-ingress will cause an outage during cluster upgrades, chart upgrades, etc.
I'm having difficulty finding info on how people configure nginx-ingress for production purposes.
So with that said:
How should the nginx-ingress be configured for high availability?

By default, nginx-ingress is configured to use 1 pod replica.. I presume this should be at least 2? Will 2 give me HA? (How is this affected by minAvailable?)

The minAvailable is set to 1. If you deploy this entirely default (with replica to 1), then presumably the pod will never be terminated due to the pod disruption budget? If the replica count is 2, will the PDB of 1 be satisfied? Do I need 3 pods minimum? Should I be concerned if all pods are scheduled on the same node...?

There aren't affinity rules by default; is this important? Should only one controller pod be scheduled per node? If I leave this blank, is there the possibility of an outage?

There is no default update strategy (should it be rolling...?) Does this matter?

Do most people entirely forego nginx-ingress and use a service: LoadBalancer for production uses? Do they use a different Ingress provider? Considering nginx-ingress is in the kubernetes/ org I assume it's fairly official, but do people rely on it?

Consider this a "pre-emptive fix to a pre-emptive bug report" 😉 This issue sounded a little complain-y, but I don't mean it that way. I just legitimately need advice and haven't found resources on how people use this in production.
Thanks for your time.

@aegershman it's alredy became an issue for me, do you know how to fix this problem?
I'm having this problem in production...

In short: you should bump the pod replica count to >1 and you should set affinity rules for the replicas to be deployed on other nodes and preferably in other availability zones. Depending on the cluster size you may also want to increase minAvailable value so that even during pod updates or node upgrades you would still have at least the minAvailable number of pods available (on a small cluster higher minAvailable value + pod affinity rules might make it unschedulable during certain situations).

authors: aegershman marcelomanchester pranas

repo: helm/charts


text:
[stable/postgresql] Pods fail to create

Describe the bug
I attempted to deploy v6.3.4 of the stable postgresql chart with HA (replication) and ended up with a deployment that could not create the master pod nor the slave pod. The error messages from each pod are listed below, along with the override values.
Version of Helm and Kubernetes:
Helm v2.14.2
Kubernetes v1.13
What you expected to happen:
I expect all master pods and slave pods to be created for a HA deployment.
How to reproduce it (as minimally and precisely as possible):

helm create chart_override_name

Delete default templates and values.

helm fetch stable/postgresql

unzip stable chart

Move postgresql chart into custom chart's chart folder.
Use the override values provided below.

Anything else we need to know:
Master pod error:
Error from server (BadRequest): a container name must be specified for pod app-db-postgresql-master-0, choose one of: [app-db-postgresql metrics] or one of the init containers: [init-chmod-data]
Slave pod error:
/entrypoint.sh: line 15: nENk: unbound variable
Chart override
postgresql:
  postgresqlUsername: postgresql
  postgresqlPassword: xyz
  postgresqlDatabase: newdb
  replication:
    enabled: true
    slaveReplicas: 3
    synchronousCommit: "on"
    numSynchronousReplicas: 1
    applicationName: app-db
  metrics:
    enabled: true

Hi @engineertdog
There's a small bug in your values.yaml. The replication.applicationName parameter should use underscore instead of hyphen:
    synchronousCommit: "on"
    numSynchronousReplicas: 1
-   applicationName: app-db
+   applicationName: app_db
  metrics:

Using the right values, I was able to run PostgreSQL without issues:
$ helm repo update
Hang tight while we grab the latest from your chart repositories...
...Skip local chart repository
...Successfully got an update from the "bitnami" chart repository
...Successfully got an update from the "stable" chart repository
Update Complete.
$ helm install stable/postgresql --name my-release -f values.yaml
...
$ kubectl logs my-release-postgresql-master-0 my-release-postgresql
...
postgresql 09:01:23.45 INFO  ==> ** Starting PostgreSQL **
2019-09-06 09:01:23.466 GMT [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2019-09-06 09:01:23.466 GMT [1] LOG:  listening on IPv6 address "::", port 5432
2019-09-06 09:01:23.469 GMT [1] LOG:  listening on Unix socket "/tmp/.s.PGSQL.5432"
2019-09-06 09:01:23.487 GMT [212] LOG:  database system was shut down at 2019-09-06 09:01:22 GMT
2019-09-06 09:01:23.492 GMT [1] LOG:  database system is ready to accept connections
2019-09-06 09:01:28.037 GMT [230] LOG:  standby "app_db" is now a synchronous standby with priority 1
$ kubectl get pods
NAME                             READY   STATUS    RESTARTS   AGE
my-release-postgresql-master-0   2/2     Running   0          11m
my-release-postgresql-slave-0    1/1     Running   0          11m
my-release-postgresql-slave-1    1/1     Running   0          11m
my-release-postgresql-slave-2    1/1     Running   0          10m

@juan131
Ah, thank you for that information. I noticed the underscore in the values.yaml file in the chart, but I was unaware that there could not be a hyphen as it’s usually not an issue. I’ll test later when I’m home from work to verify the issue so that this can be closed.
Maybe a small note could be added to the readme and values files indicating the requirement?

Hi @engineertdog
I went a step further and I found the issue why the hyphens are not accepted. I created a PR to fix the issue in the image, find it in the link below:

https://github.com/bitnami/bitnami-docker-postgresql/pull/167

I'm able to get it up and running now.
It looks like another issue I was having was in relation to the postgresqlPassword that I was trying to set. With the randomly generated password, I had special characters that weren't allowed, not even encapsulated with quotes. This was what was throwing the /entrypoint.sh: line 15: nENk: unbound variable error.

Hi @engineertdog
That's weird. We faced issues in the past with password that weren't correctly escaped but we already fixed them.
It could be related with some other configuration parameter. Could you share the values.yaml you're using so I can reproduce it locally?

It's the same values.yaml override that I listed above, with the exception that I ended up using double quotes for the password, like "some$randomPassword!1234". I did confirm that it was the password field that was causing the issue, but I didn't troubleshoot which character was the problem, or if it was all of them. I removed all of the special characters at once and the chart worked.
I do not remember all of the special characters I had in the password, but I did have the following: !$#*


text:
[stable/jenkins] issue with openshift

hello,
on Openshift 3.X , I install it with this command
helm install --name jenkins-cpaas stable/jenkins -f values_prod.yaml
values_prod.yaml is the same file as values.yaml of the repository with the following modifications :
rbac create to false
conf autoreload=false
openshift route enable
pod not starts
container log =
Running from: /usr/share/jenkins/jenkins.war
webroot: EnvVars.masterEnvVars.get("JENKINS_HOME")
2020-07-01 11:52:42.542+0000 [id=1]	INFO	org.eclipse.jetty.util.log.Log#initialized: Logging initialized @6597ms to org.eclipse.jetty.util.log.JavaUtilLog
2020-07-01 11:52:45.848+0000 [id=1]	INFO	winstone.Logger#logInternal: Beginning extraction from war file
2020-07-01 11:52:46.446+0000 [id=1]	WARNING	o.e.j.s.handler.ContextHandler#setContextPath: Empty contextPath
2020-07-01 11:52:47.646+0000 [id=1]	INFO	org.eclipse.jetty.server.Server#doStart: jetty-9.4.27.v20200227; built: 2020-02-27T18:37:21.340Z; git: a304fd9f351f337e7c0e2a7c28878dd536149c6c; jvm 1.8.0_242-b08
2020-07-01 11:52:54.946+0000 [id=1]	INFO	o.e.j.w.StandardDescriptorProcessor#visitServlet: NO JSP Support for /, did not find org.eclipse.jetty.jsp.JettyJspServlet
2020-07-01 11:52:56.444+0000 [id=1]	INFO	o.e.j.s.s.DefaultSessionIdManager#doStart: DefaultSessionIdManager workerName=node0
2020-07-01 11:52:56.444+0000 [id=1]	INFO	o.e.j.s.s.DefaultSessionIdManager#doStart: No SessionScavenger set, using defaults
2020-07-01 11:52:56.541+0000 [id=1]	INFO	o.e.j.server.session.HouseKeeper#startScavenging: node0 Scavenging every 660000ms
2020-07-01 11:53:05.841+0000 [id=1]	INFO	hudson.WebAppMain#contextInitialized: Jenkins home directory: /var/jenkins_home found at: EnvVars.masterEnvVars.get("JENKINS_HOME")
2020-07-01 11:53:08.843+0000 [id=1]	INFO	o.e.j.s.handler.ContextHandler#doStart: Started w.@4ee203eb{Jenkins v2.235.1,/,file:///var/jenkins_home/war/,AVAILABLE}{/var/jenkins_home/war}
2020-07-01 11:53:09.945+0000 [id=1]	INFO	o.e.j.server.AbstractConnector#doStart: Started ServerConnector@4157f54e{HTTP/1.1, (http/1.1)}{0.0.0.0:8080}
2020-07-01 11:53:09.945+0000 [id=1]	INFO	org.eclipse.jetty.server.Server#doStart: Started @34001ms
2020-07-01 11:53:09.946+0000 [id=20]	INFO	winstone.Logger#logInternal: Winstone Servlet Engine running: controlPort=disabled
2020-07-01 11:53:39.455+0000 [id=32]	INFO	jenkins.InitReactorRunner$1#onAttained: Started initialization
2020-07-01 11:54:13.741+0000 [id=21]	INFO	winstone.Logger#logInternal: JVM is terminating. Shutting down Jetty
Openshift monitoring log =

1:53:23 PM
jenkins-custom-7976fdbf85-69mqd
Pod
Warning
Unhealthy
Readiness  probe failed: Get http://172.23.5.159:8080/login: net/http: request  canceled (Client.Timeout exceeded while awaiting headers)         12 times in the last 9 minutes

1:47:46 PM
jenkins-custom-7976fdbf85-69mqd
Pod
Normal
Killing
Killing container with id cri-o://jenkins:Container failed liveness probe.. Container will be killed and recreated.

1:47:33 PM
jenkins-custom-7976fdbf85-69mqd
Pod
Warning
Unhealthy
Liveness probe failed: HTTP probe failed with statuscode: 503

1:47:31 PM
jenkins-custom-7976fdbf85-69mqd
Pod
Warning
Unhealthy
Readiness probe failed: HTTP probe failed with statuscode: 503

1:47:28 PM
jenkins-custom-7976fdbf85-69mqd
Pod
Warning
Unhealthy
Liveness  probe failed: Get http://172.23.5.159:8080/login: net/http: request  canceled (Client.Timeout exceeded while awaiting headers)         3 times in the last 9 minutes

1:46:48 PM
jenkins-custom-7976fdbf85-69mqd
Pod
Warning
Unhealthy
Readiness probe failed: Get http://172.23.5.159:8080/login: dial tcp 172.23.5.159:8080: getsockopt: connection refused         2 times in the last 9 minutes

1:45:29 PM
jenkins-custom-7976fdbf85-69mqd
Pod
Normal
Started
Started container

Any idea ??
regards
bruno

I ran the Jenkins Helm chart with the same configuration as you specified above and it successfully created a pod with no errors on my OCP 3.11 cluster
rbac.enable=false
configautoreload=false
route.enable=true

I think the issue in your case is related to the CPU on the host the you are running the Jenkins pod, as the default CPU limit for the Jenkins pod is 2 cores and if the pod startup utilize the CPU and reached the maximum that your host can support could cause the CPU contention.
This result a slow pod startup which cause the readiness and liveness to fail and after certain number of probe thresholds the pod restarts.

authors: shakenfr venkatalolla


text:
Update to latest image, add OWNERS as well as add new owner to team, …

…fix README, update Helm Charts root readme with incorrect text.

What this PR does / why we need it:

Adds an OWNERS file to relevant owners who can review and approve PRs for this chart.
Adds new owner (cc @bendrucker ) who is authorized to help own this chart
Updates imageTag to latest version (2.1.0)
Updates to Chart README wording
Fix minor typo in main helm charts repo README
Add hook delete policy to prevent potential chart upgrade issues

Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

N/A

Special notes for your reviewer:
Please let me know next steps on the OWNERS file set up so we have permission to maintain the chart going forward and if you need anything else. (cc @darend @flah00 FYI)
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md

/assign @unguiculus

/ok-to-test

/lgtm

authors: frankreno unguiculus


text:
[stable/prometheus-mysql-exporter] fixed install command in readme

What this PR does / why we need it:

fixed install command in readme

Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

https://github.com/helm/charts/commit/20c0827d11841cdc1db518567e209511b0b6a87a#commitcomment-32427111

Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md

/assign @prydonius

/retest

/assign @davidkarlsen

/assign @foxish

/assign @unguiculus

/assign @cpanato

anyone?

/ok-to-test

/lgtm

authors: davidkarlsen monotek


text:
[stable/mariadb] Standardize 'fullname' and 'name' macros

Signed-off-by: juan131 juan@bitnami.com
What this PR does / why we need it:
This PR standardize 'fullname' and 'name' macros.
Checklist

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/chart])

/ok-to-test
/lgtm


text:
[stable/ghost] Revert pull request #15447

This reverts commit 2ef3c959dd36066555cdbc98de5a24f66f571859.
Changes in the previous commit are breaking changes when used in some configurations, for example helm upgrade doesn't work using a static IP in the loadBalancer.
According to semver:

Given a version number MAJOR.MINOR.PATCH, increment the:

MAJOR version when you make incompatible API changes,
MINOR version when you add functionality in a backward-compatible manner, and
PATCH version when you make backward-compatible bug fixes.
Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.

Those changes are not backward-compatible, so we should have increased the MAJOR version instead of the PATCH one. In this PR, we are reverting the breaking changes so the current MAJOR version will continue working without issues.
In the same way, we will create a new PR adding again those changes but bumping the chart version in a MAJOR
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[X] DCO signed
[X] Chart Version bumped
[X] Variables are documented in the README.md
[X] Title of the PR starts with chart name (e.g. [stable/chart])

/lgtm

authors: carrodher javsalgar


text:
[stable/redis-ha] Install procps in sysctlImage command example

Is this a new chart

NOTE: We're experiencing a high volume of PRs to this repo and reviews will be delayed. Please host your own chart repository and submit your repository to the Helm Hub instead of this repo to make them discoverable to the community. Here is how to submit new chart repositories to the Helm Hub.

No
What this PR does / why we need it:
Install procps in the sysctlImage example command; it fails without it with:
sysctl: command not found

Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #

Special notes for your reviewer:
@ssalaues @dandydeveloper
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[ ] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/chart])

@hendrikmaus Can you provide a little more context on this problem? It's not something I've experienced and I'm worried we're solving the wrong thing here with this PR.
What's the error you get?
What are the steps to reproduce?
Is there an issue for this?

I will try to reproduce your issue @hendrikmaus I have used that specific functionality of the chart in the past with little to no issues but perhaps something has changed.

@hendrikmaus
Please bump chart to the latest version. Thank you.

Sorry I was out of order for a little while.
The error message was included when I opened the PR, see above. Without installing procps, the container will fail as sysctl is not available.
The only step to reproduce the issue, is to use the "sysctlImage" example snippet from the Chart's readme file.
I will bump the version, review changes made and re-test my issue.

@ssalaues Did you get a chance to try reproducing this?

Here is a quick way to reproduce it.
Tested on Ubuntu 18.04 LTS (Docker 18.09.5) and Mac OS 10.14 (Docker 19.03.2)
$ docker run --rm bitnami/minideb /bin/sh -c "install_packages systemd; sysctl --version"
(...)
/bin/sh: 1: sysctl: not found

Where this produces the expected:
$ docker run --rm bitnami/minideb /bin/sh -c "install_packages systemd procps; sysctl --version"
(...)
sysctl from procps-ng 3.3.15

/ok-to-test

/lgtm

/retest

/retest

I'm not sure why it keeps failing the tests. It keeps saying  error: timed out waiting for the condition especially since this is simply a README.md change. @davidkarlsen Any ideas on why this might be happening?

@ssalaues This is probably because some of the pods aren't deploying and are looping/erroring.
@hendrikmaus Can you make sure that this doesn't cause the initContainer to bootloop with the latest merged changes?
Maybe we let something slip through in another PR?

@DandyDeveloper I double checked with a fresh deployment of the current state: no issues - it was ready after 57s with 2 haproxy pods and 3 redis pods using the sysctlImage. By the way, the sysctlImage is not active by default and this PR still is just a README change.
I suspect another reason, as a non-fresh deployment took about 6 minutes to be ready due to timeouts in finding the current master and failover. But this would only happen if the test environment would already have the redis-ha statefulset running.
I observed that the redis followers will restart quickly as the leader is still untouched. When the leader pod is restarted, however, the config-init container needs to run into a timeout before a failover is triggered and a new leader elected.
config-init container log in the leader pod
Initializing config..
Attempting to find master

It waits a couple of minutes until it runs into a timeout and triggers a failover in order to re-elect a master; the log is then concluded by:
Could not connect to Redis at 10.105.136.64:6379: Operation timed out
Can't ping master, attempting to force failover
Updating sentinel config with master 10.102.231.33
Updating redis config
Ready...

Where 10.105.136.64:6379 was the announce service IP of itself, the leader. And 10.102.231.33 is the announce service of another redis pod which was elected to be the new leader after the failover.
Indeed a nasty thing in production, since this would mean redis would not accept any WRITE operations until a new master had been re-elected.

/retest

authors: DandyDeveloper davidkarlsen hendrikmaus ssalaues zanhsieh


text:
[stable/phpbb] Update broken link to NGINX Ingress Annotations docs

Signed-off-by: juan131 juan@bitnami.com
Description of the change
The NGINX Ingress Controller annotations documentation was moved from:

https://github.com/kubernetes/ingress-nginx/blob/master/docs/annotations.md

to:

https://github.com/kubernetes/ingress-nginx/blob/master/docs/user-guide/nginx-configuration/annotations.md

This PR address this change
Checklist

[X] Chart version bumped in Chart.yaml according to semver.
[X] Variables are documented in the README.md
[X] Title of the PR starts with chart name (e.g. [bitnami/chart])

/ok-to-test
/lgtm


text:
[stable/prometheus-node-exporter] - add podAnnotations value

Signed-off-by: Alex Williams alex.williams@skyscanner.net
Is this a new chart
NO
What this PR does / why we need it:
Add podAnnotations so node-exporter can have annotations added, for example sidecar.istio.io/inject: false
Which issue this PR fixes
No open issue when searching.
Special notes for your reviewer:
I have also added a default podLabels to the values.yaml. As that acts as a sort of documentation too.
Checklist

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/chart])

FYI @gianrubio
There are other PRs that might clash on chart version. I found:

https://github.com/helm/charts/pull/17359
https://github.com/helm/charts/pull/17534
https://github.com/helm/charts/pull/17712

/ok-to-test

/retest

Bump @gianrubio . Could you please take a look at this one?

Hey @gianrubio
I have rebased and fixed merge conflicts. However, the e2e tests are still failing and I'm a bit unsure why this is the case. Are these tests always failing or is it something that I have introduced?
Happy to fix if you can point me in the right direction.
Thanks

/retest

/lgtm

authors: Smirl davidkarlsen zanhsieh


text:
[stable/tomcat] fixed ingress and added labels on deployment, service and pods

Is this a new chart

NOTE: We're experiencing a high volume of PRs to this repo and reviews will be delayed. Please host your own chart repository and submit your repository to the Helm Hub instead of this repo to make them discoverable to the community. Here is how to submit new chart repositories to the Helm Hub.

What this PR does / why we need it:
Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #

Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[X] Chart Version bumped
[X] Variables are documented in the README.md
[X] Title of the PR starts with chart name (e.g. [stable/mychartname])

/assign @jlegrone

/ok-to-test

authors: glarfs zanhsieh


text:
[stable/mongodb-replicaset] ssl/tls flags, helm helpers

What this PR does / why we need it:
This PR makes ssl/tls flags a bit drier, at the same time supporting either ssl and tls so we can support mongo version pre/post 4.2 and its feature deprecation.
By centralizing every char's tls configuration in those helpers which generate:

plaintext parameters lists
yaml formatted parameters arrays
uri-encoded parameters list

it should be simpler and less error prone to keep them in sync, and adding other interesting features that get introduced w/ new versions.
Thank you, regards
Checklist

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

cc @unguiculus @steven-sheehy

This chart has been deprecated and is no longer maintained. It is recommended to use the Bitnami maintained MongoDB chart which has a similar feature set, including high availability. Thanks!

This chart has been deprecated and is. No longer maintained. See #23747 and #21103.

authors: aogier steven-sheehy unguiculus


text:
v2.11 was built with go 1.10 instead of 1.11

https://circleci.com/gh/helm/helm/6454 - see the env output or the configuration tab
https://github.com/helm/helm/pull/4637 has that change - Did it arrive too late in the release window?
Was hoping to have 1.11 and Sprig 2.16 (landed later) together. 1.11 added a nice thing for templates (https://golang.org/doc/go1.11 - Modifying template variables via assignments is now permitted via the = token:)

Yes, sadly that missed the window. It'll be in 2.12 though!

To explain why go 1.11 wasn't merged in and why sprig was:
Both of these PRs were merged after we cut the first release candidate. When evaluating which PRs should be squeezed in and re-cut another RC, we found that sprig 2.16 contained a few substantial bug fixes, so we considered it for merging into the release branch. However, compiling Helm against a newer version of Go has bitten us in the past, and since none of us felt comfortable with Go 1.11 to say whether or not it'd introduce breaking changes, we decided to hold off until the next release.
Hope that helps!

Fair explanation but seems like a big miss given the template change that
benefits charts. Can we expect the same time frame between 2.11 and 2.12
(to get this bump) as 2.10 to 2.11 (~5 weeks)
On Tue, Sep 25, 2018 at 19:35 Matthew Fisher notifications@github.com
wrote:

To explain why go 1.11 wasn't merged in and why sprig was:
Both of these PRs were merged after we cut the first release candidate.
When evaluating which PRs should be squeezed in and re-cut another RC, we
found that sprig 2.16 contained a few substantial bug fixes, so we
considered it for merging into the release branch. However, compiling Helm
against a newer version of Go has bitten us in the past, and since none of
us felt comfortable with Go 1.11 to say whether or not it'd introduce
breaking changes, we decided to hold off until the next release.
Hope that helps!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/helm/helm/issues/4696#issuecomment-424564611, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAETgh62YHT9Tjib2ku7TrTyk9ZrHrL-ks5ueufYgaJpZM4W5svA
.

probably not. The timeframe for 2.11 was accelerated due to the release of Kubernetes 1.11 support coming out the door shortly after 2.10 was released. #4420

authors: bacongobbler helgi

repo: helm/helm


text:
fix path issue in windows

Signed-off-by: yxxhero aiopsclub@163.com
fix path issue in windows
fix: https://github.com/helmfile/helmfile/issues/382

@mumoshu

repo: helmfile/helmfile


text:
Bug: Performance issues since v14.5

Description of the bug
Since we upgraded ng-mocks from version 14.4.0 in our project, our Unit Tests are 3x slower than before. We narrowed the performance degradation down to either v14.5.0 or v14.5.1 (we couldn't get 14.5.0 working without errors).
This is quite an issue for us, since our Unit Test Suite in said project contains ~7k Tests which used to run in 20-60 seconds depending on the machine. These now take 1-3 minutes.
An example of the bug
I'm unsure on how I can demonstrate this as I'm not allowed to share the project as-is. I'm pretty sure though you can take any project, up-/downgrade ng-mocks between v14.4.0 and v14.5.1 and notice a severe performance impact.
Link:
Expected vs actual behavior
No performance degradation compared to v14.4.0.

Hi @pascal-puetz,
thank you for the report.
Could you check how it works with the latest version?
If it's still bad.
Could you record CPU profiler during the test execution and share it with me?

Closing due to silence. Feel free to reopen it with the requested info or steps how to reproduce.
Thank you in advance.

authors: pascal-puetz satanTime

repo: help-me-mom/ng-mocks


text:
Feature Request: Make client hostname available in adguard_top_clients and adguard_processing_time_milliseconds_* metrics

Hi! Thanks for the effort put in this great piece of software.
It would be really nice to have client hostnames available in the adguard_top_clients and adguard_processing_time_milliseconds_* metrics , like on the web dashboard.

Hi team,
This feature could be easily implemented by resolving client's info within the /control/clients/find endpoint (https://github.com/AdguardTeam/AdGuardHome/blob/master/openapi/openapi.yaml#L935-L959)
Request example:
https://198.51.100.1/control/clients/find?ip0=198.51.100.42

Response example:
[
  {
    "198.51.100.42": {
      "disallowed": false,
      "disallowed_rule": "198.51.100.0/24",
      "whois_info": {
      },
      "safe_search": null,
      "blocked_services_schedule": null,
      "name": "Client-Host-Name",
      "blocked_services": null,
      "ids": [
        "198.51.100.42"
      ],
      "tags": null,
      "upstreams": null,
      "filtering_enabled": false,
      "parental_enabled": false,
      "safebrowsing_enabled": false,
      "safesearch_enabled": false,
      "use_global_blocked_services": false,
      "use_global_settings": false,
      "ignore_querylog": null,
      "ignore_statistics": null,
      "upstreams_cache_size": 0,
      "upstreams_cache_enabled": null
    }
  }
]

The name field value needs to be extracted and added as name label to the appropriate adguard_top_clients record, i.e.:
adguard_top_clients{client="198.51.100.42",name="Client-Host-Name",server="https://198.51.100.1"} 279

authors: freefd kondas


text:
🛑 hentaiOS Mail is down

In 20784c9, hentaiOS Mail (https://mail.hentaios.com) was down:

HTTP code: 502
Response time: 645 ms

Resolved: hentaiOS Mail is back up in 5131eb2 after 5 minutes.


text:
Confusing error when querying logs for upper-cased backup

If I query for logs from a backup with an upper case name, I get a confusing error:
$ ark backup logs Invalid
An error occurred: DownloadRequest.ark.heptio.com "Invalid-20180515125158" is invalid: metadata.name: Invalid value: "Invalid-20180515125158": a DNS-1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*')

When the name is lower-case, the error is accurate. (but it's still odd that it's printing raw XML)
$ ark backup logs invalid
An error occurred: request failed: <?xml version='1.0' encoding='UTF-8'?><Error>NoSuchKey<Message>The specified key does not exist.</Message>No such object: ark-web/invalid/invalid-logs.gz</Error>

@robbyt thanks for the report. For the 1st error, this is because we're actually creating a new object and sending it to the Kubernetes apiserver to accomplish log streaming. We can add some validation up-front.
For the 2nd error, we can add some validation to make sure the log file exists.

I opened #549 as a meta-issue for reviewing all Ark error messages.  That said:

Ark should validate objects before sending to the API server
Improve validation in the logs command to ensure the backup exists (similar to #389 )

@ncdc I'm curious if the validation would be covered by #155 or if there's separate work to be done.
I propose that this issue, 492, focus on improving the validation in the logs command. (similar to #389), and we split out anything else.

I'm not sure if #155 will help here when we create the DeleteBackupRequest. My gut says it probably will, but we'll have to try it.
+1 to using this issue for logs validation.

authors: ncdc robbyt rosskukulinski

repo: heptio/ark


text:
Explicit NodePort values defined in Helm charts are deleted during restoration

What steps did you take and what happened:

Deploy a Helm chart containing a K8s Service with explicitly defined NodePort port values.
Create a Velero backup of the service.
Delete the service.
Restore the backup of the service.
Note that the explicit NodePort port values are removed, and new, random port numbers are assigned.

What did you expect to happen:
Explicitly defined NodePort values should be restored from the backup.
Anything else you would like to add:
This appears to be caused by the deleteNodePorts function (see below). As written it looks for the presence of the kubectl-specific annotation kubectl.kubernetes.io/last-applied-configuration which it uses to restore the port values. Only kubectl creates this annotation so the port restoration fails when using other deployment methods such as Helm:
https://github.com/heptio/velero/blob/a111eed2af8c0bb37ecd6d682b3faad116fbad2f/pkg/restore/service_action.go#L70-L100
A potential solution would be to support reading a custom annotation on K8s services that would direct Velero to preserve and not delete any custom port values.
Possible workarounds:

Use helm template and pipe through kubectl apply. This won't work for us as we depend on the release management features of Helm.
Create a Restore Item Action Velero plugin to force the restoration of the NodePort values. It is unclear to me if this plugin would execute at the right stage so that these values would be preserved and not just removed again in the final restore.

Environment:

Velero version (use velero version):

Client:
	Version: v1.0.0
	Git commit: 72f5cadc3a865019ab9dc043d4952c9bfd5f2ecb
Server:
	Version: v1.0.0

Kubernetes version (use kubectl version):

Client Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.4", GitCommit:"c27b913fddd1a6c480c229191a087698aa92f0b1", GitTreeState:"clean", BuildDate:"2019-02-28T13:37:52Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.13", GitCommit:"954ff68d59e9dc62fa8252ffa9023a90ff8a358c", GitTreeState:"clean", BuildDate:"2019-02-13T11:03:32Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}

@Rathgore thanks for the issue report - your analysis looks correct. The challenge is knowing whether or not the NodePort value was explicitly specified by the user, or auto-assigned by the system. In the absence of being able to figure this out systematically for all cases, I agree that giving the user some kind of control over whether these get restored or not probably makes sense.

Thanks @skriss. I am tempted to pursue writing a plugin as a workaround. Would a Restore Item Action plugin work in this case? Does it execute after deleteNodePorts?

Same issue here. I don't know how velero restore works but the port  looks fine in the json, so it's really weird that this is only happening with services created by helm charts.

authors: Rathgore bernardomk skriss

repo: heptio/velero


text:
Missing Binaries for 2.7.0 release

Please add binaries for the 2.7.0 release: https://github.com/heroiclabs/nakama/releases/tag/v2.7.0

This is blocked on a discussion I've raised with the xgo team. I'll see what we can achieve with that or we'll fork xgo to maintain it as part of our build/release process. https://github.com/techknowlogick/xgo/issues/37

@sNakiex My pull request for xgo was accepted and I've been able to cross-compile binaries for the 2.7.0 release:
https://github.com/heroiclabs/nakama/releases/v2.7.0

authors: novabyte sNakiex

repo: heroiclabs/nakama


text:
Release v178

https://github.com/heroku/heroku-buildpack-python/compare/v177...3e49aeb940df368155ba710d39bf1593a06518a3
Closes @W-8052520@.

$ ./etc/publish.sh
Deploy as version: v178 [y/n]? y

Tagging commit ae56342a81c28682220e3ebec5c377479dc82a85 with v178...
Total 0 (delta 0), reused 0 (delta 0), pack-reused 0
To https://github.com/heroku/heroku-buildpack-python
 * [new tag]         v178 -> v178
Two-factor code: ********************************************
Publishing buildpack heroku/python... done
Publishing buildpack was successful
Done.

$ h buildpacks:versions heroku/python | head -n4
Version  Released At               Status
───────  ────────────────────────  ─────────
178      2020-09-07T12:23:53.459Z  published
177      2020-08-18T11:59:25.353Z  published

https://devcenter.heroku.com/changelog-items/1880 (no update needed to https://devcenter.heroku.com/articles/python-support#supported-runtimes since 3.5 not in our official support list any more)

repo: heroku/heroku-buildpack-python


text:
Add PyPy 5.7.0

This release updates the pypy2 stdlib to 2.7.13 and the pypy3 stdlib to 3.5.3
https://morepypy.blogspot.com/2017/03/pypy27-and-pypy35-v57-two-in-one-release.html

You might as well just add Python 3.6.1 based off of the 3.6.0 runtime.  It is a busy week for Python releases!

@kennethreitz What about the updated version of pypy3-5.7.0 from this PR? The commits that were just pushed only added pypy2-5.7.0.

Anything further on this?
Any reason not to merge in pypy3 5.7? (in addition to the pypy2 5.7 as has already been)

authors: cclauss joshfriend kfwls


text:
🛑 Auth-Bridge - Test 1 is down

In c01936d, Auth-Bridge - Test 1 ($AUTH_BRIDGE_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Auth-Bridge - Test 1 is back up in 55b7b50.

repo: herrphon/upptime


text:
🛑 Auth-Bridge - Test 1 is down

In 89b5cad, Auth-Bridge - Test 1 ($AUTH_BRIDGE_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Auth-Bridge - Test 1 is back up in 571d385.


text:
🛑 Auth-Bridge - Test 1 is down

In 4bd14d8, Auth-Bridge - Test 1 ($AUTH_BRIDGE_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Auth-Bridge - Test 1 is back up in 48e9046.


text:
🛑 Software Center - Test 1 is down

In 7fc159e, Software Center - Test 1 ($SOFTWARECENTER_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Software Center - Test 1 is back up in 589d732.


text:
🛑 Auth-Bridge - Test 1 is down

In d6258e4, Auth-Bridge - Test 1 ($AUTH_BRIDGE_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Auth-Bridge - Test 1 is back up in 6eda4f3.


text:
🛑 Software Center - Test 1 is down

In ade06f3, Software Center - Test 1 ($SOFTWARECENTER_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Software Center - Test 1 is back up in 575a803 after 10 minutes.


text:
🛑 Software Center - Test 1 is down

In 4c42c43, Software Center - Test 1 ($SOFTWARECENTER_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Software Center - Test 1 is back up in 1aa2e32 after 25 minutes.


text:
🛑 Auth-Bridge - Test 1 is down

In 6888a7a, Auth-Bridge - Test 1 ($AUTH_BRIDGE_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Auth-Bridge - Test 1 is back up in c65600d after 11 minutes.


text:
🛑 Software Center - Test 1 is down

In 6c3b08f, Software Center - Test 1 ($SOFTWARECENTER_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Software Center - Test 1 is back up in 9672bb9 after 21 minutes.


text:
🛑 Software Center - Test 1 is down

In 5fa1706, Software Center - Test 1 ($SOFTWARECENTER_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Software Center - Test 1 is back up in 5f8dcd0 after 10 minutes.


text:
🛑 Software Center - Test 1 is down

In da2f5ec, Software Center - Test 1 ($SOFTWARECENTER_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Software Center - Test 1 is back up in 38aaa92.


text:
🛑 Auth-Bridge - Test 1 is down

In acfb126, Auth-Bridge - Test 1 ($AUTH_BRIDGE_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Auth-Bridge - Test 1 is back up in 307dbb7 after 52 minutes.


text:
🛑 Software Center - Test 1 is down

In 79f3625, Software Center - Test 1 ($SOFTWARECENTER_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Software Center - Test 1 is back up in 0e68dc8.


text:
🛑 Software Center - Test 1 is down

In c016888, Software Center - Test 1 ($SOFTWARECENTER_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Software Center - Test 1 is back up in a860e69 after 10 minutes.


text:
🛑 Software Center - Test 1 is down

In c3b8727, Software Center - Test 1 ($SOFTWARECENTER_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Software Center - Test 1 is back up in 7a5d6bb after 21 minutes.


text:
🛑 Auth-Bridge - Test 1 is down

In 9bfd6d5, Auth-Bridge - Test 1 ($AUTH_BRIDGE_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Auth-Bridge - Test 1 is back up in a4b9756.


text:
🛑 Auth-Bridge - Test 1 is down

In e7240c4, Auth-Bridge - Test 1 ($AUTH_BRIDGE_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Auth-Bridge - Test 1 is back up in 4805582.


text:
🛑 Auth-Bridge - Test 1 is down

In 80d9308, Auth-Bridge - Test 1 ($AUTH_BRIDGE_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Auth-Bridge - Test 1 is back up in 11fc732.


text:
🛑 Software Center - Test 1 is down

In 524cf20, Software Center - Test 1 ($SOFTWARECENTER_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Software Center - Test 1 is back up in 606cfbe.


text:
Bring your own slog handler

Is your feature request related to a problem? Please describe.
Feature request.
The slog implementation defaults to the JSON handler. Slog can be adapted to use pretty much every format/opinion out there and it should therefore be flexible.
Describe the solution you'd like
Expose Logger.L to override *slog.Logger directly or pass a functional option to inject a custom slog.Handler.
Describe alternatives you've considered
Implement the entire hlog.FullLogger interface.
Additional context
N/A

slog does not provide a way to modify the output. If modification is allowed, then setoutput will have problems

I see that now. Slog itself doesn't allow you to update the io.Writer so this feat will be impossible (atleast with slog). Thanks.

authors: kamikazechaser rogerogers

repo: hertz-contrib/logger


text:
add react and draftjs

WIP

add react and draftjs
add basic editor component
add tag decorator

💪🏼

repo: heruka-urgyen/architext


text:
clang-cl support

Hello,
during a recent compilation of xbyak with clang-cl I found the following problem:
error LNK2019: reference to exernal symbol __xgetbv unresolved in function "public: __cdecl Xbyak::util::Cpu::Cpu(void)" (??0Cpu@util@Xbyak@@QEAA@XZ)
clang-cl can be recognized by the programmer because it defines both _MSC_VER and __clang__, therefore a possible fix to this issue seems to be:
--- a/xbyak/xbyak_util.h
+++ b/xbyak/xbyak_util.h
@@ -49,7 +49,9 @@
 #endif

 #ifdef _MSC_VER
-extern "C" unsigned __int64 __xgetbv(int);
+       #ifndef __clang__
+               extern "C" unsigned __int64 __xgetbv(int);
+       #endif
 #endif

 namespace Xbyak { namespace util {
@@ -118,7 +120,11 @@ public:
        static inline uint64 getXfeature()
        {
 #ifdef _MSC_VER
+       #ifndef __clang__
                return __xgetbv(0);
+       #else
+               return _xgetbv(0);
+       #endif
 #else
                unsigned int eax, edx;
                // xgetvb is not support on gcc 4.2

This compiles without problems, not sure if this causes other problems though.
Another option might be checking for (_MSC_VER  &&   !__clang__) instead of only _MSC_VER.

Thank you for your feedback.
I tried your code, but it caused link error.
unresolved symbol ; unsigned __int64 __cdecl _xgetbv(unsigned int)" (?_xgetbv@@YA_KI@Z)

I used Visual Studio Enterprise 2015 + Clang with Microsoft CodeGen 14.0.25115.
Could you tell me the version you used?

I am using "clang llvm 4.0.0 (r284979)".
To make I use:
 cmake .. -TLLVM-vs2014 -G"Visual Studio 14 2015 Win64"
Visual Studio Community 2015 v14.0.25123.00 Update 2 + clang-cl 4.0.0
I think you might be using clang-c2 (which I just found out existed) https://blogs.msdn.microsoft.com/vcblog/2015/12/04/clang-with-microsoft-codegen-in-vs-2015-update-1/.
This problems needs a bit more debugging if it doesn't work on clang-c2.
Anyway adding also "defined(__llvm__)" should make sure that you are explicitely targeting "clang-cl" and nothing else.

Thank you for your advice. I'll get and try it later.

I renamed __xgetbv() to _xgetbv() for clang-cl(you used).
https://github.com/herumi/xbyak/commit/d50d40878452121b3b10b0c5595f5342f5b0f02d
The current clang-c2(I used) does not support inline assembler or intrinsic function such as xgetbv and cpuid, then I gave up to support the version.

This seems to be working with both MSVC and Clang-cl.
Thank you 👍

authors: freiro herumi

repo: herumi/xbyak


text:
Date picker updated

Since a lot of changes had been made to frontend repo I ended up creating updated branch.
Fixes from previous PR.

removed default imports
replaced moment with static method from TimeService class and imported type for moment
added dateFormat prop for useDatepicker component
fixed scss nesting

I refactored some code and fixed the css class issues. It's more than likely that something is broken though. Let's fix it when we notice something broken.

authors: EVCareeria thejhh


text:
API link broken

Are the docs for warehouse live somewhere? Is it still in use?
Thank you

Hi,
You have link at the top of the landing github page:
JSON database https://hexo.io/warehouse/

I put in this PR to fix the links. There's a few links in it for docs and examples https://github.com/hexojs/warehouse/pull/12

authors: connor11528 hpavlino tcrowe

repo: hexojs/warehouse


text:
Instantiate services with config

First off, lovely package, thank you for making this.
Description
It would be nice to locally configure the OpenAPIConfig of a given API call when making it.
Problem it Solves
In some cases, when writing more complex applications,
it is important for me to be able to change the configuration of a given specific call.
Proposed Solution
I would like to be able to pass an OpenAPIConfig to any request, optionally,
defaulting to the global configuration for any property not specified.
Alternatives Considered
I can alter the global config right when I need to, but this is messy and might lead to complications.
It would also be an idea to be able to instantiate a Service or all Services with a given Config, so that they can be used pre-configured and distributed non-globally, e.g. with a React Context.
Additional Context
It is possible that a generation option for this exists and I just didnt see it anywhere.

Hi @clragon, thank you for opening an issue! Do interceptors not achieve what you're after? If not, can you share your configuration, and perhaps go more into specifics of what are you trying to achieve?

Hi @mrlubos, thanks for your reply.
In my specific case, I am writing an End To End test against my backend.
Because of that, I have to act as multiple users at once, so credentials are swapped out often.
Interceptors are great, but they are not the kind of scope I am looking for. An interceptor cannot identify that I wish for e.g. this specific request right now the be authenticated with different credentials than normally.
I am looking more for something like this:
// OpenAPIConfig could be optional last argument?
MyService.someRequest({
  TOKEN: someSpecificToken,
});

or maybe also (this is more involved though, since currently services are static?)
// OpenAPIConfig could be optional last argument?
MyService({
}).someRequest({

});

Yep. I like the direction of the latter approach, but will need to give it more thought before implementing. Is this a high priority issue for you? What were you doing prior to using openapi-ts if you're migrating?

I have been looking for a simple openapi generator for a while, so finding this package, I think of myself very lucky!
The large openapi generator generates a whole "sub-package" which is too much for what I usually want to achieve, and I like to avoid monorepos.
I have also previously tried more opinionated packages like rapini and also @openapi-codegen/cli, which both have different approaches to passing per-request configurations - the former, as last argument, which is extremely tedious with many paramaters, the later, as one big config object that is quite nested.
Those packages also provide react query hooks, which I fancy, but in my current project, they are not needed.
Overall, I wouldnt consider this immensly high priority, but it would make my workflow quite a bit nicer, for sure.

Those are some kind words @clragon, thank you! I'm not seeing in your list of alternatives openapi-typescript which is the most popular one. What's your opinion on it?
Separately, we have something coming up for TanStack Query later this year 👀

openapi-typescript does seem very interesting, I havent seen an approach like this before.
personally, I think if I am using a generator, which is already somewhat of a committment, I'll take the full treatment of also generating axios, etc, because it makes my life easier.
so, openapi-typescript seems a bit bare bones for my taste. I could see it being useful at my workplace though, where less code generation is preferred because we commonly have specific requirements for how we want to structure our code.

Do you mind chatting more about it? We strive to be a superset of openapi-typescript in terms of features. When you say less generated code is preferred, what exactly are you referring to? Are you aware that you can choose which parts of the generated output you need? For example, skip creating services, schemas, etc.?

right! code generation for me is a bit of a black and white situation.
When I can, I prefer not to, since it introduces extra utilities which need to be maintained and understood by the project members.
But when code generation has large benefits, I prefer it to be extensive so that I can get maximum usage out of it.
Because of that, personally I prefer code generation that gives me more rather than less.

Got it @clragon. We want Hey API to be your tool of choice for working with API data, no matter the project size. If you work with APIs, you work with Hey API. The idea is you could add or remove features as necessary as the scope changes. If you think of anything that could achieve this objective in your eyes, please let me know. We're just getting started with this thing!

@clragon i updates the issue title, let me know if that doesn't fully capture the solution you're after

Also really interested in this. Let me know if I can help.

@julianheckmann what kind of values are you looking to pass to the instance? And are we talking about per service config or global changes?

@mrlubos Thanks for the question. I'm talking about per service config. I need different headers and auth(token) based on whether I'm on the server or the client. Ideally I would simply create two services for the different needs.

Since services consume clients, sounds like being able to instantiate a new client per each service would resolve this. We will work on this, just need to come up with a clean way to achieve it

We also have the need to pass custom headers to forward Auth to another service. What I didn't like about instances, is the loosing of the static services. Would be nice to have a mix of both.

@KiwiKilian How do you solve this today?

We have this requirement in 1 out of 20 requests. So for now we stayed with the static services and made custom fetch calls with as type from the gernerated types.

@KiwiKilian do you mean 1 out of 20 services? Either way, we will want to support this as part of the upcoming client packages so would love your feedback when they're ready

Only a few services from one OpenAPI spec and only a few calls to some of their endpoints. Would be nice to have the static services created without any additional options and the opportunity of instances in parallel.

That sounds pretty clear @KiwiKilian but I'm going to ask, why aren't interceptors enough for you?

Because I would need the initial request made to our remix app, which makes calls to another API. I described this also in this comment https://github.com/hey-api/openapi-ts/issues/342#issuecomment-2049146663

This will be addressed as part of the clients release. Note that services layer will be exported as individual functions to enable tree shaking, so the concept of instantiating a service won't be relevant anymore

This will be addressed as part of the clients release. Note that services layer will be exported as individual functions to enable tree shaking, so the concept of instantiating a service won't be relevant anymore

Will we be able to pass a client instance to service functions, or have control over the client instance used internally? I'd love to be able to take advantage of connection pooling in axios by passing an HttpsAgent to the client. I don't believe that's possible currently.

@ecline123 Yes

Hey all, I think the new Fetch API client resolves this. You can play around with it in the demo. Would love to hear your thoughts, feel free to re-open if something is still missing!

authors: KiwiKilian clragon ecline123 julianheckmann mrlubos

repo: hey-api/openapi-ts