Add pipeline stage that removes embedded resources

Add new removeEmbeddedResources pipeline stage.
This fixes #401.
This fixes #267.
This stage uses a variety of heuristics to remove resources that are embedded inside other resources.
There are a number of different kinds of embeddings:

A "Properties" embedding. When we process the Azure JSON schema/Swagger we manufacture a "Spec"
type that doesn't exist in the JSON schema/Swagger. In the JSON schema the resource itself must comply with ARM resource requirements, meaning that all of the RP specific properties are stored in the "Properties" property which for the sake of example we will say has type "R1Properties". Other resources which have a property somewhere in their type hierarchy with that same "R1Properties" type are actually embedding the R1 resource entirely inside themselves. Since the R1 resource is its own resource it doesn't make sense to have it embedded inside another resource in Kubernetes. These embeddings should really just be cross resource references. This pipeline finds such embeddings and removes them. A concrete example of one such embedding is
v20181001 Microsoft.Networking Connection.Spec.Properties.LocalNetworkGateway2.Properties. The LocalNetworkGateway2 property is of type "LocalNetworkGateway" which is itself a resource. The ideal shape of Connection.Spec.Properties.LocalNetworkGate2 would just be a reference to a LocalNetworkGateway resource.
A subresource embedding. For the same reasons above, embedded subresources don't make sense in Kubernetes. In the case of embedded subresources, the ideal shape would be a complete removal of the reference. We forbid parent resources directly referencing child resources as it complicates the Watches scenario for each resource reconciler. It's also not a common pattern in Kubernetes - usually you can identify children for a given parent via a label. An example of this type of embedding is v20180601 Microsoft.Networking RouteTable.Spec.Properties.Routes. The Routes property is of type RouteTableRoutes which is a child resource of RouteTable.

Note that even though the above examples do not include Status types, the same rules apply to Status types, with the only difference being that for Status types the resource reference in Swagger (the source of the Status types) is to the Status type (as opposed to the "Properties" type for Spec).

Codecov Report

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

:exclamation: Current head b03bf4a differs from pull request most recent head a08ba76. Consider uploading reports for the commit a08ba76 to get more accurate results

@@            Coverage Diff            @@
##             master     #422   +/-   ##
=========================================
  Coverage          ?   63.29%
=========================================
  Files             ?      147
  Lines             ?    10335
  Branches          ?        0
=========================================
  Hits              ?     6542
  Misses            ?     3196
  Partials          ?      597

Impacted Files
Coverage Δ

hack/generator/pkg/astmodel/object_type.go
73.09% <0.00%> (ø)

hack/generator/pkg/astmodel/type_name_set.go
71.87% <37.50%> (ø)

.../pkg/codegen/pipeline_remove_empty_object_types.go
69.11% <69.11%> (ø)

.../pkg/codegen/pipeline_remove_embedded_resources.go
73.94% <73.94%> (ø)

hack/generator/pkg/codegen/code_generator.go
87.60% <100.00%> (ø)

Continue to review full report at Codecov.

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


Change crate prefix from "db-" to "dbs-"

db is a wide-understood as "database".

All existed db have been changed to dbs


Fix log time

A little fix. After this pr, the log would works with time and prefix.
2020/09/27 11:16:25 [REMOTE] Started EndpointManager
2020/09/27 11:16:25 [REMOTE] Starting Proto.Actor server address="<IP_ADDRESS>:8080"
2020/09/27 11:16:25 [REMOTE] Started Activator
2020/09/27 11:16:25 [CLUSTER] Starting Proto.Actor cluster address="<IP_ADDRESS>:8080"
2020/09/27 11:16:25 [CLUSTER] Started kind="Hello" id="partition-Hello"

But there is a question, why not print local time?
https://github.com/AsynkronIT/protoactor-go/blob/b225d28383f2318e0513dfabd22a3037f9043ffd/log/string_encoder.go#L55
/cc @PotterDai  @rogeralsing

👍🏻 many thanks for the fix!


Yellow data truncation indicators can sometimes be extremely thin and hard to notice

width of the yellow data truncation indicators are dependent on the range of the data. sometimes the width is so narrow that the yellow truncation bars are very hard to notice. See this example from MALED

It appears the size of the truncation warning area is impacted by the log scale option.

Just for a record, I have worked on this but I realized later that this was already addressed as a part of Bob's additional works with my original PRs, https://github.com/VEuPathDB/web-eda/pull/1241 & https://github.com/VEuPathDB/web-components/pull/371.
Here is a screen capture of the above example with the PRs. They look good to me

Sorry @moontrip

Yellow bars are now much more obvious on log scale


Last Event Video is not working

The Last Event Video Feature is not working for me:

eufy-security.0
2021-06-01 12:29:43.014
error
(4989) Station: T8411P2020000000 command CMD_DOWNLOAD_VIDEO failed with error: ERROR_OPEN_FILE_FAIL (-111)

eufy-security.0
2021-06-01 12:29:43.013
debug
(4989) [Station.onCommandResponse] Got p2p command response [{"station":"T8411P2020000000","commandType":1024,"channel":0,"returnCodeName":"ERROR_OPEN_FILE_FAIL","returnCode":-111}]

eufy-security.0
2021-06-01 12:29:43.013
debug
(4989) [P2PClientProtocol.handleData] Station T8411P2020000000 - Result data for command received [{"messageState":{"sequence":18,"command_type":1024,"nested_command_type":1024,"channel":0,"data":{"ty

eufy-security.0
2021-06-01 12:29:43.012
debug
(4989) [P2PClientProtocol.handleData] Station T8411P2020000000 - Received data [{"commandIdName":"CMD_DOWNLOAD_VIDEO","commandId":1024,"resultCodeName":"ERROR_OPEN_FILE_FAIL","resultCode":-111,"messag

eufy-security.0
2021-06-01 12:29:43.011
debug
(4989) [P2PClientProtocol.parseDataMessage] Station T8411P2020000000 - Received data [{"seqNo":18,"header":{"commandId":1024,"bytesToRead":132,"channel":0,"signCode":0,"type":1},"bytesRead":132,"bytes

eufy-security.0
2021-06-01 12:29:43.010
debug
(4989) [P2PClientProtocol.handleMsg] Station T8411P2020000000 - DATA DATA - received from host <IP_ADDRESS>:11311 - Processing sequence 18...

eufy-security.0
2021-06-01 12:29:42.999
debug
(4989) [P2PClientProtocol.handleMsg] Station T8411P2020000000 - ACK DATA - received from host <IP_ADDRESS>:11311 for sequence 18

eufy-security.0
2021-06-01 12:29:42.987
debug
(4989) [P2PClientProtocol._sendCommand] Sending p2p command... [{"station":"T8411P2020000000","sequence":18,"commandType":1024,"channel":0,"retries":0,"messageStatesSize":1}]

eufy-security.0
2021-06-01 12:29:42.984
debug
(4989) [Station.startDownload] P2P connection to station T8411P2020000000 present, download video path: /media/mmcblk0p1/Camera00//media/mmcblk0p1/Camera00/20210601122443.dat.dat

@ChristopherGier Please try latest version (0.6.0) and let me know.


Update Scala 3 version to 3.0.0-M1

Connected to https://github.com/scalameta/munit/issues/240
Seems we are no longer getting RC versions, so I reverted back to having single stable Dotty version.

I guess this will not be that easy after all :(  I will take a further look tomorrow, but it seems that we are now printing full names with packages. If anyone wants to fix it today, you can just push to this PR with a fix.

Is this related? https://github.com/lampepfl/dotty/issues/9716

@mpilquist might be, but that issue was also present in the previous versions, so it shouldn't actually change here 🤔

I just noticed this commit in community build -- trying it now: https://github.com/dotty-staging/munit/commit/1e90e9707e02c41049489849dd0e002d48d4b498

Alright figured this one out -- nothing changed in Dotty w.r.t. showing type prefixes. The bug is that we need to change def isDotty in BaseSuite to account for the version number change.

Aha, nice catch @mpilquist!

Alright figured this one out -- nothing changed in Dotty w.r.t. showing type prefixes. The bug is that we need to change def isDotty in BaseSuite to account for the version number change.

Thanks! Good catch! I updated the PR and also changed the MacroCompat a bit based on the commit you mentioned before.

I will merge and release first thing tomorrow (just in case there is an issue) if no one objects.

Looks good to me. Once munit publishes, we'll be able to start building the various Typelevel libraries. The sooner the better but if you want to wait until tomorrow, that's great. :)

Seems we are no longer getting RC versions, so I reverted back to having single stable Dotty version.

I definitely object. It's very very difficult for downstream projects to juggle incompatibilities as the ecosystem updates. Maintaining builds for the two most recent Dotty releases (whenever possible) makes this significantly easier since it allows libraries to take the upgrade in chunks, particularly if and when munit itself makes changes. Publishing for the latest two dotty releases ensures that users are able to split the upgrade pain into two steps: upgrade munit, then upgrade dotty.
Meanwhile, from the perspective of a library maintainer, not dropping the previous Dotty release is usually completely painless. Sometimes it has to be done, and particularly with ScalaJS shenanigans I can see merit to dropping 0.27.0-RC1, but I would strongly recommend that publication be for Mn and M(n-1) from this point forward. We're about to go through the most convoluted and painful cross-publication coordination effort in Scala's history; the least we can do is try to learn from what has made all of the other (otherwise simpler) migrations difficult at times.

Seems we are no longer getting RC versions, so I reverted back to having single stable Dotty version.

I definitely object. It's very very difficult for downstream projects to juggle incompatibilities as the ecosystem updates. Maintaining builds for the two most recent Dotty releases (whenever possible) makes this significantly easier since it allows libraries to take the upgrade in chunks, particularly if and when munit itself makes changes. Publishing for the latest two dotty releases ensures that users are able to split the upgrade pain into two steps: upgrade munit, then upgrade dotty.
Meanwhile, from the perspective of a library maintainer, not dropping the previous Dotty release is usually completely painless. Sometimes it has to be done, and particularly with ScalaJS shenanigans I can see merit to dropping 0.27.0-RC1, but I would strongly recommend that publication be for Mn and M(n-1) from this point forward. We're about to go through the most convoluted and painful cross-publication coordination effort in Scala's history; the least we can do is try to learn from what has made all of the other (otherwise simpler) migrations difficult at times.

I can add back 0.27.0-RC1 for sure, might have rushed with dropping it.

@tgodzik feel free to merge and release when this PR is ready!

@djspiewak I added back the 0.27.0-RC1 version. If everything runs ok, I will merge and release it if no one objects?


add «snabbdom in the wild» section

tx!

Hello @amirouche. Adding Vue is a great idea. But there already is a section called "Structuring applications". Couldn't we merge this new section with that section under a common name?

Héllo @paldepind, it's done :)


Too many arguments.

Hi there, trying to generate CRUD, but I get the following error (please see below):
One of my colleagues tried it and it works 100% on his side. Any help will be much appreciated.
Thank you for the great contribution.
php artisan crud:generate Clients --fields=“organization_name#string#required, registered_name#string#required, organization_type_id#integer#required, registration_number#integer#required, vat_number#string, vendor_number#string, switchboard_number#string#required, fax_number#string, company_email_address#string#required, physical_address#text, postal_address#text#required, industry_id#integer, country_id#integer#required, province_id#integer#required, city_id#integer#required, suburb#string#required, notes#text” --route=yes --view-path=“backend” --route-group=“backend”
Error:
←[37;41m                                                          ←[39;49m ←[37;41m  [Symfony\Component\Console\Exception\RuntimeException]  ←[39;49m ←[37;41m  Too many arguments.                      ←[39;49m ←[37;41m                                                          ←[39;49m

Hi @louiscoetzee
Glad to hear that you liked it :)
I've just run your given command everything seems okay to me.
Please try again with the below command.
php artisan crud:generate Clients --fields="organization_name#string#required, registered_name#string#required, organization_type_id#integer#required, registration_number#integer#required, vat_number#string, vendor_number#string, switchboard_number#string#required, fax_number#string, company_email_address#string#required, physical_address#text, postal_address#text#required, industry_id#integer, country_id#integer#required, province_id#integer#required, city_id#integer#required, suburb#string#required, notes#text" --route=yes --view-path="backend" --route-group="backend"

Make sure you use double quotes in proper format and full command in single line.

Hi @sohelamin thank you for your prompt reply, that was the issue.


routing: add support for pegged hops in findPaths

The PR addresses #2282
Edited (08-02-2019):
From the CLI queryroutes description:
A series of nodes and channels the route must pass through can optionally
be provided. The node id is mandatory. The channel leading to this node
can optionally be pegged too, otherwise the channel id should be set to 0.
The resulting route is composed of segments connecting between the pegged
nodes. Each segment does not have loops, but the entire path may. The
route selection assures that no edge will be transversed twice at the
same direction.
The alternate routes are stitched from N-1 shortest segment paths and
one alternate segment path.

Below is an example of a query using routing pegs:

lncli queryroutes --pegs='{"hop_pegs": [
            {
                "node_id": "026a52eadd42eabb70e9b0481af7001d299f7d7b41030977bb37a2faac7bbe0012",
                "chan_id": "2043992116101120"
            }
        ]
    }' "034a15c028970d4070c60f532018cfdb943b584ba267c83fe333ef1ad70b10feaf" 333

Note the single quote used to encapsulate the pegs.

Below is the documentation from the unit test added for this feature.
Feedback appreciated.
// TestPeggedRouting tests route selection with pegged
// nodes and channels. Pegging restrict routing to pass through the pegged
// node (and optionally through a channel) while searching for a route
// between source and destination.
// The resulting route is composed of segments connecting between the pegged
// nodes. Each segment does not have loops, but the entire path may. The
// route selection assures that no edge will be transversed twice at the
// same direction.
// The alternate routes are stitched from N-1 shortest segment paths and
// one alternate segment path.
//
//   ┌──────────┐        20         ┌──────────┐
//   │    E     │───────────────────│    D     │
//   └──────────┘        6          └──────────┘
//        |                           |      |
//        |                           |      | d/e
//        | 10                        | 50   | 20
//        | 3                         | 4    | 5
//        |                           |      |
//   ┌──────────┐        60         ┌──────────┐
//   │    B     │───────────────────│    C     │
//   └──────────┘        2          └──────────┘
//        |
//        |
//        | 30
//        | 1
//        |         ┌──────────┐
//        └─────────│     A    │
//                  └──────────┘
//
// The setup is build from symmetric channels whose base fee is
// marked and the fee rate is set to 0. The channel id between
// each node is marked below the rate.
//
// Test 1:
// Find routes from origin (A) to final destination (E) through D.
// Channel 5 disabled.
// A -> *D -> *E
//
// The expected routes are:
// r1: A -> B -> E -> D -> E                    total fees: 50
// r2: A -> B -> C -> D -> E  			total fees: 130
//
// Note that in r1, E is visited twice, before and after D. The
// pegging does not enforce order, i.e. it does not imply that D
// will be reached before E, rather that after D is reached, E
// will be reached.
//
// The following routes should not be returned:
// r1: A -> B -> E -> D -> E -> D -> E          total fees: 90
// r2: A -> B -> E -> D -> C -> B -> E
// reason: Edges cannot be transversed twice in the same direction.
// The following route is not returned:
// r1: A -> B -> C -> D -> C -> B -> E		total fees: 230
// Eventhough no edge is transversed twice at the same direction
// due to the route stitching selection. This route is similar to
// a route stiched from the 2nd best A -> D with the 2nd best
// D -> E.
//
// Test 2:
// Find routes from origin (A) back to itself through (C) and (E).
// Channel 5 disabled.
// A -> *C -> *E -> *A
//
// The expected routes are:
// r1: A -> B -> C -> B -> E -> B -> A          total fees: 170
// r2: A -> B -> C -> D -> E -> B -> A		total fees: 170
//
// Note that both routes have the same total fees.
//
// Test 3:
// Find routes back to origin (A) passign through node C through channel 4
// Channel 5 disabled.
// A -> (4)C -> *A
//
// The expected routes are:
// r1: A -> B -> E -> D -> C -> B -> A             total fees: 170
// r1: A -> B -> E -> D -> C -> D -> E -> B -> A   total fees: 190
// r3: A -> B -> C -> D -> C -> B -> A             total fees: 250
//
// Test 4:
// Find routes back to origin (A) passing through node D through
// channel 6 and then node C through channel 4
// Channel 5 disabled.
// A -> (6)D -> (4)C -> *A
//
// The expected routes are:
// A -> B -> E -> (6)D -> (4)C -> B -> A
// A -> B -> E -> (6)D -> (4)C -> D -> E -> B -> A
// A -> B -> C -> D -> E -> (6)D -> (4)C -> B -> A
//
// Test 5:
// Find routes back to origin (A) passing through node D through
// channel 6 and then node C through channel 4
// Channel 5 enabled.
// A -> (6)D -> (4)C -> (2)B -> A
//
// The expected routes are:
// A -> B -> E -> (6)D -> (4)C -> (2)B -> A
// A -> B -> C -> (5)D -> E -> (6)D -> (4)C -> (2)B -> A
// A -> B -> C -> (4)D -> E -> (6)D -> (4)C -> (2)B -> A
//

Pegging of both nodes and channels is working. The error in the integration is in the data loss protection, and I believe is unrelated to this code.

Since findPaths is going to be deprecated (mentioned here: #2497) by 0.7 release, most of the code changes here will be obsolete.  Pegging hops would not be compatible with the new queryroutes using any-to-any queries since one cannot stitch together routes in the same way one can stitch together paths.  In my mind, pegging hops requires multiple iterations of Djikstra's and might require a new pathfinding algorithm.  I can't think of any way we could pass in a "restriction" that makes findPath go through a hop without heavily modifying the algorithm itself.

Closing this for now as we've gone with an alternative approach (edge white/black listing).


shows disabled tabs after click, onTabChange return value ignored

when hovering over disabled tabs, the mouse pointer changes as if it were inactive, but in fact, if one clicks on a disabled tab, the content will still be shown to the user.
Another aspect of the same problem: false return values of onTabChange are ignored.

I have encountered the same problem, and I changed 'shown' to 'show', and bind 'onTabChange' and 'onTabClick' event.


Make sequence file support work in pyosmium-get-changes

Sigh, this stuff urgently needs some tests.


Design Logo for #50DaysOfJavascript

Description
We are in need of a distinctive and creative logo for #50DaysOfJavaScript, our community-driven open-source initiative. This logo will serve multiple purposes, including being used as a favicon for our website and featured prominently on promotional posters.
Objective
The objective of this issue is to commission the design of a versatile logo that embodies the spirit of #50DaysOfJavaScript and can be effectively used in various contexts, such as on our website, in social media posts, and on printed promotional materials.
Design Requirements

The logo should prominently feature the text "#50DaysOfJavaScript" in a clear and stylish font.
It should incorporate visual elements that represent JavaScript or coding, such as code snippets, JavaScript-related icons, or programming symbols.
The design should be scalable and suitable for various sizes, from a small favicon to a larger poster.
Use a color scheme that is visually appealing and aligns with the overall theme of the initiative.

Additional Information

Website URL (for favicon): 50daysofjavascript.netlify.app
Planned use for posters and promotional materials.

Note: Your creativity is highly valued, and your design will be an integral part of our project's identity. We appreciate your contribution to making #50DaysOfJavaScript visually appealing and memorable.
Thank you.

@vinitshahdeo can u assign me this issue

@Tejoooo Sure, please note that there's an open PR for the logo though. It'd be great if you could collaborate with them.
cc/ @deeksharungta


Missing ./data/BERT_tokenizer.pkl file

I want to run only the "Fine-tuning on SemEval2010 Task 8" section (main_task.py file). However, I get the following error:
FileNotFoundError: [Errno 2] No such file or directory: './data/BERT_tokenizer.pkl'
Can anyone tell me where I can get this file?

This is the whole stack trace:
Traceback (most recent call last):
File "main_task.py", line 50, in
net = train_and_fit(args)
File "/content/BERT-Relation-Extraction/src/tasks/trainer.py", line 33, in train_and_fit
train_loader, test_loader, train_len, test_len = load_dataloaders(args)
File "/content/BERT-Relation-Extraction/src/tasks/preprocessing_funcs.py", line 319, in load_dataloaders
save_as_pickle("%s_tokenizer.pkl" % model_name, tokenizer)
File "/content/BERT-Relation-Extraction/src/misc.py", line 22, in save_as_pickle
with open(completeName, 'wb') as output:
FileNotFoundError: [Errno 2] No such file or directory: './data/BERT_tokenizer.pkl'

You may run python main_task.py  with default values first to generate the BERT_tokenizer.pkl

I'm trying to run the main_task.py but its showing an error, Can someone explain how and in which order to execute the files?
Traceback (most recent call last):
File "d:\6th Sem\NLP\Project\BERT-Relation-Extraction-master\main_task.py", line 50, in
net = train_and_fit(args)
File "d:\6th Sem\NLP\Project\BERT-Relation-Extraction-master\src\tasks\trainer.py", line 33, in train_and_fit
train_loader, test_loader, train_len, test_len = load_dataloaders(args)
File "d:\6th Sem\NLP\Project\BERT-Relation-Extraction-master\src\tasks\preprocessing_funcs.py", line 319, in load_dataloaders
save_as_pickle("%s_tokenizer.pkl" % model_name, tokenizer)
File "d:\6th Sem\NLP\Project\BERT-Relation-Extraction-master\src\misc.py", line 22, in save_as_pickle
with open(completeName, 'wb') as output:
FileNotFoundError: [Errno 2] No such file or directory: './data/BERT_tokenizer.pkl'

Still its showing the same error

Requires SemEval2010 Task 8 dataset, available here. Download & unzip to ./data/ folder.

I have added instructions as suggested to download & unzip the data


Add guide to run Piped on CloudRun

What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Does this PR introduce a user-facing change?:

NONE

🚀
/lgtm

Well documented. There you go!
/approve


update homepage to use https://

if you visit https://github.com/sourcelair/xterm.js/ the homepage at the top is set to http://xtermjs.org/ ... should update that to https:// :)

Done, thanks! 😄


Create design system

I'd like to try a css custom properties based design system.
Color palette, spacing, header sizes, and base element styles need to be decided on

@codyarose I personally think for colors and fonts this would be great. Otherwise for spacing, sizes, etc. I think we can go with such styles in the different styled components created with emotion. :+1:

@codyarose I personally think for colors and fonts this would be great. Otherwise for spacing, sizes, etc. I think we can go with such styles in the different styled components created with emotion. :+1:

I'd like to try a css custom properties based design system.
Color palette, spacing, header sizes, and base element styles need to be decided on

By Base element styles you mean create a box component, a form component -label and input with correct spacing.. a title component etc?

I'd like to try a css custom properties based design system.
Color palette, spacing, header sizes, and base element styles need to be decided on

By Base element styles you mean create a box component, a form component -label and input with correct spacing.. a title component etc?

I'd like to try a css custom properties based design system.
Color palette, spacing, header sizes, and base element styles need to be decided on

By Base element styles you mean create the styles for a box component, a form component -label and input with correct spacing.. a title component etc?

I was referring to the base elements like h1-6,p , and inputs. So basically a good normalize or reset with smart defaults so everything is starting from the same point across all browsers.

I'd like to try a css custom properties based design system.
Color palette, spacing, header sizes, and base element styles need to be decided on

By Base element styles you mean create the styles for a box component, a form component -label and input with correct spacing.. a title component etc?

I was referring to the base elements like h1-6,p , and inputs. So basically a good normalize or reset with smart defaults so everything is starting from the same point across all browsers.

@codyarose following on from @emma-r-slight 's comment in Discord - are you thinking something along the lines of what https://every-layout.dev/rudiments/global-and-local-styling/ suggests?

@codyarose following on from @emma-r-slight 's comment in Discord - are you thinking something along the lines of what https://every-layout.dev/rudiments/global-and-local-styling/ suggests?

@nobrayner Yeah, I guess something along the lines of that, minus the xml "stack-l" part

@nobrayner Yeah, I guess something along the lines of that, minus the xml "stack-l" part


Shuffle=True

I saw this line,
trainloader = data.DataLoader(train, batch_size=64, shuffle=True, num_workers=4)
for timeseries, should shuffle be True ? Just curious, i have not shuffled the data in sliding window models,
And also these lines are interesting, you really do shuffle the data.
permutation = np.random.RandomState(98841).permutation(total_seqs)
        test_size = int(0.2 * total_seqs)
        self.test_x = all_x[permutation[:test_size]]
        self.test_y = all_y[permutation[:test_size]]
        self.test_t = all_t[permutation[:test_size]]
        self.train_x = all_x[permutation[test_size:]]
        self.train_t = all_t[permutation[test_size:]]
        self.train_y = all_y[permutation[test_size:]]

I am student still learning. :-)

Hi,
the training data array has 3 axes: [samples, timesteps, features] and the DataLoader shuffles along the first axis, i.e., shuffles the ordering of the sequences. The shuffling is required to make sure we are performing stochastic gradient descent, i.e., during each epoch iterating over the training data by a different ordering than the ordering of the previous epochs.
The code block you are quoting is not about the training process but the test-training split. When we collect the data we might collect the samples of class A first, then the samples of class B and so on. Later when we split the data into training-validation-test set we have to shuffle the data first to ensure the samples of class A,B,... between the splits are uniformly distributed. If we wouldn't shuffle here, then our test set would consist only of samples of class A, whereas no class A samples would be in the training set.

Oh ok. I have another question, I am asking these questions because i am dealing with Time series data, and the time is uneven, not equidistant. For example, a data feed about stock symbol and the volume and price. I see that the time component is removed and only the time difference between two data points are taken.
                    elasped_sec = 0.05
                else:
                    elasped_sec = float(millis - last_millis) / 1000.0
                elasped = elasped_sec * 1000 / millis_mapped_to_1

I have seen in places where they convert time into a frequency component, such as time of day, day of year/month (cos/sin). I am just curious to learn more about ODE and how that can be applied to uneven timeseries data involving timestamp.

There are several approaches on how to deal with irregularly sampled time-series. For instance, the simplest solution is to just treat the elapsed-time input as an additional input feature and then use a standard sequence processing model such as an LSTM. This works actually quite well, but other solutions that add an inductive bias for the time input to the model perform even better.
One of such options is to transform the time into some spectral domain as you suggested. The Phased-LSTM is doing exactly that.
Another method is to use ODEs: Parametrized the ODE by a neural network and use the time input as the solution time of the ODE-solver.
The elapsed-time vs total-passed-time is just a difference in the implementation if you have to solve the ODE from [0,elapsed_time] for [previous-total-time, total-time].

Oh i tried LSTM taking time as frequency component (spectral domain). It was terrible. The problem could be because of the shifting of label values (pre-trained train data). They call it windowing and label shift. I followed what google's team suggested. The performance was really poor/bad. May be i should not shift the label, but predict the values based on the time as input for varies time steps. I will look into other models as well. You can see here as to what i mean by label shift. This is very basic implementation from google.
https://www.tensorflow.org/tutorials/structured_data/time_series#data_windowing
The performance is really poor if someone follows that example.
With respect to ODE, do you think that i should consider total time instead of elapsed time ? I can try spectral domain, not sure how would work. I see one feature component here
series_t.append(elasped)
I am trying to understand your statement there for this one [previous-total-time, total-time] And also time is linearly increasing value like an entropy. This would present problems when we normalize time component. I have gone through Phased LSTM once before, and there are couple of implementations out there. I think that they have implemented Time Gate and gaps are not interpolated but rather considered as dropout. I thought ODE is little advanced compared to Phased LSTM. But it is interesting challenge to figure out best algorithm for Time related problems and to predict something into the future that it had not encountered before.

If you get really bad results with a simple LSTM + time as an additional input baseline, I expect that there is something wrong with the data. For instance, not enough data, bad preprocessing (not normalized features), or maybe you are facing a problem that is difficult to solve in general (think of predicting random noise, which is impossible).
All the fancy time-continuous RNNs (e.g., ODE, Phased-LSTM, CT-GRU) give you a bit better accuracy than the baseline but I wouldn't expect magic improvement. If your baseline doesn't work the problem probably lies somewhere else.

And yes, you are right. This problem is little complex. The data is a regular feed, and it is pretty good from what i have seen. Your code is concise. And Thanks for publishing your implementation. I will try different models and i appreciate your inputs. :pray:


Issue #04 Unittest usage.py file linting

Edited variable names and whitespace in usage.py to comply with flake8 standards

Codecov Report

Merging #24 into master will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master       #24   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            8         8
  Lines           33        33
=========================================
  Hits            33        33

Continue to review full report at Codecov.

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

Add newline at the end of conf.py


Terms that should not be localized

This article contains terms that should not be localized and some of those are being over-localized:

Reserved keywords in headings (e.g. "@try, catch, finally")
Reserved keywords in bulleted lists (under headings "Razor reserved keywords")
Directory structure in bulleted list (under heading "Inspect the Razor C# class generated for a view")
It would be great if those terms can be blocked from localization by using either in-line code, or no-loc custom syntax.

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

ID: b87067b2-347c-072d-26c8-5a8c7c9c860b
Version Independent ID: a0b3b70a-3b39-1b5f-a4ce-c41bd2d6b044
Content: razor syntax reference for ASP.NET Core
Content Source: aspnetcore/mvc/views/razor.md
Product: aspnet-core
Technology: aspnetcore-mvc
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

@Rick-Anderson Thank you for the quick fix on the reserved keywords!
There are also directory structures (folder names) in bulleted list under the heading "Inspect the Razor C# class generated for a view" that are being over-localized.
Could you please also take a look at those?

@JasonCard  sorry I missed that. Fixed in #18787

Thank you again for the quick fix!


HmIP-SWDO (window and door sensors) - Device Class

DONT'T DELETE THIS.
Is your feature request related to a problem? Please describe.
I would really appreciate, if the HmIP-SWDO sensors can be classified as "device_class: door"
Within the HmIP Integration of HomeAssistant, these devices have the device_class: door attribute, and therefore, there states are: Open / Closed.
Unfortunately, after adding some of my Sensors to the Local CCU, they don't have this device class anymore and only reporting ON / OFF

HmIP Cloud integration - Sensor: HmIP_SWDO_I

HmIP CCU integration - Sensor: HmIP_SWDO_I

HmIP CCU integration - Sensor: HmIP_SWDO_PL

Describe the solution you'd like
add the device_class: door to the HmIP_SWDO Sensors
Describe alternatives you've considered
Additional context

Good catch. You found a bug introduced by a previous refactoring.
Version 1.13.6 should fix it.
The default device_class for such sensors here is window, but you can customize it in HA

thanks :)
Just updated to 1.13.7 and it is fixed 👍


What's the best way to limit results in a joined relation using withGraphFetched/withGraphJoined?

For example,
Shop.query().select('*').withGraphJoined('products.variants')

I notice that putting a limit on the end will limit the variants to two, and limits the products to 1, which is confusing:
Shop.query().select('*').withGraphJoined('products.variants').limit(2)
[
    {
       ...shopData,
      products: [{
         // 1 result
         variants: [{}] // 2 results total
     }]
   }
]

I want to be able to use withGraphJoined (or maybe withGraphFetched in some circumstances) to be able to limit each level of relations. I know that the documentation says that fetching relations will hinder the use of offset/join; but I want to know what people are doing in practice to implement this kind of functionality then. Thanks.

Try making an SQL query which gets at most 10 shops and then joins each of them on at most 5 products. You'll see that it becomes a really complex query which differs per DB dialect. It doesn't seem viable to support this, I haven't seen any ORM that does. I'm not sure what your use case is but it sounds pretty rare.

I notice that putting a limit on the end will limit the variants to two, and limits the products to 1, which is confusing:

Basic SQL knowledge can tell you why this happens, you're joining multiple tables and returning the first two rows. If the first product has multiple variants, it's going to return those rows.

but I want to know what people are doing in practice to implement this kind of functionality then. Thanks.

Build it themselves with the Knex query builder.

Try making an SQL query which gets at most 10 shops and then joins each of them on at most 5 products. You'll see that it becomes a really complex query which differs per DB dialect. It doesn't seem viable to support this, I haven't seen any ORM that does. I'm not sure what your use case is but it sounds pretty rare.

Well I don't know if it's that rare. It seems like a common use case that you'd want to limit the number of results on a relation pulled in.

Build it themselves with the query builder.

Yeah, this issue is because I don't know how to do that. Thank you.

If you can show us the query you want in SQL, we can help you translate it to the querybuilder. If you can't, it's probably better to ask on Stackoverflow as that question isn't really related to Objection.

I suppose I'm hopeless, since I am clueless as to what the SQL would be.

@nikkwong I'm facing the same issue as well. Did you find a solution?


Make client-side timeout when talking to API Server configurable

We have a few hundreds of CRDs in our clusters, and are seeing Config Sync reconciliation fail with API Server timeouts due to the client-side timeout parameter being too aggressive.
This makes the client-side timeout for API server requests configurable under .spec.override (next to things like gitSyncDepth and statusMode; if you'd like it to be somewhere else, feel free to recommend something and I'll adjust the PR). I tried to mimic patterns already in use for other parameters, both in implementation and tests (but oh, god, does this test suite need some work...!) so I hope it looks OK.
I added two new tests for the actual expansion of config into environment variables, because I realized that all the tests of the public API that already existed were using the production implementation also to create the expected results, which in practice means that a bug there would never be exposed by the tests. There's room to add a lot more test cases in these two, to ensure that the set of expected env vars in the all the other tests match the intention. I'll leave that work for someone else 😅
A couple of questions:

Given that 1.13 was released quite recently, I expect that 1.14 is still a few weeks out. What's the easiest way I can re-generate all the manifets and locally build a Docker image to use in a deployment of Config Sync to test this out in one of our clusters, and see if it works?
I've run make generate; are there any other code-generation commands I should run?
Should I - and if so, how do I - write a changelog entry somewhere?

/ok-to-test

/retest

The e2e test that failed before seems to have passed on retest without any changes on my part. Is it just flaky?

/retest

Given that 1.13 was released quite recently, I expect that 1.14 is still a few weeks out. What's the easiest way I can re-generate all the manifets and locally build a Docker image to use in a deployment of Config Sync to test this out in one of our clusters, and see if it works?

You can build and install Config Sync from source following https://github.com/GoogleContainerTools/kpt-config-sync/blob/main/docs/installation.md#building-and-installing-from-source.

Should I - and if so, how do I - write a changelog entry somewhere?

We don't have a changelog.

The changes in this PR look good. The default client-side timeout is also used in the nomos CLI. Do you plan to update the nomos as well?

I didn't have any plans to, at this time, no. We have too many syncs for e.g. nomos status to be particularly useful, so I don't use it much - but when I do, I use it from my local environment, which typically will have an already warmed-up API discovery cache from previous kubectl usage, which means it's probably a rare problem in practice even for users who use nomos more regularly.
Of course, if you'd like nomos to support this for consistency, I can add that in here anyway.

Of course, if you'd like nomos to support this for consistency, I can add that in here anyway.

Yes, we would like the CLI to have the same behavior as the reconciler. It's okay to make the change in a separate commit.

/retest


Bugfix: Banana time and text don't get updated in the table

When banana time or the message for banana time (also referred to as "banana text") are updated in the admin page, the banana time announcement in the announcements table does not update until the page is refreshed. This is a bug and needs to be fixed so that when an administrator updates banana time or the banana time message, the change is reflected in the table.
This will require modifying the JavaScript in admin.js to asynchronously update the admin web page when a successful response is received. Other files may need modifying (the HTML or the Python code) to enable this capability.
As part of this task, I would also like the including of the bootstrap css file to be removed from the <head> in index.html. I am pretty sure that none of the bootstrap classes are utilised in index.html anymore, making including them redundant. Please double check removing it doesn't effect the appearance of the UI before doing so.
Done:

The banana time announcement in the announcements table on the admin page gets updated asynchronously when either the banana time or banana text is updated
PROVIDED IT IS NOT BEING USED the include for the bootstrap css file has been removed from index.html

This issue is no longer necessary since the changes to the admin UI from #24 have been merged


ROI selection to registration metadata

Wondering about what form we are aiming for the input to this pipeline to be? Ideally we hope that the start co-ordinates for registration of a VOI can be encoded into the metadata for the reconstructed VOI. We would also need to know the path or name for the global overview image volume that it is being registered to.

I think it would be :

NAME_OF_GLOBAL (not sure about the path since it will not be true once on HOA website and can be a bit of a security threat)
x
y
z
With x, y, z being the coordinates that are took directly during the excel conversion and added to the metadata through the macro. So we'll have directly the coordinate in pixel of the subvolume compared to the global volume


(Arch discussion required) Improve handling in contacts widget for atSigns which no longer exist

Which at_widget package you want to add enhancement?
at_contacts_flutter
On what platforms do you want to add enhancement?
Android, iOS, Windows, MacOS, Linux
Is your feature request related to a problem?
See https://github.com/atsign-foundation/at_client_sdk/issues/458#issuecomment-1085469918 for background
Describe the solution that you'd like
No response
Describe alternatives that you have considered
No response
Additional context
No response

@VJag as you were involved in the discussion on the original bug where it was suggested that we should improve the handling in the contacts widget, please could you re-familiarize yourself with the context so we can perhaps discuss this in one of next week's architecture calls?


fix: running demo app on Android

@rultor merge it.

@rultor merge it.

@rafamizes OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge it.

@rafamizes Done! FYI, the full log is here (took me 3min)


Category section ->  image changes

Pull Request Checklist

[x] I have added screenshots and videos to show before and after the working of my code.

https://github.com/user-attachments/assets/26eb4466-cf83-4b15-8960-fb6c7c7ef732

[x] I have synced the latest fork with my local repository and resolved any conflicts.

this is PR number kindly mention issue number

@LatikaAdhikari064 i closed this issue with a valid reason , you should not have worked and made this PR , nevertheless since you have done the changes i will be merging this as of now , kindly make sure to wait for the issue to be assigned before working on a PR !


add instaboost in coco.py

@GothicAi What is the difference between the albu and instaboost? Can instaboost be mixed with other data augmentation methods in detection tasks like coco ? Please give me some advice？

@whuhangzhang Hi, instaboost is a data augmentation method introduced in this paper "InstaBoost: Boosting Instance Segmentation via Probability Map Guided Copy-Pasting". It can be used together with other data augmentation methods together.

Notice:

To reduce the installation burden, by default the code will not install Instaboostfast, the users need to install it manually if they need to use the Instaboost augmentations. The code will raise an error and provide installation instructions if the Instaboost is needed but not installed for convenience.
The mmdet team will reimplement all the configs in the codebase when they re-benchmark the codebase after code refactoring. Therefore, only the configs of r50 models are kept to reduce the number of models for re-benchmarking. The results of all the models the authors implemented remain in the README and the users can implement the config of big models by themselves based on the r50 configs.
For now, the models are maintained by the authors in Baidu/Google drives (many thanks), we will provide new models in the future (maybe after re-benchmarking).

Hi @GothicAi ！First of all, we want to express our gratitude for your significant PR in the mmdetection project. Your contribution is highly appreciated, and we are grateful for your efforts in helping improve this open-source project during your personal time. We believe that many developers will benefit from your PR.
We would also like to invite you to join our Special Interest Group (SIG) private channel on Discord, where you can share your experiences, ideas, and build connections with like-minded peers. To join the SIG channel, simply message moderator— OpenMMLab on Discord or briefly share your open-source contributions in the #introductions channel and we will assist you. Look forward to seeing you there! Join us ：https://discord.gg/raweFPmdzG
If you have WeChat，welcome to join our community on WeChat. You can add our assistant ：openmmlabwx. Please add "mmsig + Github ID" as a remark when adding friends：）
Thank you again for your contribution❤


how fix this

Please provide full stack trace and xaml to repro.

Please also update title to be more detailed

Event Type Moniker	Event	Time	Duration	Thread
Exception thrown: 'System.InvalidCastException' in System.Private.CoreLib.dll ("Unable to cast object of type 'NodeEditor.ViewModels.NodeViewModel' to type 'NodeEditor.Model.IPin'.") Exception thrown: 'System.InvalidCastException' in System.Private.CoreLib.dll ("Unable to cast object of type 'NodeEditor.ViewModels.NodeViewModel' to type 'NodeEditor.Model.IPin'.") Hyperlink: Activate Historical Debugging	5.00s		[8608] Main Thread

One of the important things in this project is to enlarge the node and reduce it
Please attention

Event Type Moniker Event Time Duration Thread Exception thrown: 'System.InvalidCastException' in System.Private.CoreLib.dll ("Unable to cast object of type 'NodeEditor.ViewModels.NodeViewModel' to type 'NodeEditor.Model.IPin'.") Exception thrown: 'System.InvalidCastException' in System.Private.CoreLib.dll ("Unable to cast object of type 'NodeEditor.ViewModels.NodeViewModel' to type 'NodeEditor.Model.IPin'.") Hyperlink: Activate Historical Debugging 5.00s [8608] Main Thread

Please show complete xaml and code

Try there

One of the important things in this project is to enlarge the node and reduce it
Please attention


[3.0] fix #10042, ignore overlapping lock exception and print log

fix #10042

Codecov Report

Merging #10048 (cd65dab) into 3.0 (693965a) will decrease coverage by 0.57%.
The diff coverage is 27.27%.

@@             Coverage Diff              @@
##                3.0   #10048      +/-   ##
============================================
- Coverage     65.74%   65.17%   -0.58%
+ Complexity      319      294      -25
============================================
  Files          1220     1220
  Lines         53137    53130       -7
  Branches       8056     8028      -28
============================================
- Hits          34934    34626     -308
- Misses        14393    14687     +294
- Partials       3810     3817       +7

Impacted Files
Coverage Δ

...pache/dubbo/registry/support/AbstractRegistry.java
71.18% <27.27%> (-4.41%)
:arrow_down:

...luster/router/script/ScriptStateRouterFactory.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...zookeeper/curator/CuratorZookeeperTransporter.java
0.00% <0.00%> (-100.00%)
:arrow_down:

...pc/cluster/router/file/FileStateRouterFactory.java
0.00% <0.00%> (-80.96%)
:arrow_down:

...o/rpc/cluster/router/script/ScriptStateRouter.java
0.00% <0.00%> (-67.31%)
:arrow_down:

...ting/zookeeper/curator/CuratorZookeeperClient.java
16.34% <0.00%> (-51.93%)
:arrow_down:

...dubbo/remoting/zookeeper/ZookeeperTransporter.java
55.55% <0.00%> (-33.34%)
:arrow_down:

.../remoting/api/SingleProtocolConnectionManager.java
61.53% <0.00%> (-23.08%)
:arrow_down:

...nt/metadata/ServiceInstanceHostPortCustomizer.java
65.78% <0.00%> (-21.06%)
:arrow_down:

.../apache/dubbo/rpc/filter/ProfilerServerFilter.java
62.85% <0.00%> (-20.00%)
:arrow_down:

... and 55 more

Continue to review full report at Codecov.

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


libretro: Fix ios-arm64/tvos-arm64 toolchain setup

Also iOS was assuming ios9 (armv7) only.

Looks good to me, thanks for the fix!


Exiting with errors

Build log
TOO SLOW! does that mean I can just exclude the test on s390x?

Can you start by just re-running the test?  That test just has threads sleep for a while, so it's likely a false negative due to the test machine probably doing other stuff at the same time?

This is inside the whole rpm build on Fedora infrastructure, so I have no control over other processes running at the same time.

This is inside the whole rpm build on Fedora infrastructure, so I have no control over other processes running at the same time.

Understood, which is why the occasional false failure is seen on timing-dependent tests.  The question is how occasional it is.  :)

Let me rerun it.

Seems sporadic.


Alt-tab/Switching windows causes full-screen black flash

With BHUD Frame Limiter set to Sync With Game.
WIth other BHUD Frame Limiter settings menus still flash.
BHUD Vsync doesn't seem to change the behavior.
GW2 settings: Windowed Fullscreen, frame limiter unlimited, FPS 60-80

This should no longer be happening.


Refactor source file structure

Mostly follows https://github.com/apache/incubator-kvrocks/issues/977#issuecomment-1278446623, except:

log_collector and tls_util is moved to network/
add task_runner to common/

log_collector is not a network thing, and i think it should be put under common

log_collector is not a network thing, and i think it should be put under common

I think both common and network is ok, I put it into network because I find that this file relies on redis_reply and is using redis protocol. I will move it to common.

@PragmaTwice  log_collector is not a network-related thing, it is a statistical thing, how about adding a stats directory with log_collector.h and stats.h or even redis_disk.h (or can rename it disk_stats.h?)

@PragmaTwice log_collector is not a network-related thing, it is a statistical thing, how about adding a stats directory with log_collector.h and stats.h or even redis_disk.h (or can rename it disk_stats.h?)

Greate idea. I will do it.

geohash.h file appears to be used only by redis_geo.h. I don't think it's appropriate to put it in storage. Can we just put it inside types?

Done. Current structure:
$ tree src
├── cluster
│   ├── cluster.cc
│   ├── cluster.h
│   ├── redis_slot.cc
│   ├── redis_slot.h
│   ├── replication.cc
│   ├── replication.h
│   ├── slot_import.cc
│   ├── slot_import.h
│   ├── slot_migrate.cc
│   └── slot_migrate.h
├── commands
│   ├── redis_cmd.cc
│   └── redis_cmd.h
├── common
│   ├── cron.cc
│   ├── cron.h
│   ├── db_util.h
│   ├── encoding.cc
│   ├── encoding.h
│   ├── event_util.h
│   ├── fd_util.h
│   ├── parse_util.h
│   ├── rand.cc
│   ├── rand.h
│   ├── rocksdb_crc32c.h
│   ├── rw_lock.h
│   ├── scope_exit.h
│   ├── sha1.cc
│   ├── sha1.h
│   ├── status.h
│   ├── task_runner.cc
│   ├── task_runner.h
│   ├── util.cc
│   └── util.h
├── config
│   ├── config.cc
│   ├── config.h
│   ├── config_type.h
│   ├── config_util.cc
│   └── config_util.h
├── main.cc
├── network
│   ├── redis_connection.cc
│   ├── redis_connection.h
│   ├── redis_reply.cc
│   ├── redis_reply.h
│   ├── redis_request.cc
│   ├── redis_request.h
│   ├── server.cc
│   ├── server.h
│   ├── tls_util.cc
│   ├── tls_util.h
│   ├── worker.cc
│   └── worker.h
├── stats
│   ├── disk_stats.cc
│   ├── disk_stats.h
│   ├── log_collector.cc
│   ├── log_collector.h
│   ├── stats.cc
│   └── stats.h
├── storage
│   ├── batch_extractor.cc
│   ├── batch_extractor.h
│   ├── compact_filter.cc
│   ├── compact_filter.h
│   ├── compaction_checker.cc
│   ├── compaction_checker.h
│   ├── event_listener.cc
│   ├── event_listener.h
│   ├── geohash.cc
│   ├── geohash.h
│   ├── lock_manager.cc
│   ├── lock_manager.h
│   ├── redis_db.cc
│   ├── redis_db.h
│   ├── redis_metadata.cc
│   ├── redis_metadata.h
│   ├── redis_pubsub.cc
│   ├── redis_pubsub.h
│   ├── scripting.cc
│   ├── scripting.h
│   ├── storage.cc
│   ├── storage.h
│   ├── table_properties_collector.cc
│   └── table_properties_collector.h
├── types
│   ├── redis_bitmap.cc
│   ├── redis_bitmap.h
│   ├── redis_bitmap_string.cc
│   ├── redis_bitmap_string.h
│   ├── redis_geo.cc
│   ├── redis_geo.h
│   ├── redis_hash.cc
│   ├── redis_hash.h
│   ├── redis_list.cc
│   ├── redis_list.h
│   ├── redis_set.cc
│   ├── redis_set.h
│   ├── redis_sortedint.cc
│   ├── redis_sortedint.h
│   ├── redis_stream_base.cc
│   ├── redis_stream_base.h
│   ├── redis_stream.cc
│   ├── redis_stream.h
│   ├── redis_string.cc
│   ├── redis_string.h
│   ├── redis_zset.cc
│   └── redis_zset.h
├── valgrind.sup
└── version.h.in

8 directories, 104 files

geohash.h file appears to be used only by redis_geo.h. I don't think it's appropriate to put it in storage. Can we just put it inside types?

Agree with that.

log_collector is not a network-related thing, it is a statistical thing, how about adding a stats directory with log_collector.h and stats.h or even redis_disk.h (or can rename it disk_stats.h?)

We renamed redis_disk.h to disk_stats.h, do you think that is reasonable? @tanruixiang

We renamed redis_disk.h to disk_stats.h, do you think that is reasonable? @tanruixiang

Yes, I think it's reasonable.

@PragmaTwice After looking detail, it seems server is better than network to replace service. It's my bad that didn't mention this option, others are good to me. I think we can merge it as soon as possible to avoid conflicts.

@PragmaTwice After looking detail, it seems server is better than network to replace service. It's my bad that didn't mention this option, others are good to me. I think we can merge it as soon as possible to avoid conflicts.

Done.

The current diff in github review page seems to be a mess, maybe because I rebase some commits.

Solved by re-rebase and force-push.

@PragmaTwice please rebase on the latest unstable branch.
@ShooterIT @caipengbo could you give a review on this patch? Perhaps we should move it forward in a timely manner to avoid further conflicts.

@PragmaTwice please rebase on the latest unstable branch.

Done.


How to move the XY stage without acquisition

Hello. How can I move my xy stage in a set sequence(for instance from 0-5 at 0.1 interval) without taking an image. I tried to implement "import org.micromanager.MultiStagePosition;" but I get the error that there is no module named 'org'.  In the end, I want to be able to run a section of code and see my xy stage move in a given sequence without the camera turning on. To create my sequence for the x positions, I did the following:
nSteps =5
x_step =0.1
x_end = nSteps*x_step
x_sequence = np.arange(0, x_end + x_step, x_step).reshape(nSteps+1,1)
Thanks

core.set_xy_position()

Thank you for replying, I'm fairly new to pycromanager. I actually tried that before, but with the set of parameters that I mentioned before, when I use core.set_xy_position(), I get error: Exception: Incorrect arguments.
Expected double, double or java.lang.String, double, double
Got
I just want to make sure that I don't have to add any more parameters. Thanks

I am fairly new to pycromanager so please correct me if I'm wrong, but the above code allows me to move the xy stage to a specific position. However, for my application, it is critical that I get to the final x and y position by moving 0.1um each time. How can I make sure of that? if I put x_sequence as the x position inside the parenthesis, I get the key Error 'double'
Thanks

Can you just call it multiple times?
Also, these are more micro-manager usage questions, rather than pycro-manager questions. A better place for them would be the micro-manager part of the image.sc forum

No, because I have minimum 200 positions. Okay, thank you.


hasNotch don't work in Iphone 14

Summary
|
-- | --
Version | react-native-device-info 10.3.0
Affected OS | IOS
OS Version | IOS 16.1
Xcode Version | 14
Device | Iphone 14 pro Simulator
Current behaviorI updated the library version but hasNotch function still return false in a Iphone 14 Simulator.Expected behaviorReturn true in the new iphone 14 lineups.

Maybe you're looking for hasDynamicIsland ?
https://github.com/react-native-device-info/react-native-device-info#hasDynamicIsland
Haven't tried it, but I guess the iPhone 14 should return true for hasNotch, and the iPhone 14 pro should return false for hasNotch, but true for hasDynamicIsland

@enzomonjardin Yes, Thank you. Now It's working me

Maybe you're looking for hasDynamicIsland ?
https://github.com/react-native-device-info/react-native-device-info#hasDynamicIsland
Haven't tried it, but I guess the iPhone 14 should return true for hasNotch, and the iPhone 14 pro should return false for hasNotch, but true for hasDynamicIsland

has been fix from 10.1.2 in a such way:
https://github.com/react-native-device-info/react-native-device-info/releases/tag/v10.1.2
iphone 14: return true
iphone 14 pro: return true
No need to add hasDynamicIsland, but I added it in my app just in case:
export const HAS_NOTCH = DeviceInfo.hasNotch() || DeviceInfo.hasDynamicIsland();


test: make tests work on Windows and in GCE

This PR applies the fix from https://github.com/googleapis/synthtool/pull/240 to this repo.

[x] Tests and linter pass
[x] Code coverage does not decrease (if any source code was changed)
[x] Appropriate docs were updated (if necessary)

Oh wow. 6 Windows tests are failing for real! I'll take a look and fix in a separate PR.

(This one still can be merged, as it allows Windows builds to run on the right version of Node.js)

@bcoe @JustinBeckwith Can you please review the test changes? Looks like everything worked.

It works! @JustinBeckwith can I get one more look here? Thank you!

LGTM after Windows build is passing :)


[8.x] Avoid overwrite on php artisan make:listener command.

Hey, This PR fixes an issue that I running php artisan make:listener.
So if I run it as it is right now it overwrites the file, instead of returning Listener already exists!.
Before:

After:

Thanks,
Francisco.

Comes up every few months. This is a breaking change. Please review other PRs.

Should I push it to the 9.x?
Thanks.


Add NS1 DNS provider.

Hi!
I'd like to be able to use this package with NS1 as DNS provider.
I added integration with their REST API uning their official Go client:
https://github.com/ns1/ns1-go
Please, let me know if there any anything else I need to do to see this Pull Request merged.
Thanks for putting all this code together! :raised_hands:
Signed-off-by: David Calavera<EMAIL_ADDRESS>

Hey there!
Thank you for your time and effort!
Would you be able to support this provider in case bugs or other problems arise with it?
Could you also add your provider to the CLI here so other people are able to use your provider from the CLI?
Thank you!

Would you be able to support this provider in case bugs or other problems arise with it?

Yes, just ping me.

Could you also add your provider to the CLI here so other people are able to use your provider from the CLI?

Absolutely. Do you have any documentation that needs to be changed to? I want to make sure I don't miss anything.

The changes you made are fine. :) Thank you!


iexpress-created exe not modified correctly

"The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more detail."
When the manifest is modified with Resource Hacker, it launches correctly. Here are the two manifests side by side:

Hi,
I have had a look at the code, and tested the following:
copy rcedit.exe rcedit2.exe rcedit.exe --set-requested-execution-level requireAdministrator rcedit2.exe
Opening rcedit2.exe in Resource Hacker, I can see "" and rcedit2.exe works fine in a Administrator level Powershell.
I do not see any error message or issue from my side, maybe the calling script is not executing the set execution level.
Cheers,
Damien

@dmascord Here, try this one. https://anonfile.com/QcC7Lezbn4/env_exe

Thanks for the fix!


Saving documents with embedded collections and default storage strategy leads to inconsistent state between in memory objects and database

Bug Report

Q
A

BC Break
no

Version
2.7.0

Summary
I created a document structure that has two levels of embeddable document collections. Changing those collections by removing objects or setting them again leads to unexpected states being saved to the database. The state inside the database doesn't match the state of the object in memory anymore.
Changing the storage strategy to 'setArray' instead of using the default one resolves the issue
Current behavior
I setup the following example with the objects Bookshelf, Book and Pages.
A bookshelf has a collection of embedded books and a book has a collection of embedded pages.
I noticed unexpected behavior the following cases:
Removing one book from the collection of books and removing a page of another book.
In this case, the book gets removed as expected but the page that should have been removed stays.
Removing one book from the collection of books and resetting the pages of one of the remaining books.
In this case, the book gets removed as expected but the pages of an unrelated book get removed and the pages which were reset are duplicated.
How to reproduce
https://github.com/xammmue/doctrine_odm_save_storage_strategy_issue_poc
I created this repository which includes the classes Bookshelf, Book and Page. I also added some tests with assertions that would match the behavior I expected. The two failing tests test_removeBookAndPage and test_reinitializePagesAndDeleteOtherBook reproduce the (in my opinion) faulty behavior.
Changing the storage strategy for the books and pages to e.g. 'setArray' resolves the problems and all cases I observed work as expected.
Expected behavior
I expected that the state saved in the database matches the state of the objects in memory.

After investigating this for a while, I was able to figure out what exactly is happening for the first failing test (where pages in one book are not removed when a different book is removed entirely):
The default strategy for collections (so embedMany and referenceMany) is pushAll. With this strategy, ODM first uses the $push operator to push new elements in the collection to the document in the database. It then handles deletions by first using $unset on the elements to be deleted, followed by a $pull to extract the values previously set to null by $unset. setArray on the other hand uses the $set operator to update collections in one go - with the downside that any changes to the collection since reading the document are completely ignored. This shouldn't be an issue in many cases, but be aware that in applications with a high write contention it can cause data loss!
Back to the pushAll strategy, the issue arises when running multiple updates in a nested collection. Based on the example above, we have the following document:
{
    "_id": "661cd2c1e676fe8fe10e0fb3",
    "books": [
        { "pages": [ { "pageNumber": 1, "font": "default" } ], "name": "red" },
        { "pages": [ { "pageNumber": 1, "font": "fancy" } ], "name": "green" },
        {
            "pages": [
                { "pageNumber": 1, "font": "beauty" },
                { "pageNumber": 2, "font": "beauty" }
            ],
            "name": "blue"
        }
    ]
}

We now want to remove the red book and page one from the blue book. If we were to write the queries ourselves, it would look something like this. Note that these are NOT the queries ODM generates. First, we use $unset to remove the red book and the first page of the blue book:
{
    "$unset": {
        "books.0": true,
        "books.2.pages.0": true
    }
}

Then, we use $pull to remove the null elements left over in the two collections:
{
    "$pull": {
        "books": true,
        "books.2.pages": true
    }
}

It is at this stage that MongoDB complains:

Updating the path 'books.2.pages' would create a conflict at 'books'

In short, we can't update any collection nested in books at the same time as updating books in a single query but would instead have to make multiple queries. There is logic in place to prevent the error and it works most of the time, but not in this particular case. The reason why MongoDB forbids these kinds of updates is exactly the reason becomes apparent when we look at what ODM actually does. Here's the update that uses $unset:
{
    "$unset": {
        "books.0": true
    }
}

Followed by the $pull:
{
    "$pull": {
        "books": true
    }
}

This is the result of an optimisation made in #1880, which consolidated multiple collection updates into a single query and introduced logic to avoid the conflict error highlighted above. When looking at property paths that have changed (books and books.2.pages), the logic correctly detects that books.2.pages is a subpath of books and thus excludes it to avoid the error. While well-intented,


Free Electron Galerkin FEM in scikitfem

I have the following problem.But I don't know if it is applicable in your module
https://github.com/nikosmatsa/Finite-Differences-Methods-for-PDE-/blob/main/Free Electron Galerkin FEM .ipynb

One comment: support for complex forms was added very recently, you need to pass dtype to BilinearForm. I think there is no example but there is a test somewhere. See https://github.com/kinnala/scikit-fem/blob/master/skfem/assembly/form/form.py#L26 for the implementation.

But is a complex form required here? I see that the bilinear form a contains the imaginary factor κ but only as a simple factor. The bilinear form could be redefined without it as real and then the real assembled matrix multiplied by κ.
This is how it was done for the primitive Orr–Sommerfeld equation in ex29—a complex equation but only essentially involving real forms multiplied by complex coefficients.
https://github.com/kinnala/scikit-fem/blob/91c6c5b90a0cbf1f4d26213a13f0145aa3d90980/docs/examples/ex29.py#L97-L111
I imagine that intrinsically complex forms are possible but I can't think of an example. Do you have one?

I'm not sure but probably something where you have a complex-valued nonhomogeneous material parameter such as in this example: https://doc.freefem.org/tutorials/complexNumbers.html


remove dependencies on git pcap and gyp

I changed the homespun dep to only the utilities. This removes the arp-a dep and no build when installing. It also removed the need for libpcpap-dev requirement.
I also removed the unnecessary community types github dep, it wasn't being used. This removed the dependency on git.
I don't have a honeywell thermostat, so you will need to test this. (I have an ecobee)

I will test this when I get home too!

@mkellsy I have published this on npm as beta, and this is what I get when I try to install
`npm ERR!   I reduced it to just what you are using, but the homespun-utilities package still has a git reference.
  "dependencies": {
    "glob": "^7.0.6",
    "hap-nodejs-community-types": "git+https://github.com/homespun/hap-nodejs-community-types.git",
    "pluralize": "3.0.0",
    "underscore": "1.8.3"
  },

What we need to do is, move the one utility you are using roundTrip to this project and get rid of homespun.

This is published on npm, can't that just be changed under the dependencies? or am i wrong?
hap-nodejs-community-types

Your plugin doesn't even use community types you don't need it.

This pull request is updated with the new roundtrip.js file and homespun removed.

Sorry @mkellsy this is what I get for the output
12/31/2019, 04:24:13] Error: The requested platform 'homebridge-honeywell-home.HoneywellHome' was not registered by any plugin.
    at API.platform (/usr/lib/node_modules/homebridge/lib/api.js:140:13)
    at Server._loadPlatforms (/usr/lib/node_modules/homebridge/lib/server.js:327:45)
    at Server.run (/usr/lib/node_modules/homebridge/lib/server.js:90:36)
    at module.exports (/usr/lib/node_modules/homebridge/lib/cli.js:59:10)
    at Object.<anonymous> (/usr/lib/node_modules/homebridge/bin/homebridge:17:22)
    at Module._compile (internal/modules/cjs/loader.js:959:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:995:10)
    at Module.load (internal/modules/cjs/loader.js:815:32)
    at Function.Module._load (internal/modules/cjs/loader.js:727:14)
    at Function.Module.runMain (internal/modules/cjs/loader.js:1047:10)
[12/31/2019, 04:24:13] Got SIGTERM, shutting down Homebridge...
homebridge.service: Main process exited, code=exited, status=143/n/a
homebridge.service: Failed with result 'exit-code'.
homebridge.service: Service RestartSec=3s expired, scheduling restart.
homebridge.service: Scheduled restart job, restart counter is at 4.
Stopped Homebridge.
Started Homebridge.
[12/31/2019, 04:24:23] Loaded config.json with 0 accessories and 4 platforms.
[12/31/2019, 04:24:23] ---
[12/31/2019, 04:24:23] Loaded plugin: homebridge-config-ui-x
[12/31/2019, 04:24:23] Registering platform 'homebridge-config-ui-x.config'
[12/31/2019, 04:24:23] ---
[12/31/2019, 04:24:23] Loaded plugin: homebridge-ecoplug
[12/31/2019, 04:24:23] Registering platform 'homebridge-ecoplugs.EcoPlug'
[12/31/2019, 04:24:23] ---
[12/31/2019, 04:24:23] ====================
[12/31/2019, 04:24:23] ERROR LOADING PLUGIN homebridge-honeywell-home:
[12/31/2019, 04:24:23] Error: Cannot find module 'lib/roundtrip'
Require stack:
- /usr/lib/node_modules/homebridge-honeywell-home/index.js
- /usr/lib/node_modules/homebridge/lib/plugin.js
- /usr/lib/node_modules/homebridge/lib/server.js
- /usr/lib/node_modules/homebridge/lib/cli.js
- /usr/lib/node_modules/homebridge/bin/homebridge
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:797:15)
    at Function.Module._load (internal/modules/cjs/loader.js:690:27)
    at Module.require (internal/modules/cjs/loader.js:852:19)
    at require (internal/modules/cjs/helpers.js:74:18)
    at Object.<anonymous> (/usr/lib/node_modules/homebridge-honeywell-home/index.js:7:19)
    at Module._compile (internal/modules/cjs/loader.js:959:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:995:10)
    at Module.load (internal/modules/cjs/loader.js:815:32)
    at Function.Module._load (internal/modules/cjs/loader.js:727:14)
    at Module.require (internal/modules/cjs/loader.js:852:19)
[12/31/2019, 04:24:23] ====================
[12/31/2019, 04:24:25] Loaded plugin: homebridge-ring
[12/31/2019, 04:24:25] Registering platform 'homebridge-ring.Ring'
[12/31/2019, 04:24:25] ---
[12/31/2019, 04:24:25] Loading 4 platforms...
[12/31/2019, 04:24:25] [Config] Initializing config platform...
[12/31/2019, 04:24:25] [Config] Running in Standalone Mode.
[12/31/2019, 04:24:25] [Ring] Initializing Ring platform...
[12/31/2019, 04:24:25] [EcoPlug] Initializing EcoPlug platform...
[12/31/2019, 04:24:25] Error: The requested platform 'homebridge-honeywell-home.HoneywellHome' was not registered by any plugin.
    at API.platform (/usr/lib/node_modules/homebridge/lib/api.js:140:13)
    at Server._loadPlatforms (/usr/lib/node_modules/homebridge/lib/server.js:327:45)
    at Server.run (/usr/lib/node_modules/homebridge/lib/server.js:90:36)
    at module.exports (/usr/lib/node_modules/homebridge/lib/cli.js:59:10)
    at Object.<anonymous> (/usr/lib/node_modules/homebridge/bin/homebridge:17:22)
    at Module._compile (internal/modules/cjs/loader.js:959:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:995:10)
    at Module.load (internal/modules/cjs/loader.js:815:32)
    at Function.Module._load (internal/modules/cjs/loader.js:727:14)
    at Function.Module.runMain (internal/modules/cjs/loader.js:1047:10)

also can homebridge-honeywell-home.HoneywellHome, just be Honeywell-home? or honeywellhome instead of everything like that? is that possible?
Thanks for doing all this!

I will look at the further tomorrow. I am working on HOOBS instance support.

Thanks

@mkellsy Thanks!

The roundtrip require is fixed.

Homebridge requires that your plugin starts with "homebridge-". So the homebridge-honeywell-home.HoneywellHome is the package plus the alias.
Go ahead and test this again.

@mkellsy I was able to get this installed! So much easier to install then before!! I am totally okay with it being called @hoobs/honeywell!! I am going to merge this and release 2.1.0
This is read-only right now so I will change that in the readme. Has never had write to the thermostat support.


Multiline strings

I have been searching through the docs for past 2+ hours, but I simply can't find information if there is any support for multiline strings.
So, is there? Ideally I would love if there would be an option to automatically replace \n with , but just being able to get strings with \n would be OK too (I would look into writing filter that would replace \n with

Regarding the same issue,
I have huge text that I want to translate (terms and condition).
I want to be able to format it in en.json like this:
`
"DESCRIPTION": [
      "
Lorem ipsum dolor sit ci nec.
",

      "
Quis tantas accumsaorreant. Ex eam assum facete.
",

      "
Discere honestat eu summo sanctus.
",

      "
Ex unum viris re periculis ex vel.
",

      "
Id duo dolore signifecing an pro.
"

]
`
Is there a way to use multiple lines?

@islavi Use a single ling/string (even concatenated), but no array of strings.

I feel as though I am missing something key here! In my translation json I have a key : value pair that contains a span ( or a link or some other markup) like so:
"forgot" : {  "span" : "Here is some text in a span" }
in the template when I use the directive as mentioned above I get an empty paragraph tag:

Do I need to bind this translate string to innerHtml? I am also looking to include links in my translate strings as outlined in this post: https://github.com/ocombe/ng2-translate/issues/145
Any tips would be greatly appreciated!

@ahayn465  Please do not use already closed issues, especially if your topic has nothing to with the issue's one.
Please include/attach a proper demo, also I think your post is missing something?
Last one: Please have a look at our guide, in your case it is eventually best showed here.


Height Mod Test

Added height to config. Testing assigning height to a new var and using that to determine window height.
PR for issue: here. For @blainesch to review.

Thank you for looking into it! This is a great start.

No problem and thank you! Did you know? This is my first pull request I've ever made. :3
So I don't understand how to do lots of things yet, but I'm learning.

@Koolstr any update on this?

What kind of update would there be? Looks like you made the changes needed and tried to merge it, but the tests failed? What still needs to be done to get those tests to pass?

Has this been resolved, but the fix just isn't being merged due to build test failing? How can we ensure this passes?

About to merge the PR open here:
https://github.com/tinytacoteam/zazu/pull/300#pullrequestreview-114221704
Going to close this one as all commits from @Koolstr will be kept and merged through that PR.
Thanks again for you work on this feature!

Awesome! Thank you for fully resolving this. And you are welcome. ^_^


[Enhancement] Having a way to play a video indefinitely

Summary
Would it be good to have to play a video indefinitely?
Intended Use Case
Right we could play the video locally and via https. However, we found out that we have no way to play the video indefinitely and it would be good to have a property to tell to replay the video once the end of the video is done.

@AlfonChitoSalano Thank you for the suggestion, will be included in the next release.


Option to wait for AP regeneration instead of exiting when AP ran out

Before opening an issue:

[x] No one has asked for this feature before in other issues (even the closed ones)

If you open unnecessary/dumb issues, you'll be rewarded with appropriate tags.

Sometimes I might want to take a long (11+hr) sleep but I don't want AP from filling all the way up, so I think an option that makes FGA continue to check if AP has regenerated will be nice.
So far I made some adjustments and tested and it goes as the following:

I keep my phone plugged in all night (and all day since it's a spare phone and can be left in the same spot for days)
Turn on the option to wait for AP regeneration and turn off Refill
When in AutoBattle, after the refill message pops up after clicking on a node, FGA clicks close and waits for 20 seconds (I think some phones have a 30 second screen timeout, I'm not sure if FGA can keep the phone awake without clicking for a long time so I set it to 20 seconds for now)
After 20 seconds FGA clicks on the node again to check if AP has regenerated enough to rerun the node

This might also help people that don't want to commit all apples from the beginning in Christmas 2020 in JP but if JP UI update takes more time to adjust to that was more important than this update.
Anyways, I'll make a PR and please see if this sounds good.

I thought this feature wasn't getting implemented... Anyway it's good to finally get it. Does this work for all servers yet?

Yeah, I was against it, but, anyways since @the3dsandwich sent a PR and it's toggleable and OFF by default, I think it's fine.
It should work on all servers since it's nothing specific.


Fix #2902: ‘autoRedirect’ hardcode ‘https’ scheme

Please sign your commits following these rules:
https://github.com/moby/moby/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "master" git@github.com:icefed/distribution.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

Amending updates the existing PR. You DO NOT need to open a new one.

I was about to create almost the same PR. This would be really useful, so that a single distribution/docker-auth setup could be used both without TLS on an internal network and with TLS (via a reverse proxy) from the outside.
If someone could maybe make a comment as to what it would take to get this merged? I'd be happy to help get this in shape.

This seems like a sensible change from a functionality perspective, but I haven't worked on this area of the code before, so can you help me understand the need?
Are you running the registry and an auth server behind the same proxy, with the auth server at /auth/token?
Is there a reason you aren't using TLS internally, which I would have considered to be good practice?
Note the OAuth2 spec calls out sending secrets in the plain: https://datatracker.ietf.org/doc/html/rfc6749#section-<IP_ADDRESS>
I do wonder if forcing a manually set http realm is better than allowing an http realm by default.

This seems like a sensible change from a functionality perspective, but I haven't worked on this area of the code before, so can you help me understand the need?
Are you running the registry and an auth server behind the same proxy, with the auth server at /auth/token?

Sort of, except I am re-writing /auth/token to /auth, because that's what docker-auth wants, and I am now actually much more concerned about the /auth/token path hardcoded in the autoredirect code path than the TLS part. But, hey... :slightly_smiling_face:

Is there a reason you aren't using TLS internally, which I would have considered to be good practice?

I am actually using TLS everywhere now, but I still think having the choice would be nice. Making it more explicit does sound reasonable, though. Just as an idea, i think my favorite solution would be to be able to set realm to e.g. https://{host}/auth, and then the {host} gets replaced with the value of the host header. That way one would have very explicit control over everything, but with the flexibility of autoredirect (or, in fact, even more).

I suppose you could template it with {scheme} and {port} as well if you need to.
I'm still a little unsure that it would get many users - what's the need for accessing the same repo from two different hosts?

I'm still a little unsure that it would get many users

That I cannot judge, but the feature is already present with autoredirect. I would say the suggested approach is just fixing a shortcoming in that feature.

what's the need for accessing the same repo from two different hosts?

For me, right now, resiliency: having an internal domain for internal services (where the routing involves much fewer moving parts). And, though I am not doing this right now, I was entertaining the idea of routing the /auth endpoint for the external domain to a separate auth instance, to be able to apply different rules (e.g. internal one allows anonymous access, external doesn't).

This code hasn't been touched for a long time really, so picking some recent maintainers to request a review.

@Jamstah

I guess its not enabled by default, I can see some use cases, and it is an improvement over what's there today.

Sorry, I doesn't get it, are you mean we keep the default behavior to return https and the admin can configure whether or not to enable my modifications?

I would never recommend going without TLS in production, even internally, but for poc/dev environments its not so bad.

Yes, when I submitted the PR, it was intended for internal deployment and development purposes within the company.

Hi @bitfehler @Jamstah , I have added too config parameters, hopes that will filling your requirements.
// default /auth/token
autoredirectpath
// default false (seems too long...)
autoredirectforcetlsdisabled

I am not the authority here, but in my opinion the configuration is becoming way too complicated (from a user perspective).
I don't know if and how the release cycle management restricts the modification/removal of options, but my favorite solution would be this:

realm gains supports for inserting template parameter {host}, and maybe also {scheme} and {port}

This change would be backwards-compatible
Currently autoredirect includes the port (i.e. it fills in the entire authority, not just the host, so depending on desired functionality, it should support either {authority}, or, more flexible, {host} and {port}
If {scheme} is to be supported, it's fine to just say "looks at incoming request and X-Forwarded-For", folks should know what they are doing when they use this, and the vast majority will just use https://{host}/... anyways

autoredirect gets removed or at least deprecated with a warning that users should move to templated realm

Just my 2 cents...

I am not the authority here, but in my opinion the configuration is becoming way too complicated (from a user perspective).
I don't know if and how the release cycle management restricts the modification/removal of options, but my favorite solution would be this:
* `realm` gains supports for inserting template parameter `{host}`, and maybe also `{scheme}` and `{port}`

  * This change would be backwards-compatible
  * Currently `autoredirect` includes the port (i.e. it fills in the entire authority, not just the host, so depending on desired functionality, it should support either `{authority}`, or, more flexible, `{host}` and `{port}`
  * If `{scheme}` is to be supported, it's fine to just say "looks at incoming request and X-Forwarded-For", folks should know what they are doing when they use this, and the vast majority will just use `https://{host}/...` anyways

* `autoredirect` gets removed or at least deprecated with a warning that users should move to templated `realm`

Just my 2 cents...

Remove autoredirect is a breaking change, it will affect existing users, I don't think it's a good idea.
configuration is becoming way too complicated, remove autoredirectforcetlsdisabled may be simpler, then we let admin being aware of X-Forwarded-For header, otherwise redirect to https.
If you want custom redirect path, you can set autoredirectpath to /auth.


Kubectl -f [Filename] does not create anything

I have set up a kubernetes cluster on coreos with the official documentation.
core@hostname ~ $ kubectl get nodes
NAME           LABELS                                STATUS    AGE
<IP_ADDRESS>   kubernetes.io/hostname=<IP_ADDRESS>   Ready     3h
<IP_ADDRESS>   kubernetes.io/hostname=<IP_ADDRESS>   Ready     3h
core@hostname ~ $ kubectl get ep
NAME         ENDPOINTS          AGE
kubernetes   <IP_ADDRESS>:443   4h

The cluster seems to be working.
Now I wanted to set up the web interface with the following yaml:
apiVersion: v1
kind: Service
metadata:
  name: kube-ui
  namespace: kube-system
  labels:
    k8s-app: kube-ui
    kubernetes.io/cluster-service: "true"
    kubernetes.io/name: "KubeUI"
spec:
  selector:
    k8s-app: kube-ui
  ports:
  - port: 80
    targetPort: 8080
---
apiVersion: v1
kind: ReplicationController
metadata:
  name: kube-ui-v4
  namespace: kube-system
  labels:
    k8s-app: kube-ui
    version: v4
    kubernetes.io/cluster-service: "true"
spec:
  replicas: 1
  selector:
    k8s-app: kube-ui
    version: v4
  template:
    metadata:
      labels:
        k8s-app: kube-ui
        version: v4
        kubernetes.io/cluster-service: "true"
    spec:
      containers:
      - name: kube-ui
        image: gcr.io/google_containers/kube-ui:v4
        resources:
          # keep request = limit to keep this container in guaranteed class
          limits:
            cpu: 100m
            memory: 50Mi
          requests:
            cpu: 100m
            memory: 50Mi
        ports:
        - containerPort: 8080
        livenessProbe:
          httpGet:
            path: /
            port: 8080
          initialDelaySeconds: 30
          timeoutSeconds: 5

Now when I want to create / start the interface, I enter the following command:
core@hostname ~ $ kubectl create  -f kube-ui.yaml --namespace=kube-system
service "kube-ui" created
replicationcontroller "kube-ui-v4" created

The service & rc seem to be created. My Problem:
The following command:
core@hostname ~ $ kubectl get pods
NAME      READY     STATUS    RESTARTS   AGE
core@hostname ~ $

Also I cannot access the webinterface. After adding the necessary client certificates, I try to access the link "https://<IP_ADDRESS>/ui" which redirects me to "https://<IP_ADDRESS>/api/v1/proxy/namespaces/kube-system/services/kube-ui/#/dashboard/". There I receive the following text:
{
  "kind": "Status",
  "apiVersion": "v1",
  "metadata": {},
  "status": "Failure",
  "message": "endpoints \"kube-ui\" not found",
  "reason": "NotFound",
  "details": {
    "name": "kube-ui",
    "kind": "endpoints"
  },
  "code": 404
}

I also tried the dns-addon in the documentation, but I do not see that with a "kubectl get pods" too...

kubectl get pods --all-namespaces
By default you don't see namespace of kube-system. Are you running on bare-metal or cloud?

core@hostname ~ $ kubectl get pods --all-namespaces
NAMESPACE     NAME                          READY     STATUS    RESTARTS   AGE
kube-system   kube-apiserver-<IP_ADDRESS>   1/1       Running   0          2h
kube-system   kube-podmaster-<IP_ADDRESS>   2/2       Running   0          2h
kube-system   kube-proxy-<IP_ADDRESS>       1/1       Running   0          2h
kube-system   kube-proxy-<IP_ADDRESS>       1/1       Running   0          2h
kube-system   kube-proxy-<IP_ADDRESS>       1/1       Running   0          2h

I'm running on bare-metal. Three old HP DL380G5, to be exactly.
I created the kube-system namespace at the beginning with ```curl -XPOST -d'{"apiVersion":"v1","kind":"Namespace","metadata":{"name":"kube-system"}}' "http://<IP_ADDRESS>:8080/api/v1/namespaces"````

Can your nodes reach Internet?

Yes, they can.
core@hostname ~ $ ping www.google.com
PING www.google.com (<IP_ADDRESS>) 56(84) bytes of data.
64 bytes from ea-in-f105.1e100.net (<IP_ADDRESS>): icmp_seq=1 ttl=45 time=31.0 ms
64 bytes from ea-in-f105.1e100.net (<IP_ADDRESS>): icmp_seq=2 ttl=45 time=30.5 ms

Suggest you to join slack here https://kubernetes.slack.com and ask the question to k8s community, might be faster to get an answer.

I got the solution.
The problem was indeed something with the network. I've used a L2 Network with just a switch. Apparently, this wasn't enough. I found a guide to set up the network correctly, but that was (for me) much too complicated - therefore I switched to flannel and did the setup again. Now it's working.


Search in table with FUNCTION Mysql who create a column

Summary of problem or feature request
Hi support,
I would like to search with a column created by FUNCTION Mysql
Code snippet of problem
oh_trim_hierarchy(objects_hierarchy.full_hierarchy, '0001')) AS path
In the first query mysql
select  count(*) as aggregate from (select '1' as row_count from devices WHERE path LIKE '%search%'
i have an error because path don't exist.
In the second query, i have the colum:
SELECT REPLACE(oh_trim_hierarchy(objects_hierarchy.full_hierarchy, ''),'/',' -> ') AS path FROM devices....
System details

Ubuntu 18.04
PHP 7.2
Laravel Version 5.8
Laravel-Datatables ~9.0

Thanks a lot

I resolved the problem with REPLACE(oh_trim_hierarchy(objects_hierarchy.full_hierarchy, ''),'/',' -> ') without "AS path"
So
SELECT * FROM AS device where oh_trim_hierarchy(objects_hierarchy.full_hierarchy, '') like '%search%'


Add Fulfillment Service

Creating for @aryy this PR adds Fulfillment and helpers to Order.

Codecov Report

Merging #115 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master   #115   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          22     23    +1
  Lines         809    888   +79
=====================================
+ Hits          809    888   +79

Impacted Files
Coverage Δ

fulfillment.go
100% <100%> (ø)

util.go
100% <100%> (ø)
:arrow_up:

order.go
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

Hey @dlebech we're going to pull this in here, then make some changes on our fork

@andrewhoff yeah no problem. Sorry for the wait. Feel free to merge when you're ready, the changes look good to me :-)
Thanks for the changes @gir 👍


Flip and Stack question

Hi. The environments PandaStack-v3 and PandaFlip-v3, whether there are feasible results for them, I saw in the paper that the success rate of the stack is almost 0.

Both are feasible, in the sense that technically, you can write your hard-coded policy that would solve the task.
However, stack has an highly spare reward, and flip required a very precise control. Both are very challenging task, but possible.

Thank you for your reply. Are there any algorithms/hyperparameters that have already been successful, or do I need to implement them myself?

@Swk6666 I haven't tried PandaStack-v3, but I was able to solve PandaFlip-v3 with reasonable accuracy using the DDPG implementation in stable-baselines3.
Appendix G in this paper lists the hyperparameters I used.


Very nice project

My solution was a tiny shell script.
#!/bin/bash
#
# Kimsufi server alert.

AVAILABILITY_JSONP="https://ws.ovh.com/dedicated/r2/ws.dispatcher/getAvailability2?callback=Request.JSONP.request_map.request_0"
KS="150sk10"

wget -q -O- "$AVAILABILITY_JSONP" \
    | sed 's/},/},\n/g' \
    | grep -A8 "\"reference\":\"${KS}\"" | cut -d'"' -f8,12 \
    | tail -n +2 | grep -v "^unknown"

exit 0

Very good, thats exactly the software freedom - you share what you have, and people choose what they like to use

:smile:


Storage: Update GetPoolByInstance to use instance's StoragePool() function

This ensures that it will use an pre-loaded storage pool var inside the instance,
to avoid extra DB queries.
This is also essential as we move to creating the storage volume DB records in the
storage package, as at instance create time the storage pool to use is derived from
the instance's root disk config and then that storage pool is pre-loaded inside the
instance. Meaning that we can then access it to create the instance's volume, whereas
without this the storage volume select query would fail as the DB record hasn't been
created yet.
Also improves error messages.

jenkins: test this please

jenkins: test this please

Testsuite passed


Kadira stopped working. (period)

Not sure if related to #240 but about 30 minutes ago started getting
Kadira: authentication failed - check your appId & appSecret
on meteor server log (no changes on my part).
Also https://ui.kadira.io/ giving 502 Bad Gateway: Registered endpoints failed to handle the request.

@fvpDev Yes. We had an DB related issue due to an Google could incident. I sent you an email regarding that.
Now, things came back to the normal stage and we are monitoring it for another few hours.


Feature/worker health prototype

This is a FYI/initial feedback type PR, and not something I'm looking to actively merge to the GDK.
On our project we want to handle several cases where too many players may end up on a worker, or other reasons that a worker may become unavailable(Like a worker has crashed).
1st: I adjust the load balancer to have a delegate it can fire that indicates that an actor migration has failed.  We then provide a safe space where the actor can be teleported to.  It's not the GDK's responsibility to move the actor to the safe space, but it's up to the game to decide what to do with that data.  We're only able to provide a 2d coord and need to find a safe space on terrain, etc to successfully teleport the player to a safe space.
2nd: I store Healthy/HealthyAsOf, and the virtual worker assigned to that server worker.  This can be used to detect a worker that has crashed(stale HealthyAsOf value), or a worker that has decided to mark itself as unhealthy(Healthy set to false).  This is to mitigate too many players on a worker, or if a worker just needs a break for a little while.
Almost all of this code is foreign to me, so I'm guessing I've put things in the wrong places, or done things generally the wrong way, so any better ways of accomplishing the same would be appreciated.

Oh, and I extracted this out of our project and had to unwind some changes by hand, so if you run across some code that doesn't look like it compiles, that's probably why.

Sami pointed out that if we implemented the load balancer ourselves instead of modifying the UGridBasedLBStrategy, we could avoid a lot of the GetSafePositionForActor and SpatialActorChannel change.  That seems like a much smarter approach.


Add new command line arguments for temperature, max tokens, and context windows in main.py

This pull request adds new command line arguments to the main.py file. The new arguments include temperature, max tokens, and context windows. These arguments allow for more control over the generated text, including randomness, response length, and context consideration.
#155

context-windows is the MAX_TOKEN_LENGTH from config.py

Is that okay, now?

Is that okay, now?

Its awesome