Fixes for macOS scancode implementation

Description
Here are some fixes for the scancode feature implementation for macOS. This PR is related to #1235.
This is a work is progress. I hope to make some more improvements soon but I open this draft PR already so that other contributors do not repeat the same work and can look for other improvements from there.
Some issues remain to be fixed:

Some keys are not detected and trigger no events (caps lock and a few others)
Shift key being pressed or not has an impact of key events

How to test this PR?
Running SFML-Input on macOS

I looked into the caps lock issue a while ago and I'm not sure there's a perfect solution for it based on what we get from the OS. I looked at what others do and tried some things myself and only found these options:

Use flagsChanged checking for the caps lock modifier almost works, but tracks the actual state of caps lock not the state of the physical button
Manually track the state of the key by polling the hardware (a bit unreliable, inconsistent, and also requires extra user permissions)

The only other keys I can see not working are:

§/± (cocoa key code 0xA0) so just need to decide what key that maps to and add it
fn key, which also seems to use flagsChanged so we can collect it there along with the other modifiers (it'/s NSEventModifierFlagFunction)

What's the issue you're seeing with the shift key? As far as I can tell the scan codes are always the same whether shift is pressed or not

What's the issue you're seeing with the shift key? As far as I can tell the scan codes are always the same whether shift is pressed or not

The issue is that, when pressing shift, event.key.code values are different (bad).
I confirm event.key.scancode values are the same with or without shift (good).

I think I fixed all I could fix.
Remaining issues:

Caps lock generates no events
§/± (key above tab) generates no events
`/~ (key next to left shift) generates event with Scan::Grave code

Regarding issues 2. and 3., fixing it would require detecting if keyboard is a US keyboard or not because virtual key code 0x32 then has a different meaning. See Figure 2-10 in Macintosh Toolbox Essentials.

iOS build failure should vanish as soon as the feature branch is rebased on 2.6.x thanks to https://github.com/SFML/SFML/pull/2263

iOS build failure should vanish as soon as the feature branch is rebased on 2.6.x thanks to #2263

I just rebased 2.6.x

For caps lock if we're happy with it representing the lock status then we can use the method I mentioned above
For the other two keys, does the virtual key code matter for scan codes, where we're representing the physical location of the key?
We discussed it briefly on discord a while ago and the conclusion was that the one above tab should be Grave and the one next to left shift should be non-US backslash?

For caps lock if we're happy with it representing the lock status then we can use the method I mentioned above

I would not say I would be happy with that, but that's maybe better than nothing. I don't know.

For the other two keys, does the virtual key code matter for scan codes, where we're representing the physical location of the key?

As far as I understand, virtual key code is Apple's equivalent of SFML's scancode. It represents a physical location of a key. But the location of virtual key code 0x32 is above tab for ANSI keyboards and next to left shift for ISO keyboards.
Digging a little further, it should be doable to detect which type of keyboard is used and map the correct scancode accordingly. This is what chromium does for example.
I can give it a try next weekend. Real-time polling might need adjustments too.

I think I fixed the issue related to §/± (key above tab) and `/~ (key next to left shift).
It works well with an ISO keyboard. I do not have an ANSI keyboard to test fully though.

With the help of @ChrisThrasher, we could check the key above tab is correctly mapped to Scancode::Grave on ANSI keyboard.

Should I implement events for caps lock using the lock status? It would get one out of every two events for that key, so it would be half broken, but maybe better than nothing?
Besides caps lock, this PR is ready in my humble opinion.

Yeah I'd say it's better than nothing, and also agree this is otherwise ready

Here it is! Caps lock now generates a key pressed / released event when the corresponding modifier state changes.
Rebasing should solve CI failures thanks to fa2e61b9d5864f6a909c5ad7130c49903948a785.

Thanks A MILLION TONS for this! I personally know how much time it takes to dive into stuff like that. <3
I'll clean up the commits a bit on the feature branch.

Thank you @kimci86 for all you've done! I think we're all really excited to see this ship.


Add caching for the analysis

The cache key is the file name, to be more resilient on file moves, but
is easy to change.

PTAL


showcase: add cyql.io

Thank you for your contribution to the IC Developer Portal.
Before submitting your Pull Request, please make sure that:

[ ] You have updated the .github/CODEOWNERS file according to your changes.
[ ] You have registered new documents to /sidebars.js if any.

Dear @tomkoom,
In order to potentially merge your code in this open-source repository and therefore proceed with your contribution, we need to have your approval on DFINITY's CLA.
If you decide to agree with it, please visit this issue and read the instructions there. Once you have signed it, re-trigger the workflow on this PR to see if your code can be merged.
— The DFINITY Foundation


[release/1.2] Fix process locking and state management

There were races with the way process states.  This displayed in ways,
especially around pausing the container for atomic operations.  Users
would get errors like, cannnot delete container in paused state and
such.
This can be eaisly reproduced with docker and the following command:
> (for i in `seq 1 25`; do id=$(docker create  alpine usleep 50000);docker start $id;docker commit $id;docker wait $id;docker rm $id; done)

This two issues that this fixes are:

locks must be held by the owning process, not the state operations.
If a container ends up being paused but before the operation
completes, the process exists, make sure we resume the container before
setting the the process as exited.

Signed-off-by: Michael Crosby<EMAIL_ADDRESS>

Codecov Report

Merging #2803 into release/1.2 will not change coverage.
The diff coverage is n/a.

@@             Coverage Diff              @@
##           release/1.2    #2803   +/-   ##
============================================
  Coverage        43.74%   43.74%
============================================
  Files              100      100
  Lines            10728    10728
============================================
  Hits              4693     4693
  Misses            5305     5305
  Partials           730      730

Flag
Coverage Δ

#linux
47.41% <ø> (ø)
:arrow_up:

#windows
40.9% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

backport of https://github.com/containerd/containerd/pull/2773

LGTM


Bug: content-length header makes proxy fail on a deployed site

- If the current behavior is a bug, please provide the steps to reproduce.
Deploying the following function will result in a 502 proxy error:
exports.handler = async function (event, context) {
    return {
        statusCode: 200,
        headers: {
            "Content-Length": 3,
        },
        body: "123",
    };
};

- What is the expected behavior?
Netlify dev works correctly and doesn't generate a 502 proxy error.

Closing as stale


Moving Standard deviation

I am going to use this library in my Rust Rocket Server, as this is nice implementation of technical analysis algorithms. Well done! I have seen that it would be nice to have some more indicators, so I have added what I need the most, which is Moving Standard Deviation.  And if this project is open for contribution I would be happy to do some work, and propose what would be a 'nice to have'. Thx.

@Bartoshko Thank you for your pull request. I left number of comments.
However I haven't yet deeply reviewed the implementation of the indicator itself.
Regarding the indicator Moving Standard Deviation, I understand it as the math concept, but never really have seen something like this in any of trading tools. E.g. in investing..com: https://www.investing.com/equities/twitter-inc-chart
Can you provide some examples of tools that use it?
From a first look you PR looks good, thanks for writing the proper doc and tests.

And if this project is open for contribution I would be happy to do some work, and propose what would be a 'nice to have'. Thx.

The project is open for contributions. However the goal of the project is to provide technical analysis indicators with a unified interfaces and good documentation.
In case if you really want to something add/implement I would suggest first to open an issue and initiate discussion to prevent useless effort if by some reason the change can not be accepted from the very beginning.
Thank you! =)

I have read all your comments and I have to say I do agree with You. Therefore I don't see any value of going forward with what I have done. I just jumped in to this with a bit of rush. Thanks for Your time spent on QA ,I hope to build on this in the future.
My point was to add some code that will help me with creating tool for Bollinger Bands analysis.
I will rethink all and get back to you with an proper issue.
Thanks a lot =)


[Consumer UI Refresh] Create the Popover style Modal and switch to it for wide screens

If you haven’t already, check out our contributing guidelines for onboarding!

Now that the CreateMenu exists we need to display an alternate modal style depending on if we have a wide screen width. Here's what it should look like.

Deliverables:

Create a new style of modal called a popover
It should not have a semi-transparent back drop like other modals
It should still close when tap outside and also close when tapping the x
It should be aligned with the FAB
It should only be visible when viewing past the responsive breakpoint

@marcaaron
Just to be sure, the response when clicking the FAB on small screens (windowDimensions.width < variables.mobileResponsiveWidthBreakpoint) should not change?

@marcaaron
Just to be sure, the response when clicking the FAB on small screens (windowDimensions.width < variables.mobileResponsiveWidthBreakpoint) should not change?

Correct. In that case, we will use the bottom_docked style menu like we are now.

Correct. In that case, we will use the bottom_docked style menu like we are now.

Proposal

Add a new MODAL_TYPE in src/CONST.js called POPOVER and use it to create a new modal style in src/styles/getModalStyles.js;
Add a new prop on the Modal component called isPopover. It defaults to false and can be set in getModalStyles. Use this prop to conditionally render the backdrop;
I am still testing out the animations, but I want to end up with an animation similar to the material UI popover menu;
Conditionally renders this modal style when the screen is not small.

Aditional proposal
The proposal above would be in line with the deliverable, but a modal might not be the best solution for this. A normal View with a click away listener might provide a better UX.
For example, if the menu opens a modal, the user no longer has a pointer cursor for the fab, links or just pointers at all. And has to click twice to perform another action (close modal -> perform action).
The material UI link I sent before (this link) has a nice example of this.  I personally greatly prefer the first.

Proposal

Add a new MODAL_TYPE in src/CONST.js called POPOVER and use it to create a new modal style in src/styles/getModalStyles.js;
Add a new prop on the Modal component called isPopover. It defaults to false and can be set in getModalStyles. Use this prop to conditionally render the backdrop;
I am still testing out the animations, but I want to end up with an animation similar to the material UI popover menu;
Conditionally renders this modal style when the screen is not small.

Aditional proposal
The proposal above would be in line with the deliverable, but a modal might not be the best solution for this. A normal View with a click away listener might provide a better UX.
For example, if the menu opens a modal, the user no longer has a pointer cursor for the fab, links or just pointers at all. And has to click twice to perform another action (close modal -> perform action).
The material UI link I sent before (this link) has a nice example of this.  I personally greatly prefer the first.

Add a new prop on the Modal component called isPopover. It defaults to false and can be set in getModalStyles. Use this prop to conditionally render the backdrop;

I think we can maybe get even more generic here and have this be showBackdrop in case other things would hide it?

I am still testing out the animations, but I want to end up with an animation similar to the material UI popover menu;

Sounds good, I think we can even just have it fade into a fixed position for now. But maybe @shawnborton has thoughts on this and we should get some ideas from him.

A normal View with a click away listener might provide a better UX. For example, if the menu opens a modal, the user no longer has a pointer cursor for the fab, links or just pointers at all. And has to click twice to perform another action (close modal -> perform action). And when there is no backdrop it doesn't feel natural (for me) to have a different behavior.

That's a good point and I agree with you. I guess my counter question would be...
Is there any way to:

Not use a backdrop for the modal (hasBackdrop: false maybe can be used)
Add a click away handler so we can close the modal yet not prevent additional actions

I'm not sure if that would be possible, but it might be worth trying.

Add a new prop on the Modal component called isPopover. It defaults to false and can be set in getModalStyles. Use this prop to conditionally render the backdrop;

I think we can maybe get even more generic here and have this be showBackdrop in case other things would hide it?

I am still testing out the animations, but I want to end up with an animation similar to the material UI popover menu;

Sounds good, I think we can even just have it fade into a fixed position for now. But maybe @shawnborton has thoughts on this and we should get some ideas from him.

A normal View with a click away listener might provide a better UX. For example, if the menu opens a modal, the user no longer has a pointer cursor for the fab, links or just pointers at all. And has to click twice to perform another action (close modal -> perform action). And when there is no backdrop it doesn't feel natural (for me) to have a different behavior.

That's a good point and I agree with you. I guess my counter question would be...
Is there any way to:

Not use a backdrop for the modal (hasBackdrop: false maybe can be used)
Add a click away handler so we can close the modal yet not prevent additional actions

I'm not sure if that would be possible, but it might be worth trying.

I think we can maybe get even more generic here and have this be showBackdrop in case other things would hide it?

Make sense!

Sounds good, I think we can even just have it fade into a fixed position for now

You mean from the bottom (or left) of the screen? (not from the top of the button). It does make it easier.

Not use a backdrop for the modal (hasBackdrop: false maybe can be used)

This was my first idea when reading the react-native-modal API. But for some reason, I can't seem to get this prop to work on web and desktop for anything (works on android). I will to do some more debugging, see if I can find the reason.

I think we can maybe get even more generic here and have this be showBackdrop in case other things would hide it?

Make sense!

Sounds good, I think we can even just have it fade into a fixed position for now

You mean from the bottom (or left) of the screen? (not from the top of the button). It does make it easier.

Not use a backdrop for the modal (hasBackdrop: false maybe can be used)

This was my first idea when reading the react-native-modal API. But for some reason, I can't seem to get this prop to work on web and desktop for anything (works on android). I will to do some more debugging, see if I can find the reason.

You mean from the bottom (or left) of the screen? (not from the top of the button). It does make it easier.

Yeah I was thinking it would not necessarily have to transform from a certain origin just simply fade into a fixed position.

You mean from the bottom (or left) of the screen? (not from the top of the button). It does make it easier.

Yeah I was thinking it would not necessarily have to transform from a certain origin just simply fade into a fixed position.

I really can't seem to get this modal to behave as I want on web and desktop.
Just to summarize, the behavior I want is for the modal to not have a backdrop, so we don't have a div covering the whole screen and don't lose our cursor functionality (for other actions) when the CreateMenu is opened.
I tried:

Setting hasBackdrop to false (works on mobile);
Using the customBackdrop props, passing down an empty <View /> (works on mobile);
Setting coverScreen={false} with backdropOpacity={0} (also doesn't work as intended on mobile)

I also tried to find existing issues of this on the react-native-modal github page, but could not find anything.
If someone could please test at least the two first things I tried, to make sure it is not just me, it would be greatly appreciated.
The file is located at scr/components/Modal.js.
If someone else tests it and it really doesn't work, I see two options:

Use the modal setting backdropOpacity={0}, and not really care about the whole cursor problem;
Create a new component for this, don't use the modal.

I really can't seem to get this modal to behave as I want on web and desktop.
Just to summarize, the behavior I want is for the modal to not have a backdrop, so we don't have a div covering the whole screen and don't lose our cursor functionality (for other actions) when the CreateMenu is opened.
I tried:

Setting hasBackdrop to false (works on mobile);
Using the customBackdrop props, passing down an empty <View /> (works on mobile);
Setting coverScreen={false} with backdropOpacity={0} (also doesn't work as intended on mobile)

I also tried to find existing issues of this on the react-native-modal github page, but could not find anything.
If someone could please test at least the two first things I tried, to make sure it is not just me, it would be greatly appreciated.
The file is located at scr/components/Modal.js.
If someone else tests it and it really doesn't work, I see two options:

Use the modal setting backdropOpacity={0}, and not really care about the whole cursor problem;
Create a new component for this, don't use the modal.

Maybe the cursor thing isn’t a big deal, in that clicking outside of the
menu should close the menu and not interact with background UI. Thoughts on
that?
On Wed, Jan 20, 2021 at 3:28 PM Lucas.Neuhaus.dev<EMAIL_ADDRESS>wrote:

I really can't seem to get this modal to behave as I want on web and
desktop.
Just to summarize, the behavior I want is for the modal to not have a
backdrop, so we don't have a div covering the whole screen and don't lose
our cursor functionality (for other actions) when the CreateMenu is opened.
I tried:

Setting hasBackdrop to false (works on mobile);
Using the customBackdrop props, passing down an empty
(works on mobile);
Setting coverScreen={false} with backdropOpacity={0} (also doesn't
work as intended on mobile)

I also tried to find existing issues of this on the react-native-modal
github page https://github.com/react-native-modal/react-native-modal,
but could not find anything.
If someone could please test at least the two first things I tried, to
make sure it is not just me, it would be greatly appreciated.
The file is located at scr/components/Modal.js.
If someone else tests it and it really doesn't work, I see two options:

Use the modal setting backdropOpacity={0}, and not really care
about the whole cursor problem;
Create a new component for this, don't use the modal.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Expensify/Expensify.cash/issues/1267#issuecomment-763643311,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AARWH5UD66AHNK4UJMU643DS23SBNANCNFSM4WJFVHBQ
.

Maybe the cursor thing isn’t a big deal, in that clicking outside of the
menu should close the menu and not interact with background UI. Thoughts on
that?
On Wed, Jan 20, 2021 at 3:28 PM Lucas.Neuhaus.dev<EMAIL_ADDRESS>wrote:

I really can't seem to get this modal to behave as I want on web and
desktop.
Just to summarize, the behavior I want is for the modal to not have a
backdrop, so we don't have a div covering the whole screen and don't lose
our cursor functionality (for other actions) when the CreateMenu is opened.
I tried:

Setting hasBackdrop to false (works on mobile);
Using the customBackdrop props, passing down an empty
(works on mobile);
Setting coverScreen={false} with backdropOpacity={0} (also doesn't
work as intended on mobile)

I also tried to find existing issues of this on the react-native-modal
github page https://github.com/react-native-modal/react-native-modal,
but could not find anything.
If someone could please test at least the two first things I tried, to
make sure it is not just me, it would be greatly appreciated.
The file is located at scr/components/Modal.js.
If someone else tests it and it really doesn't work, I see two options:

Use the modal setting backdropOpacity={0}, and not really care
about the whole cursor problem;
Create a new component for this, don't use the modal.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Expensify/Expensify.cash/issues/1267#issuecomment-763643311,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AARWH5UD66AHNK4UJMU643DS23SBNANCNFSM4WJFVHBQ
.

Yeah, it is a very minor thing. But I was hoping to find an easy solution.
 If after testing out we realize we can change it so something else, we can keep the discussion there.

Yeah, it is a very minor thing. But I was hoping to find an easy solution.
 If after testing out we realize we can change it so something else, we can keep the discussion there.

I've tried for a bit to get the hasBackdrop={false} prop to work and can confirm that it is not working on web.
I can't see any reason why this shouldn't work and see that you've opened an issue here. So, probably the best thing to do for now is proceed with the modal opacity 0 and hopefully we can resolve this in the future to improve the UX.
Thanks!

I've tried for a bit to get the hasBackdrop={false} prop to work and can confirm that it is not working on web.
I can't see any reason why this shouldn't work and see that you've opened an issue here. So, probably the best thing to do for now is proceed with the modal opacity 0 and hopefully we can resolve this in the future to improve the UX.
Thanks!


Feature: Add Client Library API Documentation

Ready for review.

@curb47 can you please review?

@curb47
1.Followed M2X Python docs for commenting guidelines w.r.t adding query parameters in comments: http://m2x-python.readthedocs.io/en/latest/
2.All other changes done.
Ready for Review.

@gokulmInfy @kristinpeterson That makes sense about the query parameters.
Everything looks good, merging PR.


Add resolution data to location update schemas

I've added resolution data to location update schemas. This is due to the changes from issue https://github.com/ably/ably-asset-tracking-android/issues/509

Due to changes in requirements, the resolution will be sent via presence data which is already reflected in the JSON Schema so I'm closing this PR.


ERG - Spill size and Time of Day

Upon either changing the size or time of the spill, there is no response.

@JoeKezon Fixed the issue and widget tested thoroughly. Please get the latest widget and test in your environment. Please let me know if you encounter issues.

issue fixed


Cannot find protocol declaration for 'ASAuthorizationControllerDelegate';

Hello! I use "Cordova 8" and xCode 10.1 to build my app.
I update my "FirebaseAuth" pod to 6.5.1 for solving issue with "AppAuth 1.3.0".
During build my iOs App i catch errors in "AppDelegate.h+FirebasePlugin.h" file" (l.7):

Cannot find protocol declaration for 'ASAuthorizationControllerDelegate'; did you mean 'UINavigationControllerDelegate'?
Cannot find protocol declaration for 'ASAuthorizationControllerPresentationContextProviding' and also 18 error in other files connected with "ASAuthorizationController".

Please update to Xcode 11 - Xcode 10 is out-of-date and therefore not supported.


Live share doesn't work

Product and Version [VS/VSCode]:
OS Version [macOS/Windows/Linux]:
Live Share Extension Version:
Target Platform or Language [e.g. Node.js]:
What were you doing when you encountered the desync?
How often have you encountered desyncs?

Hey @aagneshansson could you tell us more about what didn't work? Looks like you encountered a desync. Was this impeding your ability to use Live Share overall?

Hi @aagneshansson, thanks for reaching out to Live Share. We are tracking this desync issue in #3736. I am closing as duplicate, please add your comments and logs in #3736 and join the conversation there! You can access your logs via the Live Share: Export Logs command in the command palette.


Reverse the Dataset module

Let's reverse the datasets module, the newly added datasets need to be in top, currently its opposite.

fixed

Still the same, not solved!!


Unknown function: term_start

I'm on Mac OSX, and vi version is 9.0.1283.
When I run :GhcidQuickfixStart, it fails with:
"output-vim-ghcid-quickfix-ghcid" [Not edited] --No lines in buffer--
Error detected while processing function ghcid_quickfix#start:
line   12:
E117: Unknown function: term_start

Perhaps I didn't quite install it correctly? Any help would be appreciated.

Never mind; reinstalling vim solved the issue. (+terminal wasn't enabled in the original.)

@LeventErkok Thank you for this good report :+1:
I'll add a notice to require +terminal to README!

I added the notice at 7fa539959862a45c3031448affba771ec80cfdbd :smiley:

I have neovim 3.4 and am experiencing this same issue but suspect the problem is trivial.
Error detected while processing function ghcid_quickfix#start:
line   12:
E117: Unknown function: term_start

I'm not clear on what +terminal is precisely but I gather neovim doesn't support it?
:echo has('terminal')
0

IIRC Neovim terminal thing is different from what vim8+ has. So I don't think this plugin will work (at least right now) in Neovim

Yes, this plugin may not work on NeoVim.
Sorry...
I'll implement for NeoVim if many persons want, but I don't have a plan for NeoVim now 🙆♂


Add Dockerfile Diff Extension

https://github.com/felipecruz91/dockerfile-diff-extension
@sivolko

It's now in the Extension Marketplace.

Added.


Create new Organisation with 'LOCAL_AUTHORITY' org. type

Description:
PR to add 'LOCAL_AUTHORITY' organisation_type when creating new Organisation on submission.

Can we write a test for this? Although guess it's the same as the default behaviour anyway?


[BUG] Create rollup jobs shows empty error toast when data source switches to incompatible

What is the bug?
When user switches from a compatible data source to incompatible on "Create rollup job" page, the page displays empty error toast.
How can one reproduce the bug?
Steps to reproduce the behavior:

Go to future playground
Click on 'Rollup jobs', then create rollup job
on the first create page, select data source called aos211
View the available indexes in the source index field

5. switch data source to "incompatible"
6. see the empty error toast

What is the expected behavior?
The incompatible data sources should be hidden from the data source picker.
In the interim we can lock the previously selected data source to "read only" on the "Create" page.

Catch All Triage - 1 2 3 4 5 6


Ability to disable a lint rule for a specific resource

Reason/Context
Like I can with eslint rules, I'd like to be able to disable a Microcks lint rule for any applicable resource in an OAS doc by specifying, say, x-microcks-ignore-rules and setting an array with rule names, e.g, ["microcks-examples-in-request-content"].
Description
I think it's all stated above. This would not be a breaking change.
Implementation ideas
No response

Hi @savvyintegrations,
I had a look at what is possible to do at a Spectral rule level and it seems that the "canonical way" to it is to use Overrides.
Instead of having your ignore-list managed at the specification level, it involves managing it within a .spectral.yaml file at the project level. Using overrides you can achieve what you want with this syntax if you want to ignore one rule for a specific element of your spec:
extends:
  - "https://unpkg.com/<EMAIL_ADDRESS>overrides:
  - files:
    - "resources/weather-forecast-*.yaml#/paths/~1forecast~1%7Bregion%7D/get"
    rules:
      microcks-operation-extension-valid: "off"

I have run some tests and Microcks rules can be ignored that way.
I find it more elegant than implementing something specific to Microcks. What do you think?

I'm removing the target milestone at the moment as I think we have a solution and so we don't block the release for solving #10.

Nice! Sounds good to me.


system.xml compile error

When trying to compile the mod, given CS0234 where system.xml cannot be utilized, throughout many files, whichever file has the line in use

@CXUtk Does it happen?

I think this problem has already sloved


PowerToys committing an Access Violation when right-clicking tray icon

Microsoft PowerToys version
0.43.0
Running as admin

[X] Yes

Area(s) with issue?
System tray interaction
Steps to reproduce
> Right-click the PowerToys tray icon with WinDbg installed (and set as the system's post-mortem debugger)
> WinDbg opens and displays the following (after ModLoad):
(1b88.1968): Access violation - code c0000005 (!!! second chance !!!)

✔ Expected Behavior
Tray icon context menu would appear.
❌ Actual Behavior
Tray icon context menu failed to appear, and instead PowerToys committed an access violation which WinDbg showed me.
Other Software
No response

Could you please send a bug report?
Run C:\Program Files\PowerToys\Tools\BugReportTool.exe (assuming that's your install folder location.
This will create a PowerToysReport_*.zip file in your Desktop.
Drag and drop report into a GitHub comment.


upgrade django to 1.9

see #1005 for background

@adityadharne see https://github.com/gwu-libraries/sfm-ui/issues/74

We are upgrading to Django 1.8 as an interim step


Add docker hub badge

I would separate the code-quality stats from the slack and download stats (e.g. move the go-report badge one place to the left)


[Snyk] Upgrade @salesforce/core from 2.36.3 to 2.36.4

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade @salesforce/core from 2.36.3 to 2.36.4.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 1 version ahead of your current version.
The recommended version was released 22 days ago, on 2022-04-28.

Release notes

Package name: @salesforce/core

2.36.4 - 2022-04-28chore(release): 2.36.4 [ci skip]

2.36.3 - 2022-04-21chore(release): 2.36.3 [ci skip]

    from @salesforce/core GitHub release notes

Commit messages

Package name: @salesforce/core

8b24221 chore(release): 2.36.4 [ci skip]
0dde8a7 Merge pull request #569 from forcedotcom/ew/remove-jsen
f2078e3 Merge branch 'main' into ew/remove-jsen
2f44345 fix: disable strictSchema
a0868d1 fix: schema comment
95c0710 fix: test failures and cleanup
739723a chore: cleanup
87ca60c fix: replace JSEN with AJV (wip)

Compare

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Upgraded to 2.37.1


Generate gaze training data?

https://news.developer.nvidia.com/ai-generated-faces-track-your-movements/

#322

This package could potentially provide unlimited training data:
https://github.com/wayaai/SimGAN

Implementation of Apple's Learning from Simulated and Unsupervised Images through Adversarial Training

Also...
https://www.kaggle.com/4quant/eye-gaze/version/1

Rendering of Eyes for Eye-Shape Registration and Gaze Estimation
http://arxiv.org/pdf/1505.05916.pdf


Added tvOS build target

Added test target, framework target, and updated build scripts.
Only includes files included in MacBolts, (no app links, etc.)

Generally looks great, throwing in some thoughts for discussion.

LGTM. Ship!


Dataset access service: DIY: enhancement for user dataset support

[ ] will  access installed user datasets appDB tables to determine which users can access
[ ] Uses new views instead of tuning dataset tables

FYI I'm moving this ticket to b59. We want DIY to be publicly released in b59, but made available on the QA site in b58.

Backend changes, will open new ticket if any bugs pop up


JS DOM

hopefully netlify is working right. Resolves #7

How do you plan to integrate this into your portfolio.

How do you plan to integrate this into your portfolio?

The DOM manipulation itself, or are you looking for this file to be a part of the portfolio?

Both?

How do you plan to integrate this into your portfolio?

The DOM manipulation itself, or are you looking for this file to be a part of the portfolio?

Both?

Well, I wouldn't put this in my portfolio as this is providing a feature that is not needed within the current design.  One could use something similar if they wished to implement an interactive about me ie: a timeline where you could remove each event stage as the "story" progressed.
As for the DOM manipulation itself in the current design, I might have done this for the contact form modal.

Please implement one of those features you listed out, whether a timeline, contact modal or something else. Please update the design too with whatever feature you plan on implementing. Each week should build on each other and not be done in isolation. We want you to iterate instead of creating new standalone projects each week.

Please implement one of those features you listed out, whether a timeline, contact modal, or something else. Please update the design too with whatever feature you plan on implementing. Each week should build on each other and not be done in isolation. We want you to iterate instead of creating new standalone projects each week.

👍🏼 Got yeah. I wasn't planning on having such a feature, i.e., a manipulatable list, on my portfolio as this was not a part of my design.

Following up to see how the changes are coming along.

Last night as I was thinking about the tooltip position sometimes breaking and how I could fix it, I realized that the function probably isn't even needed. I say this because everything other than the image and the border pointer is positioned absolutely, and if I can keep the hotspots where I want them, then I should be able to do that with the tooltip cards. Though I also might want to repurpose the content within them as they are more than likely too big.


Bad Request (#400) submiting a form on regular response

In a controller action if I return a regular respone, regular view with a form, when I submit this form I get a Bad Request (#400) error. I guess this is related to CSRF??
What I'm trying to do is that I don't want to use Inertia in all controllers/actions but use it only in some cases. So I would like to use regular views and forms as usually and be able to "enhance" som controllers using Svelte with Inertia. Is this possible or am I missing something?

 'class' => 'tebe\inertia\web\Request',
 'cookieValidationKey' => '<cookie_validation_key>',
 'enableCsrfValidation' => true,
 'enableCsrfCookie' => true,
 'parsers' => [
     'application/json' => 'yii\web\JsonParser',
 ]

Please remember to insert these lines into the appropriate configuration file (either config/web.php or advanced app backend/config/main.php), and replace <cookie_validation_key> with the correct cookie validation key.

Yes, and this is when I get the error:
'enableCsrfValidation' => true,
'enableCsrfCookie' => true,

If I set these to false, I get no error, but of course, I'm not using CSFR protection.
What I want is to keep using CSFR, becouse in my app there will be a lot of regular actions (without Inertia) and also some actions with Inertia.


Plex Media Player stuck connecting

In Firefox Nightly (62.0a1 (2018-06-13) (64-bit)) on my mac (10.13.5), I am getting the following error when trying to connect to Plex Media Player (3.57.1) from v2.synclounge.tv:
Pulled from console:
XML Parsing Error: no root element found Location: http://<IP_ADDRESS>:32433/player/timeline/subscribe?port=8555&protocol=http&X-Plex-Device-Name=SyncLounge&commandID=1 Line Number 1, Column 1: subscribe:1:1 XML Parsing Error: no root element found Location: http://<IP_ADDRESS>:32433/player/timeline/subscribe?port=8555&protocol=http&X-Plex-Device-Name=SyncLounge&commandID=3 Line Number 1, Column 1:

On Windows 10 using 64-Bit Google Chrome (67.0.3396.99) I cannot connect to the Windows desktop Plex app (3.57.1) when using v2.synclounge.tv
image
Issue is reproducible, so I can provide more information if needed.

Just to clarify, does connecting to PMP work when using v1 (app.synclounge.tv)? I've had a couple issues using PMP with v2 myself but I can't nail down why.

It connects flawlessly.

V1 works for me also. Funnily enough v2 does work with Plex iOS and Apple TV for v2. Not sure if this is at all related to how v2 talks with Plex apps.

Thanks, looking in to this now

Update: I was able to get SyncLounge to talk to PMP by repeatedly refreshing SyncLounge and restarting PMP. This only seems to work some of the time and I don’t have any logs that explain this process. None of the software components have updated. Important side note, I have a pretty powerful IDS and firewall and the SyncLounge server runs behind a NAT and reverse proxy. There have been no logs showing something being blocked and poke is an off site user. Connections to the SyncLounge server have been fine once established but the initial connection to the player has been hit or miss.

Thanks for the update. I think in a few cases PMP isn't updating its client details with Plex.tv - causing SyncLounge to connect to old details. That doesn't cover all cases however. Last week I couldn't connect even with up to date details but reinstalling PMP managed to get it going for a while. AppleTV has recently started facing the same issues so I'm wondering if something has been added that we're missing.
Until I can find a fix I'd suggest either using OpenPHT or the inbuilt client (which can now direct stream most formats when enabled in SyncLounge Settings).

This should be fixed now, please let me know if you have any issues.

I am seeing this issue still, with the latest update there doesn't seem to use v1 or there update was also pushed to v1.  Either way app.synclounge.tv and v2.synclounge.tv do not work with plex media player at all for me or my friends.

For now I've rolled back app.synclounge.tv to v1, although my connectivity to PMP works on both v1 and v2. It has been a little inconsistent in general, although those issues were occurring across both versions.
@TheThreemagi Which view are you using with PMP? I seem to have better results with the TV mode.

I am using TV Mode, I just played around with switching just to see if web mode had anything different, no luck in either mode.

I've just committed a potential fix for this which should be live on v2.synclounge.tv within the hour. Please let me know if it works when you get a chance. I'm not 100% certain but here's hoping.
Funnily enough my PMP has the exact same issue with v1 and v2. It will randomly start working after I leave it open for a few minutes.

Just checked now, not sure if the commit was pushed out but it still has the same behavior.  Not sure if it helps but I did figure out some oddities in the connected.  If I try to connect to v2 and it doesn't work then I got back to v1, v1 will not connect unless I restart PMP.  If on I try v1 first and connect and then connect to v2, v2 works perfectly till I restart PMP.   Hopefully that's helpful.

That definitely helps, thanks!

It works perfectly now, I'm so excited.  v2 looks much nice.  Thank you so much!


M83 Agile tasks changes

Change task instance name format for DTA tasks
Update testagent update logic based on setup file versions

looks fine


Add BLOB type to schema (Streamline issue 765)

Registry changes for https://github.com/hortonworks/streamline/issues/765

What's the use case for this? For Avro,JSON,xml you represent a blob of data as a byte[] typically.

Eg inputstream is can be turned into a byte array and vice versa

+1

Closes #188


Custom keybindings

Resolves #34
This implements things as listed in #34 with a couple of small tweaks due to issues in winit

The amount of usable keys is slimmed down
Shift now has to be specified regardless of the key (I originally wanted "G" to represent Shift+g, but the platform inconsistencies with how things like + are expressed (Shift+= vs Shift++) made me walk this back)

There is now a new section in the config file for keybindings. Here's the one from `inlyne.toml.sample
[keybindings]
# Base will override the defaults if set
# Default: Not set
base = [
    ["ToTop", "Home"],
    ["ToBottom", "End"],
    ["Copy", { key = "c", mod = ["Ctrl"] }],
    ["ToTop", ["g", "g"]],
    ["ToBottom", { key = "g", mod = ["Shift"] }],
    ["Copy", "y"],
]
# Extra will be applied on top of base/defaults
extra = ... # Refer to `base`

A decent amount of the code goes into deserializing this. I wanted to allow for the config to be simple, so you can see that you can do things like provide a single key instead of a full combo, or provide just the key if there are no modifiers
The other bulk of the changes is for handling KeyCombos. It's a struct that gets initialized with the keybindings. Afterwards it can consume keys and will emit if they corresponded to some action

Here's everything in action. The section of my config for reference
[keybindings]
extra = [
    ["Copy", "y"],
    ["ScrollUp", "k"],
    ["ScrollDown", "j"],
    ["ToTop", ["g", "g"]],
    ["ToBottom", { key = "g", mod = ["Shift"] }],
    ["Quit", "q"],
    ["Quit", [{ key = "z", mod = ["Shift"] }, { key = "z", mod = ["Shift"] }]],
    ["Quit", [{ key = "z", mod = ["Shift"] }, { key = "q", mod = ["Shift"] }]],
]

https://user-images.githubusercontent.com/30302768/187098807-18d806e2-fa8c-4afc-9c87-588a196a3c9a.mp4

Looks brilliant can't wait to try this out when I review it tonight

I tried it and I love it. The vim style shortcuts feel really good and honestly I might be tempted to implement a ghetto version of 10j, 3k..etc in the future just to move around faster in vim style. Looking at the code its clear to see how well thought out this was, so I think this is good to merge the way it is.
With this, checklist support, customising line scrolling and live reloading, I'll make another weekly release of v0.2. Unless any other spectacular changes come along I think I'll change to bi-weekly releases after this one for stability. 🥳

Some sort of vim-mode shouldn't be too hard to hack into the current system since it would just involve:

Erroring on commands that start with numbers
Special-casing if we get some numbers before a command
Adding vim-like keybindings to the default keybindings

Maybe you could match the number for any current bindings and if there isn't any then you store the number for the next time that you press j or k. That way you could still accept bindings starting with numbers, as I think a user would understand if they bind 5 to an action they can't expect 5j to work. About the vim-like bindings been set as default I think a lot of users would like that.


Data augmentation on CPU？

From my observation, you modified the data augmentation code from the caffe version. But it still cannot run on GPU. How can I do it by GPU or multi-CPU?
Thanks.

Hello,
I am running into the same problem. Have you found a solution? As I am working in a cluster, I have found that I have to wait a lot to allocate the enough amount of CPUs (+memory) and the GPU to successfully run data augmentation without running out of memory.
Cheers.

I tried to disable all transformation done regarding colour (dataset_configs.py from 'image_b' downwards) to no avail. For now I use Data augmentation on the CPU successfully but it requires a high number of resources and that means I have to wait longer for my job to enter the server's queue.
I'll try to take a look at the PyTorch implementation to see if they perform the augmentation on the GPU and try to "port it". I'll update you if I can manage to do it.


Setup the defenseunicorns/pkg library repo

Describe what should be investigated or refactored
We need to setup the defenseunicorns/pkg repo in order to have a home for all of the different libraries that we are seeking to make reuseable from Zarf.  This includes:

creating a README.md
creating an APL2 LICENSE file
creating a CONTRIBUTING.md
creating a SECURITY.md
creating a CODEOWNERS
setting up OpenSSF scorecard
setting up branch protection
setting up dependabot (this differs from other repos but is something we have elected to try)
setting up unit testing workflows for PRs
setting up a CVE workflow for PRs
setting up a license workflow for PRs
setting up a CodeQL workflow for PRs
setting up UDS tasks to run the CVE / unit tests locally
defining a release process: (something like https://github.com/defenseunicorns/kubernetes-fluent-client/blob/main/.github/workflows/release.yml)

Links to any relevant code
https://github.com/defenseunicorns/pkg
Additional context
This is story 3/4 in an ultimate goal to bring all of Zarf's OCI library into a common library for reuse across projects.

Some ideas I gathered (incomplete) are here! https://github.com/justinthelaw/repository-template

We decided against using uds task and opted for make instead. We may look at tasks again in the future, but it is missing some features we want


TCPSocket specs hang if client doesn't connect

The TCPSocket#initialize specs will hang if the client socket does not connect to the server, since the shutdown for the server expects that it will have handled a request and be wrapping up here:
https://github.com/ruby/spec/blob/master/library/socket/fixtures/classes.rb#L125-L129
I found this while adding support for the new connect_timeout keyword; we do not support hash arguments on TCPSocket#initialize at the moment, so the socket never connects. This leaves the server waiting for an incoming connection, and the Thread#join above will hang the suite.
Perhaps we should actively try to close the server socket before we join the thread, and ignore any errors on the thread from a double-close? It would allow these specs to be a bit more robust when there are errors setting up the TCPSocket before connection.

Good find, PR welcome.
Ideally we'd find a way which is not racy and doesn't involve Thread#kill (tends to be messy with open IO).

Thanks for fixing the typos. I had hoped to avoid swallowing errors during the accept or close calls but given the races involved I think that may be unavoidable.
I believe it should be expected of all Ruby specs that they can set up and tear down cleanly without any expectation that the spec body runs successfully. That is clearly not the case here, since numerous kinds of failures in the spec body will lead to the teardown logic hanging. That is not a timeout due to a bug, it is a timeout due to a badly written spec teardown.


Teams Activity Handler updates

Add composeExtension/onCardButtonClicked
BotMessagePreviewAction.submit to .send (there is no submit)

Pull Request Test Coverage Report for Build 80043

0 of 0   changed or added relevant lines in 0 files are covered.
358 unchanged lines in 58 files lost coverage.
Overall coverage decreased (-1.3%) to 79.971%

Files with Coverage Reduction
New Missed Lines
%

/libraries/Adapters/Microsoft.Bot.Builder.Adapters.Twilio/TwilioAdapter.cs
1
85.71%

/libraries/Adapters/Microsoft.Bot.Builder.Adapters.Webex/WebexAdapter.cs
1
95.41%

/libraries/integration/Microsoft.Bot.Builder.Integration.ApplicationInsights.Core/ApplicationBuilderExtensions.cs
1
71.43%

/libraries/Microsoft.Bot.Builder/ActivityHandler.cs
1
9.72%

/libraries/Microsoft.Bot.Builder.AI.LUIS/LuisApplication.cs
1
95.45%

/libraries/Microsoft.Bot.Builder.Dialogs/Prompts/PromptValidatorContext.cs
1
82.35%

/libraries/Microsoft.Bot.Builder.Dialogs/WaterfallStepContext.cs
1
86.96%

/libraries/Microsoft.Bot.Builder/TelemetryLoggerMiddleware.cs
1
57.58%

/libraries/Microsoft.Bot.Builder.Testing/XUnit/TestDataObject.cs
1
82.35%

/libraries/Adapters/Microsoft.Bot.Builder.Adapters.Twilio/TwilioClientWrapper.cs
2
0.0%

Totals

Change from base Build 80016:
-1.3%

Covered Lines:
4891

Relevant Lines:
6116

💛  - Coveralls

:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.Luis.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.QnA.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.ApplicationInsights.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Azure.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Dialogs.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.TemplateManager.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Configuration.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Connector.dll compared against version 4.3.1
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Schema.dll compared against version 4.3.1


Tab complete does not honor requires()

Registering a client command that has a requires() check does not remove it from tab complete like it does on the server.
Accepting the completion shows an immediate syntax error and highlights the command in red, so the requirement is recognized, but the tab complete isn't honoring it.
Minecraft 1.16.3, Fabric Loader v0.10.0+build.208, Fabric API 0.22.0+build.408-1.16
Workaround: Just don't register the command. Works in my case as my requires() check was "integrated server is absent", but more complex checks don't have that luxury.

So this is the result of a fundamental difference between commands originating on the server and client act. A command registered on the server will go through the requires check and will be omitted from the command tree the client receives if a player cannot access the command.
Likewise the command dispatcher on the client has no filtering of these "inaccessible" nodes, so some internal logic changes would be required to handle that.

I see; still getting used to Brigadier.
If this is complicated to implement it's probably not worth bothering. Just noticed the discrepancy between server and client command behavior.

Juuz has been working on integrating this into fabric api, so fixing this is going to be essential.

I did this for the Fabric API PR (FabricMC/fabric#1115), but it'd need quite a lot of modification to fit CCC so I'm not most likely going to port them here. (If it doesn't get merged, I'll probably reuse the FabLabs API as a new major version of CCC.)


gnome3.gnome-contacts: 3.38 -> 3.38.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for gnome3.gnome-contacts is: "GNOME’s integrated address book"
meta.homepage for gnome3.gnome-contacts is: "https://wiki.gnome.org/Apps/Contacts"
meta.changelog for gnome3.gnome-contacts is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 3.38.1 with grep in /nix/store/j34fin4cc9agpccbazpl51acjcgf78d1-gnome-contacts-3.38.1

directory tree listing: https://gist.github.com/3cf294db7866b8712f018b0b0b6df086

du listing: https://gist.github.com/93652b4c2c2a475de7c741b1821a0223

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
0 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
gnome3.gnome-contacts

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/j34fin4cc9agpccbazpl51acjcgf78d1-gnome-contacts-3.38.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A gnome3.gnome-contacts https://github.com/r-ryantm/nixpkgs/archive/38c53054bd6a47ee94bc6d5b9dcdac1db54a1130.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/j34fin4cc9agpccbazpl51acjcgf78d1-gnome-contacts-3.38.1
ls -la /nix/store/j34fin4cc9agpccbazpl51acjcgf78d1-gnome-contacts-3.38.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review 1

1 package failed to build:

gnome3.gnome-contacts

Maintainer pings
cc @hedning @jtojnar @worldofpeace @dasj19 for testing.

Duplicate of #104074.


Check that result contains expected allergens

Fixes #130
Testing for all allergies would fail if the allergens weren't in the
same order as the test vector.
This checks that the result contains all the expected allergens rather
than expecting the result and test vector to be equal.

Good change!
I would add one more test: that all and allergies have the same number of elements. If allergies contains Eggs twice, for example, it'd pass that test but still have a failure somewhere in its implementation.

Are we missing this test in https://github.com/exercism/x-common/blob/master/allergies.json?

Oh wait, do you mean check that all and allergies have the same number of elements in a completely different test? I think that makes more sense.

Same test or different test, I don't think I have a strong opinion. I'm happy to merge this as-is.
@kytrinyx, I think the tests in the json file are fine. This is just a way to make the canonical tests work for Rust, while still handling the weird edge case that could emerge because of our testing approach.

Great! I'll leave it alone then. No need to over-complicate things.

Fireworks. Marching Bands. Etc. Thank you!


[Quantization] Update AWQ Kernel to Latest Implementation

This PR bring in some of the latest kernels from AWQ. It is known that the currently AWQ kernels are not optimized. I looked up the original repo. The kernel have changed from gemm_forward_4bit_cuda_m16n128k32 to a collection of gemm_forward_4bit_cuda_m128n64k32 as well as gemv_kernel_g64/gemv_kernel_g128. I think this indicates better tuning.
https://github.com/mit-han-lab/llm-awq/blob/main/awq/kernels/csrc/quantization/gemv_cuda.cu,
https://github.com/mit-han-lab/llm-awq/blob/19a5a2c9db47f69a2851c83fea90f81ed49269ab/tinychat/modules/fused_mlp.py,
https://github.com/mit-han-lab/llm-awq/blob/main/awq/kernels/csrc/quantization/gemm_cuda_gen.cu
I tried to bring in the kernels but was stuck at the implementation, due to my limited knowledge of the quantization stack.
Here's a shape error that I ran into

```
~/vllm/benchmarks$ python benchmark_throughput.py --model TheBloke/Llama-2-7B-Chat-AWQ --input-len 512 --output-len 512 --num-prompts 10
Namespace(backend='vllm', dataset=None, input_len=512, output_len=512, model='TheBloke/Llama-2-7B-Chat-AWQ', tokenizer='TheBloke/Llama-2-7B-Chat-AWQ', quantization=None, tensor_parallel_size=1, n=1, use_beam_search=False, num_prompts=10, seed=0, hf_max_batch_size=None, trust_remote_code=False, max_model_len=None, dtype='auto')
WARNING 12-01 08:25:34 config.py:140] awq quantization is not fully optimized yet. The speed can be slower than non-quantized models.
INFO 12-01 08:25:34 llm_engine.py:72] Initializing an LLM engine with config: model='TheBloke/Llama-2-7B-Chat-AWQ', tokenizer='TheBloke/Llama-2-7B-Chat-AWQ', tokenizer_mode=auto, revision=None, tokenizer_revision=None, trust_remote_code=False, dtype=torch.float16, max_seq_len=4096, download_dir=None, load_format=auto, tensor_parallel_size=1, quantization=awq, seed=0)
INFO 12-01 08:25:34 tokenizer.py:31] For some LLaMA V1 models, initializing the fast tokenizer may take a long time. To reduce the initialization time, consider using 'hf-internal-testing/llama-tokenizer' instead of the original tokenizer.
Traceback (most recent call last):
  File "/home/xmo/vllm/benchmarks/benchmark_throughput.py", line 313, in
    main(args)
  File "/home/xmo/vllm/benchmarks/benchmark_throughput.py", line 203, in main
    elapsed_time = run_vllm(requests, args.model, args.tokenizer,
  File "/home/xmo/vllm/benchmarks/benchmark_throughput.py", line 75, in run_vllm
    llm = LLM(
  File "/home/xmo/vllm/vllm/entrypoints/llm.py", line 93, in __init__
    self.llm_engine = LLMEngine.from_engine_args(engine_args)
  File "/home/xmo/vllm/vllm/engine/llm_engine.py", line 241, in from_engine_args
    engine = cls(*engine_configs,
  File "/home/xmo/vllm/vllm/engine/llm_engine.py", line 111, in __init__
    self._init_cache()
  File "/home/xmo/vllm/vllm/engine/llm_engine.py", line 203, in _init_cache
    num_blocks = self._run_workers(
  File "/home/xmo/vllm/vllm/engine/llm_engine.py", line 735, in _run_workers
    self._run_workers_in_batch(workers, method, *args, **kwargs))
  File "/home/xmo/vllm/vllm/engine/llm_engine.py", line 709, in _run_workers_in_batch
    output = executor(*args, **kwargs)
  File "/opt/conda/lib/python3.10/site-packages/torch/utils/_contextlib.py", line 115, in decorate_context
    return func(*args, **kwargs)
  File "/home/xmo/vllm/vllm/worker/worker.py", line 88, in profile_num_available_blocks
    self.model_runner.profile_run()
  File "/opt/conda/lib/python3.10/site-packages/torch/utils/_contextlib.py", line 115, in decorate_context
    return func(*args, **kwargs)
  File "/home/xmo/vllm/vllm/worker/model_runner.py", line 318, in profile_run
    self.execute_model(seqs, kv_caches)
  File "/opt/conda/lib/python3.10/site-packages/torch/utils/_contextlib.py", line 115, in decorate_context
    return func(*args, **kwargs)
  File "/home/xmo/vllm/vllm/worker/model_runner.py", line 276, in execute_model
    hidden_states = self.model(
  File "/opt/conda/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1518, in _wrapped_call_impl
    return self._call_impl(*args, **kwargs)
  File "/opt/conda/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1527, in _call_impl
    return forward_call(*args, **kwargs)
  File "/home/xmo/vllm/vllm/model_executor/models/llama.py", line 294, in forward
    hidden_states = self.model(input_ids, positions, kv_caches,
  File "/opt/conda/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1518, in _wrapped_call_impl
    return self._call_impl(*args, **kwargs)
  File "/opt/conda/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1527, in _call_impl
    return forward_call(*args, **kwargs)
  File "/home/xmo/vllm/vllm/model_executor/models/llama.py", line 260, in forward
    hidden_states, residual = layer(
  File "/opt/conda/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1518, in _wrapped_call_impl
    return self._call_impl(*args, **kwargs)
  File "/opt/conda/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1527, in _call_impl
    return forward_call(*args, **kwargs)
  File "/home/xmo/vllm/vllm/model_executor/models/llama.py", line 211, in forward
    hidden_states = self.self_attn(
  File "/opt/conda/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1518, in _wrapped_call_impl
    return self._call_impl(*args, **kwargs)
  File "/opt/conda/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1527, in _call_impl
    return forward_call(*args, **kwargs)
  File "/home/xmo/vllm/vllm/model_executor/models/llama.py", line 152, in forward
    qkv, _ = self.qkv_proj(hidden_states)
  File "/opt/conda/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1518, in _wrapped_call_impl
    return self._call_impl(*args, **kwargs)
  File "/opt/conda/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1527, in _call_impl
    return forward_call(*args, **kwargs)
  File "/home/xmo/vllm/vllm/model_executor/layers/linear.py", line 203, in forward
    output_parallel = self.linear_method.apply_weights(
  File "/home/xmo/vllm/vllm/model_executor/layers/quantization/awq.py", line 165, in apply_weights
    return out.reshape(out_shape)
RuntimeError: shape '[256, 16, 12288]' is invalid for input of size 16777216
```

I hope this PR can be picked up and made working. At least we can benchmark the new kernels against the old ones. (@WoosukKwon would you be able to play with this? it might be quite straightforward for you to fix since you wrote the initial code.)

@simon-mo Thanks for looking into the newer kernels. Unfortunately, I have to inform you that the new kernels are much slower than the original GEMM kernel.
This is simply due to GEMV only being designed for batch size 1, so that it runs on edge devices which is part of the focus of studies that the MIT Han Lab focuses on.
The original GEMM kernel is better optimized and although slower in vLLM due to the limitations of the implementation, it will still speed up if you use a batch size of 8 or less, and in some cases, it is faster up to batch size 16.
Woosuk is working on a Triton kernel in the qmm branch, unsure what the latest progress is on it, but he said that it’s supposed to scale better when it is finished.

@casper-hansen Thanks for sharing!
@simon-mo

GEMV kernel: I agree with @casper-hansen. It's not very in our setting.
Updates in GEMM kernel: I think we don't need to import it unless there's a significant performance boost. Also, we added T4 GPU support (#1252) on top of the original kernel. So the kernel implementation already diverged.
New kernel: As @casper-hansen mentioned, I do have a Triton kernel for AWQ. I will integrate it once the torch.compile/CUDA graph stuff is merged.

Regarding the updated GEMM kernel: The update to the GEMM kernel was only made to support faster prefilling and is not meant to be used for decoding. The updated GEMM kernel was implemented because the GEMV kernel alone is roughly 10x slower than the original GEMM kernel. However, it is still 5x slower at prefilling than the original GEMM.


Feature: Redesign  Feedback input box of feedback page (Screenshot ATTACHED)

The current Feedback box is not looking good as you can see from the !st screenshot but I want to make some changes and made it look like the second Screenshot which is looking quit nice than the previous one. So assign me this task So that I could fix  the feedback input

I am GSSOC contributor, I would like to redesign the feedback form.

@bhaskarkumar1 this UI change is too minor to add a GSSoC tag, provide some more changes to make it look a little better.


No Freeos token was minted when minting POINT to FREEOS using mintfeefree allowance.

14/6/22 freeosgov2 v0.9.19, Iteration = 459772
When minting POINT to FREEOS using mintfeefree allowance only. No FREEOS token was minted.
User: vivvestin, eosio.tokens account=49.0000 XPR
Steps:

Load 100.0000 POINT to vivvestin mintfeefree allowance using setmff action.
Run mintfreeos action-> user=vivvestin, input_quantity=1.0000 POINT, mint_fee_currency= 4,XPR
Mintfreeos action successful.
mintfeefree allowance reduced from 100.0000 to 99.0000 POINTs. Correct.
No FREEOS token was minted. freeostoken5 account (vivvestin)=No data. Expecting 1.0000 FREEOS to be minted.
freeosgov2 account (vivvestin) balance remained the same. Expecting it to be reduced by 1 POINT after minting.

21/6/22 Retest scenario in freeosgov2 v0.9.21 iteration: 459935, user=vivvestin
mintfreeos action failed-> Error assertion failure with message: the correct mint fee has not been paid.
Tom looking into issue.

21/6/22 Retest scenario in freeosgov2 v0.9.22 iteration: 459936, user=vivvestin
mintfreeos action failed->Error assertion failure with message: tokens can only be issued to issuer account. Tom working on it.

21/6/22 Retest scenario in freeosgov2 v0.9.22 iteration:459937 Success. Fixed.


input is losing focus in FieldArray .

FieldArray is generating List of RadioButtons and meanwhile, some RadioButtons are rendering Input box. So while I am updating the value in Input Box focus is getting lost. I don't know why DOM is re-rendering again and root Object is changing. So is there any open Bug, or need any suggestion to change the code/syntax. I am using React-16 and redux-Form 7.0.2
<FieldArray name='commuteDeductions'
                        listData={COMMUTE_DEDUCTION_LIST}
                        label="18. Commute Deduction"
                        clearSubComponent={clearSubComponent}
                        component={ListItem }/>

const ListItem = ({fields, listData, label, clearSubComponent, meta: {error, submitFailed}}) => {

    return (

            {label &&  { label } }
            {
                fields.map((option, index) => {
                    return

                        <Field
                            name={`${fields.name}-radio`}
                            type="radio"
                            component={RadioButton}
                            value={listData[index].id}
                            onChange={()=> clearSubComponent(PROGRAM_DRIVERDETAIL, `${fields.name}-radio-inputBox`, '')}
                            item={listData[index]} />

                })
            }
            <span className={`error error-msg ${ (submitFailed  && error) && 'visible' } `}>{error}

    )
};

const RadioButton = props => {
    let {input, item, meta:{touched, error}} = props;

    return (<React.Fragment>
        <input
            type="radio"
            id={item.id}
            {...input} />
        {item.labelName}
        {input.checked && item.subComponent && <Field name={`${input.name}-inputBox`}
                                                      customplaceholder={item.subComponent.postFix}
                                                      className="expra-space-down sub-comp"
                                                      subItem={item.subComponent}
                                                      subtitle={item.subComponent.labelName}
                                                      id={item.subComponent.id}
                                                      validate={[required, number, minValue1, valueRange1To99]}
                                                      component={CustomInput}/>
        }
    </React.Fragment>)
};

const Input = ({input, meta: {touched, error}}) => (
    <React.Fragment>
        <input {...input} />
        {touched && error && {error}}
    </React.Fragment>
);

Please provide a reproducible sandbox.
Also make sure that you aren't falling in this classic trap: https://github.com/erikras/redux-form/issues/1836#issuecomment-328293635

I have been written my code in SandBox but right now I am unable to debug why it's not rendering in correct format. BTW link is https://codesandbox.io/s/p93ryrvqo7

Hi, sorry for the delay here.
Seems like your issue is on the usage of uuid.v4() to generate key props in your FieldArray.
Every time it re-renders, instead of reusing the already existing structure, React will recreate the whole field tree, as it was given a different key.
Change it to something else (eg index, or an id property of your own on each field's value).

@gustavohenke Yes, I already got that and one more issue in Validation. If validation rules are provided in array Field will be registered and unregister itself at every render.


Undefining macro [max]

Macro [max] is included and makes it impossible to use [std::max] unless it's undefined again.

https://github.com/pps83/mio/commit/73266266f52e500d6f795a46e4bad259ba85347d


docs: Steps for migrating to Envoy Gateway

Description:
Add a doc that can help users who want to migrate to Envoy Gateway
Would be great to highlight the ingress2gateway https://github.com/kubernetes-sigs/ingress2gateway/tree/main tool with an example

@arkodg I am interested in  working on this issue, Can you just tell me in which section of documentation I have to do add this.

thanks for looking into this @Manoramsharma , https://gateway.envoyproxy.io/docs/install/ is a good home for a migration doc


improve encoding/decoding interface handling

fixes #28

@zeebo added a couple of more unit test cases for the encoding code.
This PR is ready for review now :)

Now it should be possible to have a (child) value being marshaled using the (Text)Marshaler, and unmarshaled  using the Text(Un)Marshaler, no matter if it was implemented as a pointer type or a value type, and no matter how it was passed in.
The reasonable exception to this is when a value was implemented as a pointer type, but was passed in as a value type and thus isn't addressable, or it is a child value of another value which cannot be addressed and thus is therefore also not addressable. Examples:
// MarshalBencode implements Marshaler.MarshalBencode
func (t *myType) MarshalBencode() ([]byte, error) {
	// ...
}

With the type of above in mind, the following examples will not be marshaled using the Marshaler interface, as it is impossible to get them by reference within the encoding code:
// passed in by value, thus not addressable
bencode.EncodeBytes(myType{})

// passed in as part of a struct which is passed by value,
// which makes the struct and by extension the child value(s) not addressable
bencode.EncodeBytes(struct{
    MT myType
}{MT: myType{}})

If such scenarios will occur, it will be marshaled instead using the TextMarshaler if possible. And if that's not possible and it is not a RawMessage, it will be marshaled using its Go Type default encoding behavior.
As counter examples, the following cases are possible and here myType will be marshaled using the Marshaler interface:
// passed in by value, thus addressable
bencode.EncodeBytes(&myType{})

// passed in as part of a struct which is passed by reference,
// which makes the struct and by extension the child value(s) addressable
type myStruct struct{
    MT myType
}
bencode.EncodeBytes(&myStruct{MT: myType{}})

However I'm fairly sure that the interfaces should now be supported for all scenarios where they are expected to work. I think at this point if your value does not get (un)marshaled using the interface of your choice, than you are probably doing something that you shouldn't be doing in the first place. And even if that should happen, there is still a reasonable fall-back scenario.


DeleteAccountService should delete the user and then recreate it

https://github.com/nuget/engineering/issues/2358
This guarantees that the deleted user is completely purged from the DB while not requiring any schema changes.

Does this actually clear the existing relationships? In your design spec you mentioned the "pushed by user" relationship on the "Packages" table. How is that getting cleared out?
Do we have some custom SQL in migrations already that is doing the proper cascade in all cases?

@joelverhagen - The relationship doesn't get cleared out--fixing bugs with the DeleteAccountService will be done separately from this change. What this change guarantees is that if there are any FK relationships on the user row that was deleted, the delete commit will fail because the new row will have a different key.

Closing this. We should reopen if we determine that we would like to do this.


Artist names collide on small screen sizes

by @anuragsai97

We can fix that by reducing the font size when the screen goes around  800px wide right ?
@rhnvrm

iirc, it will still bug on xs screens even with changing font sizes. Better
to change xs layout to 1-3-3 from 1-2-4.
Take liberty and decide what is best, post screenshots first and we can
discuss how to resolve this in the best way
Sincerely,
Rohan Verma
<EMAIL_ADDRESS>On 19-Jul-2016 11:40 am, "Harshit Budhraja"<EMAIL_ADDRESS>wrote:

We can fix that by reducing the font size when the screen goes around
800px wide right ?
@rhnvrm https://github.com/rhnvrm
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/snu-breeze/breeze-landing/issues/23#issuecomment-233541013,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA6G5FND9AJPJB8eegXrILfqNdIp86YGks5qXGpIgaJpZM4JO4WU
.

@harshitbudhraja any update on the progress?

@rhnvrm, I just started working on it....Changed to 1-3-3....It fixes the problem

@harshitbudhraja yes with screenshots if possible using chrome dev tools

Think this should be closed now ! What say @rhnvrm ?


JSON formatter on result objects

Add JSON formatter on C# result objects. Do a proof-of-concept for the user to test for one specific result object like NodalDisplacement. Wait for feedback before full implementation.

reference
https://gist.github.com/brainded/8698865

What is the purpose of this? :)

User wants to dump results to company DB in JSON.

.NET 5 and 6 have JSON namespace built in while .NET Framework needs to add an extra dependency such as Newtonsoft.Json

@andosca
Here an example where the user can just use the extension method ToJSON() to any IResult or List object.
https://github.com/strusoft/femdesign-api/tree/21.6.0_Branch/FemDesign.Examples/C%23/Practical example - ResultsToJSON

Ah. I haven't thought about Grasshopper.
I think we shouldn't implement a new component to export to JSON as we will end up having thousands of not necessary features in our Gh toolbox.
Most Grasshopper users knows that they can use JSWAN for such task.
In my opinion, we should show the user how to do it with a custom C# component or with JSWAN.

It is also fine to add a single component "ToJSON" but I was trying to do some selection to avoid a huge library.
If you think that it is worth it, we can create a custom component that reflect what @xRadne has just been done.

This is great! Thanks


Clank should reply to commands using DMs instead of public channels

To avoid being very noisy, Clank should reply the user using DMs instead of publicly mentioning the user in the channel the user typed the message in.
In some cases, such as when triggering the !helper command, Clank may attempt to automatically delete the triggering message to clean up the conversation.

This cannot be done because many users will have their DM settings set to Only friends.


[cinder-csi-plugin] Add extraEnv support on cinder-csi-plugin and manila-csi-plugin helm charts

What this PR does / why we need it:
Add extraEnv support on the cinder-csi-plugin helm chart.
Which issue this PR fixes(if applicable):
Special notes for reviewers:

One example use case of extraEnv:  In some of our private customer cloud, cinder-csi-plugin must access the openstack API endpoint with following env variable  http_proxy, https_proxy, no_proxy.
Release note:

NONE

/ok-to-test
Looks like this could be useful for the Manila CSI charts too? Could you add it there as well?

Looks like this could be useful for the Manila CSI charts too? Could you add it there as well?

Thanks for the approval.
Yes,  i will try to add here also the modification for Manila CSI charts.

Added for manila
@dulek , Is that okay with you ?

Looks good, just why do you comment out Manila's values.yaml, but not Cinder's?

Looks good, just why do you comment out Manila's values.yaml, but not Cinder's?

mistake
it s now fixed

/approve

/lgtm


How to register a helper function for if statements?

If I want to make a greater than operator, how can I do it?
            Handlebars.RegisterHelper("gt", (writer, context, parameters) => {
                int a = (int)parameters[0];
                int b = (int)parameters[1];
                return a > b;
            });

doesn't work.

What do you mean by "doesn't work"?

@TheInvoker assuming this is what you're trying to achieve:
{{#gt foo bar}}
    {{foo}} is greater than {{bar}}
{{else}}
    {{foo}} is not greater than {{bar}}
{{/gt}}

you'll want to register a Block Helper rather than a Helper.
Like so:
Handlebars.RegisterHelper("gt", (writer, options, context, arguments) => {
    int a = (int)arguments[0];
    int b = (int)arguments[1];
    return (a > b)
        ? options.Template(writer, (object)context)
        : options.Inverse (writer, (object)context);
});

Closing due to inactivity


chore: use new k8s registry

Checklist

[x] Commits are signed with Developer Certificate of Origin (DCO - learn more)

Relates to https://github.com/kubernetes/k8s.io/issues/4780

/run-e2e


Turning features on/off crashes the settings UI

Microsoft PowerToys version
0.75.1
Installation method
GitHub
Running as admin
Yes
Area(s) with issue?
Settings
Steps to reproduce
Open settings, select feature e.g 'Color Picker' switch feature enabled to 'off'
✔ Expected Behavior
Feature switches to 'off', settings UI remains open
❌ Actual Behavior
UI hangs and crashes/closes
Event viewer application error entry:
Faulting application name: PowerToys.Settings.exe, version: <IP_ADDRESS>, time stamp: 0x653067fb
Faulting module name: KERNELBASE.dll, version: 10.0.19041.3636, time stamp: 0x326edcef
Exception code: 0xc000027b
Fault offset: 0x000000000012db22
Faulting process id: 0x3fe0
Faulting application start time: 0x01da24ae4906f1f9
Faulting application path: C:\Program Files\PowerToys\WinUI3Apps\PowerToys.Settings.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report Id: 7977a0a6-3ee6-4751-adf9-d9686bb254cb
Faulting package full name:
Faulting package-relative application ID:
Other Software
No response

Not able to repro this, going to close. Let us know if you see this again!


Confirm support for Python 3

It looks like this library supports python 3, but I'm not 100% sure. If so, could you make it so that this tool doesn't report the library as blocking:
https://caniusepython3.com/project/Logentries
I think what you need to do is add classifiers to setup.py like this:
classifiers=[
'Programming Language :: Python :: 2',
'Programming Language :: Python :: 3',
]

We probably need tests to validate if this works with python 3. From what I understand in how the library works, it probably won't work well with python3 due to the way the 'msg' line is processed.

also Queue is from Python 2

I'm using with python3 in production in more than one year, and only two problems than I found ( #46 and #53 I don't understand why this PRs is not merged =/ )


Rise/Kit: Support SVGs

The kit should have a component for rendering SVGs from the server

Or more likely - @rise-tools/kit-svg!


Make the compiler accept Json configuration files

The compiler can be used from different contexts:

from the Gradle plugin (current)
from a Gradle worker (needed for compiler APIs)
from Maven

In order to make it easier to work in these different contexts, make the compiler accept JSON configuration files.
Instead of having conventions and default behaviours in the Gradle Plugin, they are now in the Compiler.

This should now be ready for review.  Initial description updated.


menu system broken?

Hi
I'm relativ new to hugo and trying to get startet with it. For better understanding I played a bit with some simple test pages. For more complex testing I cloned the Hugo Docs repository and compiled it with the latest hugo version on my system.
I do not understand why the menu system is missing an Item. In the config.toml file the main menu contains a Item "Theme Showcase" with the weight -170. But this Item is not rendered.
Btw. it is also missing on the official hugo site ;-)
If I change the weight to -165 the Item get's rendered and displayed on the site. If I change the weight to anything above -169 the Item is not rendered, but the Items "Site Showcase" and "Download Hugo" which are -180 and -200 weighted are rendered always.
Am I doing something wrong here or misunderstanding the weight system?

Thanks for getting in touch, but it feels like this is a question  that would be better suited to the Hugo Discussion Forum.  We prefer to use GitHub issues only for bugs and enhancements. Feel free to update this issue with a link to the re-posted question (so that other people can find it) or add some more details if you feel this is a genuine bug. You may also find the answers you search for in Hugo Documentation.


Switching cameras / facingmode in ios

Switching cameras in live stream on ios ipad do not work, only the user mode/camera appears twice.
How could i include a switch of the facing mode instead switching the camera?
I tried to include something like this:
https://medium.com/@leemartin/hello-webrtc-on-safari-11-e8bcb5335295
Switching the Facingmode works great but no stream will be sent.
Thanks.

same problem.

@Crunky @chungnt92 - Did you figure out how to switch the camera on safari iOS?


Mobile tutorials review

I've reviewed the mobile tutorial update, these are my requested changes
Very good job guys! :)

Thanks for doing this @victorg1991!


FLock template

FLock template add.

Thanks for this @fengzz-coding - a couple comments (as discussed in slack):

Will be great if you could add a little more context (at least what and why. Ideally a video if possible) in the readme. This will help boost usage of it. Here is a good recent example of one https://github.com/akash-network/awesome-akash/blob/master/vllm/README.md
May want to consider not filtering GPUs - so user gets more bids

@Dimokus88 - could you please review/ test/ merge when you have the chance?

The main check is in progress.
There are currently some issues that need to be addressed before inclusion in the awesome-akash repository:

Add a Dockerfile of the image public.ecr.aws/e7z6j8c3/flock:llm-loss-validator-gpu-latest . Also, if there is an executable script inside the image, they also need to be added as a file.

You need to add information about your template to the root README.md of the awesome-akash repository

For the Docker build, you can refer to this https://github.com/FLock-io/llm-loss-validator/blob/main/Dockerfile-gpu.  What else needs to be provided for this?

It is necessary that users know what kind of image will be deployed (and, if desired, could assemble it themselves). This is why there is a need to publish a Dockerfile for custom images. Or add a link to the Dockerfile in your README.md

SDL looks working.
But it is necessary to clarify/correct the recommendations above.
Adding information to README.md and publishing a Dockerfile (or a link to it). Users need to see what they are deploying.

Thx @fengzz-coding !
Looks ready to merge @anilmurty !

Thanks @Dimokus88


Compatibility with PyTorch 0.4

Hi, Thanks for the nice package and code. I had a few issues in runnig the code on PyTorch 0.4, especially in reading the model. I saw a few similar open issues which people sugessted to change the verison to PyTorch 0.2. Since Most of the recent packages are based on PyTorch 0.4+, and I wasn't intrested in use the conda solution or downgrading, I spent time to find a way to run the code. This issue is just for sharing the location that you may need to change for the recent version of the PyTorch:
1- Loading the pre-trained model issue:
OrderedDict "checkpoint['state_dict']['FeatureExtraction.model.1.num_batches_tracked']" does not exist I'd appreciate it if you could check for the error.
To solve this you need to find the comman names between this pretrained checkpoint and TwoStageCNNGeometric model namespaces.
    if model_aff_tps_path != '':
        checkpoint = torch.load(model_aff_tps_path, map_location=lambda storage, loc: storage)
        checkpoint['state_dict'] = OrderedDict(
            [(k.replace('vgg', 'model'), v) for k, v in checkpoint['state_dict'].items()])

        for name, param in model.FeatureExtraction.state_dict().items():
            if 'FeatureExtraction.' + name in checkpoint['state_dict']:
                model.FeatureExtraction.state_dict()[name].copy_(checkpoint['state_dict']['FeatureExtraction.' + name])
        for name, param in model.FeatureRegression.state_dict().items():
            if 'FeatureRegression.' + name in checkpoint['state_dict']:
                model.FeatureRegression.state_dict()[name].copy_(checkpoint['state_dict']['FeatureRegression.' + name])
        for name, param in model.FeatureRegression2.state_dict().items():
            if 'FeatureRegression2.' + name in checkpoint['state_dict']:
                model.FeatureRegression2.state_dict()[name].copy_(checkpoint['state_dict']['FeatureRegression2.' + name])

The other optimum way is to add a more pythonic statement when you are generating the checkpoint and make a OrderedDic, something like:
 [(k.replace('vgg', 'model'), v) for k, v in checkpoint['state_dict'].items() if v in model.FeatureExtraction.state_dict()])

but I it doesn't work like this definitly and I couldn't find an optimum way anyway, so I ended up to add the explicit if statements.
2- The second issue is happening later on, in preprocess_image(), normalize_image() in ./image/normalization.py, line 38
if isinstance(image,torch.autograd.variable.Variable):
....

The fact is in the classes Tensor and Variable got merged in newer version of PyTorch, so there is no need to check if image is a Variale type and so on.
So, you can easily replace this wholeline by "else:"
Hope this would be helpful for others too.

Hi, could you give us your modified code?

Thanks, your suggestions work perfectly.


Rerunning a report succeeds while an output message is different

I copied a report to the test tab and then I edited it. I wanted to see that rerunning a report can fail. Instead, the report succeeded. When I clicked compare I could see the difference I expected from my edit:

I would expect that rerunning this report would fail.

The default xslt will only get the first and last message of the report which are then compared to determine success or not. You can change the xslt or make the person name end up in the last checkpoint

@jacodg and @MatthijsSmets, does this mean we can close this issue?


🚀[FEA]: Add gradient clipping to StaticCaptureTraining performance optimization decorator

Is this a new feature, an improvement, or a change to existing functionality?
Improvement
How would you describe the priority of this feature request
Low (would be nice)
Please provide a clear description of problem you would like to solve.
Add gradient clipping support to the performance optimization decorator. The performance optimization decorator doesn't support Gradient Clipping. This prevents its use for applications that require gradient clipping.
Describe any alternatives you have considered
No response

Fixed in #660


106-BE/bitstreams-not-correctly-imported

Problem description
Some bitstreams are imported with files from assetstore, but when one fails others are not imported also..
Fixed here: https://github.com/dataquest-dev/dspace-python-api/issues/23

Fixed here: https://github.com/dataquest-dev/dspace-python-api/issues/23


Wait For Response's response display Error 'the JSON object must be str, bytes or bytearray, not NoneType'

Describe the bug
The response of keyword Wait for Response display Error 'the JSON object must be str, bytes or bytearray, not NoneType'
To Reproduce
Open a site and wait for the page information loaded using the Wait For Response keyword to check if the API is returning data.
Expected behavior
Response did not display error and able to parse the data
Sample Error

This is the sample API response :
{     'status': 200,     'body': '{"full_name":"sample full name","email":"sample@mail.com","div_id":"2345","save_id":"1111","page":0}',     'headers': {         'pragma': 'no-cache',         'date': 'Fri, 12 Apr 2024 18:01:11 GMT',         'content-encoding': 'gzip',         'x-powered-by': 'Sails <sailsjs.com>',         'etag': 'W/"80c-asdfasdvqw4taef"',         'vary': 'Origin, Accept-Encoding',         'content-type': 'application/json; charset=utf-8',         'access-control-allow-origin': 'https://url.com',         'cache-control': 'private, no-cache, no-store, must-revalidate',         'access-control-allow-credentials': 'true',         'expires': '-1'     },     'statusText': '',     'url': 'https://url.com/api/load?rec_id=23886&div_id=6449',     'ok': True,     'request': {         'headers': {             'sec-ch-ua': '"Not A(Brand";v="24", "Chromium";v="110"',             'content-type': 'application/json',             'referer': '',             'sec-ch-ua-mobile': '?0',             'authorization': 'Bearer wasdfhuiowyerbsdfuiwelrbsdliufy',             'user-agent': 'Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36',             'sec-ch-ua-platform': '"Windows"'         },         'method': 'GET',         'postData': None     } }
Desktop (please complete the following information):

OS: Windows 10
Browser : Chrome
robotframework-browser==16.0.0 (also reproducible in 18.xx)

Additional context
Upon investigation, was able to fix the issue by converting first the data by using dumps() then proceed on loads() on method _jsonize_content() on file network.py.
See screenshot.

Hope this help since this is crucial on our automation script to wait the data loaded before proceeding the flow.

@allcontributors please add @nfaustin for bugs

Are you interested to do a PR to fix the problem?

Confirmed issue is fixed now in latest 18.4.0. Thanks.


Avoid printing object hashes in log messages related to containers

I'd like to request a PG exemption.

Merged as https://github.com/openwhisk/openwhisk/commit/f63b5359c12a55d1ff2a890a7b1fba8b6224dc75.


Setup automatic releases for packages

Automatic releases are amazing, and a great feature to have when quickly making and maintaining packages.

Already did this 😄


Make shared OpenSSL the default

Currently nodejs builds by default with the internal OpenSSL. From an OE point I think it would be better to use the the shared openssl by default.
This would also solve the path to long issues.
Maybe the same is true for shared zlib?

I've been thinking the same thing myself. 👍 for this effort.
I agree that using shared OpenSSL would be better for OE builds. However, I'd still keep zlib internal. It's trivial in size and having Node.js maintain it's own patch sets and integration for the zlib feels more safe choice. zlib has never caused any issues.
I've been following the work around Node.js core and it's integration with zlib and especially OpenSSL. Node.js is very specific about the OpenSSL version used and while compiling with shared OpenSSL is allowed, it's definitely not recommended.
We have to be careful when defining OpenSSL dependency so that too obviously incompatible version wont be accidentally used; if such limitation is reasonably possible. Using incompatible shared OpenSSL could cause catastrophic and very hard to diagnose bugs for end users.

I don't think we can guarantee the correct OpenSSL version in OE other than using the correct branch. (krogoth<->krogoth).
I just checkend and for example Debian seems to be using external OpenSSL and zlib for their nodejs package too.
We are also using it with shared zlib and openssl via the PACKAGECONFIG without problems on the krogoth branch.
But I understand your concern and I can live with the PACKAGECONFIG options that are already available

I'd say we make the switch and see how it goes?
Default to shared libs.
I'll test for jethro as I want to keep supporting it for a while without branching too far from krogoth/master.


Pc mode camera issue

When using the table in pc mode, pressing E just shows a solid black screen instead of the top down view.

Might have to do with your culling settings ; try to change the culling settings of the camera used by vrcbce.

Might have to do with your culling settings ; try to change the culling settings of the camera used by vrcbce.

I don't recall there being a camera in the prefab, do you have to manually link one?

The top view is done by using a camera, there's one in the prefab somewhere ; I can't give more informations right now since i'm on phone ! sorry

Could you provide some more detail (screenshots of your hierarchy/inspector would help) as well as the world you're reproducing this in?

Could you provide some more detail (screenshots of your hierarchy/inspector would help) as well as the world you're reproducing this in?

not sure which parts of the inspector you need but here is this

ah heck, just noticed the desktop camera one, its to high, above the ceiling of the building.


problem in year 1397 , first month, no 1397/01/02 available!

Hi,
There something wrong in day-picker
In year 1397 , there is not date 1397/01/02
!!

Hi,
thank you
its fixed. the demo

Dear
Would you please update Npm version also?

it has updated already its 2.2.1.
plunker demo uses the last version and its OK.


Server connection won't close

It seems to be an issue with MongolianServer._connection not having a cached value until one of the connections callbacks is called, it fixes the issue of you call the callback right away.
it doesn't break any of the existing tests, but I couldn't think of a clever way to test this without digging into internals.

https://github.com/marcello3d/node-mongolian/pull/67

I don't get it, how can i close the connection? my script won't finish!

force your script to close the server connection in a callback that actually uses one of the collections, say, listing the available indices for the collection.
      getCollection (err, collection) ->
        collection.indexes (err, indexes) ->
          server.close()


add twitter badge

addresses point 3 of https://github.com/bids-standard/bids-specification/issues/266

here is the rendeirng - https://franklin-feingold.github.io/BIDS/


fix A global filter has been set for the JAWS tests

:ok: 9559b7fcc660febbd3a914e2d77fcf3e3e86c6dd seems fine for me


BACPAC export fails on large databases

Issue Type: Bug
Attempted to export a 31GB database as a bacpac using the Data-tier Application wizard
Failed after a period of time with the following error
Export bacpac: Could not export schema and data from database.
One or more errors occurred. (One or more errors occurred. (One or more errors occurred. (One or more errors occurred. (One or more errors occurred. (Stream was too long.)))))

A partial file was generated, approximatly 131MB in size.
I was able to successfully export the database as a bacpac using the wizard in SSMS18preview5 and had a filesize of 765MB.
Azure Data Studio version: azuredatastudio 1.3.4-insider (8bf835c53163bb8024afbbe6224d809ab41a0994, 2018-11-28T01:02:12.569Z)
OS version: Windows_NT x64 10.0.17134

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz (12 x 2208)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: enabledvideo_decode: enabledvideo_encode: enabledwebgl: enabledwebgl2: enabled

Memory (System)
31.82GB (12.19GB free)

Process Argv
C:\Program Files\Azure Data Studio\azuredatastudio.exe

Screen Reader
no

VM
0%

Extensions (4)

Extension
Author (truncated)
Version

ssmskeymap
kev
1.0.0

agent
Mic
0.35.1

import
Mic
0.4.2

profiler
Mic
0.5.1

We will look into this. It might be an issue with DacFx running on .NET Core.

@DaveDustin - thanks for reporting.
Looks like this is issue is due to the System.IO.Packaging implementation on .NET Core, which does not support ZipArchive streaming. This API is used by the ADS DacFx extension and DacFx to generate the .bacpac file. As a result, the ADS DacFx extension will be problematic importing and exporting large database.
The issue tracking System.IO.Packaging in corefx:
https://github.com/dotnet/corefx/issues/24457
The issue tracking ZipArchive streaming in corefx:
https://github.com/dotnet/corefx/issues/20558
It doesn't look like there are any immediate plans to fix the above two issues, so a resolution for this issue might take some time.
A workaround might be to try on a machine with more memory - maybe proportional to the size of the largest table in the database? I haven't tested this out so I don't know if throwing memory at the problem is a valid workaround.

The machine I ran it on had 32GB of memory.
But yeah, if it's a downstream constraint there is not much you can do at present.
thanks

@DaveDustin this issue should be fixed in the latest release of ADS. Please let us know if still doesn't work. Thanks!


backend - add pagination to get all rules api

done via https://github.com/x-sushant-x/Rate-Shield/commit/031fdf44dd099829b48666875b2e107fcb9b87d7