Cannot use 'in' operator to search for 'key' in undefined

EDIT BY @koskimas: This has been fixed in 1.1.3
Seems to be a regression in 1.1.2.
When calling JSON.stringify(entities); (which, e. g., happens when you are trying to send an array of Objection entities as a response from Express), an error is thrown.
Error seems to only manifest itself when entity in question has custom idColumn defined (in this particular case it was defined as
	static get idColumn() {
		return 'key';
	}

)
Error stacktrace:
TypeError: Cannot use 'in' operator to search for 'key' in undefined
at assignJsonValue (C:\sources\lms-api\models\node_modules\objection\lib\model\modelToJson.js:79:33)
at toExternalJsonImpl (C:\sources\lms-api\models\node_modules\objection\lib\model\modelToJson.js:51:5)
at toJson (C:\sources\lms-api\models\node_modules\objection\lib\model\modelToJson.js:20:14)
at Brand.$toJson (C:\sources\lms-api\models\node_modules\objection\lib\model\Model.js:204:12)
at Brand.toJSON (C:\sources\lms-api\models\node_modules\objection\lib\model\Model.js:208:17)
at JSON.stringify ()
at eval (eval at stringify (C:\sources\lms-api\api\node_modules\express\lib\response.js:1117:14), :1:6)
at stringify (C:\sources\lms-api\api\node_modules\express\lib\response.js:1117:14)
at ServerResponse.json (C:\sources\lms-api\api\node_modules\express\lib\response.js:260:14)
at ServerResponse.send (C:\sources\lms-api\api\node_modules\express\lib\response.js:158:21)
at router.get (C:\sources\lms-api\api\controllers\brands.controller.js:44:7)
at
Surprisingly, this works fine when single entity is being stringified.

I'll need a repro for this. I was not able to reproduce this.

@koskimas Will create a failing test ASAP

Silly me, this throws:
const { Model } = require('./');

class Person extends Model {
  static get idColumn() {
    return 'key';
  }
}

const p1 = Person.fromJson({ key: 1 });
const p2 = Person.fromJson({ key: 2 });

JSON.stringify([p1, p2]);

@igor-savin-ht No need for repro anymore.

Fixed. A new version will be out in a couple of minutes. Sorry about this 😬

ah, sorry, missed your update. Thank you for the quick fix!

@koskimas Shouldn't this be closed :)? Published fix worked, btw.

@kibertoad Other people may have hit the same bug and they'll come looking for an answer. Let's keep this open for a couple of days.

Makes sense.


Add behave test for range query. Resolves #767

Also, fix issue with "invoke" and "query" actions in behave when functions had names other than "invoke" or "query"

Signed-off-by<EMAIL_ADDRESS>


How to use advantage of CEGB?

LightGBM claims support  of Cost Efficient Gradient Boosting. There is information, how to set penalties for feature usages, but how to use advantage of cost efficient model? Is there any interface to provide expensive-to-calculate features on request from model evaluation?

please refer to the original paper: https://papers.nips.cc/paper/6753-cost-efficient-gradient-boosting.pdf

please refer to the original paper: https://papers.nips.cc/paper/6753-cost-efficient-gradient-boosting.pdf

Thank you for your reply! But I couldn't find any reference to actual lightGBM interface to provide expensive-to-calculate features on request when applying model.

@Taube03
did you mean the code location?
you can refer to https://github.com/microsoft/LightGBM/blob/master/src/treelearner/cost_effective_gradient_boosting.hpp


[SPARK-34118][CORE][SQL] Replaces filter and check for emptiness with exists or forall

What changes were proposed in this pull request?
This pr use exists or forall to simplify filter + emptiness check, it's semantically consistent, but looks simpler. The rule as follow:

seq.filter(p).size == 0) -> !seq.exists(p)
seq.filter(p).length > 0 -> seq.exists(p)
seq.filterNot(p).isEmpty -> seq.forall(p)
seq.filterNot(p).nonEmpty -> !seq.forall(p)

Why are the changes needed?
Code Simpilefications.
Does this PR introduce any user-facing change?
No
How was this patch tested?
Pass the Jenkins or GitHub Action

Test build #134071 has started for PR 31184 at commit b9586ee.

Test build #134071 has started for PR 31184 at commit b9586ee.

Oops, I mistakenly merged this before the test results. I manually verified in my local. I will monitor the build results in the master.
Merged to master.

Oops, I mistakenly merged this before the test results. I manually verified in my local. I will monitor the build results in the master.
Merged to master.

@LuciferYang, can you open a PR against other branches too? that will reduce the conflicts.

@LuciferYang, can you open a PR against other branches too? that will reduce the conflicts.

@LuciferYang, can you open a PR against other branches too? that will reduce the conflicts.

branch 3.1, 3.0 and 2.4 ?

@LuciferYang, can you open a PR against other branches too? that will reduce the conflicts.

branch 3.1, 3.0 and 2.4 ?

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/38657/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/38657/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/38657/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/38657/

Yeah, let's do that all.

Yeah, let's do that all.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/38657/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/38657/

Test build #134071 has finished for PR 31184 at commit b9586ee.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test build #134071 has finished for PR 31184 at commit b9586ee.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/134071/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/134071/

cc @HyukjinKwon

branch 3.1:  https://github.com/apache/spark/pull/31188
branch 3.0:  https://github.com/apache/spark/pull/31190
branch 2.4:  https://github.com/apache/spark/pull/31192

cc @HyukjinKwon

branch 3.1:  https://github.com/apache/spark/pull/31188
branch 3.0:  https://github.com/apache/spark/pull/31190
branch 2.4:  https://github.com/apache/spark/pull/31192

thx!

thx!


Replace instruction list with Task List

https://trello.com/c/SPGKu5rX/95-3-replace-instruction-list-with-govuk-design-system-task-list-pages-pattern-in-create-a-dos-opportunity-journey
Have implemented a task list that's as close to the prototype kit as possible so that hopefully if/when the task list gets added to the Design System, it should be fairly easy to convert and remove the custom styling.
Pages seem to be working as expected and passing old tests.
To do
There are several more states now, and this needs to be tested more thoroughly:

Correct tags show - To do, in progress, Done, Cannot start yet and Optional - depending on state of work. I've started on testing these, but I'm sure there's an easier way to do it that I haven't figured out.
Preview/Publish text behaviour (initially unclickable, clickable once all required questions are answered). This is related to the above - what's the easiest way of generating a brief that's ready to preview, without having to manually enter all the answers in the test?
The new section_status object behaviour should be tested - maybe testing its effect on the page is enough?

Issues

The mix of task list and normal links might be a bit messy, after all. Once you're past the draft stage, I think there's only one further "Task" that we check the state of: "Let suppliers know the outcome". So that's currently set up as a task list item. Would setting ALL the links up as Task List items also be confusing since we're not checking the state of all of them? What tag would we give things that are just providing guidance?

It's definitely a messy page. What you've done is a step in the right direction though. Will discuss further offline.

A designer colleague has suggested we put the guidance links in the task list with a "Guidance" tag.
I think this is a great idea we should implement, going to push a commit doing so.

A designer colleague has suggested we put the guidance links in the task list with a "Guidance" tag.
I think this is a great idea we should implement, going to push a commit doing so.

This did not work in the end, because of the way guidance isn't the only thing that isn't a task in our task list.
See my Trello comment on this for more.

I've finally finished with the tests for this, in the end I took the cheating way out and used snapshot testing.

I can't approve my own PR, but this looks good to me as a stopgap before improving the flow of it entirely.


DO NOT MERGE – Test unicode 12 for s390x

This is only to test s390x CI with a compatible Unicode version (6.0).

Trying to find a correct match between Unicode version and GHC. Updating to Ubuntu 22.04 with Unicode 12.0

Unicode versioning is a mess in GHC. It seems the only version I can test here is Unicode 12.1 with GHC 9.0.2: GHC available for s390x and all out tests pass for x86. Let’s confirm this with the last commit…

@harendra-kumar this PR is the proof that the code is ok for s930x (BE, 64bits). I needed to downgrade the Unicode version to 12.1 to match GHC 9.0.2. I will use this code without the downgrade for #98.


Bonus task 1: Create PR after successful checks

Bonus task 1: Merge PR to release branch after successful checks


Add ppc64le support

This PR is to add ppc64le support to hacbs-test and clamav-db images.

@jsztuka @srivickynesh can you please assign this for review?

Could you please provide/create story about this change??

@jsztuka I have created story https://issues.redhat.com/projects/HACBS/issues/HACBS-921.
@srivickynesh @dirgim can you please review this?


KeyError - unexpected argument deltatoken

Not sure this is the best place to raise this, doing so coz it affects all Languages.
The docs show than SDKs have deltatoken key that can be used to get the delta token  the SDKs and the HTTP call both point to the same error:
HTTP Call
doing a call to The api does not recognise - https://graph.microsoft.com/v1.0/applications/delta?deltatoken=latest Gives:
{
    "error": {
        "code": "Request_BadRequest",
        "message": "Unrecognized query argument specified: 'deltatoken'.",
        "innerError": {
            "date": "2024-04-28T16:30:39",
            "request-id": "f2ea5621-e131-47c3-9ee2-d1bd91f96236",
            "client-request-id": "f7d27604-49ba-7cfd-b151-19d46c093e3f"
        }
    }
}

If the API does not support the argument, why do we have it in our SDKs and snippets.
A call to the C# snippet here  gives:
Unhandled exception. Microsoft.Graph.Models.ODataErrors.ODataError: Unrecognized query argument specified: 'deltatoken'.

A similar call to Python snippet  returns:
Result: Failure Exception: TypeError: DeltaRequestBuilder.DeltaRequestBuilderGetQueryParameters.__init__() got an unexpected keyword argument 'deltatoken' Stack: File "/azure-functions-...

Possible  workarounds
Loop through the get requests, following @odata.NextLink to the last page, the use odata_delta_link, and extract deltatoken from it
async def get_user_delta(max_calls=10):
    try:

        # user dela
        url = "https://graph.microsoft.com/v1.0/applications/delta"
        calls = 0
        while calls < max_calls:
            response = await user_client.applications.delta.with_url(url).get()
            print(calls)
            if response.odata_next_link:
                url = response.odata_next_link
            elif response.odata_delta_link:
                print(response.odata_delta_link)
                return response.odata_delta_link
            calls += 1

    except APIError as e:
        print(f"Error: {e.response_status_code}: {e.message}")

This might not be efficient if the loops are too many, in my case it worked as we got the deltatoken on the third iteration of
Optionally, use the page iterator

https://graph.microsoft.com/v1.0/applications/delta?deltatoken=latest

I believe, the deltaToken needs the $ character to be $deltatoken according to the docs.
The snippet generation for python (and other languages) need to be updated here for snippets using the $deltaToken to use the withUrl method. This is because the example is using a result from a nextLink and consumers should ideally not be parsing deltaToken. See an explanation at on why the openApi metadata do not include the parameters at https://github.com/microsoftgraph/msgraph-sdk-dotnet/blob/dev/docs/upgrade-to-v5.md#skiptoken-and-deltatoken-query-parameters-in-delta-requests
It should therefore be possible to do this.
url = "https://graph.microsoft.com/v1.0/applications/delta?$deltatoken=latest"
response = await user_client.applications.delta.with_url(url).get()

Good, then it implies a problem with our snippets across SDKs

Taking a look at the snippets, the snippets for C# and Java look to be okay. (This scenario should also be failing on the raptor checks).
@shemogumbe should we close this here and file issues in the snippet generator?


Pluto TV EPG (depends on proxies)

This might be interesting due to the ongrowing number of countries Pluto TV is getting in.
I have made a fork of PlutoIPTV, available here, rewrote it to ditch request since it is deprecated : https://github.com/LaneSh4d0w/PlutoIPTV. It might serve to get the EPG.

Sorry, but I can't add a source to the list if it requires a proxy to access it.


Add simpler example

This PR introduces a new example named shapes which draws a stroked rectangle, a filled circle, a filled ellipse and a line to a Winit window. It fits in a single file and is very minimal. The code is commented (can add more if needed) which makes it easier for beginners to get started.
Closes #433 (hopefully).
Any suggestions or criticisms are welcome. Cheers!

Our CI scripts have changed, so you need to rebase on main to get the CI checks to pass.

Fixed @xStrom!

Thanks :)


Solaris support

Hello!
I think it would be easy to add Solais OS support just by taking car of some issues related with getfacl and setfacl specific commands in that OS.
For example, getfacl command under Solaris does not support --absolute-names neither --no-efective arguments.
Is there any chance that you fix this problem. Could I collaborate somehow?
Kind Regards,
Raúl

Looking into this, it seems like Solaris ACLs are based on POSIX.1e, so it should be more-or-less possible. @rssh22 do you think the Illumos-based distros (like DilOS) are similar enough to Solaris to develop/test this feature on?

Hello!
I've installed dilos 1.3.4 i386 and it looks pretty similar to Solaris OS. So I think it could be possible to make the tests on it.

Closing due to age of issue. Please re-open with a pull request if you would like this enhancement.


Properly inject a runtime

I am working on a loader for OJ that compiles .oj files to JS. So far, this works very nicely especially since the compiler doesn't mind an async loader.
There is one catch that I came across that is making things a bit complicated_
When I inject the runtime via the following header:
    var header = [
        "var oj = require('!!ojc/src/runtime');",
        "global.oj = global['$oj_oj'] = oj;"
    ].join("\n");

I get back a snippet in my output file that looks like:
/***/ function(module, exports, __webpack_require__) {
	/* WEBPACK VAR INJECTION */(function(global) {
            // Within here we have the runtime. Runtime calls itself like:
            ;(function(){ /* snip */ }).call(this);
	/* WEBPACK VAR INJECTION */}.call(exports, (function() { return this; }())))
/***/ }

The problem with this injection is, that exports is transformed  into the this of the function - and further, that internal function calls its first argument global, effectively shaddowing the real global (window in a browser). And I can't quite recognize what (function() { return this; }()) will return... and I doubt it's the real global, which is mandatory.
My questions are:

How do I properly inject this runtime?
Is there a way to only inject my header once into the global space? As in, reducing the duplication of code. $oj_oj is expected to keep its state, so I only want to assign it once, and only once.

Kind regards, Ingwie!

Turns out that the seemingly shaddowed global is indeed the real global. I just made a quick and dirty test:
webpackJsonp([0,1],[
/* 0 */
/***/ function(module, exports, __webpack_require__) {

	console.log("meep.");
	__webpack_require__(1);
	//require("./lib.oj");

/***/ },
/* 1 */
/***/ function(module, exports, __webpack_require__) {

	/* WEBPACK VAR INJECTION */(function(global) {console.log("This:");
	console.log(this);
	console.log("Global:");
	console.log(global);

	/* WEBPACK VAR INJECTION */}.call(exports, (function() { return this; }())))

/***/ }
]);

The question now is, how do I run my code injection only once?

Don't use global. Don't add anything to the global scope.
To add a runtime best do it like:
var loaderUtils = require("loader-utils");
module.exports = function() {
  return "var runtime = require(" + loaderUtils.stringifyRequest(this, "!" + require.resolve("ojc/src/runtime")) + ");";
}

Add ojc to peerDependencies.
Also check these loader guidelines: https://github.com/webpack/docs/wiki/how-to-write-a-loader#guidelines

OJ requires to add oj and $oj_oj to the global object, since the compiled code reffers to it. For instance:
var Bar = $oj_oj._registerClass({ $oj_c_Bar:1 }, { $oj_c_Foo:1 }, function($oj_s, $oj_m) { function Bar() { $oj_oj._cls.$oj_c_Foo.call(this);this.constructor = Bar;this.$oj_id = ++$oj_oj._id;}
$oj_s.$oj_f_isBard = function() { return true; }
return Bar;});

The original for this code is:
@implementation Bar:Foo {}
+(BOOL)isBard { return true; }
@end

So in order to allow one class to extend another, the global $oj_oj object needs to retain its state - the added classes and such. the oj object is used to run the code, i.e. oj.sendMsg(...).
Therefore the runtime must be injected in global scope. In fact, it tries to inject itself:
https://github.com/musictheory/oj/blob/master/src/runtime.js#L366
I thought about looking into making this specific part a plugin; so that it injects the runtime, whilst the loader does the compiling. What do you think?

I just looked through the (huge!) plugin API. But I can not determine where I would hook into in order to inject the runtime. Since I am using the commonsJunk plugin, it makes two separate junks - so I only want to inject the runtime exactly once, preferably into the commons junk.

Which part do I hook into?
Is my plugin persistent enough to retain state - i.e. if I set this.isInjected, will this stay that way?

@IngwiePhoenix What about https://github.com/webpack/imports-loader?

@SimenB I am not sure with this loader - will it retain state, load my script only once and into global scope... I will be using this loader for another section of my code, but I have to let the runtime run in the global scope and be only added once.
That is why I was looking into maybe using a plugin, since i have to ensure that the runtime exists only once... Do you have any idea how I could do that? My loader, that takes OJ code and compiles it, works. I can even make sourcemaps now. But I am unable to get the runtime injected properly :/

That is why I was looking into maybe using a plugin, since i have to ensure that the runtime exists only once...

You don't need a plugin. Loader is enough.
require("xxx") === require("xxx").
var $oj_oj = require(...); should solve all problems.

I just tried that, and the result:
Uncaught ReferenceError: Foo is not defined

The output code is here:  https://gist.github.com/IngwiePhoenix/e3743bcd3bc6bbdcf43f
It appears that the vars in the generated code need to go into a reachable area - but I am not sure how.

Pinned it... im going to go and eat a broomstick INCLUDING the broom.
Turns out that OJ optimizes previously used variable names. Here is what it ACTUALLY writes, when the class is in the same file:
$oj_oj.msgSend($oj_oj._cls.$oj_c_Foo,{ $oj_f_bard: 1 })

Since the Foo interface did not exist in the other file, the Foo constant was not resolved, hence:
$oj_oj.msgSend(Foo,{ $oj_f_bard: 1 })

So yeah. This is an issue on OJ, and one that I have to figure out, somehow...probably has to do with it's optimizer.
Thanks for all of your help, I finally figured it out! Oh man. ._. Maybe @iccir has a solution for this, as he is the maintainer of OJ.
Once this works with WebPack, ill make sure to let you know so it can be added to the list of loaders! :)
Kind regards, Ingwie

Just in case anybody else hits this issue:
You need a @class Foo in this case, see https://github.com/musictheory/oj#scope-and-class :)


Remove Cloudwatch section from readme

Removes AWS stuff from README, not relevant to contributors.
I also think we should maybe remove "Fixes" and "Handy Tools" sections?  While useful to us I don't think outside contributors really care.  Maybe the "mapshaper" link would still be useful to others but not so sure about the rest.

Yeah I agree those two sections should be removed from README.


initial drag-drop implementation

initial drag-drop implementation

Sorry we couldnt pull this one one, even though you were first! :)

No hurt feelings at all. I'm much more of a backend developer, haven't
had the time to polish my frontend skills in the past few years to
catch up with most of css3, canvas, etc. If you ever have a project
idea that needs some php let me know, that's my professional and
personal expertise. :)

Nate

On 2012-02-16, at 1:41 PM, Paul Irish
<EMAIL_ADDRESS>wrote:

Sorry we couldnt pull this one one, even though you were first! :)

Reply to this email directly or view it on GitHub:
https://github.com/h5bp/mothereffinganimatedgif/pull/2#issuecomment-4006550

Word!


Organize code

I've extracted bunch of interfaces and enum-s out of the api.ts and order.ts with a goal to make code easily readable.

Move order condition interfaces to conditions folder
Move API interfaces to containers
Move enums, to enum folders

I have added some more changes:
Noticed that you use i.e. "export default interface". I didn't care about default exports at all until now because I always use the {} import (import {IBApi} from ".." rather than import IBApi from ".."). I have removed default from the delectation itself and added a "export default " instead. So we can do both now, import via {} or without.
Also I have added all missing types to index.ts - so you can do a single import like {IBApi, Contract, Order) from "@stoqey/ib".
Updated documentation as well to have new filenames on it (and upgraded typedoc version)
When you change something on /api folder, make sure to also update doc:

yarn doc
Commit the changes on /pages folder to master (this is a submodule).
Commit the new ref to /pages submodule to your branch.
With merge, ib master will get new reference to pages master and new documentation will be live.


getUri() --> uri()

Using 5.4 here I had to change getUri() to uri() in pragmarx/tracker/src/Data/RepositoryManager.php to avoid an error. I assume it's triggered by the log_routes = true setting. On another note, tracker didn't work with a separate database (but that's perhaps my fault, and I didn't investigate further). Sorry for being not more precise.

Same problem


rebuild of backend + frontend (v2)

Signed-off-by: Issif issif_github@gadz.org<!--  Thanks for sending a pull request!  Here are some tips for you:

If this is your first time, please read our contributor guidelines in the CONTRIBUTING.md file.
Please label this pull request according to what type of issue you are addressing.
If the PR is unfinished while opening it specify a wip in the title before the actual title, for example, "wip: my awesome feature"
-->

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area build

/area tests

What this PR does / why we need it:
This PR is a total rewrite of both backend and frontend.
The backend has been rewritten with Echo framework and exposes an API (in RO) to count, search, etc the events.

For the storage, and allow full text search, a Redis datababse with module [Redisearch](https://redis.io/docs/stack/search/ is used. It allows "unlimited" storage, when it was limited by a memory buffer in v1 (with 200 event as default).

The frontend is created with Vuejs 2 + Vuetify. It allows nice charts and new features like keeping query parameters (which represent filters) from page to page.

One feature is not yet implemented, the charts/tables are not auto reloaded when new event arrive.

Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Issif
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Issif]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: abaccff35e2930c9feda0805cbca8e70fa525753

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: fjogeleit, Issif
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Issif,fjogeleit]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Error in ServiceMonitor template indentation

Hi,
I'm trying to deploy the Helm chart and I've run into what I think is an error in the ServiceMonitor template.
Deploying the chart as it is now results in the following error
error="Helm release failed" revision=1.5.1 err="release trickster-proxy failed:
ServiceMonitor.monitoring.coreos.com \"trickster-proxy\" is invalid:
spec.selector.matchLabels: Invalid value: \"null\": spec.selector.matchLabels in body must be of type object: \"null\"]"

Templating the helm chart locally returns the following configuration
spec:
  jobLabel: trickster
  selector:
    matchLabels:
    component: trickster
    app: trickster
    release: release-name
    chart: trickster-1.5.1
    heritage: Tiller

Editing the indentation in line https://github.com/tricksterproxy/helm-charts/blob/master/charts/trickster/templates/servicemonitor.yaml#L16 to {{- include "trickster.labels" . | nindent 6 }} produces the correct template
spec:
  jobLabel: trickster
  selector:
    matchLabels:
      component: trickster
      app: trickster
      release: release-name
      chart: trickster-1.5.1
      heritage: Tiller

@ondrejbilcik we'll take a look at this and get back to you in the next 24 hours. Thanks for the report!

@ondrejbilcik @hato221 if you wouldn't mind giving a look @ #9 that would be great. you might not be able to submit an official review, but if you can provide a thumbs up, we'll merge it in and cut the v1.5.2 release. Thanks!

Nice, thanks!

Thanks again for the report and for the review. The release was automatically cut when the PR was merged, so you should be g2g.


Add extension column azure_kubernetes_cluster

References
New table or extension, based on the API support check.
This will provide strong support for Azure Arc management of Kubernetes clusters.
This can help to address required extensions details from the Azure Arc-managed clusters.
API can be referred
https://docs.microsoft.com/en-us/rest/api/kubernetesconfiguration/extensions/list
There is a request pending in hashicorp/terraform-provider-azurerm
https://github.com/hashicorp/terraform-provider-azurerm/issues/10635

There is no appropriate api call for getting the extension details, for future reference adding few links here
https://docs.microsoft.com/en-us/rest/api/kubernetesconfiguration/extensions/list
https://github.com/Azure/azure-sdk-for-go/blob/main/services/kubernetesconfiguration/mgmt/2021-03-01/kubernetesconfiguration/sourcecontrolconfigurations.go#L24


generic plausible data generator

The current plausible data generator finds data nodes based on hard coding within the functions. Would like to have a more adaptable solution where all data file nodes will generate synthetic files based on "data_format"

It would be good to have a class that can create dummy files. Tbh I would like to re-write it.

Read data file enums
Read subject/datafile UIDs
Copy from data template if exists in template folder, otherwise create a blank file
rename file with uid linked to subject


Can not continue sign up

Subject: Can not continue sign up
Description:
Sign up was interupted. Got a link through email to continue it but it does not work.
Results:
It gives a text invalid token and after that can not sign up with my email. It asks to sign up with the link sent which I have just tried,
Backend version: develop-7c33e18d
Frontend version:
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
Page: https://couchers.org/signup
User:

not enough info or can't reproduce


About  ILSVRC 2012 dataset result

About Figures A.13, A.14, A.15, A.16, and A.17 include visualization of the activations of all data from the ILSVRC 2012 dataset, is training set or val set?

It comes from the training set.


Parking: Track User's Previous Behavior Profile

Determine what data points to store

Previous parking garage behavior
Origin behavior

To be revisited at a later date.


Arctic datastore as Zipline datasource

Hello,
this datastore may also be worth to be add to zipline
https://github.com/manahl/arctic
at least it should be discussed here
Kind regards
See for arctic side https://github.com/manahl/arctic/issues/19

I wonder if perhaps this should be linked to odo instead where it will be available to zipline if https://github.com/quantopian/zipline/issues/659 gets implemented.

to my understanding that's quite different because with Blaze you won't have a Numpy arrays like in this datastore but you are yieding values using a generator.

I think odo handles streaming data sources too. @mrocklin?

odo supports streaming data sources with chunks

see https://github.com/ContinuumIO/blaze/issues/1185

Sorry, what am I supposed to be seeing in that issue?

Joe is correct that the right approach here is chunks.  The brief chunks documentation is here: http://odo.pydata.org/en/latest/type-modifiers.html#chunks

@llllllllll you are supposed to see your own post
for i, chunk in enumerate(odo(dat, chunks(pd.DataFrame), chunksize=10)):
    print("chunk %d" % (i + 1))
    for j, row in chunk.iterrows():
        print(row)

and you are right Blaze wasn't used in this simple example but I wonder if it will be the case if you want to align data.

Oh, were you just showing the iterable? I wasn't sure if you were responding to my comment there