auto-updated

Testing #172034
I have two windows open: vscode & xterm.js
In vscode, I ran code-insiders --install-extension<EMAIL_ADDRESS>in the terminal
I opened xterm.js and saw the extension version was 13.1.1, but it said reload required as an option. I reloaded the window. It was updated to 13.2.0, but I expected it to stay the same

I think this happened bc I had vscode opened in a profile and as indicated in a diff't issue, when you update the extension via code-cli, it doesn't work within there

actually, reproduces. install via cli, version is correct ✅ , reload window, auto-updated 🐛
https://user-images.githubusercontent.com/29464607/214389436-dceecf96-241c-43ca-a239-b73b52bb622a.mov

I just tried same steps and it seems I cant repro it. May I know are you on different profile in the VS Code you have opened?

May I know are you on different profile in the VS Code you have opened?

What do you mean?

VS Code window in the above window, are you on default profile or different profile?

different profile I think

I could not reproduce, may be I am not following the steps. Can you please provide me the exact steps ?


ppc64le: add support for building docker debs for xenial

This PR adds the ability to make docker debs for xenial on ppc64le.
This is pretty standard except for a few specific power+xenial issues.

Seccomp isn't enabled by default because the latest package version is a bit too old to
have power support in it. Once that gets updated to 2.3+, it can be added back in.
Edit: The base xenial package (v2.2.3-3) contains backports of all the power and z related changes.

Power doesn't have an official 1.6.2 golang binary we can download, so we have to build from
source. In order to build from source, we need a previous version of go, so we download that from
the xenial repo (go1.6.1), bootstrap build latest go, and then remove the older version.

Signed-off-by: Christopher Jones<EMAIL_ADDRESS>

Unfortunately it is unclear if they will update libseccomp, so far there seems to have been a policy of not doing it, although I am going to try filing issues to try to change this - maybe you could file an issue against the ppc64le port on the Ubuntu bug tracker? It seems like a security issue to me not properly supporting the running platform for this...

Yeah I agree, I'm not sure what's going on with the version, but I'll go ahead and submit a bug report on the ppc64le side for it.

LGTM.

okay, looks like power support was backported in an earlier release of libseccomp that I didn't see. I'm going to test some more and update this again.

Ah that sounds hopeful...

Updated. So all the tests passed with the xenial base version of seccomp enabled. Looking more into the package, power xenial seccomp just backported all the power and z related commits from 2.3.0 and 2.3.1 into 2.2.3-3 and just ignored all the x86 changes, hence it being an older version.

LGTM

Since the 1.12 madness is over, could this be rebased & looked at again? :cat:

I'll rebase and add in the man page dockerfile when I get back on Monday 😎

Rebased and added in the dockerfile for the man pages.

updated LGTM.

LGTM

Thanks guys!!  🎉


nested models still not working in v3-beta.7

As mentioned by @AruXc in https://github.com/vue-generators/vue-form-generator/issues/515#issuecomment-430064876
I'm using the latest beta (beta.7) of V3 and the checklist does not seem to support nested models.
This works:
<vue-form-generator :schema="test.schema" :model="test.model"></vue-form-generator>

      test: {
        model: {
          test: [],
        },
        schema: {
          fields: [
            {
              type: 'checklist',
              model: 'test',
              label: 'Test',
              values: [
                'apple', //
                'orange',
                'kiwi',
              ],
              fieldOptions: {
                listBox: true,
              },
              onChanged(model) {
                console.log('skills changed to', model.test);
              },
              onValidated(model, errors) {
                console.log('skills validated:', errors);
              },
            },
          ],
        },
      },

But this does not work:
      test: {
        model: {
          test: {
            test: [],
          },
        },
        schema: {
          fields: [
            {
              type: 'checklist',
              model: 'test.test',
              label: 'Test',
              values: [
                'apple', //
                'orange',
                'kiwi',
              ],
              fieldOptions: {
                listBox: true,
              },
              onChanged(model) {
                console.log('skills changed to', model.test);
              },
              onValidated(model, errors) {
                console.log('skills validated:', errors);
              },
            },
          ],
        },
      },

It gives the following error:
Uncaught TypeError: Cannot read property 'push' of undefined
    at VueComponent.onChanged (vfg.umd.min.js?06f3:1)
    at change (vfg.umd.min.js?06f3:1)
    at invoker (vue.js?ba4c:2128)
    at HTMLInputElement.fn._withTask.fn._withTask (vue.js?ba4c:1913)

@lionel-bijaoui mentioned this should be fixed in https://github.com/vue-generators/vue-form-generator/pull/532
But that was merged into beta.7 and that's what I'm using.. so not sure if it's something I'm doing or if it's still broken.. but it seems to not be working.. would appreciate some help! Thanks!

I just tested this against the v3 branch, and your second example appears to work just fine
I'd also like to point out that V3 is still in development and not ready for general use yet.

@zoul0813 thanks for getting back
I know it's still in dev, and I'm using it in dev too, my project isn't launched yet. But I really need the new improved grouping in order to create sub-groups.
Anyway I'm very surprised you didn't see the problem. Maybe I wasn't clear.. the checklist does render properly, it's only when you open the console that you see the error, only when you actually try to check items in the checklist.
I was wondering if this might be due to some other dependencies in my project so I created a minimal repo here
https://github.com/vesper8/vue-form-generator-v3-checklist-test
And I can still reproduce the problem...
Are you checking against a V3 branch that has more commits since the tagged beta.7? If so, how can I also pull that in? I'm using
    "vue-form-generator": "git://github.com/vue-generators/vue-form-generator.git#v3"

yarn list | grep vue-form-generator shows
├─<EMAIL_ADDRESS>
Here's a screenshot of what I see

And the minimal code
https://github.com/vesper8/vue-form-generator-v3-checklist-test/blob/master/src/main.js
https://github.com/vesper8/vue-form-generator-v3-checklist-test/blob/master/src/App.vue


GLFW_CURSOR_DISABLED produces large deltas

I am testing GLFW on an Ubuntu Desktop 16.04 LTS x64 on Oracle VirtualBox 5.0.20 with a Windows 7 x64 host.
There, when I use glfwSetInputMode(window, GLFW_CURSOR, GLFW_CURSOR_DISABLED); the callback registered via glfwSetCursorPosCallback receives very large position deltas. For example, when I move the mouse only one pixel to the right, the xpos delta sometimes is -400.0, other times -110.0 and then sometimes even -1000.0, also somtimes positive and sometimes negative.
I know that the xpos and ypos coordinates can have arbitrary large values since the mouse cursor is unrestricted. But I am talking about the delta (the changes between successive xpos and ypos values for successive calls of the callback). I am getting very large deltas here.
On Windows everything is fine. It's just weird on Ubuntu Desktop 16.04 LTS. I don't know whether it is a thing with Oracle VirtualBox.
Here is the example app I use to test this:
#include <GLFW/glfw3.h>
#include <stdlib.h>
#include <stdio.h>
static void error_callback(int error, const char* description) {
    fprintf(stderr, "Error: %s\n", description);
}
static void key_callback(GLFWwindow* window, int key, int scancode, int action, int mods) {
    if (key == GLFW_KEY_ESCAPE && action == GLFW_PRESS)
        glfwSetWindowShouldClose(window, GLFW_TRUE);
}
static void cp_callback(GLFWwindow* window, double xpos, double ypos) {
  fprintf(stderr, "%f , %f\n", (float)xpos, (float)ypos);
  fflush(stderr);
}
int main(void) {
    GLFWwindow* window;
    glfwSetErrorCallback(error_callback);
    if (!glfwInit())
        exit(EXIT_FAILURE);
    window = glfwCreateWindow(640, 480, "", NULL, NULL);
    if (!window) {
        glfwTerminate();
        exit(EXIT_FAILURE);
    }
    glfwSetKeyCallback(window, key_callback);
    glfwSetCursorPosCallback(window, cp_callback);
    glfwSetInputMode(window, GLFW_CURSOR, GLFW_CURSOR_DISABLED);
    while (!glfwWindowShouldClose(window)) {
        glfwPollEvents();
    }
    glfwDestroyWindow(window);
    glfwTerminate();
    exit(EXIT_SUCCESS);
}

And here is the output I get from moving the mouse cursor very very slightly (should be just one pixel each) to the right:
639.000000 , 479.000000
958.000000 , 479.000000
1277.000000 , 479.000000
1596.000000 , 479.000000
1915.000000 , 479.000000
2234.000000 , 479.000000
2553.000000 , 479.000000
2872.000000 , 479.000000
3191.000000 , 479.000000
3510.000000 , 479.000000

In this run, the delta happens to be around +319.0'ish.
I do not have a HighDPI monitor or HighDPI mouse.
The issue does not happen when using GLFW_CURSOR_HIDDEN or GLFW_CURSOR_NORMAL. In those two settings, I get correct pixel values.

Have you disabled cursor integration in VirtualBox?

Hm... if, then not consciously. This is a very off the shelves installation with absolutely no customization of settings or stuff. The only thing I did was to install the Guest Additions which compiled and built successfully.

Interesting. When I disable mouse cursor integration (leaving that mouse in the status bar gray with a yellow arrow) the readings of the cursor position are correct now.

This is not a bug, it's just GLFW and VirtualBox fighting over where the cursor should be. Leave cursor integration off while you're working with disabled cursor mode and it'll be fine.

Thank you! Will do.


Spacing issue with (non-symbol) completions

Although this appears in the same context as #618, it is a completely separate issue.

Note that the completion has no space before expression.

Deal with this as part of #620.


How to deploy openvino to another win10 computer (product side)?

How to deploy openvino to another win10 computer (product side) that is not installed. If I have a complete program locally, I only need to deploy the local program to the target win10 computer. Do the target computers need to install some additional libraries? Such as python, MsBuild, Visual Studio...etc?

You only need to install the libraries that you use during runtime and their dependencies (mainly, inference engine). You, probably, don't need anything from what you mentioned.


Revert back to stable Version

How to revert back from beta version to stable version

I'm not certain which OS you're on, but basically you need to go to atom.io, download stable and install it over beta.  If you are on Mac, Beta and Stable are installed side by side.
Thanks for reaching out!
We require the template to be filled out on all new issues and pull requests. We do this so that we can be certain we have all the information we need to address your submission efficiently. This allows the maintainers to spend more time fixing bugs, implementing enhancements, and reviewing and merging pull requests.
Thanks for understanding and meeting us half way 😀
Please reopen if this hasn't fixed your issue.

@ungb i am using win 8.1 and installed beta 1.18 on stable 1.17

if you go to https://atom.io/, you should beable to grab stable.  I suggest you go to control panel and remove Atom and then install Atom Stable(from https://atom.io/)

@ungb but action cant be revert back? tough I installed beta on stable
and is there any way to have both versions at same time


Is it possible to pass props other than 'value' via Select?

The problem with Select - MenuItem is that the value must match for it to work. But I like to add additional props through onChange and it doesn't seem to allow that.

    <FormControl>
      <InputLabel>排序方式</InputLabel>
      <Select
        value={displayList}
        onChange={listMenu}
      >
      {Object.keys(sortListMap).map((name, key) =>
        <MenuItem
          key={key}
          value={name}
          props={{sort: sortListMap[name].sort}}
        >
          {`按${sortListMap[name].name}排序`}
        </MenuItem>
      )}
      </Select>
    </FormControl>

For example I may want to add additional props 'sort' as shown above.

@aeroxy You could apply the prop as an data-sort attribute. Alternatively, you can retrieve the sort value from the name at any time.

Did you mean something like this?
    <FormControl>
      <InputLabel>排序方式</InputLabel>
      <Select
        value={displayList}
        onChange={listMenu}
        MenuProps={{
          PaperProps: {
            style: {
              backgroundColor: '#1d1d2e'
            }
          }
        }}
      >
      {Object.keys(sortListMap).map((name, key) =>
        <MenuItem
          key={key}
          value={name}
          data-sort={sortListMap[name].sort}
        >
          {`按${sortListMap[name].name}排序`}
        </MenuItem>
      )}
      </Select>
    </FormControl>

The above code doesn't seem to work. There is no data object in event or event.target. I tried to lookup your source code here:
  handleItemClick = (child: Element<any>) => (event: SyntheticMouseEvent<> & { target?: any }) => {
    if (!this.props.multiple) {
      this.setState({
        open: false,
      });
    }

    if (this.props.onChange) {
      const { onChange, name } = this.props;
      let value;
      let target;

      if (event.target) {
        target = event.target;
      }

      if (this.props.multiple) {
        value = Array.isArray(this.props.value) ? [...this.props.value] : [];
        const itemIndex = value.indexOf(child.props.value);
        if (itemIndex === -1) {
          value.push(child.props.value);
        } else {
          value.splice(itemIndex, 1);
        }
      } else {
        value = child.props.value;
      }

      event.persist();
      event.target = { ...target, value, name };

      onChange(event, child);
    }
  };

It seems to me that only value was taken from the props on MenuItem.


Enabling ErrorProne and NullAway with initial fixes

Description of what I changed

See #1247 for the context. This is mostly to enable ErrorProne and NullAway. These two exposed over 370 warnings. From these, less than 20 are addressed in this PR; this is still WIP.
E2E test

TESTED:
Relying on e2e/unit tests.
Checklist: I completed these to help reviewers :)

[x] I have read and will follow the review process.

[x] I am familiar with Google Style Guides for the language I have coded in.
No? Please take some time and review Java and Python style guides.

[x] My IDE is configured to follow the Google code styles.
No? Unsure? -> configure your IDE.

[ ] I have added tests to cover my changes. (If you refactored existing code that was well tested you do not have to add tests)

[x] I ran mvn clean package right before creating this pull request and added all formatting changes to my commit.

[x] All new and existing tests passed.

[x] My pull request is based on the latest changes of the master branch.
No? Unsure? -> execute command git pull --rebase upstream master

Codecov Report
Attention: Patch coverage is 87.50000% with 3 lines in your changes missing coverage. Please review.

Project coverage is 51.45%. Comparing base (ea7d0fe) to head (46327df).

Files with missing lines
Patch %
Lines

...main/java/com/google/fhir/analytics/FetchUtil.java
0.00%
1 Missing :warning:

...com/google/fhir/analytics/JdbcConnectionPools.java
0.00%
1 Missing :warning:

...in/java/com/google/fhir/analytics/ParquetUtil.java
95.00%
1 Missing :warning:

Additional details and impacted files
@@             Coverage Diff              @@
##             master    #1248      +/-   ##
============================================
- Coverage     51.49%   51.45%   -0.05%
+ Complexity      717      714       -3
============================================
  Files            95       95
  Lines          5909     5912       +3
  Branches        787      786       -1
============================================
- Hits           3043     3042       -1
- Misses         2578     2581       +3
- Partials        288      289       +1

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

🚨 Try these New Features:

Flaky Tests Detection - Detect and resolve failed and flaky tests

@chandrashekar-s I think this is ready for review (I'll remove the Maven log file from this PR later; keeping it for now to have a sample of new WARNING messages).
BTW, the e2e-test failed a few times but passed on its own here. Looking at the some of the failed tests, I think there is a race condition between the BULK_EXPORT test and the controller test. IIUC from the dep graph and FHIR-server parameters, I think both of these tests are querying http://hapi-server:8080; but the problem is that in the controller test we are testing the incremental pipeline functionality as well. So depending on whether it runs before or after BULK_EXPORT test we may get extra resources in BULK_EXPORT test, does that make sense?

@chandrashekar-s I think this is ready for review (I'll remove the Maven log file from this PR later; keeping it for now to have a sample of new WARNING messages).
BTW, the e2e-test failed a few times but passed on its own here. Looking at the some of the failed tests, I think there is a race condition between the BULK_EXPORT test and the controller test. IIUC from the dep graph and FHIR-server parameters, I think both of these tests are querying http://hapi-server:8080; but the problem is that in the controller test we are testing the incremental pipeline functionality as well. So depending on whether it runs before or after BULK_EXPORT test we may get extra resources in BULK_EXPORT test, does that make sense?

I think you are right Bashir, there can be a race condition here because of parallel tests. This has to be fixed. Also, one more issue that I could think of is that 'Turning of the HAPI source server' is not made dependent on the BULK EXPORT Test and can run into issues if the server is turned off before the BULK EXPORT job completes.


Next.js 13 App Router Issue

Hello,
I am working on a project with Next.js 13 and it seems that there is this error when I am using useWallet in any file of the app dir.
error -<EMAIL_ADDRESS>(37:2) @ DEFAULT_COUNTEXT
error - TypeError: (0 , import_react.createContext) is not a function
    at eval (webpack-internal:///(sc_server)/./node_modules/@aptos-labs/wallet-adapter-react/dist/index.js:39:52)
    at<EMAIL_ADDRESS>(/home/homefolder/dev/project/web_app/frontend/.next/server/app/home/page.js:579:1)
    at __webpack_require__ (/home/homefolder/dev/project/web_app/frontend/.next/server/webpack-runtime.js:33:43)
    at eval (webpack-internal:///(sc_server)/./src/app/components/AppContext.tsx:30:91)
    at Module.(sc_server)/./src/app/components/AppContext.tsx (/home/homefolder/dev/project/web_app/frontend/.next/server/app/home/page.js:1820:1)
    at __webpack_require__ (/home/homefolder/dev/project/web_app/frontend/.next/server/webpack-runtime.js:33:43)
    at eval (webpack-internal:///(sc_server)/./src/app/layout.tsx:12:80)
    at Module.(sc_server)/./src/app/layout.tsx (/home/homefolder/dev/project/web_app/frontend/.next/server/app/home/page.js:1923:1)
    at Function.__webpack_require__ (/home/homefolder/dev/project/web_app/frontend/.next/server/webpack-runtime.js:33:43)
    at processTicksAndRejections (node:internal/process/task_queues:96:5) {
  type: 'TypeError',
  page: '/home'
}

Implementing the old way with pages and _app.tsx has no problems.

looks like our demo app uses Next version 13.0.0 https://github.com/aptos-labs/aptos-wallet-adapter/blob/main/apps/nextjs-example/package.json#L30 , what is the exact Next version you are trying to use?

looks like our demo app uses Next version 13.0.0 https://github.com/aptos-labs/aptos-wallet-adapter/blob/main/apps/nextjs-example/package.json#L30 , what is the exact Next version you are trying to use?

yes, I am trying to use the wallet adapter with Next 13.0.0 and the new app directory that I am talking about is this one: https://beta.nextjs.org/docs/routing/fundamentals, looks like your demo app is developed in the old way with pages/

looks like our demo app uses Next version 13.0.0 https://github.com/aptos-labs/aptos-wallet-adapter/blob/main/apps/nextjs-example/package.json#L30 , what is the exact Next version you are trying to use?

yes, I am trying to use the wallet adapter with Next 13.0.0 and the new app directory that I am talking about is this one: https://beta.nextjs.org/docs/routing/fundamentals, looks like your demo app is developed in the old way with pages/

For any pages that involving the wallets, should be done in browser side. The simple solution is add 'use client' on top of the file imported AptosWalletAdapterProvider.


Wiki

Hi,
I recently discovered your API but it's very hard to understand and use, a simple wiki / documentation would be great.
Have a nice and wonderful day,
Mouton_redstone

Hello,
I don't use this anymore, so it might not be working anymore. I'm not planning a wiki, as this project is more or less deprecated, but what do you need help with? I'd be happy to assist.
I have an example in the README.


Error after upgrading Docker

error while interpolating services.powerauth-nextstep.mem_limit: failed to cast to expected type: strconv.ParseInt: parsing "700m": invalid syntax

See also: https://github.com/docker/for-mac/issues/6041


How to visualize the proportional distribution of positive and negative sample gradients of different category classifiers

Hello, I want to ask if there is any visual code or tool script for the gradient proportional distribution of positive and negative samples of different categories of classifiers in mmdet. For example, the visualization of the gradient ratio of positive and negative samples in Seesaw Loss paper. I also want to have such visual pictures added to my paper. Thank you for telling me.

@chensen668 Sorry, we do not provide such tools at the moment.

@chensen668 Sorry, we do not provide such tools at the moment.

Is there any relevant instance code? I think some authors say that  can collect positive and negative gradients (of output Logits) in the training for each category. But I don't know how to encode it.


Use OSC8 terminal hyperlinks in aur search

Many terminals use OSC 8 to allow hyperlinking text in the terminal, as
described in here, and most that don't will silently eat the link and
just display the same text.  This adds support so that an aur search
can link to the AUR webpage for further information.
Note that I rarely write Bash scripts, doing most of my programming in other languages; Iʼm sure that despite what Shellcheck says Iʼve done somethnig thatʼs bad style or worse, and Iʼd be willing to fix that if pointed out.

I don't use a terminal that supports OSC8, but I guess the proposed functionality is useful if you do. I will wait a while to see if more people are interested in this feature.

I will wait a while to see if more people are interested in this feature.

This feature looks beneficial to me :+1:

I've tried this in gnome-terminal and it looks pretty nice.
@Earnestly you mentioned a review, but I still can't see it in this window. Could you maybe mention it again?

I have no idea how to use this interface

They keep changing it, and every time it's more confusing...


stop_text_encoder_training missing for SDXL and could we set different LR for text encoder training for SDXL?

I just wanted to use stop_text_encoder_training since SDXL text encoder becomes overcooked very quickly but SDXL train not supporting it
Moreover by any chance could we set separate learning rate for text encoder?
LR for U-NET cooking the text encoder very badly

@kohya-ss thank you so much


Kenshi - Not Launching.

Well basically the game isn't launching at all while using DXVK. However, it used to work a couple of months ago, so I'm inclined to believe it might be related to my AMD drivers (which are up-to-date). I added Kenshi's logs as part of the log files, at the very end it's throwing me the following error:
"OGRE EXCEPTION(80004005:RenderingAPIException): Failed to create Direct3D11 device in D3D11RenderSystem::D3D11RenderSystem at ......\RenderSystems\Direct3D11\src\OgreD3D11RenderSystem.cpp (line 265)"
Again, I would like to clarify that this is the first time something like this has happened, Kenshi used to work flawlessly using DXVK, so I really don't really know what happened. In any case, thanks!
Software information
Kenshi
System information

GPU: RX 580
Driver: 24.3.1
Wine version: -
DXVK version: 2.3.1 (latest release)

Apitrace file(s)
Log files
kenshi_x64_d3d11.log
kenshi_x64_dxgi.log
kenshi.log

Try using the latest master build. Can be downloaded here https://github.com/doitsujin/dxvk/actions/runs/9838048395
Else i would try to downgrade the driver.

Also make sure Dozen isn't installed https://github.com/doitsujin/dxvk/wiki/Windows#dozen

Alright, checked for Dozen and nope, I don't have it installed (yaay!).
Just tried the latest master build and got the same error in the Kenshi logs, the DXVK logs look the same basically, nothing has changed as far as I've seen.
Anyways, time to downgrade drivers then, or wait until this gets fixed.

Have you tried any other D3D11 games with DXVK on your setup? This doesn't sound like something that would only break one single game.
Either way, Kenshi still works on Proton.

I have not , since I don't really use DXVK that much. In fact I started
using DXVK for Kenshi (and only for Kenshi) around December 2023 due to it
being the only way to fix the armor/hair/texture flickering , which only
seems to show up if the user has an AMD GPU (which is somewhat weird , but
it seems to be related to the devs not having AMD Gpus to playtest their
game and such) and yeah it worked flawlessly , the flickering was gone and
the game ran smoothly. Anyways , yeah that's all I can really gather ,
sorry if it ain't much. Still , I'm quite inclined to believe it's the
drivers because that's the only thing that really changed since I played
the game in January this year.
El mar, 9 jul 2024 09:45, Philip Rebohle @.***>
escribió:

Have you tried any other D3D11 games with DXVK on your setup? This doesn't
sound like something that would only break one single game.
Either way, Kenshi still works on Proton.
—
Reply to this email directly, view it on GitHub
https://github.com/doitsujin/dxvk/issues/4127#issuecomment-2217613024,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BJX45XBVBGZEHVLIAVZO7JLZLPLNDAVCNFSM6AAAAABKSKENVOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJXGYYTGMBSGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

To answer your question , I have not. I don't really use DXVK for anything else.
In fact I started using DXVK + Kenshi around December 2023 to fix a very annoying texture flickering bug that only seems to appear if the user has an AMD GPU (which is weird , but it seems to be related to the devs not having AMD GPUs to playtest their game) and yeah , it worked flawlessly !
So I really don't know what could be causing this issue , but I'm quite inclined to believe it's the drivers (or something related to that) , due to them being the only thing that has changed ever since I played Kenshi + DXVK in February.

I tried installing 24.3.1 for my iGPU (rdna2) but am able to start the game fine.
I don't think it would do anything but you could try deleting shader cache in your Radeon settings.

Alright, I ended up testing 2 games using DXVK.
Hearts of Iron 4: Instantly crashed at launch (DX11) - Log files are similar to Kenshi.
GTA San Andreas: Working (DX9).
Gonna try deleting the shader cache, if not I'll reinstall the drivers or something.

Alright deleted the shader cache, nothing changed.
I DDU'd the current drivers and reinstalled them (clean-new download) and still nothing. Still getting the same logs.

Do you have HDR enabled or something? Might just be the AMD driver trying to do something with DXGI and loading ours or something, wouldn't be the first time that happened.

Yeah, don't know what's going on, I don't think this is somerthing we can fix.

Ah, damn. I might just do what I said before and roll back to a previous driver version and see if that works, hopefully it does but again it's super weird that it isn't at this moment.
Anyways, thanks a lot everyone for your help and time, I appreciate it a lot.

Okay I found something interesting (I hope).
First of all, I ended up downgrading to 3 different versions, and still got the same error every single time (using different DXVK versions)
After that I thought, "wait the event viewer should be throwing some indication about the issue that the app is having or why it is crashing". Checked it and found out that there's a module that is having an error when running the app (Kenshi): ntdll.dll
Now I am gonna go scan my PC and see if that dll got f'ed or something.

Not just you, I can't launch any game with DXVK since a Windows and NVIDIA graphics driver update today, I was running these fine yesterday.

@LordSalahuddin What happens if you use a older release like 1.10.3

Well, at least something changed, we got new errors.
kenshi_x64_dxgi.log
kenshi_x64_d3d11.log
kenshi.log

Are you able to check in Windows Event Viewer if there are any interesting errors. Look under Custom Views and then Administrative Events. You can sort by time and double click on a event to get more information.

What what i can gather a 0xc00000fd is a Stack Overflow Exception

Well, continued testing DXVK with other games, it seems I can't run DX11 games using DXVK. Tested MGSV GZ, MGSV TPP, and a couple of other games, to no avail.
Something interesting that I found is that MGSV GZ and TPP threw some more info about the error and in the event viewer section I am getting: "Exception Code: 0xc0000005" and "Faulting Module: amdvlk64.dll_unloaded" (amdvlk64.dll).
Don't know if that helps at all, hopefully it does.
MGSV TPP logs:
mgsvtpp_d3d11.log
mgsvtpp_dxgi.log

@LordSalahuddin Are you still having this issue?

@Blisto91 Okay that's quite an awesome timing, I reinstalled Kenshi a couple of nights ago and I was about (just now) to test if the issue got finally solved (be it either a Windows issue, a card related issue or whatevs).
I'll be back with a proper answer.

@Blisto91 Let's GOOO!
It's actually working now!
Was able to launch the game and get in it, will do some further testing in case something else shows up or if something happens

Yup , I ended up trying DXVK with other games and it's perfectly working now, no crashes, nothing.
I also noticed that it's working much better than before so that's a plus.


Package re-arrange: Move new aggregation related classes from operator to query

Inside pinot-core:
Move aggregation package from operator to query.
Move DataCacheBlock from aggregation to common.

Current coverage is 66.54% (diff: 100%)

No coverage report found for master at 1d8b016.

Powered by Codecov. Last update 1d8b016...523e225


Removing cells_sim from GoWin bram techmap

Answering @eddiehung reviews request, I'm fixing one of the comments:
https://github.com/YosysHQ/yosys/commit/f9272fc56d7179f04a9f776bf056eedfc33dd358#r37144384
the other one: https://github.com/YosysHQ/yosys/commit/f9272fc56d7179f04a9f776bf056eedfc33dd358#r37144371
Makes perfect sense to remove run("techmap -map +/techmap.v"); since is irrelevant, but fine synthesis seems to be replaced for map_ffram and map_gates in current head, so these lines does not exists in master anymore.

Thanks Diego! This was something I spotted working on #1682 .
Re: https://github.com/YosysHQ/yosys/commit/f9272fc56d7179f04a9f776bf056eedfc33dd358#r37144371 I think I changed it here: https://github.com/YosysHQ/yosys/pull/1682/files#diff-83149add259aef87d7424c0bd00533c0L214
Also, can you re-do your branch with just the 931a68f commit and not the previous two which seem to be no-ops?

Yeah, one of these two commits was too old. Sorry for that.


Allow iterables in mapdl.cmsel

As the title.

Mmhhh.. Now I think about it... it does not make much sense to have iterables..... because...
cmsel,s, ['cm1', 'cm2']

you cannot have:
cmsel, s, cm1
cmsel, s, cm2

However, you could have:
cmsel, s, cm1
cmsel, a, cm2

I am wondering if makes sense to overload the math operators for selections. Given:
# node selection 1
cm1 = mapdl.cm("cm1", "nodes")  # current implementation does not return anything
# node selection 2
cm2 = mapdl.cm("cm2", "nodes")

mapdl.select # imaginary function to select components

What the following operation will mean:
AND operator
What the following statement should mean:
mapdl.select(cm1 and cm2)

I guess it should mean to select both:
mapdl.cmsel("s", "cm1")
mapdl.cmsel("a", "cm2")

However, using R could make sense also:
mapdl.cmsel("s", "cm1")
mapdl.cmsel("R", "cm2")

OR operator
But then what about the or operator?
mapdl.select(cm1 or cm2)

probably here the only reasonable option will be to use A:
mapdl.cmsel("s", "cm1")
mapdl.cmsel("a", "cm2")

NOT operator
I guess this is easy, it should unselect:
mapdl.select(not cm1)

will be translated to:
mapdl.cmsel("U", "cm1")

Summary
So...

Python operator
MAPDL operation
Python example
MAPDL command

and
Reselect R
mapdl.select(cm1 and cm2)
mapdl.cmsel("S", "cm1")$mapdl.cmsel("R", "cm2")

or
Add A
mapdl.select(cm1 or cm2)
mapdl.cmsel("S", "cm1")$mapdl.cmsel("A", "cm2")

not
Unselect U
mapdl.select(not cm1)
mapdl.cmsel("U", "cm1")

Pinging @koubaa, @mcMunich, @mikerife and @pthieffry for feedback before considering it for future work.

@germa89 I much prefer the idea of logic operators than iterables. I concur with your assessment on the ambiguity iterables could introduce.


command not found: tailwindcss-extend

with Next14.5

You can not use the cli directly when not installing globally (using the -g flag).
Instead create a script inside your package json or use npx npx tailwindcss-extend.
While testing i noticed that there is a problem with the esm syntax. I´ll try to resolve that when i have more time.

Hey @fouadelhamri
have you checked out my advice?


Update helpers.html

Small text-only proposal to change 'wtf' to 'what' because that makes it more friendly to all

Eventhough I am with you on changing WTF to what, WTF actually  makes sense in certain places :)


Local Flow Run Keyboard Interrupt Does Not Cancel a Running Query

In using the current main branch version of the library and leveraging the basic example of creating a credentials and connection object, when the query execution is running a long running query and the flow run gets canceled via
Command + C, the snowflake query is not getting canceled.
snowflake_credentials = SnowflakeCredentials(
        account="account",
        user="login",
        autocommit=True,
        password=os.getenv("PRIVATE_KEY_PASSPHRASE"),
        private_key="private key string",
        role="sysadmin",
    )
    snowflake_connector = SnowflakeConnector(
        database="development",
        warehouse="compute_wh",
        schema="braun",
        credentials=snowflake_credentials,
    )
    file_counter = 0
    with snowflake_connector.get_connection() as sf:
        with sf.cursor() as cur:
            cur.execute("long running query")

I would expect this to behave the same way as using the snowflake connector directly.

Curious if you have a traceback?
Also, what if you tried using the built-in snowflake_query?


[WIP] Dev/jela/issue2999 2x

Seeing what needs to be done.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


HttpApiClient Allow for non-tagged errors / don't die on parse errors.

What is the problem this feature would solve?
We incrementally introduce effect in an existing codebase. We have an HttpApi where authorization is done on the application level (using effect code), but authentication is done by AWS by an API gateway authorizer. This authorizer can throw an 401 error that is not tagged.
Currently, when the API returns a non-tagged error (as in our case with the AWS api authorizer), there is no way to handle that error. The program dies with:
ParseError: (Unauthorized (Encoded side) <-> Unauthorized)
└─ Encoded side transformation failure
   └─ Unauthorized (Encoded side)
      └─ ["_tag"]
         └─ is missing

https://github.com/Effect-TS/effect/blob/3686ff644f57a7d8ed3a498f521cadfa70267c1e/packages/platform/src/HttpApiClient.ts#L187
Discord thread: https://discord.com/channels/795981131316985866/1098177242598756412/threads/1309819953482039356
What is the feature you are proposing to solve the problem?
 Personally I would prefer if the client never dies on its own without the possibility to change that behavior and catch/handle errors.
What alternatives have you considered?
In this case I think there are none, since a third-party system is involved where we have no control over the returned error.

Thanks to the really great community on discord, this has been resolved.
Problem origin: We had an Unauthorized error defined in our codebase as a tagged error like this
export class Unauthenticated extends S.TaggedError<Unauthenticated>()(
  "Unauthenticated",
  {},
  HttpApiSchema.annotations({ status: 401 }),
) {}

Since the error from AWS was not tagged, this led to the parse error.
Defining the error like this works:
class UnauthFromAWS extends S.Class<UnauthFromAWS>("Schema")({
  message: S.String,
}) {
  readonly _tag = "UnauthFromAWS"; // being added only on decoded side
}
api.addError(UnauthFromAWS, { status: 401 })


Merge changes from external forks

It might be a good idea to merge changes back from https://bitbucket.org/mayastudios/nbugx/commits/all and some other external repos where people did some nice refactorings.

:+1 https://github.com/soygul/NBug/network

You could also update the nuget package.

Done. Can't update NuGet as I don't use Windows any more.


Improve Text Visibility in "Personalized Recommendation at index.html"

Fixes:  #1613
Description
Improve Text Visibility in "Personalized Recommendation at index.html"
Type of PR

[x] Bug fix
[ ] Feature enhancement
[ ] Documentation update
[ ] Other (specify): _______________

Screenshots / videos (if applicable)

Checklist:

[x] I have made this change from my own.
[x] My code follows the style guidelines of this project.
[x] I have performed a self-review of my own code.
[x] My changes generate no new warnings.
[x] I have tested the changes thoroughly before submitting this pull request.
[x] I have provided relevant issue numbers and screenshots after making the changes.

please not that this commit also linked with #1614
so please assign that also

It happen just because i work on 2 issue at same time


Update Dialyzer CI Cache Steps

Dialyzer's README was updated to add common CI caching steps. I've
updated our procedure to match theirs.

Thank you @jherdman 😁


Long links break proper rendering of feed

As usual @virgile-dev breaking things as in this example when viewed in mobiles:
post with long link
Make sure to parse all links (even if inside brackets) and prevent long links from displaying in full and use '...' after a certain length.

fixed


[bug][apps][onelogin] Bug fixes for OneLogin integration app

to: @ryandeivert @jacknagz
cc: @airbnb/streamalert-maintainers
size: small
Background
New integration app was added to handle OneLogin events. During deployment we came across a couple of issues and this PR fixes them all.
Changes

Bug in the regex to validate client_secret and client_id for the OneLogin API (app_integrations/apps/onelogin.py).
Bug in debug message formatter, it was expecting number when a string was passed (app_integrations/config.py).
Bug in debug message formatter, it was expecting number when a string was passed (app_integrations/apps/app_base.py).
Bug in OneLogin app when headers were set and not returned (app_integrations/apps/onelogin.py).
Adjusted schema for OneLogin events, since returned fields and non-consistent with their online documentation and changed types to string to handle returned null values (conf/logs.json).

Testing
Tested locally and app was deployed.

Coverage increased (+0.007%) to 95.075% when pulling 061fa80ec6c39d2254ce0b1ff325ed70b0d36d11 on javier-streamalert-onelogin-fixes into 65396ade41d1d54f58eec6b35dc7f8237ede6ca7 on master.


Added UIAlertController extension

Checklist

[x] I checked the Contributing Guidelines before creating this request.
[x] New extensions are written in Swift 5.0.
[x] New extensions support iOS 10.0+ / tvOS 9.0+ / macOS 10.10+ / watchOS 2.0+, or use @available if not.
[x] I have added tests for new extensions, and they passed.
[x] All extensions have a clear comments explaining their functionality, all parameters and return type in English.
[x] All extensions are declared as public.
[x] I have added a changelog entry describing my changes.

          1 Warning

:warning:
The source files have been modified. Please consider adding a CHANGELOG entry if necessary.

          1 Message

:book:
Thank you for submitting a pull request to SwifterSwift. The team will review your submission as soon as possible.

  Generated by :no_entry_sign: Danger

Also @NickNguyeniOS14 you need to add a CHANGELOG entry.

@NickNguyeniOS14 I'm closing this for now, but feel free to reopen if you want to deal with the review change requests.


Updated contributors

Landed in https://github.com/postcss/postcss-filter-plugins/commit/85840a2026d84fa61ce049ebea596bfb08a7afba.


How will multiple characters be represented in a match?

Currently, the $.entrant1Character and $.entrant2Character properties of a Game can only be a single string. I don't believe this accounts for situations like Melee's Zelda + Sheik where a player could intentionally use multiple characters in a single game.

Zelda/Sheik is not the real problem. There are other games, like MVC, where you pick 3 characters, not just one. Making entrant1Character and entrant2Character an array instead of a string should probably do it..

In Melee's Zelda/Sheik case - that is a pretty specific thing and hard to determine, since a player can also transform between characters mid-game. I assume they'd pick Zelda since she is the actual character, but the SSBM community could come up with an agreed upon solution.
Nacho has a good example with the MVC case, and changing it to an array sounds like a good fix.

Another place where this comes up is team games, where each entrant is actually a team of e.g. 2 players. I agree changing the entrant1Character string field to an entrant1Characters array of strings is probably the best solution (unfortunately I think it sacrifices a bit of simplicity, but the flexibility seems worth it here).

addressed in https://github.com/VestboyMyst/openbracketformat/commit/d65519c47410e0fb0061e842dd829234ef85a030


The rocm links in the doc is outdated

See the ROCm and Linux link in https://iree.dev/guides/deployment-configurations/gpu-rocm/
They are https://rocm.docs.amd.com/en/latest/deploy/linux/quick_start.html and https://www.amd.com/en/graphics/servers-solutions-rocm which are all 404 errors.

We had some ROCm doc updates in https://github.com/iree-org/iree/pull/17029 (cc @nithinsubbiah ). I wanted to make a pass through those docs myself, but I'm still waiting on a local dev machine so I can go through the steps personally.

@ScottTodd I see that the docs have been updated, can we close this?

Yep.


[4.12] OCPBUGS-18417: set TLS cipher suites in Kube RBAC sidecars

https://issues.redhat.com/browse/OCPBUGS-18417

Bump library-go to get default TLS cipher suite list
OCPBUGS-18417: set TLS cipher suites in Kube RBAC sidecars

cc @openshift/storage

/label backport-risk-assessed

/lgtm

Checked ci job and passed.

/label qe-approved

/label cherry-pick-approved


Dec 2 - Build a decentralized app

Event Information

Category
Details

Reactor Topic
Emerging Technologies

Stream Topic
blockchain decentralized app

Stream Date
Dec 2, 2020

Stream Time
9am

Stream Duration
60 min

Title
Build a decentralized app

Description
Decentralized applications, or Dapps for short, are what really brings smart contracts to life. Creating these UI applications is what allows people to interact with and execute transactions with contracts. Dapps are used in everything from games to supply chain management to financial transactions. The possibilities of Dapps you can build are endless. This stream is for anyone who wants to learn more about creating apps with blockchain. Join this stream to see how to use Drizzle to build a Dapp from scratch. To best follow along, we recommend that you have a fundamental understanding about blockchain technology and the Ethereum platform.

Speaker
@meaghanlewis

Moderator

SharePoint ID
11921

Additional Resources:

Event Checklist
10 Weeks Prior

[x] Reactor Content Team (RCT) or Speaker opens a new issue for an upcoming stream filling in the Event Information table. Both RCT and Speaker are marked as assignees.
[x] RCT and Speaker discuss details of the event in the comments of this issue. RCT adds a confirmed-event label and global-twitch-event tag to the issue and adds event to the Global Live Streams project. Issue will appear in the Upcoming Streams column
[x] Speaker adds a ready-for-marketing-edit label so the RCT can review title and description

8 Weeks Prior

[x] RCT does a review of title and description and removes the ready-for-marketing-edit label
[x] RCT moves the issue to the Ready for SharePoint column
[x] RCT informs the Reactor Marketing Team of the new event information
[x] RCT provides speaker with assets (e.g. slides, overlays) and the survey data for the event
[x] RCT moves the issue to the MONTH Streams Prep column (according to the month it will be streamed in)

2 Weeks Prior (Done in /microsoft/Reactors)

[ ] Speaker opens a PR with the new content for the stream on the customer-facing Reactor repository and adds the content-development and global-twitch-event tag to the PR.
[ ] Speaker adds to the same PR a modification to the online-event-resources directory to include their stream information.
[ ] Speaker adds the RCT assigned to the issue as the reviewer when it is ready for review/merge
[ ] RCT reviews, approves, and merges the changes

1 Week Prior

[ ] Speaker and Moderator test setup for streaming (instructions coming soon)
[ ] RCT checks in with the speaker and moves the issue to the Ready to Stream column

During and After Stream

[ ] Speaker and Moderator run the stream
[ ] RCT submits recording to be uploaded to the Reactor YouTube and to be made available on LearnTV
[ ] RCT moves issue to the Stream Complete column

@meaghanlewis  - what do you think of this?
Decentralized applications, or Dapps for short, are what really brings smart contracts to life. Creating these UI applications is what allows people to interact with and execute contracts. Dapps are used in everything from games to supply chain management to cross-border financial transactions. The possibilities are endless with this amazing tool. This stream is for [insert the intended audience]. Join this stream to learn about the popular tools to build Dapps, and walk through the steps to build a Dapp from scratch.
To best follow along, we recommend that you ...[insert pre-reqs]

@mebaumb I added edits inline to your comment above. thanks!

Looks great to me! Do you want me to publish?
Also is there any links that you want to share? Like to github or anything?

@mebaumb this looks good! no links to add at this time.

@meaghanlewis  - great! I will get it published! :)

This event has run, stream data has been recorded.

Hi, where can I find the code you copy-pasted during the video for the Shipment.sol and ShipComponent.js files? Thank you!

@bumbdy you can find that code here: https://github.com/microsoft/Reactors/blob/main/workshop-resources/emerging-tech/Blockchain_2/creating_decentralized_apps/create-a-dapp-for-shipping.md


Disk Read / write spam 100% disk usage

To the left the blue bar shows when i closed ray
i have no idea how to reproduce but Ray has been spamming my disk for the past hour
It's happened a few times before but i am unsure how to reproduce, usually it happens after my mac goes to sleep and then wakes up after a few hours to continue work (think go home at 16:00 and start work at 8:00)
My usual fix is just to quit ray and restart it but it would be helpful if the app didn't screw up my SSD health, since SSD's only have a max number of writes, it's pretty annoying that an app can cause 100% disk writes
As shown on the image Ray managed to write 4,5 TB of data in the last 3 hours...
while it isn't obvious from the screenshot it's Ray, i assure you it was showing up in the tab as the top contender for writing to disk, i then promptly shut it down and took the screenshot
I am unsure what/why Ray needs to write to the disk at all? could it not just be in memory? ( imo it's rare to have the need to reopen ray at a later stage and see past dumbs )

Same issue on Ubuntu 24.04.1

I am experiencing the same issue. I am only using Ray with a remote SSH server.
I code on a macbook pro i9 , version 13.5
The ssh remote machine is a Ubuntu 22.04.5 LTS
Ray : Version 2.8.1 (2.8.1)
Occasionally (roughly every two days), Ray spikes to 100% CPU usage on a single core without any apparent reason. I also put my laptop into sleep mode when I travel.

I'm getting this too, on Windows.

Also experiencing this on Windows 11 Pro 23H2 with a remote SSH server connection to an Ubuntu VM. High disk usage remains after disconnecting from the server and stops when I close Ray. I put the laptop in sleep/hibernate mode - will test this to see if this is causing the issue.  I'll also test whether this happens when connected/disconnected, sleeping/not-sleeping.

I just bought the lifetime license and noticed the same issue on Windows 11. I'm only using Ray with a remote SSH server. Is there a fix in the works? Otherwise I'll see if I can get a refund.

Apologies for the late response to this issue, as this issue has been here for some time without any response from our side. The issues you are having with Ray is not the experience we aim to deliver. We understand the frustration around the performance of Ray and it's definitely something we are focusing on. At the moment we are working towards Ray version 3.0. Which contains a full refactor of the application from the ground up. It will have new look and a better user experience. The performance of the application is, as we are working towards the 3.0 release, mandatory and something we are keeping an eye on. We aim to improve on it in the next major release. We'll communicate through our channels when the next version will be ready for launch! Thank you all for your patience concerning this issue.


Add Windows support

Support should be added for running pretty much all of the linters in Windows.
I am working on this now. I initially tried writing a Windows variant of the stdin-wrapper as a Batch script, but it didn't go so well, as Batch is pretty awful. My plan now is to write the wrapper in D, and include a portable .exe file for Windows in this repo. After that is done, there will be some further adjustments to make, around dealing with strange Windows shell escaping issues.

I spend a few hours tonight working on a D program for this, and it seem to basically work with some limited amount of testing. I'll see if I can finish this off tomorrow night.

I have added a wrapper program to the repository now for Windows. Users who clone the repo on Windows should just receive a portable executable ALE will pick up on and use to run some linters, like the Haskell linter, csslint, etc.
Are there any Windows users out there who would like to test this? I performed only quite limited testing myself.

After some back and forth with this, and some testing for issue #39, I believe I can safely say that WIndows support works now.


Serialization on the WASM side?

Hi, I've been looking for a library exactly like yours - thank you for making it!
However, as I understand it, it can only be accessed from Typst code. The plugin code that will be compiled to WASM also needs to serialize and deserialize between the objects and the byte arrays.
Can you give me some advice on how to do that?

Hi alexanderkoller
This primary goal of project is to show the great ability of Typst. To conveniently interact with Typst, WASM can communicate in cbor, json,toml,yaml,xml and other format. Actually, Typst has these (APIs)[https://typst.app/docs/reference/data-loading/cbor/] to serialize and deserialize objects.
To make it simple, you can assume cbor as the 'official' language of WASM and typst, and typst code as wrapper to send parameters and receive results in cbor format. You can write Rust code to deserialize the parameters and serialize the results in cbor.(Rust is the most convenient language to implement your ideas and the Typst wasm plugin project support Rust the best ).
I developed a lib called vist that can deal with image in Typst but I haven't release it due to my tight schedule. I will release it soon and you can read it. Maybe it's the better practice you know to write Typst wasm plugin.

Thank you for the quick response!
If the point of yats is to illustrate that one can implement serialization and deserialization within Typst, might I suggest to clarify in the README that it is not intended to facilitate interaction between wasm and Typst, as it currently suggests? This might make it easier for future readers to understand what yast is and is not.

OK, I will add some infos to clarify my point.


feat: add domoritz/arrow-tools/json2parquet

domoritz/arrow-tools/json2parquet: A collection of handy CLI tools to convert CSV and JSON to Apache Arrow and Parquet
$ aqua g -i domoritz/arrow-tools/json2parquet

How to confirm if this package works well
Reviewers aren't necessarily familiar with this package, so please describe how to confirm if this package works well.
Please confirm if this package works well yourself as much as possible.
Command and output
$ json2parquet --help
Usage: json2parquet [OPTIONS] <JSON> <PARQUET>

Arguments:
  <JSON>     Input JSON file
  <PARQUET>  Output file

Options:
  -s, --schema-file <SCHEMA_FILE>
          File with Arrow schema in JSON format
      --max-read-records <MAX_READ_RECORDS>
          The number of records to infer the schema from. All rows if not present. Setting max-read-records to zero will stop schema inference and all columns will be string typed
  -c, --compression <COMPRESSION>
          Set the compression [possible values: uncompressed, snappy, gzip, lzo, brotli, lz4, zstd, lz4-raw]
  -e, --encoding <ENCODING>
          Sets encoding for any column [possible values: plain, rle, bit-packed, delta-binary-packed, delta-length-byte-array, delta-byte-array, rle-dictionary]
      --data-pagesize-limit <DATA_PAGESIZE_LIMIT>
          Sets data page size limit
      --dictionary-pagesize-limit <DICTIONARY_PAGESIZE_LIMIT>
          Sets dictionary page size limit
      --write-batch-size <WRITE_BATCH_SIZE>
          Sets write batch size
      --max-row-group-size <MAX_ROW_GROUP_SIZE>
          Sets max size for a row group
      --created-by <CREATED_BY>
          Sets "created by" property
      --dictionary
          Sets flag to enable/disable dictionary encoding for any column
      --statistics <STATISTICS>
          Sets flag to enable/disable statistics for any column [possible values: none, chunk, page]
      --max-statistics-size <MAX_STATISTICS_SIZE>
          Sets max statistics size for any column. Applicable only if statistics are enabled
  -p, --print-schema
          Print the schema to stderr
  -n, --dry
          Only print the schema
  -h, --help
          Print help
  -V, --version
          Print version

Thanks!

Released. https://github.com/aquaproj/aqua-registry/releases/tag/v3.129.0


Feat/initial

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


skypeforlinux hash mismatch

Issue description
skypeforlinux doesn't build:

output path ‘/nix/store/xpd37szphzwvryjghp2z4kg7bjgvgmqz-skypeforlinux-64.deb’ has sha256 hash ‘1dwyj5wm2amkysbnzxsskq6sl7rbqggm6n4sabnq7wd5xnbq4i06’ when ‘18v861x0n2q2jaglap8193sia476dwkwr0ccfzl29mi5ijma24ml’ was expected

Steps to reproduce
nix-build -A skypeforlinux
Technical details

System: 17.09.git.d282d6b (Hummingbird)
Nix version: nix-env (Nix) 1.11.8
Nixpkgs version: 17.09.git.7746327080M
Sandboxing enabled: No

cc @PanAeon

Oh snap. It is not a stable url:
      fetchurl {
        url = "https://repo.skype.com/latest/skypeforlinux-64.deb";
        sha256 = "18v861x0n2q2jaglap8193sia476dwkwr0ccfzl29mi5ijma24ml";
      }

We need a more stable mirror here. Otherwise it will always break.

Should be taken from here: https://repo.skype.com/deb/pool/main/s/skypeforlinux/

Thank you for fixing this, works for me now.


Cannot Click

The Dump button is behind the gigantic log console and cannot be clicked.

This is most likely the issue if you don't have the dumper window maximized (min 1920x1080). However thanks for reporting this issue, i will allow log window resizing in the future for smaller window dimensions

however for a temporary fix change in file
https://github.com/Spuckwaffel/UEDumper/blob/master/UEDumper/Frontend/Windows/LogWindow.cpp
in the function windows::LogWindow::render
at ImGui::SetCursorPosY(ImGui::GetWindowSize().y - 310);
the number 310 with anything smaller (like 200) to make the log window smaller.
Keep in mind that i currently don’t know which impact it will have on the layout of other windows

This will be fixed once the development branch is pushed into the main branch. The development branch has this feature now in testing mode.

#9 fixed this issue


[SUPPORT] Hudi Clean and Delta commits taking ~50 mins to finish frequently

Tips before filing an issue

Have you gone through our FAQs?

Join the mailing list to engage in conversations and get faster support at<EMAIL_ADDRESS>

If you have triaged this as a bug, then file an issue directly.

Describe the problem you faced
We have a Hudi table with metadata enabled and using delta streamer, async clean, async compact services . Delta commit and clean operations are taking ~50 minutes frequently.
A clear and concise description of the problem.
To Reproduce
Steps to reproduce the behavior:

Run 0.12.1 version Hudi with metadata table enabled.
2.Enable async compaction and cleaner services.

use the below configuration.
hoodie.cleaner.policy=KEEP_LATEST_COMMITS
hoodie.clean.automatic=true
hoodie.clean.async=true
hoodie.cleaner.commits.retained=5
hoodie.keep.min.commits=10
#compaction config
hoodie.datasource.compaction.async.enable=true
hoodie.parquet.small.file.limit=1048576
hoodie.compaction.target.io=50
hoodie.metadata.metrics.enable=true
hoodie.metadata.index.bloom.filter.enable=false
hoodie.metadata.index.column.stats.enable=false
hoodie.write.concurrency.mode=optimistic_concurrency_control
hoodie.cleaner.policy.failed.writes=LAZY
hoodie.write.lock.provider=org.apache.hudi.client.transaction.lock.InProcessLockProvider
hoodie.write.lock.wait_time_ms=300000

Expected behavior
Delta commit and clean actions should not take longer times.
A clear and concise description of what you expected to happen.
Environment Description

Hudi version : 0.12.1

Spark version : 3.2.1

Hive version : 2.3.5

Hadoop version : 2.7.7

Storage (HDFS/S3/GCS..) : GCS

Running on Docker? (yes/no) : yes

Additional context
Add any other context about the problem here.
Delta streamer runs in continuous mode.
Adding the screenshot of timeline of operations

Below is the only error I see in logs.
Stacktrace
 RequestHandler: Bad request response due to client view behind server view. Last known instant from client was<PHONE_NUMBER>3021745 but server has the following timeline [[20221128033016359__rollback__COMPLETED], [20221128042615784__rollback__COMPLETED], [20221128052249948__rollback__COMPLETED], [20221128100542977__rollback__COMPLETED], [20221128114411534__rollback__COMPLETED], [20221128121237952__rollback__COMPLETED], [20221128121547373__rollback__COMPLETED], [20221128124007294__rollback__COMPLETED], [20221128130510784__rollback__COMPLETED], [20221128150135765__rollback__COMPLETED], [20221202082857955__rollback__COMPLETED], [20221202083358380__rollback__COMPLETED], [20221205180609234__rollback__COMPLETED], [20221213024840399__rollback__COMPLETED], [20221215121336002__rollback__COMPLETED], [20230103075416732__clean__COMPLETED], [20230103080003681__clean__COMPLETED], [20230103080537813__clean__COMPLETED], [20230103081110194__clean__COMPLETED], [20230103081642791__clean__COMPLETED], [20230103082158513__clean__COMPLETED], [20230103082749103__clean__COMPLETED], [20230103083327661__clean__COMPLETED], [20230103083915577__clean__COMPLETED], [20230103084450294__clean__COMPLETED], [20230103085022170__clean__COMPLETED], [20230103085539296__deltacommit__COMPLETED], [20230103085550414__clean__COMPLETED], [20230103090129353__deltacommit__COMPLETED], [20230103090140117__clean__COMPLETED], [20230103090705599__deltacommit__COMPLETED], [20230103090716308__clean__COMPLETED], [20230103091245975__deltacommit__COMPLETED], [20230103091256846__clean__COMPLETED], [20230103091825253__deltacommit__COMPLETED], [20230103091836101__clean__COMPLETED], [20230103092403683__deltacommit__COMPLETED], [20230103092414824__clean__COMPLETED], [20230103092828723__commit__COMPLETED], [20230103092851264__clean__COMPLETED], [20230103092923310__deltacommit__COMPLETED], [20230103093158260__clean__COMPLETED], [20230103102048896__deltacommit__COMPLETED], [20230103102100480__clean__COMPLETED], [20230103102637434__deltacommit__COMPLETED], [20230103102648856__clean__COMPLETED], [20230103103218354__deltacommit__COMPLETED], [20230103103229738__clean__COMPLETED], [20230103103812033__deltacommit__COMPLETED], [20230103103823381__clean__COMPLETED], [20230103104351306__deltacommit__COMPLETED], [20230103104402684__clean__COMPLETED], [20230103104950491__deltacommit__COMPLETED], [20230103105002062__clean__COMPLETED], [20230103105541444__deltacommit__COMPLETED], [20230103105552964__clean__COMPLETED], [20230103110154035__deltacommit__COMPLETED], [20230103110205541__clean__COMPLETED], [20230103110749857__deltacommit__COMPLETED], [20230103110801657__clean__COMPLETED], [20230103111344582__deltacommit__COMPLETED], [20230103111356019__clean__COMPLETED], [20230103111912226__deltacommit__COMPLETED], [20230103111923380__clean__COMPLETED], [20230103112519397__deltacommit__COMPLETED], [20230103112531041__clean__COMPLETED], [20230103113021745__commit__COMPLETED], [20230103113045783__clean__COMPLETED]]

Hi @BalaMahesh Thanks for raising the issue.  To better triage this, could you provide more details about the Hudi table, partitioned or non-partitioned table, how many partitions if partitioned, Spark driver logs, and screenshots of the stages which take a long time to finish?

This is a non-partitioned table with minimum file size set to 1 MB and ~150 parquet files are created.  Below are the screenshots from spark web ui.

I am adding the logs between 23/01/04 03:48:51  and 23/01/04 04:41:25 - which took longer duration for delta commit.
hudi_logs.txt

@yihua - did you get chance to check this ?

@BalaMahesh DId you try with the bloomfilter index metadata disabled ?

I have changed the index type to simple and then restarted the application.

I guess we run into some performance issue when using BloomFilter index for mor table with metadata table disabled, thanks for the feedback, let me record this issue first for this on-call time and have a discussion on the meeting

Same issue faced here, but we use Spark to append MOR tables with async cleaning.
A lot of warning messages came into log file, any good ideas more ?

We were running with
hoodie.metadata.index.bloom.filter.enable=false hoodie.metadata.index.column.stats.enable=false
I hope that answers your question. We have set this false because, I have run into this issue when set to true. #7657
I have changed the index type to simple and then restarted the application.
Index look up duration has come down and uniform now.
delta commit durations are uniform too except for the issue I mentioned here #7364. After the restart delta commit gets stuck and then later progresses.

@BalaMahesh  Hello, BalaMahesh, we met same issue here, I have two questions here, hope you could have chance to response. Thanks in advance !

how to find charts of "Index lookup duration" ?
simple is the default index type on Spark engine, and we are using simple index type on our Custom Spark job, seems simple index type is not the key solution. do you have any more updates ?

Thanks in advance again !

We were running with
hoodie.metadata.index.bloom.filter.enable=false hoodie.metadata.index.column.stats.enable=false
I hope that answers your question. We have set this false because, I have run into this issue when set to true. #7657
I have changed the index type to simple and then restarted the application.
Index look up duration has come down and uniform now.
delta commit durations are uniform too except for the issue I mentioned here #7364. After the restart delta commit gets stuck and then later progresses.

@BalaMahesh Hello, BalaMahesh, we met same issue here, I have two questions here, hope you could have chance to response. Thanks in advance !

how to find charts of "Index lookup duration" ?
simple is the default index type on Spark engine, and we are using simple index type on our Custom Spark job, seems simple index type is not the key solution. do you have any more updates ?

Thanks in advance again !

You have to push metrics to either Prometheus push gateway or any other monitoring solution for plotting these charts.
You can see the spark stages and jobs in the spark web ui to identify which task is taking long.

We were running with
hoodie.metadata.index.bloom.filter.enable=false hoodie.metadata.index.column.stats.enable=false
I hope that answers your question. We have set this false because, I have run into this issue when set to true. #7657
I have changed the index type to simple and then restarted the application.
Index look up duration has come down and uniform now.
delta commit durations are uniform too except for the issue I mentioned here #7364. After the restart delta commit gets stuck and then later progresses.

@BalaMahesh Hello, BalaMahesh, we met same issue here, I have two questions here, hope you could have chance to response. Thanks in advance !

how to find charts of "Index lookup duration" ?
simple is the default index type on Spark engine, and we are using simple index type on our Custom Spark job, seems simple index type is not the key solution. do you have any more updates ?

Thanks in advance again !

You have to push metrics to either Prometheus push gateway or any other monitoring solution for plotting these charts.
You can see the spark stages and jobs in the spark web ui to identify which task is taking long.

Got it! Thanks a lot !!!


Add Running status

Signed-off-by: Kevin Cormier<EMAIL_ADDRESS>To be used for status of "hot" clusters in a cluster pool. (spec.runningCount)

/cc @Randy424

/cc @ellajuengst


Hope to add the function of importing pictures from the clipboard

Is your feature request related to a problem? Please describe.
Describe the solution you'd like
When adding pictures, in addition to using the file selector, I would like to add a function to import clipboard pictures.
In this way, you can copy a picture when browsing in other applications, and then import it directly from the clipboard when you return to ImageToolbox. The operation will be more convenient.
Describe alternatives you've considered

added


Make query normalization use same variable for same constants

This is needed to make select-or-insert work when using constants,
since otherwise this hides the equality of constants from the
compiler.
Work on #684.

Closing this per redesign in #1639 making this not necessary for now


cp -U unknown

But native cp works just fine.

This is from the OMVS cp man  page:

I don't know if there are other differences from the standard cp.

Another part of the OMVS cp manpage:

When copying records, the string " \n" is copied the same way as the string
"\n": both are read back as "\n", where "\n" indicates that z/OS XL C++ will
write a record containing a single blank to the file (the default behavior of
z/OS XL C/C++). All other blanks in your output are read back as blanks, and any
empty (zero-length) records are ignored on input. However, if the environment
variable _EDC_ZERO_RECLEN is set to Y before cp is called, an empty record is
treated as a single newline character and is not ignored. Also, if
_EDC_ZERO_RECLEN is set to Y, a single newline character is written to the file
as an empty record, and a single blank will be represented by " \n".

More:
You can copy:

*  One file to another file in the working directory.
*  One file to a new file on another directory.
*  A set of directories and files to another place in your file system.
*  A UNIX file to an MVS data set.
*  An MVS data set to a file system.
*  An MVS data set to an MVS data set.

Perhaps consider not including cp in your ported tools.

@lbdyck is this still broken with our change to 'fail over' to /bin/cp if a dataset is specified?


⚠ Bofrost.fr has degraded performance

In 50f9d12, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 847 ms

Resolved: Bofrost.fr performance has improved in 89a6283 after 9 minutes.


Update README.md

Address issues of https://github.com/SuzanneSoy/SearchBar/issues/1#issuecomment-1055626952 in PR #3
 (this image is used on the README page. Please don't delete it from this ticket.)

PR merged, thanks a lot :)


Creating CircleCI workflow and jobs to build/deploy to S3

This PR wasn't updating with new commits, superseding it with a new PR: https://github.com/book-a-desk/book-a-desk-ui/pull/13


[Feature Request] resuming an algorithm after termination

This feature is particularly important for checkpointing and resuming long-running jobs. I wonder whether this feature already exists but it has slipped my attention?

It does not exist directly and I did not have any feature request regarding that yet.
A simply fix is to use the same algorithm object, but provide the final population as the initial population.
from pymoo.algorithms.nsga2 import NSGA2
from pymoo.factory import ZDT1
from pymoo.factory import get_sampling, get_crossover, get_mutation
from pymoo.optimize import minimize

algorithm = NSGA2(
    pop_size=40,
    n_offsprings=10,
    sampling=get_sampling("real_random"),
    crossover=get_crossover("real_sbx", prob=0.9, eta=15),
    mutation=get_mutation("real_pm", eta=20),
    eliminate_duplicates=True
)

problem = ZDT1()

res = minimize(problem,
               algorithm,
               ('n_gen', 40),
               seed=1,
               pf=problem.pareto_front(use_cache=False),
               save_history=True,
               verbose=True)

algorithm.sampling = res.algorithm.pop

res = minimize(problem,
               algorithm,
               ('n_gen', 20),
               seed=1,
               pf=problem.pareto_front(use_cache=False),
               save_history=True,
               verbose=True)

Does that work for you?

Thank you very much for your quick reply Julian! I realized the solution a few minutes ago once I took a deeper dive into the API. I came here to post the solution and close the issue but you already did it :) thanks again!


add short name mcl for managedCluster

Signed-off-by: Zhiwei Yin<EMAIL_ADDRESS>story:  https://github.com/open-cluster-management/backlog/issues/12424

/assign @qiujian16

/lgtm
will need opinion from David on this short name.
/assign @deads2k

Rather than one at a time, can you make a list of the APIs in this repo, indicate which ones you think deserve a shortname, and what that shortname will be?
I'm trying to decide how well the pattern holds up if we decide that manageclustersets or managedclustersetbindings need short name: mcls?  I think the plural appearance makes it hard to reason about.  mcsets? mclsets? (do we even need a shortname for these?

@qiujian16 @deads2k  please review the short names of APIs.
A simple short name pattern for the name beginning with cluster/managedcluster/placement:

cluster -- cl
managedcluster -- mcl
placement -- pl
clusterXXX/managedclusterXXX/placementXXX -- cl/mcl/plXXX

the short name lists:

API
singular
plural

clustermanagementaddons.addon.open-cluster-management.io
clmaddon
clmaddons

managedclusteraddons.addon.open-cluster-management.io
mcladdon
mcladdons

managedclusters.cluster.open-cluster-management.io
mcl
mcls

managedclustersets.cluster.open-cluster-management.io
mclset
mclsets

managedclustersetbindings.cluster.open-cluster-management.io
mclsetbinding
mclsetbindings

clusterclaims.cluster.open-cluster-management.io
clclaim
clclaims

placements.cluster.open-cluster-management.io
pl
pls

placementdecisions.cluster.open-cluster-management.io
pldecision
pldecisions

klusterlets.operator.open-cluster-management.io
kl
kls

clustermanagers.operator.open-cluster-management.io
clmgr
clmgr

manifestworks.work.open-cluster-management.io
mwork
mworks

appliedmanifestworks.work.open-cluster-management.io
\
\

ignore appliedmanifestworks since it is rarely used by users via terminal.

Ok, thanks for writing them all out, it helps to see where we could go and extend the pattern.  The clmaddon and mcladdon are muddy distinctions when abbreviated, I think I would skip those.  I think I'm -1 on kl and mwork given a length savings to legibility ratio.
Based on this list, I'm good to start with all the mcl* names.  I think I would hold off on cl* (it's not that many characters saved).

thanks for the comments from @deads2k . let's start with the mcl* .
A simple short name pattern for the name beginning with managedcluster:

managedcluster -- mcl
managedcluster*- mcl*

the given short name lists:

API
singular
plural

managedclusters.cluster.open-cluster-management.io
mcl
mcls

managedclustersets.cluster.open-cluster-management.io
mclset
mclsets

managedclustersetbindings.cluster.open-cluster-management.io
mclsetbinding
mclsetbindings

will give short name to the other APIs if have better options in the future.

/approve

/lgtm


How do I customize the Fixture used by the XUnit AutoDataAttribute?

See Title, I'm using AutoFixture to simply generate numbers, and it's working well, but I have a custom number type Half that I want to essentially be the same as float just for 16 bytes.
I can't find anything on how to customize the AutoDataAttribute Fixture though.

What you should do in this case is to create a class inheriting from AutoDataAttribute and use the constructor that accepts a Func<IFixture>.
Here is an example
public class MyAutoDataAttribute : AutoDataAttribute
{
    public MyAutoDataAttribute() : base(CreateFixture) { }

    private static IFixture CreateFixture()
    {
        var fixture = new Fixture();

        // your customizations here

        return fixture
    }
}

Then you proceed by decorating your tests with this new attribute.
Here I am using the equivalent pattern for NUnit 3, hopefully it helps :)


x/tools/go/analysis/cmd/vet: reporting "unicode.Range32 composite literal uses unkeyed fields", but not for unicode.Range16

What version of Go are you using (go version)?

$ go version
go version go1.12.5 darwin/amd64

Does this issue reproduce with the latest release?
Yes. 1.12.5 is the latest release available for macOS on golang.org/dl/.
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/comatoast/Library/Caches/go-build"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/comatoast/Projects/Go"
GOPROXY=""
GORACE=""
GOROOT="/usr/local/go"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/darwin_amd64"
GCCGO="gccgo"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD="/Users/comatoast/Projects/quote-educator/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/wy/3sprnnbj2yx9h60jbs4qjvpr0000gn/T/go-build895608949=/tmp/go-build -gno-record-gcc-switches -fno-common"

What did you do?

I used struct literals without keys. go vet doesn't complain when it sees unicode.Range16{0xfdd0, 0xfdef, 1}, but complains when it sees unicode.Range32{0x1fffe, 0x1ffff, 1}.
Minimized test case: https://play.golang.org/p/atnHOc10YRs
Semi-minimized real-world example: https://play.golang.org/p/VzaW9okIUic
What did you expect to see?
No go vet errors. Or, now that I've researched a bit into how go vet should work, errors for using unicode.Range16 like this, too.
What did you see instead?
go vet errors on lines like unicode.Range32{0x1fffe, 0x1ffff, 1}. After seeing the discussion on #6820 I'm not sure why unicode.Range16 is fine but unicode.Range32 is warning-worthy.

I've submitted a CL for this: https://go-review.googlesource.com/c/tools/+/180922

Thank you for this report @adiabatic and for working on the fix @letientai299!
Since this cmd/vet is now under x/tools/go/analysis/cmd/vet  https://github.com/golang/tools/tree/master/go/analysis/cmd/vet we can put this under the Unreleased milestone and it can get in at anytime.


Does not work in Laravel 10

When I've tryed install in my Laravel 10 app, my shell console returns:
$ sail composer require ryoluo/sail-ssl --dev
Info from https://repo.packagist.org: #StandWithUkraine
./composer.json has been updated
Running composer update ryoluo/sail-ssl
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires ryoluo/sail-ssl * -> satisfiable by ryoluo/sail-ssl[v1.0.0, ..., v1.1.1].
    - ryoluo/sail-ssl[v1.0.0, ..., v1.1.1] require illuminate/console ^8.0|^9.0 -> found illuminate/console[v8.0.0, ..., v8.83.27, v9.0.0, ..., v9.52.0] but these were not loaded, likely because it conflicts with another require.

You can also try re-running composer require with an explicit version constraint, e.g. "composer require ryoluo/sail-ssl:*" to figure out if any version is installable, or "composer require ryoluo/sail-ssl:^2.1" if you know which you need.

Installation failed, reverting ./composer.json and ./composer.lock to their original content.

I have made Pull Request to add support for Laravel 10 - https://github.com/ryoluo/sail-ssl/pull/8

I've just released v1.2.0 that is compatible with Laravel 10.
Thank you very much @israelcena san and @janar153 san

Thank you for release v1.2.0 @ryoluo


Don't fail if the PSK identity doesn't match

In 1.1.0 s_server if the PSK identity doesn't match what we have then
a warning is printed and we continue the connection anyway. In 1.1.1,
if TLSv1.3 is used and the identity doesn't match then we abort the
connection. We should really be consistent with the old behaviour.

Checklist

[ ] documentation is added or updated
[ ] tests are added or updated

There is some guidance in the TLS 1.3 spec on this topic; let me pull it up.

This got pushed. Closing.


Uifeatures 1.1.0.m1

You did it @dinakarmeda!
Thank you for signing the Anthem Opensource Software CLA.


Release version 2.1.0

Before submitting (must do checklist)

[x] Did you read the contribution guide?
[ ] Did you update the docs? We use Numpy format for all the methods and classes.
[ ] Did you write any new necessary tests?
[x] Did you update the CHANGELOG?

Proposed Changes

Closing issues

Codecov Report

Merging #1303 (6b6d79c) into master (99782c8) will not change coverage.
The diff coverage is n/a.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@          Coverage Diff           @@
##           master   #1303   +/-   ##
======================================
  Coverage    7.09%   7.09%
======================================
  Files         193     193
  Lines       11745   11745
======================================
  Hits          833     833
  Misses      10912   10912

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


SmartLedsAdapter::new does not have async impl for Rmt::new_async?

Mentioned in esp-rs matrix and here too, flagging it here:
error[E0277]: the trait bound `esp_hal::rmt::ChannelCreator<Async, 0>: TxChannelCreator<'_, _, _>` is not satisfied
  --> src/main.rs:27:37
   |
27 |     let led = SmartLedsAdapter::new(rmt.channel0, io.pins.gpio38, rmt_buffer, &clocks);
   |               --------------------- ^^^^^^^^^^^^ the trait `TxChannelCreator<'_, _, _>` is not implemented for `esp_hal::rmt::ChannelCreator<Async, 0>`
   |               |
   |               required by a bound introduced by this call
   |
   = help: the following other types implement trait `TxChannelCreator<'d, T, P>`:
             <esp_hal::rmt::ChannelCreator<Blocking, 0> as TxChannelCreator<'d, esp_hal::rmt::Channel<Blocking, 0>, P>>
             <esp_hal::rmt::ChannelCreator<Blocking, 1> as TxChannelCreator<'d, esp_hal::rmt::Channel<Blocking, 1>, P>>
             <esp_hal::rmt::ChannelCreator<Blocking, 2> as TxChannelCreator<'d, esp_hal::rmt::Channel<Blocking, 2>, P>>
             <esp_hal::rmt::ChannelCreator<Blocking, 3> as TxChannelCreator<'d, esp_hal::rmt::Channel<Blocking, 3>, P>>

I somehow missed that on Matrix.
There is no async-version of smart_leds_trait AFAIK but probably we can just implement an async-write on SmartLedsAdapter

Thanks! Perhaps worth opening another issue/discussion although applies to this case too:
What do you think about the use of ::new() builder for both blocking and async? As mentioned over matrix:

Regarding blocking vs async ::new() methods in esp_hal, I've observed that there's I2s::new() which is is async (when feature-gated w/ async), but then there's Uart::new_async_with_config and Rmt::new_async() (instead of just using ::new() for both modes like in the I2s case).
I personally like ::new() for both blocking and async if possible, so if I have to implement SmartLedsAdapter's new async builder method?:
SmartLedsAdapterAsync::new()
SmartLedsAdapter::new()
SmartLedsAdapter::new_async()

Is it worth making this uniform across peripherals in esp-hal or is it too painful of a breaking change at this point?
/cc @MabezDev

Seeing as the SmartLedsAdapter struct itself doesn't provide the async-ness, but the rmt channel does. It makes sense to just have a single new() function, then the write method can be conditionally async or blocking depending on what the rmt channel's config is.
(Though one could argue that since this struct's sole purpose was to provide an adapter for smart_leds, maybe it shouldn't have an async variant without an upstream trait, but no reason to be strict I guess)

Is it worth making this uniform across peripherals in esp-hal or is it too painful of a breaking change at this point?

This could probably be done for the drivers that mandate DMA, as the async mode could be inferred from the dma channel as well. (Personally I'd say it's too soon as the DMA based apis aren't mature enough)

Thanks for the comments and ideas!

Seeing as the SmartLedsAdapter struct itself doesn't provide the async-ness

Indeed, that Rmt struct member, Option<TX>, pointing to pub trait TxChannel: private::TxChannelInternal<crate::Blocking> does seem to seal the deal on blocking, unfortunately :_/

(...) then the write method can be conditionally async or blocking

I'm not sure if limiting the async-ness to just the write method as @Dominaezzz suggests would help for too long since the RX side would eventually need async as well (for other applications or even for, say, RMT async-driven RX code for photosensors (or LEDs being used as photosensors :P)?
For now I'm being cheeky, breaking stuff locally, patching and defaulting to async for write (don't know if the #cfg's/conditionals/gating needed here would be accepted as "clean"?):
on smartleds-esp-hal:
diff --git a/esp-hal-smartled/src/lib.rs b/esp-hal-smartled/src/lib.rs
index 98164779..86a91249 100644
--- a/esp-hal-smartled/src/lib.rs
+++ b/esp-hal-smartled/src/lib.rs
@@ -30,7 +30,7 @@ use esp_hal::{
     clock::Clocks,
     gpio::OutputPin,
     peripheral::Peripheral,
-    rmt::{Error as RmtError, PulseCode, TxChannel, TxChannelConfig, TxChannelCreator},
+    rmt::{asynch::TxChannelAsync, Error as RmtError, PulseCode, TxChannelConfig, TxChannelCreatorAsync},
 };
 use smart_leds_trait::{SmartLedsWrite, RGB8};

@@ -73,7 +73,7 @@ macro_rules! smartLedBuffer {
 /// interaction functionality using the `smart-leds` crate
 pub struct SmartLedsAdapter<TX, const BUFFER_SIZE: usize>
 where
-    TX: TxChannel,
+    TX: TxChannelAsync,
 {
     channel: Option<TX>,
     rmt_buffer: [u32; BUFFER_SIZE],
@@ -82,7 +82,7 @@ where

 impl<'d, TX, const BUFFER_SIZE: usize> SmartLedsAdapter<TX, BUFFER_SIZE>
 where
-    TX: TxChannel,
+    TX: TxChannelAsync,
 {
     /// Create a new adapter object that drives the pin using the RMT channel.
     pub fn new<C, O>(
@@ -93,7 +93,7 @@ where
     ) -> SmartLedsAdapter<TX, BUFFER_SIZE>
     where
         O: OutputPin + 'd,
-        C: TxChannelCreator<'d, TX, O>,
+        C: TxChannelCreatorAsync<'d, TX, O>,
     {
         let config = TxChannelConfig {
             clk_divider: 1,
@@ -160,7 +160,7 @@ where

 impl<TX, const BUFFER_SIZE: usize> SmartLedsWrite for SmartLedsAdapter<TX, BUFFER_SIZE>
 where
-    TX: TxChannel,
+    TX: TxChannelAsync,
 {
     type Error = LedAdapterError;
     type Color = RGB8;
@@ -168,7 +168,7 @@ where
     /// Convert all RGB8 items of the iterator to the RMT format and
     /// add them to internal buffer, then start a singular RMT operation
     /// based on that buffer.
-    fn write<T, I>(&mut self, iterator: T) -> Result<(), Self::Error>
+    async fn write<T, I>(&mut self, iterator: T) -> Result<(), Self::Error>
     where
         T: IntoIterator<Item = I>,
         I: Into<Self::Color>,
@@ -187,14 +187,15 @@ where
         *seq_iter.next().ok_or(LedAdapterError::BufferSizeExceeded)? = 0;

         // Perform the actual RMT operation. We use the u32 values here right away.
-        let channel = self.channel.take().unwrap();
-        match channel.transmit(&self.rmt_buffer).wait() {
-            Ok(chan) => {
-                self.channel = Some(chan);
+        let mut channel = self.channel.take().unwrap();
+        match channel.transmit(&self.rmt_buffer).await {
+            Ok(_) => {
+                //self.channel = Some(chan);
                 Ok(())
             }
-            Err((e, chan)) => {
-                self.channel = Some(chan);
+            //Err((e, chan)) => {
+            Err(e) => {
+                //self.channel = Some(chan);
                 Err(LedAdapterError::TransmissionError(e))
             }
         }

Then adding async on the fn write trait member from smart-leds-trait crate, effectively having a breaking version of the (now async) trait.

Oh, scratch that comment about what to convert to async @Dominaezzz: I just realised that smart-leds-trait only implements TX because it only has the SmartLedsWrite... and what I commented about the photosensors (RX case) would be implemented via the already async RMT impl 🤦🏻
With this out of the way, I indeed only have to focus on carefully gating my changes through #[cfg(feature = "async")], so it might not be too tricky after all.

Digging around with this today (see comments in #1779) I seem to be stuck. The async context switching is surprisingly slow. Sometimes so slow that by the first time the future is polled, the RMT has already read 32 pulses. And wake up triggered by interrupt is particularly bad. (though I am also suspicious I may be doing something wrong with the interrupts)
I have this kind of working in my branch (https://github.com/esp-rs/esp-hal/compare/main...tschundler:esp-hal:async-led-iterator) in very messy code with no interrupts. Maybe it can serve as inspiration?
I may personally give up on async and focus on my original goal in #1768 of iterator input for RMT since that part I have working well. I'm well beyond my depth at this point. I'm debugging by panicking and dumping RMT registers. I feel there has to be a better way.

The async context switching is surprisingly slow.

Are you running in release mode?

The async context switching is surprisingly slow.

Are you running in release mode?

Yes. Even though the cargo generate template has some optimization in debug mode, I also tried with --release

@tschundler Maybe async is an issue, but you'll likely also want to place the rmt driver in RAM (esp-idf has an option for this), for better perf.
We already have a config option for this with SPI, once #2156 is merged we could add one for RMT.


ARTEMIS-2019 - Seperate ServerPlugin Interfaces

Seperate plugin interface by area, all extending a base interface.
Update code to check and call only plugins implementing specific interfaces.
Existing interface extends all the new interfaces for back compatibility or those who want simplicity and don't care about perf.

@cshannon this is what i was thinking, in regards to our discussion on https://github.com/apache/activemq-artemis/pull/2229

Looks good to me


Improved raycastparser.py

Hi peeps!
I've made major changes to the overall Raycastparser.py script.
Changes:
Documentation Added:

Added an overall script description to explain the purpose and functionality of the script.
Added class and method-level docstrings to provide a more detailed understanding of each component.
Added comments to the RayCastObjects enum to describe what each enum value stands for.

Type Annotations:

Introduced type annotations for method arguments and return types, making it easier to understand what kind of data each method expects and returns.

Dynamic Length Handling:

Removed hard-coded array length assertions in the parse method, replacing them with dynamic checks based on the actual length of the input raycast array. This makes the code more robust to changes in the raycast array's length as opposed to having to restructure it with every new addition to the list of raycast objects (highly scalable operation).

Code Readability:

Used more descriptive variable names for better readability.
Added inline comments to complex operations, explaining what they are intended to do.

Detailed Changes:
Documentation:

Added an overall script description at the top of the script.
Included class-level docstrings for the RayCastParser class to describe its purpose.
Each method now has a detailed docstring describing its parameters, return types, and functionality.
Enum RayCastObjects now has comments to describe what each object type is.

Type Annotations:

Added Python type annotations to method parameters and return types for parse, reorderRow, and prettyPrint.

Robustness:

Replaced static array length checks with dynamic length checks based on the length of the input array in the parse method.

Code Readability:

Introduced more meaningful variable names to make the code self-explanatory.
Added inline comments to clarify the steps involved in complex operations.

Priority is HIGH for this pull so please do test as much as you can. All my unit testing produced successful returns but I haven't tested on training models such as Braitenberg.
-Ibrahim

Before I do a proper review, a question already: are we aware/ok that  a raycaster can not detect the side of button pillar that has the button? Or is that not true?

I don't have time to properly test, but the code looks good. Definite improvement.

I mean, can a raycast agent differentiate a pillarbutton observation from the back, from a pillarbutton observation from the front (where it can bump against the button)?

That would require the entire pillar button mesh to be individualised which can be done. However it will increase the complexity by adding new raycast objects where currently it has just one entry. I could however add a unique tag to the actual button of the pillar button which can then be differentiated from the rest of the whole pillar button object/mesh. Did I answer your question?
On 5 Sep 2023 at 12:38 +0300, Wout Schellaert @.***>, wrote:

I mean, can a raycast agent differentiate a pillarbutton observation from the back, from a pillarbutton observation from the front (where it can bump against the button)?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were assigned.Message ID: @.***>

That answers my question, thanks! Just something to be mindful off in documentation and explanation of the buttonpillar in the future.

Hi everyone, I've spent a few hours looking at this and I can't get any of the old raycast-based stuff to work. There are a few things that I've noticed:

As far as I can tell, only 6 object categories are being returned in the observations, plus distance. I can't see where the other 5 object types are.
I'm having issues with the actions now. Some of that code seems to have broken too, perhaps under the update to mlagents 0.30.0.

I'm going to keep exploring to see if I can find the issue, but I can't approve the PR till we can get the braitenberg vehicles working again.

I'm happy that everything seems to work for now. It should be noted that I haven't been able to run tests with the new raycasting, so I'm not sure whether everything is working for the new AAI objects. However, reviewing the code, it ought to be flexible enough to handle this. @alhasacademy96 let us know when you have the new experimental build ready for the button, etc. and we can try it out.
For what it's worth, I've added an updated braitenberg script that we can run to check nothing has broken. You can request outputs from it to see what the raycasts are looking like. At the moment, I'm only getting 6 object types corresponding to the old ontology. I haven't been able to get more even when building afresh from animal-ai-unity, but perhaps I'm looking in the wrong place?
I'm going to approve this PR and merge into develop, as I think the purpose of the PR has been fulfilled. Thanks everyone!

I'll leave it to you @alhasacademy96 to merge when you're happy (especially with the updated egg)

Not the first time there are some issues with the egg. As far as I know, this shouldn't even be committed to version control. This is normally generated by build tools like pip based on specifications like setup.py. So, @kozzy97, I don't think it's safe to specify dependencies in the egg, as opposed to in the setup.py.
We could merge right now, but I've already made #31 to not lose it out of sight.

@kozzy97 can you look into the comments myself and Wout posted? I'm planning on merging on Sunday after the final details are done


MongoDB

I've launched my own instance of zira but it is unresponsive to any commands. I think this might be because I've setup MongoDB incorrectly. I'm really unsure of what to enter in the "Host/Collection" slot.
This error is thrown alot too
[Cluster (Error)] TypeError: Cannot read property 'collection' of null

Yeah it has something to do with the initial connection to the database, which it apparently only tries once. And then after that it just has the null error you provided.
Here's the erorr for the initial connection
[ ERROR ] 7/9/2018 15:3:30 [Cluster (Error)] { MongoError: failed to connect to server [ziradb:27017] on first connect [MongoError: getaddrinfo EAI_AGAIN ziradb:27017]
I haven't been able to figure out what to put in the host/collection slot either. I tried just putting "ziradb" hoping it would create said database/collection automatically but that didn't work. I used mongo shell to do "use ziradb" and then created a collection called "zcollection" inside of ziradb which DOES show when I use "show collections" in mongo shell... So I know the collection exists. I then tried just putting "zcollection" in the host/collections field, but that didn't work. I then tried "ziradb/zcollection" and that didn't work either, and just "ziradb" alone still doesn't work. Wish there was a little bit more documentation in the pm2.example.json but this whole shut down/self host thing all happened pretty fast.
I really just want to get this thing running for a week or so until I can just rewrite its tasks into another bot since this thing won't be maintained anymore..... Does anyone have any clues as to what to put in this host/collection field?

Host is the host of the database if you are running it on the same machine as zira it should be localhost  collection is just the Database name
Example
Localhost/Zira


Is there a native solution for jq's .load?

I have read the discussions on stackoverflow and seems there's still no good native solution to replace .load(). Then how do you guy deal with .load?

It's pretty easy to replace with fetch.
// jquery
$(selector).load(url);

// native
fetch(url).then(data => data.text()).then(data => document.querySelector(selector).innerHTML=data)


Resolved bug 1065 : Components > Contact Us > Default > Send message button alignment issue

Description

Resolve the issues on Component:

Resolved issue on Contact Us > Default > Send message button alignment.
Resolved issue on Menu > Default > Horizontal line is display.

Screenshots :

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

Resolved Conflict

Resolved issue on button alignment.