Move the offset into the table slice state

:notebook_with_decorative_cover: Description
This reduces sizeof(table_slice) from 24 to 16.
Weirdly enough, the tests fail if I run the index test suite using vast-test -v 4 -s index, but succeed if I run the failing test individually using vast-test -v 4 -s index -t 'iterable integer query result'.
This is not a breaking change.
:memo: Checklist

[x] All user-facing changes have changelog entries.
[x] The changes are reflected on docs.tenzir.com/vast, if necessary.
[x] The PR description contains instructions for the reviewer, if necessary.

:dart: Review Instructions
Benchmark! I've requested @tobim as a reviewer for this.

Weirdly enough, the tests fail if I run the index test suite using vast-test -v 4 -s index, but succeed if I run the failing test individually

This is pathologic for having forgotten to initialize a factory. Since factory initialization is idempotent and process-wide, you may benefit from the side effects of other tests when running the whole test suite.

This is pathologic for having forgotten to initialize a factory. Since factory initialization is idempotent and process-wide, you may benefit from the side effects of other tests when running the whole test suite.

It's the other way around, though: It works if I run a single test, but fails if I run all index tests.

Huh, that is weird.
Maybe @tobim has an idea about what other side effects might be at play?!

The problem is in the test directly above. A local function rebase modifies the offsets of the table slices in question. Before this PR, the offset is located inside the table_slice, so not part of the shared data. In this PR, the offset is part of the shared data, so even though the table_slices are copied, rebase is modifying the content of the events fixture.
I guess rebase should create clones of the slices instead.

The fact that ubuntu-clang didn't fail here has me worried. The only explanation I have for that is undefined behavior.

I've pushed a fix that does a deep copy in rebase and rebased the branch onto master.
This could really use some cleanup, but I don't want to sink time into this until after we've benchmarked—after all, we'e still unsure whether we want this at all.

I've run some benchmarks on the side today and they confirm the initial numbers reported by @tobim: This is just slightly slower than before, but not by much. The additional API constraints are undesirable. I am closing this PR, we won't be merging this.


test: Add a test that runs with the IPAs in "isolation" mode

This checks that we aren't sending any ControlLists to libcamera that
could potentially cause problems.
Signed-off-by: David Plowman<EMAIL_ADDRESS>

@naushir Of course we probably want to delay merging this until we've got the necessary patches into libcamera - currently the new test is failing as we would expect!


Fix provider namespace changes

What does this PR do?

6ff19cb Fix test for #669
spec.template.spec.containers[0].args is an array, so notContains is
testing that the given string does not exist in the array, not whether
it is present as an arbitrary substring.
Issues like this can be detected before release by following a
"red-green" approach when writing tests (e.g. write a failing test, like
this one, then make the code change to fix it).

e478289 Fix #669
The original fix in #670 didn't actually fix the issue, rather the test
was broken and the fix didn't change anything (or already
operates on 'emptiness' as described in
https://helm.sh/docs/chart_template_guide/function_list/#or – e.g. .namespaces and not (empty .namespaces) have the same meaning inside or).

Motivation
#669 is still an issue.
More

[x] Yes, I updated the tests accordingly
[x] Yes, I ran make test and all the tests passed

It was quite tricky to get it work properly, without regression.
Thanks @connec for this PR !


[5.1] Url::to() from http://example.com/index.php

Hello there!
The Url::to() behaves differently when running from http://example.com/ and http://example.com/index.php
http://example.com/
Url::to('some/page') => http://example.com/some/page
http://example.com/index.php
Url::to('some/page') => http://example.com/index.php/some/page
If search crawler visits http://example.com/index.php, it may index a whole bunch of strange links such as http://example.com/index.php/some/page, which mirror real site pages. This is not very well for SEO, not to mention general usability.
One can even confirm this on laravel.com, visit this link, open dropdown with versions and look at the urls you see there, they all will start with "index.php".
I checked the framework test file for UrlGenerator to understand why tests do not catch that. And that's because a new artificial Request object is created for tests. That requests' SCRIPT_FILENAME will be empty. On the other hand, the natural Request object created from server globals will have its SCRIPT_FILENAME set to 'index.php'. That's why test works just fine, but reality sucks.
I've created a straightforward solution for the problem, but I'm not sure whether my approach is any good.
By the way, any site owner who want completely handle this problem, should also fix his nginx host by adding rewrite rule such as this one:
    location / {
        rewrite ^/(.*?)index\.php[^/] /$1? redirect;
        rewrite ^/(.*?)index\.php(?:/(.*))?$ /$1$2? redirect;
        try_files $uri $uri/ /index.php?$query_string;
    }

and also making sure his site has proper "canonical" meta tag.
Here are related links from elsewhere:
https://laracasts.com/discuss/channels/general-discussion/remving-indexphp-completely
http://stackoverflow.com/questions/25105872/remove-redirect-index-php-from-url-to-prevent-duplicate-urls

I don't think this PR is actually correct tbh. There is no reason to assume that file is actually named index.php.

Well, why then we don't check that when generating asset urls? I tried to keep this thing contained.

Just FYI, I ended-up with this in nginx conf in order to redirect traffic from wrong urls:
    location / {
        rewrite ^/(.*?)index\.php(?:/(.*))?$ /$1$2? redirect;
        try_files $uri $uri/ /index.php?$query_string;
    }
    if ($request_uri ~* "^(.*/)index\.php$") {
        return 301 $1;
    }

It may be worthwhile to update default forge and homestead host definitions.

How about an item in config to trigger this on and off?


Conversations are not getting finished or reset

Conversations are not getting finished or reset, because of that if u try to start a new conversation it will return an error 401 error because the conversation will have been expired on bot framework

Fixed.


Sent WETH Didn't Receive MKR

Hi,
Regarding this transaction -
https://etherscan.io/address/0x14fbca95be7e99c15cc2996c6c9d841e54b79425#tokentxns
You'll see the WETH left my wallet, however the MKR was never sent to it. Please advise how we can fix this
Chris

Please post a valid tx hash. The link you provided just points to the Oasis contract.


Parse <Foo.bar /> elements

Found in #124.
Reason parser used to parse JSX elements like <Foo.bar />:
https://astexplorer.net/#/gist/e21abaf96358b68be3ed3da19930be58/32e083720817c639502960b54984dff8396a3f7b.
React ppx also builds on top of this to allow custom make names, e.g.
let t = <Foo.bar />
let t = <Foo.Bar />

is transformed into:
let t = React.createElement(Foo.bar, Foo.barProps()); /* We can call `bar` instead of `make` */
let t = React.createElement(Foo.Bar.make, Foo.Bar.makeProps());

(shameless plug, can be tested in https://jchavarri.github.io/ppx-explorer/ 😜 )

@jchavarri Muchas gracias!


Add Cookbooks link to navbar

Closes https://github.com/ProjectPythia/projectpythia.github.io/issues/240
Related to https://github.com/ProjectPythia/pythia-foundations/pull/285

This is a small enough change that I feel confident merging it so that it is live before my demo.


Two level deep indexed access: read works, write fails

Bug Report
Reading from a two level deep Indexed Access type works, but writing gives "Type cannot be used to index".
🔎 Search Terms

Indexed Access
Mapped Type

🕗 Version & Regression Information

This changed between versions 3.3.3 and 3.5.1

⏯ Playground Link
Playground link with relevant code
💻 Code
enum A {
    First = "1",
    Second = "2"
}

type Values = { [a in A]: { [b: string]: string }}
const values: Values = {} as any;

function test<T extends A>(a: T, b: string) {
    const valueA = values[a];
    values[a] = valueA;

    const valueB = values[a][b]; // indexing Values[T] with string works
    values[a][b] = valueB; // => Type 'string' cannot be used to index type 'Values[T]'
}

🙁 Actual behavior
Indexing a type while reading works, while writing fails with the same indexer.
🙂 Expected behavior
Indexed reads and writes both work when using the same indexer.

I don't see what this has to do with TS4.6 or the linked PR.  Your code example has the same behavior in TS4.5 and indeed all the way back to TS 3.5.  I assume it's a consequence of #30769.

@jcalz seems you are right. I previously tested with a different return type for each of the Values with
interface Lookup {
  [A.First]: number
  [A.Second]: string
}
type Values = { [a in A]: { [b: string]: Lookup[a] }}

This is where 4.6 did come in to play. Simplifying the problem further I must have forgotten to check if it persisted in older versions. Will update the issue.

As @jcalz pointed out it does seem related to #30769. In particular the following:

Given a type variable T with a constraint C, when an indexed access T[K] occurs on the target side of a type relationship, index signatures in C are now ignored. This is because a type argument for T isn't actually required to have an index signature, it is just required to have properties with matching types.

function f3<T extends { [key: string]: any }>(obj: T) {
    let foo = obj['foo'];
    let bar = obj['bar'];
    obj['foo'] = 123;  // Error
    obj['bar'] = 'x';  // Error
}

If in my case values[a] is typed as Values[T], does that mean that it in effect becomes the T with constrain C that is referred to in the PR?

On read you're allowed to fall back to the constraint type, but as noted above this isn't allowed during a write

@RyanCavanaugh I can't say I understand why, that may be way above my pay grade :) But it seems to me
const valueB = values[a][b];
values[a][b] = valueB;

should never fail given no changes in a and b.

To correctly analyze that, the type of valueB would somehow have to encode that it came from the specific indices given by a and b. The type system is generally designed to track sets of values (types), not specific values or variables.


Correction in base.py file

Here: https://github.com/mnick/scikit-kge/blob/master/skge/base.py#L130
self.batch_size = np.ceil(len(xys) / self.nbatches)
self.batch_size = int(np.ceil(len(xys) / self.nbatches))
In the latest stable version of numpy (1.13.0) np.ceil() returns a float value not int.
Because of this error, my code was crashing with:

TypeError: slice indices must be integers or None or have an index method

Please make the change.

I still see same self.batch_size = np.ceil(len(xys) / self.nbatches)

I still found this mistake:
"slice indices must be integers or None or have an index method"

This also happened with me for the following snippet in base.py.
def _optim(self, xys):
        idx = np.arange(len(xys), dtype=int)
        self.batch_size = np.ceil(len(xys) / self.nbatches)
        batch_idx = np.arange(self.batch_size, len(xys), self.batch_size, dtype=int)

I just introduced the dtype=int parameter to fix it.


[DISCUSS] DataFusion upgrade policy

What is the problem the feature request solves?
During the Comet community call this morning, we discussed some options around how we keep up to date with changes in DataFusion core.
There are two main options:

Always have the Comet main branch use an official DataFusion release from crates.io
Between Comet releases, keep updating the main branch to use a recent revision of DataFusion and update it as needed to pick up new features / bug fixes

There are pros and cons to each approach.
Option 1 has less overhead, but means we have to wait longer for fixes, and could also find out that we are affected by breaking changes after DataFusion is already released.
Option 2 allows us to catch regressions earlier but means we cannot release a new version until DataFusion releases (although we would still be able to create patch releases from the previous release branch, using an older version of DataFusion).
Let's use this issue to discuss.

Always have the Comet main branch use an official DataFusion release from crates.io
Between Comet releases, keep updating the main branch to use a recent revision of DataFusion and update it as needed to pick up new features / bug fixes

I think we can always use an official DataFusion release from crates.io for a release of Comet.
But it is hard to guarantee that the Comet main branch always uses an official DataFusion release at any moment. For example, we might temporarily switch to revisions of DataFusion/arrow-rs to add workarounds/fixes or get features which are not available yet in the official releases.


Fix double invocation of postCollection when MultiBucketCollector is present

Description
Fixes a bug where postCollection would be called twice when a MultiBucketCollector is present. This was resulting in double counting the docs in the last segment for deferred bucket collectors.
Related Issues
Resolves #14000
Check List

[x] Functionality includes testing.
[x] API changes companion pull request created, if applicable.
[x] Public documentation issue/PR created, if applicable.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@sohami @reta @dennisoelkers could you please take a look?
Thanks!

@jed326: Tested it locally and it fixes the problem. Great work! Many thanks for the quick investigation and fix, as well as providing a workaround for 2.14!

Thank you @jed326 !


Terminal window is showing the same sticky top that the editor window just recently started showing

Does this issue occur when all extensions are disabled?: Yes/No

Version: 1.86.0-insider (user setup)
Commit: 789c802e75813bfb38ff2e13e4b322bd7e90124b
Date: 2023-12-14T05:36:50.991Z
Electron: 27.1.3
ElectronBuildId: 25612240
Chromium: 118.0.5993.159
Node.js: 18.17.1
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.22621
Steps to Reproduce:

Not sure what to caused it. Just running normal terminal commands.

I got this when I tried to scroll up through some test output:

It has a preview? Not sure what the new editor feature is called.

Oh I guess this is on purpose:

Doesn't seem to work correctly then. It's showing output, not the current command.

/duplicate https://github.com/microsoft/vscode/issues/201260


:fix: mount third param has type error

When I pass in the third argument in the mount function, but it is not an object form, but a string, the mount function will report Cannot use 'in' operator to search for 'Symbol()' in test and interrupt the rendering. And quit directly

Thanks but it's better to explicit warn incorrect arguments.


ReactiveSwift causes build error

make bootstrap works without problems, make test-all fails because of Atomic.swift in ReactiveSwift. The project doesn't build in Xcode as well, giving the error below:
/Users/akaralar/Development/github/ios-oss/Frameworks/ios-ksapi/Frameworks/ReactiveExtensions/Frameworks/ReactiveSwift/Sources/Atomic.swift:65:42: Let 'value' is private and cannot be referenced from an '@inline(__always)' function

Seems like this issue was fixed in ReactiveSwift by this commit: https://github.com/ReactiveCocoa/ReactiveSwift/commit/b5c383240593bbd6fc155b696f4bd7c68a48d944
I'm using Xcode 8.3.3 on macOS 10.12.6
Thanks for sharing knowledge!

Seems like my mistake, nevermind!


[Flaky Test] CP Migration Test Suite is flaky

How to categorize this issue?

/area testing
/kind flake
Which test(s)/suite(s) are flaking:
CP Migration Test Suite - /src/test/testmachinery/system/shoot_cp_migration
CI link:
Not applicable (internal test-machinery).
Reason for failure:
I noticed 2 flakes in the last days (the one is on gcp, the other one is on alicloud):
2022-08-18T14:52:53.859347117Z stdout F   In [AfterEach] at: /src/test/testmachinery/system/shoot_cp_migration/migrate_test.go:88
2022-08-18T14:52:53.859331672Z stdout F   The Shoot CP Migration health checks failed with: the following secrets did not have their data or labels persisted during control plane migration: [ca-provider-gcp-controlplane-d483fd48]

2022-08-22T15:02:35.54678121Z stdout F   In [AfterEach] at: /src/test/testmachinery/system/shoot_cp_migration/migrate_test.go:88
2022-08-22T15:02:35.546775973Z stdout F   The Shoot CP Migration health checks failed with: the following secrets did not have their data or labels persisted during control plane migration: [ca-provider-alicloud-controlplane-f36f9b25]

More flakes:
2022-08-23T15:01:48.560884288Z stdout F   In [AfterEach] at: /src/test/testmachinery/system/shoot_cp_migration/migrate_test.go:88
2022-08-23T15:01:48.56087846Z stdout F   The Shoot CP Migration health checks failed with: the following secrets did not have their data or labels persisted during control plane migration: [ca-provider-azure-controlplane-9e2c8c05]

Anything else we need to know:
Environment:

Gardener version: 195189a61500b1010d9555c816755a91c0747e7c

cc @plkokanov

/assign @plkokanov

More verbose logging from a failed run:
Secret shoot--it--tmig2-6bq-hs-mgr/ca-provider-aws-controlplane-bdef740c did not have it's data persisted.
Secret shoot--it--tmig2-6bq-hs-mgr/ca-provider-aws-controlplane-bdef740c did not have it's labels persisted: labels before migration: map[checksum-of-config:6178420258531182942 issued-at-time:1662389362 last-rotation-initiation-time: managed-by:secrets-manager manager-identity:provider-aws-controlplane name:ca-provider-aws-controlplane persist:true valid-until-time:1978008562], labels after migration: map[checksum-of-config:6178420258531182942 issued-at-time:1662390520 last-rotation-initiation-time: managed-by:secrets-manager manager-identity:provider-aws-controlplane name:ca-provider-aws-controlplane persist:true valid-until-time:1978009720]

The secret name does not change but its data is regenerated.
We were discussing that the Secret can be regenerated during restore if is not present in the ShootState for some reason.
During migrate of a ControlPlane we delete the ControlPlane. Deletion of ControlPlane at the end calls sm.Cleanup()
https://github.com/gardener/gardener/blob/cffdb9fd10d598be614d90055ef1bf79d4e5a791/extensions/pkg/controller/controlplane/genericactuator/actuator.go#L533
which should also delete the Secrets. But the gardenlet's shootsecret controller does not remove Secrets from the ShootState when a Secret is deleted during migrate operation of a Shoot.
https://github.com/gardener/gardener/blob/b1e7f278b6d3bc781631fbbb3b3292c816355fe2/pkg/gardenlet/controller/shootsecret/reconciler.go#L142-L143
For now I am not able to explain the flakes or reproduce them.

I am now wondering whether the issue can be caused by https://github.com/kubernetes/kubernetes/issues/110625 (similar to https://github.com/gardener/gardener/issues/6441). In short the kube-apiserver does not always return all of the resources when --label-selector /--field-selector are used. Our Seeds are at 1.23.6, the corresponding backport for 1.23 is present in 1.23.9+.
I think it makes sense to update our Seeds to 1.23.9+ just to make sure that we are not hitting the above-mentioned issue in the context of this issue (or any other one). @dguendisch @BeckerMax WDYT?

Sure, I added an internal issue on the update, let's discuss the priority there.

Wrt https://github.com/gardener/gardener/issues/6565#issuecomment-1248269874 I am able to reproduce according to the steps in https://github.com/kubernetes/kubernetes/pull/110652#issue-1276119362 but I am not sure whether it can be reproduced with client-go/controller-runtime client. --chunk-size flag has client side implementation that relies on the limit and continue query params.
Anyways, let's see whether this issue still occurs in new runs of the test.

There is 1 failure from 2 days ago. The newest failures are due to https://github.com/gardener/gardener/issues/6703.

Meanwhile our Seeds were updated to 1.23.9. I now checked and was not able to see the particular error from this issue occurring for the past 10 days. Let's keep it open for a while to see whether it will occur again in the next days.

I now actually noticed a failure on other landscape from 2 days ago:
2022-10-05T15:57:55.202114102Z stdout F   Secret shoot--it--tm1m0-hgk-hs-mgr/ca-provider-openstack-controlplane-6a1a1e13 did not have it's labels persisted: labels before migration: map[checksum-of-config:14896576601499449788 issued-at-time:1664983816 last-rotation-initiation-time: managed-by:secrets-manager manager-identity:provider-openstack-controlplane name:ca-provider-openstack-controlplane persist:true valid-until-time:1980603016], labels after migration: map[checksum-of-config:14896576601499449788 issued-at-time:1664984997 last-rotation-initiation-time: managed-by:secrets-manager manager-identity:provider-openstack-controlplane name:ca-provider-openstack-controlplane persist:true valid-until-time:1980604197]
2022-10-05T15:57:55.202110499Z stdout F   Secret shoot--it--tm1m0-hgk-hs-mgr/ca-provider-openstack-controlplane-6a1a1e13 did not have it's data persisted.

In short, the issue occurs due to a transient error in the migrate flow after the ControlPlane Destroy. In the migrate flow we first Restore the ControlPlane, then we Destroy it. If a transient error occurs after the ControlPlane Destroy, in the next try we will Restore the ControlPlane which will created fresh new ca-provider-{provider}-controlplane Secret (because the existing ones were already deleted during Destroy) which will be updated/synced to the Shoot state by gardenlet.
Restore of ControlPlane calls Reconcile which generates all Secrets if they don't exist.
https://github.com/gardener/gardener/blob/cffdb9fd10d598be614d90055ef1bf79d4e5a791/extensions/pkg/controller/controlplane/genericactuator/actuator.go#L579
https://github.com/gardener/gardener/blob/cffdb9fd10d598be614d90055ef1bf79d4e5a791/extensions/pkg/controller/controlplane/genericactuator/actuator.go#L212-L217
Delete/Migrate of ControlPlane deletes all SecretManager Secrets:
https://github.com/gardener/gardener/blob/cffdb9fd10d598be614d90055ef1bf79d4e5a791/extensions/pkg/controller/controlplane/genericactuator/actuator.go#L533
Steps to reproduce:

Create a Shoot on Seed foo.

Save the ca-provider-{provider}-controlplane Secret to be able to compare it afterwards.

Simulate a transient error after https://github.com/gardener/gardener/blob/036fa069d610a2a62f7b819493df3bd19aa779a7/pkg/gardenlet/controller/shoot/shoot_control_migrate.go#L280:

I used a webhook that forbids deleting the kube-apiserver Deployment.

Trigger CP migration to Seed bar.

Make sure that on every retry of the migrate flow the ControlPlane is redeployed and destroyed and the ca-provider-{provider}-controlplane Secrets are recreated.

Compare the ca-provider-{provider}-controlplane in the ShootState and the one you saved in step 2. and make sure they are different.

So it's an actual bug that we found here, nice summary @ialidzhikov, thanks. Do you have any ideas/suggestions what we can improve?

Before the introduction of the secrets manager we used to redeploy all secrets from the shoot state at the start of the migrate phase. Not sure if the same can be done now though - basically change this code:
https://github.com/gardener/gardener/blob/66b1975adf5d6656930d1273c150792028646ad5/pkg/operation/botanist/secrets.go#L59-L63
to also be executed during Migrate phase.

and only redeploy the ControlPlane and the kube-apiserver if there are any ManagedResources or extension resources retrieved from this list inside the shoot's namespace.

I don't think we want to make such assumptions. Extensions using ManagedResources is just a convention, not a requirement and rather an implementation detail.
Can we rather not redeploy the ControlPlane if it is already deleted?

I found the issue that was causing this redeployment in the first place: https://github.com/gardener/gardener/issues/4484. Basically, [the WakeUpKubeAPIServer])(https://github.com/gardener/gardener/blob/40b0bf10522e53c55ceaf1b361a4d016a94fe741/pkg/gardenlet/controller/shoot/shoot_control_migrate.go#L229-L233) would cause problems for providers for which the webhook that mutates the kube-apiserver deployment relies on the cloud-provider-config secret (e.g. azure and alicloud), if the ControlPlane is gone. Both RestoreControlPlane and WakeUpKubeAPIServer steps are not executed if the kube-apiserver deployment does not exist, however we cannot delete the ControlPlane after deleting the kube-apiserver deployment, because then the deletion of ManagedResources that are created by the ControlPlane reconciliation would fail.
Another idea that sprang to mind is to not restore the ControlPlane and do not wake up the kube-apiserver, if it has already been woken up (meaning we would need to add a check if the replicas are > 0), although that's also a bit counterintuitive to what we generally do when deploying components.

As discussed in our meeting today, the only reason that the ControlPlane is deployed before the kube-apiserver was that we don't have CSI for all providers when the Kubernetes version is < 1.21. Consequently, when we drop support for shoots < 1.21, we can clean all this up (i.e., first deploy kube-apiserver, then deploy ControlPlane) and then these issues should disappear, am I right?
In this case, I would vote to not make it even more complicated now and wait for above mentioned cleanup. Instead, maybe we can improve the test assertions to accept re-generated secrets of the provider extensions so that the test does no longer flake. It shouldn't be critical if they are recomputed after a migration.

@rfranzke we could temporarily skip this assertion similar to what we did for resources inside the Shoot that are generated from ManagedResources: https://github.com/gardener/gardener/blob/1e01b2163c2383f3692d70e14f4f85072211b4e6/.test-defs/MigrateShoot.yaml#L20
Btw do we currently have any timeframe for dropping support for k8s 1.20?

I think we can start with the removal after 1.63 got released, cc @dimitar-kostadinov @ialidzhikov.
Generally, we are in discussion about applying a general guideline for supporting only 3-4 Kubernetes versions at a time, but that's not yet fully clarified.


Using datepicker component as input

Hello there!
There is no documentation how to use datepicker component as input. Only inline datepicker is available at the moment as far as I can see. Is it possible to make it work as input?
Thanks.

Is there any solution to enable datepicker in input?

https://github.com/valor-software/ng2-bootstrap/issues/1455
check this , it support input and icon show hide

added documentation for new datepicker,
and how to use it with inputs
available in v1.9.2
http://valor-software.com/ngx-bootstrap/#/datepicker


feat: Modify Column Type

I hereby agree to the terms of the GreptimeDB CLA.
Refer to a related PR or issue link (optional)
https://github.com/GreptimeTeam/greptimedb/issues/3517
What's changed and what's your intention?
Support: ALTER TABLE <table_name> ALTER COLUMN <column_name> TYPE <data_type>;
ref: https://www.postgresql.org/docs/current/sql-altertable.html
Tips: sql parser does not support Modify Column temporarily, I have created a PR: https://github.com/sqlparser-rs/sqlparser-rs/pull/1216
public=> CREATE TABLE test(i INTEGER, j TIMESTAMP TIME INDEX);
OK 0
public=> ALTER TABLE test ALTER COLUMN I TYPE STRING;
OK 0
public=> DESCRIBE t2;
+--------+----------------------+-----+------+---------+---------------+
| Column | Type                 | Key | Null | Default | Semantic Type |
+--------+----------------------+-----+------+---------+---------------+
| i      | String               |     | YES  |         | FIELD         |
| j      | TimestampMillisecond | PRI | NO   |         | TIMESTAMP     |
+--------+----------------------+-----+------+---------+---------------+

Checklist

[x]  I have written the necessary rustdoc comments.
[x]  I have added the necessary unit tests and integration tests.
[x]  This PR does not require documentation updates.

Nice job🚀

Tips: sql parser does not support Modify Column temporarily, I have created a PR: https://github.com/sqlparser-rs/sqlparser-rs/pull/1216

BTW, Should we support both dialects(i.e., ALTER TABLE <table_name> ALTER COLUMN <column_name> TYPE <data_type>; and ALTER TABLE <table_name> MODIFY <column_name> INT )?

https://github.com/GreptimeTeam/greptimedb/issues/3517 mentioned that it supports MySQL dialects as much as possible. I think it is good to only support MySQL.
The current PostgreSQL syntax is only for testing

Run make fmt for formatting the code.

Since altering column types is a big feature, we might need further discussions and implement it carefully. Could you please describe how you implemented this feature in the issue?
We also need to consider the following things:

Conversion rule

Do we allow altering a string column to an integer column?
Do we allow converting int16 to int8 or uint16?

Should we allow altering time index or tag column types? How to support that?
How it works?

Does it rewrite all SST files?

Query performance impact
Should other region engines such as metric and file support this?

What's more, I'd suggest implementing this step by step as it also depends on other crates. For example:

Support altering column type in the region engine first
Support this in the region server, which also modifies the greptime-proto crate
Support parsing SQL texts to alter the column type

Conversion rule

Do we allow altering a string column to an integer column?
Do we allow converting int16 to int8 or uint16?

Should we allow altering time index or tag column types? How to support that?

How it works?

Does it rewrite all SST files?

Query performance impact

Should other region engines such as metric and file support this?

Conversion rule

Q 1: Do we allow altering a string column to an integer column?
A 2: String can theoretically be converted to any type, so it should be possible
Q 2: Do we allow converting int16 to int8 or uint16?
A 2: I think it should be allowed, specific reference： ConcreteDataType::can_arrow_type_cast_to & VectorOp::cast

Q 3: Should we allow altering time index or tag column types? How to support that?

A 3: src/table/src/metadata.rs L479 column verification will be performed here, and modification of timesindex and tag is not allowed.

How it works?

Q 4: Does it rewrite all SST files?
A 4: It is definitely not a good idea to completely modify the data, especially for time series databases. I implemented it with reference to add/drop column, and checked whether expect and actual are consistent in compat.rs. When the names are consistent but the types are inconsistent, type conversion will be performed based on IndexOrDefault::Index. Therefore, ModifyColumn does not modify the data, but temporarily performs type conversion when reading, and changes the type to the modified type when the next compaction is triggered to avoid type conversion (this can also be done when modify column is performed multiple times in a short period of time, No additional overhead will be incurred)

/// Index in source batch or a default value to fill a column.
#[derive(Debug)]
enum IndexOrDefault {
    /// Index of the column in source batch.
    Index {
        pos: usize,
        cast_type: Option<ConcreteDataType>,
    },
    /// Default value for the column.
    DefaultValue {
        /// Id of the column.
        column_id: ColumnId,
        /// Default value. The vector has only 1 element.
        default_vector: VectorRef,
    },
}

Q 5: Query performance impact？
A 5: as I said before, the data needs to be type converted before the next compaction, so there is a column type conversion performance problem when reading.
Q 6: Should other region engines such as metric and file support this?
A 6: I don't know how to use other engines. hope you can make more suggestions in this regard

Q 1: Do we allow altering a string column to an integer column?
A 2: String can theoretically be converted to any type, so it should be possible
Q 2: Do we allow converting int16 to int8 or uint16?
A 2: I think it should be allowed, specific reference： ConcreteDataType::can_arrow_type_cast_to & VectorOp::cast

What about error handling?

We can't cast a string like 'hello' to an integer
Converting int16 to int8 might overflows
arrow::cast may returns an error

Maybe we can only support a subset of conversion rules that arrow implements.

src/table/src/metadata.rs L479 column verification will be performed here, and modification of timesindex and tag is not allowed.

Modifying the data type of the time index might be helpful. e.g. Alter a timestamp(second) to timestamp(millisecond). But we can support it later.
For other engines (file, metric), you could refer to their implementation of the RegionEngine trait. Maybe we should disallow modifying the column type for those engines.
I'm not going to implement ALTER COLUMN in this single PR. We can convert https://github.com/GreptimeTeam/greptimedb/issues/3517 into a tracking issue. You can summarize your design in that issue and list your steps to implement it. Then we can move the discussion to the issue.
It'd be better if we only modify a single crate in each step. e.g.

Add a new variant for modifying a column to the AlterRegionRequest in the store-api
Support that variant in mito2
Deal with other region engines
Add the variant to the gRPC request
Support it in the region server
Parser
Support ALTER COLUMN statement


Refactoring of StructuralRules.groupSequence()

Good idea! Please rename groupSequenceMakeConjunctionAndCreateTask to createSequenceTask and update your PR. it can be merged then.


Gimbal MAVLink configuration and control support

WIP
Will test this next week

Bench tested. Could someone have quick look? :)

Thanks!


Enitity Framework Core Support

Please support EF Core

I was dissapointed to see this was for .net framework ef, was trying to figure out why I don't have IDbAsyncEnumerable interface


Update feeder to 3.5.10

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.
[x] The commit message includes the cask’s name and version.

old appcast 404s


Release multi threshold (pipeline & code)

### Other release notes to watch out for
- [ ] Also update: email logo URLs on prod API (+ remove old logo's from mailchimp) see task 1533
- [ ] Make sure new packages (mjml/more?) are processed correctly
- [ ] update trigger statements all countries
- [ ] Monitor first pipeline run on production (check raster file writing permissions)

Refinement:

Prerequisite: some test item.
Deploy pipeline and code at same time.
Code deployment: also add data via API on production.
Out of scope for this item: version nrs code and pipelines? Leave it for this item. Phuoc will get an idea on how to approach this separately. Jannis knows about a prior Spike in DevOps. With Bouke and Aki as well.

Memory will give a training 4 to 7 November, so needs to at least be able to demo the new release then.

@p-phung I've made a task in this item to create the trigger statements for all countries. Can you provide them with help of @jmargutt  (technical phrasing) + @gal-agmon (UX copy)?

@gal-agmon @jannisvisser where can I find all the trigger statements for riverine floods?

@p-phung https://github.com/rodekruis/IBF-system/blob/master/services/API-service/src/scripts/json/notification-info.json

@p-phung I've made a task in this item to create the trigger statements for all countries. Can you provide them with help of @jmargutt (technical phrasing) + @gal-agmon (UX copy)?

@p-phung can we have a shared place to review all statements?


doesn't scrobble to last.fm reliably

Seems to only be picking up like 5% of scrobbles.

Last.fm were having some API issues last week that affected scrobbling - I was having the exact same issue: https://getsatisfaction.com/lastfm/topics/and-scrobbling-stopped-working-again
You should be able to fix this by deauthorizing the player, then reauthorizing (Preferences > Last.fm > Deauthorize).  You may need to restart the player in between those steps.
Let me know if you're still having issues.


Mutation APIs for ICS Team Info

The mutations to add/edit/remove a mentor or mentee have been added.

@all-contributors add @riteshsp2000 for Code, Maintenance


Add an example forge script for easy test to anvil

Time spent on this PR: 0.1
Pull request type
Please check the type of change your PR introduces:

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

What is the current behavior?
No way to easily run some forge script to deploy into a real EVM
What is the new behavior?
Updated config to target anvil by default and an example script.
Note: once the end to end refacto is done, I think that we'll update the structure of the solidity project

How does one run this script? Should we add comments / a make command?

tbh I'm not a huge fan of wrapping commands in makefile, it creates a later of complexity/abstraction and prevent people from learning how to use the few basic tool of the stack. It's like always rewriting a custom cli instead of using the standard one.

I think because in our case we have specific flags we need to pass everytime to make it work, it's worth it? Unless the plane command just works

I think because in our case we have specific flags we need to pass everytime to make it work, it's worth it? Unless the plane command just works

used with anvil, the plain command forge scripts path/to/script works


update

Add IPV6 compatibility in the voting page to avoid the infinite loader
@if(setting('vote.ipv4-v6-compatibility'))     @push('scripts')         <script src="https://ipv6-adapter.com/api/v1/api.js" async defer></script>     @endpush @endif

This theme is already compatible as it doesn’t override the vote views.

This theme is already compatible as it doesn’t override the vote views.


NetHttpRequest should only set Content-Length if it's not set.

See https://github.com/google/google-http-java-client/issues/346.
The reason this bug isn't more common is probably that nobody sets sun.net.http.allowRestrictedHeaders=true. If they do, and they set Content-Length, then NetHttpClient will duplicate it.

CLA signed.


Enhance autoprec function in mpmath library for precision control and early termination

According to issue #751 implemented next functionality:
Control Precision Increase Rate: Modified autoprec to accept a parameter (learning rate) to regulate the speed of precision increase.
Early Termination on First Successful Computation: Extended autoprec to include a parameter (early_termination) to stop precision increase upon the first successful computation.

Ok, feel free to reopen pr, when you will be ready to continue your work and address review comments.


Avoid scrollbars to appear if they aren't needed

It should fix issue #77. Please review.

This PR was reimplemented at Ancor's desk, he will create another to fix the issue. Thanks @jreidinger for the tip.


Halogen.Svg.Attributes.Path.c  - missing whitespace between some parameters causes incorrect markup

c ref x1_ y1_ x2_ y2_ x_ y_ =
PathCommand $ renderCommand ref "c"
<> show x1_
<> ","
<> show y1_ -- there should be a space after y1_
<> show x2_
<> ","
<> show y2_  -- there should be a space after y2_
<> show x_
<> ","
<> show y_

Care to submit a PR?

Sure - done.

Fix has been released as v5.0.2 and package set PR is pending merge.


feat(FMP-228, ui2): include chain information

Current dependencies on/for this PR:

main

PR #9   👈

This comment was auto-generated by Graphite.


collection view datasource mthod not getting called

Hi,
I have more than one type of cell in a table view.One of the types is a collection view rest are not. In that case, I used the code u referred but the data source methods of collection view are not getting called.
Hope you understand what I am trying to say and expect a solution from your side
thank you

Hey, sorry to hear you're having trouble. This is a repo for a tutorial, not a place where I debug your problems for you. Double-check your code and list your assumptions, then test them. You can do this, good luck.

@ashfurrow great tips for debugging,long time no see @ashfurrow  What are you doing now?

@MarcSteven thanks – I've been pretty busy at work and moving (within NYC, which has been difficult). Things starting to settle back down but still more to do than hours in a day 😅

That make sense I reviewed your status via twitter ,thank for your sharing ,learn more from you .Welcome to China next time and then give more developers a great talk about software engineer. @ashfurrow Good luck to you !!


Historical Rock API endpoint

Description
We were planning to use Github Gists to save rocks, but I don't think this would be easy to do without authentication.
Instead we could spin up a postgresql DB on railway, and then save rocks to the DB on compile.

Type
What it would do

POST
Create a new record

PUT
Update the record

Each session would get it's own session record which would link to rocks. The only data that would be stored for individual rocks is a UUID, the sessionID, ID of rock as seen in the session, and the input. log & output would be compiled on request.
API route
/historicalRock/<date>/<id>
Date format would be DDMMYYYY

We could Still load from a gist without Authentication, I think

This is working and deployed to production.
The endpoint also loads it into cache


Feature: [trigger configuration] add new parameter for control delay  between sql scans from triggers

#558 brings weekly, daily and hourly intervals

#558 brings weekly, daily and hourly intervals


Revert "wgpu: init at 22.1.0"

This package was added in https://github.com/NixOS/nixpkgs/pull/345248 to address https://github.com/NixOS/nixpkgs/issues/344689, a request for a package of wgpu-native, wgpu’s native WebGPU implementation that other applications can use as a library.
However, it doesn’t package that at all; instead, it contains only several binary utility and example programs shipped as part of wgpu, and in fact, these were already present as the more appropriately‐named wgpu-utils package, which needs only an update.
Given that this package was added without the due diligence to check whether the software being packaged was what was being requested, or whether it was already present under an obvious name, I don’t think there’s an argument for retaining this duplicate. wgpu-utils can be updated and refactored to be on par with this package, and if the library that was actually requested is ever packaged, it should be called wgpu-native instead.
This reverts commit 27e304c09e479c3ba328c22d58fb7c5a7dd00038.

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

My fault.


Reopening a PR triggers labeling rules

In order to coerce autolabeler into triggering on PRs which were opened before the labeling rules were setup, a repo admin should be able to close/re-open a PR in order to get autolabeler to apply labeling rules.
tl;dr, this triggers labeling rules when a PR has been closed and then reopened, rather than only the first time a PR was opened.
p.s., apologies for sloppy commit messages. I can definitely fix them up if desired.

Any interest in this? If not, no worries at all, we can close out this PR 👍

I manually merged this in https://github.com/mithro/autolabeler/commit/a56874f03ec76fbce6e477c4c52367ae31f5e70b


Support realistic delays in device simulator

Support realistic delays in device simulator

The delay should be a random configurable interval, not a fixed 1 second delay

The device-simulator supports now delays.
The delay is configurable:
response.delay.time2000
response.delay.random.range=2000
The settings work fine.
In the logging the following is visible:
12:05:42.788  27863 [New I/O worker #6] INFO  c.a.o.w.service.OslpChannelHandler - Sleeping for 3595 milliseconds


use obspy input/ouput and signal processing tools where appropriate

Status update:  preprocess.base now has obspy as a dependency; preprocess.legacy does not.  Since obspy adoption is a major change, additional testing is underway, beyond the usual integration tests and readthedocs example.

Are there any plans to make readers format exclusive? For example having a singular reader for SU formats or will they remain a combination of solver + format? Also are the processing routines be migrated exclusively to Obspy stream objects? I'd like to make sure any future code follows the current direction.

Are there any plans to make readers format exclusive? For example having a singular reader for SU formats or will they remain a combination of solver + format?

Great question.   I think an ideal solution would be to have say, seisflows.solver.data specify the path to the data, and seisflows.preprocess.reader be an all purpose reader that simply reads from that paths.  Unfortunately though, this might create a circular import.
For now, probably we will stick to the current way of doing things in preprocess.base, because  that module is currently pretty clean, and for a number of other reasons including idiosyncratic SPECFEM filename conventions.
Feel free to either add your own readers to seisflows.seistools.readers, or to add your own completely new seisflows.preprocess class and build your SU reader (probably just a thin wrapper over obspy.segy.core.readSU ?) directly into to it.
Also are the processing routines be migrated exclusively to Obspy stream objects?

Yes, the plan is to transistion to a new data processing class in which all signal processing operations are handled by obspy calls on stream objects.  All new development will make use of obspy stream objects.  Because things are set up in a modular way, the old way of doing things preprocess.legacy should continue to work indefinitely.

P.S.  I would that, if you haven't looked at seisflows.preprocess.base recently, it might be worth a short glance.  It has been cleaned up considerably this month.

Is it fair to assume that the reader/writer routines will adjusted to the format in preprocess.base? The current reader/writers include various positional/keyword arguments not used in the processing class.

The extra arguments are provided to support use cases like noise tomography, which are not currently part of the seisflows main repository, but which users might want to pursue through their own subclasses and possibly contribute to the main repository in the future.

Bug in preprocess/base.py: Positional arguments inconsistency
get_time_scheme returns dt, nt, t0 whereas functions in the base class call nt, dt, _. dt and nt are swapped.

Current Obspy read/write for SU files is in a deprecated format.

Update:  I made some of the changes Gian suggested in my own fork, in particular, doing away with complicated readers and writers in favor of simple wrappers over obspy calls.   In the next or month or two, hope to roll out these changes as part of the upcoming tagged release (issue #29 ).


ENH: Add type/format for CheckV database

This PR closes #1 .

Defines a semantic type for the CheckV database.

The CheckV database is fetched once and then used multiple times for viromics analysis.
Set up the environment
mamba create -n q2-viromics -c conda-forge -c bioconda -c https://packages.qiime2.org/qiime2/2024.10/metagenome/passed/ -c defaults q2cli q2-types checkv  pyhmmer

Activate q2-viromics environment
conda activate q2-viromics

Clone the repo and checkout the PR branch
git clone https://github.com/bokulich-lab/q2-viromics.git
cd q2-viromics
git fetch origin pull/4/head:pr-4
git checkout pr-4
pip install -e .

1. Download initial  CheckV database directory
here
2. Test it out!
Import database
# It may take some time!
qiime tools import --type 'CheckVDB' --input-path db --output-path checkv_db.qza

Hey @VinzentRisch, I made the corrections, you can have a look.


ImportError: cannot import name 'xla_client' from 'jaxlib' (unknown location)

Building jaxlib from source on Windows.
Installation sequence as here and here

PowerShell: https://github.com/PowerShell/PowerShell/releases/tag/v7.1.2
Bazel: https://github.com/bazelbuild/bazel/releases
MSYS2: https://repo.msys2.org/distrib/x86_64/msys2-x86_64-20210105.exe
Check if there is pacman in PATH
Install patch realpath: pacman -S patch realpath
Check that the PATH contains bazel, path, realpath
Clone the repository: git clone https://github.com/google/jax
We go to the directory
Activating the conda environment: conda activate
Trying to build jaxlib: python. \ Build \ build.py
If so, install jax: pip install -e.

Trying to run the package in Python
>>> import jax.numpy as jnp
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "c:\bin\jax\jax\__init__.py", line 22, in <module>
    from .api import (
  File "c:\bin\jax\jax\api.py", line 39, in <module>
    from . import core
  File "c:\bin\jax\jax\core.py", line 31, in <module>
    from . import dtypes
  File "c:\bin\jax\jax\dtypes.py", line 32, in <module>
    from .lib import xla_client
  File "c:\bin\jax\jax\lib\__init__.py", line 53, in <module>
    from jaxlib import xla_client
ImportError: cannot import name 'xla_client' from 'jaxlib' (unknown location)

But xla_client it is C:\bin\jax\bazel-jax\external\org_tensorflow\tensorflow\compiler\xla\python\xla_client.py
And how to introduce them? Where is the mistake?
Sys.info()
sysname        release        version       nodename        machine
"Windows"       "10 x64"  "build 19042"  "VLAD-MASTER"       "x86-64"

Did you install the jaxlib you built?
You need to pip install dist/jaxlib*.whl in your jaxlib directory.

Thank. I will try.

"Did you install the jaxlib you built?"
Look at the logs and tell me where I am from jaxlib.
instal_jax.txt
cla_client_test.txt


lua error 283

I keep getting this lua error, ive tried reinstalling the mod even tried uninstalling all others. Please help. Here is the code

Message: Interface\AddOns\GSE\API\Storage.lua:283: bad argument #1 to 'getn' (table expected, got nil)
Time: Fri Nov  9 00:21:54 2018
Count: 2
Stack: Interface\AddOns\GSE\API\Storage.lua:283: bad argument #1 to 'getn' (table expected, got nil)
[C]: in function getn' Interface\AddOns\GSE\API\Storage.lua:283: in function ImportSerialisedSequence'
Interface\AddOns\GSE_GUI\Import.lua:95: in function GUIImportSequence' Interface\AddOns\GSE_GUI\Import.lua:44: in function <Interface\AddOns\GSE_GUI\Import.lua:44> (tail call): ? [C]: ? [string "safecall Dispatcher[4]"]:9: in function <[string "safecall Dispatcher[4]"]:5> (tail call): ? Interface\AddOns\GSE\Lib\AceGUI-3.0\AceGUI-3.0.lua:314: in function Fire'
...s\GSE\Lib\AceGUI-3.0\widgets\AceGUIWidget-Button.lua:22: in function <...s\GSE\Lib\AceGUI-3.0\widgets\AceGUIWidget-Button.lua:19>
Locals:

You have a corrupt macro.  Until you fix that uninstalling and reinstalling will do nothing.
See https://wowlazymacros.com/forums/topic/gse2-howto-fix-unable-to-import-macros/ for the details.
TimothyLuke

On 9 Nov 2018, at 5:52 pm, GreedHD<EMAIL_ADDRESS>wrote:
I keep getting this lua error, ive tried reinstalling the mod even tried uninstalling all others. Please help. Here is the code
Message: Interface\AddOns\GSE\API\Storage.lua:283: bad argument #1 to 'getn' (table expected, got nil)
Time: Fri Nov 9 00:21:54 2018
Count: 2
Stack: Interface\AddOns\GSE\API\Storage.lua:283: bad argument #1 to 'getn' (table expected, got nil)
[C]: in function getn' Interface\AddOns\GSE\API\Storage.lua:283: in function ImportSerialisedSequence'
Interface\AddOns\GSE_GUI\Import.lua:95: in function GUIImportSequence' Interface\AddOns\GSE_GUI\Import.lua:44: in function <Interface\AddOns\GSE_GUI\Import.lua:44> (tail call): ? [C]: ? [string "safecall Dispatcher[4]"]:9: in function <[string "safecall Dispatcher[4]"]:5> (tail call): ? Interface\AddOns\GSE\Lib\AceGUI-3.0\AceGUI-3.0.lua:314: in function Fire'
...s\GSE\Lib\AceGUI-3.0\widgets\AceGUIWidget-Button.lua:22: in function <...s\GSE\Lib\AceGUI-3.0\widgets\AceGUIWidget-Button.lua:19>
Locals:
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

The GSE.lua file im supposed to fix is non-existent in my folder.

It will be there somewhere.  Without it GSE can’t operate.
It’s usually c:\path\to\World of Warcraft\WTF\Account{Your accounts name}\SavedVariables\GSE.lua
TimothyLuke

On 9 Nov 2018, at 6:32 pm, GreedHD<EMAIL_ADDRESS>wrote:
The GSE.lua file im supposed to fix is non-existent in my folder.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

I have no clue what to do, not good with coding at all.

Or even looking at it, im sorry to be a bother.

Is which case do this:
/gs showspec
Pay attention to the Classid
/run GSELibrary[the class id] = {}
This will reset the class you are playing and you will need to import macros from scratch
TimothyLuke

On 9 Nov 2018, at 6:43 pm, GreedHD<EMAIL_ADDRESS>wrote:
Or even looking at it, im sorry to be a bother.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.


Informative admin dashboard

Create site stats for admin:

number of articles to date
number of articles by topic
number of articles by question number
number of articles by source
number of search requests by topic
number of search requests by question number

[x] number of articles to date
[x] number of articles by topic, top and bottom
[x] number of articles by question number, top and bottom
[ ] number of search requests by topic
[ ] number of search requests by question number


Scalafix and Dotty

Scalafix libraries aren't published to Dotty, and require CrossVersion.full, which is incompatible with withDottyCompat.  This is so macro-laden, I doubt that Dotty compat even works.
Commented it out on the Dotty branch for now, but we need a way forward.

I don't think we need to run scalafix under Dotty, and the project is already split out from the aggregate build.


termscp: 0.11.2 -> 0.12.2

Description of changes
Diff: https://github.com/veeso/termscp/compare/v0.11.2...v0.12.2
Changelog: https://github.com/veeso/termscp/blob/v0.12.2/CHANGELOG.md

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 258850 run on x86_64-linux 1

1 package built:

termscp


For non-configurable filters, mark fields as pub

I would like to be able to set all fields for the varying filters - and I personally only like defining new for structs if more than just copying fields into a struct has to be performed to initialize it hence why I've just marked the fields as pub.

I'm sorry, but I don't want to make those fields public


Fix username duplicates

Fixes username duplicates by adding a 'lower_username' to a user's userdata, this is checked when creating new accounts to make sure duplicate accounts with different capitalization won't be created.

Don't merge, I forgot one crucial thing


WIP Fix in-place tensor mutation when sharding

Add option to construct sharded tensors without inserting device placement operations.
Add a simple test for in-place addition
t += 1
It exports and runs on IREE.
When unflattening a sharded tensor during exporting insert in-place device placements, which get translated to function argument affinity attributes.

This depends on https://github.com/iree-org/iree-turbine/pull/220


HBASE-23887 Bug fix heavyEvictionMbSizeLimit (AdaptiveLRU cache)

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 29s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ master Compile Tests _

+1 :green_heart:
mvninstall
3m 49s
master passed

+1 :green_heart:
compile
3m 13s
master passed

+1 :green_heart:
checkstyle
1m  6s
master passed

+1 :green_heart:
spotbugs
2m  3s
master passed

_ Patch Compile Tests _

-1 :x:
mvninstall
1m 37s
root in the patch failed.

-1 :x:
compile
0m 29s
hbase-server in the patch failed.

-0 :warning:
javac
0m 30s
hbase-server in the patch failed.

-0 :warning:
checkstyle
0m 18s
The patch fails to run checkstyle in hbase-server

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

-1 :x:
hadoopcheck
1m 47s
The patch causes 16 errors with Hadoop v3.1.2.

-1 :x:
hadoopcheck
3m 37s
The patch causes 16 errors with Hadoop v3.2.1.

-1 :x:
hadoopcheck
5m 29s
The patch causes 16 errors with Hadoop v3.3.0.

-1 :x:
spotbugs
0m 24s
hbase-server in the patch failed.

_ Other Tests _

-1 :x:
unit
0m 28s
hbase-server in the patch failed.

22m  5s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2957/2/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2957

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 876d9f5ec416 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / b2f85e5fd2

Default Java
AdoptOpenJDK-11.0.6+10

mvninstall
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2957/2/artifact/yetus-jdk11-hadoop3-check/output/patch-mvninstall-root.txt

compile
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2957/2/artifact/yetus-jdk11-hadoop3-check/output/patch-compile-hbase-server.txt

javac
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2957/2/artifact/yetus-jdk11-hadoop3-check/output/patch-compile-hbase-server.txt

shadedjars
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2957/2/artifact/yetus-jdk11-hadoop3-check/output/patch-shadedjars.txt

javadoc
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2957/2/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-server.txt

unit
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2957/2/artifact/yetus-jdk11-hadoop3-check/output/patch-unit-hbase-server.txt

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2957/2/testReport/

Max. process+thread count
101 (vs. ulimit of 30000)

modules
C: hbase-server U: hbase-server

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2957/2/console

versions
git=2.17.1 maven=3.6.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 28s
Docker mode activated.


_HOST to _URL in settings and reftag name refactor

addresses #55

Codecov Report

Merging #58 (9c70619) into prep-release (1228637) will not change coverage.
The diff coverage is 64.70%.

@@              Coverage Diff              @@
##           prep-release      #58   +/-   ##
=============================================
  Coverage         50.49%   50.49%
=============================================
  Files               107      107
  Lines              3418     3418
=============================================
  Hits               1726     1726
  Misses             1692     1692

Impacted Files
Coverage Δ

src/fullctl/django/rest/decorators.py
46.03% <0.00%> (ø)

src/fullctl/django/views/__init__.py
41.66% <0.00%> (ø)

src/fullctl/service_bridge/client.py
42.85% <ø> (ø)

src/fullctl/service_bridge/ixctl.py
0.00% <0.00%> (ø)

src/fullctl/service_bridge/pdbctl.py
0.00% <0.00%> (ø)

src/fullctl/service_bridge/peerctl.py
0.00% <0.00%> (ø)

src/fullctl/django/context_processors.py
100.00% <100.00%> (ø)

src/fullctl/django/settings/__init__.py
82.43% <100.00%> (ø)

src/fullctl/django/urls.py
73.33% <100.00%> (ø)

src/fullctl/service_bridge/aaactl.py
81.81% <100.00%> (ø)

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more

will be merged though #61


Namespacing issue (reported on community channel)

I don't know any details here, hopefully someone with more experience in this area are able to investigate this.
There's no simple reproduction case for this yet, but it do appear to be a regression from 1.2.1.
ref https://fusecommunity.slack.com/archives/C0BJ8V4TV/p1507527418000151

one more issue report here.. I'm creating a Class based on the <Alive.Page> and I get an error when the ux:Class is prefixed with the namespace that I've been using for other things in the app
build\Local\Designer\cache\ux13\SOS.PageNewAlert.g.uno(4.46): E3111: SOS.Alive does not contain type or namespace 'Page'. Could you be missing a package reference?
[7:37]
<Alive.Page ux:Class="SOS.PageNewAlert"> -> error
<Alive.Page ux:Class="PageNewAlert"> -> all good :thinking_face:
[7:38]
E3111: SOS.Alive does not contain type or namespace 'CarouselPage'. Could you be missing a package reference? this is also happening, but I'm not even trying to create a class from CarousselPage
duckers [7:39 AM]
Can you provide a simple repro?
igorls [7:40 AM]
Well I was trying to do that, but I wasn't able to make it fail

beewarloc [2:57 PM]
Is this a regression, ie. it worked on 1.2.1?
igorls [3:01 PM]
I have to check
...
I think you are right, the problem doesn't happen on 1.2.1

Possibly they have a class named SOS somewhere. You can't have a symbol used for both a class and namespace. That might explain why the one line works and the other not.

But wouldn't that also be a problem on 1.2.1?

I think you are right, the problem doesn't happen on 1.2.1

It might not be as the Uno compiler does tend to get more strict over time. It's just a possibility we'd like to eliminate before looking further (a reproduction would be required in any case).

It could be then that this is not a blocker, I'll leave it to the fuselibs team to investigate this further and remove the "Release blocker" label if it's not.

The problem here seems to be this generated code:
namespace SOS
{
    [Uno.Compiler.UxGenerated]
    public partial class PageNewAlert: Alive.Page
    {
        readonly Fuse.Navigation.Router router;
        [Uno.Compiler.UxGenerated]
        class Template1: Alive.CarouselPage
        {

...The problem is that the app contains an SOS.Alive-namespace, and symbol-resolution prefers these over matches closer to the root namespace. If we instead generated this
namespace SOS
{
    [Uno.Compiler.UxGenerated]
    public partial class PageNewAlert: global::Alive.Page
    {
        readonly Fuse.Navigation.Router router;
        [Uno.Compiler.UxGenerated]
        class Template1: global::Alive.CarouselPage
        {

... we should be good. That is, we're lacking global:: before the Alive-namespace.

Could using global:: everywhere be a solution to this problem? Or would that ruin the readability of the generated code?

@BeeWarloc: That would be a good fix, I think. I have the patch for that already.

But looking through the changes of the UX-compiler, it doesn't look to me like this is a regression.
And I'm unable to build the example with the previous release, due to it using newer features.

But, thinking about this a bit more, it might actually be a regression because some Uno namespace-resolving issues was fixed AFAIK. That bug could have previously masked this bug. If so, this is probably a release-blocker after all...

No, confirmed with the reporter that this actually didn't work in 1.2 with this setup. So I'm pretty sure it's not a regression.

Ok, then I agree we shouldn't try to fix it now. Even though the mentioned fix seems solid to me, it's a bit late in the release cycle to introduce something like that.

Yep, I completely agree.

Here's a minimal reproduction-case:
Foo.uno:
namespace Foo
{
	public class Bar
	{
	}
}

Bar.ux:
<Foo.Bar ux:Class="Bar.Foo.Baz" />

Bar.Foo.Baz.g.uno(4.35): E3111: Bar.Foo does not contain type or namespace 'Bar'. Did you perhaps misspell 'Baz'? Could you be missing a package reference?

This seems like the right fix:
diff --git a/Source/UX/Uno.UX.Markup.CodeGeneration/CodeGenerator.cs b/Source/UX/Uno.UX.Markup.CodeGeneration/CodeGenerator.cs
index 4c9d87a610..1213fa4b82 100644
--- a/Source/UX/Uno.UX.Markup.CodeGeneration/CodeGenerator.cs
+++ b/Source/UX/Uno.UX.Markup.CodeGeneration/CodeGenerator.cs
@@ -187,14 +187,14 @@ void BeginClass(Scope scope)
             {
                 var t = scope.DocumentScope as UXIL.ClassNode;
                 Emit("[Uno.Compiler.UxGenerated]");
-                Emit("public partial class " + t.GeneratedClassName.Surname + ": " + t.BaseType.FullName);
+                Emit("public partial class " + t.GeneratedClassName.Surname + ": global::" + t.BaseType.FullName);
                 PushScope();
             }
             else if (scope.DocumentScope is UXIL.TemplateNode)
             {
                 var t = scope.DocumentScope as UXIL.TemplateNode;
                 Emit("[Uno.Compiler.UxGenerated]");
-                Emit("public partial class " + t.GeneratedClassName.Surname + ": Uno.UX.Template");
+                Emit("public partial class " + t.GeneratedClassName.Surname + ": global::Uno.UX.Template");
                 PushScope();
                 EmitParentScopeClosureConstructor(scope);
             }

...but in general, we should probably have the UX compiler always use fully qualified types. Which would probably change some APIs.

Given how short and common names are in fuselibs I'm surprised this hasn't come up before. Definitely we should be using a global:: prefix on names we've already resolved.
I can't think of anything in fuselibs that would have a problem with this -- since they already work with actual types, thus nothing changes at runtime.

Just thought I'd point this out: I tried out the patch above, and it makes uno complain about global::object. So I guess we say that BaseType.FullName returns "object" in that case? That sounds a bit strange, as I'd expect it to return "Uno.Object" instead...

You probably need to resolve all fundamental types to just the name. float, int, object, etc. All others should get the global:: treatment.

Yeah, as long as 'float', 'int', 'object' etc is the real "full" typename. I thought the name was Uno.Float, Uno.Int, Uno.Object etc, and 'float', 'int', 'object' etc were keyword-aliases...

@kusma: You can use dt.QualifiedName, but you need to handle any generic type arguments
        static string GetGlobalName(this DataType dt)
        {
            var retval = "global::" + dt.QualifiedName;

            if (dt.GenericArguments.Length > 0)
            {
                var first = true;
                var sb = new StringBuilder(retval);
                sb.Append("<");

                foreach (var a in dt.GenericArguments)
                {
                    if (!first)
                        sb.Append(", ");

                    sb.Append(GetGlobalName(a));
                    first = false;
                }

                sb.Append(">");
                retval = sb.ToString();
            }

            return retval;
        }


Cert permission too open for postgres ssl requirement

What steps did you take and what happened:
When mounting key vault cert permission of file is 0644. Meaning anyone can read cert file. My specifc issue is postgres requires permission for cert files to be 0640 in order to use ssl connection .
What did you expect to happen:
I expected permission for cert to be more restrictive and not read everyone.
Anything else you would like to add:
If there is a way to change permission during mount it would resolve my issue.
Which access mode did you use to access the Azure Key Vault instance:
System Assigned Managed Identity]
Environment:

Secrets Store CSI Driver version: latest helm deployment
Azure Key Vault provider version: (use the image tag):
Kubernetes version: 1.19.3
Cluster type: AKS

File permissions are currently not configurable. The default permission is 0644 which is set and passed from the driver. Please feel free to comment on this issue: https://github.com/kubernetes-sigs/secrets-store-csi-driver/issues/346 and for tracking.

Closing this issue as the feature request is being tracked in the driver. The issue will contain a reference to this issue.


Can't move collision with SnapToGrid Mode

When the SnapToGrid is true
We can't grad any collision
When I hold the left click to move the collision when grid is not "SnapToGrid"
And I press H Key to set "SnapToGrid" keeping the left click
Result is I can move the collision ( with magnetic )

Seems this issue is fixed, open it again if you encounter the problem !


[DOC] Visualization types - Area chart

Signed-off-by: vagimeli<EMAIL_ADDRESS>Description
Create new doc page and content for area chart viz type
Issues Resolved
#1402
#2216
Checklist

[x] By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and subject to the Developers Certificate of Origin.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@ashwin-pc Please review the tutorial in its entirety. Confirm the changes align to your feedback to add an aggregation-based visualization. Also, please sync with me on how to properly embed the video. Thanks!

@Naarcha-AWS and @kolchfa-aws I added the GIF to this tutorial. Will you review and provide feedback? I'd like to add these quick hits to other viz types content and work out any kinks now before I get too deep into the other tutorials. Thanks!


Dragging and dropping event in such a way that chart "scrolls", the even is dropped at some other place

Checklist

[X] I've verified that I'm running react-big-scheduler-stch version 1.3.0

Describe the bug
Try dragging an event from one end of chart to another end in such a way that the chart would scroll
Seems it gets dropped to the point where 'it would be, had the chart not scrolled'
https://github.com/hbatalhaStch/react-big-scheduler/assets/44032634/f71d72ad-4134-4453-88b9-e01b8e0fa4f6
Reproduction Link/Code
This is present in examples directory's DragandDrop.js
https://github.com/hbatalhaStch/react-big-scheduler/blob/a10d26c06e2a70f52d8e66804b9098fb947bdfac/example/DragAndDrop.js
Steps to reproduce

Clone https://github.com/hbatalhaStch/react-big-scheduler.git
install deps and go to http://localhost:8080/example/#/draganddrop (or on port on which the project is running)

@shivamjjha brother, this problem is solved yet or not ?


requirements.txt is empty

requirements.txt is empty.

@c0mtruice currently there is no requirement for the reverse shell payload, it works with the default python installation, the other payloads are still in development and some dependencies are OS specific, when i find what works well, i'll create a proper way of installing dependencies depending on the payloads/OS you use.


add(): Accurate tick function

I think that the mod functions would be better named as "BeforeTick" and "AfterTick"

Should be fixed now

LGTM!


Unrecognized in Seo checker

I added some seo tags like described in the readme, but seo checker websites tell me, that there is no title tag for example.
I added the title tag like this:
meta.ogTitle(ogTitle: "my title");
How does this package handle the fact that the flutter environment needs some time to load and how does it handle dynamic content?
Cheers!

Thanks for your interest Tim, I am still working on SSR and the work not completed yet as mentioned before to make new out of the box solution, thanks again..

Now the support only for JS DOM not SSR...


Backend for general tasks

Why is this merge request being submitted?
Because a backend for general task is required.
What does this merge request add functionality-wise?
It adds backend functionality for generic tasks.
How has the code been tested?
[ ] Automated tests
[X] Manual tests (specify what you've done)
Tested whether json serialization works and generic tasks are created based on json input.
[x] New feature (never existed before)
[ ] Feature update (enhancing already existing feature)
[ ] Breaking feature (changes the already existing way of how the process works)
Co-Authored: @Somafet  @benedekdaniel

@TeaWithLucas Could you please have a look at this?


[5.5] isMine() on Model & mine() on Query to check and get result for authenticated user

I find myself doing lots of checks if current model belongs to a user in views and throughout the app.
$tweet = App\Tweet::find($id);
if( $tweet->user_id == auth()->id() ) {
   ...
}

It will be great if we could do it in very laravel way directly from Model
$tweet = App\Tweet::find($id);
if( $tweet->isMine() ) {
   ...
}

// or with a different foriegn key
if( $tweet->isMine('owner_id') ) {
   ...
}

And similarly, I can query all the records owned by current user
// get all tweets by authenticated user
App\Tweet::mine()->get()

// with a different foreign key
App\Tweet::mine('owner_id')->get()

This PR does just that, I think it will be useful for everyone.

@saqueib what about models with polymorphic relations? This wouldn't work for them.
I have a package with this functionality which includes polymorphic relations too: https://github.com/cybercog/laravel-ownership

I think this would work better as a Trait, not all models have a relationship with a user.

No plans to add this to core.

@jmarcher @taylorotwell alright I will keep using trait for this


"chat with us" link on voting page does not work

With the "Need more info?" box on https://ep2016.europython.eu/conference/voting/ there's a link "chat with us", containing this code:

habla_window.show(); habla_window.expand()

Clicking it causes this error however:

ReferenceError: habla_window is not defined

Seems to have been removed in bc759e7f97ddc6c7174970f49f9b9263f1e86f04 / 1179376a38bb0f41329ab42228dfc7589bca0e9c.

Thanks for reporting this - the chat with us functionality has been removed from the recent versions of the website, going to close this ticket.


Add materials for a template for the paper.

No content yet.

are you planning to add any content before merging? or is this GTG?

This is GTG, so we can all start working on it.
Let's coordinate via slack. If you want to start working on some particular section, just let the others know that you are working on that part.


Room and on Event in room

Hello, I'm trying to connect a NodeJS with Socket.io (Javascript) and SocketIoClientDotNet. I need to join SocketIoClientDotNet client in a room, but when i emit an event from socket.io javascript into the room, SocketIoClientDotNet client can't listen the event. I don't retrieve any kind of error.
This is the pastebin with the code: http://pastebin.com/X52X6KBu
Thx

Try something like this.
//-------------- App.js (Socket.io) ----------------- //
var room = io.of('/myroom');
room.on('connection', function(socket){
console.log('Client connected!');
socket.on('joinRoom', function(room){
    socket.join(room);
});

socket.on('nameEv', function(data){
    console.log('From .Net: ', data);
    io.in('nameRoom').emit('successEv', 'Ok');
});

});
//-------------- C# SocketIoClientDotNet ----------------- //
using Quobject.SocketIoClientDotNet.Client;
IO.Options optConnect = new IO.Options();
optConnect.Timeout = 3000;
//var socket = IO.Socket("http://hostname:3000", optConnect);
Manager manager = new Manager(new Uri("http://hostname:3000"), optConnect;
var socket = manager.Socket("/myroom");
socket.On(Socket.EVENT_CONNECT, (data) =>
{
socket.Emit("join", "nameRoom");
socket.Emit("nameEv", "Hello world!");
});
socket.On("successEv", (data) =>
{
MessageBox.Show(data.ToString());

stackoverflow.com is a far better place to ask this question.


Revised PoSE

PR types

PR changes

Description

Pose + Yarn Algorithm

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

PaddleNLP-CI 有报错看一下

license签署


eslint: properties starting with underscore are private

rules to check that properties starting with underscore are private
related to https://github.com/microsoft/vscode/pull/165117

Here's an updated eslint rule that forbids leading underscores on public and protected properties:
"@typescript-eslint/naming-convention": [
	"warn",
{
	"selector": "default",
	"modifiers": [
		"public"
	],
	"format": null,
	"filter": "^_\\w+Service",
	"leadingUnderscore": "forbid"
},
{
	"selector": "default",
	"modifiers": [
		"protected"
	],
	"format": null,
	"filter": "^_\\w+Service",
	"leadingUnderscore": "forbid"
}
],

This identifies 91 errors in our codebase

closing this - we have a different approach where we don't need this


Patch thrift package so it handles transport errors with a corresponding opertion's callback

Nodejs thrift package is build in a way that only errors returned in Thrift RPC response message will be passed to an operation's callback. All other errors, e.g. failed request, non-2xx HTTP response, etc. will be just emitted on connection object.
This PR adds a local patch for a thrift package which allows to pass HTTP errors to operation callback which later could be handled in .catch() handlers. It becomes possible to examine error object and find out why particular operation failed. It could be useful, for example, for re-trying particular request if it failed due to HTTP 5xx error, etc.

Codecov Report
Base: 93.77% // Head: 93.77% // No change to project coverage :thumbsup:

Coverage data is based on head (d670d86) compared to base (3df4326).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #99   +/-   ##
=======================================
  Coverage   93.77%   93.77%
=======================================
  Files          49       49
  Lines         707      707
  Branches      100      100
=======================================
  Hits          663      663
  Misses         20       20
  Partials       24       24

Impacted Files
Coverage Δ

lib/connection/connections/HttpConnection.ts
94.44% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

Thanks for releasing this. Makes my code a lot simpler.

Hi @fjakobs! Sadly, we've noticed some issues with this patch, but we're working on fixing it. More updates will be ASAP. Also, we're going to release library more often to faster deliver changes to users


use the demo code train a new dataset (got some problems )

I got some problems with AdaNet API,when I use the customizing_adanet.ipynb in the
adanet/adanet/examples/tutorials/  to train a new dataset, I got some error like this:
InvalidArgumentError: ValueError: generator yielded an element of shape (150, 150) where an element of shape () was expected.
Traceback (most recent call last):
File "D:\Program Files\Anaconda3-5.2\lib\site-packages\tensorflow\python\ops\script_ops.py", line 206, in call
ret = func(*args)
File "D:\Program Files\Anaconda3-5.2\lib\site-packages\tensorflow\python\data\ops\dataset_ops.py", line 454, in generator_py_func
"of shape %s was expected." % (ret_array.shape, expected_shape))
ValueError: generator yielded an element of shape (150, 150) where an element of shape () was expected.
[[{{node PyFunc}} = PyFuncTin=[DT_INT64], Tout=[DT_FLOAT, DT_INT32], token="pyfunc_184", _device="/device:CPU:0"]]
[[{{node IteratorGetNext}} = IteratorGetNextoutput_shapes=[[?,150,150,1], [?]], output_types=[DT_FLOAT, DT_INT32], _device="/job:localhost/replica:0/task:0/device:CPU:0"]]
 The old data is fashion_mnist, whose image is 28x28, my dataset is 150x150, I've tried lots of ways to adjust the parameters or change the demo code, but it still not works, that's so disappointing！How can I make it？I’d appreciate much if who can do me a favor ！

Do you have a colab you can share with some sample data?

here are the sample data，which has 8 classes，shape of 150x150，in 3 channels.I‘d appreciate much if you can do me a favor！

这个库是不是实验品？


chore(package): update semantic-release to version 15.4.1

:tada: This PR is included in version 1.0.6 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


rename button labels

Issue:

Looks great thank you!
@all-contributors please add @mohitshende for code and content


About the training set Di

Hello, I am reading this paper and very intrested in it. There is a point that I can not understand.
In Eq.2, the i-th test_entities get all entities in the Di. Then, Eq.3 remove all the sentences which labeled entities contained in the test_entities.
I think there only the sentences remained which labeled only 'O', if so, the model should have no ability to recognize the type entities. How could the model to disticnt the label mistake?
I am looking forward for your reply, thanks a lot.

Hi Jacky,
In Eq.2, the ej means the named entities (or surface names). For example, if I went to [Chicago]{LOC} is in the test fold, then the sentence I went to [New York]{LOC} in the training fold will NOT be removed. However, the sentence I played football in [Chicago]{LOC} will be removed since it contains the same entity.
Hope this answers your question.

So,the test_entities only contain the entities in the test set of the Di,is that right?
Is the test set in each fold sepreated from the train set or test set?

Yes, for each fold, the test_entities contains only the entities in that fold.
You can think the whole process as cross-validation. First, we separate the train set into k folds, we each fold, we treat it as a test fold and the other k - 1 folds as a training set. Then, we remove all the sentences in the training set that have an entity appearing in the test fold.

Thank you for your reply, I understand.


python3Packages.metar: disable failing test

Description of changes
Fix build (https://hydra.nixos.org/build/169519201)
Should fix failure of nws test of #165293.

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 165336 run on x86_64-linux 1

5 packages built:

home-assistant-component-tests.nws
python310Packages.metar
python310Packages.pynws
python39Packages.metar
python39Packages.pynws

Was already fixed.


Git clone URL in README references old organization name

Git clone should be updated to the current URL path of: https://github.com/TruSat/trusat-frontend.git

fixed with this PR - https://github.com/TruSat/trusat-frontend/pull/298


Consider dropping lein in favor of direct aws cli calls?

Hello folks ;)
Just putting there this idea in order for me to understand what it would take to have something that just calls the AWS command line tool directly without spinning a JVM (this maybe is the same as the other issue in cljs-lambda).
It would make startup time way faster and little or no change to the current plugin.
:peace_symbol: :wave:

@arichiardi When serverless-cljs-plugin is used, it doesn't make any AWS calls - serverless is responsible for doing that (if you use cljs-lambda to deploy, w/out serverless, then it'll make the API calls).
So if you want to avoid the JVM, the problem you'd want to solve is writing something executable which takes a project directory and compiles it into a zip file of compiled cljs code, with an index.js file containing an entry for each handler.  That would then be a drop-in replacement for the lein cljs-lambda invocation used inside this serverless plugin.
I personally am not motivated to do that, because for my use cases, JVM compilation makes a lot of sense.  I'm more than happy to answer questions you might have about what you'd need to do, if I'm able.

You are right, I see that this plugin basically calls the deploy of cljs-lambda. I have studied a bit in the meantime and I am going to work on something...if it is worth publishing you'll see a link here at some point.

I am wondering whether I should try to wrap this and compile with lumo. It would probably be ok for some libs, less ok for others, but eventually the GCC for JS will get feature parity I guess...

If you write a javascript module which takes the same inputs as the lein cljs-lambda build invocation in this project, and which creates an identical zip output file (compiled with lumo, or whatever), I can help you with the rest.

I have always had in the radar calvin-cljs. This might be the time when I can actually start using it ;)

I have just tried in a cljs-lambda project and it fails, both for core.async and because of the macros namespaces not compatible

Yeah - I think getting cljs-lambda, the runtime library, to compile with another tool is best considered a separate problem from using the serverless plugin to trigger a project build without involving the JVM.  You could have a project with no custom dependencies, and an xyz.core namespace like so:
(ns xyz.core)

(def ^:export handler [event ctx callback]
  (callback nil "Success"))

And that would work with lein-cljs-lambda, the plugin, if you associated xyz.core/handler with a lambda function. If I were focused on getting the process to work, I'd initially forget about the optional runtime library (which contains very little functionality), and try to concentrate on compilation and zip structure.

I am doing exactly that, with partial success. I also think that probably, unless you think otherwise, this would be considered a separate plugin. Or otherwise there is going to be a need of a :compilation-style key in the config somewhere.

The serverless bit could probably be the same plugin, i.e. if your 'compile my code' thing was an npm dependency of this project, we could use a command line switch to conditionally use it over the JVM.  Assuming that you don't want to launch a JVM, then yeah, the 'compile my code' thing would have to be totally separate, I would guess.

Yes calvin-cljs is on npm and the command I am trying is as simple as:
./node_modules/.bin/calvin build dev
That calls lumo after resolving all the deps from project.clj.

This was started in #6 and continues in branch wip/lumo. I guess I can close it now.


Migrate from backoff to backon

Motivation
backoff has been unmaintained for a while now, which is starting to cause rustsec warnings (#1635). backon is a maintained alternative.
Fixes #1635.
Solution
This PR migrates all uses of backoff to backon. This is a pretty breaking change for anyone who interacts with our backoff system beyond letting Controller use its default.
backon::Backoff doesn't have an equivalent to backoff::Backoff::reset, so this PR adds a new ResettableBackoff wrapper system for those use cases.

Hm, locally all tests pass except for test::pod_can_exec_and_write_to_stdin_from_node_proxy, since that assumes that it is executed from a machine with a running kubelet.

/cc @xuanwo

Hm, really not sure about what's still making tarpaulin unhappy.. :/

not sure about tarpaulin either. ci is has tarpaulin pinned to 0.28.0 (so should not be a new version thing), and it should otherwise run equivalently locally with just tarpaulin. last stuff was a test failure in crd_derive_schema so maybe that had a stray failure? re-running.

Might be related to this error in the middle of the compile log..
/home/n/Documents/kube-rs/target/debug/deps/kube_derive-81b5765bf8276125: error while loading shared libraries: libstd-ca74a2d9c5166d9f.so: cannot open shared object file: No such file or directory

That doesn't happen if I use the Rust 1.82.0 toolchain instead.

#1658 seems to have sorted out the CI issues at least.


Don't Fail On Non-Mappable Entities in Children

Objective
Fixes #6790
Solution

Don't fail when mapping entities that aren't found in the EntityMap.

I don't think this requires a changelog entry, but let me know if I'm wrong.
Changelog

This section is optional. If this was a trivial fix, or has no externally-visible impact, you can delete this section.

What changed as a result of this PR?
If applicable, organize changes under "Added", "Changed", or "Fixed" sub-headings
Stick to one or two sentences. If more detail is needed for a particular change, consider adding it to the "Solution" section

If you can't summarize the work, your change may be unreasonably large / unrelated. Consider splitting your PR to make it easier to review and merge!

Migration Guide

This section is optional. If there are no breaking changes, you can delete this section.

If this PR is a breaking change (relative to the last release of Bevy), describe how a user might need to migrate their code to support these changes
Simply adding new functionality is not a breaking change.
Fixing behavior that was definitely a bug, rather than a questionable design choice is not a breaking change.

Looks like we need another solution then.
I'll close this PR, so discussion can be continued in the issue, and we can open a new PR if we come up with a different solution.