Check for datatiers

@ericvaandering,  @ticoann,  @belforte
DBS Block/bulk insert API will automatically insert a new tier into DBS when a dataset is inserted with a new tier. This was a requirement from WM. There were two reasons for this: 1. The datatier from WMA was always valid because this was a well controlled application. 2. If DBS rejected a dataset because its datatier was not in the DB, it would fail the job and it was in  the late stage of a job process. Reprocessing the data because someone forget to pre-register a datatier was considerate a price too high to pay.
However, when we use the same API to publish user data, the datatier could be anything. These datasets might be migrated into PROD DBS later. So we have to introduce the check of datatier some where in the system to make sure the production DB is not polluted by testing data.
There are several ways we can make sure the PROD only holds valid datatiers. I would like keep the block/bulk insert API as it is because failing it in last minutes is too late, but check the datatier before giving it to DBS or during the physics  DBs to PROD migration.

Check it in WMA  before it send to DBS . @ticoann, can you check if WMA already does it? if not, would be easy for you to do it?
Can Crab check it too, @belforte ?
Check it in DBS migration server, if a datatier is not already in destination, we will fail the migration.

Seems like #3 gets us the behavior we want.
Eric

On Apr 20, 2015, at 09:46, Yuyi Guo<EMAIL_ADDRESS>wrote:
@ericvaandering https://github.com/ericvaandering, @ticoann https://github.com/ticoann, @belforte https://github.com/belforte
DBS Block/bulk insert API will automatically insert a new tier into DBS when a dataset is inserted with a new tier. This was a requirement from WM. There were two reasons for this: 1. The datatier from WMA was always valid because this was a well controlled application. 2. If DBS rejected a dataset because its datatier was not in the DB, it would fail the job and it was in the late stage of a job process. Reprocessing the data because someone forget to pre-register a datatier was considerate a price too high to pay.
However, when we use the same API to publish user data, the datatier could be anything. These datasets might be migrated into PROD DBS later. So we have to introduce the check of datatier some where in the system to make sure the production DB is not polluted by testing data.
There are several ways we can make sure the PROD only holds valid datatiers. I would like keep the block/bulk insert API as it is because failing it in last minutes is too late, but check the datatier before giving it to DBS or during the physics DBs to PROD migration.
Check it in WMA before it send to DBS . @ticoann https://github.com/ticoann, can you check if WMA already does it? if not, would be easy for you to do it?
Can Crab check it too, @belforte https://github.com/belforte ?
Check it in DBS migration server, if a datatier is not already in destination, we will fail the migration.
—
Reply to this email directly or view it on GitHub https://github.com/dmwm/DBS/issues/466.

Eric W. Vaandering
Computing Physics Developer
CMS Computing Development Lead
Scientific Computing Division
Fermi National Accelerator Laboratory
630 962 7260 office
www.fnal.gov http://www.fnal.gov/

Checked with Seangchan. T0 controls what tiers to put in the DBS. it is well managed on the T0 side. There are eight tiers allowed and they registered to DBS already. Should we allow any new tiers from user data? Should user data tiers be predefined too?

Hi Yuyi,

Check it in WMA before it send to DBS . @ticoann, can you check if WMA already does it? if not, would be easy for you to do it?

Actually we don't really check the tier whether that is correct tier or not. Tier0  tightly control (hard coded) which tier is allowed. But WMAgent not validating whether is correct tier or not. We can add that in the validation when request is created. The only concern is when new the new tier is introduced, I think we need to able to handle that in short notice. (not waiting the cms deployment schedule)

Tier0 cannot determine all the Tiers. It certainly doesn’t do anything with “SIM” in it nor, I assume, mini AOD tiers.

On Apr 20, 2015, at 10:31, Yuyi Guo<EMAIL_ADDRESS>wrote:
Checked with Seangchan. T0 controls what tiers to put in the DBS. it is well managed on the T0 side. There are eight tiers allowed and they registered to DBS already. Should we allow any new tiers from user data? Should user data tiers be predefined too?
—
Reply to this email directly or view it on GitHub https://github.com/dmwm/DBS/issues/466#issuecomment-94484498.

Eric W. Vaandering
Computing Physics Developer
CMS Computing Development Lead
Scientific Computing Division
Fermi National Accelerator Laboratory
630 962 7260 office
www.fnal.gov http://www.fnal.gov/

I like that users can not write to PROD, but in the end we can not think of "phys03" as a junkyard. Remember that most migrations go the other way, in the end all useful data is listed in phys03.
Nor is a good reason to get an oddly named tier in PROD due to a typo in a workflow !
I can surely understand the history of how we go here, but maybe we can still improve.
Best solution IMHO is:

we list valid Tiers (in Lexicon.py)
WMA, ReqMgr, Prep, CRAB ...all that check and validate that EARLY, do not rely on DBS server to barf at the end of the workflow
So I will do that for CRAB. And if production ever does the same, then we will be able to put the check in DBS server as well and make sure database stays clean.

Stefano

OK, new tiers created after T0.
Seangchan, adding a new tier does not CMSWEB release. Just a sql command.

we can think of moving the list of valid tiers off the code.
On 04/20/2015 05:32 PM, ticoann wrote:

The only concern is when new the new tier is introduced, I think we need
to able to handle that in short notice. (not waiting the cms deployment
schedule)

I agree that we cannot treat "phys03" as a junkyard.
I my think that valid tiers stays in the DB instead of code. There is DBS API to list all the tiers. Can WMA and Crab call this API during the time PREPPARE for the bulk/block data?
If indeed a new data tier is needed, I can just insert it into the DB without waiting for any code update.

Yes, we can use the service DBS (or something else) provide for tier validation.

Sounds good. Anyhow it is not urgent, currently CRAB forces tier = USER, we will add NOTEDM  and will see in time about publication with user script.
Passage of datasets from phys03 to PROD can't be done by user anyhow.
On Apr 20, 2015 5:54 PM, Yuyi Guo<EMAIL_ADDRESS>wrote:I agree that we cannot treat "phys03" as a junkyard.
I my think that valid tiers stays in the DB instead of code. There is DBS API to list all the tiers. Can WMA and Crab call this API during the time PREPPARE for the bulk/block data?
If indeed a new data tier is needed, I can just insert it into the DB without waiting for any code update.
—Reply to this email directly or view it on GitHub.

@belforte , is crab ready for inserting tier into DBS if new tier appears before sending data to DBS for block/bulk insertion?
Talked with @ticoann  yesterday, WMA is ready since there is no new data tiers needed. I think WMA still need to check.
If crab is ready I am going to remove automatic tier insertion in block/bulk insert API as well as in the migration in June release. Please let me ASAP.

so far CRAB2+3 only writes with tier=USER
We never create tiers !
any plan for other tier name there is only chat.
On 05/15/2015 08:11 PM, Yuyi Guo wrote:

@belforte https://github.com/belforte , is crab ready for inserting tier into DBS if new tier
appears before sending data to DBS for block/bulk insertion?
Talked with @ticoann https://github.com/ticoann yesterday, WMA is ready since there is no new data
tiers needed. I think WMA still need to check.
If crab is ready I am going to remove automatic tier insertion in block/bulk insert API as well as
in the migration in June release. Please let me ASAP.
—
Reply to this email directly or view it on GitHub
https://github.com/dmwm/DBS/issues/466#issuecomment-102475405.

--
Stefano Belforte - I.N.F.N.     tel   : +39<PHONE_NUMBER> (fax: 375-6258)
Area di Ricerca - Padriciano 99 tel mobile: +39<PHONE_NUMBER>
34012 TRIESTE TS  - Italy       AIM: stefanobelforte

Ok. I am going to change DBS since no one is going to insert new tiers in near future. But I still recommend  that both crab and WMA check the tier in the code . If you have new tiers, please let me know and I will insert them. Any one with insert privilege can insert them too.

Dinitely. You can be sure that CRAB will be very careful in this. Thanks
On 05/15/2015 08:24 PM, Yuyi Guo wrote:

Ok. I am going to change DBS since no one is going to insert new tiers in near future. But I still
recommend that both crab and WMA check the tier in the code . If you have new tiers, please let me
know and I will insert them. Any one with insert privilege can insert them too.

Done with coding API and unit tests

Done.


[#14 fix][v0.2.8] Claude endpoint update!

CHANGELOG

Updated Claude endpoint for send_message, fixes #14
Request payload and response parsing updated accordingly.

Waiting for confirmations in order to release the v0.2.8 version!

it works smoothly, wonderful~ :thumbsup:


using assert function to throw error

So lovely. Could you please rebase + I'll merge this in?

rebased

So fresh and clean :+1:


Rename default contexts on Bungee/Velocity

I have suggested it before, but never in it's own issue.
My proposal is as follows:

What's currently the server context should be renamed to the proxy context.
What's currently the world context should be renamed to the server context.

This makes per server nodes consistent with the bungee.
Additionally the backend servers should get the context proxy=none, so you can still have nodes that target individual servers (either just the bungee or just the backend server).
This is especially useful for per server groups and their respective prefixes.

In addition I would suggest to also change server: in the config.yml of LPB to proxy so that people won't get confused.
https://github.com/lucko/LuckPerms/blob/c86f6c0f368610152112ece73c898aa0954cfcc9/bungee/src/main/resources/config.yml#L29-L34

I was implying that but that’s a fair point to point out.

I've had an idea on how this could be implemented and minimize impact when updating:
Add a config setting that reenables the old (insane) behavior. In the default config it is set to false. But if the setting is missing it defaults to true.

Bumping it because I've yet seen another case where this causes massive issues.

Yeah I support this change.

It's pretty difficult to explain why it happens to some people. Sure, we can just tell them to set the prefixes again with a world context to cover the proxy but some people have a lot of groups and we typically get a lot of resistance when suggesting this solution.
Please consider adding proxy context soon 🙏

It's not just difficult to explain the why but it's even more difficult to suggest somewhat decent solutions. Even helper groups that inherit the actual group twice, once with the per server context and once with the per world context, always fall short somewhere.
It always boils down to being a lot of work that really isn't necessary or the setup being very stiff. Often both.
I know you dread of making that change, but it needs to happen. The sooner, the better.
And frankly I don't know what concerns are left, but you major concern regarding upgrading has been addressed. So if there's anything else, feel free to start a discussion. We're always happy to find solutions to the problems there are.

I'd like to keep the server context as it is, but rename world to connected-server on Bungee/Velocity.
I'm open to other names, ideally something shorter. backend-server is another consideration.
Currently, the server context is a way of isolating permissions to a specific LP instance, whether that's a Minecraft server or a proxy server doesn't matter - it's still a server. I don't think it's necessary to change. (unless anyone has anything to say to convince me otherwise)

This is especially useful for per server groups and their respective prefixes.

I guess this is a fair point I overlooked, hmm

One point has been mentioned several times here, which is, that it helps to distinguish context more easly, especially when using LP on both proxy and server.
Most people won't think of "server" when they want to set a perm, group, ... on a proxy-level. A server for them is often the backend one and it can easly get confusing with when you want to set permissions for the Spigot Server only and then one for the proxy only...
2 different instances of LP both using the server context can become really confusing as you can't quite know which one now is about the proxy and which about the actual server.

Currently, the server context is a way of isolating permissions to a specific LP instance

That is correct and that is exactly the issue here.
Contexts are used to narrow then the when and where a permission applies. The LP instances themselves are utterly useless in operation. While it makes sense being able to differentiate them (ideally with a dedicated context) it's not something the majority of users care about. They care about the when and where a permission or group applies.
Now that means to them they don't care how the backend servers are essentially worlds to the proxy. All they care is that they want to give groups and permissions, when a player is on a certain backend server. They care what server the player plays on, not which LP instance to target.
A fairly common use case is to have per server groups. Now while typically only the backend servers matter it's not unheard off that permissions and groups on the bungee should match the ones on the backend server.
Currently the only way to achieve this somewhat elegantly is by using a helper group. As mentioned that quickly runs into issue when there are many groups and multiple servers. The operations of the plugin become very complicated and it can quickly mean that only one person is able to properly set per server ranks. A very common complaint from server admins that did actually understand why proposed setup is that they don't know how to make sure their staff knows how to properly set per server ranks. And frankly most people had no idea what to do. As they seem to be not able to understand that LP refers to instances and not places.
Again I do understand your initial intention behind adding those contexts in the first place. Being able to target a specific LP instance makes a lot of sense on the surface. But it's not what people use this feature for. They couldn't care less about the instances. They only care about the wheres and whens of a player. Most commonly the server they currently play on.
So to summarize I propose:

Make sure the server context always refers to the backend server the player is on. For the backend server that naturally is equivalent with the LP instance
Add the proxy context to be able to differentiate the different proxies. It might make sense adding proxy=none to the backend server but I would be against that.
Also change the server setting in the proxy config to proxy.
Add a config option that reenables the current behavior. If it's missing it defaults to true, but in the default config it's false. This means that for servers updating nothing changes but new servers will use the new and improved contexts
Add a context to identify the LP instance. Like instance. It would default to the same name as either the server or proxy setting in the respective LP config. That way you have the best of both worlds, should you ever actually need to target a specific LP instance instead of a backend server. Maybe even rename the server config to instance-name in the LP config. And the server and proxy contexts get adjusted accordingly.
I personally am against this context but could definately understand an argument being made for it.

And if you are still not convinced how cumbersome the current system is, just setup a bungee network with 3 backend servers and 10 groups. Make sure you can add any group to a player that only applies to any one specific player with one command. For both the backend server and the bungee. Additionally the actual permission and prefix holding groups cannot have permissions with contexts. You can verify everything working by making sure the /lp user <user> info and the `/lpb user  info`` always show the same prefixes.

Bumping this again.

Bumping this again.

There's no need to bump, I work on suggestions as and when I have time.
This is a complex problem with a potentially large impact on users setups if implemented incorrectly. It is also not something I consider to be urgent, the current system (whilst I admit is not perfect) is at least functional at the moment (and has been for the past 3/4 years...)
As well as the complexity of the code change, it also has knock-on effects on documentation and other behaviours (e.g. the include-global setting) which need to be considered and worked on.

There's no need to bump, I work on suggestions as and when I have time.
This is a complex problem with a potentially large impact on users setups if implemented incorrectly. It is also not something I consider to be urgent, the current system (whilst I admit is not perfect) is at least functional at the moment (and has been for the past 3/4 years...)
As well as the complexity of the code change, it also has knock-on effects on documentation and other behaviours (e.g. the include-global setting) which need to be considered and worked on.

I'd like to address the one issue that has been brought up many many times, which is essentially that implementing this would be a breaking change.
Many have argued that a change in storage would be required, or that it is impossible to implement without breaking older stuff etc.
My two cents to this are as follows:

Change of storage format is not required, as a new database field for the proxy context is not necessary due to the rarity of it being used. That context should just go to where the other ones are going.
I see two ways of how to deal with introducing breaking changes:

Just break it. Jump a major version, have a banner up for like 2 years and call it a day. People running into this issue are typically fairly adept and clearly have decently deep understanding of what's going on
My preferred option would be to just add a config setting. When migrating the config, set it to false and when generating a new config set it to true (or vice versa, depending on which way the config works). This even allows people to opt in or opt out, depending on their needs.


Document myos.sh (Comments)

As promised, this is my pull request to make the myos script easier to understand.

You're welcome


Deploy CA before workers are ready

How to categorize this PR?

/area control-plane
/area ops-productivity
/kind enhancement
What this PR does / why we need it:
As discussed in issue #7057, this PR will enhance the current shoot reconciliation flow to deploy Cluster Autoscaler before the workers become ready. Here workers become ready means that all the machine deployments in the cluster should have the desired number of machines in the Running state. This PR will deploy CA after the worker resource is updated (and possibly before the machine deployments are updated/deployed).
Which issue(s) this PR fixes:
Fixes #7057
Special notes for your reviewer:
This solution was tested using the Hard Way setup of gardener using an AWS shoot(k8s version 1.23.17) on the dev landscape. The following scenarios were tested:-

Creation of a Cluster
Update the existing worker to increase its min and max limits
Addition of a worker to get schedule the existing un-schedulable pods
To move a workload from one worker to another by changing one worker to min:0 and max:0 and increasing the min and max limits for another.
Rolling update scenario by changing the machine image in one of the workers
Hibernation/waking up of the cluster
Deletion of the cluster

A separate test was done by introducing a 5 min delay in worker reconciliation to see what happens if CA is deployed before a worker is reconciled and MD is created/updated. The following scenario was tested:-

Addition of a worker to get schedule the existing un-schedulable pods

Things to keep in mind about CA behaviour:-

CA does nothing productive until all the node groups(machine deployments) specified in the --nodes flag is present in the cluster. It simply keeps on giving error logs which say, machine deployment [xyz] not found.
If a node group has min > 0 and does not have at least 1 node in the cluster, then it will not be considered for scale-up by CA, and there will not be any backoff for this node group. This is because it will not be able to get the Readiness of the node group, and without that, it will not be considered for scale-up. The calculation of the number of nodes required to be in the Ready state for the node group to be considered for scale-up is done here.

Release note:

Gardener now deploys the [Cluster-Autoscaler](https://github.com/gardener/autoscaler) earlier in the shoot reconciliation flow without checking if the workers are Ready

/assign

/hold


Including Styling to the page

Including styling on the website will create a positive impression on users, so I would like to add CSS to enhance its appearance.

Please assign me this issue.


feat: port Algebra.AddTorsor

There are some dangerous instances here marked with nolint dangerous_instance in Lean3 that cause problems

If it's the add_torsor.nonempty dangerous instance that causes problems, then it might be worth doing a preliminary refactor in mathlib3: as suggested in https://leanprover.zulipchat.com/#narrow/stream/116395-maths/topic/Empty.20torsors allow an add_torsor to be empty and instead add nonempty hypotheses at only those use sites that need them.

If it's the add_torsor.nonempty dangerous instance that causes problems, then it might be worth doing a preliminary refactor in mathlib3: as suggested in https://leanprover.zulipchat.com/#narrow/stream/116395-maths/topic/Empty.20torsors allow an add_torsor to be empty and instead add nonempty hypotheses at only those use sites that need them.

I think it's probably the toVSub one sadly.

I just pushed some proofs which allow the instance to compile, though they are a lot uglier than what lean3 used to have. This is almost certainly sweeping a deeper problem under the rug, since the proofs feel unnatural and there is probably something messy going on with instance synthesization, but perhaps this can also help  someone to understand what the problem is.

Thanks :tada:
If CI passes, please remove the label awaiting-CI and merge this yourself, by adding a comment bors r+.
bors d+

Thanks :tada:
bors merge


Zoom speed

Hi!
I use OS X 10.11.6, Chrome 51. And I have some troubles with different zooming gestures. When I zoom image using swipe with two fingers (like mousewheel event) it works fine, but when I zoom using pinch gesture it zooms very fast and it's inconvenient. Check out the gif below. First I use swipe and then pinch.

I'll try to dig into the pinch zooming logic when I get time, feel free to look into it and submit a PR.


Generate tiles from 5 ROIs from Bangalore for testing

[x] Create test_imageTiling_Bangalore script for creating tiles with different sizes per ROI

[ ] Generate 80% "pure" tiles for Slum, Built-up and Nonbuilt-Up for the following tile sizes:
pxl: 67, 134, 200, 268, 334, 400
m: 10, 20, 30, 40, 50, 60

Creating tile sets for ROI:ROI1

> Tiling for dataset 1:px67m10...
> There are 699 number of images for class Slum.
> There are 12673 number of images for class BuiltUp.
> There are 3576 number of images for class NonBuiltUp.
> There are 8782 number of images for class Mixed, but they are not saved!.
> Done for dataset: 1!
> ---------------------------------
> Tiling for dataset 2:px134m20...
> There are 119 number of images for class Slum.
> There are 2427 number of images for class BuiltUp.
> There are 530 number of images for class NonBuiltUp.
> There are 3238 number of images for class Mixed, but they are not saved!.
> Done for dataset: 2!
> ---------------------------------
> Tiling for dataset 3:px200m30...
> There are 39 number of images for class Slum.
> There are 897 number of images for class BuiltUp.
> There are 164 number of images for class NonBuiltUp.
> There are 1760 number of images for class Mixed, but they are not saved!.
> Done for dataset: 3!
> ---------------------------------
> Tiling for dataset 4:px268m40...
> There are 16 number of images for class Slum.
> There are 430 number of images for class BuiltUp.
> There are 63 number of images for class NonBuiltUp.
> There are 1090 number of images for class Mixed, but they are not saved!.
> Done for dataset: 4!
> ---------------------------------
> Tiling for dataset 5:px334m50...
> There are 9 number of images for class Slum.
> There are 236 number of images for class BuiltUp.
> There are 27 number of images for class NonBuiltUp.
> There are 751 number of images for class Mixed, but they are not saved!.
> Done for dataset: 5!
> ---------------------------------
> Done for ROI:ROI1!
> +++++++++++++++++++++++++++++++++++++++
> Creating tile sets for ROI:ROI2
> Tiling for dataset 1:px67m10...
> There are 665 number of images for class Slum.
> There are 8187 number of images for class BuiltUp.
> There are 3141 number of images for class NonBuiltUp.
> There are 7335 number of images for class Mixed, but they are not saved!.
> Done for dataset: 1!
> ---------------------------------
> Tiling for dataset 2:px134m20...
> There are 104 number of images for class Slum.
> There are 1483 number of images for class BuiltUp.
> There are 424 number of images for class NonBuiltUp.
> There are 2714 number of images for class Mixed, but they are not saved!.
> Done for dataset: 2!
> ---------------------------------
> Tiling for dataset 3:px200m30...
> There are 34 number of images for class Slum.
> There are 516 number of images for class BuiltUp.
> There are 102 number of images for class NonBuiltUp.
> There are 1498 number of images for class Mixed, but they are not saved!.
> Done for dataset: 3!
> ---------------------------------
> Tiling for dataset 4:px268m40...
> There are 13 number of images for class Slum.
> There are 231 number of images for class BuiltUp.
> There are 33 number of images for class NonBuiltUp.
> There are 939 number of images for class Mixed, but they are not saved!.
> Done for dataset: 4!
> ---------------------------------
> Tiling for dataset 5:px334m50...
> There are 3 number of images for class Slum.
> There are 109 number of images for class BuiltUp.
> There are 13 number of images for class NonBuiltUp.
> There are 655 number of images for class Mixed, but they are not saved!.
> Done for dataset: 5!
> ---------------------------------
> Done for ROI:ROI2!
> +++++++++++++++++++++++++++++++++++++++
> Creating tile sets for ROI:ROI3
> Tiling for dataset 1:px67m10...
> There are 342 number of images for class Slum.
> There are 15197 number of images for class BuiltUp.
> There are 15041 number of images for class NonBuiltUp.
> There are 18380 number of images for class Mixed, but they are not saved!.
> Done for dataset: 1!
> ---------------------------------
> Tiling for dataset 2:px134m20...
> There are 53 number of images for class Slum.
> There are 2421 number of images for class BuiltUp.
> There are 2450 number of images for class NonBuiltUp.
> There are 7002 number of images for class Mixed, but they are not saved!.
> Done for dataset: 2!
> ---------------------------------
> Tiling for dataset 3:px200m30...
> There are 16 number of images for class Slum.
> There are 801 number of images for class BuiltUp.
> There are 784 number of images for class NonBuiltUp.
> There are 3799 number of images for class Mixed, but they are not saved!.
> Done for dataset: 3!
> ---------------------------------
> Tiling for dataset 4:px268m40...
> There are 6 number of images for class Slum.
> There are 353 number of images for class BuiltUp.
> There are 312 number of images for class NonBuiltUp.
> There are 2344 number of images for class Mixed, but they are not saved!.
> Done for dataset: 4!
> ---------------------------------
> Tiling for dataset 5:px334m50...
> There are 2 number of images for class Slum.
> There are 186 number of images for class BuiltUp.
> There are 162 number of images for class NonBuiltUp.
> There are 1594 number of images for class Mixed, but they are not saved!.
> Done for dataset: 5!
> ---------------------------------
> Done for ROI:ROI3!
> +++++++++++++++++++++++++++++++++++++++
> Creating tile sets for ROI:ROI4
> Tiling for dataset 1:px67m10...
> There are 523 number of images for class Slum.
> There are 34763 number of images for class BuiltUp.
> There are 19967 number of images for class NonBuiltUp.
> There are 36857 number of images for class Mixed, but they are not saved!.
> Done for dataset: 1!
> ---------------------------------
> Tiling for dataset 2:px134m20...
> There are 60 number of images for class Slum.
> There are 5607 number of images for class BuiltUp.
> There are 3531 number of images for class NonBuiltUp.
> There are 13152 number of images for class Mixed, but they are not saved!.
> Done for dataset: 2!
> ---------------------------------
> Tiling for dataset 3:px200m30...
> There are 12 number of images for class Slum.
> There are 1813 number of images for class BuiltUp.
> There are 1317 number of images for class NonBuiltUp.
> There are 6958 number of images for class Mixed, but they are not saved!.
> Done for dataset: 3!
> ---------------------------------
> Tiling for dataset 4:px268m40...
> There are 3 number of images for class Slum.
> There are 739 number of images for class BuiltUp.
> There are 623 number of images for class NonBuiltUp.
> There are 4260 number of images for class Mixed, but they are not saved!.
> Done for dataset: 4!
> ---------------------------------
> Tiling for dataset 5:px334m50...
> There are 1 number of images for class Slum.
> There are 391 number of images for class BuiltUp.
> There are 377 number of images for class NonBuiltUp.
> There are 2891 number of images for class Mixed, but they are not saved!.
> Done for dataset: 5!
> ---------------------------------
> Done for ROI:ROI4!
> +++++++++++++++++++++++++++++++++++++++
> Creating tile sets for ROI:ROI5
> Tiling for dataset 1:px67m10...
> There are 488 number of images for class Slum.
> There are 20731 number of images for class BuiltUp.
> There are 6604 number of images for class NonBuiltUp.
> There are 10956 number of images for class Mixed, but they are not saved!.
> Done for dataset: 1!
> ---------------------------------
> Tiling for dataset 2:px134m20...
> There are 70 number of images for class Slum.
> There are 4309 number of images for class BuiltUp.
> There are 1149 number of images for class NonBuiltUp.
> There are 3988 number of images for class Mixed, but they are not saved!.
> Done for dataset: 2!
> ---------------------------------
> Tiling for dataset 3:px200m30...
> There are 16 number of images for class Slum.
> There are 1730 number of images for class BuiltUp.
> There are 402 number of images for class NonBuiltUp.
> There are 2116 number of images for class Mixed, but they are not saved!.
> Done for dataset: 3!
> ---------------------------------
> Tiling for dataset 4:px268m40...
> There are 6 number of images for class Slum.
> There are 891 number of images for class BuiltUp.
> There are 182 number of images for class NonBuiltUp.
> There are 1300 number of images for class Mixed, but they are not saved!.
> Done for dataset: 4!
> ---------------------------------
> Tiling for dataset 5:px334m50...
> There are 1 number of images for class Slum.
> There are 543 number of images for class BuiltUp.
> There are 97 number of images for class NonBuiltUp.
> There are 878 number of images for class Mixed, but they are not saved!.
> Done for dataset: 5!
> ---------------------------------
> Done for ROI:ROI5!
> +++++++++++++++++++++++++++++++++++++++
> DONE!

Creating tile sets for ROI:ROI1
Tiling for dataset 1:px67m10...
There are 761 number of images for class Slum.
There are 14300 number of images for class BuiltUp.
There are 4311 number of images for class NonBuiltUp.
There are 6358 number of images for class Mixed, but they are not saved!.
Done for dataset: 1!
---------------------------------
Tiling for dataset 2:px134m20...
There are 147 number of images for class Slum.
There are 3026 number of images for class BuiltUp.
There are 705 number of images for class NonBuiltUp.
There are 2436 number of images for class Mixed, but they are not saved!.
Done for dataset: 2!
---------------------------------
Tiling for dataset 3:px200m30...
There are 50 number of images for class Slum.
There are 1251 number of images for class BuiltUp.
There are 237 number of images for class NonBuiltUp.
There are 1322 number of images for class Mixed, but they are not saved!.
Done for dataset: 3!
---------------------------------
Tiling for dataset 4:px268m40...
There are 19 number of images for class Slum.
There are 667 number of images for class BuiltUp.
There are 101 number of images for class NonBuiltUp.
There are 812 number of images for class Mixed, but they are not saved!.
Done for dataset: 4!
---------------------------------
Tiling for dataset 5:px334m50...
There are 11 number of images for class Slum.
There are 405 number of images for class BuiltUp.
There are 57 number of images for class NonBuiltUp.
There are 550 number of images for class Mixed, but they are not saved!.
Done for dataset: 5!
---------------------------------
Tiling for dataset 6:px400m60...
There are 2 number of images for class Slum.
There are 285 number of images for class BuiltUp.
There are 32 number of images for class NonBuiltUp.
There are 409 number of images for class Mixed, but they are not saved!.
Done for dataset: 6!
---------------------------------
Done for ROI:ROI1!
+++++++++++++++++++++++++++++++++++++++
Creating tile sets for ROI:ROI2
Tiling for dataset 1:px67m10...
There are 729 number of images for class Slum.
There are 9349 number of images for class BuiltUp.
There are 3877 number of images for class NonBuiltUp.
There are 5373 number of images for class Mixed, but they are not saved!.
Done for dataset: 1!
---------------------------------
Tiling for dataset 2:px134m20...
There are 132 number of images for class Slum.
There are 1892 number of images for class BuiltUp.
There are 607 number of images for class NonBuiltUp.
There are 2094 number of images for class Mixed, but they are not saved!.
Done for dataset: 2!
---------------------------------
Tiling for dataset 3:px200m30...
There are 45 number of images for class Slum.
There are 751 number of images for class BuiltUp.
There are 180 number of images for class NonBuiltUp.
There are 1174 number of images for class Mixed, but they are not saved!.
Done for dataset: 3!
---------------------------------
Tiling for dataset 4:px268m40...
There are 19 number of images for class Slum.
There are 369 number of images for class BuiltUp.
There are 83 number of images for class NonBuiltUp.
There are 745 number of images for class Mixed, but they are not saved!.
Done for dataset: 4!
---------------------------------
Tiling for dataset 5:px334m50...
There are 10 number of images for class Slum.
There are 215 number of images for class BuiltUp.
There are 40 number of images for class NonBuiltUp.
There are 515 number of images for class Mixed, but they are not saved!.
Done for dataset: 5!
---------------------------------
Tiling for dataset 6:px400m60...
There are 6 number of images for class Slum.
There are 136 number of images for class BuiltUp.
There are 25 number of images for class NonBuiltUp.
There are 383 number of images for class Mixed, but they are not saved!.
Done for dataset: 6!
---------------------------------
Done for ROI:ROI2!
+++++++++++++++++++++++++++++++++++++++
Creating tile sets for ROI:ROI3
Tiling for dataset 1:px67m10...
There are 387 number of images for class Slum.
There are 17806 number of images for class BuiltUp.
There are 17270 number of images for class NonBuiltUp.
There are 13497 number of images for class Mixed, but they are not saved!.
Done for dataset: 1!
---------------------------------
Tiling for dataset 2:px134m20...
There are 58 number of images for class Slum.
There are 3282 number of images for class BuiltUp.
There are 3200 number of images for class NonBuiltUp.
There are 5386 number of images for class Mixed, but they are not saved!.
Done for dataset: 2!
---------------------------------
Tiling for dataset 3:px200m30...
There are 20 number of images for class Slum.
There are 1200 number of images for class BuiltUp.
There are 1171 number of images for class NonBuiltUp.
There are 3009 number of images for class Mixed, but they are not saved!.
Done for dataset: 3!
---------------------------------
Tiling for dataset 4:px268m40...
There are 6 number of images for class Slum.
There are 566 number of images for class BuiltUp.
There are 551 number of images for class NonBuiltUp.
There are 1892 number of images for class Mixed, but they are not saved!.
Done for dataset: 4!
---------------------------------
Tiling for dataset 5:px334m50...
There are 3 number of images for class Slum.
There are 319 number of images for class BuiltUp.
There are 302 number of images for class NonBuiltUp.
There are 1320 number of images for class Mixed, but they are not saved!.
Done for dataset: 5!
---------------------------------
Tiling for dataset 6:px400m60...
There are 2 number of images for class Slum.
There are 208 number of images for class BuiltUp.
There are 191 number of images for class NonBuiltUp.
There are 949 number of images for class Mixed, but they are not saved!.
Done for dataset: 6!
---------------------------------
Done for ROI:ROI3!
+++++++++++++++++++++++++++++++++++++++
Creating tile sets for ROI:ROI4
Tiling for dataset 1:px67m10...
There are 614 number of images for class Slum.
There are 41938 number of images for class BuiltUp.
There are 22635 number of images for class NonBuiltUp.
There are 26923 number of images for class Mixed, but they are not saved!.
Done for dataset: 1!
---------------------------------
Tiling for dataset 2:px134m20...
There are 88 number of images for class Slum.
There are 8716 number of images for class BuiltUp.
There are 4313 number of images for class NonBuiltUp.
There are 9233 number of images for class Mixed, but they are not saved!.
Done for dataset: 2!
---------------------------------
Tiling for dataset 3:px200m30...
There are 21 number of images for class Slum.
There are 3667 number of images for class BuiltUp.
There are 1685 number of images for class NonBuiltUp.
There are 4727 number of images for class Mixed, but they are not saved!.
Done for dataset: 3!
---------------------------------
Tiling for dataset 4:px268m40...
There are 6 number of images for class Slum.
There are 1952 number of images for class BuiltUp.
There are 863 number of images for class NonBuiltUp.
There are 2804 number of images for class Mixed, but they are not saved!.
Done for dataset: 4!
---------------------------------
Tiling for dataset 5:px334m50...
There are 2 number of images for class Slum.
There are 1187 number of images for class BuiltUp.
There are 545 number of images for class NonBuiltUp.
There are 1926 number of images for class Mixed, but they are not saved!.
Done for dataset: 5!
---------------------------------
Tiling for dataset 6:px400m60...
There are 0 number of images for class Slum.
There are 774 number of images for class BuiltUp.
There are 370 number of images for class NonBuiltUp.
There are 1406 number of images for class Mixed, but they are not saved!.
Done for dataset: 6!
---------------------------------
Done for ROI:ROI4!
+++++++++++++++++++++++++++++++++++++++
Creating tile sets for ROI:ROI5
Tiling for dataset 1:px67m10...
There are 539 number of images for class Slum.
There are 23134 number of images for class BuiltUp.
There are 7499 number of images for class NonBuiltUp.
There are 7607 number of images for class Mixed, but they are not saved!.
Done for dataset: 1!
---------------------------------
Tiling for dataset 2:px134m20...
There are 100 number of images for class Slum.
There are 5284 number of images for class BuiltUp.
There are 1427 number of images for class NonBuiltUp.
There are 2705 number of images for class Mixed, but they are not saved!.
Done for dataset: 2!
---------------------------------
Tiling for dataset 3:px200m30...
There are 28 number of images for class Slum.
There are 2282 number of images for class BuiltUp.
There are 534 number of images for class NonBuiltUp.
There are 1420 number of images for class Mixed, but they are not saved!.
Done for dataset: 3!
---------------------------------
Tiling for dataset 4:px268m40...
There are 10 number of images for class Slum.
There are 1251 number of images for class BuiltUp.
There are 250 number of images for class NonBuiltUp.
There are 868 number of images for class Mixed, but they are not saved!.
Done for dataset: 4!
---------------------------------
Tiling for dataset 5:px334m50...
There are 4 number of images for class Slum.
There are 776 number of images for class BuiltUp.
There are 144 number of images for class NonBuiltUp.
There are 595 number of images for class Mixed, but they are not saved!.
Done for dataset: 5!
---------------------------------
Tiling for dataset 6:px400m60...
There are 1 number of images for class Slum.
There are 534 number of images for class BuiltUp.
There are 85 number of images for class NonBuiltUp.
There are 446 number of images for class Mixed, but they are not saved!.
Done for dataset: 6!
---------------------------------
Done for ROI:ROI5!
+++++++++++++++++++++++++++++++++++++++


Training GraphSpace with large data

Dear all
I have 400K customers including relationship data. We're analysing them by the GraphSpace model.
I created a file graph-relationship including ~380M relationships (size 18GB) with format:
user_1 friend __label__user2
...
I got an issue over memory. I using CPU 16 cores with 64GB RAM, but it's not enough memory and the GraphSpace was killed.
Anyone have any solution for my problem?
How to optimize my data to decrease Hardware requirements?
Which are server requirement enough for 380M data (or more..)? How to calculate?

@tuphamngoc Hi, it sounds like your data is too big to be loaded in to memory. You can roughly calculate the usage by
O(num_of_relations * size_of(int32 + float)) + O(size_of(float) * num_of(users + label_users) * dimension)
What are the number of unique users and labels in your data? What is the dimension you're using?
One thing we can do is to write an another data loader that does not load the data into memory.

Similar issue: https://github.com/facebookresearch/StarSpace/issues/137
Closing this one now.


Fix bug in DMRG-X with QNs

Fixes #45.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (161209a) 86.50% compared to head (5e2ffa2) 86.50%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main      #61   +/-   ##
=======================================
  Coverage   86.50%   86.50%
=======================================
  Files          17       17
  Lines         600      600
=======================================
  Hits          519      519
  Misses         81       81

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


Add rehydration to example/aphrodite

Enhanced example with style rehydration, and additional attribute in the style tag.
This prevents duplication of tags, or styles within the tags.
Also added comments to explain each piece.

@Grokling  test failed. please check.

@aranajhonny All passing now - sorry for the messiness!

@Grokling could you check the yarn.lock. It includes aphrodite related packages, those shouldn't be there 😄

@timneutkens said:

@grokling ahh I think the github merge resolver got to me
Let me fix the merge conflict and I'll merge

I've commited a merge with master, so yarn.lock should not have any conflicts.


Crashes with odd image height in Stereo 3D

I have a bunch of files shot with a DSLR on a slider and converted to 2k CineForm 3D files. Due to the sensor size the 2k frames are 2048x1363. So this is an odd image height (not a multiple of two).
The decoder returns a Stereo 3D image when set to VIDEO_SELECT_BOTH_EYES and STEREO3D_TYPE_DEFAULT that is 2048x2728 (i.e. not 2048x2726 as one would expect) and has a black line (single pixel height) below each of the views/eyes.
Switching the Stereo 3D types to STEREO3D_TYPE_STACKED or STEREO3D_TYPE_FIELDS crashes the decoder. All other types work correctly (as long as I make the output buffer large enough to hold an extra scanline).

Does everything work if you crop the source to 2048x1362?  Formats like  STEREO3D_TYPE_STACKED or STEREO3D_TYPE_FIELDS can't work with odd sizes. STACKED would present both frames in under-over scaled to fit the original frame size, which would force left and right views to be none integer sizes. Interlaced would have left and right with differing numbers of scan lines.

Files with even number of scanlines (per view/eye) work fine. I do understand that some of the modes don't really make sense with odd frame heights. But then they should not crash and those that do work and do make sense (like the "normal" top/bottom aka. STEREO3D_TYPE_DEFAULT) should just work normally without any extra black scanlines between the two eyes.
I can provide test files, if you want to give it a try yourself.

Also the code is now here for others to help solve.  Best solution would be to automatically crop incompatible input so that there is no ambiguity over what will work with a encoded file.

Yes, I'm slowly working my way though the code, trying to fix things... But I don't like the idea of "just don't encode frames with an odd height". The encoder should either refuse to do so or the decoder should handle it correctly (or give an error, but NOT crash).

After more testing I found the following: The black scanline does not just affect Stereo 3D files but also normal files if they have an odd height. Just that with Stereo 3D in top/bottom view the black scanline between the views is easier to spot.
What is actually happening is that for images with an odd image height the last scanline gets displayed black. This only happens when the TAG_DECODE_CURVE metadata is set to the same value as the encoding curve specified in the file (i.e. no curve conversion required).
My sample file has CFHD_CURVE_GAMMA_2pt2 set as encode and decode curve. When I request CFHD_CURVE_GAMMA_2pt2 as decode curve the last scanline is black. Then I tried switching the decode curve to CFHD_CURVE_LOGC. Now the last scanline gets decoded properly. Switching back to CFHD_CURVE_GAMMA_2pt2 now gives a last scanline that still contains the LogC image data. The same is true for any other encode/decode curves specified in the file.
Conclusion: When decoding to the same curve as encoded (i.e. no change) the last scanline doesn't get rendered (i.e. written to the output buffer) at all.
This ONLY applies to RGB encoded files, YUV is fine. My output pixel format is CFHD_PIXEL_FORMAT_RG48.

Odd scanline numbers from RGB encodes should be supported.  That is a bug.

You have an idea / hint where I should be looking in the code? I was trying to find where curves get changed, but somehow always ended up in bayer.c which is probably not where I should be looking.

RAW (Bayer) was where all the curves and ActiveMetadata was developed first, so stepping into bayer.c makes sense.  However, the failure is likely in the last scanline of the wavelet.  Different wavelet code may be used if ActiveMetadata image development is active.  So having a mismatch in encode and decode curve will likely use a different inverse wavelet, one that handles the odd scanline, and one that doesn't.  Look at the last wavelet used.

Found something. In wavelet.c most of the TranformInverseXXX() functions do this:
//DAN20050606: Added to fix issue with heights that are not divisible by eight
last_display_row = info->height/2;

However, TransformInverseRGB444ToRGB32() does it like this:
//DAN20050606: Added to fix issue with heights that are not divisible by eight
last_display_row = (info->height+1)/2; // DAN20090215 -- fix for odd display lines.

So for a test I used CFHD_PIXEL_FORMAT_B64A as output format instead of CFHD_PIXEL_FORMAT_RG48 and now the last scanline gets rendered correctly.

Yes, the "DAN20090215" note looks like is might be useful on other pixel format optimized wavelet transforms (TranformInverseXXX()).
Try: last_display_row = (info->height+1)/2;

That seems to fix it... I just replaced all occurances with the version that is rounding up instead of truncating.
However, just below the "DAN20090215" fix is the following:
odd_display_lines = info->height & 1;

And then further down:
	if(odd_display_lines)
	{
		if(row == last_display_row - do_edge_row - 1)
		{
			strip.height = 1;
		}
	}

The other verions of TranformInverseXXX() don't do this either. So I'm not sure my "fix" is the full story or I'm just lucky that I don't run into more/other problems now.

On closer inspection it seems that the odd_display_lines variable makes sure that on the last iteration of the loop we don't generate two output rows but just one. So I guess just applying my change means it will now write past the end of the buffer.

Yes.  You will need to prevent writing outside of the buffer.

Added that check for the last single row to all functions. Will do more testing with that version, but for now here's my modified wavelet.c.
wavelet.zip

Changes to TransformInverseRGB444ToRGB48 aren't good.  With TestCFHD set the resolution to 1081 and run the decoder test -D, it will crash with those changes.  I'm looking at the benefits of the other modifications.


The SQL is incorrect using the time type field

SELECT toStartOfMinute(toDateTime(toDateTime((timestamp/1000)))) AS timestamp,
       COUNT(*) AS count
FROM pupuolap.component_dependency_records_distributed
WHERE timestamp >=<PHONE_NUMBER>000
  AND timestamp <<PHONE_NUMBER>000
GROUP BY toStartOfMinute(toDateTime(toDateTime((timestamp/1000))))
ORDER BY count DESC
LIMIT 10000;

The alias name should not match the original field name.
Environment
(please complete the following information):

superset version: 0.38.0
python version: 3.7.9
node.js version: v12.18.3

hi @chen-ABC
Why is date picker generated long int in where clause? could you show me the full screenshot on the explore page?
Could you test this dataset in Superset 1.0?

@zhaoyongjie
Because my time field is a timestamp,

From the CK error log seems that you use incompatible data type calculation. please double check table schema in clickhouse


facilitate custom additions to the "preload, create, update" trifecta

I write a lot of engines where someone can customize which files are loaded by editing the xml or json file.  The problem is, the rigidity of one preload method makes this hard.  For example, right now I have to do this awkward setup to get my current test to work:
`function preload ()
{
this.load.xml('xml', 'assets/test.xml');
}
function create ()
{

     var xmlData = this.cache.xml.get('xml');
    var unit = $(xmlData).find("unit");
    var imageList = $(unit).find("imageList");
    var images = $(imageList)[0].innerHTML.split(",");

    images.forEach(loadImage.bind(this));
      this.load.start();
    this.load.once('complete', finishCreating, this);

}`

I didn't include finishCreating or anything after, but you get the idea.  I would love to be able to just have a more intuitive way to dynamically add methods to the scene object inside of the config object and have them call in order.  (i.e. preload1, preload2, etc.)

I don't really understand the question here, and this doesn't appear to be an API Bug, more just a general support question - there are much better places to ask those than GitHub.
Regardless, Phaser already has it's own JSON packfile format, which allows you to create a json file that contains all of the game data to be loaded, and then load just this one json file instead. Have a look at the File Pack examples here: http://labs.phaser.io/index.html?dir=loader/&q=
Also, there's no reason why you should only have 'one preload method'. Every Scene can have its own preload method, and you can load files at any point in the Scene, even after preload has finished, or even add files into the load queue as it runs. Again, there are lots of examples in the link above (see the Loader Events folder specifically for this). Scenes also have a files payload config option, which means you could put your XML file in here, and then process its contents at the start of the preload method, making whatever loader calls you need.

Certainly did not mean to offend with my suggestion. I only made it because, while the information about the kind of feature I need is clearly present as you pointed out, the style of your documentation is frankly a little unclear. All the searches I did kept coming up with three built in functions per state, called in sequence, with no clear explanation of how to add your own custom built in functions to the sequence.
Sent from my iPhone

On May 17, 2019, at 8:51 AM, Richard Davey<EMAIL_ADDRESS>wrote:
I don't really understand the question here, and this doesn't appear to be an API Bug, more just a general support question - there are much better places to ask those than GitHub.
Regardless, Phaser already has it's own JSON packfile format, which allows you to create a json file that contains all of the game data to be loaded, and then load just this one json file instead. Have a look at the File Pack examples here: http://labs.phaser.io/index.html?dir=loader/&q=
Also, there's no reason why you should only have 'one preload method'. Every Scene can have its own preload method, and you can load files at any point in the Scene, even after preload has finished, or even add files into the load queue as it runs. Again, there are lots of examples in the link above (see the Loader Events folder specifically for this). Scenes also have a files payload config option, which means you could put your XML file in here, and then process its contents at the start of the preload method, making whatever loader calls you need.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Support retries for non-loadbalanced requests

Java 11
Spring Boot 2.3.10.RELEASE
Spring Cloud Hoxton.SR11
Spring Retry 1.2.5.RELEASE
When I create FeignClient with attribute url, load balancer retry doesn't work. In the previous version (Hoxton.SR10) it worked.
Sample: DemoFeignNotRetryApplicationTests
correctRetry test shows that FeignClient without url was retried.
retryDoesNotWork test shows that FeignClient with url wasn't retried.
I think it related to RetryableFeignBlockingLoadBalancerClient does not respect 'url' parameter of @FeignClient.
@OlgaMaciaszek Could you please check?
Thank you!

Ther retry support was added for LoadBalancer, hence even all the retry-related properties are prefixed with spring.cloud.loadbalancer.retry. The fact that there were retries when url was passed was sort of an accidental side-effect, they were working cause the requests were being passed via the load-balancing client where they should not have been. We could add retries for non-load-balanced requests as a separate feature, though.

I would say that this is an issue of naming things correctly. spring-cloud-loadbalancer states in it's name and properties names that it does only load-balancing and thus we are having problems with supporting some of the features for non loadbalanced requests (configured via url in Feign client). spring.cloud.loadbalancer properties semantically do not fit for non loadbalanced requests, so I guess there might be other issues in the future with the same root cause :(

Retries were historically never added as part of the OpenFeign integration. The retry support was introduced in SC Commons as part of the LoadBalancer integrations and added to OpenFeign as part of the effort to support feature parity between the commons LB implementation and the LB implementation used in OpenFeign and that's also where the property comes from. Retries were never supported or requested for non-load-balanced requests in OF. We can introduce this as a new enhancement, though.

I think, that I wasn't quite obvious with what I was trying to say.
My idea is that whole chain of feign+loadbalancer is quite strange in terms of retries, but that was before as well with feign+ribbon.
Initially (openfeign + ribbon integration) retries were available both from Feign side via Retryer interface and also via ribbon properties (MaxAutoRetries, MaxAutoRetriesNextServer, OkToRetryOnAllOperations, retryableStatusCodes). It is understandable why those are required, but definitely not user-friendly and error prone to configure retries in different places and making sure that those are in sync. Unfortunately, introducing loadbalancer did not change that concept of retries, instead made it semantically more difficult to understand.

For now, we can just add support for non-load-balanced retries (although it is not high-priority, as also Retryer support is present); when we publish next major we can think of improving the API and properties: https://github.com/spring-cloud/spring-cloud-openfeign/issues/535.


Define MVP

We need to define the set of features for the MVP

Possibly in the MVP:

slided per view
loop
autoplay (including play/pause buttons)
reacting to DOM changes in the slides slot

Not in MVP:

Specify custom pagination indicators (by adding them to a specific slot)
Specify custom navigation buttons (by adding them to a specific slot)
Specify custom play/pause buttons (for when autoplay is enabled)
RTL layout

MVP APIs:
Properties / Attributes:

slides-per-view (default: 1). Number of slides in a view. The final view will have empty slots if there isn't an exact number of slides.
selected (default: 0). The currently selected view.
loop (default: false). If true, the first and the last cell are wrapper around to ensure infinite scrolling.

Methods:

next(): programmatically selects the next view
prev(): programmatically selects the previous view
update(): Forces an update. Useful if something has changed and the component hasn't updated itself.

Events:

view-selected: fired every time a new is selected

CSS:

--x-slider-gap (default: 16px). Gap between slides
--x-slider-transition-duration (default: 0.5s) The duration of the transition between views
--x-slider-transition-timing-function (default: ease-in-out) The timing function for the transition between views
--x-slider-pagination-color (default: #999) Color for pagination items
--x-slider-pagination-color-selected (default: #000) Color for the selected pagination item
--x-slider-navigation-color (default: #000) Color for the navigation buttons

Closing this issue as every feature has now become a separate issue


Implement tail sampling on the client

We currently implement open telemetry tail-sampling only on the OTel Collector. This causes a bunch of issues, though:

We noticed "congestion" since we log a lot of spans and only sample a few of them. In the past, OTel collector was discarding events because of this for larger periods of time.
We can only send the traces to our dedicated OTel collector since otherwise it will be too noisy. This prevented us from enabling traces on enterprise instances in any useful way.

This PR attempts to implement tail-sampling like we do it on the OTel collector on the client. Since there is no Tail Sampler, this is done by extending the HTTP SpanExporter. For every span that is exported, we will now look at the root span and only record if if it was manually marked as sampled.
Since spans can be flushed out of order (sub-spans can be flushed before the parent span is sent), theres a bit of bookkeeping that queues spans until their parent was received (or up to 1min in total).
Test plan

To test this, I made some changes in the source code, mainly:

Comment out the check in CodyTraceExport line 17 for this.isTracingEnabled
Add a console.log to see which traces are flushed in CodyTraceExport on line 58

Then, trigger things that would collect traces like autocomplete or chat and see if there's something logged:

For every span that is exported, we will now look at the root span and only record if if it was manually marked as sampled.

@philipp-spiess at least in the Go SDK, it's possible to set the trace is sampled flag https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/sdk.md#sampling that automatically applies to all spans in a trace and controls whether the underlying processor receives the span or not, which sounds like the behaviour you describe here

The native sampling flag behaviour sounds like pretty much what you want here, but I may be missing some nuance - feel free to ping me on Slack to discuss if that might be more effective!

@bobheadxi I'll look into it but one problem I remember is that for autocomplete we only know towards the end of the trace if we will sample it so all sub-spans that are already flushed need to wait for that, hence the tail sampling approach.
If we can do this with TraceFlags too than that should help a ton yep

@bobheadxi I tried (via span.spanContext().traceFlags = TraceFlags.SAMPLED) but I couldn't get this to work the way I want to. Any ideas what else I can try? 🤔

When I just make this change, everything else is sampled by default too
When I use it in combination with TraceIdRatioBasedSampler set to 0 (i.e nothing is sampled) it won't sample any trace
I guess I can use it with a custom Sampler but this has the issue that some spans may be flushed before we make the sampling decision (I tried this early with the manual sampled field and it was not working reliably).

I tried (via span.spanContext().traceFlags = TraceFlags.SAMPLED) but I couldn't get this to work the way I want to. Any ideas what else I can try? 🤔

It should be a read-only attribute, so the should-trace flag must be set by a custom Sampler implementation, Go version: https://sourcegraph.com/github.com/sourcegraph/sourcegraph/-/blob/internal/tracer/policy_sampler.go?L23:1-44:2 i.e. wrap TraceIdRatioBasedSampler with your own sampling decider

we only know towards the end of the trace

Curious how this works, as your custom sampler in this PR interrogates the root span 🤔 do we set the attribute only at the end of the root span?

Curious how this works, as your custom sampler in this PR interrogates the root span 🤔 do we set the attribute only at the end of the root span?

@bobheadxi Yeah. I only wanted to sample autocomplete requests that also end up being shown to users. We do a similar thing for telemetry, because we don't really care about those which aren't shown (these won't be noticed by a user anyhow and we only care about their cost which we can capture from the gateway traces).
So what we do here is we start a trace and then do all the fancy shmancy to build the autocomplete result and only if the request was not interrupted in the mean time (i.e by another keystroke or some other things) will it be marked as "suggested" and also sampled. That's the inherent issue I had with custom Sampler, the decision on wether something samples need to be made ahead of time.
I'll try this out for now, my main motivation behind this PR is that we reduce the load of traces being sent from the Cody Clients to the OTel collectors so if we run into issues we can continue to move the sampling decision into the otel collector but it would be nice if the client doesn't log every single I/O operation going on 😬

Sounds good!


[WIP:] Slackdemo2

@ErisDS

Cleaned up icon
Added short link to my.slack.com for webhook creation
Removed channel config - this is confusing, seeing as you set it up on slack.com already
Removed username config - there's no reason this shouldn't just be "Ghost" at the moment
Cleaned up some markup - there is unfortunately a lot more to do here.
Replaced pixelated icon with new hires icon

Still needs doing:

There should be no "activate" button on the first screen. It should just be a right > chiclet. Same as post-settings menu meta data. This does not need to change state.
I recommend stripping the concept of "activate" completely

Have to get on a plane now so I can't finish this list

There should be no "activate" button on the first screen. It should just be a right > chiclet. Same as post-settings menu meta data. This does not need to change state.

I think the whole bar is meant to be a link as well, rather than just the arrow? That's how the PSM functions so I think it should be the same.

I recommend stripping the concept of "activate" completely

It seems to me that the url should be empty to start, rather than / and that we should therefore base active/inactive on whether a URL is set.
I think for this version, with only one field, it does make sense to drop the activate/deactivate button. Ideally we would have a way other than the URL to indicate whether or not the feature was active so that we can do things like - deactivate if the ping fails 5 times (URL is probably wrong) and to have a consistent way across integrations / apps to determine if the functionality is supposed to be "on" else the software will be doing more work (using more resources) than needed. Still this will probably all fall out much more naturally when we have more than one of these in place and we can figure out a good framework for them.

FYI I'm working on this and I think I have it working ok, but probably not the best code 🙃
I think I can push direct to this branch

I've pushed a commit that removes the whole concept of activate/deactivate everywhere.
isActive is now a computed property based on whether the URL is empty or not. The default url is now empty instead of /.
I also set the url field to have a placeholder of https://hooks.slack.com/services/... as there is now default value.
I also did a bit of cleanup around the username, it will now always be 'Ghost' just like the icon will always be the ghost emoji 👻 . There is a way to set this when you configure your webhook, just as there is with the channel, however our settings will always override this.
I'm not sure if this is really the right thing? We could also not include them at all, and the messages would use whatever the user configures in slack. Either way works, one way we get consistency, the other way the user gets control and can configure different things e.g. if they have more than one blog posting into the same slack channel (edge case, but we have that 😉 ).

Cleaned some more styles - this is looking way better now. I think it needs a save button on the detail state? I know it doesn't need one but it's unclear if state has been saved or not.
Icon in navbar on the left needs to change - that's a me thing - will come back to it!
Everything else is looking good I think. @kevinansfield if you can spot any UX improvements here - would definitely be welcome

As we're moving away from save buttons, it seems weird to me to add one for this. I know what you mean about it being unclear - it's the same on the tags page, labs page, etc In this case, I think it might work to have some sort of "going green" validation? Either an icon like on signup/setup etc or a green border or checkmark next to the URL field to demonstrate that it has been validated / "accepted".
There is an error message that appears if it isn't valid, so this would fit with what we already have? Just a suggestion as that was what came to my mind before you said about a save button.
One thing I noticed as well was that if you hit enter in the url input, the form submits and this causes a test notification, rather than a save, which was what I would have expected.

@ErisDS icon updated - I think I'm done. I agree with everything you said about save button, but the fact remains that we don't have anything to replace it sanely. I don't think there's a better option at the moment than just having a save button, until we actually have something better.
@kevinansfield Not related to this PR I don't think - but we seem to have lost a lot of styling on the search box. I've included a few fixes in the latest commit, but there's still more that doesn't look right. Eg there's no border colour on:focus, and the "no results" message formatting has broken.
Before:

After:

@kevinansfield can you look at adding the save button? I think it is beyond my ember fu.
@johnonolan can you go to settings on your repo and add Kevin as a collaborator? Then we don't need a new PR again 😉

Done!

Just to be clear, once the save button is in are we getting rid of the save on focus-out or keeping that? (focus-out will cause the save button to spin so there is some indication that saving is happening)
Re the search input styling I'll tackle that in a separate PR.

@kevinansfield either is fine w/ me

Closing in favour of #6795


Unable to locate .exe file

Hi there, I have installed the program and everything seems to be in order, but i cannot locate the .exe file to launch xivalexander when running the game.
For reference, previously before Endwalker the plugin was working fine.
Thank you

If you're looking for a shortcut to launch XivAlexander, you don't have to. Installing XivAlexander means that XivAlexander will automatically launch along with the game whenever you launch the game.


How to send composing presence?

Hi I am trying to send a presence composing using res, err :=<EMAIL_ADDRESS>"composing") but the status in whatsapp app in my contact's cell phone not show "composing". But when I try to send available presence res, err :=<EMAIL_ADDRESS>"available") , the status in Whatsapp app show "Online".

I think you have to read this #23

The issue was an incomplete implementation, I fixed that in PR #80


make documentation more accessible

I realized that the haddock rendering of the tutorial module (Generics.Eot.Tutorial, for example here: https://www.stackage.org/haddock/lts-11.3/generics-eot-<IP_ADDRESS>/Generics-Eot-Tutorial.html) ended up without the tutorial comments. Therefore I thought it was actually harmful to include that module in the package -- because it might prevent people from finding the real tutorial (here: http://generics-eot.readthedocs.io/en/stable/tutorial.html). Therefore I removed that module from the exposed modules of the package.
This PR also includes various other tweaks that makes the documentation hopefully more discoverable.
CC: @gwils

I still have to remove the markdown-unlit dependency from the library section of the package.


setup folders and db connection files

setup basic folder structure and db connection files

setup basic folder structure and db connection files


Add class definition fixer.

Fix white spaces in classy definitions.
For example:
<?php
interface     Test    extends TestInterface  ,  /* */   TestInterface2   {
}

to:
<?php
interface Test extends TestInterface, /* */ TestInterface2 {
}

I don't think we should allow comments in those places either tbh. I think it would be cool if the fixer remoed them.

it's valid in PSR-2 matter:
<?php
class ClassName extends ParentClass implements
    \ArrayAccess,  /* to have [] */
    \Countable,    // to count them as well ;)
    \Serializable  // as we want to serialize it!
{

it's valid in PSR-2 matter:

Yeh. Looks ugly though. Also, this fixer isn't in the PSR2 level. :P

it doesn't matter, it is a standard.

At least, this fixer should be named class_definition_whitespaces and another one can be propose to remove comments IMO.
I'm surprised to see this fixer on Contrib section. There is no valid PSR about class definition for that?

https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-2-coding-style-guide.md#41-extends-and-implements
There are few rules in PSR 2 about what should be on one line. There is nothing about the separation of the items on it, unless some other rules apply on these items?

items?

I mean stuff like implements class extends ;)

PSR-2 states:
Control structure keywords MUST have one space after them; method and function calls MUST NOT.

So there are no rules for white space around between class, interface, extends, so this fixer should stay at contrib (unless Symfony agrees).
Renamed the class following the suggestion of @Soullivaneuh and did a fix following @dereuromark.

hmm forgot to re-gen the readme, will do later on.

choose right branch for PR: https://github.com/FriendsOfPHP/PHP-CS-Fixer/blob/1.11/CONTRIBUTING.md#quick-guide
tests failing
Symfony level indeed

choose right branch for PR: https://github.com/FriendsOfPHP/PHP-CS-Fixer/blob/1.11/CONTRIBUTING.md#quick-guide

I know about that file. However I think I'm going to wait with this one until either 2.0 is released or a feature stop is in place for 1.x.

tests failing

I noticed https://github.com/FriendsOfPHP/PHP-CS-Fixer/pull/1501#issuecomment-157491192 :P

Symfony level indeed

good to hear, I'll take that into account the next time.

I know about that file. However I think I'm going to wait with this one until either 2.0 is released or a feature stop is in place for 1.x.

why is that? what exactly do you need for this fixer from 2.x line that you don't have at 1.x line?
Fixer looks pretty ready, just send it to 1.x ;)


Screenshots from Deadman Mode can overwrite screenshots from Normal Accounts

If a player uses the same account on both Normal and Deadman modes, the automatic screenshots for levelling up/clue rewards/barrows rewards can overwrite images from the other mode.

This is still valid issue until the PR will be added.

Fixed in 6c803dce035d3f18e179421bedc36e7df1ea7826


Added what can sql do

[ x] I have read freeCodeCamp's contribution guidelines.
[x ] My pull request has a descriptive title (not a vague title like Update index.md)
[ x] My pull request targets the master branch of freeCodeCamp.
[ x] None of my changes are plagiarized from another source without proper attribution.
[x ] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Hey @username
It seems that similar changes have already been submitted on an earlier PR (#28789) for this article you're editing, sorry about that. 😓  We are closing this duplicate.
If you feel you have more to add, please feel free to open up a new PR.
Thanks again! 😊

If you have any questions, feel free to reach out through Gitter or by commenting below. 💬


[Enhancement] Expand saveScreenshot() to capture full page

What are you trying to achieve?
The default behaviour for saveScreenshot() is to capture the current viewport, but from my experience on Nightmare in particular the focus isn't on the area of the fault when the screen is captured.
What do you get instead?
Basically you need to manually set the set the viewport to the height that the page may need to be in order to capture any issues to aid investigation of failed tests.
Proposed solution
Allow for saveScreenshot() to capture the full page by resizing the viewport on demand to the availible scrollHeight and scrollWidth
Notes
I've already solved this, the PR should be following shortly. This is more for reference.

full page should mean resize to scrollHeight but leave the width alone; don't resize to scrollWidth.
This is important for responsive design testing.


Submission to Play Store?

Hi @anjlab,
Is there any possibility that you submit this app to the play store? Or do you mind if I would do it?

yes, you can do it if you like


Remove MIDAS as it has been archived

MIDAS is no longer support and has been archived as per the message on their README.md.

Very nice, thank you!

Agreed. osquery is the evolution for MIDAS and should be used in it's place.


pr

Description
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.
Fixes # (issue)

pr


duplicate examples directory

examples in gpfit/examples/ should be updated / renamed as appropriate, moved to docs/source/examples, and added to tests/t_examples.

It seems like the example 6-1 was duplicated in docs/source/examples around the time of the creation of this issue, and added to tests/t_examples as suggested. What remains is for example 6-3 to have the same (there is currently a t_ex6_3 but should be moved to t_examples for parallelism).


feat(global symbols): make config to disable export global symbols

I saw this comment from @mjbvz that it's normal behavior when I create any *.ts or *.js file without export symbols and I can see all declared symbols in global namespace.
I would like to have a config to avoid such behavior.

Tracked upstream by https://github.com/Microsoft/TypeScript/issues/14279
Please upvote if you are interested in this


Remove -a/--app from Quickstart documentation

As mentioned in #2009, simplifying the CLI saw the removal of the -a/--app flag. Therefore, the only way to specify the module to import is by setting FLASK_APP.

This change is

Thanks!


Cycling through tabs, forgets scroll position

SQL Operations Studio Version:
Version 0.23.6
Commit 8a3011756318a2ded1e6e84332230a2b2bf9c544
Date 2017-11-05T22:46:14.815Z
Shell 1.7.9
Renderer 58.0.3029.110
Node 7.9.0
Architecture x64
Steps to Reproduce:

Open a file
Scroll down a bit
Cycle to another query (Ctrl + Tab)
Cycle back to the previous query (Ctrl + Tab)

The tab has forgotten its scroll position.

Seems sort of related to #123.

Is this in regard to the query results grid forgetting its position or something else? I closed #123 for now on assumption that this is about the results grid forgetting its position. If that's not the case then I'll reopen #123. Thanks.

Is this in regard to the query results grid forgetting its position or something else?

The original issue is for actual query tabs, but it feels like the same issue, really, since it's behaving the same way in the results grid.

The messages tab is also affected by this problem.

Scroll position not preserved when switching over tabs.

Please also look at the Edit Data related problems discussed in https://github.com/Microsoft/sqlopsstudio/issues/299.

I would be glad if this is fixed as I'm working with multiple files quite often. Note that this is working just fine Visual Studio Code, which I thought sqlopsstudio is based upon...

A new version (0.31.4) is out but error #114 is still not fixed... or, am I missing something?

Can confirm this error is still occurring and I am currently working between multiple, length files and this is very disrupting.

thanks for the update.

This issue has reappeared in the latest insider build.
Version 0.33.4-insider
Commit c92b88bfaff3bed7c8f6190d33534dc649a39e0c
Date 2018-09-13T07:08:25.140Z
VS Code 1.26.1
Shell 2.0.8
Renderer 61.0.3163.100
Node 8.9.3
V8: 6.1.534.41
Architecture x64

Hi,
Getting this issue with column sizing and scroll position being lost in:
Version 1.3.7-insider
Commit 5a3087859918b1564d2622b95defa662facdbef6
Date 2018-12-07T02:33:40.014Z
VS Code 1.26.1
Shell 2.0.9
Renderer 61.0.3163.100
Node 8.9.3
V8: 6.1.534.41
Architecture x64


[Bug]: Server constantly restarting after installation using docker-compose

Preflight Checklist

[X] I agree to follow the Code of Conduct that this project adheres to.
[X] I have searched the issue tracker for an issue that matches the one I want to file, without success.
[X] I am not looking for support or already pursued the available support channels without success.

Version
1.15.0
Installation Type
Official Docker Compose
Service Name
Docker(DongTai-Base-Image), Deploy(DongTai-deploy), DongTai-Core
Describe the details of the bug and the steps to reproduce it
DongTai server docker container constantly restarts right after installing DongTai according to this documentation: https://docs.dongtai.io/docs/getting-started/server/deploy-docker-compose
Additional Information
Docker version 24.0.5, build 24.0.5-0ubuntu1~20.04.1
Docker Compose version v2.22.0
Linux dongtai 5.4.0-163-generic #180-Ubuntu SMP Tue Sep 5 13:21:23 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Logs
$ docker ps | fgrep server-1
caa9e6207a07   registry.cn-beijing.aliyuncs.com/huoxian_pub/dongtai-server:1.15.0      "/bin/bash /opt/dong…"   14 minutes ago   Restarting (1) 31 seconds ago                                       dongtai-dongtai-server-1

$ netstat -lntp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 <IP_ADDRESS>:80              <IP_ADDRESS>:*               LISTEN      20885/docker-proxy
tcp        0      0 <IP_ADDRESS>:53           <IP_ADDRESS>:*               LISTEN      934/systemd-resolve
tcp        0      0 <IP_ADDRESS>:22              <IP_ADDRESS>:*               LISTEN      1027/sshd: /usr/sbi
tcp        0      0 <IP_ADDRESS>:38141         <IP_ADDRESS>:*               LISTEN      10733/node
tcp        0      0 <IP_ADDRESS>:45287         <IP_ADDRESS>:*               LISTEN      991/containerd
tcp6       0      0 :::80                   :::*                    LISTEN      20891/docker-proxy
tcp6       0      0 :::22                   :::*                    LISTEN      1027/sshd: /usr/sbi

$ ./dtctl logs server
"docker logs" requires exactly 1 argument.
See 'docker logs --help'.

I tried reinstalling it but the result is the same.
I also tried installing it from the github main, develop, and release-1.15.0 branches and directly from the zip release package.
Result is the same.

I tried reinstalling it but the result is the same. I also tried installing it from the github main, develop, and release-1.15.0 branches and directly from the zip release package. Result is the same.

Have you tried ./dtctl rm -d?
The previously released version has data problems and needs to be cleaned and rebuilt.

Before no. Now I retried it with -d on the same three branches. Result is still the same.

Before no. Now I retried it with -d on the same three branches. Result is still the same.

Could you give me some logs?
Just use this command docker logs dongtai-dongtai-server-1

Check whether there is a container with the normal running image registry.cn-beijing.aliyuncs.com/huoxian_pub/dongtai-server:1.15.0
Run the following command
docker exec -it dongtai-dongtai-server-1 bash -c 'python manage.py migrate'

All of these containers are based on the image you mentioned:
root@cerebrates:~/DongTai/deploy/docker-compose# docker ps | fgrep registry.cn-beijing.aliyuncs.com/huoxian_pub/dongtai-server:1.15.0
4ba5533f4bf8   registry.cn-beijing.aliyuncs.com/huoxian_pub/dongtai-server:1.15.0      "/opt/dongtai/deploy…"   2 days ago   Up 2 days                                          dongtai-dongtai-worker-beat-1
e1d83b0a6fd3   registry.cn-beijing.aliyuncs.com/huoxian_pub/dongtai-server:1.15.0      "/opt/dongtai/deploy…"   2 days ago   Up 2 days                                          dongtai-dongtai-worker-es-1
450f3ba79a20   registry.cn-beijing.aliyuncs.com/huoxian_pub/dongtai-server:1.15.0      "/bin/bash /opt/dong…"   2 days ago   Up 6 seconds                                       dongtai-dongtai-server-1
958e98453dc3   registry.cn-beijing.aliyuncs.com/huoxian_pub/dongtai-server:1.15.0      "/opt/dongtai/deploy…"   2 days ago   Up 2 days                                          dongtai-dongtai-worker-other-1
6e6ef618c530   registry.cn-beijing.aliyuncs.com/huoxian_pub/dongtai-server:1.15.0      "/opt/dongtai/deploy…"   2 days ago   Up 2 days                                          dongtai-dongtai-worker-sca-1
888b3b5011de   registry.cn-beijing.aliyuncs.com/huoxian_pub/dongtai-server:1.15.0      "/opt/dongtai/deploy…"   2 days ago   Up 2 days                                          dongtai-dongtai-worker-high-freq-1
015d3a829b71   registry.cn-beijing.aliyuncs.com/huoxian_pub/dongtai-server:1.15.0      "/opt/dongtai/deploy…"   2 days ago   Up 2 days                                          dongtai-dongtai-worker-task-1

Since the server-1 is constantly restarting I cannot execute any migrate command on it:
$ docker exec -it dongtai-dongtai-server-1 bash -c 'python manage.py migrate'
Error response from daemon: Container 450f3ba79a20a464a9a4b9d700d8ab7e7412c3f30b53fdd3f6c0e876b916ef89 is restarting, wait until the container is running

dongtai-dongtai-worker

try other container like dongtai-dongtai-worker-xxxx

I got the following:
Running migrations:
  No migrations to apply.
  Your models in app(s): 'dongtai_common' have changes that are not yet reflected in a migration, and so won't be applied.
  Run 'manage.py makemigrations' to make new migrations, and then re-run 'manage.py migrate' to apply them.

So I run makemigrations and than migrate on all containers, even on server. I was able to catch it in between restarts. Some of the containers created and applied migrations, others didn't. The result is still the same. Server is constantly restarting. Example log of migrations on one container:
$ docker exec -it dongtai-dongtai-server-1 bash -c 'python manage.py makemigrations; python manage.py migrate'
use local file
is in gevent patched : False
INFO 2023-10-17 00:54:18,738 [__init__.monkey_patch:68] app: dongtai_common module: dongtai_engine.plugins.method_pool class:  func : method_pool_after_scan is patched by PlugMethodPoolAfterScan
preheat settings now : True
INFO 2023-10-17 00:54:19,058 [report_handler_factory.wrapper:80] Registration report type 130 handler FilePathHandler
INFO 2023-10-17 00:54:19,059 [report_handler_factory.wrapper:80] Registration report type 129 handler ThirdPartyServiceHandler
INFO 2023-10-17 00:54:19,062 [report_handler_factory.wrapper:80] Registration report type 97 handler ApiRouteHandler
INFO 2023-10-17 00:54:19,064 [report_handler_factory.wrapper:80] Registration report type 81 handler ErrorLogHandler
INFO 2023-10-17 00:54:19,067 [report_handler_factory.wrapper:80] Registration report type 37 handler HardEncodeVulHandler
INFO 2023-10-17 00:54:19,071 [report_handler_factory.wrapper:80] Registration report type 1 handler HeartBeatHandler
INFO 2023-10-17 00:54:19,076 [report_handler_factory.wrapper:80] Registration report type 33 handler NormalVulnHandler
INFO 2023-10-17 00:54:19,087 [report_handler_factory.wrapper:80] Registration report type 36 handler SaasMethodPoolHandler
INFO 2023-10-17 00:54:19,183 [report_handler_factory.wrapper:80] Registration report type 17 handler ScaHandler
INFO 2023-10-17 00:54:19,183 [report_handler_factory.wrapper:80] Registration report type 18 handler ScaBulkHandler
No changes detected
use local file
is in gevent patched : False
INFO 2023-10-17 00:54:21,529 [__init__.monkey_patch:68] app: dongtai_common module: dongtai_engine.plugins.method_pool class:  func : method_pool_after_scan is patched by PlugMethodPoolAfterScan
preheat settings now : True
INFO 2023-10-17 00:54:21,915 [report_handler_factory.wrapper:80] Registration report type 130 handler FilePathHandler
INFO 2023-10-17 00:54:21,916 [report_handler_factory.wrapper:80] Registration report type 129 handler ThirdPartyServiceHandler
INFO 2023-10-17 00:54:21,920 [report_handler_factory.wrapper:80] Registration report type 97 handler ApiRouteHandler
INFO 2023-10-17 00:54:21,921 [report_handler_factory.wrapper:80] Registration report type 81 handler ErrorLogHandler
INFO 2023-10-17 00:54:21,924 [report_handler_factory.wrapper:80] Registration report type 37 handler HardEncodeVulHandler
INFO 2023-10-17 00:54:21,928 [report_handler_factory.wrapper:80] Registration report type 1 handler HeartBeatHandler
INFO 2023-10-17 00:54:21,933 [report_handler_factory.wrapper:80] Registration report type 33 handler NormalVulnHandler
INFO 2023-10-17 00:54:21,944 [report_handler_factory.wrapper:80] Registration report type 36 handler SaasMethodPoolHandler
INFO 2023-10-17 00:54:22,032 [report_handler_factory.wrapper:80] Registration report type 17 handler ScaHandler
INFO 2023-10-17 00:54:22,032 [report_handler_factory.wrapper:80] Registration report type 18 handler ScaBulkHandler
System check identified some issues:

WARNINGS:
dongtai_common.IastAssetVulRelationMetaData.vul_asset_key: (mysql.W003) MySQL may not allow unique CharFields to have a max_length > 255.
        HINT: See: https://docs.djangoproject.com/en/3.2/ref/databases/#mysql-character-fields
Operations to perform:
  Apply all migrations: admin, auth, authtoken, captcha, contenttypes, db, django_celery_beat, dongtai_common, sessions
Running migrations:
  Applying dongtai_common.0026_auto_20231017_0046... OK

reinstall latest docker and docker-compose v1 can fix this problem.
https://docs.docker.com/compose/install/standalone/
./dtctl install -v 1.15.0

Is there any simpler way to run it locally? I've been trying to quickly see how it works and potentially use it in future but seems like either I'm unlucky with choosing the OS/environment or the setup process is troublesome.


Version 5.0.0-SNAPSHOT release notes

Hi, I was trying to upgrade the SDK's dependency from 4.0.3-FINAL to 5.0.0-SNAPSHOT but before I do that, I wanted to know if are there any breaking changes etc. I tried searching for the release notes but could not find it. Can someone help?

Also, is 5.0.0-FINAL available?

@visheshruparelia I'm terribly sorry for the late reply, I'm just catching up here and trying to put everything on track.
5.0.0 will be released with 0.9 spec version.  You can try the PR on your end if you don't mind. #273


importlib_metadata: 0.23 -> 1.3.0

This unbreaks tox, closes #76150.
Turns out the importlib-metadata tests are fixed upstream too, so
re-enable them.

Motivation for this change
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Notify maintainers
cc @

already in #76059

This commit enables tests though https://github.com/NixOS/nixpkgs/pull/76059/commits/bcb63f49e39256aa27c3bc6d92bf259209f0057d.

true, I'll modify the other PR, seeing as this is a mass rebuild

commit has been updated in the PR https://github.com/NixOS/nixpkgs/pull/76059/commits/ca25dc2b905afe0756fa10c12c88a1798a8b30be
buildPythonPackage defaults doCheck to true

verified that setuptools ran test suite in other PR

great, thanks @flokli


Fenced Matrix using Python

Fenced Matrix
LGM-SOC'21 Participant
Author : Mansi Singh

Description
The issue was generated by  the author and two solutions have been provided to make understand others the concept of list, list comprehension, deep and shallow copy methods in Python. The project can be performed on Jupyter Notebook or Google Colab.
Two solutions have been provided for better understanding where one uses library while other doesn't.
Fixes #597
Type of change

[✔] New feature (non-breaking change which adds functionality)

Checklist:

[ ✔] My code follows the style guidelines(Clean Code) 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 created a helpful and easy to understand README.md
[ ] I have made corresponding changes to the documentation   -------------------------------- Not Required
[ ✔] My changes generate no new warnings
[✔ ] I have added tests/screenshots(if any) that prove my fix is effective or that my feature works

@singhmansi25 delete other files

Hey, after deleting other files, do I need to do PR again ???
On Tue, Jun 22, 2021 at 8:38 PM Amit Kumar Mishra @.***>
wrote:

@singhmansi25 https://github.com/singhmansi25 delete other files
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Ayush7614/Daily-Coding-DS-ALGO-Practice/pull/1109#issuecomment-866066402,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASKQICTQ7RF4O3VI5G3GAK3TUCRNDANCNFSM463WQYYA
.

@singhmansi25 is it a question from any online coding platform?? If yes then face it in the respective folder

Actually, its not from any platform. That's why I posted it in Data
Structures.
Please tell further details.
On Wed, 23 Jun, 2021, 7:56 pm Amit Kumar Mishra, @.***>
wrote:

@singhmansi25 https://github.com/singhmansi25 is it a question from any
online coding platform?? If yes then face it in the respective folder
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Ayush7614/Daily-Coding-DS-ALGO-Practice/pull/1109#issuecomment-866885609,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASKQICWDCIV4QWC7M4SKJMLTUHVILANCNFSM463WQYYA
.

@singhmansi25 ok but atleast add test case

Test Case in the form of images ?? Then do I need to do PR again ??
Please let me know.
On Wed, 23 Jun, 2021, 8:29 pm Amit Kumar Mishra, @.***>
wrote:

@singhmansi25 https://github.com/singhmansi25 ok but atleast add test
case
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Ayush7614/Daily-Coding-DS-ALGO-Practice/pull/1109#issuecomment-866913083,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASKQICWI33RCXFZ44AP6MP3TUHZDXANCNFSM463WQYYA
.

Just add it below the code. Look at other PRs.

@singhmansi25 any updates??

Yeah, I have made the changes. Do I need to do PR again ??


BXMSPROD-1084: changed execution command

Thank you for submitting this pull request
JIRA: (please edit the JIRA link if it exists)
BXMSPROD-1084
referenced Pull Requests: (please edit the URLs of referenced pullrequests if they exist)

referenced pull request 1
referenced pull request 2
referenced pull request 2
etc.

How to retest a PR or trigger a specific build:

* a pull request please add comment: Jenkins retest this

replaced sh './droolsjbpm-build-bootstrap/... everywhere where before was used sh 'sh droolsjbpm-build-bootstrap/...


Doc: Code review SaaS SideCI was renamed to Sider

According their website & blog, the service was renamed few weeks ago.
Because this is a minor doc change, so I thought it's okay to removed todos included in PR template. Let me know if there's any concern. Thanks!
P.S. Just noticed a good interview for RuboCop on their blog 😉

👍


Quantum resistance of Sia network

Quantum computing is going to be available to the public soon. Did you consider the quantum vulnerability of Sia network? The privacy ability of Sia brought by the cryptography can be lost due to quantum computing.

There are three crypto operations that Sia uses: symmetric encryption, asymmetric encryption, and hashing. We use symmetric encryption for file encryption; asymmetric encryption for host announcements and spending money; and hashing for, well, tons of stuff, but most notably Merkle proofs.
My understanding is that quantum crypto breaks asymmetric encryption, but not symmetric encryption or hashing. So a strong quantum computer threatens our payments and host announcements, but does not allow people to decrypt your files or cheat storage proofs.
We did not make Sia's asymmetric encryption "quantum proof" from the beginning because no post-quantum algorithms have been standardized yet. NIST is currently holding a contest to select such an algorithm to standardize; I expect that, as in the past, we will use either the winner or a runner-up. Fortunately, Sia was designed to accommodate arbitrary signature algorithms (see types.SiaPublicKey), so once we do select an algorithm, switching to it will be relatively painless.

that sounds not bad.


Add support for devfile 2.0 variables

Description
The devfile 2.0 spec includes global variables, which define key-value pairs, e.g.
variables:
  my-var: "some value"

These variables can be referenced in non-key string fields within the devfile using {{my-var}} to template different versions of a devfile by setting only the variable field.
We should add support for this in DWO.
See issue https://github.com/devfile/api/issues/239 and PR https://github.com/devfile/api/pull/352 for details.

is implemented with https://github.com/devfile/devworkspace-operator/pull/509

duplicates https://github.com/devfile/devworkspace-operator/issues/408


macOS tar.gz

In what situation would users actually make good use of the tar.gz package for macOS?

@gdams Can you help?

It's for when they want to bundle that in another package.  See https://github.com/AdoptOpenJDK/openjdk-support/issues/97

I use it for testing because I do not have to install it. As long as I download it with curl/wget or remove the quarantine attribute, it does its job.
@brunoborges Why do you ask?

Can't one extract the contents from a PKG file as well?

Yes, but complicated: https://stackoverflow.com/a/11299907. Again, why do you ask?

there are several reasons that users may wish to use the tarball:

To work around notarization/codesign issues on a local mac
To bundle the JDK/JRE into an application
To create a custom bundle with extra CACERTS etc

Closing as I think we have the complete answer.


Add file entry for alpine

The error about mocap_msgs will be fixed by https://github.com/alpine-ros/rosdistro/pull/177


Cannot enter username in Jitsi

Hello!  On NixOS, when I install Jitsi, I cannot enter in my username.  Consequently, I can't figure out how to connect.  Here is a screenshot:

Sounds like you're using the old broken version from the Ubuntu 14.04 repository. Anyway, this is either a packaging and/or a Java problem that we can't do anything about.


Related to #466, adding Serilog to the build

Looks good to me, FWIW. I've enjoyed MassTransit a lot over the years, so great to see Serilog providing some value in return. All the best with it!

I'm a big fan of Serilog, a lot of great work in there. So thanks for sharing this!

MassTransit + Serilog = :+1: from me!
Also, thanks for all your effort on MassTransit, Chris. We used it in most of our distributed apps and it works like a champ.