Cannot found entity after some and/remove operation

Hi @enricostara , this is my test code
var d = Dominion.create();
var entity = d.createEntity(new A());
var s = d.createScheduler();
s.schedule(() -> {
    d.findEntitiesWith(A.class, C.class).stream().forEach(rs -> {
        try {
            System.out.println("AAAA");
            if (!rs.entity().has(B.class)) {
                rs.entity().add(new B());
            }
        } finally {
            rs.entity().removeType(C.class);
        }
    });
});
s.schedule(() -> {
    d.findEntitiesWith(A.class, B.class).stream().forEach(rs -> {
        System.out.println("BBBBBB");
    });
});
/// always handle the A.class
s.schedule(() -> {
    System.out.println("Before CCCC");
    d.findEntitiesWith(A.class).stream().forEach(rs -> {
        System.out.println("CCCCCCCCCCCC");
    });
});
s.tickAtFixedRate(1);
TimeUnit.SECONDS.sleep(2);
entity.add(new C());

I have three component （A,B,C）and three system, always have a system to handle A.class. In the initial situation, the system operation is normal，but when I add C.class and add B.class then remove C.class, the system is not working
My version is 0.9.0-SNAPSHOT, you can run my test code and see the output.

I debugged the source code and found the problem.
/// dev.dominion.ecs.engine.ResultSet.IteratorWrapper
private static final class IteratorWrapper<T> implements Iterator<T> {
        private final ResultSet<T> owner;
        private final Iterator<CompositionRepository.Node> nodesIterator;
        private Iterator<T> wrapped;

        public IteratorWrapper(ResultSet<T> owner, Iterator<CompositionRepository.Node> nodesIterator) {
            this.owner = owner;
            this.nodesIterator = nodesIterator;
            this.wrapped = this.nodesIterator.hasNext() ?
                    owner.compositionIterator(this.nodesIterator.next().getComposition()) :
                    new Iterator<>() {
                        @Override
                        public boolean hasNext() {
                            return false;
                        }

                        @Override
                        public T next() {
                            return null;
                        }
                    };
        }

        @Override
        public boolean hasNext() {
            return wrapped.hasNext()
                    || (nodesIterator.hasNext() && (wrapped = owner.compositionIterator(nodesIterator.next().getComposition())).hasNext());
        }

        @Override
        public T next() {
            return wrapped.next();
        }
    }

The problem in hasNext() method, the nodesIterator has 4 node, and the entity in the last node Node={types=[A,B]}
{IndexKey@1539} "|1:null|" -> {CompositionRepository$Node@1540} "Node={types=[A]}"
{IndexKey@1541} "|30817:[1, 2, 3]|" -> {CompositionRepository$Node@1542} "Node={types=[A,B,C]}"
{IndexKey@1557} "|994:[1, 2]|" -> {CompositionRepository$Node@1558} "Node={types=[A,C]}"
{IndexKey@1559} "|995:[1, 3]|" -> {CompositionRepository$Node@1560} "Node={types=[A,B]}"

But the hasNext() method only view the first two nodes and return false

I debugged the source code and found the problem.
/// dev.dominion.ecs.engine.ResultSet.IteratorWrapper
private static final class IteratorWrapper<T> implements Iterator<T> {
        private final ResultSet<T> owner;
        private final Iterator<CompositionRepository.Node> nodesIterator;
        private Iterator<T> wrapped;

        public IteratorWrapper(ResultSet<T> owner, Iterator<CompositionRepository.Node> nodesIterator) {
            this.owner = owner;
            this.nodesIterator = nodesIterator;
            this.wrapped = this.nodesIterator.hasNext() ?
                    owner.compositionIterator(this.nodesIterator.next().getComposition()) :
                    new Iterator<>() {
                        @Override
                        public boolean hasNext() {
                            return false;
                        }

                        @Override
                        public T next() {
                            return null;
                        }
                    };
        }

        @Override
        public boolean hasNext() {
            return wrapped.hasNext()
                    || (nodesIterator.hasNext() && (wrapped = owner.compositionIterator(nodesIterator.next().getComposition())).hasNext());
        }

        @Override
        public T next() {
            return wrapped.next();
        }
    }

The problem in hasNext() method, the nodesIterator has 4 node, and the entity in the last node Node={types=[A,B]}
{IndexKey@1539} "|1:null|" -> {CompositionRepository$Node@1540} "Node={types=[A]}"
{IndexKey@1541} "|30817:[1, 2, 3]|" -> {CompositionRepository$Node@1542} "Node={types=[A,B,C]}"
{IndexKey@1557} "|994:[1, 2]|" -> {CompositionRepository$Node@1558} "Node={types=[A,C]}"
{IndexKey@1559} "|995:[1, 3]|" -> {CompositionRepository$Node@1560} "Node={types=[A,B]}"

But the hasNext() method only view the first two nodes and return false

I try to fix this issue, and test my code, it seems to work.
        @Override
        public boolean hasNext() {
            if (wrapped.hasNext()) {
                return true;
            }

            while (nodesIterator.hasNext()) {
                if ((wrapped = owner.compositionIterator(nodesIterator.next().getComposition())).hasNext()) {
                    return true;
                }
            }

            return false;
        }

Hi @endison1986 !
Thanks so much for testing and debugging! Let me check all your findings, I'll give you an update very soon.

Hi @endison1986 ,
I really appreciate your effort and it would be great if you started as a project contributor.
First step, maybe take it to the next level by trying to write a specific unit test to highlight the problem you discovered.
Even if you're working on multi-threaded examples, you might want to try distilling the issue to see if it's really about concurrency.
This is because, as a general rule, unit tests should be as single-threaded as possible - although there are some situations where you can't help it.
For example, this is the unit test I'm about to add into the suite starting from your multi-threaded example (and without any patch the last assert fails as expected):
    void findEntitiesAddingAndRemovingComponents() {
        EntityRepository entityRepository = (EntityRepository) new EntityRepository.Factory().create("test");

        var entity = entityRepository.createEntity(new C1(0));
        var iterator = entityRepository.findEntitiesWith(C1.class).iterator();
        Assertions.assertTrue(iterator.hasNext());

        entity.add(new C2(0));
        iterator = entityRepository.findEntitiesWith(C1.class).iterator();
        Assertions.assertTrue(iterator.hasNext());

        entity.add(new C3(0));
        iterator = entityRepository.findEntitiesWith(C1.class).iterator();
        Assertions.assertTrue(iterator.hasNext());

        entity.removeType(C3.class);
        iterator = entityRepository.findEntitiesWith(C1.class).iterator();
        Assertions.assertTrue(iterator.hasNext());
    }

I'm not using the scheduler as the problem you discovered is not with concurrency but is a plain bug.
Now, if you apply your own patch, it works as expected.
So you could just create a pull request from your fork and submit your commit with a unit test like this and the patch you created.
After my review your code will (hopefully) be merged and you will be in the list of committers 👍

Hi, @enricostara
Thank you for your trust and help, this is the first time I create a PR on github, so I'm not sure if the creation was successful. I forked the project, created unit tests and modified the code, then pushed it to my private project, and then created a PR. I don’t know if my steps are correct. If there is something wrong, please forgive me.

Fixed by #139


Bug syntax error

It was working in php 7.
When tried to impliemnt this in php 5.6 I got an error "syntax error, unexpected 'function' (T_FUNCTION), expecting identifier (T_STRING) or \ (T_NS_SEPARATOR) in vendor/zoonman/linkedin-api-php-client/src/Client.php on line 22"
line number 22 is this "use function GuzzleHttp\Psr7\build_query"

Duplicate of #22

This not a bug, please, upgrade to PHP v5.6. You are using deprecated PHP version.


enable multiple queues

allow the command to inspect multiple queues, instead of running the check multiple times

@InformatiQ Can you take a look at merging this by hand please.  Most likely I would try a rebase and then see where that gets you.  If you need help feel free to ask.
Thanks!

should be ready now + added a small fix


Private network

Broken Link
https://docs.substrate.io/tutorials/v3/private-network
Expected Location
Looking for documentation/ tutorial on building a small private network with substrate.
Context and Origin
I know I've come across this link in a few places, clicking around like a madman searching for about anything on the subject. The two I could find from recent memory (will add as I find any others)...

The Node template README.
Google/ Brave Search for a query in the neighborhood of "build a private chain substrate"... so, out of your control

I want to say that I remember finding the same link at some point in the actual documentation itself... maybe that's been caught already, or I'm just misremembering things.

https://docs.substrate.io/tutorials/get-started/trusted-network/


Riker workspace

Automatic nickname update when the user has changed their default nickname

Fix for "Need an 'update' option #7"


discoverd: client keep headers on redirect

Closes #1880

Currently Authorization header is copied. Spec is not clear about this. curl does not pass that header unless explicitly set:

When authentication is used, curl only sends its credentials to the initial host. If a redirect takes curl to a different host, it won't be able to intercept the user+password. See also --location-trusted on how to change this.
--location-trusted
(HTTP/HTTPS) Like -L, --location, but will allow sending the name + password to all hosts that the site may redirect to. This may or may not introduce a security breach if the site redirects you to a site to which you'll send your authentication info (which  is  plain-text in the case of HTTP Basic authentication).

LGTM, thanks!


[WorkAround Available] Serious Console Stop Error!!

Assets/Plugins/RealtimeCSG/Editor/Scripts/Managers/MeshInstanceManager.cs(27,27): error CS0104: SceneUtility' is an ambiguous reference between RealtimeCSG.SceneUtility' and `UnityEngine.SceneManagement.SceneUtility'
Assets/Plugins/RealtimeCSG/Editor/Scripts/Managers/MeshInstanceManager.cs(584,31): error CS0104: SceneUtility' is an ambiguous reference between RealtimeCSG.SceneUtility' and `UnityEngine.SceneManagement.SceneUtility'
Hello... this comes up in version 1.312 , 1.314
Oh, I'm trying this on Unity 5.5b11

WorkAround Available? k and.....

No I'm going to fix it, I just meant that until I have the fix for you, you can do what I described before

Where exactly did you describe before? I didn't see any info...

Oh, seems like my original comment disappeared .. :(
So the workaround is to simply rename all occurrences SceneUtility in realtime CSG with RealtimeCSG.SceneUtility ..

Oh ok.. lol I see now... Ya I was looking everywhere but thanks, I'll try that.. So, is it just this "MeshInstanceManager.cs" script I need to edit?

It's possible that you might need to do this in a couple of other files, but I think editing MeshInstanceManager.cs should be enough

K, I just had to edit 5 lines in the "MeshInstanceManager.cs" script.. Magic! everything is perfect! Thanks for the quick Fix.. :)

np!

This is fixed in version 1.315 which is available on the update site ( http://prenominal.nl/updates/index.php )!
I will close this ticket when it's available on the asset store

That was quick! :) Thanks for the Awesome support..

You're welcome :) This version is now available on the asset store, so closing ticket


Tests for a delb plugin implementation

as we discussed a few months back, here's a proposal how the api of a delb Document extension might look like.
i'm already puzzled about that prefix (usually exist) that a database instance would often use to be adressed. technically it part of the url, but one cannot distinguish what parts of the url are that prefix and the collection path. would there be a reliable way to probe that?
so i left that prefix out of the url scheme deliberately. though it should probably be contained.
be reminded that i'm absolutely naive here.

Great work.
Thanks for also taking the time to clean up the test fixtures.

erm, i'm not sure whether this all make sense. as noted regarding the path prefix of an instance.

proposal: could you re-merge this commit into the master branch: 59fd3a1bace062394789ece59a794995c53f7c32
i'd then open a new pr that solely displays the design relevant test module and move discussion there.

it's done

continued in #18


UAA 2.4.1

Hi there!
We use Pivotal Tracker to provide visibility into what our team is working on. A story for this issue has been automatically created.
The current status is as follows:

[ ] #99824310 UAA 2.4.1

This comment, as well as the labels on the issue, will be automatically updated as the status in Tracker changes.

This change was commited directly in this commit


MSFT_xExchWaitForADPrep is failing basic schema validation tests with Test-xDscResource

Test-BasicDscFunction : In function Test-TargetResource, the type System.Object of parameter VerbosePreference is not supported.
Test-SetTestIdentical : Set-TargetResource and Test-TargetResource must take identical parameters. Set-TargetResource is missing parameter VerbosePreference from
Test-TargetResource.
Test-SetTestIdentical : Set-TargetResource and Test-TargetResource should take identical parameters.

@Dan1el42 This was discussed early on in the development of the resource, and it was determined that it is not actually an issue in this case even though Test-xDscResource complains about it. -VerbosePreference is currently used in two calls to Test-TargetResource:
$testResults = Test-TargetResource @PSBoundParameters -VerbosePreference SilentlyContinue

Reopening, per: https://github.com/PowerShell/xExchange/pull/27


Consider diogenes in relation to Drain

https://github.com/dssg/drain
It might be worth pulling in code, writing some docstrings, and incorporating into diogenes.

In particular, drain's precision_at_k (https://github.com/dssg/drain/blob/master/metrics.py) is probably better than ours.


CLA assistant

closes #1133
Depends on #1188

Travis automatic deployment:
https://pr1187--safereact.review.gnosisdev.com/app

Travis automatic deployment:
https://pr1187--safereact.review.gnosisdev.com/app

Travis automatic deployment:
https://pr1187--safereact.review.gnosisdev.com/app

Travis automatic deployment:
https://pr1187--safereact.review.gnosisdev.com/app

Travis automatic deployment:
https://pr1187--safereact.review.gnosisdev.com/app

Travis automatic deployment:
https://pr1187--safereact.review.gnosisdev.com/app

should we maybe create a repo where we test this first?

I did it https://github.com/matextrem/safe-electron-multisig/pull/4 and it seems to be working fine.

Cool, it fails here though

Travis automatic deployment:
https://pr1187--safereact.review.gnosisdev.com/app

Travis automatic deployment:
https://pr1187--safereact.review.gnosisdev.com/app

Travis automatic deployment:
https://pr1187--safereact.review.gnosisdev.com/app

Travis automatic deployment:
https://pr1187--safereact.review.gnosisdev.com/app

Travis automatic deployment:
https://pr1187--safereact.review.gnosisdev.com/app

@matextrem could you please link your email used for first two commits to your github account?

Done!

recheckcla

doesn't seem to work 🤔

recheckcla

It passed successfully now

yes, because I re-ran it. Have you tested actual CLA signing functionality?

No. I've tested it recently in my repo and it does not work either.

are you going to debug/research the problem or you need help?

I'm going to investigate it and let you know


Mixed Paint Bucket - Add a QCFPunch keyword for Pallete Pick

The keyword did not work. I need to make sure that it does.

Ok, non-breaking space, thanks Gk, this solves it.


Feature request: Give priority to .plugin.zsh files when sourcing for OMZ compatibility

Some OMZ plugins have multiple files ending in .zsh, and Znap currently just uses the first if a specific one isn't given. The OMZ framework uses the .plugin.zsh extension to indicate which file actually needs to be sourced to run the plugin, for instance in their bundled copy of history-substring-search.
When automatically finding a file to source, would Znap be able to prioritise .plugin.zsh files over plain .zsh? This would improve compatibility with OMZ plugins, and as far as I can tell wouldn't break the existing behaviour with other frameworks like Prezto.

Done.

Done.


Translate Part 1 of the Lessons into French

What is needed?
Essentially, I am looking for a native French speaker to translate Part 1 of the Lessons into French. As I am trying to reach more people you may be asked to become a collaborator on this project so that you can handle any issues in French. This is more than just a one off translation job.

I want to complete this task.

My native language is Chinese，I want to help join this project.Do you need a translation of ChineseDo you need a translation of Chinese?

@wuyu-wy I do want to have Chinese as a translation but I haven't yet added it to my timeline. Just give me a bit and I will create Chinese as part of the overall project. May I ask is this going to be Cantonese or Mandarin translation? I know the characters cross over between dialects but some words are used and others aren't. At least to my understanding.

Mandarin translation

@wuyu-wy Okay, essentially I need to know if this is going to be in Simplified Chinese or Traditional Chinese so that I can create issues on the timeline. Please checkout the translation guidelines here: https://github.com/rcallaby/Learn-Git/blob/main/translation.md

zh-CN: Simplified Chinese

@wuyu-wy Okay, I started to add zh-CN to the timeline. You can find the first issue here: https://github.com/rcallaby/Learn-Git/issues/193

I have noticed ，and I will try my best to do it well. THANKS


Linking to a Catalog page part

Currently, because we use hash history this isn't possible. We could switch to pushState-style routing but that would require a server which supports that.

Difficult from a technical standpoint but essential from a users' perspective :)
This has been a very real problem in several projects, where we wanted to link from one section to another in order to guide the user. In larger projects there are tons of components, so we need to provide a way to make them accessible by linking stuff.
Bonus points for checking whether the links actually point to a valid, exisiting place or whether they go into the void … Dead links, the other problem encountered in documentation.
 Let's brainstorm a better way.

Am 27.10.2015 um 10:41 schrieb Jeremy Stucki<EMAIL_ADDRESS>Currently, because we use hash history this isn't possible. We could switch to pushState-style routing but that would require a server which supports that.
—
Reply to this email directly or view it on GitHub https://github.com/interactivethings/catalog/issues/28.

I'd recommend to use a query string parameter – which react router already supports and parses.
Even if we later were to switch to push state routing this would continue to work and also be sent to the server where potential redirects of old / dead links could happen.

I prefer using a quasi-standard solution like the query string to inventing our own syntax here. Although I think it's really stupid that we can't just write [my lovely buttons](/components#buttons)
This would all not be a problem if catalog produced a static site as output :trollface:

Another point: we should turn internal links into <Link>s but not external ones.

When Catalog is integrated in a React app, it's up to the app to decide which routing strategy (browser or hash history) it uses. When using browser history, regular hashes can be used to jump to page parts. The only thing we'd need for that is to generate IDs on headings.
I'm closing this issue because I don't want to build some hacky solution for this which covers every possible use case. If a real need arises, feel free to reopen again.


docs.rs should ignore .cargo/config

Fixing this should be basically the same steps as https://github.com/rust-lang/docs.rs/issues/555#issuecomment-571950211, rustwide should remove .cargo/config before starting the build.
Originally posted by @jyn514 in https://github.com/rust-lang/docs.rs/issues/647#issuecomment-602042380

i'll try working on it

This won't be fixed until we bump the version of rustwide.

I'm maintaining a crate whose docs.rs builds fail because of this issue. Do you plan to bump rustwide soon or should I try work around it?

#758 will have a rustwide bump once the async changes are released, though that may take some time, so a small PR bumping to 0.7.0 to get this fix out seems useful.

I'll make a PR updating it.

Thanks a lot!

That was quick, thank you! Is there a way to rerun a failed docs.rs build or do I need to push a new version?

I can rerun the build for you. What crate and version?

I guessed that it was bootloader 0.9.3, it just rebuilt successfully :) https://docs.rs/crate/bootloader/0.9.3

Yes, it was. Thank you so much!


Update Event Emitter

background the move to stay in line with react-native 0.30 was premature and broke implementation for people stuck on pre 0.28. Instead we will wait until the old event emitter usage is fully deprecated before making the switch.
Leaving this PR open as a reminder and to track progress.

we don't need to merge this in for people upgrading?

Let me know if you need me to help with anything

We do not need this yet, until react-native officially deprecates the old method. In this case I think I jumped the gun implementing this (and publishing v0.4) as it is not backwards compatible with react-native <0.28. I published v0.5 today which reverts back to the old method, and opened this PR so when the official deprecation comes we can easily switch over.

note: there was one backwards compatible change to the header imports required for rn 0.30 which is included in the v0.5 release.

I just did this (#152). Closing this PR.


Suggestion : Resolve image url

When a message contains a link to an image, it should be displayed in the embed when starred.
--> Suggestion by Dev-CasperTheGhost
https://github.com/SimonLeclere/discord-starboards/issues/3#issuecomment-753304562

Added in the develop branch

Added in the develop branch


oncomplete not called when set with option function

I'm attempting to set the oncomplete method using the new option function, but something seems to be going wrong.
<!DOCTYPE html>
<html>
<head>
  <title>Testing</title>

  <script type="text/javascript" src="jquery-1.11.2.js"></script>
  <script type="text/javascript" src="inputmask.js"></script>
  <script type="text/javascript" src="jquery.inputmask.js"></script>

  <script type="text/javascript">
    $(document).ready(function() {
      $("#my-val").inputmask("999-99-9999", {
        oncomplete: function() {
          console.log("howdy!");
        }
      });

      $('#my-val').inputmask('option', {
        oncomplete: function() {
          console.log("hello!");
        }
      });
    });
  </script>
</head>
<body>
  <input type="text" id="my-val" />
  <input type="text" />
</body>
</html>

calling $('#my-val').inputmask('option', 'oncomplete') shows that the function has indeed been updated to reflect the new "hello!" message, but when I actually complete the mask, it still logs the original "howdy!" message.

By the way, it seems that this is true for other options besides oncomplete.
For example:
$('#my-val').inputmask('option', {
  mask: '999'
});

seems also to not actually change the mask, but when you ask for the mask value using the option function, it gives you "999".

@RobinHerbots I tried to follow the documentation you added for the option function, but am I doing it wrong? Also, if there are any options that you know for a fact work with this function, let me know and I can try my hand at a fix for this.

@itslittlejohn ,
Fixed,

Thank you! I will test out the new version.


Bluetooth pairing

Signed-off-by: Jorma Virkkunen<EMAIL_ADDRESS>

I have no more changes for this in my mind.

Document looks good to me, however we have now ran out of the numbers on the nav order, the number 14 is already in use and numbers around it as well, so those needs to be adjusted

It's even worse, we have accidentally already used 14 twice, for both "Backup Extraction" and "Battery Lifetime". @jovirkku could you make some room here? Preferably in a separate commit.

Android App Support: 10
Backup Extraction: 14 (NOTE)
Backup and Restore: 13  (NOTE)
Battery Lifetime: 14
Bluetooth Pairing: 14
Collecting logs with Logcat: 15
It has been "broken" already before my commit. Fixing the indexes requires touching 10-20 documents. But it is doable, of course.

It has been "broken" already before my commit. Fixing the indexes requires touching 10-20 documents. But it is doable, of course.

That is well understood. Still, it would be easiest to just fix it here instead of opening a new task for it. But for the sake of clarity it's still best to make those changes in a separate commit.

It has been "broken" already before my commit. Fixing the indexes requires touching 10-20 documents. But it is doable, of course.

That is well understood. Still, it would be easiest to just fix it here instead of opening a new task for it. But for the sake of clarity it's still best to make those changes in a separate commit.

https://bz.jollamobile.com/show_bug.cgi?id=59444

https://bz.jollamobile.com/show_bug.cgi?id=59444

Ok, let's finish that one first and then rebase this PR on top of that, if that's ok with you?

https://bz.jollamobile.com/show_bug.cgi?id=59444

Ok, let's finish that one first and then rebase this PR on top of that, if that's ok with you?

Yes, ok.

Nav_order fixed.


Preview not updating on Safari

The preview is not updating using Chrome or Safari on iOS. Seems ok on Android. Changing tab in the browser and back again appears to update the altered CSS a bit but not correctly. My guess is that iOS does not like the on-the-fly changing of style elements. Needs investigation.

Ok, so it looks like it doesn't update on desktop Safari either.

Fixed. Added a random number (cachebuster-esque) to animation name. This forces Safari to know the CSS has been changed and to reflect this on the preview. Not the most elegant solution but also prevents any clashes if someone names the custom animation the same as the playing example above. Might remove the 'v' as this suggests a sequential version number.


Zotero: Ref's collection changes dont update modified

This causes refs with changed collections still have them in notion (not updated where must)

Should probably use sync api endpoints instead?
https://www.zotero.org/support/dev/web_api/v3/syncing#get_updated_group_metadata
Which allows for incremental sync.

Added zotero versions to the sync. Should be fixed.
TODO for later: save the current version to allow bidirectional sync and incremental sync


"rollup": "^3.9.1" error

have an error when upgraded the roll up
``[plugin:vite:import-analysis] Failed to resolve import "rollup/dist/es/rollup.browser.js" from "src\lib\workers\bundler\index.js?type=module&worker_file". Does the file exist?
C:/Users/Administrator/Downloads/sites-master/packages/repl/src/lib/workers/bundler/index.js:2:26
1  |  import '/@vite/env'
2  |  import * as rollup from 'rollup/dist/es/rollup.browser.js';
   |                           ^
3  |  // import * as rollup from 'rollup/dist/es/rollup';
4  |  // import { rollup } from 'rollup/dist/rollup'

Upgraded Rollup where? This isn't nearly enough info as to what exactly you did to cause this error

Thanks for the great package. ok, seems this one works "@rollup/browser": "^3.9.1",


Error invalid syntax providerName=docker

Hello,
I have a problem. I have Traefik running in my HomeLab on a Docker Swarm cluster. Traefik of course uses the Docker provider for this.
For this I then did the configuration as described for traefik-kop. Redis with on the Docker cluster.
The container mut the docker-kop runs on my Synology NAS. Now when I start another container with NGINX and traefik label on the Synology NAS, I get the following error message.
Any idea what can be wrong? You can't really do much wrong with the syntax.
time="2022-04-30T22:52:32Z" level=info msg="Starting provider aggregator.ProviderAggregator {}"
time="2022-04-30T22:52:32Z" level=info msg="Starting provider *docker.Provider {\"watch\":true,\"endpoint\":\"unix:///var/run/docker.sock\",\"swarmModeRefreshSeconds\":\"15s\"}"
time="2022-04-30T22:52:32Z" level=error msg="Skip container nginx-traefik-central: strconv.ParseBool: parsing \"true\\\"\": invalid syntax" providerName=docker
time="2022-04-30T22:52:32Z" level=info msg="refreshing configuration"
time="2022-04-30T22:54:54Z" level=info msg="Skipping same configuration" providerName=docker
time="2022-04-30T22:56:55Z" level=error msg="Skip container nginx01-traefik-central: strconv.ParseBool: parsing \"true\\\"\": invalid syntax" providerName=docker
time="2022-04-30T22:56:55Z" level=info msg="Skipping same configuration" providerName=docker
time="2022-04-30T23:03:15Z" level=error msg="Skip container nginx01-traefik-central: strconv.ParseBool: parsing \"true\\\"\": invalid syntax" providerName=docker
time="2022-04-30T23:03:19Z" level=info msg="Skipping same configuration" providerName=docker
time="2022-04-30T23:04:31Z" level=info msg="Skipping same configuration" providerName=docker
time="2022-04-30T23:05:18Z" level=error msg="Skip container nginx01-test: strconv.ParseBool: parsing \"true\\\"\": invalid syntax" providerName=docker
time="2022-04-30T23:05:18Z" level=info msg="Skipping same configuration" providerName=docker

Thank you
best regards

@strausmann not clear what's going on here, as the error appears to be coming from the traefik parsing code itself, not my code. Can you post the config for your nginx container and also for running traefik kop itself?

@strausmann looking at this again, I'm guessing you may have had an errant quote in your docker label, something like this:
    labels:
      - traefik.enable=true"

That could lead to the above error. You need to remove that " or or add another at the start so it looks like:
    labels:
      - "traefik.enable=true"

In any case, I'm closing this for now as it does not appear related to traefik-kop, however feel free to reopen if you are still having is sues.


Update to latest image, add OWNERS as well as add new owner to team, …

…fix README, update Helm Charts root readme with incorrect text.

What this PR does / why we need it:

Adds an OWNERS file to relevant owners who can review and approve PRs for this chart.
Adds new owner (cc @bendrucker ) who is authorized to help own this chart
Updates imageTag to latest version (2.1.0)
Updates to Chart README wording
Fix minor typo in main helm charts repo README
Add hook delete policy to prevent potential chart upgrade issues

Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

N/A

Special notes for your reviewer:
Please let me know next steps on the OWNERS file set up so we have permission to maintain the chart going forward and if you need anything else. (cc @darend @flah00 FYI)
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md

/assign @unguiculus

/ok-to-test

/lgtm


fix: upgrade to the latest @google-cloud/common

@DominicKramer I'm kinda scared about these common upgrades.  Is this running the system tests if I push the branch to upstream?

@googleapis/node-team I'm not sure who owns this one these days, but this is ready for a close look. Depends on https://github.com/googleapis/nodejs-common/pull/145 landing.


Leverage Hash#merge

Only call update_attributes once

Is there some metastuff in automate that calls this? I wondered why this method even needs to exist and can't find any direct callers.

@chrisarcand There are three callers in this file.

Sorry, should have said 'continue to exist as public API' 😄

@chrisarcand good point 👍 I made the method private

Gaprindashvili backport details:
$ git log -1
commit 70aff84e0d75bba5bf9ab79e7ef6e92ce00dbb4d
Author: Greg McCullough<EMAIL_ADDRESS>Date:   Sat Nov 11 08:36:41 2017 -0500

    Merge pull request #16424 from bdunne/refactor_update_progress

    Leverage Hash#merge
    (cherry picked from commit 9f622d71a6b17faf910125a44310c1873bf7ae12)


avoid crash at the init of the module.

hi,
My modifications avoid the crash of the module if the user does not have the sensor on his phone.

#8

#8 throw new RuntimeException("No Gyroscope found")

@Lleios This looks pretty good, except for the Runtime exception. As it improves the situation I will merge it, would you mind doing a follow-up PR including the RCTMakeError  thing? It is described here, just search for the term 👍


Get comments sorted by anything other than new

Trying to get comments on a subreddit sorted in any way other than by new, but I cannot see any way to do this.
Is it possible?

Seems the reddit api doesn't provide sorting on the comments endpoint for subreddits at all

Awesome! Thanks!


[11.x] Adds Enums folder to make:enum command

https://github.com/laravel/framework/pull/50394
In our previous PR, we didn't include the option to create enums in the Enums folder or App folder. However, we have now added this feature! If someone would like to create an enum file in the Enums folder, they just need to create a folder named Enums :)
Like models

@driesvints
I think we need to re-run the tests.
Also, I can't access to the Styleci!!

@milwad-dev seems tests still fail

@milwad-dev Would be nice if this were configurable. I use Enumerations as my directory/namespace name, for example.

"We cannot do that because if we do it for one command, we will have to do it for all commands such as models

Added Enumerations support @martinbean

I was expecting this command to default to the 'Enums' folder, regardless of whether it exists or not... Sad.


Create netLabel when the trace component has the to prefix as net

Not sure if i understand the question completely but if the user specifies a net label we'll draw a net label on the schematic and NOT a schematic trace.


V1 shuheng fix

Fix #364 and #244

@isc-shuliu note, going forward, it's better to have one PR per fix. No need to detangle this one though.

Note - the CI fail was due to an apparent blip in containers.intersystems.com availability


Expensify.Cash - Unable to add multiple emails to workspace separated by comma

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Login to expensify.cash using an account under freePlan beta
Create a workspace via Global create (i.e. the green + icon)
Go to Settings and access the Workspace
Go to People tab
Select "Invite"
Attempt to invite multiple valid email addresses and separate them by comma

Note: you will need to be a part of the freePlan beta to test this issue. if you are hired, please let us know your test email/s and we can add you!
Expected Result:
Multiple users should be added to this workspace (i.e. emails should be able to be separated by commas).
Actual Result:
"Invalid Email" error occurs:

Workaround:
N/A
Platform:
Where is this issue occurring?
Web ✔
iOS✔
Android✔
Desktop App✔
Mobile Web✔
Version Number: 1.0.77-2
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:
View all open jobs on Upwork

Posted to Upworks: https://www.upwork.com/jobs/~0185dff64f02b86eaf

Triggered auto assignment to @marcaaron (Exported), see https://stackoverflow.com/c/expensify/questions/7972 for more details.

I have a suggestion to improve the input. I think this input for entering emails should expand based on the number of emails.

Proposal

We have to update inviteUser method https://github.com/Expensify/Expensify.cash/blob/f1ea424068fea065809c95f8a32ff2e08d7d52dc/src/pages/workspace/WorkspaceInvitePage.js#L74.
We split the emailorPhone state property via , and then validate each email or phone input as we are currently doing.
We will update the state variable name to be more relavant.
We will highlight the email which is wrong in the Error Growl.
We have to update the invite method https://github.com/Expensify/Expensify.cash/blob/f1ea424068fea065809c95f8a32ff2e08d7d52dc/src/libs/actions/Policy.js#L142.
So that it takes an array of login instead of a single user.
we already support multiple employees in https://github.com/Expensify/Expensify.cash/blob/f1ea424068fea065809c95f8a32ff2e08d7d52dc/src/libs/actions/Policy.js#L154.

This will fix the issue at hand.
Suggestions

We should highlight the User emails in the input for clarity for example
<EMAIL_ADDRESS><EMAIL_ADDRESS>We should increase the height of the input so that it is easier to see all the entered emails and wrap emails in next line.

@parasharrajat, your proposal sounds right for this. I think you can go ahead and work on it!
3. We will highlight the email which is wrong in the Error Growl. - not strictly necessary, but would be a very helpful feature - I like it.
For the first suggestion, what do you  mean by We should highlight the User emails in the input for clarity. Do you mean to literally just bolden the emails?

Yeah, I meant bolden the emails as we currently don't have Email Input fields where each email is shown with a close button to interact separately instead of using backspace to remove it.

I found the following issues while working on this.

If we invite and phone number. It is not added to the Assignee list until we refresh the page.
Str.isValidPhone is returning true for value 98?

Thanks for the investigation @parasharrajat - I'll go ahead and hire you for this job.

Hey, @TomatoToaster Please check https://github.com/Expensify/Expensify.cash/issues/4029#issuecomment-880087243. What do you think?

If we invite a phone number, It is not added to the assignee list until we refresh the page.
Ooh now this is weird. I would think the optimistic addition from here would add them in. Did it work before with just one phone number?

Str.isValidPhone is returning true for value 98?
When I read this, I thought this must be a bug, but it turns out it's technically right 😖 ?

It looks like we're using the E.164 specification and technically those can be valid international numbers. 2 digits seems really short, but I think that's fine since it matches the specification. A source I found for this:
https://stackoverflow.com/questions/6478875/regular-expression-matching-e-164-formatted-phone-numbers/23299989#23299989
Some others buffer it by more digits, but I don't think we need  to change this part.

Ooh now this is weird. I would think the optimistic addition from here would add them in. Did it work before with just one phone number?

I think the list expects emails so a ph number should be converted to @expensify.sms email first.

Some others buffer it by more digits, but I don't think we need to change this part.

Ok.

What is the update on this change?

@MitchExpensify PR merged https://github.com/Expensify/App/pull/4068

It's been deployed recently to prod I believe.

Paid, sorry for the delay @parasharrajat !


Scifi. For Daniel, Nat, Roon, and Andrej. 💜

whoa what an easter egg...!

Magisk, including all git submodules are free software:
you can redistribute it and/or modify it under the terms of the
GNU General Public License as published by the Free Software Foundation,
either version 3 of the License, or (at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program.  If not, see http://www.gnu.org/licenses/.```


Job reservation is missing, unsuitable for scalability

It looks live the driver does not honor job reservations like the redis or database driver.
At this point when you would run multiple instances of the queue worker, for example 10 workers. And PubSub having an acknowledge deadline of 10 seconds.
It is very likely that multiple workers run the same job.
(I was also able to actually reproduce this, multiple workers working on the same job ID)
An other flaw is the acknowledge deadline, if you have job that might take a couple of hours, it will probably exceed the PubSub acknowledge deadline;
Any thoughts how this is desired to be implemented?, i am happy to help out to write something for this.
I think building a reservation system like redis and the database driver would be an over complicated solution, while you cannot fetch a reserved job back, and delete it once it's released back to the queue, or should be deleted forever.
From my opinion it would be easier to: https://cloud.google.com/pubsub/docs/reference/rest/v1/projects.subscriptions/modifyAckDeadline
The deadline should be synchronised, by the timeout setting of the queue worker if possible.
Assume that would solve both issues...
Let me know what u guys think
Thnx
Danny

Hi @v8-ict
I think a PR was submitted regarding this. You issue should be fixed if messages are acknowleged when received (in the current implementation, they are acknowleged after the proccessing).
I don't remember why I closed this PR, but feel free to submit a new one if you know how to fix it. Otherwise I will work on it when I have some free time.

Fixed the acknowledgement issue on master branch. A new version will be pushed later this week with few other fixes.


Remove Memory reservation on Windows

Windows does not have a memory reservation in the platform. This removes the field from the runtime spec.
Signed-off-by: Darren Stahl<EMAIL_ADDRESS>

LGTM

LGTM


Can add the function of entering purple？

Can add the function of entering purple？

Currently using version 2.0 with the boot to purple mode built in because this version with purple pro (purple pro failure not MagicCFG) fails to boot my iPhone 8 into purple mode. It boots enough to get the phones screen to change to white and stop. It doesn't make it to the iterm screen. Would be nice to have back to being built in


Adds Kontent.ai CMS guide

What kind of changes does this PR include?

New or updated content

Description

Adds CMS guide for connecting Kontent.ai to Astro including the blog page use case

Hey there @ondrabus !
We're a little backed up on CMS guides right now, but we'll take a look at this as soon as we can!

For anyone following along; Here's the preview CMS guide: https://deploy-preview-4049--astro-docs-2.netlify.app/en/guides/cms/kontent-ai/

@ElianCodes thank you for the review! All suggestions made sense to me, so I committed them directly and added two minor tweaks.

Hey @ondrabus. Thanks for applying the changes! This is on my radar to finish and merge this week!
So keep an eye here! I'll be in touch soon!

Heads up that I'm doing a full first-round review today!

Hey @ElianCodes, all good, thank you for the suggestions!

Hey @ondrabus, I see that you added quite a lot of the suggestions, but you forgot some. Can you take a quick look if you've added everything?

Hi @ElianCodes, some of them were indeed hidden a button click away from me :-) I resolved them now.

@Yan-Thomas thank you! All suggestions merged 👍

Awesome @ondrabus thanks for taking the time to process our reviews! I'll be taking another look at everything in the PR today!


Adding schema renaming and three-part name support to Copy-DbaDbTableData

Type of Change

[x] Bug fix (non-breaking change, fixes #4134)
[x] New feature (non-breaking change, adds functionality)
[ ] Breaking change (effects multiple commands or functionality)
[ ] Ran manual Pester test and has passed (`.\tests\manual.pester.ps1)
[ ] Adding code coverage to existing functionality
[ ] Pester test is included
[ ] Nunit test is included
[ ] Documentation
[ ] Build system

Purpose
Adding support for -DestinationTable database.schema.tablename
Fixing some bugs along the way (schema name replacement)
Approach
Get-TableNameParts and regex magic
Commands to test
Copy-DbaDbTableData -SqlInstance sql1 -Database DB1 -AutoCreateTable -Table T1 -DestinationTable DB2.dbo.[T2.1] -Verbose
Screenshots

Learning

heck yeah! thank you!

:banandance:


PassManager quick review

PLEASE NOT MERGE.  Also how Gradient and InferShapeType will change accordingly. Please have a look.
After we fix the interface, I will create the pass-manager branch in nnvm for further development.

Changes highlights:
New Pass Interface:
class Pass {
  void Setup();
  PassResult RunOnGraph(Graph src, const PasssArgument& args);
  void Finalize();
};

Setup and Finalize will only be called once when the pass is created and destroyed, while RunOnGraph may be called multiple times.
New Attribute Interfaces
The old adhoc attribute interface is still kept. The categorized attributes are simply implemented by prefixing to distinguish them.

Set/GetGraphAttr: All graph attributes are destroyed if a graph is changed by a pass.
Set/GetNodeAttr: All node attribute keys are prefixed by __node_. They will only be kept if PassResult specifies the node_remapping field by a pass.
Set/GetNodeEntryAttr: All node entry attribute keys are prefixed by __entry_. They will only be kept if PassResult specifies the entry_remapping field by a pass.
Set/GetPassAttr: All pass attribute keys are prefixed by __pass_. They will never be destroyed unless the corresponding pass is destroyed.

PassManager Inferface

Enable: Enable a pass during running.
EnforceOrder: Specify the order of two passes.
SetPassArguments: Set the arguments of pass running.
Run: Run all enabled passes in the order that we've discussed about.

Welcome any comments!

should we consider that one pass may depend on multiple other passes?  if this situation is often, maybe it's good to provide an interface like PassManager& EnforceOrder(const std::string& prev, const std::vector<std::string>& succ).
also, I'm curious about the schedule rule of the pass manager, if A ->(depend on) C, and B -> (depend on) C, will the sort should be C=>A=>B/ C=>B=>A or C=>A=>C=>B/C=>B=>C=>A?

You mean both A and B will change the graph?

right

If C is an immutable pass, it should be C->A->C->B and Enforce(A, B) should be called otherwise error will be thrown. I think a more problematic one is if A and B are both mutable passes, A provides a, B provides b and another pass C depends on a and b, what is the order? It seems that we have cyclic problem here since schedule either A or B will erase the other's attributes.

Maybe it's too rough to delete all previous results after every pass. We can consider a way to preserve the results of previous passes by their dependency.

Any updates on this?
I'm worried some changes will break mxnet. Could you open a new branch for this?

Sorry, haven't updated this for a long time. It is already on a new branch and I will merge the master myself. It is not meant to be merged in short time. Just ask for advices for the changes.


Broken link to full 'LabelSectionController.swift'

Changes in this pull request
Pull request checklist

[ ] All tests pass. Demo project builds and runs.
[ ] I added tests, an experiment, or detailed why my change isn't tested.
[ ] I have reviewed the contributing guide

Replaced with direct link in repo

Changes Unknown when pulling 0b58de153bbd1abc3cdd177a237e84b2751cbc7c on linkthrow:patch-1 into ** on Instagram:master**.

Changes Unknown when pulling 0b58de153bbd1abc3cdd177a237e84b2751cbc7c on linkthrow:patch-1 into ** on Instagram:master**.

Good call. I'm about to take @KrauseFx's advice and unit test our documentation.

👍


Profiler fails to profile the bigquery tables in case of partition type of table and field of Record Datatype

Affected module
Ingestion Framework
Describe the bug
Profiler Ingestion fails to compute metrics/profiler data in case of schema containing RECORD  datatype as mentioned here

OM parses above schema as array or struct based on if it’s repeated or not

now when we try to run profiler for these partitioned table with these fields, then computed query from OM fails on the bigquery side as it doesn’t unnest this field as array while firing to bigquery, now since this query fails we are not getting the profiling results for these tables which is like 90% of our datasets. This issue can be resolved if we use UNNEST function of bigquery for those array fields while firing it to the bigquery.
To Reproduce

Create bigquery partitioned type of table.
Add fields in the schema of datatype RECORD in bigquery.

Run the profiler workflow and see the failed profiler logs / Find the created profiler query and run in the bigquery console directly and see the error in the bigquery console.

Encountered exception Logs
[2023-01-03 10:38:55] INFO     {Ingestion:database_service:206} - Scanned [yyy.bq.schedule_record_event]
[2023-01-03 10:38:55] DEBUG    {Ingestion:noop_secrets_manager:46} - Adding auth provider security config using noop secrets' manager
[2023-01-03 10:38:55] DEBUG    {OMetaAPI:server_mixin:86} - Validating client and server versions
[2023-01-03 10:38:55] DEBUG    {OMetaAPI:client:177} - URL http://localhost:8585/api/v1/version, method GET
[2023-01-03 10:38:55] DEBUG    {OMetaAPI:client:178} - Data {'headers': {'Content-type': 'application/json', 'Authorization': 'Bearer no_token'}, 'allow_redirects': False, 'params': None}
[2023-01-03 10:38:55] DEBUG    {OMetaAPI:client:177} - URL http://localhost:8585/api/v1/version, method GET
[2023-01-03 10:38:55] DEBUG    {OMetaAPI:client:178} - Data {'headers': {'Content-type': 'application/json', 'Authorization': 'Bearer no_token'}, 'allow_redirects': False, 'params': None}
[2023-01-03 10:38:55] DEBUG    {OMetaAPI:client:177} - URL http://localhost:8585/api/v1/databaseSchemas/95601612-6dc1-4586-a138-144d185a403a, method GET
[2023-01-03 10:38:55] DEBUG    {OMetaAPI:client:178} - Data {'headers': {'Content-type': 'application/json', 'Authorization': 'Bearer no_token'}, 'allow_redirects': False, 'params': None}
[2023-01-03 10:38:58] INFO     {Profiler:core:376} - Computing profile metrics for yyy.bq.schedule_record_event...
[2023-01-03 10:39:04] DEBUG    {Profiler:stddev:83} - schedule_record_event.event_id has type VARCHAR, which is not listed as quantifiable. We won't compute STDDEV for it.
[2023-01-03 10:39:07] DEBUG    {Profiler:stddev:83} - schedule_record_event.event_source has type VARCHAR, which is not listed as quantifiable. We won't compute STDDEV for it.
[2023-01-03 10:39:11] DEBUG    {Profiler:stddev:83} - schedule_record_event.event_type has type VARCHAR, which is not listed as quantifiable. We won't compute STDDEV for it.
[2023-01-03 10:39:14] DEBUG    {Profiler:min_length:50} - Don't know how to process type FLOAT when computing MIN_LENGTH
[2023-01-03 10:39:14] DEBUG    {Profiler:max_length:50} - Don't know how to process type FLOAT when computing MAX_LENGTH
[2023-01-03 10:39:18] DEBUG    {Profiler:mean:71} - Don't know how to process type TIMESTAMP when computing MEAN
[2023-01-03 10:39:18] DEBUG    {Profiler:min_length:50} - Don't know how to process type TIMESTAMP when computing MIN_LENGTH
[2023-01-03 10:39:18] DEBUG    {Profiler:max_length:50} - Don't know how to process type TIMESTAMP when computing MAX_LENGTH
[2023-01-03 10:39:18] DEBUG    {Profiler:stddev:83} - schedule_record_event.event_time has type TIMESTAMP, which is not listed as quantifiable. We won't compute STDDEV for it.
[2023-01-03 10:39:21] DEBUG    {Profiler:mean:71} - Don't know how to process type TIMESTAMP when computing MEAN
[2023-01-03 10:39:21] DEBUG    {Profiler:min_length:50} - Don't know how to process type TIMESTAMP when computing MIN_LENGTH
[2023-01-03 10:39:21] DEBUG    {Profiler:max_length:50} - Don't know how to process type TIMESTAMP when computing MAX_LENGTH
[2023-01-03 10:39:21] DEBUG    {Profiler:stddev:83} - schedule_record_event.last_update_ts has type TIMESTAMP, which is not listed as quantifiable. We won't compute STDDEV for it.
[2023-01-03 10:39:25] DEBUG    {Profiler:stddev:83} - schedule_record_event.correlation_id has type VARCHAR, which is not listed as quantifiable. We won't compute STDDEV for it.
[2023-01-03 10:39:28] DEBUG    {Profiler:stddev:83} - schedule_record_event.record_source has type VARCHAR, which is not listed as quantifiable. We won't compute STDDEV for it.
[2023-01-03 10:39:32] DEBUG    {Profiler:mean:71} - Don't know how to process type DATE when computing MEAN
[2023-01-03 10:39:32] DEBUG    {Profiler:min_length:50} - Don't know how to process type DATE when computing MIN_LENGTH
[2023-01-03 10:39:32] DEBUG    {Profiler:max_length:50} - Don't know how to process type DATE when computing MAX_LENGTH
[2023-01-03 10:39:32] DEBUG    {Profiler:stddev:83} - schedule_record_event.create_date has type DATE, which is not listed as quantifiable. We won't compute STDDEV for it.
[2023-01-03 10:39:35] DEBUG    {Profiler:mean:71} - Don't know how to process type TIMESTAMP when computing MEAN
[2023-01-03 10:39:35] DEBUG    {Profiler:min_length:50} - Don't know how to process type TIMESTAMP when computing MIN_LENGTH
[2023-01-03 10:39:35] DEBUG    {Profiler:max_length:50} - Don't know how to process type TIMESTAMP when computing MAX_LENGTH
[2023-01-03 10:39:35] DEBUG    {Profiler:stddev:83} - schedule_record_event.source_record_create_ts has type TIMESTAMP, which is not listed as quantifiable. We won't compute STDDEV for it.
[2023-01-03 10:39:38] DEBUG    {Profiler:stddev:83} - schedule_record_event.client_country_code has type VARCHAR, which is not listed as quantifiable. We won't compute STDDEV for it.
[2023-01-03 10:39:42] DEBUG    {Profiler:stddev:83} - schedule_record_event.client_code has type VARCHAR, which is not listed as quantifiable. We won't compute STDDEV for it.
[2023-01-03 10:39:45] DEBUG    {Profiler:min_length:50} - Don't know how to process type INTEGER when computing MIN_LENGTH
[2023-01-03 10:39:45] DEBUG    {Profiler:max_length:50} - Don't know how to process type INTEGER when computing MAX_LENGTH
[2023-01-03 10:39:49] DEBUG    {Profiler:stddev:83} - schedule_record_event.client_location_name has type VARCHAR, which is not listed as quantifiable. We won't compute STDDEV for it.
[2023-01-03 10:39:53] DEBUG    {Profiler:stddev:83} - schedule_record_event.schedule_category_code has type VARCHAR, which is not listed as quantifiable. We won't compute STDDEV for it.
[2023-01-03 10:39:56] DEBUG    {Profiler:min_length:50} - Don't know how to process type INTEGER when computing MIN_LENGTH
[2023-01-03 10:39:56] DEBUG    {Profiler:max_length:50} - Don't know how to process type INTEGER when computing MAX_LENGTH
[2023-01-03 10:40:00] DEBUG    {Profiler:min_length:50} - Don't know how to process type FLOAT when computing MIN_LENGTH
[2023-01-03 10:40:00] DEBUG    {Profiler:max_length:50} - Don't know how to process type FLOAT when computing MAX_LENGTH
[2023-01-03 10:40:03] DEBUG    {Profiler:mean:71} - Don't know how to process type DATE when computing MEAN
[2023-01-03 10:40:03] DEBUG    {Profiler:min_length:50} - Don't know how to process type DATE when computing MIN_LENGTH
[2023-01-03 10:40:03] DEBUG    {Profiler:max_length:50} - Don't know how to process type DATE when computing MAX_LENGTH
[2023-01-03 10:40:03] DEBUG    {Profiler:stddev:83} - schedule_record_event.shift_start_date has type DATE, which is not listed as quantifiable. We won't compute STDDEV for it.
[2023-01-03 10:40:06] DEBUG    {Profiler:stddev:83} - schedule_record_event.shift_start_time has type VARCHAR, which is not listed as quantifiable. We won't compute STDDEV for it.
[2023-01-03 10:40:10] DEBUG    {Profiler:mean:71} - Don't know how to process type DATE when computing MEAN
[2023-01-03 10:40:10] DEBUG    {Profiler:min_length:50} - Don't know how to process type DATE when computing MIN_LENGTH
[2023-01-03 10:40:10] DEBUG    {Profiler:max_length:50} - Don't know how to process type DATE when computing MAX_LENGTH
[2023-01-03 10:40:10] DEBUG    {Profiler:stddev:83} - schedule_record_event.shift_end_date has type DATE, which is not listed as quantifiable. We won't compute STDDEV for it.
[2023-01-03 10:40:14] DEBUG    {Profiler:stddev:83} - schedule_record_event.shift_end_time has type VARCHAR, which is not listed as quantifiable. We won't compute STDDEV for it.
[2023-01-03 10:40:17] DEBUG    {Profiler:min_length:50} - Don't know how to process type INTEGER when computing MIN_LENGTH
[2023-01-03 10:40:17] DEBUG    {Profiler:max_length:50} - Don't know how to process type INTEGER when computing MAX_LENGTH
[2023-01-03 10:40:20] DEBUG    {Profiler:stddev:83} - schedule_record_event.worker_name has type VARCHAR, which is not listed as quantifiable. We won't compute STDDEV for it.
[2023-01-03 10:40:23] DEBUG    {Profiler:min_length:50} - Don't know how to process type INTEGER when computing MIN_LENGTH
[2023-01-03 10:40:23] DEBUG    {Profiler:max_length:50} - Don't know how to process type INTEGER when computing MAX_LENGTH
[2023-01-03 10:40:26] DEBUG    {Profiler:stddev:83} - schedule_record_event.workgroup_name has type VARCHAR, which is not listed as quantifiable. We won't compute STDDEV for it.
[2023-01-03 10:40:29] DEBUG    {Profiler:min_length:50} - Don't know how to process type INTEGER when computing MIN_LENGTH
[2023-01-03 10:40:29] DEBUG    {Profiler:max_length:50} - Don't know how to process type INTEGER when computing MAX_LENGTH
[2023-01-03 10:40:32] DEBUG    {Profiler:stddev:83} - schedule_record_event.job_name has type VARCHAR, which is not listed as quantifiable. We won't compute STDDEV for it.
[2023-01-03 10:40:36] DEBUG    {Profiler:min_length:50} - Don't know how to process type INTEGER when computing MIN_LENGTH
[2023-01-03 10:40:36] DEBUG    {Profiler:max_length:50} - Don't know how to process type INTEGER when computing MAX_LENGTH
[2023-01-03 10:40:40] DEBUG    {Profiler:stddev:83} - schedule_record_event.labor_role_name has type VARCHAR, which is not listed as quantifiable. We won't compute STDDEV for it.
[2023-01-03 10:40:43] DEBUG    {Profiler:stddev:83} - schedule_record_event.shift_type_code has type VARCHAR, which is not listed as quantifiable. We won't compute STDDEV for it.
[2023-01-03 10:40:47] DEBUG    {Profiler:stddev:83} - schedule_record_event.schedule_available_to_worker_flag has type VARCHAR, which is not listed as quantifiable. We won't compute STDDEV for it.
[2023-01-03 10:40:50] DEBUG    {Profiler:stddev:83} - schedule_record_event.trace_metadata.key_value.key has type VARCHAR, which is not listed as quantifiable. We won't compute STDDEV for it.
[2023-01-03 10:40:51] DEBUG    {Profiler:stddev:83} - schedule_record_event.trace_metadata.key_value.value has type VARCHAR, which is not listed as quantifiable. We won't compute STDDEV for it.
[2023-01-03 10:41:10] DEBUG    {Profiler:median:53} - Don't know how to process type VARCHAR when computing Median
[2023-01-03 10:41:12] DEBUG    {Profiler:median:53} - Don't know how to process type VARCHAR when computing Median
[2023-01-03 10:41:14] DEBUG    {Profiler:median:53} - Don't know how to process type VARCHAR when computing Median
[2023-01-03 10:41:18] DEBUG    {Profiler:median:53} - Don't know how to process type TIMESTAMP when computing Median
[2023-01-03 10:41:20] DEBUG    {Profiler:median:53} - Don't know how to process type TIMESTAMP when computing Median
[2023-01-03 10:41:22] DEBUG    {Profiler:median:53} - Don't know how to process type VARCHAR when computing Median
[2023-01-03 10:41:24] DEBUG    {Profiler:median:53} - Don't know how to process type VARCHAR when computing Median
[2023-01-03 10:41:26] DEBUG    {Profiler:median:53} - Don't know how to process type DATE when computing Median
[2023-01-03 10:41:28] DEBUG    {Profiler:median:53} - Don't know how to process type TIMESTAMP when computing Median
[2023-01-03 10:41:30] DEBUG    {Profiler:median:53} - Don't know how to process type VARCHAR when computing Median
[2023-01-03 10:41:32] DEBUG    {Profiler:median:53} - Don't know how to process type VARCHAR when computing Median
[2023-01-03 10:41:36] DEBUG    {Profiler:median:53} - Don't know how to process type VARCHAR when computing Median
[2023-01-03 10:41:38] DEBUG    {Profiler:median:53} - Don't know how to process type VARCHAR when computing Median
[2023-01-03 10:41:44] DEBUG    {Profiler:median:53} - Don't know how to process type DATE when computing Median
[2023-01-03 10:41:46] DEBUG    {Profiler:median:53} - Don't know how to process type VARCHAR when computing Median
[2023-01-03 10:41:48] DEBUG    {Profiler:median:53} - Don't know how to process type DATE when computing Median
[2023-01-03 10:41:50] DEBUG    {Profiler:median:53} - Don't know how to process type VARCHAR when computing Median
[2023-01-03 10:41:54] DEBUG    {Profiler:median:53} - Don't know how to process type VARCHAR when computing Median
[2023-01-03 10:41:58] DEBUG    {Profiler:median:53} - Don't know how to process type VARCHAR when computing Median
[2023-01-03 10:42:01] DEBUG    {Profiler:median:53} - Don't know how to process type VARCHAR when computing Median
[2023-01-03 10:42:05] DEBUG    {Profiler:median:53} - Don't know how to process type VARCHAR when computing Median
[2023-01-03 10:42:06] DEBUG    {Profiler:median:53} - Don't know how to process type VARCHAR when computing Median
[2023-01-03 10:42:08] DEBUG    {Profiler:median:53} - Don't know how to process type VARCHAR when computing Median
[2023-01-03 10:42:10] DEBUG    {Profiler:median:53} - Don't know how to process type VARCHAR when computing Median
[2023-01-03 10:42:12] DEBUG    {Profiler:median:53} - Don't know how to process type ARRAY when computing Median
[2023-01-03 10:42:13] DEBUG    {Profiler:median:53} - Don't know how to process type VARCHAR when computing Median
[2023-01-03 10:42:15] DEBUG    {Profiler:median:53} - Don't know how to process type VARCHAR when computing Median
[2023-01-03 10:42:17] DEBUG    {Profiler:workflow:426} - Traceback (most recent call last):
  File "/Users/Desktop/airflow-plugins/data-catalog-airflow-plugins/venv/lib/python3.9/site-packages/google/cloud/bigquery/dbapi/cursor.py", line 203, in _execute
    self._query_job.result()
  File "/Users/Desktop/airflow-plugins/data-catalog-airflow-plugins/venv/lib/python3.9/site-packages/google/cloud/bigquery/job/query.py", line 1499, in result
    do_get_result()
  File "/Users/Desktop/airflow-plugins/data-catalog-airflow-plugins/venv/lib/python3.9/site-packages/google/api_core/retry.py", line 283, in retry_wrapped_func
    return retry_target(
  File "/Users/Desktop/airflow-plugins/data-catalog-airflow-plugins/venv/lib/python3.9/site-packages/google/api_core/retry.py", line 190, in retry_target
    return target()
  File "/Users/Desktop/airflow-plugins/data-catalog-airflow-plugins/venv/lib/python3.9/site-packages/google/cloud/bigquery/job/query.py", line 1489, in do_get_result
    super(QueryJob, self).result(retry=retry, timeout=timeout)
  File "/Users/Desktop/airflow-plugins/data-catalog-airflow-plugins/venv/lib/python3.9/site-packages/google/cloud/bigquery/job/base.py", line 728, in result
    return super(_AsyncJob, self).result(timeout=timeout, **kwargs)
  File "/Users/Desktop/airflow-plugins/data-catalog-airflow-plugins/venv/lib/python3.9/site-packages/google/api_core/future/polling.py", line 137, in result
    raise self._exception
google.api_core.exceptions.BadRequest: 400 Cannot access field key on a value with type ARRAY<STRUCT<key STRING, value STRING>> at [4:2163]

Location: US
Job ID: db1e3933-650a-4cba-b29e-8cd77d69f31a

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/Users/Desktop/airflow-plugins/data-catalog-airflow-plugins/venv/lib/python3.9/site-packages/sqlalchemy/engine/base.py", line 1802, in _execute_context
    self.dialect.do_execute(
  File "/Users/Desktop/airflow-plugins/data-catalog-airflow-plugins/venv/lib/python3.9/site-packages/sqlalchemy/engine/default.py", line 719, in do_execute
    cursor.execute(statement, parameters)
  File "/Users/Desktop/airflow-plugins/data-catalog-airflow-plugins/venv/lib/python3.9/site-packages/google/cloud/bigquery/dbapi/_helpers.py", line 494, in with_closed_check
    return method(self, *args, **kwargs)
  File "/Users/Desktop/airflow-plugins/data-catalog-airflow-plugins/venv/lib/python3.9/site-packages/google/cloud/bigquery/dbapi/cursor.py", line 166, in execute
    self._execute(
  File "/Users/Desktop/airflow-plugins/data-catalog-airflow-plugins/venv/lib/python3.9/site-packages/google/cloud/bigquery/dbapi/cursor.py", line 205, in _execute
    raise exceptions.DatabaseError(exc)
google.cloud.bigquery.dbapi.exceptions.DatabaseError: 400 Cannot access field key on a value with type ARRAY<STRUCT<key STRING, value STRING>> at [4:2163]

Location: US
Job ID: db1e3933-650a-4cba-b29e-8cd77d69f31a

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/Users/data-catalog-airflow-plugins/ingestion/src/metadata/orm_profiler/api/workflow.py", line 418, in execute
    profile: TableProfile = self.profiler_obj.process(
  File "/Users/data-catalog-airflow-plugins/ingestion/src/metadata/orm_profiler/profiler/core.py", line 379, in process
    self.compute_metrics()
  File "/Users/data-catalog-airflow-plugins/ingestion/src/metadata/orm_profiler/profiler/core.py", line 364, in compute_metrics
    self.profile_entity()
  File "/Users/data-catalog-airflow-plugins/ingestion/src/metadata/orm_profiler/profiler/core.py", line 355, in profile_entity
    profile_results = self.profiler_interface.get_all_metrics(
  File "/Users/data-catalog-airflow-plugins/ingestion/src/metadata/interfaces/sqa_interface.py", line 299, in get_all_metrics
    profile, column = future.result()
  File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/concurrent/futures/_base.py", line 439, in result
    return self.__get_result()
  File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/concurrent/futures/_base.py", line 391, in __get_result
    raise self._exception
  File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/Users/data-catalog-airflow-plugins/ingestion/src/metadata/interfaces/sqa_interface.py", line 267, in compute_metrics_in_thread
    row = compute_metrics_registry.registry[metric_type.value](
  File "/Users/data-catalog-airflow-plugins/ingestion/src/metadata/interfaces/sqa_interface.py", line 487, in get_query_metrics
    row = runner.select_first_from_query(metric_query)
  File "/Users/data-catalog-airflow-plugins/ingestion/src/metadata/orm_profiler/profiler/runner.py", line 95, in select_first_from_query
    return query.first()
  File "/Users/Desktop/airflow-plugins/data-catalog-airflow-plugins/venv/lib/python3.9/site-packages/sqlalchemy/orm/query.py", line 2810, in first
    return self.limit(1)._iter().first()
  File "/Users/Desktop/airflow-plugins/data-catalog-airflow-plugins/venv/lib/python3.9/site-packages/sqlalchemy/orm/query.py", line 2894, in _iter
    result = self.session.execute(
  File "/Users/Desktop/airflow-plugins/data-catalog-airflow-plugins/venv/lib/python3.9/site-packages/sqlalchemy/orm/session.py", line 1689, in execute
    result = conn._execute_20(statement, params or {}, execution_options)
  File "/Users/Desktop/airflow-plugins/data-catalog-airflow-plugins/venv/lib/python3.9/site-packages/sqlalchemy/engine/base.py", line 1614, in _execute_20
    return meth(self, args_10style, kwargs_10style, execution_options)
  File "/Users/Desktop/airflow-plugins/data-catalog-airflow-plugins/venv/lib/python3.9/site-packages/sqlalchemy/sql/elements.py", line 325, in _execute_on_connection
    return connection._execute_clauseelement(
  File "/Users/Desktop/airflow-plugins/data-catalog-airflow-plugins/venv/lib/python3.9/site-packages/sqlalchemy/engine/base.py", line 1481, in _execute_clauseelement
    ret = self._execute_context(
  File "/Users/Desktop/airflow-plugins/data-catalog-airflow-plugins/venv/lib/python3.9/site-packages/sqlalchemy/engine/base.py", line 1845, in _execute_context
    self._handle_dbapi_exception(
  File "/Users/Desktop/airflow-plugins/data-catalog-airflow-plugins/venv/lib/python3.9/site-packages/sqlalchemy/engine/base.py", line 2026, in _handle_dbapi_exception
    util.raise_(
  File "/Users/Desktop/airflow-plugins/data-catalog-airflow-plugins/venv/lib/python3.9/site-packages/sqlalchemy/util/compat.py", line 207, in raise_
    raise exception
  File "/Users/Desktop/airflow-plugins/data-catalog-airflow-plugins/venv/lib/python3.9/site-packages/sqlalchemy/engine/base.py", line 1802, in _execute_context
    self.dialect.do_execute(
  File "/Users/Desktop/airflow-plugins/data-catalog-airflow-plugins/venv/lib/python3.9/site-packages/sqlalchemy/engine/default.py", line 719, in do_execute
    cursor.execute(statement, parameters)
  File "/Users/Desktop/airflow-plugins/data-catalog-airflow-plugins/venv/lib/python3.9/site-packages/google/cloud/bigquery/dbapi/_helpers.py", line 494, in with_closed_check
    return method(self, *args, **kwargs)
  File "/Users/Desktop/airflow-plugins/data-catalog-airflow-plugins/venv/lib/python3.9/site-packages/google/cloud/bigquery/dbapi/cursor.py", line 166, in execute
    self._execute(
  File "/Users/Desktop/airflow-plugins/data-catalog-airflow-plugins/venv/lib/python3.9/site-packages/google/cloud/bigquery/dbapi/cursor.py", line 205, in _execute
    raise exceptions.DatabaseError(exc)
sqlalchemy.exc.DatabaseError: (google.cloud.bigquery.dbapi.exceptions.DatabaseError) 400 Cannot access field key on a value with type ARRAY<STRUCT<key STRING, value STRING>> at [4:2163]

Location: US
Job ID: db1e3933-650a-4cba-b29e-8cd77d69f36a

[SQL: /* {"app": "OpenMetadata", "version": "<IP_ADDRESS>"} */
WITH `only_once` AS
(SELECT count(`trace_metadata`.`key_value`.`value`) AS `count_1`
FROM (SELECT `schedule_record_event`.`event_id` AS `event_id`, `schedule_record_event`.`event_source` AS `event_source`, `schedule_record_event`.`event_type` AS `event_type`, `schedule_record_event`.`event_specversion` AS `event_specversion`, `schedule_record_event`.`event_time` AS `event_time`, `schedule_record_event`.`last_update_ts` AS `last_update_ts`, `schedule_record_event`.`correlation_id` AS `correlation_id`, `schedule_record_event`.`record_source` AS `record_source`, `schedule_record_event`.`create_date` AS `create_date`, `schedule_record_event`.`source_record_create_ts` AS `source_record_create_ts`, `schedule_record_event`.`client_country_code` AS `client_country_code`, `schedule_record_event`.`client_code` AS `client_code`, `schedule_record_event`.`client_location_id` AS `client_location_id`, `schedule_record_event`.`client_location_name` AS `client_location_name`, `schedule_record_event`.`schedule_category_code` AS `schedule_category_code`, `schedule_record_event`.`shift_id` AS `shift_id`, `schedule_record_event`.`shift_net_hours` AS `shift_net_hours`, `schedule_record_event`.`shift_start_date` AS `shift_start_date`, `schedule_record_event`.`shift_start_time` AS `shift_start_time`, `schedule_record_event`.`shift_end_date` AS `shift_end_date`, `schedule_record_event`.`shift_end_time` AS `shift_end_time`, `schedule_record_event`.`client_worker_id` AS `client_worker_id`, `schedule_record_event`.`worker_name` AS `worker_name`, `schedule_record_event`.`workgroup_id` AS `workgroup_id`, `schedule_record_event`.`workgroup_name` AS `workgroup_name`, `schedule_record_event`.`job_id` AS `job_id`, `schedule_record_event`.`job_name` AS `job_name`, `schedule_record_event`.`labor_role_id` AS `labor_role_id`, `schedule_record_event`.`labor_role_name` AS `labor_role_name`, `schedule_record_event`.`shift_type_code` AS `shift_type_code`, `schedule_record_event`.`schedule_available_to_worker_flag` AS `schedule_available_to_worker_flag`, `schedule_record_event`.`trace_metadata` AS `trace_metadata`, `schedule_record_event`.`trace_metadata`.`key_value` AS `trace_metadata_key_value`, `schedule_record_event`.`trace_metadata`.`key_value`.`key` AS `trace_metadata_key_value_key`, `schedule_record_event`.`trace_metadata`.`key_value`.`value` AS `trace_metadata_key_value_value`
FROM `cs_gwfm`.`schedule_record_event`
WHERE `event_time` >= %(event_time_1:STRING)s AND `event_time` <= %(event_time_2:STRING)s) AS `anon_1` GROUP BY `trace_metadata`.`key_value`.`value`
HAVING count(`trace_metadata`.`key_value`.`value`) = %(count_2:INT64)s)
 SELECT count(*) AS `uniqueCount`
FROM `only_once`
 LIMIT %(param_1:INT64)s]
[parameters: {'event_time_1': '2022-12-04', 'event_time_2': '2023-01-04', 'count_2': 1, 'param_1': 1}]
(Background on this error at: https://sqlalche.me/e/14/4xp6)

Expected behavior
Expectation is to use unnest operator of bigquery to unnest array type of fields in case of partitioned tables and execute the profiling without failure.
Version:

OS: ios
Python version: python3.9
OpenMetadata version: <IP_ADDRESS>
OpenMetadata Ingestion package version: [e.g. openmetadata-ingestion[docker]==<IP_ADDRESS>]

Additional context

Better to use https://github.com/googleapis/python-bigquery-sqlalchemy for bigquery instead of https://github.com/sqlalchemy/sqlalchemy for bigquery as sqlalchemy doesn't understand bigquery operators.


API leads to confusion between node ids and labels

Given that Node constructor takes Label, and Label supports HTML, I expected
Factory.graph().with(Factory.node(Label.html("a")))

to work and produce bold "a". However, in my tests it produces a node with text "a" as label, when rendered on JSVGCanvas. Instead, I need
Factory.mutGraph().with(Factory.node("some random id").with("label", Label.html("a"))))

Is this the expected result, or is it just failure on Batik's side?

You are right, there's a confusion. I'm going to look at this.

Finally, this works now as expected.


adds workflow for deploying sample-service to dev0 cluster

ch3494

Should we create a helmrelease k8s object like with roadie-backstage?

@nicolasarnold12321 I like the idea, but I think it adds a bit of complexity. I dont think we need the type of auto recovery and resiliance for this service. What do you think?

@nicolasarnold12321 I like the idea, but I think it adds a bit of complexity. I dont think we need the type of auto recovery and resiliance for this service. What do you think?

We could even just deploy it manually instead of having automation if you prefer. Whenever we make changes to chart in the future we just bump the chart version. I just don't really like the idea of github creating resources that's all.

If you're happy with that I don't mind approving!
Might be worth adding a change to the sample-service repo so that it is triggered.

ok cool. done. Ive deployed it manually. Ill close this.


improve performance of package by lazy loading or removing extra unneeded dependencies

@avoinea let's wait for @zotya review on Monday, there seems to be issues with elastic/search-ui updates and not from my changes but from new releases.
I am trying with a pin I added 1.21.3 but I might have todo 1.19.0 since there seems to be export changes from 1.2x.x releases

Puttin in draft due to trying to lazy load luxon and now  with the latest commit the loading of the apps is stuck without an error given

@zotya although I could get around loading DateTime within ResultModel https://github.com/eea/volto-searchlib/pull/133/commits/e8201a94040ef6c5461ad0cf5cadfc3cfb6ddc1e#diff-f183675ede2f9b6838700ea8542a58fd10e8cebaa5d8c578ef2c7e50ebef666aR117
I couldn't get it to work to lazy load from here https://github.com/eea/volto-searchlib/blob/master/searchlib/components/DateTime/DateTime.jsx
As such I am limiting the scope of this pull request to only get rid of the elastic/react-search-ui-views


Inquiry about Training Data Used in the Sana Paper and Its Availability

I have thoroughly read the Sana paper and found it highly insightful.
However, I couldn't find detailed information regarding the training data used for the model.
Could you please provide clarification on the following points?

What specific datasets were used to train the Sana model?
Is there any plan to release or make the training data publicly available for research purposes?

I believe that knowing more about the data used in training would greatly benefit the research community.
Thank you for your time and for sharing your work.

Data is a senstive thing. We will discuss about it later.

Refer to: https://github.com/NVlabs/Sana/issues/95


[CARBONDATA-3532] Support Query Rollup for MV TimeSeries Queries

Supported Query RollUp for MV TimeSeries queries.
How it is supported?
For each timeseries query, check if query can be rolled up from the existing datasets, by replacing the granularity in given user query. If query is rewritten and rolledUp, then add Select and Group by nodes on the rewritten query.
User Query:
SELECT timeseries(col,'day') from maintable group by timeseries(col,'day')
Available datasets,
datamap1 => SELECT timeseries(col,'hour') from maintable group by timeseries(col,'hour')
datamap2 => SELECT timeseries(col,'second') from maintable group by timeseries(col,'second')
Rewritten Query For datamap1:
`SELECT datamap1_table.`UDF:timeseries_projectjoindate_hour` AS `UDF:timeseries (projectjoindate,hour)`
 FROM
 default.datamap1_table
 GROUP BY datamap1_table.`UDF:timeseries_projectjoindate_hour``

RolledUp Query:
`SELECT timeseries(gen_subsumer_0.`UDF:timeseries(projectjoindate, hour)`,'day' ) AS
`UDF:timeseries(projectjoindate, day)`
FROM

( SELECT datamap2_table.`UDF:timeseries_projectjoindate_hour` AS
 `UDF:timeseries(projectjoindate,hour)`
  FROM
  default.datamap2_table
  GROUP BY datamap2_table.`UDF:timeseries_projectjoindate_hour` )    gen_subsumer_0

GROUP BY timeseries(gen_subsumer_0.`UDF:timeseries(projectjoindate, hour)`,'day' )`

Performance report:
MainTable schema: 88 columns
Tested on 3 node cluster
Data size - 4.8GB
DataMaps :
DM1 => created with query SELECT timeseries(timecolumn,'hour'), sum(intcolumn) from mainTable group by timeseries(timecolumn,'hour')
DM2 => created with query SELECT timeseries(timecolumn,'second'), sum(intcolumn) from mainTable group by timeseries(timecolumn,'second')
Query: SELECT timeseries(timecolumn,'day'), sum(intcolumn) from mainTable group by timeseries(timecolumn,'day')

MainTable(time in seconds)
DataMap(Rolledup (DM1)) table(time in seconds)

5.458
2.002

[ ] Any interfaces changed?

[ ] Any backward compatibility impacted?

[x] Document update required?

[x] Testing done

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.1/1076/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.2/1085/

Build Failed  with Spark 2.3.2, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/1094/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.1/1079/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.2/1088/

Build Failed  with Spark 2.3.2, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/1098/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.1/1085/

Build Failed with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.2/1094/

Build Success with Spark 2.3.2, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/1104/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.1/1090/

Build Success with Spark 2.3.2, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/1109/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.2/1099/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.1/1122/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.2/1131/

Build Success with Spark 2.3.2, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/1141/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.1/1126/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.2/1135/

Build Success with Spark 2.3.2, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/1145/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.1/1137/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.2/1146/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/1156/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.1/1146/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.2/1155/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/1165/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.1/1151/

Build Success with Spark 2.2.1, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.2/1160/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/1170/

retest this please

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/1828/

Build Failed  with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.4/13/

Build Success with Spark 2.4.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbon_PR_Builder_2.4.4/130/

Build Success with Spark 2.3.4, Please check CI http://<IP_ADDRESS>:12545/job/ApacheCarbonPRBuilder2.3/1834/

LGTM

LGTM


Bug: Query method fails in case of nested struct

Describe the bug
type BaseModel struct {
	ID        *models.RecordID       `json:"id,omitempty"`
	CreatedAt *models.CustomDateTime `json:"created_at,omitempty"`
	UpdatedAt *models.CustomDateTime `json:"updated_at,omitempty"`
}

UnitOfMeasureResponse struct {
	BaseModel
	Name             string                  `json:"name"`
	Code             string                  `json:"code"`
	BaseUnit         *UnitOfMeasureResponse  `json:"base_unit,omitempty"`
	ConversionFactor float64                 `json:"conversion_factor,omitempty"`
	IsBase           bool                    `json:"is_base,omitempty"`
	Description      string                  `json:"description,omitempty"`
}

type AttributeResponse struct {
	BaseModel
	Name     string                 `json:"name"`
	Unit     *UnitOfMeasureResponse `json:"unit,omitempty"`
	DataType string                 `json:"data_type,omitempty"`
}

When I try to call the Query method as below:
res, err := surrealdb.Query[surrealdb.Result[[]AttributeResponse]](db.DB, query, nil)
if err != nil {
	return nil, err
}

I am getting the following error:
cbor: cannot unmarshal array into Go struct field
connection.RPCResponse[[]github.com/surrealdb/surrealdb%2ego.QueryResult[github.com/surrealdb/surrealdb%2ego.Result[[]olive/models.AttributeResponse]]].result of
type surrealdb.Result[[]olive/models.AttributeResponse] (cannot decode CBOR array to struct without toarray option)

Steps to reproduce
Mentioned above
Expected behaviour
Nested struct should be supported
SurrealDB version
surreal 2.0.4, surrealdb.go 0.3.0, windows 11
Contact Details
<EMAIL_ADDRESS>Is there an existing issue for this?

[X] I have searched the existing issues

Code of Conduct

[X] I agree to follow this project's Code of Conduct

I noticed that this seems to work:
results, err := surrealdb.Query[[]AttributeResponse](db.DB, query, nil)
if results == nil {
   // handle this to prevent panics
}
rows, err := (*results)[0] // there was only one query, so this should eixst

More specifically, the TResult of the .Query (between the []) should be an array.
That does result in some ugly parsing/validating/error-checking code, so I wouldn't be surprised if this changed again in a future update.

@EtienneBruines please verify again it does NOT work

@EtienneBruines please verify again it does NOT work

I think it has been changed a little, I will post the updated way here tomorrow


Transforming incoming data?

Forgive me if I'm missing something, but it's not immediately apparent to me nor does it seem to be mentioned in the docs:
What about recieving data? If I have an object in the database, and for simplicity's sake let's us the example that in the database a column is called "start_date", I transform this to simply be "start" when it's sent to the client. Now, when I recieve data back, it will obviously just be a "start" property, which isn't actually in the database.
Do transformers support inverting their own operations?

@philsturgeon That link is now dead, and in any case refers to Ruby code, not PHP code. Do you have any recommendations for getting this behavior in a way that complements a Fractal transformer? Is there any likelihood in it being added here? (I note that this issue and many similar ones remain closed.)


Team - Random info

Add location to team member's list
Add current % defense boost from team members somewhere
Add the ability to promote someone to team leader
Add online/offline to team members list
Add ability to rename team

This is related to #123
Closing this as a duplicate


Closing brace has too much spacing

Currently, the closing brace autocompletes to } );
Although there's no standard for this in WP's PHP, there is one for WP JS, which is to not space this out.

This is fixed in 0.2.1 which will be released shortly.


Escape character is now inserted for subsequent keypresses when the A…

…lt modifier is held down
I suppose this is more of a question on reasoning than a real request for my patch to be merged, is the behavior of enforcing self.ctx.received_count() to be zero typical? I noticed that using Emacs in alacritty felt a little bit off, since I tried to use M-< and M-> to navigate the buffer and it would only work for the first keystroke, with any subsequent keystrokes inserting '<' into the buffer. This is the only terminal emulator I've used that does this.
To reproduce this, I would suggest running cat and inserting key sequences while holding the alt key.
In URxvt:
$ cat
^[<^[>^[<^[>^[<^[>^[<^[>

In alacritty:
$ cat
^[<><><><>

The behavior for holding down a key is similar, only inserting the escape character once. URxvt and xterm insert the escape character every time when '<' or '>' are held down.
Although, while doing a little bit more experimentation I've found that this issue only applies to 'M-<' and 'M->'. I can hold Alt and insert nearly any other keystroke, including those where Shift is held down.

I have no idea why received_characters() == 0 was added. Git blame doesn't help either. :disappointed:
I'll try removing it locally and see if I run into any problems.


Imported functionallity from the host

What is your question?
We are currently using Javy and are very happy with it! The way we are using the Wasm modules output by Javy currently is that, from the host runtime we are providing a JSON input over its stdin and parsing a JSON output from its stdout. The Wasm modules are written by our users and most of them don't need all the data in the JSON. As we add more data to the JSON input, it keeps getting larger and it takes longer to produce.
Performance could be improved if we could, instead of providing all the data the Wasm module could possibly need before it is invoked, have the Wasm module be able to request the information that it actually needs through imported functions from the host (custom ones outside of the WASI standard). Is this something that Javy plans to support in the future?

Have you read our documentation on extending Javy, which includes adding custom APIs?
To summarize what's in there, we have a number of crates published to crates.io which we recommend using and then writing your own CLI and javy-core implementation that re-use those crates.

Thanks a lot!


Auto play

Can we have help to modify the code and implement auto play on the first radio in the list?

we must add in the tag , the src="" and autoplay and it's good :)

we must add in the tag , the src="" and autoplay and it's good :)

in the which file?


Enable HSTS protection for CDN assets.

Enabling HTTP Strict Transport Security will afford better protection to CDN traffic.
Currently assets can be served over HTTP or HTTPS from the CDN, there is no redirection from HTTP to HTTPS. By enabling HSTS, capable clients will automatically upgrade to using HTTPS whilst those that are not capable, or may not be capable, will remain on HTTP.
This can be done in the following ways:

Inject the Strict-Transport-Security header when serving assets.
HSTS preload the CDN domain.
A combination of 1 and 2.

For reference: https://twitter.com/Scott_Helme/status/761537848218644480

Do other CDNs do this? Google doesn't do this as far as I can tell.
I'm all for security and stuff but the redirect takes some time, even if it's a trivial amount. Also, if the user chose to go with plain HTTP, they know what they get.

Both Google and Microsoft do this: https://scotthel.me/cdn
With HSTS there is no redirection, this is one of the benefits. The browser will use HTTPS on the first request, even if the src attribute specifies HTTP.
It's not the user that chooses HTTP/HTTPS, it's the site owner. If the browser is HSTS compliant then it will use HTTPS, if not it will continue to use HTTP as before.

You are right about the redirection part, of course, I totally mixed those up.
By user I meant the site owner, not the visitor. So if the site owner believes they don't need SSL, who are we to force them? :P
Joking aside, this should be investigated before any actual changes made to the CDN.
I'm personally all for security (I follow your posts for some time now). It's just that better be safe than sorry.

I agree completely, the impact of the change needs to be fully explored, of course.
As for the site owner, whilst they do choose what protocol they embed in the src attribute, they have no control over the user agent. If the user agent is HSTS capable and chooses to upgrade their connection to the CDN, I don't think the site owner has a say there. If they wish to control that, they should host the asset themselves ;-)

For the record, starting on day 1 (July 25 2012) we promoted schemeless url's:

We switched to promoting https only on March 31st 2015.
Unfortunately MaxCDN doesn't have a report showing HTTP vs HTTPs (yet) so we have to stick to assumptions.

Joking aside, this should be investigated before any actual changes made to the CDN.

@XhmikosR is dead on. And I am glad you agree, @ScottHelme. With that said I would like to assemble a Task Force (always wanted to say that) that will explore this and put together a plan. TF (so far):

@jonathanKingston
@ScottHelme
@XhmikosR
@jmervine

A Google Doc might in order. Thoughts?

Would there be issues if assets got redirected to https?

Well a redirect is definitely slower. With HSTS preload, the browser will use the HTTPS version. See https://github.com/MaxCDN/bootstrap-cdn/issues/750#issuecomment-239620743

I just meant additionally as well as the HSTS header. If HTTP only needed to be deprecated in the future.

For now I think HSTS will absorb a lot of any remaining HTTP requests. The preload approach is especially favourable here if the redirect is a concern.
It's also worth noting that if a browser got a single HTTP -> HTTPS redirect and then picked up HSTS on one site, it'd never see it again on any other site using the CDN.
Should the CDN ever start redirecting HTTP -> HTTPS, the only browsers that would ever see a continued impact from the redirect would be those that aren't HSTS compliant. Even then, I believe they'd cache a 301 for 30 days, further reducing the impact. However, we aren't there yet, so no real worry.

It's been a few years since 2016 :) Since then we had a good experience enabling HSTS on the CDN domain on jsDelivr without any problems. So I took the liberty to enable it here as well.

Hmm, we might need to update https://github.com/MaxCDN/bootstrapcdn/blob/develop/test/functional_test.js, I'll try to have a look in the next days.

Expected headers will need to be updated


Bump addressable from 2.7.0 to 2.8.0

Bumps addressable from 2.7.0 to 2.8.0.

Release notes
Changelog
Commits

updated-dependencies:

dependency-name: addressable
dependency-type: indirect
...

Signed-off-by: dependabot[bot]<EMAIL_ADDRESS>

This looks amazing/.

here is another commnet.


Update the README.md

Hey!
I suggest adding badges for tech stack for a cool look
If its ok, I would like to work on this issue
Thoughts?? (example)

Yh, this would be nice.
I'll assign this to you real quick.

Thanks for the reply
Working on it in some time


fix: use container for responsiveness

Describe the changes you have made in this PR
Modifies the Container component and uses it for responsiveness.
Link this PR to an issue
Extends #1118
Type of change (Remove other not matching type)

fix: Bug fix (non-breaking change which fixes an issue)

Screenshots of the changes (If any)

How has this been tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Checklist

[x] My code follows the style guidelines of this project and performed a self-review of my own code
[x] New and existing tests pass locally with my changes
[x] I checked if I need to make corresponding changes to the documentation (and made those changes if needed)

Tested with "Send". lgtm

@im-adithya could you check the conflict?

Done!


mlayer-datasetAPI updates

added instance parameter to getAllDatasets method in mlayer service to filter out responses based on instance
corrected query to get all domains in popular dataset API
added 0 count instead of null in popular dataset API

Can one of the admins verify this patch?

ok to test


Nfs client provisioner

What this PR does / why we need it: Add PodSecurityPolicy support

/ok-to-test

/ok-to-test

/retest

/lgtm

/lgtm cancel
Wait for one more round of testing

Tests pass
/lgtm


the string 'fasfafhttp://google.com' recognition error

result:
'fasfafhttp://google.com'  => 'fasfafhttp://' + google.com
i want
'fasfafhttp://google.com'  => 'fasfaf' + http://google.com:
version 3.0.3

@nfrasser are you considering fixing this for v4? or is this desired behavior for Linkify going forward?
FWIW, a lot of user input text fields suffer from this problem, so it's unfortunately something we have to deal with often and it was great when linkify handled it automatically.

are you considering fixing this for v4? or is this desired behavior for Linkify going forward?

Unfortunately no, it would require a complete rethinking of the internal parsing system and honestly I don't have the necessary language processing knowledge to do it

it was great when linkify handled it automatically.

I don't recall that linkify was ever able to handle these cases, except perhaps years ago in V1. Do you know the last version of linkify where this worked?


Distributing into .dmg

Hello,
I'm trying to create a .dmg to distribute my app but I can't because of the symlinks in Contents/Frameworks/Electron Framework/.
cp: cannot create symbolic link '/mnt/test/HackHands.app/Contents/Frameworks/Electron Framework.framework/Frameworks': Operation not permitted
cp: cannot create symbolic link '/mnt/test/HackHands.app/Contents/Frameworks/Electron Framework.framework/Libraries': Operation not permitted
cp: cannot create symbolic link '/mnt/test/HackHands.app/Contents/Frameworks/Electron Framework.framework/Electron Framework': Operation not permitted
cp: cannot create symbolic link '/mnt/test/HackHands.app/Contents/Frameworks/Electron Framework.framework/Versions/Current': Operation not permitted
cp: cannot create symbolic link '/mnt/test/HackHands.app/Contents/Frameworks/Electron Framework.framework/Versions/A/Libraries/Libraries': Operation not permitted
cp: cannot create symbolic link '/mnt/test/HackHands.app/Contents/Frameworks/Electron Framework.framework/Resources': Operation not permitted
cp: cannot create symbolic link '/mnt/test/HackHands.app/Contents/Frameworks/Squirrel.framework/Headers': Operation not permitted
cp: cannot create symbolic link '/mnt/test/HackHands.app/Contents/Frameworks/Squirrel.framework/Squirrel': Operation not permitted
cp: cannot create symbolic link '/mnt/test/HackHands.app/Contents/Frameworks/Squirrel.framework/Modules': Operation not permitted
cp: cannot create symbolic link '/mnt/test/HackHands.app/Contents/Frameworks/Squirrel.framework/Versions/Current': Operation not permitted
cp: cannot create symbolic link '/mnt/test/HackHands.app/Contents/Frameworks/Squirrel.framework/Resources': Operation not permitted
cp: cannot create symbolic link '/mnt/test/HackHands.app/Contents/Frameworks/Mantle.framework/Headers': Operation not permitted
cp: cannot create symbolic link '/mnt/test/HackHands.app/Contents/Frameworks/Mantle.framework/Modules': Operation not permitted
cp: cannot create symbolic link '/mnt/test/HackHands.app/Contents/Frameworks/Mantle.framework/Mantle': Operation not permitted
cp: cannot create symbolic link '/mnt/test/HackHands.app/Contents/Frameworks/Mantle.framework/Versions/Current': Operation not permitted
cp: cannot create symbolic link '/mnt/test/HackHands.app/Contents/Frameworks/Mantle.framework/Resources': Operation not permitted
cp: cannot create symbolic link '/mnt/test/HackHands.app/Contents/Frameworks/ReactiveCocoa.framework/Headers': Operation not permitted
cp: cannot create symbolic link '/mnt/test/HackHands.app/Contents/Frameworks/ReactiveCocoa.framework/Modules': Operation not permitted
cp: cannot create symbolic link '/mnt/test/HackHands.app/Contents/Frameworks/ReactiveCocoa.framework/ReactiveCocoa': Operation not permitted
cp: cannot create symbolic link '/mnt/test/HackHands.app/Contents/Frameworks/ReactiveCocoa.framework/Versions/Current': Operation not permitted
cp: cannot create symbolic link '/mnt/test/HackHands.app/Contents/Frameworks/ReactiveCocoa.framework/Resources': Operation not permitted

I also tried run with sudo but doesn't works.
Any workaround for this problem?

From my experiences with dmg files it absolutely supports symbol links, I suggest asking about this on StackOverflow or the electron forum since it looks more like a general problem to me.