text:
add framework for damage types

update branch

def didn't like not merge the other commits in this pull or anything...

repo: SpiritXIV/the-shit-of-crypt


text:
[API 8+] Add (back) timings support

Is this request specific to one implementation of Sponge?
No
Sponge Version
8.0.0
What are you requesting?
As we all know, timings has been slated for removal for API 8, after much internal and external discussion. Two days ago, it was removed (https://github.com/SpongePowered/Sponge/commit/235f3dd293e401834a5d01f862ed2ccb43239650), completing one more milestone towards API 8's completion.
While I understand why timings was a lot to maintain when it comes to continuous support, timings also provided additional context on performance no other system provides, from WarmRoast to Spark. To diagnose performance in feature parity to timings, you would need to track over X minutes a lot more than simply the main thread. Timings' strength stemmed from the contextual timeline display of fluctuating variables such as playercount, chunks, entity count, TPS, etc.
Therefore, I am suggesting the re-adding of timings to the Sponge API platform, either included by default within it, or as an external mixin plugin for diagnosing purposes. After all, platforms like Bukkit have continuously supported timings even with resources like WarmRoast or Spark around. In fact, even Spark itself is meant to be used within the context of other statistical data... including timings (https://github.com/lucko/spark/issues/5#issuecomment-405154388).

I (as owner of multiple servers) am also in for re-adding of timings to sponge 8. Its helpfull and i would like to see this feature in new versions of sponge.

Please re-add timings. It's an extremely important resource for server owners and admins.

Thanks for adding this Ras, timings one of the essential resources for understanding performance-related issues. The removal of timings in API 8 would be a huge loss to all server owners/admins

Since the early days of timings 2013, or at least I remember using it since then, timings were an easy and quick command to check a servers rough health status. Timings got better and better and with v2 it actually gave admins a very good overview how the server was doing in the last 30 minutes. Entity/Chunk/tps over etc. time.
Imagine having 100 people online and you are offering a special event for players or are testing a new plugin that could degrade performance, the first time on live servers. You can test plugin performance with a few test players, but there wil always be the first time with many players.
So what tool do you wanna use to check if performance is great all the time during it? Yes, you can use /tps. But what if tps actually reported bad in the last 5 minutes?
You cannot see why.
So you may say "use Spark/warmroast". Yes, you could Spark to get a snapshot, but there is that entry barrier. You need spark installed, plugin commands are a bit more complex than timings ones and its not that straight forward to read.
Back to my example. Without timings there is no way to check for admins if there was something going nuts during the last 30 minutes during that event. You would only notice lagspikes or you could spam /tps all the time. But you wont see the reason for lag.
In case staff members are noticing lag spikes they need to call an admin that take Spark timings RIGHT now to identify the issue.
Far more simple if you get some time when using timings because its always recorded.
You also might be saying that timings are inaccurate (Sponge impl). Yes thats true. BUT: There is no entry barrier. As a newbie owner you can simple run /timings, post the link and other can point you in the right direction where the lag is coming come.
And yes, in some cases you need a Spark or warmroast report to exactly define where the was coming from.
In short, timings give you a perfect, snappy overview, be it tps/events/configs/playercount to tps/chunkcount/entitycount relation and MUCH more, for a specific moment and, thats the most important, it gives you that view retrospectively over the last 30 minutes.
Also the output is far more easier to read. I am saying that as someone that used warmroast, timings and other profilers since day one back in 2013 and is comfortable with reading and understanding them.
So please, bring it back, this tool is heavily needed

You also might be saying that timings are inaccurate (Sponge impl). Yes thats true. BUT: There is no entry barrier. As a newbie owner you can simple run /timings, post the link and other can point you in the right direction where the lag is coming come.

I think there is a lot to say about the early implementations of timings, where it not only was accurate, but also was heavily favoured by mod and plugin devs alike. Having an in-house profiling solution the standard for good reason - a well implemented timings provides the perfect balance between performance history and lightweight accessibility. Once can't say the same of Spark, or WarmRoast.

Timings are an essential tool to many servers, it helped me identify key problems with my server with ease and was quick and reliable. Do bring back timings cause otherwise that's a bad move on Sponge's part 👎

The removal of timings creates an unnecessary entry barrier for those looking to figure out lag issues within their server.
Many servers do not have the capability or knowledge in order to read things which are as complex as Spark reports or the like, but the vast majority of owners can quite easily deduce the cause of their lag from a well-written timings report.

We're not re-adding timings in the way they were added. A comment above sums this up well:

You also might be saying that timings are inaccurate (Sponge impl). Yes thats true.

Bad data is worse than no data. If the timings are inaccurate, then they should not be there - and that was a factor in our decisions.
We did think about the wider implications of the removal of timings when we made this decision.

Accuracy of the data - it wasn't that accurate.
Maintenance cost on our end. We were trying to support an old system (Paper, which also uses the timing system, pretty much has an entirely different implementation - the updates were never ported to Sponge), and the implementation was old and not fit for purpose. We have our hands full sorting out Forge support, which is an entirely different beast in 1.16, worrying about timings is the least of our concerns.
The timings views actually caused some confusion. The graphs at the top might have been nice, but people constantly mis-reading the lag views caused many a mis-diagnosis. For example, Nucleus got blamed a lot for lag because it had a large tick time for /rtp, but it actually it was one tick, for perhaps twice the tick time, and not a continuous thing. We were rarely able to pinpoint a lag issue by looking at timings. Whether that was a problem in data analysis, or how we sent up the data, I don't know.
There are other plugins and methods for timings. Indeed, once we can get SF to 1.18.x, there is the /jfr command that uses inbuilt Java systems to measure stuff. Indeed, I'd be open to trying to enhance timings though that.

I know that the removal of this command was never going to be universally praised, but nor should we keep a system that is fundamentally flawed in our codebase, especially if we have many other priorities.
That said, this is open source! I know many of you here are not developers, but you likely know people who are, have a bit of time, and might be interested in taking a swing at this. I am not opposed to seeing PRs that update the timings systems to be more modern, perhaps aligned more to what Paper does. Alternatively, if someone wants to create an external mixin plugin that re-introduces the code, by all means.
I'm not against a timings system being re-introduced to the main code base, but it needs to be re-written completely.

I've been doing support on the Sponge discord for a few years now and I've seen a lot of Timings reports but I've rarely been able to extract anything other than "you have wrong GC flags" or "you should upgrade hardware". Most of the time, the reports were useless or misleading. I've been integrating Timings in my plugins, thinking this would help diagnosing performance but I ended up using Spark.
In my opinion, Spark and JFR are currently way better solutions on Sponge. Timings is an excellent idea, but the current integration with Sponge is very flawed. If someone really wants to dedicate its time to improve Timings on Sponge, feel free, but I doubt Sponge core devs have the time to.
Whatever is the best solution (Timings vs Spark vs future plugins), I don't see why Sponge should favor one over another. Timings should be an external plugin, like all other performance diagnostic tools.

Please re-add timings support, it would save a lot of people a lot of time and efficiency.

Please do not continue to comment "please re-add timings support", because that does not add anything to this thread. Read what I said, and if you havee something constructive to contribute based on that then, please do so. Simply asking to re-add timings without addressing my comments adds nothing and will do nothing, and is quite frankly rude when I've spent time outlining our position and what we feel needs doing.
I haven't closed this issue because I very much believe it's in our interest to listen and I understand why some people feel such a command is useful, but it's also very much in our interest that everyone understands our position - especially in that timings were very flawed and somewhat useless in the context of 1.16.
I reiterate - Sponge is an open source project and if any developers want to take up the challenge of re-writing Timings to be a lot more accurate and performant, you can! If you want the current implementation, we'll not be reintegrating it, but someone is free to turn it into an external mixin plugin if they so wish.

I've had a similar experience trying to diagnose issues using timings, and have gradually learned that it's better to skip the timings step entirely and get straight to the Spark report. It was a wise move to drop it from the API; bad information is much worse than no information. And it's worth stressing, Spark is a spectacular alternative and should be the recommended way to diagnose issues until things move to 1.18.

Bad data is worse than no data. If the timings are inaccurate, then they should not be there - and that was a factor in our decisions.

That statement is true for the real world or enterprise applications. The data that was generated was not always inaccurate and even if it was inaccurate,it gave you a direction, which was very important. Its nice to know where to start.

Maintenance cost on our end. We were trying to support an old system (Paper, which also uses the timing system, pretty much has an entirely different implementation - the updates were never ported to Sponge), and the implementation was old and not fit for purpose. We have our hands full sorting out Forge support, which is an entirely different beast in 1.16, worrying about timings is the least of our concerns.

Cant say that much here, but when skimming through SpongeForge/Common 1.12.2 commits, there wasnt that much timings related.

The timings views actually caused some confusion. The graphs at the top might have been nice, but people constantly mis-reading the lag views caused many a mis-diagnosis. For example, Nucleus got blamed a lot for lag because it had a large tick time for /rtp, but it actually it was one tick, for perhaps twice the tick time, and not a continuous thing. We were rarely able to pinpoint a lag issue by looking at timings. Whether that was a problem in data analysis, or how we sent up the data, I don't know.

In that example indeed it was not nucleus itself, but maybe slow chunk loading or disk, but still, admins could see where it was coming from roughly.

The timings views actually caused some confusion. The graphs at the top might have been nice, but people constantly mis-reading the lag views caused many a mis-diagnosis

Well, when reading help discords, spark view and warmroast view is a lot harder to understand. mis-diagnosis is very often also a thing with spark.

There are other plugins and methods for timings. Indeed, once we can get SF to 1.18.x, there is the /jfr command that uses inbuilt Java systems to measure stuff. Indeed, I'd be open to trying to enhance timings though that.

So far so good, but we are talking (mainly) about 1.16
Its a bit sad that developers are saying this timings thing is useless compared to maintenance cost and therefore remove it.
In the end, we, admins are using this software on small/big servers with 20 or 1000 people. When admins are saying they find it useful, this word is definitely more worth than a developer saying "its useless and delivers inaccurate data, lets remove it"
You as developer probably did not even find the chance to use that feature on a regular basis on servers with many players online where its vital to track entitycount over the time, playercount over the time. How the server was doing over the time with settings X changed etc.
That feature was also helpful to easily compare servers health over a timeframe when you have changed settings etc.
Admins do find this very useful and at least for me and even if no one will care, it renders Sponge 1.16 not viable for me.
This whole removal thing felt a bit like when a Sponge dev would remove the stop command with the reason that he uses the "X" on the powershell console all the time while developing anyway and the stop command fails from time to time with bad plugins.

That statement is true for the real world or enterprise applications.

This isn't the real world? It feels pretty real when we get people coming for support with timings that tell us nothing, or worse, look bad but actually were a one tick blip on some command. For some, gaming is part of their real world, a coping mechanism for all the bad out there, supports those with anxiety or autistic tendencies. Part of why I got into Minecraft modding was because of family friends who could use Minecraft as a way to help their children, and I could build little things that helped their children cope with life.
So don't tell me this isn't real world. For some, it really is.
Bad data has also led to our support getting requests with no context, just a timings report that says nothing. That our support's time and effort. It also wastes the time of admins who read it and try to fix things, only to find their problem wasn't a problem.

The data that was generated was not always inaccurate and even if it was inaccurate,it gave you a direction, which was very important.

Not always, as I said, it led to mis-diagnosis because of bad data. Some of that is down to the implementation doing the wrong thing.

In that example indeed it was not nucleus itself, but maybe slow chunk loading or disk, but still, admins could see where it was coming from roughly.

My point was that it wasn't though. Admins were looking at one tick taking a long time, rather than multiple ticks just lagging a little. In that particular scenario, their entire reasoning was wrong - Nucleus was top of the list but it was a half second pause, not continuous 70ms ticks.
That's more a problem with how timings were displayed, but that was my point which you missed by telling me the cause of the single tick issue, not the underlying "my server is continuously lagging" problem.

Its a bit sad that developers are saying this timings thing is useless compared to maintenance cost and therefore remove it.
In the end, we, admins are using this software on small/big servers with 20 or 1000 people. When admins are saying they find it useful, this word is definitely more worth than a developer saying "its useless and delivers inaccurate data, lets remove it"

In the end, we developers are the ones who are maintaining the software, and we made that judgement call as no-one else has been pitching in. As I said, Sponge is open source, many server admins have developers on their rosters, why not contribute back to the project and help build a better timings, at least one that is on par with Paper?

You as developer probably did not even find the chance to use that feature on a regular basis on servers with many players online where its vital to track entitycount over the time, playercount over the time. How the server was doing over the time with settings X changed etc.

Don't ever assume. Some of us run servers and do eat our own dogfood.

This whole removal thing felt a bit like when a Sponge dev would remove the stop command with the reason that he uses the "X" on the powershell console all the time while developing anyway and the stop command fails from time to time with bad plugins.

How is that even a comparison? The removal of timings was to do with the implementation and how it was bad data, a fundamental issue, not a workflow one.

This is what I find quite extraordinary about some of these statements - we're getting significant criticism about this decision and while I've made the position clear, I'm still being told "this is bad, Sponge should have this, etc. etc."., yet we're getting no-one coming up to the plate to help us with a better version of Timings. Indeed:

Admins do find this very useful and at least for me and even if no one will care, it renders Sponge 1.16 not viable for me.

Comments like this aren't going to make us change our opinions, demands and what feels like blackmail aren't going to get anywhere. Please remember that:

Sponge is a free product, we have never, and will never charge for it.
We are volunteers who try to work on it in our spare time because we want to make the best API we can. None of us get paid to do this, none of us want to get paid to do this.
We are open source and we accept contributions, as I said before.

I have explained what the options are in a previous comment. I haven't closed this issue because I understand people's arguments, but equally, understand that we're not reintroducing what we had.

That statement is true for the real world or enterprise applications. The data that was generated was not always inaccurate and even if it was inaccurate,it gave you a direction, which was very important. Its nice to know where to start. >Here again, low entry barrier. Basic diagnosis for people that have Spark not (yet) installed.
It's not nice to know where to start when you can't have any confidence in it being correct. People were on dual's case for Nucleus in timings, so they must have felt very nice knowing where to start - but they were also wrong.

This is the crucial problem with timings, in my opinion: Some server owners think it works because once in a blue moon it turns up with a result that vaguely points in the right direction. The code for it is outdated, painful to maintain unless I miss my guess, and generates an avalanche of incorrect diagnoses - but some server owners think it works, have been conditioned to think it works by its accuracy in the past, so they fight tooth and nail to protect it. They don't have the development knowledge to know how misleading it is, how much damage it causes to be misled, or even the kind of time that needs to be spent (free of charge!) to maintain the same tool that's generating so many misdiagnoses. What they do know is that it makes them feel like they have a grip on what's going on, regardless of how untrue that is, and they know that they don't want to learn how to generate or read Spark reports for real answers.
The TL;DR is this: Developers working for free should not spend their time working on only seasonally useful tools for the illusion of benefit to server owners that simply don't want to learn how to use a working one. As dualspiral has said repeatedly, if you're so keen on this half-measure placebo, put some money into having it maintained.

I have explained what the options are in a previous comment. I haven't closed this issue because I understand people's arguments, but equally, understand that we're not reintroducing what we had.

This discussion has strayed far, far from my original post. I am not asking for anyone's opinion on a hypothetical server spending, I am asking to consider the other side of the argument. There was no need for this adversity, and it has no place here.

In the end, we developers are the ones who are maintaining the software, and we made that judgement call as no-one else has been pitching in.

I didn't realize this had been a public consideration before removal, but if it was, it likely wasn't made public enough - I for one would've pitched in sooner. I understand why it was an internal decision, someone has to pull the trigger eventually on big changes, and this is one of them.

Not always, as I said, it led to mis-diagnosis because of bad data. Some of that is down to the implementation doing the wrong thing.

Absolutely, which is why I pointed to an implementation issue being at fault for timings' lack of reliability. I remember 1.10.2 as an entirely different beast to 1.12.2 when it came to performance diagnosis, and timings was used widely then.

This brings me back to my main point, which yes, was the use-case of timings concerning accessibility, but also the standard in place vis-a-vis other profilers. I've mentioned this to Luck prior - when Spark became the norm due to lack of Timings' maintaining. His answer made sense, Spark doesn't need to relay as much information as timings because it is meant to be used in conjunction, not instead of.

Therefore, I am suggesting the re-adding of timings to the Sponge API platform, either included by default within it, or as an external mixin plugin for diagnosing purposes.

The first option of my suggestion is a no-go, but is there the possibility of the second one?

Someone external can do it, it won't be the core team.

source: gharchive/issue

authors: HackuJacku Hiroku Mikirae Niiohontesha PGGreed Rasgnarok Yeregorix aglarcz dualspiral johnfriedrich snomnomnom

repo: SpongePowered/Sponge

license: MIT

license_type: permissive

license_source: github-api


text:
snip

snip

@pie-flavor Please don't remove the content from your issue when you resolve it yourself.

authors: kashike pie-flavor

repo: SpongePowered/SpongeAPI


text:
Add 'title scheduler' to allow plugins to display multiple sequential titles

Currently, the API allows plugins to send individual Titles to plugins. However, sending a title while another title is in progress will cause one of the titles to be immediately overwritten.
Sponge should provide a utility class to allow a plugin to schedule a sequence of titles to be displayed to the client. This class would take care of scheduling titles to be sent as soon as possible, while ensuring that none of them overwrite each other.

The same is true with other things in the game:

titles
scoreboard data
action bar

I was thinking this was near useless honestly and that plugins could handle it themselves.
But then I realized it may be needed for cross plugin queuing.

@kashike: I don't see how scoreboard data fits here - nothing that's displayed on a scoreboard is ephemeral the way that titles and action bar messages are.

At least we can check, if scoreboard exists, but we can't do this with titles+action bar.

authors: Aaron1011 XakepSDK kashike ryantheleach


text:
[WIP] Add API for generating error reports

API | Common

This is a continuation of #793.

@phroa Since you seem to be interested in this, what are your thoughts on renaming ErrorReport to CrashReport (and related Error -> Crash)?
When being displayed Minecraft Crash Report is used to display and we shouldn't/can't change that really, as well as the fact that this is a crash, not an error (we intentionally "crash" the server).

Shouldn't it only crash the server and spew the report if #dispatchFatal is called?
(If not, I'd say rename it.)

Technically, yes, but the issue is that we refer to it as an "error report", but when it is being displayed/etc it is referred to as a "crash report".

Another issue is reusability - ErrorReport and ErrorReport.Category cannot be reused due to stacktraces being included, which will be different each call more than likely.

Yeah, I'd say rename.

To be honest, I've taken a liking to @Mumfrey's PrettyPrinter as it's powering a lot of the new cause tracker's exception printing and debugging. If anything, it's far easier to manage than having the equivalent of CrashReporter from Minecraft itself.

I find Minecraft's CrashReport to be more useful in a crash - a PrettyPrinter is fine for a non-crash error.

@kashike Did we abstract the Pastebin service?

@20zinnm CrashReportPublisher

Would this API allow for what I'm talking about here:
https://forums.spongepowered.org/t/crash-handlers/12694

@SocraticPhoenix What are you wanting to do on crash?

I guess something like Calling an service or API that informs the admin of the crash or reset the server to a valid state after it had crashed serveral times in a row.

@ST-DDT A CrashReportPublisher is able to publish reports to an external service if allowed by the server administrator. As for resetting the server, that's best handled by a server wrapper in my opinion.

@kashike
I'd like to emergency-save plugin data to disk. Configuration, player data, etc. The problem with this is that it could potentially spawn it's own errors, so I'm not sure if it fits into this API.

Please update the target branch to bleeding (Edit this PR and change the target branch) and reopen.

source: gharchive/pull-request

authors: 20zinnm Deamon5550 ST-DDT SocraticPhoenix gabizou kashike phroa


text:
Retrieve world a block resides in

In the current API there is no ability to retrieve the world a block resides in. This PR adds this ability which is helpful for plugins that rely on checking blocks and their location.

blockLoc.getExtent() is your world.

authors: MattBDev kenzierocks


text:
Add getter for Chat Receivers

This adds the ability to easily and simply get who receives a chat message.

Could this be modified to also include other events that send messages to players, such as PlayerDeath, PlayerJoin and PlayerQuit? Perhaps abstract out this and get/setXMessage() into an interface?
I was creating a project a while back that would only show death messages to players in certains areas, but I had to blank the message and resend it to only those people, which wasn't particularly elegant.

Why is it only players who are receivers? What about the console
how about a set of CommandSources instead?

I would rename the method to getRecipients().

You'll also need to add the necessary setters in SpongeEventFactory. If you add a field called getX, you need to have a values.put("X", value) in the event factory (in this case, any event that extends or is PlayerChatEvent needs to have a values.put("recipients", someSetReferenceOfPlayers);).

Oops forgot to import Set, doing it now.

Changed. Hopefully this will be the last commit :)

Now you also have to change createMessage in the event factory.

Closing this in favor of https://github.com/SpongePowered/SpongeAPI/pull/694
Thanks for bringing this to our attention @DotDashh .

authors: DotDashh ZephireNZ Zidane boformer gabizou simon816


text:
Lightning set to be an effect still creates fire

Location<World> loc = ...;
Optional<Entity> optLightning = loc.getExtent().createEntity(EntityTypes.LIGHTNING, loc.getPosition());
if (optLightning.isPresent()) {
    Lightning lightning = (Lightning) optLightning.get();
    lightning.setEffect(true);
    loc.getExtent().spawnEntity(lightning, Cause.of(this));
}

Per the java-docs when setEffect is set to true lightning should not do damage, and thus should not create fire.

@DarkArc: I'm having trouble reproducing this. Can you give me a test plugin that can easily reproduce it?

@Aaron1011 seems it's been fixed by something (either from updating Forge or Sponge, made the 1.8.9 jump) either way, no longer an issue.

This is back.

I'll look into this

@DarkArc I can't reproduce this on the latest SpongeForge. Is there still an issue?

@simon816 I'm still seeing fire blocks.

Oh I think I had the difficulty level set incorrectly. I've reproduced it now.

repo: SpongePowered/SpongeCommon


text:
Does not support CYD ESP32-2432S024

Stably works only on ESP32-2432S028 which is 2.8 inches.
On ESP32-2432S024 which is 2.4 inches - does not work

this is the USB C Version correct? it should work if you flash that variant
also if it doesn't work its gonna be hard for me to verify that any fixes i do would work since i don't have that CYD Model and don't plan on supporting it right now
the only CYD Variants i support is
Micro USB
Dual USB
And USB C 2.8 inch
Maybe in the future ill begin supporting more CYDs but there's too many rn to count

Buddy, I understand the confusion, but the ESP32-2432S024C module has a CST820 sensor. It simply won't work because this library is not declared. Please confirm that this firmware is only for the ESP32-2432S028.

Не подтвердите а укажите в тексте чтобы другие не путались

Buddy, I understand the confusion, but the ESP32-2432S024C module has a CST820 sensor. It simply won't work because this library is not declared. Please confirm that this firmware is only for the ESP32-2432S028.

i plan to be more transparent in the future about what CYDs specifically work with this firmware thank you


text:
🛑 [B] IP Ending with .222 is down

In df5256c, [B] IP Ending with .222 ($IP_GRP_B.222:$MONITORING_PORT) was down:

HTTP code: 0
Response time: 0 ms

Resolved: [B] IP Ending with .222 is back up in 1437bbf after 5 minutes.


text:
feat: scrim locked reason [CU-3yw11q7]

adds a reason for why scrims are being locked

Task linked: CU-3yw11q7 Scrim Locked Reason

repo: SprocketBot/sprocket


text:
Abstract subnet implementation relationship issue

The relationship 'implements' was previously used from a logical subnet to an abstract subnet implemented by the logical subnet. This was used to indicate when a radio access network or IP network was part of a cellular network, or when a WiFi LAN represented a WiFi hotspot in a specific location.
Subtypes were later introduced while addressing issues #162 and #152: implementsCN always refers to a Cellular Network, and implementsHS to a WiFi hotspot.
Unfortunately, some cases were overlooked where the base type 'implements' is still used when actually it should be one of the new types.

A review of patterns using the 'implements' relationship reveals that some threats really do need to use 'implements'. These threats apply to radio networks that may be:

A WiFi subnet accessible in only one space, so not abstract even if the providing host is portable, so it would be called a hotspot. In this case, the subnet would have a loopback 'implementsHS' relationship indicating it is its own implementation.
A WiFi subnet in one space implementing a hotspot that is available in multiple spaces. The first subnet would be related to the hotspot via 'implementsHS'.
A radio access network (RAN) implementing a cellular network in a space, with an 'implementsCN' relationship.

All three cases can be covered by a threat containing any radio subnet related via 'implements' to an abstract subnet.
In other cases, 'implements' was used by accident because of the way MS Access does autocomplete when selecting from a list of options. The only way to fix that is to make 'implements' more restrictive than either subtype, but that would also mean replacing threats that cover both with two separate threats.

Now fixed on branch 151.
Renamed 'implements' as 'implementsAN', then reviewed threat and construction patterns and replaced 'implements' by this or by one of its subtypes, whichever is appropriate.

Note that the reason the original relationship was split into two subcases was because we needed one of them to be assertible and the other not in order to address #152.

repo: Spyderisk/domain-network


text:
[Add] Scroll to Top button

Details
Problem:
When user scroll down then there should be button to back to top of the website which is not present here so they have to scroll again to back to top.
Solution:
I would like to add scroll to top button so that user can went to top of website in a single click.
Screenshots
No response
Type of Contribution

[ ] Update to an existing Animated Button
[ ] Adding a new Button
[ ] Resolving a bug
[X] Proposal to the Repository
[ ] Changes related to documentation or README.md
[ ] Other Changes

Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I am willing to work on this issue
[X] I am a GSSoC'23 contributor

It's already added in the new UI!
Closing as completed!


text:
[Add] GLASSMORPHISM BUTTON

Details
I want to add a GLASSMORPHISM BUTTON
Screenshots
https://github.com/Spyware007/Animating-Buttons/assets/119161467/9be37be9-11f7-4b9e-84fa-2a3c0d148e09
Type of Contribution

[ ] Update to an existing Animated Button
[X] Adding a new Button
[ ] Resolving a bug
[ ] Proposal to the Repository
[ ] Changes related to documentation or README.md
[ ] Other Changes

Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I am willing to work on this issue
[X] I am a GSSoC'23 contributor

@Souravvmishra I writing to bring you attention towards considering and reviewing the issue and assigning me this issue.
so please can you assign me this issue

@TANYA-CHAN Please assign me this issue

@Spyware007  I writing to bring you attention towards considering and reviewing the issue and assigning me this issue.
so please can you assign me this issue

@adity2911  please assign me this issue

Kindly make PR asap and try not to make any further changes.

ok


text:
Added a cool button

I have added a new button

Thank you for your contribution. 🤩


text:
crash

my game crashes pls fix 1.20.2

Can you send over your latest.log? Should be located inside your .minecraft/logs folder.

Closed because of inactivity.

repo: Spyxar/TipTapShow


text:
TSC Meeting (02 June 2020) Agenda: ChatOps Survey, Integrating EWC Components

TSC Agenda June 2nd, 5:30pm UTC, 12:30pm EDT, 9:30am PDT
Administrative Items

[ ] Next meeting is July 7th, 2020

[ ] Who is leading?

Discussions

[ ] Integrating EWC components

[ ] st2flow -> st2web

[ ] How to handle VCS integration?

[ ] Electron app that uses git on user's local machine?
[ ] Have ST2 add a commit in pack repo in /opt/stackstorm/packs/?
[ ] Automatic push to git remote + open a PR?

[ ] Apt/RPM packaging for LDAP/RBAC/SSO plugins? Or just roll them into st2 package?

[ ] ChatOps Survey (@blag)

[ ] Survey Monkey?
[ ] Who is paying for this/can we get LF to pay for this?

[ ] Revisit v3.3 proposed featureset (@blag, @punkrokk)
[ ] Review status of proposed new contributors

v3.2.1 patch release (https://github.com/orgs/StackStorm/projects/10) (@punkrokk)
Ravi from Extreme should join us to answer any EWC OSS transition questions

FYI we should also plan to open our monthly TSC meetings, likely from the next one July 7th, 2020, per LF requirement.

TSC Meeting Minutes
Changing copyright headers

Needs to be done or at least approved by somebody at Extreme Networks
Need to add Linux Foundation to copyright claims
Need to have a template for copyright headers on new files?

DECIDED

For Apache 2.0 License:

Add one line to the copyright section of every file that has a header.
Do not remove it.
Winson will approve the PRs

Linux Foundation Updates

May need to change the CLA to be in alignment with LF
Don't necessarily need to change to EasyCLA

Don't like it because it forces clickthroughs for every single commit
Needs more research into wording in technical charter

LF Community Bridge approved

provides a way for people to donate to project

provides a way for us to expense it

Zoom
ChatOps User Survey with Survey Monkey

Plan is to make announcement about it

Dmitri will update ActiveCampaign list, and send out another email regarding LF donations

Ping Dmitri when we update the blog, so he can blast out emails on ActiveCampaign

Opening up TSC Meetings

Use LF "TSC Open" mailing list to announce meetings and invite spectators
Use LF "TSC Closed" mailing list to record votes and keep LF folks up-to-date

How to run TSC meetings?

Do we want a different person running every TSC meeting?

Do we want to appoint a TSC chairperson to run all TSC meetings?

Continuity is important - difficult to parachute into an issue

It might be good for each TSC member to do a lap of running TSC meetings

12 months is too long of a period for one person to run meetings

3 months is the minimum length

6 months seems about right

Do we want to split up meetings into 1 monthly administrative meeting and 1 technical meeting?

DECIDED

Eugen running TSC meetings for the next 3 months - THANK YOU!

JP and Nick will informally help do the sprint planning
will revisit how this is working in 3 months

Expectations of TSC members

What is the bare minimum?

At what point do we vote to take action on another community member?

DECIDED

Tabled - moving discussion to the next meeting

JP will consolidate the concerns

ChatOps User Survey

How many people?

Target is to get 100+ responses
Below 50 responses, results aren't super useful
Check out the previous ChatOps User Survey

Is there an Issue for July’s agenda?

We'll create one a several days before the July meeting as composing agenda right now is too early and things may change.

authors: armab blag timfong888

repo: StackStorm/discussions


text:
Adding initial all-in-one installation

This PR adds the initial documentation for the All-in-one installer. This adds instructions on how to get the AIO install via Vagrant or AWS.
The actual AMI instructions do not exist yet. Still waiting on upstream approval, but that shouldn't stop a cursory review of content.
More to come!

Some info on how to get help on errors and linking them to slack-community in the doc would be useful I think.

<3. Good PR.

Some info on how to get help on errors and linking them to slack-community in the doc would be useful I think.

Ok, I'll keep that in mind as I go through these updates, but not going to stop to block here.

Good stuff.

Hawt!

authors: Kami dzimine jfryman lakshmi-kannan

license_source: bigquery


text:
Project Status?

Hello.
Would it be possible to get an update on the status of this project? Is it done? Is there something lacking to remove the beta label?
It seems to be the encouraged method for ssh agent forwarding when using mosh, do you know if this is still the case?

Guardian Agent was written as part of an academic project, which has been completed, so I'm not currently actively maintaining it. It is done, but since it has never undergone a thorough security review,  the beta label serves mostly as a warning.

Thank you for the quick reply Dima. I hope this isn't an annoying question,
but is there any related works or other similar projects that you're aware
of, maybe that you use or recommend, or is guardian-agent fairly unique?
Cheers!
On Fri, Jun 28, 2019, 15:09 Dima Kogan notifications@github.com wrote:

Guardian Agent was written as part of an academic project, which has been
completed, so I'm not currently actively maintaining it. It is done, but
since it has never undergone a thorough security review, the beta label
serves mostly as a warning.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/StanfordSNR/guardian-agent/issues/24?email_source=notifications&email_token=AACP25FJOFV2OF42FWBYF5DP4YERTA5CNFSM4H4DN4TKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODY2A36Y#issuecomment-506727931,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AACP25C7CHJRMUDLSYZTSI3P4YERTANCNFSM4H4DN4TA
.

I guess that despite the beta status, I think that I would still recommend using Guardian Agent as it is better than insecure agent forwarding.

authors: colemickens dimakogan

repo: StanfordSNR/guardian-agent


text:
:bug: Fixing a bug that lead to StackOverflow

Version: 1.5.1.2-SNAPSHOT
Hi @StannisMod!
Recently found a bug in latest version of GExt in GLink component that lead to infinity recursion call and StackOverflow exception
Can you pls review && merge if approved?

Thanks for the contribution!

@Veritaris молодец джордж

authors: StannisMod Veritaris tox1cozZ

repo: StannisMod/gext


text:
addColor method doesn't correctly verify parameters

Minecraft Version: 1.12.2
Forge Version: 14.23.5.2768
Java Version: 11.0.1 2018-10-16 LTS
OCGlasses Version: 2.1.1-6
When using addColor, if you input any value over 1, it causes a crash with the error "Color parameter outside of expected range".  This crash persists when reloading the world.  The only fix I have found so far is to reload the world without the OCGlasses mod.

thanks for reporting this issue. The next release will limit the values to 0-1
you can grab a prebuild here:
http://ci.pc-logix.com/job/OCGlasses/13/artifact/build/libs/OpenGlasses-MC1.12.2-2.1.1-13.jar

Looks like it's fixed as of 2.1.1-13.

authors: ben-mkiv mrmakeit

repo: StarChasers/OCGlasses

license: Zlib


text:
🛑 Action API is down

In 803f735, Action API (https://starcitizen.tools/api.php?action=query&prop=info&titles=Gladius) was down:

HTTP code: 403
Response time: 20 ms

Resolved: Action API is back up in 09672f3.

repo: StarCitizenTools/upptime


text:
🛑 Star Citizen Wiki Archiv is down

In 8307492, Star Citizen Wiki Archiv (https://archiv.star-citizen.wiki) was down:

HTTP code: 404
Response time: 466 ms

Resolved: Star Citizen Wiki Archiv is back up in b511451 after 9 minutes.

repo: StarCitizenWiki/status


text:
Query failed due to remove comment

query
select 'a' in ('/products/men\'s-urina' , '/products/super--absorbency-short-trucks-washable-reusable' );

https://github.com/StarRocks/starrocks/commit/8c456a89a40a2d1aa3803597c1096876f275d9d4
this pr do remove comment , but don't consider apostrophe in string literal.
StarRocks version (Required)
2.3.4

I don't understand what it means.

I don't understand what it means.

For example,  select  'ab 'sdf' , 'bsdf --sdfssdfas'  is changed( com.starrocks.sql.parser.SqlParser#removeComment )  to  select  'ab 'sdf' , 'bsdf , send to sqlparser , and failed. root cause is that https://github.com/StarRocks/starrocks/commit/8c456a89a40a2d1aa3803597c1096876f275d9d4 don't consider nested apostrophe in string literal.

https://github.com/StarRocks/starrocks/pull/15561 solved

repo: StarRocks/starrocks


text:
BE crash when enable_pipeline_engine true

Steps to reproduce the behavior (Required)

CREATE TABLE :

CREATE TABLE `unique_table_with_null_partition` (
                `k1` date,
                `k2` datetime,
                `k3` char(20),
                `k4` varchar(20),
                `k5` boolean,
                `k6` tinyint,
                `k7` smallint,
                `k8` int,
                `k9` bigint,
                `k10` largeint,
                `k11` float,
                `k12` double,
                `k13` decimal(27,9)
            ) ENGINE=OLAP
            UNIQUE KEY(`k1`, `k2`, `k3`, `k4`, `k5`)
            COMMENT "OLAP"
            PARTITION BY RANGE(`k1`)
            (
                PARTITION `p202006` VALUES LESS THAN ("2020-07-01"),
                PARTITION `p202007` VALUES LESS THAN ("2020-08-01"),
                PARTITION `p202008` VALUES LESS THAN ("2020-09-01")
            )
            DISTRIBUTED BY HASH(`k1`, `k2`, `k3`, `k4`, `k5`) BUCKETS 3
            PROPERTIES ("replication_num" = "1");

stream load:

curl --location-trusted -u root: -T /home/disk5/tiannan/sr_cases/StarRocksTest/lib/../common/data/basic_types_data -XPUT -H label:stream_load_1639809757529 http://***.***.***.***:8030/api/pred_push_down_join_1639809755002/unique_table_with_null_partition/_stream_load

SELECT:

select * from unique_table_with_null_partition partition(p202006) a left join unique_table_with_null_partition partition(p202007) b on a.k1 = b.k1 and b.k13 <= 29.6265 cross join unique_table_with_null_partition partition(p202008) c on a.k7 = c.k7 and c.k6 < 50 and c.k13 >= 0;

Expected behavior (Required)
query returns the right result
Real behavior (Required)
mysql> set enable_pipeline_engine = false;
Query OK, 0 rows affected (0.00 sec)

mysql> select * from unique_table_with_null_partition partition(p202006) a left join unique_table_with_null_partition partition(p202007) b on a.k1 = b.k1 and b.k13 <= 29.6265 cross join unique_table_with_null_partition partition(p202008) c on a.k7 = c.k7 and c.k6 < 50 and c.k13 >= 0;
Empty set (7.64 sec)

mysql> set enable_pipeline_engine = true;
Query OK, 0 rows affected (0.00 sec)

mysql> select * from unique_table_with_null_partition partition(p202006) a left join unique_table_with_null_partition partition(p202007) b on a.k1 = b.k1 and b.k13 <= 29.6265 cross join unique_table_with_null_partition partition(p202008) c on a.k7 = c.k7 and c.k6 < 50 and c.k13 >= 0;
ERROR 1064 (HY000): there is no scanNode Backend

coredump:
*** Aborted at 1639810635 (unix time) try "date -d @1639810635" if you are using GNU date ***
PC: @          0x1926811 butil::FlatMap<>::operator
*** SIGSEGV (@0x68) received by PID 23116 (TID 0x7f7267b33700) from PID 104; stack trace: ***
@          0x3353502 google::(anonymous namespace)::FailureSignalHandler()
@     0x7f72cfb54630 (unknown)
@          0x1926811 butil::FlatMap<>::operator
@          0x22a8ab9 starrocks::pipeline::CrossJoinLeftOperator::_copy_joined_rows_with_index_base_build()
@          0x22a978a starrocks::pipeline::CrossJoinLeftOperator::pull_chunk()
@          0x22bb375 starrocks::pipeline::PipelineDriver::process()
@          0x22b3820 starrocks::pipeline::GlobalDriverDispatcher::run()
@          0x1c6f129 starrocks::ThreadPool::dispatch_thread()
@          0x1c7d755 starrocks::Thread::supervise_thread()
@     0x7f72cfb4cea5 start_thread
@     0x7f72cef519fd __clone
@                0x0 (unknown)
StarRocks version (Required)

You can get the StarRocks version by executing SQL select current_version()

mysql> select current_version();
+-------------------+
| current_version() |
+-------------------+
| UNKNOWN d01c21d   |
+-------------------+
1 row in set (0.01 sec)

Fixed by https://github.com/StarRocks/starrocks/pull/2279

mysql> select * from unique_table_with_null_partition partition(p202006) a left join unique_table_with_null_partition partition(p202007) b on a.k1 = b.k1 and b.k13 <= 29.6265 cross join unique_table_with_null_partition partition(p202008) c on a.k7 = c.k7 and c.k6 < 50 and c.k13 >= 0;
Empty set (0.20 sec)
mysql> select current_version();
+------------------------+
| current_version()      |
+------------------------+
| QA_TEST_MASTER 728e940 |
+------------------------+
1 row in set (0.00 sec)

authors: Pslydhh tiannan-sr


text:
[WIP] [enhancement] BE support multiple s3 auth info

What type of PR is this：

[ ] bugfix
[ ] feature
[x] enhancement
[ ] refactor
[ ] others

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：

S3ClientFactory can generate client using variant S3 auth info now.
HdfsScanNode add THdfsProperties so that FE can pass different S3 auth info to BE

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] I have added user document for my new feature or new function

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.comboqiu seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

[FE PR Coverage Check]
:heart_eyes: pass : 0 / 0 (0%)

[FE PR Coverage Check]
:heart_eyes: pass : 0 / 0 (0%)

authors: CLAassistant cbcbq wanpengfei-git


text:
[Feature] Support Primary Key table Backup & Restore

What type of PR is this：

[ ] BugFix
[x] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：

Fixes #11879
Problem Summary(Required) ：
[Feature] Support Primary Key table Backup & Restore(#11879)
Problem:
At present, StarRocks does not support the backup and restore of Primary Key tables. This feature will support it.
Solution:
We basically reused the code of the primary key clone and transformed it to adapt to the backup restore process.

[FE PR Coverage Check]
:heart_eyes: pass : 1 / 1 (100.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/backup/BackupJob.java
1
1
100.00%
[]

[FE PR Coverage Check]
:disappointed: fail : 0 / 1 (00.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/task/SnapshotTask.java
0
1
00.00%
[82]

[FE PR Coverage Check]
:disappointed: fail : 0 / 3 (00.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/task/SnapshotTask.java
0
1
00.00%
[82]

:large_blue_circle:
com/starrocks/backup/BackupJob.java
0
2
00.00%
[625, 626]

[FE PR Coverage Check]
:disappointed: fail : 1 / 2 (50.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/task/SnapshotTask.java
0
1
00.00%
[82]

:large_blue_circle:
com/starrocks/backup/BackupJob.java
1
1
100.00%
[]

[FE PR Coverage Check]
:disappointed: fail : 1 / 2 (50.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/task/SnapshotTask.java
0
1
00.00%
[82]

:large_blue_circle:
com/starrocks/backup/BackupJob.java
1
1
100.00%
[]

[FE PR Coverage Check]
:heart_eyes: pass : 2 / 2 (100.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/task/SnapshotTask.java
1
1
100.00%
[]

:large_blue_circle:
com/starrocks/backup/BackupJob.java
1
1
100.00%
[]

[FE PR Coverage Check]
:heart_eyes: pass : 2 / 2 (100.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/task/SnapshotTask.java
1
1
100.00%
[]

:large_blue_circle:
com/starrocks/backup/BackupJob.java
1
1
100.00%
[]

[FE PR Coverage Check]
:heart_eyes: pass : 2 / 2 (100.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/task/SnapshotTask.java
1
1
100.00%
[]

:large_blue_circle:
com/starrocks/backup/BackupJob.java
1
1
100.00%
[]

[FE PR Coverage Check]
:heart_eyes: pass : 2 / 2 (100.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/task/SnapshotTask.java
1
1
100.00%
[]

:large_blue_circle:
com/starrocks/backup/BackupJob.java
1
1
100.00%
[]

[FE PR Coverage Check]
:heart_eyes: pass : 2 / 2 (100.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/task/SnapshotTask.java
1
1
100.00%
[]

:large_blue_circle:
com/starrocks/backup/BackupJob.java
1
1
100.00%
[]

run starrocks_admit_test

authors: srlch wanpengfei-git


text:
[BugFix] Disable tablet migration between local disks for pk table

What type of PR is this：

[x] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：

Fixes #13097
Problem Summary(Required) ：

Currently, primary key table doesn't support tablet migration between local disks.
Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Please check the version labels which this pr will be auto backported to target branch and click the checkbox:

[ ] check done.

[FE PR Coverage Check]
:disappointed: fail : 0 / 7 (00.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/leader/ReportHandler.java
0
7
00.00%
[916, 917, 918, 920, 922, 923, 928]

run starrocks_admit_test

@mergify backport branch-2.3 branch-2.4 branch-2.5

@mergify backport branch-2.3 branch-2.4 branch-2.5

authors: nshangyiming wanpengfei-git


text:
[Enhancement] Support cancel for TabletReader and SegmentIterator

What type of PR is this：

[ ] BugFix
[ ] Feature
[x] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：

Fixes #14290
Problem Summary(Required) ：

This PR adds cancelling support for TabletReader and SegmentIterator, so setting RuntimeState's canceled flag could cancel TabletReader and SegmentIterator's iteration.
Checklist:

[x] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto backported to target branch

[x] 2.5
[ ] 2.4
[ ] 2.3
[ ] 2.2

run starrocks_be_unittest

run starrocks_admit_test

run starrocks_admit_test

run starrocks_admit_test

run starrocks_admit_test

authors: decster wanpengfei-git


text:
[Enhancement][Cherry-Pick] Supports modifying the version to take effect without restarting

Fixes #34033
What type of PR is this:

[ ] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Does this PR entail a change in behavior?

[ ] Yes, this PR will result in a change in behavior.
[x] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

[x] I have added test cases for my bug fix or my new feature
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto-backported to the target branch

[ ] 3.2
[ ] 3.1
[x] 3.0
[x] 2.5

https://github.com/Mergifyio backport branch-3.0


text:
[cherry-pick] Support automatical meta compaction. (#4765)

What type of PR is this：

[ ] bug
[ ] feature
[x] enhancement
[ ] others

Which issues of this PR fixes ：

Fixes #4199
Problem Summary
In some cases, the meta stored in RocksDB does not compact for a long time, and the metadata size will reach a large number. Then the user can compact the meta with the meta_tool manually.
We need to let our users do fewer things, so we do this compaction automatically, so this PR puts the compact logic into the garbage_sweeper_thread thread to implement it.
10 column, 400000000 lines, origin data file 50G, random update 1000 rows(per data file 0.016M), one second one load, total 40000 loads,
reproduce large meta data dir

After this PR.

run starrocks_fe_unittest

authors: Linkerist chaoyli


text:
[others] Fix unstable RefreshTableStmtTest

What type of PR is this：

[ ] bug
[ ] feature
[ ] enhancement
[ ] refactor
[x] others

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：

Fix unstable RefreshTableStmtTest

[FE PR Coverage Check]
:heart_eyes: pass : 0 / 0 (0%)


text:
Planning: strings and unicode

There is some good discussion in https://what.thedailywtf.com/t/so-about-strings-and-unicode/52250/
Also, Perl 6 seems to be handling things in the ideal way:
https://6guts.wordpress.com/2015/04/12/this-week-unicode-normalization-many-rts/
Separate types and treatments for bytes, code points, and graphemes.

Certainly, UTF-8 will only be used via byte buffers (which are possibly behind a strong type alias) and signed types will be nowhere nearby.

repo: StardustPL/Stardust

license: Unlicense


text:
[bug]: Bitcoin price too low

Prerequisites

[X] I have searched for existing issues that already report this problem, without success.

EmbassyOS Version
0.3.0~2
Device
Laptop/Desktop
Device OS
MacOS
Device OS Version
10.14.6
Browser
Firefox
Browser Version
99.0.1
Current Behavior
Price too low
Expected Behavior
Mewn
Steps to Reproduce

Buy dip
Repeat
Deny possibility of market downtrend
Pain

Anything else?
No response

Closing as 1BTC is still 1BTC
Price has not moved and remains stable


text:
Issues with Brave tor

Signing up/logging in renders a page that asks if cookies are being blocked.
A naive messing with the cookie settings don't seem to reveal anything. Filing here for later.

Mastodon needs to set http onions as a secure context

authors: ProofOfKeags dr-bonez


text:
Not out of the box, but it can be adapted to be compatible with Vue.

Not out of the box, but it can be adapted to be compatible with Vue.
Originally posted by @davidtmiller in https://github.com/BlackrockDigital/startbootstrap-sb-admin-2/issues/192#issuecomment-458672881
We hope to have a tutorial to integrate Vue

We may have a Vue version on the way at some point this year, along with Angular!


text:
Division 2

Game Title
Division 2
Game Website
No response
Anti-Cheat Software
Easy Anti-Cheat
Status of the Anti-Cheat
⭐ Supported
Tinkering Steps
No response
Proof of Mention
https://store.steampowered.com/news/app/2221490/view/3632750190483497136?l=english

Tinker Steps should be:
Set Proton to Proton Experimental and set Proton Experimental to the Bleeding Edge branch. Fixes many still standing issues

duplicate of #1086


text:
Device numbering removal bug

Hello, I seem to have got myself into a pickle with the device numbering..
I have not yet tried the absolute minimum requirements to make this happen, but I have taken a video of it happening with 1 chip housing and 2 additional battery devices.
Video 🎥 https://streamable.com/re15bv
Though, I am currently unsure if the 2nd battery is really required here, but it is what I currently had, and I wanted to document this first incase I forget how I got in this mess.
Step 1: Have the default chip housing.
Step 2: Add 2 Station Batteries, default everything, but add 1 battery has d0, and 1 as d3 (no idea why I choice d3, just a whim)
Step 3: Refresh the browser. ❗ Observe they should STILL be the devices from before.
Step 4: Add d1 to the d0 battery, and observe they are both listed.
Step 5: Remove d0 ⚠ Observe they BOTH vanished ⚠
Step 6: Re-add d0 ❓ Observe d1 has returned with no mention of d0 ❓

Thanks. Fixed.

Confirmed, thank you.

authors: Traineratwot WORMSS


text:
Unify and merge style declarations into dedicated node

Unify and merge the style into dedicated node, and append to head at first run, instead of declaring them individually through DOM.
All conditional and dynamic styling has not been touched.
This should also fix #195,  #204 and column-count for the option columns.
Not sure about GM_addStyle and Chrome, as I haven't used it before.

Please squash your commits.

Sorry about that!

Tested it, seems to work as expected. But you need to rebase your branch so we can merge it.

I managed the squash part, but doing a rebase is another story.
I've really no idea, as I've never used github before, except basic commiting.
Can't really say the documentation on this site helps much.

It's basic git functionality. See https://github.com/edx/edx-platform/wiki/How-to-Rebase-a-Pull-Request

Why did you add so many empty lines?

The empty lines was a accidentally added while comparing.
Fixed now.

I'm glad its over.

authors: Orrielel chauffer xPaw

repo: SteamDatabase/steamSummerMinigame


text:
Support for Generichost in net core

Hi, the package for net core works fine in a wep app that uses the Webhost
What about net core console apps? a console app uses the Generichost. I try to use the package but i didn't succeeded.
class Program
    {
        static async Task Main(string[] args)
        {
            var host = new HostBuilder()
                .ConfigureHostConfiguration(configHost =>
                {
                    configHost.SetBasePath(Directory.GetCurrentDirectory());
                    configHost.AddJsonFile("appsettings.json", optional: true);
                    configHost.AddCommandLine(args);
                    // This method requires IHostingEnvironment param which is not available in a net core console app
                    configHost.AddConfigServer();
                })
                .ConfigureAppConfiguration((hostContext, configApp) =>
                {
                    configApp.AddJsonFile("appsettings.json", optional: true);
                    configApp.AddJsonFile($"appsettings.{hostContext.HostingEnvironment.EnvironmentName}.json", optional: true);
                    configApp.AddCommandLine(args);
                })
                .ConfigureServices((hostContext, services) =>
                {
                    services.Configure<ConfigServerData>(hostContext.Configuration);
                    services.AddHostedService<AuthJobConsumer>();
                    services.AddSingleton<IAuthResponseProducer, AuthResponseProducer>();
                })
                .ConfigureLogging((hostContext, configLogging) =>
                {
                    configLogging.AddConsoleAdvanced();
                })
                .UseConsoleLifetime()
                .Build();
            await host.RunAsync();
        }
    }

Thanks!

Hi @patrickqsos,
Can you elaborate on what didn't work and possibly provide a basic but complete sample app that illustrates the issue, so we can see which libraries and versions you're working with?
Up front, it looks like you're configuring your app configuration twice (under ConfigureHostConfiguration and ConfigureAppConfiguration) -- you could try the IConfigurationBuilder.AddConfigServer(); extension, that would go under .ConfigureAppConfiguration();

Hi @TimHess
I´ve created an app to reproduce the problem
https://github.com/patrickqsos/configserverconsole
That app is not meant to be a web app so I´m not using the  IWebHostBuilder. Instead I´m using the IHostBuilder,  which is useful for hosting apps that don't process HTTP requests.
Thanks!

OK, several things:

That project is referencing Steeltoe.Extensions.Configuration.ConfigServer version 1.1.1

That should be Steeltoe.Extensions.Configuration.ConfigServerBase version 2.1.1

I needed to add a reference to Microsoft.Extensions.Options.ConfigurationExtensions for services.Configure<ConfigServerData>(hostContext.Configuration) to compile
Unlikely to be part of your problem, but that appsettings.json wasn't being used as it wasn't getting copied to the output

appsettings.json has a typo (validate_certifates)

After fixing those, I'm able to retrieve config from Spring Cloud Config Server

So I was referencing a wrong package. I changed the reference to Steeltoe.Extensions.Configuration.ConfigServerBase and it works perfect!
Thank you for your time!.

authors: TimHess patrickqsos

repo: SteeltoeOSS/Configuration


text:
Make HealthEndpoint compatible with ALV

Description
Make health actuator response compatible with ALV.
Fixes #877
Quality checklist

[ ] Your code complies with our Coding Style.
[ ] You've updated unit and/or integration tests for your change, where applicable.
[ ] You've updated documentation for your change, where applicable.
If your change affects other repositories, such as Documentation, Samples and/or MainSite, add linked PRs here.
[ ] There's an open issue for the PR that you are making. If you'd like to propose a new feature or change, please open an issue to discuss the change or find an existing issue.
[ ] You've added required license files and/or file headers (explaining where the code came from with proper attribution), where code is copied from StackOverflow, a blog, or OSS.

/azp run Steeltoe.All

authors: TimHess hananiel

repo: SteeltoeOSS/Steeltoe


text:
allow auth plugin, include test module

Allow authentication to be plugged in as a module.
Also added an API register_storage_server to register a storage server.
A file in test folder test/test_auth.jl defines a module that can be plugged in to PkgServer as an optional authentication layer.

intended to serve as a test authentication system only.
reads userid and password from a plaintext file.
issues access_token and refresh_token after authenticating plaintext userid and password.
validates access_token
issues new access_token and refresh_token given a valid refresh_token

Example curl commands:
Fetch a fresh token.
$ curl -k -d "user_name=guest1&password=password1" -X POST https://pkg.server.com:8000/auth/issue
refresh_token = "QccAHlP1PnXg3xH5TFdohnjwfx5EOZx6"
expires_at = 1576133893
access_token = "N0pMCQQAAAA0EAEKTmFtZWRUdXBsZR9OAQRNYWlum0QCAAAAFAMBCmV4cGlyZXNfYXQBCmV4cGlyZXNfaW4BBnVzZXJpZBBTH04BBE1haW6bRAMAAAAACAAIEAEJU3ViU3RyaW5nH06eRAEAAAAAITEF5fFdMYBRAQA0LAUAIQZndWVzdDHf5Q=="
refresh_url = "http://127.0.0.1:8000/auth/refresh"
expires_in = 86400
userid = "guest1"

Refresh token:
$ curl -f -H "Authorization: Bearer 6oGZ78ft5xu9ozKIHOJxGdOTu0gJZ1Fh" http://127.0.0.1:8000/auth/refresh
refresh_token = "llkwYd2VddaMAb8EOvXqep5bAJh2Mwq6"
expires_at = 1576062956
access_token = "N0pMCQQAAAA0EAEKTmFtZWRUdXBsZR9OAQRNYWlum0QCAAAAFAMBCmV4cGlyZXNfYXQBCmV4cGlyZXNfaW4BBnVzZXJpZBBTH04BBE1haW6bRAMAAAAACAAIACEx7M/wXTGAUQEAIQZndWVzdDE="
refresh_url = "http://127.0.0.1:8000/auth/refresh"
expires_in = 86400
userid = "guest1"

Fetch resources using the token:
$ curl -f -H "Authorization: Bearer N0pMCQQAAAA0EAEKTmFtZWRUdXBsZR9OAQRNYWlum0QCAAAAFAMBCmV4cGlyZXNfYXQBCmV4cGlyZXNfaW4BBnVzZXJpZBBTH04BBE1haW6bRAMAAAAACAAIEAEJU3ViU3RyaW5nH06eRAEAAAAAITG6DfFdMYBRAQA0LAUAIQZndWVzdDHf5Q==" -o reg http://127.0.0.1:8000/registry/23338594-aafe-5451-b93e-139f81909106/a981131789e105c58d514d2d3adc8de5920ab149
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 1256k    0 1256k    0     0   409M      0 --:--:-- --:--:-- --:--:--  409M


text:
gio.nim codegen broken (new GTK3 version)

Hi,
after a GTK3 update (using arch linux or msys2) the gio code is broken.
Installed GTK3 version: extra/gtk3 1:3.24.30+62+g8d04980f38-2 [installed]
Exception:
/home/dankrad/.nimble/pkgs/gintro-0.9.4/gintro/gio.nim(25396, 6) Error: overloaded 'dupDefault' leads to ambiguous calls

In gio.nim, there are now overloaded functions, by return type:
proc dupDefault*(): MemoryMonitor

proc dupDefault*(): PowerProfileMonitor

I downgraded gintro and also python-gobject, but it still generates those two functions.

Thanks for reporting. Yes, that can happen, it's in some way a result of the name mangling and the fact that the return type of a function for Nim is not considered for overload resolution.
But it's a result of your GTK3 update, so downgrading gintro can not help. I am a bit surprised that this happened for GTK3, which is regarded as stable now. I hope that I can reproduce it on my Linux box. The fix is usually to rename the functions manually.
If you have a grep command available, then please execute in a terminal window
grep -C12 "proc dupDefault" ~/.nimble/pkgs/gintro-#v0.9.2/gintro/gio.nim

for your actual gintro version installed, so that I can see the original function names. For my Linux box there is currently only g_memory_monitor_dup_default(), but you should have one more.
I was going to release v0.9.5 soon, which contains a fix for very old GTK3 versions like Debian Buster, we can add a fix for your problem then too.

Sorry, I accidentally wrote gintro, but meant gtk.
Your requested grep execution (with -C num set to 16, to show the whole function implementation):
[dankrad@TNB ~]$ grep -C16 "proc dupDefault" ~/.nimble/pkgs/gintro-0.9.4/gintro/gio.nim
type
  MemoryMonitorWarningLevel* {.size: sizeof(cint), pure.} = enum
    low = 50
    medium = 100
    critical = 255

type
  MemoryMonitor00* = object of gobject.Object00
  MemoryMonitor* = ref object of gobject.Object

proc scLowMemoryWarning*(self: MemoryMonitor;  p: proc (self: ptr MemoryMonitor00; level: MemoryMonitorWarningLevel; xdata: pointer) {.cdecl.}, xdata: pointer, cf: gobject.ConnectFlags): culong =
  g_signal_connect_data(self.impl, "low-memory-warning", cast[GCallback](p), xdata, nil, cf)

proc g_memory_monitor_dup_default(): ptr MemoryMonitor00 {.
    importc, libprag.}

proc dupDefault*(): MemoryMonitor =
  let gobj = g_memory_monitor_dup_default()
  let qdata = g_object_get_qdata(gobj, Quark)
  if qdata != nil:
    result = cast[type(result)](qdata)
    assert(result.impl == gobj)
  else:
    fnew(result, gio.finalizeGObject)
    result.impl = gobj
    GC_ref(result)
    if g_object_is_floating(result.impl).int != 0:
      discard g_object_ref_sink(result.impl)
    g_object_add_toggle_ref(result.impl, toggleNotify, addr(result[]))
    g_object_unref(result.impl)
    assert(g_object_get_qdata(result.impl, Quark) == nil)
    g_object_set_qdata(result.impl, Quark, addr(result[]))

--
  if gerror != nil:
    let msg = $gerror.message
    g_error_free(gerror[])
    raise newException(GException, msg)
  result = resul0

type
  PollableSourceFunc* = proc (pollableStream: ptr gobject.Object00; userData: pointer): gboolean {.cdecl.}

type
  PowerProfileMonitor00* = object of gobject.Object00
  PowerProfileMonitor* = ref object of gobject.Object

proc g_power_profile_monitor_dup_default(): ptr PowerProfileMonitor00 {.
    importc, libprag.}

proc dupDefault*(): PowerProfileMonitor =
  let gobj = g_power_profile_monitor_dup_default()
  let qdata = g_object_get_qdata(gobj, Quark)
  if qdata != nil:
    result = cast[type(result)](qdata)
    assert(result.impl == gobj)
  else:
    fnew(result, gio.finalizeGObject)
    result.impl = gobj
    GC_ref(result)
    if g_object_is_floating(result.impl).int != 0:
      discard g_object_ref_sink(result.impl)
    g_object_add_toggle_ref(result.impl, toggleNotify, addr(result[]))
    g_object_unref(result.impl)
    assert(g_object_get_qdata(result.impl, Quark) == nil)
    g_object_set_qdata(result.impl, Quark, addr(result[]))

I am a bit surprised that this happened for GTK3, which is regarded as stable now.

I'm surprised too, and realized that I downgraded the wrong package. I should have downgrade glib.
The glib update was a minor update, so it makes sense that it's broken now:
[2021-09-28T18:32:44+0200] [ALPM] upgraded glib2 (2.68.3-1 -> 2.70.0-1)

For my Linux box there is currently only g_memory_monitor_dup_default(), but you should have one more.

I still only have one g_memory_monitor_dup_default() function:
[dankrad@TNB gintro-0.9.4]$ grep -A2 "proc g_memory_monitor_dup_default" ~/.nimble/pkgs/gintro-0.9.4/gintro/gio.nim
proc g_memory_monitor_dup_default(): ptr MemoryMonitor00 {.
    importc, libprag.}

Should be fixed in #head.
Please try with
nimble uninstall gintro
nimble install gintro@#head

I have done a manually rename of the procs:
< fixedProcNames["g_memory_monitor_dup_default"] = "dupDefaultMemoryMonitor"
< fixedProcNames["g_power_profile_monitor_dup_default"] = "dupDefaultPowerProfileMonitor"

We could consider trying to detect such name conflicts automatically, and do a plain automatic rename in that cases appending a number to the proc name.
On the other hand, I think this is the first time in 5 years that we got surprised by such a NEW name conflict. Indeed as it was glib/gio that changes are not that surprising, they still develop GTK4, and GTK3 and GTK4 uses the same glib. Indeed I just updated my Gentoo Linux box and got the same name conflict -- there must have been a Gentoo update in the last few days, as a week ago all was still fine.
When it works for you, I will then ship v0.9.5 in the next days.

This issue is fixed in my case. Thank you!

repo: StefanSalewski/gintro

license: mit


text:
Add the psp reference as the response code if it doesn't exist.

In a previous PR (#64) we fixed an issue where the redirect didn't have a psp_reference, so couldn't combine with the notification properly. However the PR only fixed the scenario where the redirect was first. This ties up the loose ends when the notification is first, and adds a test for the issue when psp_reference isn't included in the redirect response.

:+1:

authors: Dkendal simonpfry

repo: StemboltHQ/solidus-adyen


text:
No Data or Unique ID

Firstly - this is my potential unicorn! Been looking for so long to try and get my SofarSolar ME3000SP into Home Assistant..
I can split this if it’s two issues, but I’m not getting any figures returned. The IP/serial is correct, and I also get the following on all entities - is it related to my issue?
“This entity ('sensor.solarinverter_daily_production') does not have a unique ID, therefore its settings cannot be managed from the UI. See the documentation for more detail.”
Could you give me any pointers as to where I’d look for errors? Nothing in the main HA log, but any others I should check?
Many thanks, and appreciate your work..

I just had a look to see if I can replicate the issue, and if I select the entity, then click on the gear icon, I get the same message. However, the entity is updated automatically and you do not need to manage the entity settings.
If you select the entity on a card, and it displays the actual value (instead of "unknown"), the component is working as expected. If however it stays on "unknown" it may be due to the following:

Check if the inverter has a solarman wifi stick.  I do not have a Sofar inverter, but from info I received it does seem like there is a high probabilty that the collector will be compatible.
https://www.sofarsolar.com/product-detail/499/Stick-Logger
Verify the settings. For that go the web portal of the stick on the local network (not the solarman web portal). If it asks for login, it is proably "admin" and "admin". Then expand "Device Information" and note the "Device serial number". The IP you used and the serial number displayed in the portal is supposed to be used in the configuration settings.
If it works and you get the information you need, just reserve the IP for the stick on the router so that it will not change.

Thanks for the quick reply. That side is all good - I’ve had it working with Solarman for a year now. One difference seems to be that you’re on a slightly higher firmware of the logger (1.29) whereas I’m on 1.15. Wonder if that could be an issue. I’ll see if I can track down some firmware for it..
Other than that, it’s pretty much the same, hence wondering if there are any logs or trace info somewhere.
Thanks though

Update - my serial number starts 40, which I think might use the earlier version of the Solarman protocol, so think I’ll need to try that now archived project you linked to. Might get a more recent logger and hook that in, in the medium term

I see someone else took over that project, and it is now added to HACS. Good luck!
https://github.com/hultenvp/home_assistant_omnik_solar

authors: StephanJoubert jimmy-mc


text:
Added timeout to WaitAsync method

Renamed the _mutex variable to _syncRoot, as it's actually a sync root for a monitor lock and is not an actual mutex

Hello, nzaugg,
Thank you for the pull request. However, not having int/TimeSpan timeout overloads is a deliberate decision. The AsyncEx way of doing timeouts is to use CancellationTokens.
On a side note, your implementation would use a single timer for the entire AsyncManualResetEvent instance, which would have incorrect semantics. You'd need a timer per method call so that the timer isn't shared.

authors: StephenCleary nzaugg

repo: StephenCleary/AsyncEx


text:
🛑 DNS (he.net) is down

In 8538277, DNS (he.net) ($HE_NS) was down:

HTTP code: 0
Response time: 0 ms

Resolved: DNS (he.net) is back up in c2d0f50.

repo: Sternwarte-St-Ottilien-e-V/status


text:
🛑 Wetter is down

In 140db9a, Wetter ($WETTER) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Wetter is back up in 35fc18b.


text:
🛑 DNS (he.net) is down

In b50c6f3, DNS (he.net) ($HE_NS) was down:

HTTP code: 0
Response time: 0 ms

Resolved: DNS (he.net) is back up in 221cd05.


text:
🛑 DNS (he.net) is down

In 40eca52, DNS (he.net) ($HE_NS) was down:

HTTP code: 0
Response time: 0 ms

Resolved: DNS (he.net) is back up in 9f7115b.


text:
New porn sites

jjgirls.com
sexverhalen.com

Ping @sinfonietta

@StevenBlack this is done in commit https://github.com/Sinfonietta/hostfiles/commit/f4765111bfdb37d80709c5986d910b42b15fca65

authors: Sinfonietta StevenBlack simon1964

repo: StevenBlack/hosts


text:
Error downloading account name

DebugInfo.txt

Procurement 1.9.9 has been released, please retest and reopen your issue if your error persists:
https://github.com/Stickymaddness/Procurement/releases/tag/1.9.9

repo: Stickymaddness/Procurement


text:
Unable to connect to OBS. Attempting to reconnect {count} of {max}

Describe the bug
After enabling obs at "..\TrovoBot-master\services\obs\obs.json" "active": true," the bot fails to start throwing the following error:
Unable to connect to OBS. Attempting to reconnect {count} of {max}

C:\Users\user\Desktop\TrovoBot-master\services\obs\obs.js:25
                                activate();
                                ^

ReferenceError activate is not defined
    at Timeout._onTimeout (C:\Users\user\Desktop\TrovoBot-master\services\obs\obs.js:25:5)
    at listOnTimeout (internal/timers.js:554:17)
    at processTimers (internal/timers.js:497:7)

To Reproduce
Steps to reproduce the behavior:

Go to '..\TrovoBot-master\services\obs'
Open 'obs.json'
Change '"active": false,' to '"active": true,'
Go to '..\TrovoBot-master"
Open the terminal
Run 'npm .' or 'npm index'
See Error

Expected behavior
Run normally being able to integrate custom alerts with obs
Desktop

OS: Microsoft Windows 10 Version 2004 (OS Build 19041.572)
Browser: Microsoft Edge
Version: 86.0.622.56

YAY <3 I love you :D first real Bug Report YIPPY~ I'll get on this ASAP ^_^

i notice this bug when obs is not open but when opened this error does not come up

We will make changes to the documentation, and throw additional errors into OBS plugin for this.

This is solved, and will be in the next release

repo: Streamers-Workshop/Blazebot


text:
Added Doc-Blocks for API documentation generation by ApiDoc

See: https://github.com/Strider-CD/strider/issues/667#issuecomment-120571324

Hopefully I did not make many mistakes, though I am sure that there are some.  I'll happily make corrections on request.
To view the output documentation, first checkout strider, then:
> cd strider
> npm install -g apiDoc
> npm run-script gendoc

.. output will go to apidocs.
On a side note, I added a .editorconfig file to the project as well.  My IDE settings promote tabs and not spaces, so I added the .editorconfig so that my IDE would not constantly overwrite your conventions with my own.

Regarding the Travis CI failure.  I apologize that I am not very familiar with Travis or the particulars of the Strider builds and tests, so I could be mistaken, but it seems like the tests are failing on code unrelated to my changes.  How should I proceed?

Luke, I think you are right that the tests are broken for unrelated
reasons. See #664
On Sunday, July 12, 2015, Luke Chavers notifications@github.com wrote:

Regarding the Travis CI failure. I apologize that I am not very familiar
with Travis or the particulars of the Strider builds and tests, so I could
be mistaken, but it seems like the tests are failing on code unrelated to
my changes. How should I proceed?
—
Reply to this email directly or view it on GitHub
https://github.com/Strider-CD/strider/pull/835#issuecomment-120763407.

--
Niall O'Higgins
W: http://niallohiggins.com
E: n@niallo.me
T: @niallohiggins

Wow @vmadman! Have you used apiDoc before? This is great, glad to have you contributing.

Also, you don't need to install it globally since it's installed as a devDependency, just run npm run gendoc after npm installing in the strider directory.

Wow @vmadman! Have you used apiDoc before? This is great, glad to have you contributing.

I've looked closely at it for one of our projects, and maybe tampered with it a bit, but have never officially used it.  I ended up going with Swagger, instead, because Swagger allowed for testing the API directly in the docs and allows you to be a bit more specific (with validators, etc).
Still, ApiDoc seems like a really nice product and its concepts were easy enough to follow.

Swagger cam up in my research, but it was so vague that I didn't even pursue it. Do you think ApiDoc is the right move, having used both so far?

I made several changes based on your previous feedback and pushed my changes.  Please let me know if I missed any or if you find anything else.

Swagger came up in my research, but their site is so vague that I didn't even pursue it. Do you think ApiDoc is the right move, having used both so far?

I think ApiDoc is more suitable for Strider.  Swagger has a lot of extra features but for smaller projects I think its a little too clunky.  We use the json-schema style swagger definitions in our "developer center" -- as we have commercial subscribers to our API.  More than once I've shaken my fist in the air, though, and I think its probably more than Strider would need.

Oh, I also forgot to mention:  Although my curl tests should be correctly formatted, I was not sure about how the auth process works.  I assume I would call POST /api/session and then retain a token of some sort for my subsequent calls, but I was not able to figure that out... so, my curl examples do not reflect that.
If you can provide me with a little insight into that I can update the docs and will add additional request and response examples.

I'm actually not that familiar with the auth process, but having a look at the code it looks like it's basic auth, so Basic <base64(username + ':' + password)> in the authorization header, so it can be done directly once you have an account, no two way process.
FWIW, I think this is a bad design security wise and In the future we should look at using JWT tokens or similar.

authors: knownasilya niallo vmadman

repo: Strider-CD/strider


text:
Every GUI action is expensive

Because of https://github.com/StrikeForceZero/KSP-OrbitPOInts/blob/70dad7b9d63586731dbc5cc12f74084ca85c6c47/OrbitPOInts/OrbitPoiVisualizer.cs#L906 we are destroying and recreating the map drawing each time a POI changes when we only need to update the ones affected. We can utilize the new subscriptions setup for detecting which POI changed but we probably have to write a new state machine to track each poi and it's map drawings.
The poor responsiveness is really noticable when typing in the radius for custom POIs.
(This isn't exactly a bug as it was a known side affect when the code linked above was added)

fix is in https://github.com/StrikeForceZero/KSP-OrbitPOInts/tree/dev/rewrite_manager
just need to do some more testing, maybe add some more tests, and decide if I'm going to go back and break up some of the commits or squash merge it

repo: StrikeForceZero/KSP-OrbitPOInts


text:
🛑 Nextcloud Papa is down

In 2c0ff88, Nextcloud Papa ($NEXTCLOUD_2) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Nextcloud Papa is back up in c163c8c.

repo: StudFu-WordToMD/status


text:
🛑 Nextcloud Papa is down

In e4a45cb, Nextcloud Papa ($NEXTCLOUD_2) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Nextcloud Papa is back up in aa4581c.


text:
[PLUGIN/PROVIDER REQUEST] strapi-plugin-comments

Name
strapi-plugin-comments
Link
https://github.com/VirtusLab-Open-Source/strapi-plugin-comments
Status
Work In Progess
Type
Plugin
Author
No response

More info here: https://github.com/VirtusLab-Open-Source/strapi-plugin-comments/discussions/92

@Stun3R, plugin got rc.1 version already so it might be marked as Ready :)


text:
Cancel function

Thank you very much for this work which makes our lives easier... a question how can I know that a recording has just been canceled ?

Hello @Yaliih
can you update to latest version 1.0.0 and check stopRecording function
i call this function when user press cancle or slide to max left or user need to send audio sound
check it please and if you need any change tell me

you're welcome @Yaliih
can you check again please because stopRecording  call when user press on send button after lock record or when leave finger from record button

Thank you  @Subhi-Khalife
Yes you are right it was linked to a problem with my codes otherwise it works very well.
I am now thinking about how to add pause and play before sending the recorded message

@Yaliih
you're welcome
you can make it like inside sendRequestFunction you can take the file path and show record with pause and paly button
when user press send you can send message else igonre it

@Subhi-Khalife You are an angel thank you!
Lots of love !

authors: Subhi-Khalife Yaliih


text:
Valid MySQL escape characters likely to cause 'IndexError: list index out of range'

Building CTags for D:\broken.sql: Please be patient
error: An unknown error occured.
Check the console for info.
Exception in thread Thread-454:
Traceback (most recent call last):
  File "./threading.py", line 901, in _bootstrap_inner
  File "./threading.py", line 858, in run
  File "ctagsplugin in C:\Users\user\AppData\Roaming\Sublime Text 3\Installed Packages\CTags.sublime-package", line 119, in run
  File "ctagsplugin in C:\Users\user\AppData\Roaming\Sublime Text 3\Installed Packages\CTags.sublime-package", line 907, in build_ctags
  File "ctagsplugin in C:\Users\user\AppData\Roaming\Sublime Text 3\Installed Packages\CTags.sublime-package", line 892, in build_ctags
  File "ctags in C:\Users\user\AppData\Roaming\Sublime Text 3\Installed Packages\CTags.sublime-package", line 331, in build_ctags
  File "ctags in C:\Users\user\AppData\Roaming\Sublime Text 3\Installed Packages\CTags.sublime-package", line 365, in resort_ctags
IndexError: list index out of range

Environment:

Windows
ctags58.exe
Sublime Text 3 - Stable Build 3065

Minimal repro case:
INSERT INTO X (a) VALUES ('\'');
INSERT INTO X (a) VALUES ('DOMAIN');
INSERT INTO X (a) VALUES ('');

DOMAIN is a valid SQL token that happened to be in the original file as a string value.
Other SQL tokens I've tried don't lead to this issue.
Theory: Incorrect handling of backlash escape sequences.

I'll do debugging against head when I have time, unless someone beats me to it. ;)

ctags58.exe produces some trailing garbage ); in the tags file for the repro case above. This looks more like an exuberant-ctags bug.
However, should Sublime CTags try to work around the issue in the meantime?

Related PR: https://github.com/SublimeText/CTags/pull/279

repo: SublimeText/CTags


text:
[BUG] Dead link in Titanic Example

The link pointing to the titanic example on github is broken: https://doc.substra.ai/setup/demo.html#follow-titanic-example
It's the link on the repository word in the sentence:  see this repository for further details.

Woups, thank you @RomainGoussault for spotting this! There is indeed a .md that is missing at the end of the url, I will fix this!

repo: SubstraFoundation/substra-documentation


text:
docker error

This command
nvidia-docker run -it foresight/sim: bash

spits out an error:
nvidia-docker | 2019/03/12 13:31:02 Error: invalid reference format

I think the correct command is:
nvidia-docker run -it foresight/sim bash

Good catch! I forgot the tag. Below command should work too: (fixed in spec now)
nvidia-docker run -it foresight/sim:latest bash

authors: SudeepDasari skasewa


text:
Remove tags from generated artifacts

I.e. the changes in https://github.com/SuffolkLITLab/ALKiln/pull/561/files#diff-4b632aedc4c91285de358dd7cbcc91a52724745c5c759b81b3a6d80e8d6d7abcL187-R195.
Adding all of the tags to every output file makes the file names much too long, to the point where it's difficult to see more important information about an artifact. IMO tags are much less useful that the scenario id, which serves the same purpose.

Sounds good. I was on the fence about having them around anyway.

authors: BryceStevenWilley plocket

repo: SuffolkLITLab/ALKiln


text:
🛑 Chem Exper is down

In 02bce99, Chem Exper (http://www.chemexper.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Chem Exper is back up in 2c55603.

repo: Sulstice/Uptime-Cheminformatics


text:
🛑 Spectral Database for Organic Compounds is down

In 47a03b5, Spectral Database for Organic Compounds (https://sdbs.db.aist.go.jp/sdbs/cgi-bin/cre_index.cgi?lang=eng) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Spectral Database for Organic Compounds is back up in 88a9e34.


text:
🛑 Chem Exper is down

In fcdfa36, Chem Exper (http://www.chemexper.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Chem Exper is back up in 3351c7c.


text:
🛑 Zinc 20 is down

In 096b01d, Zinc 20 (https://zinc20.docking.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Zinc 20 is back up in 0941ca8.


text:
🛑 Chem Exper is down

In fdf1f0a, Chem Exper (http://www.chemexper.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Chem Exper is back up in 04e3e18.


text:
🛑 Chem Exper is down

In f453fac, Chem Exper (http://www.chemexper.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Chem Exper is back up in 19eb523.


text:
🛑 Chem Exper is down

In 8d6c1eb, Chem Exper (http://www.chemexper.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Chem Exper is back up in 4516f17.


text:
🛑 Zinc 15 is down

In e508915, Zinc 15 (https://zinc15.docking.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Zinc 15 is back up in 883c054 after 778 days, 18 hours, 21 minutes.


text:
🛑 Zinc 15 is down

In 25a7b79, Zinc 15 (https://zinc15.docking.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Zinc 15 is back up in c97de36 after 9 minutes.


text:
🛑 Zinc 15 is down

In 196d09a, Zinc 15 (https://zinc15.docking.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Zinc 15 is back up in c5430fc after 7 minutes.


text:
🛑 Chem Exper is down

In a0a986b, Chem Exper (http://www.chemexper.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Chem Exper is back up in 0207e24 after 16 minutes.


text:
🛑 Chem Exper is down

In 829dc19, Chem Exper (http://www.chemexper.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Chem Exper is back up in 2cce524 after 37 minutes.


text:
🛑 Chem Exper is down

In 4df84d7, Chem Exper (http://www.chemexper.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Chem Exper is back up in 0367813 after 7 minutes.


text:
🛑 Binding Database is down

In e984e8f, Binding Database (http://www.bindingdb.org/bind/index.jsp) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Binding Database is back up in 904a543 after 1 hour, 43 minutes.


text:
🛑 Chemical Resolver is down

In b058fba, Chemical Resolver (https://cactus.nci.nih.gov/chemical/structure) was down:

HTTP code: 500
Response time: 54 ms

Resolved: Chemical Resolver is back up in a5631a4 after 42 minutes.


text:
🛑 Chem Exper is down

In 8b140d4, Chem Exper (http://www.chemexper.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Chem Exper is back up in e51a7cd after 17 minutes.


text:
🛑 Chem Exper is down

In a040971, Chem Exper (http://www.chemexper.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Chem Exper is back up in 788843c after 7 minutes.


text:
🛑 Zinc 20 is down

In 533d9d9, Zinc 20 (https://zinc20.docking.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Zinc 20 is back up in 8b81757 after 23 minutes.


text:
🛑 Zinc 20 is down

In 419c273, Zinc 20 (https://zinc20.docking.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Zinc 20 is back up in f52daa6 after 1 hour, 49 minutes.


text:
🛑 Zinc 20 is down

In f69dc7d, Zinc 20 (https://zinc20.docking.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Zinc 20 is back up in 6302106.


text:
🛑 ITK Analysis of Large Histology Datasets is down

In 6100f59, ITK Analysis of Large Histology Datasets (http://www.na-mic.org/Wiki/index.php/ITK_Analysis_of_Large_Histology_Datasets) was down:

HTTP code: 502
Response time: 281 ms

Resolved: ITK Analysis of Large Histology Datasets is back up in 363ea40 after 18 minutes.

repo: Sulstice/Uptime-Medical-Informatics


text:
🛑 Zinc 15 is down

In 9223c1f, Zinc 15 (https://zinc15.docking.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Zinc 15 is back up in a56009d.

repo: Sulstice/uptime-zinc-db


text:
Pod name retains random segments from Deployments

We noticed that %{pod} is meant to be the "friendly" name of an app, stripping out the randomized parts added by different controllers. A pod created by a Deployment on Kubernetes@1.11 is named like this:
app-556455c97c-k8tdx

The plugin assumes the pod name has 2 random parts when the second to last part is a numeric string (is_number?(pod_parts[-2])). However, this has not been the case for several recent versions of Kubernetes.
ReplicaSets are named with a encoded version of the pod template hash, seemingly since k8s@1.8. Given our example above, there would be a ReplicaSet named app-556455c97c. Kubernetes is continuing to move forward in this direction and in a future release pod template hashes themselves will be encoded and no longer numeric.
We're still thinking about a better solution for stripping the dynamic parts with the metadata that the plugin receives but wanted to outline the problem in the mean time.

Just upgraded to 1.11 and also seeing this issue.

Sergei and I worked together on https://github.com/SumoLogic/fluentd-kubernetes-sumologic/pull/83 🙂
Kubernetes defines metadata.labels.pod-template-hash for pods so I think it would be ok to strip that out directly.

If anybody has a chance to take a look, #100 should address this issue.

fixed in v2.1.0

authors: bendrucker frankreno nmohoric rfein-hearst

repo: SumoLogic/fluentd-kubernetes-sumologic


text:
Needs standardisation

Congratulations on advancing the state of the art.
May I enquire whether you have considered submitting your algorithm to a reputable organisation for consideration as a future standard?

+1

+1

lgtm +1 (y)

authors: 190n TomCaserta numbnats woverton

repo: SunDwarf/UKSecurity


text:
add tz to inputs and make localized timestamps

since pvlib-0.3.0 naive times no longer work

seems like this is still an issue. TZ is in the data for PVPower demo, but never used except in the test

repo: SunPower/Carousel


text:
Refactor Ingestion/Processing code

Refactor the python (God) script

break it down into multiple python modules
write unit tests
Use YAML with JINJA template as substitute for construction of the JSON files (CSV to JSON conversion)

This issue will be addressed in cQube v5.0.

This is implemented

authors: RNarmatha satendrapalsingh

repo: Sunbird-cQube/community


text:
Issue #CO-760 Fw user cat issue

Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Type of change
Please choose appropriate options.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes in the below checkboxes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[ ] Ran Test A
[ ] Ran Test B

Test Configuration:

Software versions: Nodejs 8.11.2
Hardware versions:

Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

You have to update the API collection of Program-service as well for this call.
Share the documentation link once you updated. Create separate ticket and share the PR

authors: shubhambansaltarento vinukumar-vs

repo: Sunbird-coKreat/program-service


text:
docs: fix missing request in logger sample

There is ctx.method

Thanks Justin!

authors: gzuidhof justinnoel

repo: SunderJS/sunder


text:
Blocking version of the Compressor Engines

Have you considered adding the option to compress the images in a blocking fashion for times when we are already processing the image in a background thread and would prefer to not spawn a new background thread and callback?

The blocking`s callable will join the linkedBlockingQueue, also can use cachedThreadPool.

authors: Sunzxyong imminent

repo: Sunzxyong/Tiny


text:
Add serializer for custom serialization

Description

Related Issues

Checklist

[ ] Is this code covered by new or existing unit tests or integration tests?
[ ] Did you run make test successfully?
[ ] Do new classes, functions, methods and parameters all have docstrings?
[ ] Were existing docstrings updated, if necessary?
[ ] Was external documentation updated, if necessary?

Additional Notes or Comments

Codecov Report
Attention: 165 lines in your changes are missing coverage. Please review.

Comparison is base (cbe6b32) 78.22% compared to head (2d50017) 80.27%.
Report is 92 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1129      +/-   ##
==========================================
+ Coverage   78.22%   80.27%   +2.05%
==========================================
  Files         101       97       -4
  Lines        6351     6592     +241
==========================================
+ Hits         4968     5292     +324
+ Misses       1383     1300      -83

Files
Coverage Δ

superduperdb/__init__.py
100.00% <100.00%> (ø)

superduperdb/__main__.py
71.42% <100.00%> (ø)

superduperdb/base/config.py
100.00% <100.00%> (ø)

superduperdb/base/jsonable.py
80.55% <ø> (ø)

superduperdb/cli/serve.py
31.81% <ø> (ø)

superduperdb/container/component.py
82.92% <100.00%> (+2.92%)
:arrow_up:

superduperdb/container/dataset.py
87.17% <100.00%> (ø)

superduperdb/container/encoder.py
90.00% <100.00%> (+0.16%)
:arrow_up:

superduperdb/container/listener.py
83.05% <100.00%> (ø)

superduperdb/container/serializable.py
98.14% <100.00%> (+3.02%)
:arrow_up:

... and 30 more

... and 8 files with indirect coverage changes

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

repo: SuperDuperDB/superduperdb