Add OrderQuery and MemberQuery to GraphQL v2

Adds OrderQuery and MemberQuery for v2
Adds fetchOrderWithReference

@sbinlondon What's the use case for MemberQuery? I'm not sure about it. fromAccount and toAccount are looking odd.

https://github.com/opencollective/opencollective-frontend/blob/471b43ab7e5fb9bdbd3f97b7763c06c4a85ba643/components/new-contribution-flow/ContributionFlowSuccess.js#L337
When we navigate to the order success page, we don't feed in any order information via props. We do have the OrderId in the router query though. So first we get the order info using the OrderQuery but then we also need the Member info to see if there is a public message from when the sponsor has donated to this collective before. So we make an additional MemberQuery using the info we get back from the OrderQuery (the toAccount, or the Collective that's being donated to, and the fromAccount, who is giving the donation).
There is a v1 query I could use from the old Order page but I thought we were going to update old queries as we went.

I think that could be introduced as a property to the Order like order.membership. Would be interested to see @Betree's feedback on this.

I think that could be introduced as a property to the Order like order.membership. Would be interested to see @Betree's feedback on this.

I agree with this. We could also add a account field on account.memberOf:
order(order: $order) {
  fromAccount {
    memberOf(account: $account) {
      // Returns all the memberships for fromAccount <> account
    }
  }
}

Whatever we do, it would be elegant to solve this with just one query.

@Betree @znarf I've made some changes, let me know what you think


Getting dialog instance from DOM object

I want to trigger show and hide to dialog - but is it possible when i have only access to DOM object which was used to initialize dialog? Can i get dialog instance out of that dom object?
I did that manually, like this, but i wonder if this is somehow built in library.
  const element = document.getElementById('some-id')
  const dialog = new A11yDialog(element)
  element._dialog = dialog

Hello Piotr!
You’re right, you cannot get the instance from the DOM object itself. As mentioned in the documentation, if you want to manipulate the dialog instance, you need to instantiate yourself instead of relying on the auto-instantiation.
It seems like a pretty minor case, so I’m not sure I’m keen on adding it to the core library. :)


Confusingly added in the timeshift pull request.


[Feature] Replace the dynamic styling in listing.js with class-based CSS approach

Problem
In the _assets/js/listing.js file, to make the resources visible, the use of dynamic styling has been done.
Description
Instead of creating a new style element for the displaying of resource cards, It will be better to use a css property of display: none via a class based approach. we can create a new utility class for the task.
The link to listing.js file: https://github.com/creativecommons/cc-resource-archive/blob/main/docs/_assets/js/listing.js
Implementation

[x] I would be interested in implementing this feature.

I would like to work on this issue, kindly assign.

Kindly review my pr and let me know if any other changes are required!!


IOS: Success/Error images not showing

Please check all of the platforms you are having the issue on

[x] iOS
[] Android
[] UWP
[] PCL

Please state the issue to the best of your ability below

Version 6.2.0 from nuget doesn't show the images for success or error on iOS.
The sample app does show the images, but when i remove the references to the lib projects and add the nuget package, the images don't show up anymore.
According to https://github.com/aritchie/userdialogs/issues/162 you fixed this in 6.1, but it looks like this fix is not in the nuget 6.2?

It is obviously some weird linker issue.  At this point, I'm pretty sick of these methods as I don't use them anywhere and I'm marking them as deprecated


Create the "Designer Contribution Guideline" for the wedding cake website

chsanche created the following on Jan 21:
User story
As a Digital Design System adopter, I need a way to contribute my design back to the team, so that my design can be added to the Digital Design System and be utilized.
Deliverables

Designer Contribution Guideline

Notes

We do not currently have any guideline around contribution.
Resource: Carbon
(for Designer) https://next.carbondesignsystem.com/contributing/designers
(for Add-on) https://next.carbondesignsystem.com/contributing/add-ons

Acceptance Criteria (defining "done")

Have the guideline published on the website

Tasks

[ ] Create a high-level draft on what we need in the guideline
[ ] Review with the designers
[ ] Review with the content team
[ ] Review with the DDS team
[ ] Finalize the guideline
[ ] Post the guideline on the website

Original issue: https://github.ibm.com/webstandards/digital-design/issues/482

On Mar 06, chsanche commented:
Note: We need to figure out if the contributions from others are for us or for Carbon to handle.

On Mar 06, chsanche commented:
I created a rough draft of the contribution guideline for designers based on what Carbon has and can be view here.
A few findings, there are quite a few repos, guideline, and templates Carbon has. We need to do an audit on what we have then either create one or update ours to make sure we are aligned with Carbon's process and templates.

On Mar 06, chsanche commented:
@Olivia-Flory @Wonil-Suh1 @Lisa-Lurie Tagging you for FYI purpose.

On Jun 24, chsanche commented:
Update: This guideline will be published on the new Gatsby website or use the one Carbon has based on the mental model/ website IA decision.


'contains' filter should be case insensitive

According to the docs:

To only show articles where the title attribute is a case-insensitive match against linux-rocks:
http://localhost:16006/rest/articles?filter[title]=~linux-rocks
To only show articles where the title attribute contains for:
http://localhost:16006/rest/articles?filter[title]=:for

It doesn't state that seaching within a field (:) should be case-sensitive.
Looking at for example the jsonapi-store-relationaldb handler, you can see that the : filter is actually case insensitive.
Searching with the mongodb handler should also be case-insensitive, because the behavior of filters should be identical between storage providers.
A workaround is to query all possible cases and merge the search results:

?filter[title]=:for
?filter[title]=:For
?filter[title]=:FOR

The offending line is this: https://github.com/holidayextras/jsonapi-store-mongodb/blob/eaf0c479d2354ce85ff578a42cb7c6fe717c5edd/lib/mongoHandler.js#L70
I will provide a PR below.

I'll be working on forking store-mongodb to jagql in this week


PTM datasets

@khanspers and Bing are collecting PTM datasources. Let's capture that table here in folder called datasets, as a README, along with some sample datasets.
At first, let's get our hands on a few datasets that will likely relate to the handful of test pathways we have selected (see #1)

From Sarah: CPTAC pancancer, harmonizing 10 cancer datasets.
https://kb.linkedomics.org/download

Yuxing will send correlated PROGENy:EGFR and pathway activity score (linear model) values per phosphosite.

From Yuxing we got the following:
CPTAC_phospho_tn.txt (The p-values and statistics (“val”) are from Wilcoxon rank sum test. Positive values mean abundance is higher in tumor.)
CPTAC_protein_tn.txt (The p-values and statistics (“val”) are from Wilcoxon rank sum test. Positive values mean abundance is higher in tumor.)
CPTAC_PROGENy__EGFR.txt (EGFR pathway set correlation from PROGENy. The cohort.val is the Spearman correlation coefficient and cohort.pval is the p-value)


PowerRename has two entries in Explorer context menu

Microsoft PowerToys version
0.64.0
Installation method
PowerToys auto-update
Running as admin
Yes
Area(s) with issue?
PowerRename
Steps to reproduce
Allow PowerToys auto-update to update previous version to v0.64.0.
✔ Expected Behavior
PowerRename should only appear in each context menu level once.
❌ Actual Behavior
PowerRename appears in the legacy context menu twice.

It appears that when PowerRename is registered with the new Windows 11 context menu, it automatically propagates to the legacy context menu as well.
Problem seems to be resolved by deleting the now redundant legacy context menu registry key:
[-HKEY_LOCAL_MACHINE\SOFTWARE\Classes\AllFilesystemObjects\shellex\ContextMenuHandlers\PowerRenameExt]
Other Software
No response

You just beat me to it. I see this too on my computer. Both work, by the way

Same for the Resize Pictures addin.

same issue here, thought it was caused by a context menu mod I installed, but it happened with that disabled too

Same for the Resize Pictures addin.

You can fix it by deleting all entries of ImageResizer in HKEY_CLASSES_ROOT\SystemFileAssociations
Find it with Ctrl+F

@Dgamefinisher: Thanks, you saved my day! 👍🏼

Update: When updating powertoys to version 0.72.0 power rename may disappear from the windows modern context menu. For anyone who used this fix, upon updating revert the registry change with the reg file below (remove .txt first).
powerrename_remediation.reg.txt

I did everything listed above but couldn't delete the second entry and so I dug through the registry and found another key that solved the issue for me. Under Computer\HKEY_CLASSES_ROOT\CLSID\ run a find (Ctrl + F) and search for PowerRenameExt and mine personally looked like this HKEY_CLASSES_ROOT\CLSID{0440049F-D1DC-4E46-B27B-98393D79486B}. Delete the entire key (export first in case it doesn't work). There was a subkey titled InprocServer32 which I believe just holds the UID for the com class object but I could be wrong. Regardless it fixed the issue.
 Image of the simplified structure.
here's a command that might delete it assuming the 0440049F... is the same reg delete HKEY_CLASSES_ROOT\CLSID{0440049F-D1DC-4E46-B27B-98393D79486B}

Also whit recent 0.78 it's present double entries. remove this (after backup) fix the issue.

I did everything listed above but couldn't delete the second entry and so I dug through the registry and found another key that solved the issue for me. Under Computer\HKEY_CLASSES_ROOT\CLSID\ run a find (Ctrl + F) and search for PowerRenameExt and mine personally looked like this HKEY_CLASSES_ROOT\CLSID{0440049F-D1DC-4E46-B27B-98393D79486B}. Delete the entire key (export first in case it doesn't work). There was a subkey titled InprocServer32 which I believe just holds the UID for the com class object but I could be wrong. Regardless it fixed the issue.
 Image of the simplified structure.
here's a command that might delete it assuming the 0440049F... is the same reg delete HKEY_CLASSES_ROOT\CLSID{0440049F-D1DC-4E46-B27B-98393D79486B}

This works really well. thank you !


improvements on overview documentation

went a little bold with 64f7305, I think it works out nicely

went a little bold with 64f7305, I think it works out nicely

That's super helpful!


How do I run the trained agent, or play as a human?

Hi,
I'm excited to be able to start trying out lab2d now - can I ask a few questions about how to use it?

My understanding from the "lab" docs is that when I run bazel run dmlab2d/python:random_agent -- --level_name=clean_up I am training an (initially random) agent in the "clean_up" world. What corresponds to the number of training steps in Fig 2 of your paper? How do I run the trained agent?
The clean_up/play.py file starts with the comment "A simple human player for testing the clean_up level." How can I access the human player? The lab docs suggests something like bazel run :game -- --level_script=tests/empty_room_test" but I can't work out how to modify that for lab2d.

(Two minor comments - is the difference between level_script and level_name significant? And all the different levels' play.py files start with comments saying they are for the "clean_up" level.)
Also, I imagine the training would go faster without the pygame rendering - can it be turned off during training?
Thanks!
Btw, I've had some fun watching the agent play the chase-eat level, bazel run --config=lua5_2 dmlab2d/python:random_agent -- --level_name=chase_eat --num_episodes 100 👻

The "random agent" doesn't learn anything. It just takes random moves. It just demonstrates how to connect an agent and shows off (a part of) a given level.

The DeepMind Lab :game binary is something very Quake-III-specific and doesn't apply here, it's essentially a direct Quake-III UI (not an RL agent at all) that entirely bypasses the RL interface and serves mostly for direct testing of the levels. Here, in Lab 2D, we need to use a proper "human agent". I'm not sure about how to do this (I think it involves https://github.com/deepmind/lab2d/blob/main/dmlab2d/python/ui_renderer.py), @charlesbeattie should know this.

The "random agent" doesn't learn anything. It just takes random moves. It just demonstrates how to connect an agent and shows off (a part of) a given level.

The DeepMind Lab :game binary is something very Quake-III-specific and doesn't apply here, it's essentially a direct Quake-III UI (not an RL agent at all) that entirely bypasses the RL interface and serves mostly for direct testing of the levels. Here, in Lab 2D, we need to use a proper "human agent". I'm not sure about how to do this (I think it involves https://github.com/deepmind/lab2d/blob/main/dmlab2d/python/ui_renderer.py), @charlesbeattie should know this.

Oh, maybe it's something like bazel run -c opt //dmlab2d/game_scripts/levels/chase_eat:play?

Oh, maybe it's something like bazel run -c opt //dmlab2d/game_scripts/levels/chase_eat:play?

Oh cool thanks - that :play command does try to compile but then hits a new arm64 problem 😢
external/luajit_archive/src/host/buildvm.c:63:10: fatal error: '../dynasm/dasm_arm64.h' file not found
#include "../dynasm/dasm_arm64.h"

So - putting that aside - how do I go about training a model in lab2d?

Oh cool thanks - that :play command does try to compile but then hits a new arm64 problem 😢
external/luajit_archive/src/host/buildvm.c:63:10: fatal error: '../dynasm/dasm_arm64.h' file not found
#include "../dynasm/dasm_arm64.h"

So - putting that aside - how do I go about training a model in lab2d?

Yes, as discussed before, you probably need --define=lua=lua5_1 or somesuch, since luajit doesn't work for ARM.

Yes, as discussed before, you probably need --define=lua=lua5_1 or somesuch, since luajit doesn't work for ARM.

d'oh! sorry, yes that's got it, thanks!

d'oh! sorry, yes that's got it, thanks!

Training an agent is the essence of RL research, isn't it :-) That's not in scope for Lab 2D, which only provides the environment. You need to build your own learning agent, with whatever technology you like.

Training an agent is the essence of RL research, isn't it :-) That's not in scope for Lab 2D, which only provides the environment. You need to build your own learning agent, with whatever technology you like.

Please reopen if you want to discuss anything else.


http:backstage:request action will throw out invalid plugin token error when call custom plugin

http:backstage:request action will throw out invalid plugin token error when call custom plugin
Expected Behavior
When we use the http:backstage:request action, we would like to call an internal API from our custom plugin, it should work as our frontend plugin can call it without any issue
Current Behavior
However, when we call the internal API, it throws out the invalid plugin token error like below:

The issue happened after our backstage upgrade to 1.28+.
Currently we can only use the action to call the internal api from backstage catalog plugin without any issue.
Steps to Reproduce
Possible Solution
We did some investigation for the issue, and found some reason:

in the latest backstage, the auth method has been changed:
https://backstage.io/docs/auth/service-to-service-auth/#standard-plugin-to-plugin-auth
Currently the action code use the ctx.secrets.backstageToken as the token: https://github.com/RoadieHQ/roadie-backstage-plugins/blob/9684eb1480dd3586b7a320724a7b90d3d192c360/plugins/scaffolder-actions/scaffolder-backend-module-http-request/src/actions/run/backstageRequest.ts#L120
In backstage scaffolder-backend plugin, the secrets.backstageToken is hardcoded to the catalog plugin only: https://github.com/backstage/backstage/blob/96e143f744160f2a581bef4b691209a5a04fcd55/plugins/scaffolder-backend/src/service/router.ts#L478
https://github.com/backstage/backstage/blob/96e143f744160f2a581bef4b691209a5a04fcd55/plugins/scaffolder-backend/src/service/router.ts#L541

That's why we only be able to call the catalog plugin api with this action.
I think we can update our token logic to get the target plugin token with the standard method:
const { token } = await auth.getPluginRequestToken({
onBehalfOf: credentials,
targetPluginId: '', // e.g. 'catalog'
});
Context
Your Environment

This error is also been seen due to the ctx.secrets.backstageToken  change:
https://github.com/backstage/backstage/issues/25096
in addition, I have my proxy config set as following:
proxy:
  endpoints:
    '/gitlab':
      target: 'https://gitlab.com/api/v4'
      headers:
        content-type: 'application/json'
        Authorization: 'Bearer {token}'
      changeOrigin: true
      # Change to "false" in case of using self hosted instance with a self-signed certificate
      secure: true

and get the following error:
 401 Response body: {"error":{"name":"AuthenticationError","message":"Illegal token","stack":"AuthenticationError: Illegal token\n

does the plugin try to override the authentication token even when if the Authentication hearder has already been set in proxy config?

So, I think this should be a bug for the action, I will try to create a PR on this.

Ran into this today with Backstage 1.28.3
Workaround (not ideal) is to set the proxy.credentials to dangerously-allow-unauthenticated.  Definitely not secure unless the API endpoint also requires an auth token.
Subscribed to follow when this is fixed 😎

This error is also been seen due to the ctx.secrets.backstageToken  change: backstage/backstage#25096
in addition, I have my proxy config set as following:
proxy:
  endpoints:
    '/gitlab':
      target: 'https://gitlab.com/api/v4'
      headers:
        content-type: 'application/json'
        Authorization: 'Bearer {token}'
      changeOrigin: true
      # Change to "false" in case of using self hosted instance with a self-signed certificate
      secure: true

and get the following error:
 401 Response body: {"error":{"name":"AuthenticationError","message":"Illegal token","stack":"AuthenticationError: Illegal token\n

does the plugin try to override the authentication token even when if the Authentication hearder has already been set in proxy config?

This action has set the Authentication header, but it is just to call the proxy plugin api. And I remember that for backstage proxy plugin, Authentication header will be not forward to the target endpoint by default.

This action has set the Authentication header, but it is just to call the proxy plugin api. And I remember that for backstage proxy plugin, Authentication header will not be forwarded to the target endpoint by default.

with the workaround suggested in https://github.com/RoadieHQ/roadie-backstage-plugins/issues/1464#issuecomment-2212563950
adding proxy.credentials = dangerously-allow-unauthenticated, I'm able to by-pass the error, and also the authentication header got forwarded. I'm able to call gitlab API with no issues.

any updates when this this will be fixed, we are also facing this issue with latest backstage version where they have made changes in their backend-proxy plugin.

Thanks @Nitinvonage , would you be able to provide a PR for this and we will get it merged

sure, I can try this out, if my understanding is correct we need to change the token extraction logic here -
https://github.com/RoadieHQ/roadie-backstage-plugins/blob/c62ec52707b3be39c40d240d299dba00995a3243/plugins/scaffolder-actions/scaffolder-backend-module-http-request/src/actions/run/backstageRequest.ts#L120
with something like this - ctx.getInitiatorCredentials()

I'm trying to create a PR on this, and it's now under the internal review..

Hi @Xantier I created a PR on this, could you please help review and approve it if no issue.

@Xantier Here's the PR: https://github.com/RoadieHQ/roadie-backstage-plugins/pull/1532

Hi @Xantier Could you please help check? Thanks a lot.


Missing tag for v1.3.0 and changelog for v1.3.1

It would be great to update changelog for v1.3.1
Also, strange, tag for v1.3.0 is missing

Unfortunately it is hard to go back and append git history without causing Ruby gem issues in my experience.  Sorry.


Using AntiForgeryToken on React/Redux Server Side Rendering

I need to use the AntiForgeryToken for form submits. What I do on the client is generate a js variable like this
window.aft = '@Html.AntiForgeryToken()';

I can then do this in pages where I need it.

When doing server side rendering this isn't possible.
How do you recommend doing this?
My only guess is to use asp-prerender-data. Is there a better way?

Using asp-prerender-data is the correct way to flow arbitrary info from your .NET code into your Node-side SPA code during prerendering, so I think you're already on the correct lines.


add RouterStore and RouterObject PropertyWrapper

This is a follow up to https://github.com/rundfunk47/stinsen/issues/5
As I described in the issue I use Resolver for injecting my dependencies. Since using it directly within Resolver is messy I created a RouterStore which kind of copies the SwiftUI Environment behavior.
It allows to use the Router without directly passing them from via the View, so there is no tight coupling.
I created a new protocol called RouterIdentifiable which has to be implemented optionally by a Coordinator.
This way the code is 100% backward compatibly.
It would be cool if you like my solution our if we could find a similar solution enabling better ViewModel usage :blush:

Hi! This looks like the beginning of a good solution! 👍🏽  I'll give it a good look later this week :)

It would also possible to create it without id just with type like this, without id. In this case the id could be the type description:
 @RouterObject
  var unauthenticated: NavigationRouter<UnauthenticatedCoordinator.Route>?

I'm not sure how we can handle possible duplicates then. The Swiftui Environment has a tree structure based on the view render tree. The RouterStore is just a plain Dictionary.

Hi! I haven't had the time to really give this a through look, holidays and all. But there were one thing I noticed:
The RouterStore should probably be a Dictionary<String, Array<...>>. Right now the Testbed does not work when pushing two of the "same" coordinator.
I'll give it a closer look ASAP though! :)

I implemented the changes I suggested now @savage7 , it seems to work with the Testbed now :) . Does these changes look good?

@rundfunk47
I'm on vacation too so I couldn't compile it :sunny:. But from looking at the code your solution looks cleaner, thanks for looking into it :blush:

Great! I'll just clean it up a bit and then I'll merge it 😄


Save docker images to aci with rkt

As I can see docker2aci tool is not going to be included to CoreOS,
so we need e.g. save/convert option for rkt to save docker images to aci files.

This will actually be resolved by https://github.com/coreos/rkt/issues/645 - once that exists users will be able to rkt fetch && rkt export to convert Docker images to ACIs.

:+1:


Adding unit tests for the util package

Added unit tests for the util package

@brian-brazi Thanks for the review. Done!

Thanks!


Use default CLI prog name

Codecov Report

Merging #11 (e12422b) into main (32c57d8) will not change coverage.
The diff coverage is 100.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@           Coverage Diff           @@
##             main      #11   +/-   ##
=======================================
  Coverage   98.37%   98.37%
=======================================
  Files           5        5
  Lines         185      185
  Branches       31       31
=======================================
  Hits          182      182
  Misses          3        3

Impacted Files
Coverage Δ

pictureshow/cli.py
100.00% <100.00%> (ø)

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


[Bug] New auth on google sheet is failing, not redirecting to new query page

Version: Cloud
OS: MacOSX
Browser chrome
Environment : production

Cloud services had not been promoted in a while, doing so has fixed this.


Zoom.Zoom version <IP_ADDRESS>48

[ ] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[x] Does your manifest conform to the 1.4 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: codeflow:open?pullrequest=https://github.com/microsoft/winget-pkgs/pull/110539&drop=dogfoodAlpha

@microsoft-github-policy-service agree

@microsoft-github-policy-service agree


How do I use connection for multi thread?

Hi.
I want to use RedisClusterClient with multi thread client with StatefulRedisClusterConnection.
but I cannot found how I should use connection.
in thins issue(https://github.com/mp911de/lettuce/issues/157), mp911de said we no need to use connection pool.
if so, which we should use for multi thread client access?

reuse stateful connection
every time we create new connection

Thanks!

Hi @uryyyyyyy,
lettuce is thread-safe, you can reuse stateful connections across multiple threads. The only exception is if you use blocking commands such as BLPOP. When using blocking commands, you should use multiple connection to not block other threads.
お役に立ったなら幸いです, Mark

@mp911de
that's all I want to know!
Thanks!! I will use lettuce for our service.


[libsoundio] Add Linux support

It would great if the port for libsoundio would support Linux.
Would it be as simple as -DENABLE_ALSA=${VCPKG_TARGET_IS_LINUX} in the portfile?
Should it support options to allow different backends (e.g. ALSA, Jack, PulseAudio), or should it default to ALSA?
I'm happy to put in a PR but I would appreciate some guidance first. Thanks!

Sadly, we doesn't have a port named ALSA.

It's included in most Linux distributions and will be automatically found by libsoundio (see here)

This seems fixed by #16891 -- thanks for the PR!


Translation Update for Multiple Documents

Your code's awesome, and my translation gig is just adding to the coolness. I've tweaked the doc names like you asked, dumping the '-en' from the English ones. Whenever I've got some free time in the future, I'll keep plugging away at translating those docs that are only in Japanese, making sure the English versions are all set.


A Kit with toolchainFile fails to determine CMAKE_(C|CXX)_COMPILER without the user adding both variables to the cache file

Brief Issue Summary
A local user CMake kit using a toolchainFile will make cmake-tools fail at determining the C/C++ compiler path.
Then IntelliSense setup is done wrong:

Architecture/Pltform/CompilerFlavor dependent codepaths highlighting is wrong (eg:  __amd64__ or __arm__, _WIN32 or __linux__, __MINGW32__ or __MINGW64__)
Code completion is made difficult or incorrect (because of 1., symbols may be missing etc...)

Expected:
CMake toolchain file documentation doesn't mandate that CMAKE_C_COMPILER and CMAKE_CXX_COMPILER  variables be placed in the cache.
CMAKE_C_COMPILER and CMAKE_CXX_COMPILER should be figured out automatically by the extension w/o adding a cache entry for them both.
Note that the cache workaround is mentioned in:

#602 where writing the CXX/C compiler settings forces them on the command line and thus in the cache
#500 where a specific pair of set(... CACHE ...) calls are inserted in the toolchain file

Reproduction steps:

Setup a local CMake build kit using a toolchain file documented as per CMake guidelines. (eg: a buildroot generated toolchain file will do just fine)
Import a C++ project for which code blocks vary depending on the architecture (eg: __amd64__ or __arm__)  or on the platform (eg: _WIN32 or __linux__) or the compiler flavor (eg: __MINGW32__ or __MINGW64__)
Ctrl+Shift+P Cmake: Configure
Observe the codepaths highlighting mismatches and the code completion problems

Apparent Behavior:
CMake Tools expects CMAKE_C_COMPILER and CMAKE_CXX_COMPILER in the cache to setup the CPP project correctly.
CMake Tools Log
No relevant logs to copy/paste.
Developer Tools Log
No relevant logs to copy/paste.
Platform and Versions

Operating System: Debian GNU/Linux SID
CMake Version: 3.16.3
VSCode Version: Version: 1.44.2 Commit: ff915844119ce9485abfe8aa9076ec76b5300ddd
CMake Tools Extension Version: 1.3.1
Compiler/Toolchain:  any cross toolchain would exhibit the problem as long as it's setup only through a toolchain file. (tested with a GCC 7.3 generated by a ARM based buildroot build, or Debian's (g++|gcc)-arm-linux-gnueabi packages, or Debian's gcc-mingw-w64-(x86-64|i686))

Other Notes/Information
Here is a failing toolchain file example. It targets mingw32 builds using mingw32 debian packages.
set(CMAKE_SYSTEM_NAME Windows)
set(CMAKE_SYSTEM_PROCESSOR x86)

set(toolchain_dir "/usr/bin")
set(toolchain_triplet "i686-w64-mingw32")
set(toolchain_prefix "${toolchain_triplet}-")
set(toolchain_suffix "-posix")

set(CMAKE_SYSROOT "/usr/${toolchain_triplet}")

set(CMAKE_C_COMPILER   "${toolchain_dir}/${toolchain_prefix}gcc${toolchain_suffix}")
set(CMAKE_CXX_COMPILER "${toolchain_dir}/${toolchain_prefix}g++${toolchain_suffix}")
set(CMAKE_RC_COMPILER "${toolchain_dir}/${toolchain_prefix}windres" CACHE FILEPATH "" FORCE)

set(CMAKE_FIND_ROOT_PATH_MODE_PROGRAM NEVER)
set(CMAKE_FIND_ROOT_PATH_MODE_LIBRARY ONLY)
set(CMAKE_FIND_ROOT_PATH_MODE_INCLUDE ONLY)
set(CMAKE_FIND_ROOT_PATH_MODE_PACKAGE BOTH)

Appending these two lines are the current workaround for hand made toolchain files
set(CMAKE_C_COMPILER "${CMAKE_C_COMPILER}" CACHE FILEPATH "C Compiler path")
set(CMAKE_CXX_COMPILER "${CMAKE_CXX_COMPILER}" CACHE FILEPATH "C++ Compiler path")

The problem can't be workaround easily when using generated toolchain files (eg: buildroot ./host/usr/share/buildroot/toolchainfile.cmake) or external toolchain files provided by third parties.

@edgomez, how about @bobbrow's comment at the end of issue https://github.com/microsoft/vscode-cmake-tools/issues/602, that didn't work for you?
Copy pasting the suggestion:
"You should be able to set the C and CXX compilers without editing the Cache by adding a "Kit" to your user-local or project kits file: https://vector-of-bool.github.io/docs/vscode-cmake-tools/kits.html#kits.
Then select that Kit and reconfigure the project."

@andreeis, indeed this actually works.
But, IMHO this still qualifies as a workaround because vscode-cmake-tools need those variables cached to configure correctly the CPP backend.
Here is my reasoning:

According to cmake-toolchains(7) documentation, having the C/CXX compiler defined as simple variables in the toolchain file should suffice. And all toolchain files I came across and those I write myself do use regular set(CMAKE_C|CXX_COMPILER value), no CACHE involved.
cmake-toolchains(7) command line examples tend to suggest that one can complement some toolchain files w/ additional variables directly defined on the command line, this is for example mentioned for Android or iOS support. But no mention of the necessity to define CMAKE_C|CXX_compiler using -D options on top of the toolchain file itself.
vscode-cmake-tools documentation tells configuring a local kit is as simple as filling in the C/CXX properties. Then the only example found for the toolchainFile property, totally omits to fill the C/CXX properties. This strongly suggests you either fill in the C/CXX properties, or you fill in the toolchainFIle property. No need for both.
Additionally, vscode-cmake-tools seems to use the compile_commands.json file to grab lots of information for the CPP backend (command line defines etc...). It could find the compilers used in each "command" entry's first token.

So to me, the fact we need to fill in the C/CXX properties in a CMakeKit defeats the whole purpose to fill all the required information in a toolchain file to support a different target system:

If this is not considered a bug/vscode-cmake-tools shortcoming, then the documentation could be at least rephrased to make clearer that if one wants perfect CPP backend configuration by the extension, the C/CXX must be filled in even if the toolchainFile property is already used and the file defines those two.
If current behavior is considered a shortcoming of the current vscode-cmake-tools implementation, then C/CXX could be deduced differently. From the compile_commands.json file then provided to the CPP backend the same way command line defines are found. Or by asking nicely cmake to output the C/CXX vars itself and fill automatically those when needed in the CMakeKit. This would avoid users setting up the properties themselves and potentially create configuration mistakes (what happens if the toolchainFile and C/CXX properties don't agree on which compiler is "used", the CPP backend will still be mis-configured).

whats is your opinion ?

To illustrate the proposal in my comment.
When configuring a cmake kit, vscode-cmake-tools could configure a temporary project whose sole CMakeList.txt would provide it with the C/CXX compiler information it needs. This can be done as follow:
cmake_minimum_required(VERSION 2.8)

project(PrintCLanguageCompilersForVSCode)

enable_language(C CXX)

message(STATUS "vscode-cmake-tools kit configuration: CMAKE_C_COMPILER=${CMAKE_C_COMPILER}")
message(STATUS "vscode-cmake-tools kit configuration: CMAKE_CXX_COMPILER=${CMAKE_CXX_COMPILER}")

The result could be grep'ed from cmake output, or maybe communicated over whatever the extension cmake driver supports.
What do you think ?

@edgomez, makes sense. We need to digest this proposal more. Also, upvoting the first comment in this issue will help us to prioritize it appropriately.

Ok up-voted my first comment. Hope this is picked for a future release soon :-)
If you need any further detail, do not hesitate to ask.

I think I have a similar issue. We're using the proprietary ARM compiler (ARMClang), and here even the workaround putting the compiler in the cache or setting with the cmake-tools-kits.json does not help to make the cpp code highlighting work correctly.
`/*

ARM Compiler 6 (armclang)
*/
#elif defined (__ARMCC_VERSION) && (__ARMCC_VERSION >= 6010050)
#include "cmsis_armclang.h"

/*

GNU Compiler
*/
#elif defined ( GNUC )
#include "cmsis_gcc.h"`

In this part the the armclang.h line is highlighted as inactive, although the whole project compiles perfectly with it. Perhaps this is also just a bug/missing feature of the cpp-tools extension to be able to use the armclang compiler.

Nevermind, I just saw that a fix is underway here.
When will that be released?

CMake Tools 1.4.0 Beta is available on GitHub and contains this fix that you are interested in (but which does not address this current issue): https://github.com/microsoft/vscode-cmake-tools/issues/1155.
https://github.com/microsoft/vscode-cmake-tools/releases/tag/1.4.0-beta
Please try it out and let us know if you encounter any issues.

Tested newer cmake tools a few times since then.
The problem still persists and the cmake plugin doesn't seem to communicate the C/CXX compiler information  to intellisense w/ the toolchain files with regular variables. The same workarounds are still to be applied: either put the vars in the cache, or manually edit again the toolchain file.
Will there be progress on the proposed solution ? newer cmake propose a file API that can allow the plugin to extract all sorts of informations about the project as well. Pretty sure the C/CXX compiler information is one of them.

Did you try the recent release of CMake Tools? 1.7 contains support for the CMake toolchains object and we get the C/CXX compiler information from there. Let us know if it doesn't fully work for your scenario.

hi @andreeis ,
Yes i'm activelly using the latest vscode + C/C++ insider + cmake tools 1.7.1
For testing, I just created a debian container + mingw installed + handwritten toolchain file.
I compiled a cmake 3.20.2 in the container so that cmake tools had everything required to introspect the fileApi toolchain output.
I noted some improvements. I think we're almost there...
I could find the fileApi toolchain info, showing that cmake tools did request the information, however intellisense remained totally wrong w.r.t defined symbols.
I could trace this to the fact the c_cpp_properties.json configuration entry isn't flexible enough to point it to the correct compile_commands automatically, i had to manually add:
       {             "name": "mingw64",             "includePath": [                 "${workspaceFolder}/**"             ],             "compileCommands": "${workspaceFolder}/build/mingw64/compile_commands.json",             "configurationProvider": "ms-vscode.cmake-tool"         }
I wish we had a ${command:cmake.buildKit} so that i could rewrite this like:
       {             "name": "Linux Host based Compilation",             "includePath": [                 "${workspaceFolder}/**"             ],             "compileCommands": "${workspaceFolder}/build/${command:cmake.buildKit}/compile_commands.json",             "configurationProvider": "ms-vscode.cmake-tool"         }
I would not have to toggle both the build kit and the C/C++ configuration manually in the status bar to get things working.
Note that I didn't check w/ a different CPU target toolchain, so i can't figure if ms-vscode.cmake-tool provides the information if the compiler being used is gcc-x64 or gcc-arm.

Mentioning  #993 which should deliver something close to what is need in my case, but for c_cpp_properties.json

@andreeis : for cmake >= 3.20, vscode does not account for all toolchain fileApi information. It found it was clang, but didn't check which target architecture. The test was based on a docker based android toolchain. I can provide the Dockerfile if needed.

adding @benmcmorran, for the >= 3.20 part of this issue.

@benmcmorran looked at the >=3.20 scenario and developed a fix here https://github.com/benmcmorran/vscode-cmake-tools/commit/1619ffcddebe35e5024e12b6b03e693b2e7f9a6a, that we will pickup and finalize (needs one more fix). I am opening a new work item for this and I am leaving this report open for the < 3.20 scenario and the suggestion from @edgomez.

@edgomez and @aelray, can you try the CMake Tools vsix from here and confirm if it solves anything for you, when you use a CMake at least as new as 3.20?

@andreeis should this build help with regard to #1877? I just tested it and it seems to still not provide the correct Intellisense configuration.

No, not that one, but for latest comments from @edgomez. I think you were referring to different issues earlier in this report (it became too large and with multiple different problems being described :), so a bit confusing). So maybe you can ignore the vsix and I'll wait for @edgomez answer.

@andreeis ok, i think the best approach to tackle this is simply to provide you with a test environment. Once setup you should have everything ready for tracking the issue and fixing it.
https://github.com/edgomez/cmake-tools-1188-env
Please follow the README.md instructions and let me know if you run into trouble using the environement.

Related: #1278 I think.


openssl s_client -reconnect causes following connections to fail with timeout

This was originally https://github.com/skupperproject/skupper/issues/954; moved here is it's probably on skupper-router, if confirmed to be an issue.
Description
openssl has a debug client called s_client, which in turn has a flag named -reconnect.  That flag, according to the man page, "Reconnects to the same server 5 times using the same session ID, this can be used as a test that session caching is working".
Session caching is not supposed to be working on Skupper.  However, after running a test with that flag, any ensuing connections time out.
This is possibly a router issue (should this be moved there?), but the steps to reproduce use skupper.
How to reproduce
$ skupper init
$ k create -f /tmp/ssl-server.yaml
$ skupper expose --enable-tls --port 8443 deployment/ssl-server
$ k exec -ti deployment/ssl-server -- openssl s_client -connect ssl-server:8443 # works; try it a few times
$ k exec -ti deployment/ssl-server -- openssl s_client -connect ssl-server:8443 -reconnect # doesn't work anymore
$ k exec -ti deployment/ssl-server -- openssl s_client -connect ssl-server:8443 # new connection, and it does not work anymore

Here, 'works' means that the server responds to any inputs with the reversed input (ie, typing asdf and hitting enter immediatelly gets a response of fdsa).  'Doesn't work', in turn, means that no response is ever sent, even if the openssl s_client output shows a successful TLS connection.
ssl-server.yaml contents:
---
apiVersion: apps/v1
kind: Deployment
metadata:
  labels:
    app: ssl-server
  name: ssl-server
spec:
  replicas: 1
  selector:
    matchLabels:
      app: ssl-server
  template:
    metadata:
      labels:
        app: ssl-server
    spec:
      containers:
      - command:
        - sh
        - -c
        - microdnf install openssl ; openssl s_server -port 8443 -rev -cert /cert/tls.crt
          -key /cert/tls.key -brief
        image: quay.io/skupper/skupper-tests
        imagePullPolicy: IfNotPresent
        name: skupper-tests
        ports:
        - containerPort: 8443
          protocol: TCP
        volumeMounts:
        - mountPath: /cert
          name: volume-cert
      volumes:
      - name: volume-cert
        secret:
          defaultMode: 420
          secretName: skupper-tls-ssl-server

Alternative setup, imperative, using Openshift's oc to add the volumes.
$ k create deployment ssl-server --image quay.io/skupper/skupper-tests --port 8443 -- sh -c "microdnf install openssl ; openssl s_server -port 8443 -rev -cert /cert/tls.crt -key /cert/tls.key -brief"
$ skupper expose --enable-tls --port 8443 deployment/ssl-server
$ oc set volumes --add --secret-name skupper-tls-ssl-server --path /cert deployment/ssl-server

Reproducer: https://gist.github.com/hash-d/8eca63bbd0fb86eafa087fdfbcc7c4ea


Research exchanges and determine if GDAX is really the best option given how my algorithm has evolved

Binance has a much lower transaction fee, though they get you good on the withdrawals.
WS API documentation: https://github.com/binance-exchange/binance-official-api-docs/blob/master/web-socket-streams.md

Binance it is


Array of enum values and includes false positive with undefined value

Bug Report

🔎 Search Terms

enum, includes.
🕗 Version & Regression Information

This is a crash that occurs with the current typescript@next version.

⏯ Playground Link

Playground link with relevant code
💻 Code

export enum Status {
  pending = 0,
  created = 1,
  creation = 2,
  renewal = 3,
  outdated = 4,
};

function isUpdating(status?: Status): boolean {
  return [
    Status.creation,
    Status.pending,
    Status.renewal,
  ].includes(status);
}

console.debug(
  isUpdating(Status.creation),
  isUpdating(2),
  isUpdating(5),
  isUpdating(undefined),
);

🙁 Actual behavior
TSError: ⨯ Unable to compile TypeScript:
index.ts:14:14 - error TS2345: Argument of type 'Status | undefined' is not assignable to parameter of type 'Status'.
  Type 'undefined' is not assignable to type 'Status'.

14   ].includes(status);
                ~~~~~~

🙂 Expected behavior
Should work. Running with a @ts-expect-error give me the following:
❯ node --loader ts-node/esm index.ts
(node:641729) ExperimentalWarning: --experimental-loader is an experimental feature. This feature could change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
true true false false

Good point. @ts-expect-error makes much more sense.

@RyanCavanaugh I would argue that Working as Intended is the wrong tag for this issue, since it was expressed in #26255 that there was a desire for string[].includes(string | undefined) to be a valid call (but there is no current mechanism to enable it).

I'm never really sure what to label "intended given constraints whose removal is already captured in other issues" 🤷

@RyanCavanaugh Waiting that, the issue is closed because of this label, however, this is not working as intended, I am wrong? :thinking:

It is working as intended given the current constraints in the language. You can follow #14520 for an improvement on this.


Update index.html: add link to login page

The login page is not linked inside the welcoming index page. Adding a link here makes it easier for newcomers to find the login page URL.

Just after the CSS account you get a link to the pod ( localhost:3000/podname/ ) but when trying to browse the pod ( clicking on profile/ ) the user gets an error:
Not logged in

This resource is only accessible by logged in agents.

Which mad me wonder where the login page was but now I understand why it was not in the index.html


wg_engine: shape bbox based rendering (optimization)

Before the current changes, all surfaces were painted using a full-screen overlay, no matter how large the object was rendered. This approach is redundant and required reorganization. At the moment, all objects are rendered using an overlay equal to the box of the object itself, which reduces the cost of filling the surface.
Also surfaces and images were divided into different entities, which reduces the pressure on memory.
Also geometry data for rendering and geometry data for calculations in system memory were logically separated.

see also: https://github.com/thorvg/thorvg/issues/1519


As a developer, I want to fork a UI-starter that leverages the SDK

Problem
Users can start-up a UI out of the box to build an app, forking Coinhippo UI might have too much going on
Ideas to solve this
Add simple ui to the xapp starter kit.
Demonstrate various uses of the transfer status utilities exposed by SDK.
Acceptance Criteria
[ ] Forkable and runnable UI out of the box
[ ] Tracking transfers through status
[ ] xcall fast and slow works
Other
Austin Griffith down to show scaffold.eth and this could be a better integration point for devs
Should this live in it's own repo? Depends if we need to test

Consider breaking out into two:

Scaffold  - P3 (Nice)
Internal testing one - P1 (Need)

Close as we will basically have this done with the chain abstraction UI template


chore: unify docker proto container name

Unify docker container name with the name used by Cosmos SDK.
The container is using the same docker image, so no need to duplicate hanging containers (each of them is few hundreds of MB).
Documentation and Release Note

Does this pull request introduce a new feature or user-facing behavior changes? no
Is a relevant changelog entry added to the Unreleased section in CHANGELOG.md? rather no
How is the feature or change documented? (not applicable   /   specification (x/<module>/spec/)  /  Osmosis docs repo   /   not documented)

This PR breaks make proto-all for me, I think we should revert


Calendar Item isSelectable() method

In the CalendarItem there is an isSelectable() method. It currently does not tell you whether the item is selectable, and instead tells you if it IS selected.
It should be renamed to isSelected()

Or is it the other way around? Does the variable selected need to be changed to selectable?

@bkach yep, you're right the variable selected should be changed to selectable.
I'm going to do this refactor ASAP.


How to limit the range of the super-resolved image

Hi, just a curiosity.
What are the main parameters that influence the final output range if I do not consider the final scaling and rescaling thus the plain x here, without x = (x - self.mean) * self.img_range and x = x / self.img_range + self.mean.
Because I'm trying to use it with an image bounded between 0 and 1, but it gives output values from -30 to +200, and I don't know why. I'm doing this because I want to apply this algorithm to non-real images, like temperature or gas emissions maps.
If i force the net to output values bounded between 0 and 1, i.e. x[x<0]=0 and x[x>1]=1 I obtain images filled with ones, thus the training stops after some epochs since the loss is nearly constant and does not improve.
Thanks a lot!

@antonelse The model process data in float32 and the image is processed into [0,1] range in the data loader. If you want to save the float data instead of the uint8 data ranging [0,255], modify the model file avoiding tensor2img. https://github.com/XPixelGroup/BasicSR/blob/033cd6896d898fdd3dcda32e3102a792efa1b8f4/basicsr/models/sr_model.py#L208

Thanks @chxy95 !
The problem is that, after some batches, the network tries to shrink the values to match the input range of the image, but after some epochs, it explodes, returning values far above the original range.
To avoid this, I wanted to know how I could act to reduce the problem in the image synthesis part and prevent this unusual behavior.
I'll experiment with some regularization and gradient clipping techniques.
If you have any suggestions, I'm here :)
Many thanks.


ZeldaLinkAaron working

You can delete this branch after merging it and I'll create a fork. If you have any questions about any changes, just ask. And here's an image that shows mostly everything I changed.

I was fixing something I missed with the beds

I was fixing something I missed with the beds

Make that a separate PR then, and rebase your branch. The bed changes here are causing conflicts with master.


chore: upgrade mdex

mdex 0.2.0 uses to_html!/2 to behave the same way that mdex 0.1.0 did, whereas to_html/2 now returns {:ok, String.t()} or {:error, %MDex.DecodeError{}}.
This should be merged after #92 (it will likely require a rebase).

Apologies, I actually bumped this in #96 before I saw your PRs!


[GSK-2079] Fix issue with filter and empty dataset

Description

Related Issue

Type of Change

[ ] 📚 Examples / docs / tutorials / dependencies update
[ ] 🔧 Bug fix (non-breaking change which fixes an issue)
[ ] 🥂 Improvement (non-breaking change which improves an existing feature)
[ ] 🚀 New feature (non-breaking change which adds functionality)
[ ] 💥 Breaking change (fix or feature that would cause existing functionality to change)
[ ] 🔐 Security fix

Checklist

[ ] I've read the CODE_OF_CONDUCT.md document.
[ ] I've read the CONTRIBUTING.md guide.
[ ] I've updated the code style using make codestyle.
[ ] I've written tests for all new methods and classes that I created.
[ ] I've written the docstring in Google format for all the methods and classes that I used.

LGTM
Is there any not nullable type check, that may be broken by this?

no, should be good. Just an untested corner case on my part


Feature/navbar color enhancements rebased

Replaces #742

Cleaned up styling on nav-priority and navlink, created navbar anchor ribbon example.
I'm not sure the best way to merge as @sghoweri has other tweaks to navbar as well.

Thanks @remydenton for helping with this!!

Approved, thanks @theSadowski


Validating phone number

Hello! I was wondering if anyone has run into the issue of validating a phone number after adding to cart - not sure if was a one time thing or I have to account for it every time now. Thanks!

Yes I have found in my testing if you attempt to buy a SNKRs release from another location (signed in/purchase location different from last purchase attempt or no verified phone number), it will prompt you to verify phone number before checkout. Also, you can verify your phone number in your Account settings ahead of time.

Oh okay, great. Just making sure. Thank you


[DevOps Roadmap] Additional K8s resource

Description
What do you think about adding KubeCampus in Kubernetes section under Container Orchestration?

@siddhant-khisty @kaiwalyakoparkar, Hey I found the KubeCampus stuff really useful and for that, I created this issue. Please let me know what you think about this. Thanks,

Hey @SD-13, I've heard about this resource and that it's great. Could you please confirm if it's a free resource? We're not including any paid resources or paid courses in this repo. If it's free, then please feel free to open a PR for the same 😄

Hey @siddhant-khisty, yeah I can confirm that it's totally free and that's why I mentioned it here. Will create a PR for this soon🚀


keep getting INVALID_SERVER_JSON  errors

Hi, i am not sure how to describe the error in an easier way, but i keep getting that error when i am editing any lua files.  I am currently using nvim-lspconfig  to configure the client with the current config:
sumneko_lua = {
    cmd = function()
      local cache_location = vim.fn.stdpath("cache")
      return {
        string.format(
          "%s/nvim_lsp/sumneko_lua/lua-language-server/bin/Linux/lua-language-server",
          cache_location),
        "-E",
        string.format("%s/nvim/nvim_lsp/sumneko_lua/lua-language-server/main.lua",
                      cache_location),
      }
    end,
    filetypes = {"lua"},
    settings = {
      Lua = {
        runtime = {version = "LuaJIT", path = vim.split(package.path, ";")},
        diagnostics = {
          enable = true,
          globals = {
            "vim",
            "describe",
            "it",
            "before_each",
            "after_each",
            "teardown",
            "pending",
          },
        },
        completion = {keywordSnippet = "Disable"},
        workspace = {
          library = {
            -- This loads the `lua` files from nvim into the runtime.
            [vim.fn.expand("$VIMRUNTIME/lua")] = true,
            [vim.fn.expand("~/.local/neovim/src/nvim/lua")] = true,
          },
        },
      },
    }

below, some log messages from ~/.local/share/nvim/lsp.log in a screenshot:

Neovim Version:
NVIM v0.5.0-702-g569e75799
Build type: RelWithDebInfo
LuaJIT 2.1.0-beta3
Compilation: /usr/bin/gcc-5 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -O2 -g -Og -g -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wshadow -Wconversion -Wmissing-prototypes -Wvla -fstack-protector-strong -fno-common -fdiagnostics-color=auto -DINCLUDE_GENERATED_DECLARATIONS -D_GNU_SOURCE -DNVIM_MSGPACK_HAS_FLOAT32 -DNVIM_UNIBI_HAS_VAR_FROM -DMIN_LOG_LEVEL=3 -I/home/travis/build/neovim/bot-ci/build/neovim/build/config -I/home/travis/build/neovim/bot-ci/build/neovim/src -I/home/travis/build/neovim/bot-ci/build/neovim/.deps/usr/include -I/usr/include -I/home/travis/build/neovim/bot-ci/build/neovim/build/src/nvim/auto -I/home/travis/build/neovim/bot-ci/build/neovim/build/include
Compiled by travis@travis-job-f44b8486-babf-4af2-ba88-3d51779021ff

Features: +acl +iconv +tui
See ":help feature-compile"

   system vimrc file: "$VIM/sysinit.vim"
  fall-back for $VIM: "/share/nvim"

lua-language-server HEAD
~/.cache/nvim/nvim_lsp/sumneko_lua/lua-language-server master
❯ git l
* f5f6fe9b (HEAD -> master, origin/master, origin/HEAD) 打开文件大纲的测试

This is due to an illegal Unicode character in the JSON string.
LSP specifies that the protocol uses utf8 encoding, but it does not specify how to deal with illegal Unicode characters.
When encountering illegal Unicode characters, VSCode's own language client directly encodes the original text into the protocol.
Of course, it also supports protocols that contain illegal Unicode characters.
Therefore, I think the client you use should also support the protocol for parsing illegal Unicode characters.

so you think it's a problem in lua nvim-lspconfig code?

so you think it's a problem in lua nvim-lspconfig code?

Yes.


Interface inconsistency for OAuth2 client requests

By default when calling createAPIRequest() it returns a ReadableStream provided by request
The issue is reproducible when calling with some API method which is using an expired OAuth2 token, then it's required to refresh and obtain a new token, so performing this operation is asynchronous, returning undefined in that case. Code here
It would be great if the method could provide always the same interface.
Maybe returning a new stream which acts as proxy pattern listening and dispatching all the event originally fired by the async request instance

After a brief review of the code, maybe returning the request stream in refreshToken_ could fix this

I hit the same problem.
OAuth2Client.prototype.getRequestMetadata returns undefined rather than a request object.
This causes body.pipe(req) fail for file uploading.
~Keyang

By the way, for anyone met the same problem, a current work around is to refresh the token manually before any google api request. as it does not need asynchrously refresh the token, it will return the request object synchorously.
~Keyang

Also ran into this. Thanks for the suggestino @Keyang
Here is the code needed to refresh:
var jwtClient = new google.auth.JWT(...);
jwtClient.refreshAccessToken(function(err, tokens) {
    // can now pipe files to a stream
});

For maintainers, I believe the following issues both relate to this: #501, #423


feat: Update Docker HTTPS certificate

Description
Improved on the Docker HTTPS certificate
Type of change
Check what is relevant to this pull request

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Checklist
Check what is relevant to this pull request

[x] My code follows the style guidelines of this project
[x] I did not update API Controllers, if I did, I added/changed Postman or XUnit integration tests
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[ ] I updated the changelog with an end-user readable description
[ ] I assigned this pull request to the correct project board to update the sprint board

Steps to Test or Reproduce
Rebuild the docker container to activate the changes
Link to issue
Closes: LPR-42

Does it matter that the password is exposed?

For development it's not a problem, with the password the file will be encrypted.


Screen color saturation very off; Needs saturation controls

The screen itself looks great but any color from yellow to red looks brown and desaturated. There should be a way to adjust this.
An example showing the RetroStone 2 on the left and my laptop on the right, displaying the same game.

http://orangepi.club/showthread.php?tid=3393&pid=9198#pid9198


Subtitle found when scanning within folder but not from the parentfolder for the same movie

I have a video:
/volume2/Movies/Jack Reacher- Never Go Back (2016)/Jack.Reacher.Never.Go.Back.2016.1080p.WEBDL.AC3.x264-FGT.mkv

When I try to find a subtitle from within this folder /volume2/Movies/Jack Reacher- Never Go Back (2016) it finds matching subtitles with 90+ scores.
But when I try to do the same but from within the parent directory /volume2/Movies it does find subtitles for that movie but only with scores around 60.
In the debug log from within the Jack Reacher folder it says the following that could have something to do with it:
INFO:subliminal.core:Refining video with metadata
DEBUG:subliminal.refiners.metadata:Found video_codec h264
DEBUG:subliminal.refiners.metadata:Found audio_codec AC3
DEBUG:subliminal.refiners.metadata:Found embedded subtitle set([<Language [und]>])
INFO:subliminal.core:Refining video with omdb
DEBUG:subliminal.refiners.omdb:Found 1 results
DEBUG:subliminal.refiners.omdb:Found result with matching year
DEBUG:subliminal.refiners.omdb:Found movie {u'imdbID': u'tt3393786', u'Title': u'Jack Reacher: Never Go Back', u'Type': u'movie', u'Poster'<EMAIL_ADDRESS>u'Year': u'2016'}

In the debug log from the parent folder this:
INFO:subliminal.core:Refining video with metadata
DEBUG:subliminal.refiners.metadata:Found video_codec h264
DEBUG:subliminal.refiners.metadata:Found audio_codec AC3
DEBUG:subliminal.refiners.metadata:Found embedded subtitle set([<Language [und]>])
INFO:subliminal.core:Refining video with omdb
DEBUG:subliminal.refiners.omdb:Found 1 results
WARNING:subliminal.refiners.omdb:No matching movie found

debug log from /volume2/Movies/Jack Reacher- Never Go Back (2016): http://pastebin.com/4MUWyezT
debug log from /volume2/Movies http://pastebin.com/3yKagKAM
root@LINNAS:/volume1/.@root # pip show subliminal
Name: subliminal
Version: 2.0.5

edit: I did some further testing and apparently it doesn't play well when the directory has a release year in the name like Jack Reacher- Never Go Back (2016).

It may be related to guessit, I'll try to reproduce to further investigate this.

Yes , i have been experiencing the same problem .

This seems an old guessit issue that was fixed several months ago.


GL-364: Add model for exemption overrides, possibly should 'relate' to certificates model

Jira link
GL-364
What?
I have added/removed/altered:

[ ] Added GreenLane::ExemptingCertificateOverride model
[ ] Associate it with Certificate model

Why?
I am doing this because:

This model represents certificates that included exemption or excluded exemption, exception to its default behaviour

Looks good but can you add a relationship back from the certificate to the override class
When this is getting loaded in it'll be chaining through from the certificate to the override rather than vice versa

I added the relationship now


LANDING_PAGE ignores default theme

Gitea version (or commit ref): 1.12.5
Git version:
Operating system: Docker
Database (use [x]):

[x] PostgreSQL
[ ] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[x] No

Log gist:

Description
when setting DEFAULT_THEME = arc-green & LANDING_PAGE = login - landing page (login page) will open with white theme ignoring DEFAULT_THEME parameter. when logged in, user preferences applies.
if LANDING_PAGE is not specified, DEFAULT_THEME parameter works fine.

Does this issue still occur?
If yes, feel free to reopen this issue.


Adds strict IRI validation following RFC 3987

Benchmark results:

Full validation based on this PR: 5.2s
Basic validation (very similar with the one from the RDF/XML and JSON-LD parser): 0.28s

Ok, so strict validation is ~20 times slower, which is quite a lot.
But ok, at least we know that.
Once this is merged, could you also do a quick perf check when this is plugged into the RDF/XML parser (with strict IRI validation enabled)? Perhaps the overhead compared to parsing is lower.


Remove camhead option

Headless is sufficient for MK.
Most users these days use a virtual environment so will not need headed for other projects.
If user needs headed they probably have skills to install it.
Giving user a headed option as standard is a choice they don't need IMO.

That option was added for a reason. On some platforms (such as pi) it is not feasible (maybe not possible) to compile headed opencv, so having the option is important. Is there some other reasoning behind removing it?

Yeah, it's a pointless bifurcation of choice but this comes from OpenCV.
If you already have the headed version installed demanding the headless version is going to require both version which is explicitly what OpenCV said do not do.
Inpain used to use the headed version and I we really can't make that decision for the end user. If we require OpenCV we must accept either the headed or headless version. And while headless is enough that is why it's called cam, the regular version with the gui stuff included gets camhead which is clearly more cryptic but also perfectly allowed.
We clearly prefer headless afterall, cam and all go with the headless version, but the full version with stuff we don't use is fine and can be included in a limited number of cases where the user has some requirements or a pre-established requirement to use one version rather than a different version. Tiger's also right that there's different support within opencv for the different version and it might be impossible to meet the requirements of one without meeting it for the other.

This should probably closed without merging unless there's a more robust rationale for the change.


⚠ Minecraft has degraded performance

In 65099fd, Minecraft (https://www.minecraft.net) experienced degraded performance:

HTTP code: 200
Response time: 1014 ms

Resolved: Minecraft performance has improved in c14227a.


Run tests automatically on Travis

It would be really great to run all the tests on Travis, for every pull request. Currently we just build the code using the HEAD of the closure-compiler. I discovered that Travis can run tests in Firefox using Karma so if we can make our tests Karma-compatible (I have no idea if that would be easy or hard to do) then we can run them on Travis, at least in one browser.

Finally done in https://github.com/google/closure-library/pull/528!


Release 0.1.14

Bump version: 0.1.13 → 0.1.14
Update changelog
Update changelog contributor credits

FYI all the links in the changelog and release are in the filepack repo, not here.

T_T

Thanks for reporting, I'll fix that.

Fixed in #544!


Add total buckets of sand count in the grinder to the plugin window

Would be nice to have it on the side panel as I usually deliver the sand and instantly run back without checking.

Fixed in #3

Plugin update submitted to the plugin hub in https://github.com/runelite/plugin-hub/pull/3373.


ModelPatcherAndInjector.unpatch_model() got an unexpected keyword argument 'unpatch_weights'

Heyyy Author,
Big fan of Animatediff,
I updated to the new Rewrite of IP adaptor node, and it broke,
I tried both Gen 1 and Gen 2 nodes, with Ip adaptor single and batch unfold node. No luck...
I'm Using simple Animatediff pipeline with new IP adaptor node. Also updated comfy and other nodes from manager,
Am I doing something wrong? or I just have to wait for animatediff to be compatible with the new IP update.
Error occurred when executing KSamplerAdvanced:

ModelPatcherAndInjector.unpatch_model() got an unexpected keyword argument 'unpatch_weights'

File "F:\Stable Diffusion\Stability Matrix\Packages\ComfyUI\execution.py", line 151, in recursive_execute
output_data, output_ui = get_output_data(obj, input_data_all)
File "F:\Stable Diffusion\Stability Matrix\Packages\ComfyUI\execution.py", line 81, in get_output_data
return_values = map_node_over_list(obj, input_data_all, obj.FUNCTION, allow_interrupt=True)
File "F:\Stable Diffusion\Stability Matrix\Packages\ComfyUI\execution.py", line 74, in map_node_over_list
results.append(getattr(obj, func)(**slice_dict(input_data_all, i)))
File "F:\Stable Diffusion\Stability Matrix\Packages\ComfyUI\nodes.py", line 1403, in sample
return common_ksampler(model, noise_seed, steps, cfg, sampler_name, scheduler, positive, negative, latent_image, denoise=denoise, disable_noise=disable_noise, start_step=start_at_step, last_step=end_at_step, force_full_denoise=force_full_denoise)
File "F:\Stable Diffusion\Stability Matrix\Packages\ComfyUI\nodes.py", line 1339, in common_ksampler
samples = comfy.sample.sample(model, noise, steps, cfg, sampler_name, scheduler, positive, negative, latent_image,
File "F:\Stable Diffusion\Stability Matrix\Packages\ComfyUI\custom_nodes\Comfyui-StableSR\nodes.py", line 75, in hook_sample
return original_sample(*args, **kwargs)
File "F:\Stable Diffusion\Stability Matrix\Packages\ComfyUI\custom_nodes\ComfyUI-Impact-Pack\modules\impact\sample_error_enhancer.py", line 9, in informative_sample
return original_sample(*args, **kwargs) # This code helps interpret error messages that occur within exceptions but does not have any impact on other operations.
File "F:\Stable Diffusion\Stability Matrix\Packages\ComfyUI\custom_nodes\ComfyUI-AnimateDiff-Evolved-main\animatediff\sampling.py", line 346, in motion_sample
latents = wrap_function_to_inject_xformers_bug_info(orig_comfy_sample)(model, noise, *args, **kwargs)
File "F:\Stable Diffusion\Stability Matrix\Packages\ComfyUI\custom_nodes\ComfyUI-AnimateDiff-Evolved-main\animatediff\utils_model.py", line 360, in wrapped_function
return function_to_wrap(*args, **kwargs)
File "F:\Stable Diffusion\Stability Matrix\Packages\ComfyUI\custom_nodes\ComfyUI-Advanced-ControlNet\adv_control\control_reference.py", line 47, in refcn_sample
return orig_comfy_sample(model, *args, **kwargs)
File "F:\Stable Diffusion\Stability Matrix\Packages\ComfyUI\comfy\sample.py", line 93, in sample
real_model, positive_copy, negative_copy, noise_mask, models = prepare_sampling(model, noise.shape, positive, negative, noise_mask)
File "F:\Stable Diffusion\Stability Matrix\Packages\ComfyUI\comfy\sample.py", line 86, in prepare_sampling
comfy.model_management.load_models_gpu([model] + models, model.memory_required([noise_shape[0] * 2] + list(noise_shape[1:])) + inference_memory)
File "F:\Stable Diffusion\Stability Matrix\Packages\ComfyUI\comfy\model_management.py", line 445, in load_models_gpu
cur_loaded_model = loaded_model.model_load(lowvram_model_memory)
File "F:\Stable Diffusion\Stability Matrix\Packages\ComfyUI\comfy\model_management.py", line 303, in model_load
self.model_unload()
File "F:\Stable Diffusion\Stability Matrix\Packages\ComfyUI\comfy\model_management.py", line 313, in model_unload
self.model.unpatch_model(self.model.offload_device, unpatch_weights=unpatch_weights)

```

Update AnimateDiff-Evolved, this was caused by a comfy update that came out a couple weeks ago and was fixed back then.
If updating did not work (and you are<PHONE_NUMBER>% sure it actually updated), then check your custom_nodes directory for either duplicate AnimateDiff-Evolved installs, or ComfyUI-AnimateLCM (which is not needed for anything as AnimateDiff-Evolved already supports AnimateLCM). If you have duplicate ComfyUI-AnimateDiff-Evolved installs of ComfyUI-AnimateLCM, since they are copies of my repo, the class definition will shadow each other and having a single un-updated version of ComfyUI-AnimateDiff-Evolved will override the updated ones.


[package] update FFmpeg binaries

Fix vpx flags for macos, see https://github.com/PyAV-Org/pyav-ffmpeg/pull/63

@uvjustin this makes use of the FFmpeg builds with your fix. Am I good to merge ?

Good to merge, thanks


Faster X-Rotations

Overview
We added 2 new CUDA kernels to accelerate x-rotations. They increase the speed of each rotation by ~2.5x, based on this benchmark.
We got the following results on a NVIDIA T4:

N Qubits
LABS (Before)
MaxCut (Before)
LABS (After)
MaxCut (After)
Improvement

22
1.5177
1.5227
0.5929
0.5926
2.56x

24
6.6131
6.6295
2.4754
2.4794
2.67x

26
28.5703
28.5143
11.5100
11.4985
2.48x

Approach
The in-place rotation kernel is applied $n$ times for $n$ qubits to perform a single rotation. We found that for every $k < n$ steps in the operation, we can divide the state vector into $2^{n-k}$ independent sub-groups. This allows us to process groups of states independently (requiring fewer synchronizations) and ensure that for each group all memory accesses are perfectly cached.
The furx_kernel uses shared memory to store all values for a given sub-group. $k$ is limited by the maximum shared memory size of the GPU and the maximum number of threads per block. For most modern GPUs we can at most allocate 64KB of shared memory per block, which is slightly below $16*2^{12}$ and thus limits us to $k \le 11$. We find that we achieve the best performance for $k = 10$, most likely because that requires only $512$ threads and achieves higher occupancy. We tried partitioning the data such that each thread is responsible for multiple rows, which gives us control over the number of threads needed independently of the shared memory requirement. Although this can lead to higher occupancy, we saw an overall decrease in performance and thus removed the partitioning. This mean $k$ is additionally limited to $\le 11$ because the kernel requires $t = 2^{k-1}$ threads per block and cuda only support a maximum of $t = 1024$.
The warp_furx_kernel does not use shared memory, but instead uses only registers and warp-shuffle primitives to exchange data. This implies the kernel is limited to $k \le 6$ because currently each warp has 32 threads. For $k \lt 6$ each warp handles multiple groups to ensure peak occupancy.
To perform a rotation we split up the $n$ steps into a sequence of calls to the furx_kernel with $k=10$ and a final call if $n$ is not a multiple of 10 to either the furx_kernel if $n \mod 10 \gt 6$ or the warp_furx_kernel otherwise. In total, instead of $n$ kernel calls, we know have $\lceil n/10 \rceil$ kernel calls for each rotation.
Possible Future Improvements
For the  warp_furx_kernel we only have 4 global memory accesses per thread, and no other memory accesses. The furx_kernel also only has 4 global memory accesses, but has $4*k$ shared memory accesses. It is possible to incorporate the warp level exchange into this kernel and to handle it as a sequence of 2 sub-groups. For example if $k=10$, we could process this as one $k=6$ and one $k=4$ (or whatever the most efficient distribution is) sub-group, where each sub-group can work purely on the warp level. This would reduce the shared memory accesses to $8$ for each thread, and only require $2$ block-level synchronizations, instead of $k$.
Furthermore, in terms of memory requirements, this approach of processing groups of states independently can allow us to work with a large number of qubits without requiring the whole state vector to be in memory at the same time. Groups could either be processes on multiple GPUs concurrently, or in sequence on a single GPU.

Confirmed the claimed performance:
	LABS finished in 0.5839 on average, min: 0.5792, max: 0.5895
	MaxCut finished in 0.5835 on average, min: 0.5790, max: 0.5872
N=24
	LABS finished in 2.4353 on average, min: 2.4193, max: 2.4506
	MaxCut finished in 2.4457 on average, min: 2.4352, max: 2.4561
N=26
	LABS finished in 11.3791 on average, min: 11.2953, max: 11.4151
	MaxCut finished in 11.3921 on average, min: 11.3866, max: 11.4027

@mebenstein-vorticity I'm seeing that one of the tests breaks after the change to cupy.
E   TypeError: Implicit conversion to a NumPy array is not allowed. Please use `.get()` to construct a NumPy array explicitly.

cupy/_core/core.pyx:1479: TypeError

Examining qaoa_objectives suggests that the error is caused by the GPU objective for "overlap" now returning a cupy array instead of a float:
In [1]: [type(x) for x in qaoa_objectives]
Out[1]: [cupy.ndarray, numpy.float64, numpy.float64]

In [2]: qaoa_objectives
Out[2]: [array(0.13751705), 0.13751704613944205, 0.1375170461394406]

Could you please fix? In general, it would be appreciated if you could run the tests locally before opening a PR. Thanks!

@mebenstein-vorticity I'm seeing that one of the tests breaks after the change to cupy.
E   TypeError: Implicit conversion to a NumPy array is not allowed. Please use `.get()` to construct a NumPy array explicitly.

cupy/_core/core.pyx:1479: TypeError

Examining qaoa_objectives suggests that the error is caused by the GPU objective for "overlap" now returning a cupy array instead of a float:
In [1]: [type(x) for x in qaoa_objectives]
Out[1]: [cupy.ndarray, numpy.float64, numpy.float64]

In [2]: qaoa_objectives
Out[2]: [array(0.13751705), 0.13751704613944205, 0.1375170461394406]

Could you please fix? In general, it would be appreciated if you could run the tests locally before opening a PR. Thanks!

I ran the unit tests before and after my changes, and this test was already failing before. You can see in my changes that we never change the array type and never return a cupy array. I only create a wrapper around the numba memory pointer and pass it to the the functions internally. I will look into it, but I am quite sure this error was there before.

I found the issue. Like I said, it was there before my changes. In the get_overlap method, it is trying to import cupy (which failed before because it was not in the dependencies). Now that it is included the test failed. I solved it by calling .item() on the output return value.

@mebenstein-vorticity I did some digging and it looks like the error was caused by the introduction of cupy dependency. I just rerun the version as of 778e129 commit and it passed all tests. However, after installing cupy, even the older version (778e129) fails the test.

LGTM. Once @gromitsun approves, we can merge.

@gromitsun confirmed via chat, merging


ERC1820 deployment: Unknown error Error: nonce too low

Hi did any one encounter this error?
I had this error when the deployment to ropsten went to the second file 2_erc1820_registry.js. The 3rd file 3_erc1400.js was deployed successfully, but I couldn't find the token generated on ropsten.
Here is the contract I deployed: https://ropsten.etherscan.io/address/0x9C7DbCcd5727C575a9d45601Ec078286Ff25c8c9
Thanks in advance.

ERC1820 is a unique contract registry. It is deployed at a pre-defined address (0x1820a4b7618bde71dce8cdc73aab6c95905fad24).
2_erc1820_registry.js migration file is useful in cases where ERC1820 is not deployed, like on private networks.
But on ropsten it is already deployed:
https://ropsten.etherscan.io/address/0x1820a4b7618bde71dce8cdc73aab6c95905fad24


Audio for passing parameters to the function

Description
I will do audio contribution on the topic "ways of passing parameters to the function".
Domain
C/CPP
Type of Contribution
Audio
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of this project.

/assign

/assign


Errors I do not understand

Type: Performance Issue
I downloaded Visual Studio
I installed python (recommended)- from Visual Studio
I installed C/C++ (recommended) - from Visual Studio
I installed java pack -manually as it gave me an error
When I tried java it game an error of json input, I closed and opened the programm and suddenly I have nothing installed, I google some possible solutions and I do the command Reset:Sync. I just have the same error everytime I want to download anything and I do not know what to do.
The error is:
2023-02-02 12:31:54.206 [error] Unexpected end of JSON input: SyntaxError: Unexpected end of JSON input
at JSON.parse ()
at Object.factory (vscode-file://vscode-app/private/var/folders/x5/wp7qgyjd50jbwf3y6b1bsq9c0000gn/T/AppTranslocation/89029B15-682D-40EF-847A-11608D4E1559/d/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/code/electron-browser/sharedProcess/sharedProcessMain.js:87:91783)
VS Code version: Code 1.74.3 (Universal) (97dec172d3256f8ca4bfb2143f3f76b503ca0534, 2023-01-09T17:07:18.579Z)
OS version: Darwin x64 20.3.0
Modes:
Sandboxed: No

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-8210Y CPU @ 1.60GHz (4 x 1600)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
14, 18, 11

Memory (System)
8.00GB (0.20GB free)

Process Argv
--crash-reporter-id 0d7775b3-c58f-4259-a652-88bfe479addb

Screen Reader
no

VM
0%

Process Info
CPU %	Mem MB	   PID	Process
   19	   115	 93323	code main
    9	    41	 93337	   gpu-process
    0	    16	 93338	   utility-network-service
    0	   246	 93340	   window (Extension: C/C++ Extension Pack)
    0	   106	 93349	   shared-process
    0	    41	 93351	     ptyHost
    0	     0	 93372	       /bin/bash --init-file /private/var/folders/x5/wp7qgyjd50jbwf3y6b1bsq9c0000gn/T/AppTranslocation/89029B15-682D-40EF-847A-11608D4E1559/d/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/contrib/terminal/browser/media/shellIntegration-bash.sh
    0	    33	 93357	     fileWatcher
    0	     0	 93409	     /bin/ps -ax -o pid=,ppid=,pcpu=,pmem=,command=
    0	    49	 93350	   extensionHost
    0	    66	 93399	   window (undefined)
    0	    74	 93407	   issue-reporter

Workspace Info
;

Extensions: none
A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstes627cf:30244335
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vsdfh931cf:30280410
vshan820:30294714
vstes263cf:30335440
pythondataviewer:30285071
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593:30376534
pythonvs932:30410667
cppdebug:30492333
vsclangdc:30486549
c4g48928:30535728
dsvsc012cf:30540253
azure-dev_surveyone:30548225
vsccc:30610678
pyindex848:30577860
nodejswelcome1:30587005
282f8724:30602487
f6dab269:30613381
pythonsymbol12:30652348

I am not sure this issue is related to VS Code. Can you share a screenrecording of the bug you encountered?

https://user-images.githubusercontent.com/84547453/216403961-ac3da22d-adc3-4787-af7d-6b166b8fc668.mov

there you have

That popup says "see the logs for details"... So do it and provide those details here.

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Handle repo cleanup race more elegantly

Due to recent changes in the way repositories are cleaned up after deletion on GitHub.com, we can find ourselves in a race where the queued linguist job runs moments after the repository cleanup job has removed the repo from disk resulting in Linguist attempting to run on a non-existent directory.
This leads to the following exception:
git-linguist failed: fatal: Unable to read current working directory: No such file or directory
/data/github/releases/deploy-b/vendor/gems/2.4.3/ruby/2.4.0/gems/github-linguist-5.3.3/bin/git-linguist:122:in `pwd': No such file or directory - getcwd (Errno::ENOENT)
	from /data/github/releases/deploy-b/vendor/gems/2.4.3/ruby/2.4.0/gems/github-linguist-5.3.3/bin/git-linguist:122:in `git_linguist'
	from /data/github/releases/deploy-b/vendor/gems/2.4.3/ruby/2.4.0/gems/github-linguist-5.3.3/bin/git-linguist:146:in `<top (required)>'
	from /data/github/releases/deploy-b/bin/git-linguist:8:in `load'
	from /data/github/releases/deploy-b/bin/git-linguist:8:in `<main>'

Yes, ideally the job should be removed before it's run, but until then, this PR goes towards addressing this by a) not attempting to print the current directory in the event it goes missing, and b) printing the error to STDERR instead of raising another exception.
The lack of the directory in the error message reduces user-friendliness ever-so-slightly, but the removal of the exception improves it vastly.
Previously when run on a non-repo directory:
$ ~/github/linguist/bin/git-linguist stats
fatal: Not a git repository (or any of the parent directories): .git
/Users/lildude/github/linguist/bin/git-linguist:123:in `git_linguist': git-linguist must be run in a Git repository (/Users/lildude/Downloads/trash/foo.XX) (RuntimeError)
	from /Users/lildude/github/linguist/bin/git-linguist:150:in `<main>'
$

Now...
$ ~/github/linguist/bin/git-linguist
fatal: Not a git repository (or any of the parent directories): .git
git-linguist must be run in a Git repository
$

I did think of keeping the directory in the message and catching Errno::ENOENT but that would still have left a pretty 🤢  user-experience for peeps running on the CLI and would then have led to a RuntimeError we'd need to catch to keep our internal monitoring happy.  I like to think this approach is a happy compromise.
/cc @carlosmn & https://github.com/github/github/issues/81249

This provides a somewhat nicer message, but not that it won't stop the flurry of exceptions. For that we'll have to change the GitRPC call to ignore the error if the target directory doesn't exist (which we've done for other calls previously).

This provides a somewhat nicer message, but not that it won't stop the flurry of exceptions.

Wouldn't these changes stop the Errno::ENOENT exceptions and any other that come directly from Linguist?

Oh huh, these needles do look like they're coming out of linguist itself, rather than gitrpc raising when it exists with an error. No wonder there's a lot of them, each time this happens we run linguist six times concurrently.
I was thinking of https://haystack.githubapp.com/github/rollups/9cbdc9f4d37ff9c7dd4a31ca2fc06dd1 which is what the gitrpc system then generates (but it knows to simplify into a single exception).
Where is linguist set up to raise needles itself? Is that something we want to do for any uncaught exception? Or should we trust gitrpc to propagate the errors to haystack?

Where is linguist set up to raise needles itself? Is that something we want to do for any uncaught exception? Or should we trust gitrpc to propagate the errors to haystack?

AFAIK Linguist doesn't raise needles itself at all.
I'm not sure how the exceptions are being propagated up to haystack. Most of the exceptions I've seen have been via gitrpc or from github/github.

The stack trace shows that this is happening inside linguist. GitRPC would (and does, like the rollup I linked above) throw a GitRPC::Error https://github.com/github/github/blob/00b559e2f28b60147c38e9f7703cae21ebf61f77/vendor/gitrpc/lib/gitrpc/backend/language_stats.rb#L32 It's a script we shell out to, so it has no way of telling GitRPC to raise anything else.
The ENOENT needles' stack trace looks like
endor/gems/2.4.3/ruby/2.4.0/gems/github-linguist-5.3.1/bin/git-linguist:122:in `pwd'
vendor/gems/2.4.3/ruby/2.4.0/gems/github-linguist-5.3.1/bin/git-linguist:122:in `git_linguist'
vendor/gems/2.4.3/ruby/2.4.0/gems/github-linguist-5.3.1/bin/git-linguist:146:in `<top (required)>'
bin/git-linguist:8:in `load'
bin/git-linguist:8:in `<main>'

which is not a stack trace that GitRPC would even know how to recreate. The stack traces from GitRPC mention all the code in ernicorn, and usually all the stack trace from the app or job as well.
We have some setup in github/github config/initialization which sets up the failbot exit_hook. If linguist indirectly loads that, it might be setting it up (but that's just a guess at this point).
Either way, these ENOENT needles could only come from inside the git-linguist script, as there is no way to indicate to GitRPC that it should generate that needle. Inadvertent loading of github/github magic would be my bet, but I don't really know where they would actually be generated.

I guess I posted too quickly. I just ran strace -f git linguist and I can see the following interesting output:
[pid 47564] open("/data/github/releases/deploy-b/lib/github/config/failbot.rb", O_RDONLY|O_NONBLOCK|O_CLOEXEC) = 11
...
[pid 47564] open("/data/github/releases/deploy-b/vendor/gems/2.4.3/ruby/2.4.0/gems/failbot-2.0.1/lib/failbot/exit_hook.rb", O_RDONLY|O_NONBLOCK|O_CLOEXEC) = 11

which is how github/github sets itself up to report uncaught exceptions. So yeah, these are definitely coming from the git-linguist script.
Which still means that this change is going to shut them up by not bubbling up this uncaught exception. But we might still throw others. We can punt on that, but maybe the git_linguist method could rescue anything, print it out and exit 1 so this kind of thing doesn't happen in the future.

But we might still throw others. We can punt on that, but maybe the git_linguist method could rescue anything, print it out and exit 1 so this kind of thing doesn't happen in the future.

I did think about going that route, but wasn't sure this was "best practice".

print it out

Do you mean just the single error or the full stack too?

but wasn't sure this was "best practice".

I think i'ts fine because we're catching an exception and erroring out in our main function. Anything calling this script needs to react to an error exit code anyway.

Do you mean just the single error or the full stack too?

Either works, but I think I would print out stack trace too, so we know more exactly what went wrong. Otherwise we'll just have the stack trace from us calling it over RPC and that just shows uninteresting code.


Update to 1.2.171 + VK_KHR_synchronization2

I tried my best to implement Flag64 but i am not a rust god.

Thanks for taking the time really helpful.
I cant think of an easy way to get the correct flag type for formatting in the const KNOWN[(Flag,&str)] array.
For the present the flag>u32::max check seems save there are only the two flag64 types from synchronization2.

@Caradhrass Thanks for your patience, as mentioned in https://github.com/MaikKlein/ash/pull/403#discussion_r594607379 / https://github.com/MaikKlein/ash/pull/402#issuecomment-799658326 I have already been working on extending vk-parse with the appropriate field to distinguish the 32- and 64-bit variant, even though the all_bits > u32::MAX hack works for now; see #410 / #411.
As non-collaborator I am not allowed to mark my own review comments as resolved; feel free to close everything that has to be fixed so that we have a clear overview of what is done.
It remains to be seen what the best order is to merge all these PRs in; we can possibly get your solution in first including the wrapper for Synchronization2, then I'll have to do some conflict resolution to get the proper bitwidth variant on top.

@Caradhrass are you available to discuss how to proceed? My plan is to take in #410 / #411 first to use updated vk-parse for accurately distinguishing 32- and 64-bit fields now and in the future. Feel free to update this PR afterwards to resolve conflicts, but I can do that for you while maintaining authorship.
Sounds good?

Sure, just keep the synchronization2 part of this and I am happy.
That should stay the same regardless of the Flag64 generator used.

You've done an excellent job on the non-raw bindings so there's no reason to drop them nor change authorship :grinning:
I'll take care of rebasing this when the generator and flags are in, thanks!


Allow click columns to be specified for row selection

Just as the titles says - at the moment the whole row is used of the click - would be good to disallow certain columns.

This was done with the sRowSelector option


Remove excess Core/Assets files

Is your feature request related to a problem? Please describe.
There are a ton of unused files in the Core/Assets folders that could easily be removed without changing much at all.
Describe the solution you'd like
I want the files that are currently "orphaned" (have no scenes that use them) be deleted to reduce file size and ultimately build size. (And selfishly I want this done before Ludum Dare so I can have a smaller download size!)
Describe alternatives you've considered
Only alternative would be to not do this, but then the problems would persist.
Are you prepared to write the solution to this feature? If so please describe how you intend to implement it
Hell yeah!
Additional context
I am uncomfortable with how we call these resources "orphans". "I'm working on deleting orphans" feels objectively evil.

 Working on this now


Your documentation is really bad.

Hey,
Please explain how to use this plug-in a little better. Your documentation makes no sense. You also have a ton of files in which we have no idea what to do with.
It's a shame because this looks like it could be good.
Thanks,
RS.

I thought it had been explained clearly enough in wiki pages, I just don't understand what "no sense" means.  You can help me improve it anyway.

Cheers.

Sorry if it came off harshly, I was having a bad night trying to find a script, so I just made my own instead and it works great.
Your documentation doesn't explain how to install or use it. Some people don't use NPM or Bower, so then basically you have all these additional files which we have no idea what to do with. I'm a Web Dev with over 15+ years of experience and I'm just lost looking at the docs. While they are obviously advanced instructions, it's always nice to state what things actually are and put things in layman's terms. I tried installing, but I guess I'm missing something.
 ;)
Your scrollbar is very app'esk, so I'm looking forward to using it.

@TheOGL has a point. The docs make many assumptions about the developer environment. There is no "all-in-one" basic demo, such as ...

    <title>basic demo</title>
    <link rel="stylesheet" href="dist/smooth-scrollbar.css">

There's no quick reference to the size footprint of your script (75k for the JS).
There's no reference to controlling height or max-height at all in the docs.
There's no FAQ / common troubleshooting tips.

Despite this, anyone who sees how gorgeously your script performs will take the time to figure it out.

@neokio

There's no quick reference to the size footprint of your script (75k for the JS).

I don't mention it because I think there's no need to worry about content's size today. And the size of outputs depends on the tool you're using, with Babel@5 it's about 60KB and 75KB with Babel@6 :(

There's no reference to controlling height or max-height at all in the docs.

Well...limited height is necessary for a scrollable area, right? Just like what you do with native scrollbars.
The documentation is bad and I don't know how to improve it, any PR on it will be welcomed :)

Hey,
Well you could for starters explain how to install the script manually. For instance, what files do we need and what do we add to the the container? Is all we need the .js file? Also, how to we initialize it?

I'm going through this again because I can't seem to find an all in one scroller.
Looking through the src folder, I see tons of folders with js files... Are we suppose to add all these? Or is there one all in one file?

I managed to get it working, however does this script support horizontal scrolling? I see that it's supposed to but my mousewheel doesn't move the horizontal bar.

@TheOGL all right, my 15-year-trained web engineer. You've almost been coding since I was born, so I suppose that you can understand what I'm going to say despite my poor English.
First of all, there's no need to dive into codebase under src/, since they are written in ECMAScript 2016+. Have you noticed the big green DOWNLOAD button right on the homepage? Download and extract the source code, you can find the compiled code under dist/ directory. Then:

Including stylesheet inside your  tag: <link rel="stylesheet" href="dist/smooth-scrollbar.css">.

Importing scripts: `

Writing your scrollable blocks:

    some contents...

Make sure this block is scrollable - a calculatable width&height, a larger content and a smaller container.

Initializing smooth-scrollbars in your app.js, no need for import declarations as you've imported source files:
var scrollbar = Scrollbar.init(document.getElementById('scrollbar');

If you want to play anything with the instance scrollbar, check the API docs in the WiKi page here: https://github.com/idiotWu/smooth-scrollbar/wiki.

Horizontally scroll may be unsupported depends on the type of mouse you are using.

The first time I looked at it, it was hard to find the script since it was bloated with all separate files. It's also very confusing when you start off by explaining how to install with bower.
I managed to get it all working the other day, however it does not support horizontal scroll, so until it does, it's pretty unusable. You have something good here so I suggest digging into that.
Cheers,
Ryan

@TheOGL if you can't scroll horizontally now, you might not be able to do it anyway. Because I can't get deltaX from your mouse.


Fixed #26029 -- Allowed configuring custom file storage backends.

ticket-26029

@carltongibson Thanks for checking :+1:

buildbot, test on selenium.


Texture Loading

When Loading in a texture, it creates a .json file called "Texture#[insert number here].json". This file does not get renamed when you rename it and load a texture file, but instead creates a completely new .json file with the actual name and data in it.
This means that for every texture being loaded in via the editor, an empty, superfluous .json file is created.

Duplicate issue of #491


how to sent multiple number at same time

how to sent multiple number at same time
show some example code please

Hey @Sreejithtechno
You can pass multiple numbers separated by a ;
await telephony.sendSmsByDefaultApp(
    to: "1234567890;5724352435;24653456345",
    message: "May the force be with you!"
    );

It will send the sms to all the numbers. Although keep in mind that this may not work on all devices.

Attempting to send a message to multiple recipients using the semicolon separated list does not work on my Google Pixel 5.


[stable/traefik] Fixed icon url in chart.yaml

What this PR does / why we need it:
Fixed the broken icon url in the chart
Checklist

[X] DCO signed
[X] Chart Version bumped

/assign @nmengin

/ok-to-test

/lgtm


doc/api-extensions: /1.0 doesn't accept a trailing "/"

Documentation preview available at: https://linuxcontainers.org/lxd/docs/pr.11026/


Addresses several issues #gh-124, #gh-139, #gh-140

https://github.com/redis/redis-om-spring/issues/140
https://github.com/redis/redis-om-spring/issues/139
https://github.com/redis/redis-om-spring/issues/124

Also is it possible to do full text search in stream ? as one of the filters ?
Thanks