Bug: exclude quantityReserved from products (stockAvailability: IN_STOCK)

What are you trying to achieve?
Hello guys,
We're currently using the reservation feature in our project and we need to know which product is "virtually" out of stock (I mean products that can't be reserved anymore because of quantity - quantityAllocated - quantityReserved = 0).
Actually the GraphQL API is only computing quantity - quantityAllocated when the filter stockAvailability: IN_STOCK is present, so even product that are fully reserved are appearing in the request results.
Is it possible (the way you want) to add an additional argument to take quantityReserved into account.
Bellow the query that're using:
query GetProductsByCollection {
  products(
    filter: {
      collections: "Q29sbGVjdGlvbjox"
      stockAvailability: IN_STOCK
    }
    first: 100) {
    edges {
      node {
        id
        name
        variants {
          id
          name
          stocks {
            quantity
            quantityAllocated
            quantityReserved
          }
        }
      }
    }
  }
}

Thanks a lot for your help
Steps to reproduce the problem

Open the GraphQL playground
Paste this query:

query GetProductsByCollection {
  products(
    filter: {
      collections: "Q29sbGVjdGlvbjox"
      stockAvailability: IN_STOCK
    }
    first: 100) {
    edges {
      node {
        id
        name
        variants {
          id
          name
          stocks {
            quantity
            quantityAllocated
            quantityReserved
          }
        }
      }
    }
  }
}

What did you expect to happen?
Product that are fully reserved (quantity - quantityAllocated - quantityReserved = 0) need somehow to be excluded from the result.
Logs

stockAvailability: IN_STOCK

{
  "data": {
    "products": {
      "edges": [
        {
          "node": {
            "id": "UHJvZHVjdDo3",
            "name": "Product #1",
            "variants": [
              {
                "id": "UHJvZHVjdFZhcmlhbnQ6OA==",
                "name": "PRD1",
                "stocks": [
                  {
                    "quantity": 2,
                    "quantityAllocated": 1,
                    "quantityReserved": 1
                  }
                ]
              }
            ]
          }
        }
      ]
    }
  }
}

Environment
Saleor version: 3.7.11
OS and version: macOS Monterey 12.5

@peelar Is it a bug or it's the targeted behaviour (so a feature) ?

@0xWhiteleaf thanks for reporting, this is indeed a bug. We have added this to our backlog


style: format all markdown files

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 75.159%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
118

Relevant Lines:
157

💛  - Coveralls


Change default IDENTITY to 1,1

Hello,
Currently, the default IDENTITY is (0,1):

However, could you please change it to (1,1) as it has MS SQL Server Management Studio by default?

You must specify both the seed and increment or neither. If neither is specified, the default is (1,1).

Thanks.

Thank you for request

Also which DBeaver version do you use?

I am not the original submitter of this issue, but I encountered this today in DBeaver Community Version <IP_ADDRESS>405051837
In SQL Server, when you create a new identity column for a table and then click "Save", the resulting DDL defaults to an identity seed value of 0, which means the first record inserted into the table gets an id of 0.
@E1izabeth Would you be open to me submitting a PR to fix this?

@Sgierek106 we're open for contributions, sure. Here is some useful information on this matter https://github.com/dbeaver/dbeaver/wiki/Contribute-your-code


About the use of large matrix causes Memory Error

不好意思打搅了, 我在使用较大的图, 调用deeprobust.graph.utils.preprocess时, 出现了内存超限的错误, 在调用时将sparse参数置为True会影响后面的训练吗, 谢谢!
Excuse me, I used a larger graph and called the function deeprobust.graph.utils.preprocess, which caused https://github.com/DSE-MSU/DeepRobust/blob/master/deeprobust/graph/utils.py#L32 to throw the Memory Error.
If I set sparse to True: adj, features, labels = preprocess(adj, features, labels, sparse=True), does it affect the training behind? Thank you!

Hi ZhangYikaii,
Sorry for the late reply.
It depends on what model you are using now. Some models require the input graph to be dense graph. If you are using Metattack/PGD/MinMax/ProGNN, it would throw an error.

Hi ChandlerBang, Thank you very much for your reply.
ProGNN seems to use Metattack when generating Attack samples generate_attack.py. Actually I have tried to change the Metattack source code in many places when I use sparse tensor.
For example, when adj is sparse, the type conversion of this code is repeated: https://github.com/DSE-MSU/DeepRobust/blob/master/deeprobust/graph/global_attack/mettack.py#L256
Is there any other way to deal with large matrices?
Anyway, thank you very much for the method proposed in your paper!

Actually ProGNN directly loads the pre-attacked graph in link without calling generate_attack.py.
The operation that requires dense input graph is torch.svd() and the reconstructed graph from SVD is a also dense matrix. Although you may use scipy.sparse.linalg.svds to do a sparse SVD, to reproduce the reported results in the paper, I would suggest you to still use dense graph and try to find a machine with larger RAM and large GPU memory (12GB).

Thank you very much!


BIG-IP clustering fails when BIG-IPs have IPv4 and IPv6 management and self IP addresses

Environment

Declarative Onboarding Version: 1.18.0-4
BIG-IP Version: <IP_ADDRESS> 0.0.8

Summary
My BIG-IPs are configured with IPv4 and IPv6 addresses on the management interface. They are also configured with both IPv4 and IPv6 self IPs. When attempting to configure a BIG-IP cluster using the IPv4 management IP addresses for the remoteHost in DeviceTrust and the owner and members in DeviceGroup and the IPv6 self IPs for the failoverAddress and configsyncIp, the DO declaration runs out of retries without ever successfully creating the device group.
I think this will no longer be an issue for my use case once https://github.com/F5Networks/f5-declarative-onboarding/issues/198 is fixed, but it is not clear what is invalid about doing things this way either.
I am able to work around this issue by using IPv6 self IPs everywhere and changing the DeviceGroup owner property to use a JSON pointer: /Common/trust/remoteHost.
Steps To Reproduce
Steps to reproduce the behavior:

Configure two BIG-IPs with IPv4 and IPv6 addresses on the management interface and with IPv4 and IPv6 self IPs
Submit the following declaration. The DeviceTrust remoteHost and DeviceGroup owner and members are the IPv4 management IP addresses to work around the fact that IPv6 addresses can't be used for the DeviceGroup owner attribute (using the IPv4 self IP addresses here does work, unfortunately the automation creating the request does not have these currently). The failoverAddress and configsyncIp addresses are the IPv6 self IPs we want to use for failover:

{
    "async": true,
    "schemaVersion": "1.18.0",
    "Common": {
        "trust": {
            "localUsername": "admin",
            "remoteHost": "<IP_ADDRESS>",
            "remoteUsername": "admin",
            "class": "DeviceTrust"
        },
        "f5test-ha-dg": {
            "autoSync": true,
            "fullLoadOnSync": false,
            "saveOnAutoSync": false,
            "members": [
                "<IP_ADDRESS>",
                "<IP_ADDRESS>"
            ],
            "asmSync": false,
            "owner": "<IP_ADDRESS>",
            "networkFailover": true,
            "type": "sync-failover",
            "class": "DeviceGroup"
        },
        "failoverAddress": {
            "class": "FailoverUnicast",
            "address": "fd32:f5:0:a70::2aa1",
            "port": 1026
        },
        "class": "Tenant",
        "configsync": {
            "configsyncIp": "fd32:f5:0:a70::2aa1",
            "class": "ConfigSync"
        }
    },
    "class": "Device",
    "label": "BVT BIG-IP declaration for DO"
}

Observe the following error response:

{
  "id": "4b5484ff-eaed-4d77-917b-7d685913c18a",
  "selfLink": "https://localhost/mgmt/shared/declarative-onboarding/task/4b5484ff-eaed-4d77-917b-7d685913c18a",
  "code": 500,
  "status": "ERROR",
  "message": "rollback failed",
  "errors": [
    "tryUntil: max tries reached: tryUntil: max tries reached: 01020036:3: The requested device group (/Common/f5test-ha-dg) was not found.",
    "unicastAddresses.map is not a function"
  ],
  "result": {
    "class": "Result",
    "code": 500,
    "status": "ERROR",
    "message": "rollback failed",
    "errors": [
      "tryUntil: max tries reached: tryUntil: max tries reached: 01020036:3: The requested device group (/Common/f5test-ha-dg) was not found.",
      "unicastAddresses.map is not a function"
    ]
  },
  "declaration": {
    "async": true,
    "schemaVersion": "1.18.0",
    "Common": {
      "trust": {
        "localUsername": "admin",
        "remoteHost": "<IP_ADDRESS>",
        "remoteUsername": "admin",
        "class": "DeviceTrust"
      },
      "f5test-ha-dg": {
        "autoSync": true,
        "fullLoadOnSync": false,
        "saveOnAutoSync": false,
        "members": [
          "<IP_ADDRESS>",
          "<IP_ADDRESS>"
        ],
        "asmSync": false,
        "owner": "<IP_ADDRESS>",
        "networkFailover": true,
        "type": "sync-failover",
        "class": "DeviceGroup"
      },
      "failoverAddress": {
        "class": "FailoverUnicast",
        "address": "fd32:f5:0:a70::2aa1",
        "port": 1026
      },
      "class": "Tenant",
      "configsync": {
        "configsyncIp": "fd32:f5:0:a70::2aa1",
        "class": "ConfigSync"
      }
    },
    "class": "Device",
    "label": "BVT BIG-IP declaration for DO"
  }
}

Expected Behavior
BIG-IP cluster should be created successfully.
Actual Behavior
BIG-IP cluster fails to be created.
Attached is a snippet of the /var/log/restnoded/restnoded.log showing the errors while this is waiting to time out:
restnoded.log

Moved the log output to an attachment to reduce the character count of the issue description. It was causing some problems for our internal tracker.

Moved the log output to an attachment to reduce the character count of the issue description. It was causing some problems for our internal tracker.

Thank you for reporting this issue. I have added it to our internal product backlog as AUTOTOOL-2218.

Are you still seeing this issue with the latest release (v1.22.0)?

This issue is being automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.


Beautiful work! Would like to ask how to adapt velodyne LiDAR? Thanks!

Thank you for your interest, and sorry for the late reply!
Unfortunately, this repository is utilized the intensity and ambient channels. In the case ambient (these days, called NIR), it is only involved in Ouster LiDAR, this repository does not seem to fit your request.
However, even if it is no matters in utilizing only intensity information with velodyne LiDAR , I recommend to use the intensity-slam.


Adjusting contact route interface

Just fixing some elements on the contact page. (image below)
I've already opened an issue: https://github.com/toddjordan/ember-cli-tutorial-style/issues/11

Thanks =)

Tried out the changes and looks good.  Thanks so much for the fix!


Fix typos in Xshm and make Xshm-struct members public

Hi,
I'm a user of this lib for xgifwallpaper For that, I'm using the Xshm-extension. Thanks for adding support!
This pull-request addresses some minor typos in the xshm module. But really important are the public struct members. Otherwise the module is not usable.

[x] Tested on an x11 machine
[x] Compilation warnings were addressed
[x] cargo fmt has been run on this branch
[x] cargo doc builds successfully
[x] Added an entry to CHANGELOG.md if knowledge of this change could be valuable to users
[x] Updated documentation to reflect any user-facing changes
[ ] Created or updated an example program if it would help users understand this functionality

Nice PR bro


release: 0.4.1

:robot: I have created a release beep boop
0.4.1 (2022-10-09)
Performance Improvements

perfect use go 1.19 (a621de0)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/starudream/creative-apartment/releases/tag/v0.4.1 :sunflower:


Add MarkApplicantParser and update classes related

Codecov Report

Merging #89 (5645188) into master (861f1ba) will increase coverage by 1.19%.
The diff coverage is 75.00%.

@@             Coverage Diff              @@
##             master      #89      +/-   ##
============================================
+ Coverage     73.10%   74.29%   +1.19%
- Complexity      473      545      +72
============================================
  Files            82       90       +8
  Lines          1491     1747     +256
  Branches        158      204      +46
============================================
+ Hits           1090     1298     +208
- Misses          342      383      +41
- Partials         59       66       +7

Impacted Files
Coverage Δ

...main/java/seedu/address/commons/core/Messages.java
0.00% <ø> (ø)

...address/logic/commands/applicant/AddApplicant.java
66.66% <ø> (ø)

...ddress/logic/commands/applicant/MarkApplicant.java
0.00% <0.00%> (ø)

.../seedu/address/logic/parser/AddressBookParser.java
76.19% <0.00%> (-12.70%)
:arrow_down:

...ss/logic/parser/applicant/MarkApplicantParser.java
0.00% <0.00%> (ø)

...seedu/address/model/applicant/InterviewStatus.java
36.36% <0.00%> (+36.36%)
:arrow_up:

...ain/java/seedu/address/storage/StorageManager.java
94.44% <ø> (ø)

...in/java/seedu/address/logic/parser/ParserUtil.java
74.66% <35.71%> (-2.53%)
:arrow_down:

...main/java/seedu/address/model/applicant/JobId.java
70.00% <70.00%> (ø)

...licant/NameApplicantContainsKeywordsPredicate.java
71.42% <71.42%> (ø)

... and 19 more

Continue to review full report at Codecov.

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


feat: add LTO support

Resolves https://github.com/grampelberg/kty/issues/19

That's great, thanks!


IrfanSkiljan.IrfanView version 4.66

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

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

Microsoft Reviewers: Open in CodeFlow

There is already a PR open... #132930


HuduAPI 2.2

Hello,
I am using your Hudu API powershell module and it is awesome!  Thanks for the hard work.
Can you update this to allow passwords to be updates/created into password folders?
password_folder_id is an available field... Hudu support confirmed...  It does not work in the API 2.2 I am using.

Implemented in #25


在windows 10 使用webpack打包不能打包

在windows 10使用webpack命令会提示选择编辑器，打开后编辑webpack.js。注意是只要包含webpack命令的都会这样

Update to webpack v2.3.2

And please write in english (via Translator etc.), bad/generated english is still way better than mandarin

It looks like you just deleted our lovely crafted issue template. It was there for good reasons. Please help us solving your issue by answering the questions asked in this template. I'm closing this. Please open a new issue with filled issue template. Also make sure your issue is not a question. Questions should be posted on Stack Overflow.


Document that hyper is using tracing

The main lib.rs page would benefit from a section explaining how to view logs in hyper.

Would it be best to do that while carrying #2261 to completion?

I think they can happen separately. Really, a larger tracing effort would be good to organize for hyper, as there's several metrics people would like to know, and some simple placement of spans and proper key-value designations in some events in hyper could allow them to more easily get that info.

@seanmonstar not sure if the docs here are sufficient to close this?
They'll expand as the implementation roles out, but right now have a 10,00ft view of what tracing in Hyper means (OTel semantic conventions).

The 1.0 docs now mention that tracing is available as an unstable feature. I think that's enough for now.


SitePicker shows App Catalog

Category

[ ] Question

Observed Behavior
Site Picker shows unwanted sites as well such as App Catalog. Is there a way to exclude/filter some sites?
Thanks!

Hi @spverma03 - sorry for the long delay.
We've introduced the new property additionalQuery?: string; that allows you to add an additional query to filter out sites you don't want.


Fix export(float ...) so that step is .01

So that in the property editor the range does not increment by integer step. Fix for #11964
@bojidar-bg pointed out those lines so I changed both. It's my first contribution to godot, so be blunt if I'm doing something wrong. Also if someone could explain to me what the functions I adjusted achieve on a higher level I'd appreciate that. I understand that it has something to do with display when the property editor is updated, but some more info would be cool.
Bugsquad edit: Fixes #11964.

Shoudn't you do something like (psuedo-cpp) type == TYPE_INT ? 1 : 0.01? This way, I guess, it wouldn't work for integers.

Well, it seems to work with export(int, 0, 100) because I'm assuming the int is casting the float.

I can still do it though.

are any tests needed?

@minifigmaster125 We don't have a test suite for the editor yet, so no tests needed.


Readme suggestions

Not really an issue but a suggestion for readme.
2 things you should mention to make it work:

You need to add using CommandTerminal; to be able to register commands
and you need to have CommandArg[] args as a parameter even if you don't have any parameters. This confused me as it wasn't showing up in commands and there were no errors.

And great stuff! Thanks a lot!

I realize the readme is quite minimal so I'll be sure to add a note about the using derivative.
The CommandArg[] parameter is shown in the examples, do you think a footnote about requiring it even in commands without parameters would be useful there?
Thanks for the suggestion!

How do you use a library without importing?


Testing steps

Hello,
This article is from 05/31/2017!
Azure portal changed long time ago, maybe it is time to review the setup?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 081729e5-959f-d8c2-de1b-b035c6dbc8fb
Version Independent ID: c93eda68-5b52-04bf-fca2-53bb7eba178a
Content: Azure AD Connect Multiple Domains
Content Source: articles/active-directory/hybrid/how-to-connect-install-multiple-domains.md
Service: active-directory
Sub-service: hybrid
GitHub Login: @billmath
Microsoft Alias: billmath

@lightupdifire Thanks for the feedback !  I have assigned this issue to content author to investigate and update the document as appropriate.

@SaurabhSharma-MSFT,
Thanks! I think procedure should be updated with latest Azure portal, latest AD Connect and latest ADFS steps.

@lightupdifire Thank you for the feedback.  I have created a backlog work item for this and will be working on this in the coming months.  I will send a follow-up once this has been updated.  Thanks!
#please-close


fix egde case in doc test setup

use '<IP_ADDRESS>' as bind host in order to prevent binding to interface that
does not support multicast

ack


adding default attr values for aws_ebs_volume introduced runtime error

volume = aws_ebs_volume 'ha-ebs' do
  availability_zone "#{node['qa-chef-server-cluster']['aws']['availability_zone']}" # => 'b'
  size 1
  device '/dev/xvdf'
  aws_tags node['qa-chef-server-cluster']['aws']['machine_options']['aws_tags']
end

# Breaks on the attachment resource
aws_ebs_volume 'ha-ebs' do
  machine 'bootstrap-backend'
end

It's comparing the default availability_zone 'a' to the 'b' in the previous resource.
 RuntimeError
    ------------
    aws_ebs_volume[ha-ebs] (vol-1eb0e10c).availability_zone is us-west-2a, but actual volume has availability_zone_name set to us-west-2b.  Cannot be modified!

Need to update resource to recall the availability_zone value when checking the immutable options.

applies to :size as well

There's a conflict here on the premise of allowing chef-provisioning to set sensible defaults, and the notion of failing the run when immutable attributes are changed via the resources.  The easy fix here would be to remove the default attribute values, and making the on-create attributes required (like device).
Another option would be to flip the idea of just allow chef provisioning to run but log a warning instead of raising the exception.  I don't particularly like this idea, but its an option.

Yeah, this is a good example of why it can be tricky to set defaults for attributes in Chef.  I didn't think about this back then.
The way we fixed this was to not have any defaults on immutable attributes, and instead defaulting them in the provider during the action_create method


Document extensibility interface

Need more detailed documentation around the extensibility interface. A few assets would be helpful:

Link to the Oni.d.ts file
Simple extensibility provider (maybe autocomplete months in the same vein as VIM)
Sample extensibility provider walkthrough - all the moving parts that are needed:

Package.json metadata
index.js to handle the requests / responses

Using #610 to track this now.


Update Species/Strain relations with Repository/Entry

[x] Add Species <> Repository foreign key
[x] Add Strain <> Entry foreign key
[x] Add database migrations
[x] Add tests
[x] Update database models projection

Coverage remained the same at 100.0% when pulling 07bcaf3df1717b2d6deff68f89c2226a48aeb77f on add-species-fk-to-repository into 47f351a7f72acf11c47d839989fd90be19be7d54 on master.


README: Clarify COPR distribution versions

Signed-off-by: Till Maas<EMAIL_ADDRESS>

This change is

Coverage remained the same at ?% when pulling e6148265f6c3568c4ac6d3a0af2df3b4734693fc on tyll:README into 167f75b64fc34ff1723d7a60fab3f93ef0ffc273 on nmstate:master.


why react-native-maps is getting crashed when coordinates is given from remote server.

Is this a bug report?
(Yes)

Have you read the Installation Instructions?
(Yes)
Environment

Steps to Reproduce

(1.installed "react-native-maps": "0.22.0"
2.Fetched coordinates from remote server node.js using POST
3.using Mapview.marker
4.App is getting crashed with error "Uncaught Error:Requiring unknown module "undefined"" when build,
5.It is working fine in devmode )

Expected Behavior

(Mapview should show markers with the coordinates from remote server)
Actual Behavior

(App Got Crashed)
package.json
{
"main": "node_modules/expo/AppEntry.js",
"scripts": {
"start": "expo start",
"android": "expo start --android",
"ios": "expo start --ios",
"eject": "expo eject"
},
"dependencies": {
"@expo/vector-icons": "^9.0.0",
"body-parser": "^1.17.2",
"concurrently": "^4.1.0",
"connect-history-api-fallback": "^1.6.0",
"dotenv": "^4.0.0",
"errorhandler": "^1.5.0",
"expo": "^32.0.0",
"firebase": "^5.8.4",
"lottie-react-native": "^2.5.11",
"moment": "^2.24.0",
"native-base": "^2.10.0",
"node": "^11.9.0",
"prop-types": "*",
"react": "16.5.0",
"react-native": "https://github.com/expo/react-native/archive/sdk-32.0.0.tar.gz",
"react-native-collapsible": "^1.4.0",
"react-native-datepicker": "^1.7.2",
"react-native-datepicker-modal": "^1.0.2",
"react-native-floating-action": "^1.14.1",
"react-native-gifted-chat": "^0.7.2",
"react-native-image-grid": "^1.0.0",
"react-native-image-picker": "^0.28.0",
"react-native-modal": "^7.0.2",
"react-native-maps": "0.22.0",
"react-native-parallax-scroll-view": "^0.21.3",
"react-native-progress": "^3.6.0",
"react-native-responsive-dimensions": "^1.0.2",
"react-native-share": "^1.1.3",
"react-native-simple-radio-button": "^2.7.3",
"react-native-tab-view": "^1.0.2",
"react-native-ui-kitten": "^3.1.2",
"react-navigation": "^3.0.9",
"react-navigation-backhandler": "^1.2.0",
"react-timer-mixin": "^0.13.4",
"validate.js": "^0.12.0"
},
"devDependencies": {
"babel-preset-expo": "^5.0.0"
},
"private": true
}
Reproducible Demo

(Paste the link to an example project and exact instructions to reproduce the issue.)

This seems to be an implementation issue. Without any code sample we cannot help.
I'll close this for now.


Create Dynamic Clipping library for impression and duration measurements

Background

For impression/duration measurements, we have to set an impression/duration cap to guarantee differential privacy
Currently, the measurement consumers(MC) select the cap, but it's challenging for MCs since the optimal cap should be chosen based on the frequency/duration distribution
The Dynamic Clipping library allows the EDP to automatically optimize the cap for each campaign and to achieve higher accuracy than using a fixed cap, based on the frequency distribution of the events

Need to Know
The Dynamic Clipping library is provided as a reference implementation for EDP to potentially improve impression/duration measurement accuracy. It is an optional EDP feature, and will require additional local market approval for deployment in production.
Reference
https://docs.google.com/document/d/1vboqbbHOqblYhooYCwAJ2fyqBCZOILFKmxtCm_O-kaY/edit
Rally task link: https://rally1.rallydev.com/#/?detail=/task/729250522061&fdp=true

This change is


during deploy, non-deploy branches should NOP

@homunkulus try

:hourglass: Trying commit 582e022 with merge 582e022...

:sunny: Test successful - status-appveyor, status-travis
State: approved= try=True

:sunny: Test successful - status-appveyor, status-travis
State: approved= try=True

:sunny: Test successful - status-appveyor, status-travis
State: approved= try=True

:pushpin: Commit fcd65aa has been approved by japaric

@homunkulus r+

:hourglass: Testing commit fcd65aa with merge fcd65aa...

:sunny: Test successful - status-appveyor, status-travis
Approved by: japaric
Pushing fcd65aab5ec32c44b98b5610fa60bbe2d5f92c2e to master...


Example of selecting option value using select step?

from user query in https://github.com/kelaberetiv/TagUI/issues/454#issuecomment-503546722

One more issue which I was facing was in the UI, I had a dropdown and based on the documentation I tried a few things but then the option value is not getting selected.
select //*[@id="abc1"]/div/div/div/div[1]/div/div/div/div[3]/div[1]/div/span[1]/div/select/ as Travelling
And even tried specifying the option number instead.
select //*[@id="abc1"]/div/div/div/div[1]/div/div/div/div[3]/div[1]/div/span[1]/div/select/ as 2 or select //*[@id="abc1"]/div/div/div/div[1]/div/div/div/div[3]/div[1]/div/span[1]/div/select/ as option[2]

The documentation didn't have many examples so was a little hard to follow. Can you help me out here?
Thanks.

@abhishek-27, first double check that the XPath element identifier is correct. You can do that by searching in Chrome web inspector, or trying to do a click action on the element with TagUI. Second is inspect the dropdown to see the value attribute of the option. TagUI uses the HTML value attribute of the option item as it is usually the unique identifier for the option. After that use that value as the second parameter.
Alternatively, you can consider writing custom JavaScript code and use dom step to send the JS code to browser to do the selection.
Or consider using visual automation to visually click on the dropdown menu and visually selecting the option you want. This way, don't have to use XPath or web selectors.

Yeah i got it working with dom step and query selector like this:
dom document.querySelector("#abc1 > div > div > div > div.insidePage_wrapper > div > div > div > div:nth-child(3) > div.apply_grid_container > div > span.apply_grid_col1 > div > select > option:nth-child(2)").setAttribute('selected', true)

Cool! wow this looks like a tough to locate web element, nested deep within the anchor tag 👍


Google Workspace: Add file path information

Description
Adds the file path information to the list of accessories.
closes #14874

Screencast

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

Maybe you can turn this hook into a useCachedPromise to add the file path information from there since I'm not sure it's possible to do that from useFetch.

It seems that useFetch can't be used inside useCachedPromise because both are hooks that handle asynchronous data fetching independently. React hooks must be called at the top level, and combining them would violate that rule.

@thomaslombart, do you mean to change it to this?


PostListItem Description Field

The PostListItem should have a post description field, and this field needs to be populated when a PostListItem is created in the methods in PostRepository

Never mind, its in the content field. The content field wasn't updating for me so I thought the description field was something else. User error as I didn't click the save button.


[Application] mnist: Fix tf example

Modified for tensorflow 2.10.0.
Signed-off-by: Jiho Chu<EMAIL_ADDRESS>

:memo: TAOS-CI Version: 1.5.20200925. Thank you for submitting PR #2072. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://ci.nnstreamer.ai/.

We generate a report if there are dangerous coding constructs in your code. Please read http://ci.nnstreamer.ai/nntrainer/ci/repo-workers/pr-checker/2072-202212201926360.84138488769531-ac20e47b0657b53bab3e24596ff198020212cbe7/report/pylint_result.txt.

LGTM! But "tf.compat.v1" also Deprecated in Tensorflow 2.x Version. I think We will fix Tensorflow Example

compat.v1 is checked as deprecated for some, but still working for many.
Toally deprecation would take long time. If you know the schedule of it, please let us know.


ApplicationLoadBalancedCodeDeployedFargateService generates an invalid alarm configuration.

If both the ResponseTimeAlarmThreshold property and the ApiTestSteps property of the ApplicationLoadBalancedCodeDeployedFargateService construct are not set, the AlarmRule property of the HealthAlarm resource  will be ().
Attempting to deploy such a stack will result in the following error.

Resource handler returned message: "Error in AlarmRule [Unsupported token ')' at char 1] (Service: AmazonCloudWatch; Status Code: 400; Error Code. ValidationError; Request ID: 89955519-71e5-4629-b72f-bdb728a7eb57; Proxy: null)" (RequestToken: 292bf444-de8e-fe00-f076-f96b46e4bbe6, HandlerErrorCode: InvalidRequest)

package version: 0.0.109

Repository for reproduction: https://github.com/aetos382/EmptyAlarm
problematic line: https://github.com/aetos382/EmptyAlarm/blob/99693aaa9a6eaa24e1be569aa1b99d76f846b232/cdk.out/EmptyAlarmStack.template.json#L509


KfJsonFlexible

closes #406
@l3r8yJ take a look, please

PR-Codex overview
This PR focuses on adding support for creating custom Kafka consumers and producers from JSON configuration files.
Detailed summary

Added KfJsonFlexible class for creating custom consumers and producers from JSON.
Modified ConsumerXmlMapParams and ProducerXmlMapParams to have public access.
Updated dependencies in pom.xml.
Added license headers to package-info.java and test files.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

@h1alexbel thank you for your Pull Request. I'll assign someone to review it soon.
If this PR solves a todo from the code, please don't forget to remove it.

@h1alexbel please review this Pull Request. Deadline (when it should be merged or closed) is 2023-07-10T10:59:05.416805.
You should check if the requirements have been implemented (partially or in full), if there are unit tests covering the changes and if the CI build passes. Feel free to reject the PR or ask for changes if it's too big or not clear enough.
Estimation here is 30 minutes, that's how much you will be paid. You will be paid even if this PR gets rejected.

@h1alexbel I think we need tests with reading and asserting values from json, wdyt?

@l3r8yJ These tests are already created and maintained by emotion, in JsonXML object
here, we just transform JSON to XML

@h1alexbel I think we need tests with reading and asserting values from json, wdyt?

@l3r8yJ These tests are already created and maintained by emotion, in JsonXML object here, we just transform JSON to XML

@h1alexbel so, has the produced xml been tested?

@l3r8yJ
yes, here it is

@rultor merge

@rultor merge

@h1alexbel OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@h1alexbel Done! FYI, the full log is here (took me 2min)

@h1alexbel thank you for resolving this ticket. I've just added it to your active invoice. You can always check all your invoices and more on the Contributor Dashboard.


Error opening modal window Shift + Enter

System information:

Windows 10 Pro x64
DBeaver <IP_ADDRESS>011291229
No additional extensions

Connection specification:

PostgreSQL 9.5
PostgreSQL JDBC Driver [42.2.5]
No tunnels or proxies (SSH, SOCKS, etc)

Describe the problem you're observing:
Modal does not open when trying to edit text cell (Shift + Enter)
Steps to reproduce, if exist:
Run the query below, stand on the code field in query results and press Shift + Enter (id field opens correctly)
select *
from(values(1,'123')) t(id, code)

Include any warning/errors/backtraces from the logs
error.log

I can open both cells. What do we do differently (I can open Edit window by Shift +Enter and by the button from the bottom toolbar)? Please note the cells are in read-only mode from this query because  do not have corresponding table column

Doesn't reproduces in version <IP_ADDRESS>012201616


Use list comprehension

WeatherData could be converted into a collections.namedtuple.

I tried to use list() instead loop here, but the code look ugly in order to fit PEP8.
Closing this PR due to overkill.


Segmentation fault on Linux Mint 20.2

I was really exited to test it but I get a segfault every times...
Tested the debian and tarball build on Linux Mint 20.2 ( / Unbuntu bionic) x86_64 (Linux 5.4.0-88-generic) inside VirtualBox.
I also attempted a custom build with cargo 1.56.0 with no better results.
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `binocle xq'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x00007fe980281b40 in ?? () from /usr/lib/x86_64-linux-gnu/libvulkan_lvp.so
[Current thread is 1 (Thread 0x7fe94d7fa700 (LWP 315115))]

$ dpkg -l | grep vulkan
ii  libvulkan1:amd64           <IP_ADDRESS>-1                amd64  Vulkan loader library
ii  mesa-vulkan-drivers:amd64  21.0.3-0ubuntu0.3~20.04.3  amd64  Mesa Vulkan graphics drivers

Thank you very much for reporting this. Unfortunately, I don't really know how to move forward with debugging this. Looks very much like it could be Vulkan related somehow, but I don't really have any experience with this. Does vkcube work for you?

Yes, vkube (from vulkan-tools amd64 <IP_ADDRESS>+dfsg1-1) does work.
The problem I get with binocle is weird; the interface does popup and display for a fraction of second before segfaulting.
If you can guide me through some steps to generate an useful trace, I will happily provide.

libvulkan_lvp.so is the LLVMpipe driver, which is known to have some bugs. Update to a more recent Mesa package might help...

@parasyte Thank you!! @romain-dartigues did you have a chance to test this?

With a lot of delay I finally tried @parasyte suggestion.
After adding kisak/kisak-mesa PPA the following packages were updated:

libdrm-amdgpu1 libdrm-common libdrm-intel1 libdrm-nouveau2 libdrm-radeon1 libdrm2 libegl1-mesa libgl1-mesa-glx libgles2-mesa libva-drm2 libva-wayland2 libva-x11-2 libva2 libwayland-egl1-mesa va-driver-all

Unfortunately libvulkan_lvp.so is provided by the package mesa-vulkan-drivers which was kept back (and it didn't affect the segfault).
So apt-get install mesa-vulkan-drivers=21.3.1~kisak2~f, apt upgrade, yada yada, then trying to recompile with cargo install --force (in doubt).
And now it does work.
Thank you Jay! Thank you Peter.


GO: 130. Surrounded Regions

File(s) Modified: 130-Surrounded-Regions.go.
Language(s) Used: Go
Submission URL: _https://leetcode.com/submissions/detail/762557388/_

Thanks, @MaratKhakim!


licenses missing from jars

Unlike other jackson projects, none of the modules have META-INF/LICENSE files added to the jars.

Right, I added missing NOTICE and LICENSEs the other day on format modules and jackson-jr.
I think most repos had them at some point but they were sometimes dropped when consolidating. And in this case probably just not copied over when cloning jaxrs-providers repo.

Fixed via #15.


Incorrect path to handler in openapi specification

Expected Behavior
Api1 has been installed in routing under /api1.
I would expect such a specification to be generated :
{
  "openapi": "3.0.0",
  "info": {
    "title": "Oneof",
    "version": "1.0"
  },
  "servers": [
    {
      "url": "http://localhost:3000/api1"
    }
  ],
  "tags": [],
  "paths": {
    "/api1/create-post": {
      "post": {

Actual Behavior
Extract from the current specification http://<IP_ADDRESS>:3000/spec1.json
{
  "openapi": "3.0.0",
  "info": {
    "title": "Oneof",
    "version": "1.0"
  },
  "servers": [
    {
      "url": "http://localhost:3000/api1"
    }
  ],
  "tags": [],
  "paths": {
    "/create-post": {
      "post": {

Steps to Reproduce the Problem
I created a test repository https://github.com/szagi3891/poem-test
You have to clone and then run with cargo run
A swagger will be available at "http://<IP_ADDRESS>:3000/ui1"
Specifications
Version: poem = "1.0.34", poem-openapi = "1.0.35"
Platform: MacOs
Subsystem:
struct Api1 {}

#[OpenApi]
impl Api1 {
    pub fn new() -> Api1 {
        Api1 {}
    }

    #[oai(path = "/create-post", method = "post")]
    async fn create_post(
        &self,
        obj: Json<MyObj>,
    ) -> CreateBlogResponse {

        CreateBlogResponse::Ok(Json(444))
    }
}

    let api1 = Api1::new();

    let api_service1 = OpenApiService::new(api1, "Oneof", "1.0").server("http://localhost:3000/api1");
    let ui1 = api_service1.swagger_ui();
    let spec1 = api_service1.spec_endpoint();

    let api2 = Api2::new();

    let api_service2 = OpenApiService::new(api2, "Oneof", "1.0").server("http://localhost:3000/api2");
    let ui2 = api_service2.swagger_ui();
    let spec2 = api_service2.spec_endpoint();

    Server::new(TcpListener::bind("<IP_ADDRESS>:3000"))
        .run(Route::new()
            .nest("/spec1.json", spec1)
            .nest("/api1", api_service1)
            .nest("/ui1", ui1)
            .nest("/spec2.json", spec2)
            .nest("/api2", api_service2)
            .nest("/ui2", ui2)
        )
        .await

This method could potentially take an additional parameter:
let spec1 = api_service1.spec_endpoint("/api1");
which would specify the base address to which this part of the api has been mounted.
It would probably be a good idea to add such a parameter also for the method :
let ui1 = api_service1.swagger_ui();

TypeError: Failed to execute 'fetch' on 'Window': Request with GET/HEAD method cannot have body.

When I changed the method to POST, everything worked fine.
#[oai(path = "/hello", method = "post")]
async fn create_post()

The point is that the "create_post" method is available at: "http://<IP_ADDRESS>:3000/api1/hello"
If I send this http request:
POST http://<IP_ADDRESS>:3000/api1/hello
Content-Type: application/json
Accept: application/json

{
    "type": "A",
    "v1": 0,
    "v2": "dddsssaaaa"
}

I will receive a reply from the server:
HTTP/1.1 200 OK
content-type: application/json
content-length: 3
date: Sun, 05 Dec 2021 13:17:57 GMT

444

This behaviour is obviously correct.
The problem is that the path in the specification is generated like this:
"paths": {
  "/hello": {
    "post": {

In the specification, the location should be "/api1/hello".

I made a new handler in this sample repo: http://<IP_ADDRESS>:3000/spec1-correct.json
I made a function that changes the generated specification and adds this prefix:
fn add_base(base: impl Into<String>, spec: &String) -> String {

Question, can this be integrated into poem-openapi somehow ?

I made a new handler in this sample repo: http://<IP_ADDRESS>:3000/spec1-correct.json
I made a function that changes the generated specification and adds this prefix:
fn add_base(base: impl Into<String>, spec: &String) -> String {

Question, can this be integrated into poem-openapi somehow ?

Ah, I see what you want, it's easy.
#[OpenApi(prefix_path = "/api1")]

.nest_no_strip("/api1", api_service1)

You only need to change these two places.

@sunli829 Thank you very much. It works fantastically :)


Multiple issues in register command

Use of undefined variables name, role, keyid
Unused variable isfirst
Aborts leaving half-written file plus .bak if the user exists and no --overwrite
Doesn't actually overwrite if --overwrite
sys.path.exists should be os.path.exists
[minor] Subject to IndexError in case of bad input CSV

Thanks for the great testing @welshjf! Please address these issues for the MVP.

Git Guild Bounty Program

Total
Dev
Sales
Reporter
Tester(s)
Maintainer
Documenter

N/A
assignee(s)
N/A
@welshjf
@isysd, @d3brouille
@isysd
@d3brouille

$609.58
$385.00
$0.00
$32.08
$128.33
$32.08
$32.08

Testing Results

Use of undefined variables name, role, keyid

Variables name, role, keyfp replace these undefined variables.

Unused variable isfirst

Removed.

Aborts leaving half-written file plus .bak if the user exists and no --overwrite

No longer utilizes .bak file, Previous bug is now handled by throwing an error and returning. Before, program would abort after creating new members and .bak, which lead to os.remove never being called.

Doesn't actually overwrite if --overwrite

Confirmed with timestamps that --overwrite now properly overwrites old members file.

sys.path.exists should be os.path.exists

Fixed - no longer contains sys.path.exists

[minor] Subject to IndexError in case of bad input CSV

Fixed by removing direct assignments to each index position in row[]


[Provider] Allow for configurable timeout and retries

Is your feature request related to a problem? Please describe.
I've been traveling and thus have a bit poor connection issues. As part of that, I've been having connection timeout issues as seen in #74 when using providers.
Describe the solution you'd like
Constructing a provider should allow for a customizable connection timeout and retries for each call.
Bonus: Allowing for customizable tries and timeouts per individual call would be nice. For example, a large query for blocktx might take longer than getBalance, so therefore, we should be able to customize it to tailor our needs.
Describe alternatives you've considered
Additional context
Slow internet shannegians :(

Since updating to PocketJS 2.1.0, timeout errors have become less of a problem (haven't gotten one yet). I am not sure if this due to fact I moved to JSONRPCProvider from IsomorphicProvider or if it was due to the update.


Monospaced font option!

Is your feature request related to a problem? Please describe.
No problems but I find that JSON and GraphQL queries are easier to read/write in a monospaced font (what I'm used to as a developer).
Describe the solution you'd like
I would love a monospaced font inside the editor and result windows :) Even better, let me choose a system font.

@elloboblanco I don't know if you have seen #228 and #265.

Oh no! I had no idea this was by design. Maybe I could feature request theme-ability on top of just "dark" or "light"?

So sad this is by design. The monospaced font in programmers tools is not just cosmetic preference, it's usability option. It's so easy to add custom font-family and font-size (for those of us who has bad vision). I thought I found an ideal tool for GraphQL but alas.

So you want a customisation option for font family?

Yes, it would be cool.

What is the outcome of this? It was added to a completed milestone and not implemented.
I'm moving off of Altair because of the lack of this font family configuration.

@grrttedwards Shouldn't you just ask about it, or even try looking at the commit that closed this issue, rather than jumping into conclusions.
There is no reason why you should limit yourself to Altair. There are many other options to choose from.

@imolorhe Could you show a configuration that uses a monospace font. From the commit it isn't clear how to set that.

{
  "theme": "light",
  "language": "en-US",
  "addQueryDepthLimit": 3,
  "tabSize": 2,
  "theme.editorFontFamily": "monospace"
}

Is how you get it working


Add pic to menu

Need to add a POST /api/menu/:menuId/pic route.
Need to add testing to verify that the image is properly sent and received.

PR #57

Testing is separate issue


Rav4 PHEV plug in range

Thank you for this integration. I report that the Toyota integration for the Rav4 PHEV has lost the Range (that is the battery range that reported in miles). The display shows unavailable and I confirm that in April it was working. I have not changed the configuration.

We recently released version 2.0.0 of the Custom Component with major changes and support for the new Mytoyota API.
As we unfortunately cannot provide support for Custom Component versions < v2.0.0, I hereby close your issue.
If the issue still applies to the current version, you are of course free to open a new issue. 😊


[release-0.53] [e2e-tests]Should remove and restore labeler only from workers

What this PR does / why we need it:
This is a manual cherrypick of https://github.com/kubevirt/kubevirt/pull/9215
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:

NONE

/cc @Barakmor1 @enp0s3

/lgtm


W5500::peek ignores the number of bytes available for read

Hi!
First of all, great work on the driver library. I am making use of this as part of a custom board I am designing for home automation.
It would be good to get a LICENSE file attached to this project.
I think there is an issue with the peek function, in that it completely ignores how many bytes are available in the RX buffer of the W5500 chip.
This would mean that it is possible for the READ pointer to go past the WRITE pointer and effectively start reading garbage. The correct implementation for peek should probably be:
size_t W5500::peek(uint8_t socket, uint8_t *buffer, size_t size) {
    // Set up the read transaction
    uint8_t cmd[3];
    uint16_t read_offset = get_rx_read_pointer(socket);
    // <<<<<<<<<<< Begin changes <<<<<<<<<<<<<<<
    uint16_t write_offset = get_rx_write_pointer(socket);
    if (write_offset < read_offset) {
      size = write_offset + (0xFFFF - read_offset) + 1;
    } else {
      size = write_offset - read_offset;
    }
    // <<<<<<<<<<< End changes <<<<<<<<<<<<<<<<<
    cmd[0] = (read_offset >> 8) & 0xFF;
    cmd[1] = read_offset & 0xFF;
    cmd[2] = (
        (SOCKET_RX_BUFFER(socket) << 3) |
        (0 << 2) | // Read
        0x0 // Always use VDM mode
    );
    _bus.chip_select();

    // Initiate the read
    _bus.spi_xfer(cmd, nullptr, 3);

    // Read the data
    _bus.spi_xfer(nullptr, buffer, size);

    // Done
    _bus.chip_deselect();

    // Return the amount of bytes that were actually sent
    return size;
}

If I manage to create a working solution for this, I'll send a PR, but for now I wanted to get a discussion going.

Hi cvicentiu, I've added a MIT license to the repo. Feel free to use this code for whatever purpose.
With regards to peek - I dug out my old code that used this library, and it looks like the access pattern I had was to first call W5500::get_rx_byte_count in my application code to determine the number of bytes actually residing on chip, and then peek only that amount of bytes. I suppose there's no harm in including that call to get_rx_byte_count inside of peek and using MIN(size, rx_byte_count) as the number of bytes to then read from the buffer. If you want to make a PR that does that, and test it out on some hardware (I don't believe I have anything with this IC lying around still), I'd be happy to merge it.

@rschlaikjer Thanks for the quick reply!
I did discover get_rx_byte_count shortly after creating this issue. The main concern I have is that the datasheet doesn't seem to clearly state that the particular register handles the overflow case properly.(for example READ offset = 0xFFFF, write offset = 0x10)  It only says that it returns the difference between the WRITE offset and READ offset registers. In any case, I'll test it out. Given that your code worked, I assume the IC covers this case.
I have a board available and once I get everything working I'll create a PR for this.


CommandPrompt Activation

Description
I added the "AppExecutionAlias" files.exe, so the app can be launched from any command prompt.
In the folder %localappdata%\Microsoft\WindowsApps is now files.exe created, which helps #236.
I also did some testing with opening files in the current directory from the cmd, but there is currently a race condition between the app startup and the PopulateDrivesListWithLocalDisks-method, which does not populate the list fast enough. At a normal start from the cmdline, it always crashes, in the debugger with a breakpoint not. This only occurs if files wants to show the current directory.
Questions
I would love some input on the cmdline-protocoll: Which commands, ...
PS:
The code as is does not support open in a directory, but works, in that it opens files. Don't know if you want to merge this as whole or as little parts.

Do not merge
Please do not merge. Code is broken.

I added a parser and implemented the command:
files.exe -Directory C:\Users

!!!The crash is not fixed!!!

@lampenlampen Would threading be a way out of the race condition?

I'm currently trying to convert the list to a task-based approach, so we can await them.

@lampenlampen The WIP branch for the settings view model might simplify/remove some of the list items.

I had a look at the branch and i basically had the same idea. You can have a look at https://github.com/lampenlampen/files-uwp/commit/496a84e2c2f0efd7e3f6f4571d97bd297a13ce01.
I extracted all "drives"-related things to it's own class and added an Drives-property to the SettingsViewModel.
Please leave a short answer, if you want to refactor these yourself or i can go ahead.

Your implementation looks better than mine! For now, don't worry about my branch, as I can refactor those changes later

@lampenlampen I probably won't have the time to make any refactors myself until Friday at the earliest, so if you can that would be excellent!

@duke7553 I saw that your are using "mvvmlight" and ViewModelBase. I had a brief look at their github repo, but docu is a bit rare there. Can you point me to something, that explains ViewModelBase.

This sounds like a question for @yaichenbaum 😀

I would check out http://www.mvvmlight.net/


Automatically recover consumer

Hi,
I was reviewing this gem and it seems to me that it happened to not enable recover_cancelled_consumers flag on the worker queue channel.
The flag causes the consumers to resubscribe to queues after network failure recovery. You can see that in the bunny gem code here: https://github.com/ruby-amqp/bunny/blob/master/lib/bunny/channel.rb#L1651
IMHO, since this gem focuses on simplicity, it should enable this option by default.

This is not a flag for consumer recovery after a network failure. Consumers are recovered right after queues and bindings without any flags. This flag means that Bunny will attempt to recover a consumer that was cancelled by the server (e.g. because the queue was deleted). There's a similar flag for recovering connections closed via management UI. Both are opinionated decisions and disabled by default. They can easily lead to zombie apps/consumers that cannot be disconnected/cancelled via management UI because they will immediately recover.

Good point! My mistake with the interpretation of the meaning of this flag. However, as you may know, there is another use case, HA failover, when the queue was existing on the node, which failed. In that case consumers connected to other nodes would also receive the cancel notification. How would you approach this when using sneakers?

RabbitMQ 3.4.0+ should re-add your consumer automatically. I'm not against Sneakers having a way to configure this option but the way you described it was incorrect.

If I understand correctly, sevos was discussing the following case:
in a clustered setup, the node on which the queue is located fails, but the client listens on a different node.
According to the docs, a cancel notification is sent to the client in this case. It would be convenient if there would be a way to configure sneakers such that it handles this message and automatically reconnects.
Does that make sense? We're planning to run on a clustered setup and that would be useful to have.

@anpr: I was referring to the same scenario. But starting with 3.4.0 (IIRC), the consumer will be re-added for you automatically (as long as your client is connected to a mirror that didn't fail). There is no need for it to reconnect.
Having a way to register consumer cancellation callbacks is OK, it's just not as crucial as it may sound with recent server versions.

Oh dang!  I think this is what I've been struggling with for weeks!  It sounds like it the consume re-connects to a mirror node, it's fine, but if it connects to a non-mirror node, it might be cancelled?  I would like for the consumer in my case to keep trying to re-connect until it reaches a node that doesn't cancel it.  Sounds like maybe I do need to use the recover_cancelled_consumers flag for this case?  I'l look into it, but since it's been 4+ years, if anybody has any more up-to-date pointers on this, I'd be grateful for them!


Add JAX array to registry

@janosg looks good. Maybe the placeholder value was always a bad idea since it is hard to come up with a value that will work for all objects.


More SGMCMC methods

In particular we could add the SGNHT algorithm (paper, code).
And perhaps also SGHMC and SGHNT algorithms that use the BAOAB integrator rather than Euler-Maruyama, comprehensive info in Leimkuhler and Matthews textbook (p271 and p350)
In all cases we should be carefully implement with a temperature parameter that accepts the value 0 and to only evaluate the gradient once per iteration.

SGNHT added in #89


Update visual-studio-team-services.md

Removed broken link per #68

Docs Build status updates of commit 09e1e8e:
:warning: Validation status: warnings

File
Status
Preview URL
Details

cordovadocs/docfx.json
:warning:Warning

Details

cordovadocs/2017/build-deploy/visual-studio-team-services.md
:white_check_mark:Succeeded

cordovadocs/docfx.json

Line 55: [Warning] Invalid value for 'ms.technology': 'cordova' is not valid with 'ms.prod' value 'visual-studio-dev15'

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


when add many projects to the atom, then ctrl + p gives the file fetch from all the project loaded

Suggestion
Scenerio : when add many projects to the atom,
when ctrl + p gives the file fetch from all the project loaded,
is it possible to implement a functionality like active project after that ctrl +p should fetch file from activated project.
Prerequisites

[x] Can you reproduce the problem in safe mode?
[x] Are you running the latest version of Atom?
[x] Did you check the debugging guide?
[ ] Did you check the FAQs on Discuss?
[x] Are you reporting to the correct repository?
[ ] Did you perform a cursory search to see if your bug or enhancement is already reported?

For more information on how to write a good bug report or enhancement request, see the CONTRIBUTING guide.
Description
[Description of the bug or feature]
Steps to Reproduce

[First Step]
[Second Step]
[and so on...]

Expected behavior: [What you expected to happen]
Actual behavior: [What actually happened]
Versions
You can get this information from executing atom --version and apm --version at the command line.

I would like this as well!
Is there someone who knows anything about?


Null checks and type annotations

Context
Currently we are doing a lot of null-checks where we are not sure if they are really needed or not.
We should use the ? operator to specify if a nullcheck might be necessary (see docs)

The ? type constructor was introduced in C# 8 (2019), and DTXMania was written in older C# standards, so this is a language-style–under-updated issue.


Restore completed build cleanups for TEST and PROD

Moving to workflow calls has required dropping completed artifact cleanup.  Find a new place for the code below.
          # Remove completed build runs, build pods and deployment pods
          for p in $(oc get po | grep "Completed" | awk '{print $1}')
          do
            oc delete po ${p}
          done

Added to deployer action.
https://github.com/bcgov-nr/action-deployer-openshift/pull/59


[Bug]: Camera images appear with incorrect aspect ratio/do not fill card

What happened?
When using a camera_image referencing the snapshots taken by my Ring cameras, the image only partially fill the card, thus:

Expected: card-filling image.
(I see this has also been noted by @jlaska, here: https://github.com/junalmeida/homeassistant-minimalistic-area-card/issues/6#issuecomment-1364540323)
Card Version
1.0.6
HomeAssistant Version
2022.12.8
Relevant javascript log output
No relevant log output was seen.

Thanks for reporting, I also have noticed this.

A release will appear shortly in HACS

Works great now, thanks.


chore: Debugging CI error

Description
This is a temporary PR to debug CI Test failure
Checklist:

[x] My code follows the style guidelines of this project
[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
[ ] My changes generate no new warnings
[ ] 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

/ok-to-test sha=d445667

Closing this as the fix was done via https://github.com/appsmithorg/appsmith/pull/15450


Resizing and floating not working on Scratchpad

When on the Scratchpad window, resizing mode and floating window wouldn't work, unless the window moved to the Scratchpad was already floating.
Steps to reproduce

Open a window
Push it to the scratchpad
Make it floating and try to move or resize it with mouse, or enter the resize mode and try to diminish it

Expected outcome

Noted outcome

dupe of #827

@vaxerski uh I'm sorry, when searching for existing issues I used the word "Scratchpad" instead of "special" workspace


Version resource folders should separate Integer and Decimal components

At the moment, folders for specific versions are named, eg. 101, 102 and 201.
By doing this, it is ambiguous where in the folder name the integer part ends and the decimal part begins. This will become even more of a problem should SemVer be used.
As such, there should be a separator between the components of the Version Number. I would propose that a hyphen (-) should be used since it is a clear separator and has no special meaning in either regular expressions (outside of character classes, which is a non-issue) or in filepaths on any sane filesystem.
This would cause the above folder names to become: 1-01, 1-02 and 2-01.

In 0.3.0.


Drop support for define mutation tests

The GraphQL ruby gem dropped support for define mutations between version v1.9.19 and v1.10.0. This bumps the required version to the latest and removes the legacy test.
Note: initial proposed in https://github.com/Shopify/graphql-batch/pull/120
Per discussion - blocked until release is live with fix?

It's not just in tests, we have backwards compat code as well: https://github.com/Shopify/graphql-batch/blob/fe002252ce61822af91f47ceb5851f0d61a337f2/lib/graphql/batch.rb#L26-L32
I think we still want to wait a bit even with a new version. Because any other new features/fixes in the future wouldn't apply to anyone who needs 1.9 support (unless we backported them to other versions which be annoying).
So I'm good with doing this... but only after some time passes. Like 6 months for example.

@swalkinshaw I wanted to followup on this and see if you think enough time has passed for users of graphql-batch to have upgraded? I've adjusted this PR (noticed the CI swapped to GH, and didn't seem to run). I'd be happy to make any changes needed, or close if your thoughts on timing have changed.

Thanks for the followup! I think we can safely ship this now. graphql-batch is pretty stable and feature complete anyway/
Did CI not run on this PR at all? It might need to be re-created 🤔

@swalkinshaw hmm - tried closing / re-opening https://github.com/Shopify/graphql-batch/pull/136. I'm not familiar with GH actions - but didn't see it appear.


feat: emit pod events on drain

If you plan to PR this upstream I'd suggest you add an extra test here https://github.com/newrelic-forks/aws-node-termination-handler/blob/main/test/e2e/spot-interruption-test-events-on


Colour and misc

Change colour
Add interest rate and start date fields
Change a keyboard shortcut

Pull Request Test Coverage Report for Build 418

17 of 17 (100.0%) changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.04%) to 84.0%

Totals

Change from base Build 416:
0.04%

Covered Lines:
2268

Relevant Lines:
2700

💛  - Coveralls


Sourcing data error

Description
I am getting the error below sporadically. I get this error in ~70% of the builds. The remaining ~30% of the time the build is successful.
Steps to reproduce

Run gatsby build

Additional info

Craft version: 3.7.17
PHP version: 7.3
Database driver & version: NA
Plugins & versions:
Craft composer.json  "born05/craft-enforcepassword": "<IP_ADDRESS>",
  "born05/craft-twofactorauthentication": "2.9.0",
  "craftcms/aws-s3": "1.2.15",
  "craftcms/cms": "3.7.17",
  "craftcms/feed-me": "4.4.0",
  "craftcms/gatsby-helper": "1.0.6",
  "craftcms/mailgun": "1.4.3",
  "craftcms/redactor": "2.8.8",
  "diginov/craft-sentry-logger": "^1.1",
  "nystudio107/craft-retour": "3.1.61",
  "nystudio107/craft-seomatic": "3.4.7",
  "sebastianlenz/linkfield": "2.0.0-rc.1",
  "spicyweb/craft-neo": "2.11.14",
  "verbb/field-manager": "2.2.4",
  "verbb/navigation": "1.4.21",
  "vlucas/phpdotenv": "^3.4.0"

Gatbsy package.json  "@googlemaps/js-api-loader": "^1.12.2",
  "@tailwindcss/aspect-ratio": "^0.2.1",
  "algoliasearch": "^4.10.5",
  "encodeurl": "^1.0.2",
  "formik": "^2.2.9",
  "gatsby": "^3.11.1",
  "gatsby-plugin-algolia": "^0.22.2",
  "gatsby-plugin-canonical-urls": "^3.14.0",
  "gatsby-plugin-gatsby-cloud": "^2.11.0",
  "gatsby-plugin-google-tagmanager": "^3.14.0",
  "gatsby-plugin-image": "^1.11.0",
  "gatsby-plugin-manifest": "^3.11.0",
  "gatsby-plugin-offline": "^4.11.0",
  "gatsby-plugin-react-helmet": "^4.11.0",
  "gatsby-plugin-robots-txt": "^1.6.10",
  "gatsby-plugin-sharp": "^3.11.0",
  "gatsby-plugin-sitemap": "^4.10.0",
  "gatsby-source-filesystem": "^3.11.0",
  "gatsby-transformer-json": "^3.13.0",
  "gatsby-transformer-sharp": "^3.11.0",
  "mailgun-js": "^0.22.0",
  "prop-types": "^15.7.2",
  "react": "^17.0.1",
  "react-dom": "^17.0.1",
  "react-helmet": "^6.1.0",
  "react-instantsearch-dom": "^6.12.1",
  "react-nl2br": "^1.0.2",
  "react-transition-group": "^4.4.2",
  "use-debounce": "^7.0.0"

Stack Trace
 ERROR #11321  PLUGIN

"gatsby-source-craft" threw an error while running the sourceNodes lifecycle:

Failed to execute query LIST_footer_Node.

  468 |     if (remoteConfigVersion !== localConfigVersion || !localContentUpdateTime) {
  469 |         reporter.info("Cached content is unavailable or outdated, sourcing _all_ nodes.");
> 470 |         await sourceAllNodes(config);
      |         ^
  471 |     }
  472 |     else {
  473 |         reporter.info(`Craft config version has not changed since last sourcing. Checking for content changes since "${localContentUpdateTime}".`);

File: node_modules/gatsby-source-craft/gatsby-node.js:470:9

  Error: Failed to execute query LIST_footer_Node.

  - paginate.ts:60 Object.paginate
    [forhealth001-gatsby]/[gatsby-graphql-source-toolkit]/src/source-nodes/fetch-nodes/paginate.ts:60:13

  - runMicrotasks

  - task_queues.js:95 processTicksAndRejections
    internal/process/task_queues.js:95:5

  - fetch-lists.ts:61 fetchNodeList
    [forhealth001-gatsby]/[gatsby-graphql-source-toolkit]/src/source-nodes/fetch-nodes/fetch-lists.ts:61:20

  - fetch-lists.ts:36 Object.fetchAllNodes
    [forhealth001-gatsby]/[gatsby-graphql-source-toolkit]/src/source-nodes/fetch-nodes/fetch-lists.ts:36:24

  - create-nodes.ts:13 Object.createNodes
    [forhealth001-gatsby]/[gatsby-graphql-source-toolkit]/src/source-nodes/node-actions/create-nodes.ts:13:20

  - async Promise.all

  - source-all-nodes.ts:20 sourceAllNodes
    [forhealth001-gatsby]/[gatsby-graphql-source-toolkit]/src/source-nodes/source-all-nodes.ts:20:3

  - gatsby-node.js:470 Object.exports.sourceNodes
    [forhealth001-gatsby]/[gatsby-source-craft]/gatsby-node.js:470:9

  - api-runner-node.js:434 runAPI
    [forhealth001-gatsby]/[gatsby]/src/utils/api-runner-node.js:434:16

not finished source and transform nodes - 32.244s
not finished fetching pages_default_Entry - 31.443s

@brandonkelly we are still experiencing this issue.
We have upgraded to Craft 3.7.18 and will still often receive the following error during builds:
15:44:11 PM:
Cloning into '/usr/src/app/www'...

15:44:13 PM:
Using node version from .nvmrc: v16.10.0

15:44:13 PM:
Installing node version v16.10.0

15:44:13 PM:
Downloading and installing node v16.10.0...

15:44:16 PM:
Now using node v16.10.0 (npm v7.24.0)

15:44:33 PM:
npm

15:44:33 PM:
 WARN deprecated<EMAIL_ADDRESS>This version has been deprecated and is no longer supported or maintained
npm WARN deprecated<EMAIL_ADDRESS>This version has been deprecated and is no longer supported or maintained

15:44:33 PM:
npm

15:44:33 PM:
WARN

15:44:33 PM:
deprecated

15:44:33 PM:
<EMAIL_ADDRESS>Please see https://github.com/lydell/urix#deprecated

15:44:33 PM:
npm

15:44:33 PM:
 WARN deprecated<EMAIL_ADDRESS>https://github.com/lydell/resolve-url#deprecated

15:44:33 PM:
npm

15:44:33 PM:
 WARN deprecated<EMAIL_ADDRESS>The querystring API is considered Legacy. new code should use the URLSearchParams API instead.

15:44:34 PM:
npm WARN deprecated<EMAIL_ADDRESS>Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.

15:44:34 PM:
npm

15:44:34 PM:
 WARN deprecated<EMAIL_ADDRESS>The querystring API is considered Legacy. new code should use the URLSearchParams API instead.

15:44:34 PM:
npm

15:44:34 PM:
 WARN deprecated<EMAIL_ADDRESS>Moved to 'npm install @sideway/address'

15:44:34 PM:
npm

15:44:34 PM:
 WARN deprecated<EMAIL_ADDRESS>Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.

15:44:34 PM:
npm

15:44:34 PM:
 WARN deprecated<EMAIL_ADDRESS>This version has been deprecated and is no longer supported or maintained

15:44:35 PM:
npm

15:44:35 PM:
 WARN deprecated<EMAIL_ADDRESS>Switch to 'npm install joi'

15:44:35 PM:
npm

15:44:35 PM:
 WARN deprecated<EMAIL_ADDRESS>This SVGO version is no longer supported. Upgrade to v2.x.x.

15:44:37 PM:
npm

15:44:37 PM:
 WARN deprecated<EMAIL_ADDRESS><EMAIL_ADDRESS>is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependencies to the actual version of core-js.

15:44:43 PM:

added 2310 packages in 18s

15:44:43 PM:

251 packages are looking for funding
  run `npm fund` for details

15:44:47 PM:
From https://gitlab.com/batchnz/work/forhealth001-gatsby
 * branch            133-create-link-list-component -> FETCH_HEAD

15:44:47 PM:
HEAD is now at ef16564 feat(link-list): change class on heading and index

15:44:48 PM:
Already on '133-create-link-list-component'

15:44:48 PM:
Your branch is up to date with 'origin/133-create-link-list-component'.

15:44:49 PM:
Node version v16.10.0

15:44:50 PM:
Gatsby version Gatsby CLI version: 3.12.0

15:44:50 PM:
  Note: this is the Gatsby version for the site at: /usr/src/app/www

15:44:50 PM:
Gatsby version: 3.12.0

15:44:50 PM:
BUILDS

15:44:53 PM:
success open and validate gatsby-configs, load plugins - 0.755s

15:44:53 PM:
success onPreInit - 0.033s

15:44:53 PM:
success initialize cache - 0.009s

15:44:53 PM:
success copy gatsby files - 0.052s

15:44:55 PM:
success Compiling Gatsby Functions - 1.904s

15:44:55 PM:
info Clearing previous fragments.

15:44:55 PM:
info Writing default fragments.

15:45:04 PM:
success onPreBootstrap - 11.023s

15:45:04 PM:
info Found 0 additional fragments

15:45:09 PM:
success createSchemaCustomization - 5.182s

15:45:09 PM:
info Checking Craft config version.

15:45:10 PM:
info Cached content is unavailable or outdated, sourcing _all_ nodes.

15:45:12 PM:
success fetching practicesIndex_practicesIndex_Entry - 1.805s

15:45:13 PM:
success fetching contact_contact_Entry - 1.899s

15:45:14 PM:
success fetching sitemap_sitemap_Entry - 3.450s

15:45:14 PM:
success fetching referAGp_referAGp_Entry - 3.511s

15:45:16 PM:
success fetching social_GlobalSet - 4.811s

15:45:16 PM:
success fetching documents_Asset - 4.830s

15:45:16 PM:
success fetching User - 5.170s

15:45:19 PM:
success fetching practicesServices_default_Entry - 8.772s

15:45:20 PM:
success fetching jobsCategories_default_Entry - 9.246s

15:45:20 PM:
success fetching jobsTypes_default_Entry - 9.313s

15:45:21 PM:
success fetching states_default_Entry - 10.402s

15:45:21 PM:
success fetching recruiter_default_Entry - 10.783s

15:45:23 PM:
success fetching jobs_default_Entry - 11.833s

15:45:23 PM:
success fetching practices_default_Entry - 12.723s

15:45:25 PM:
success fetching images_Asset - 13.745s

15:45:40 PM:
success fetching pages_default_Entry - 29.530s

15:45:40 PM:
ERROR "gatsby-source-craft" threw an error while running the sourceNodes lifecycle:

15:45:40 PM:
  468 |     if (remoteConfigVersion !== localConfigVersion || !localContentUpdateTime) {

15:45:40 PM:
Failed to execute query LIST_pages_default_Entry.

15:45:40 PM:
  471 |     }

15:45:40 PM:
      |         ^

15:45:40 PM:
  472 |     else {

15:45:40 PM:
  469 |         reporter.info("Cached content is unavailable or outdated, sourcing _all_ nodes.");

15:45:40 PM:
> 470 |         await sourceAllNodes(config);

15:45:40 PM:
  473 |         reporter.info(`Craft config version has not changed since last sourcing. Checking for content changes since "${localContentUpdateTime}".`);

15:45:40 PM:
  Error: Failed to execute query LIST_pages_default_Entry.

15:45:40 PM:
  - task_queues:96 processTicksAndRejections

15:45:40 PM:
  - paginate.ts:60 Object.paginate

15:45:40 PM:
    node:internal/process/task_queues:96:5

15:45:40 PM:
    [www]/[gatsby-graphql-source-toolkit]/src/source-nodes/fetch-nodes/paginate.    ts:60:13

15:45:40 PM:
    [www]/[gatsby-graphql-source-toolkit]/src/source-nodes/fetch-nodes/fetch-lis    ts.ts:61:20

15:45:40 PM:
  - fetch-lists.ts:61 fetchNodeList

15:45:40 PM:
  - fetch-lists.ts:36 Object.fetchAllNodes

15:45:40 PM:
    [www]/[gatsby-graphql-source-toolkit]/src/source-nodes/fetch-nodes/fetch-lis    ts.ts:36:24

15:45:40 PM:
  - create-nodes.ts:13 Object.createNodes

15:45:40 PM:
  - async Promise.all

15:45:40 PM:
  - source-all-nodes.ts:20 sourceAllNodes

15:45:40 PM:
    [www]/[gatsby-graphql-source-toolkit]/src/source-nodes/node-actions/create-n    odes.ts:13:20

15:45:40 PM:
  - api-runner-node.js:434 runAPI

15:45:40 PM:
  - gatsby-node.js:470 Object.exports.sourceNodes

15:45:40 PM:
    [www]/[gatsby-graphql-source-toolkit]/src/source-nodes/source-all-nodes.ts:2    0:3

15:45:40 PM:
    [www]/[gatsby-source-craft]/gatsby-node.js:470:9

15:45:40 PM:
    [www]/[gatsby]/src/utils/api-runner-node.js:434:16

15:45:40 PM:
not finished fetching footerNav_default_Entry - 29.308s

15:45:40 PM:
not finished fetching headerNav_default_Entry - 29.263s

15:45:40 PM:
not finished source and transform nodes - 30.643s

15:45:40 PM:
not finished fetching home_home_Entry - 29.481s

15:45:41 PM:
ERROR Failed to compile: Error: Exited with code 1

If a query just failed with no more information on build step, it most likely failed no Craft side, so - same question as before -anything in your Craft logs?


Store BLOB_DATA in QRTZ_BLOB_TRIGGERS as json value rather than java serialization

Is there any way to configure quartz to store BLOB_DATA as json/string value as there are serialization issues -
 local class incompatible: stream classdesc serialVersionUID =<PHONE_NUMBER>653121010, local class serialVersionUID = -33983373018933994 [See nested exception: java.io.InvalidClassException: com.example.ExampleClass; local class incompatible: stream classdesc serialVersionUID =<PHONE_NUMBER>653121010, local class serialVersionUID = -33983373018933994]
The only work around right now is manually deleting the triggers using the API.
I am able to store JOB_DATA as String using the property org.quartz.jobStore.useProperties=true. I am looking to see if BLOB_DATA can be stored as a String similarly. Haven't found too much from the documentation.

I have been thinking this feature myself as well. It would be very nice to have. Storing blob is really a hassle and not easy to maintain/upgrade. However this would mean break old Quartz API and DB schema completely though. Let's add as part of Quartz3 feature.


Add content to AgentLookingForGroup

Most of the Detailed struct fits the packet PartyFinderListing, so i sticked with names used in that packet

0x3104 offset is Recruitment Criteria(lookingforgroupcondition addon) tab, this part 0-1-2 respectively


[fix][license] Update the log4j version in the presto license file

Motivation
We update the log4j version in PR,
but we haven't update the license file for the version.
Modifications
update the log4j version in license file to the correct version
Verifying this change

[ ] Make sure that the change passes the CI checks.

(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end deployment with large payloads (10MB)
Extended integration test for recovery after broker failure

Does this pull request potentially affect one of the following parts:
If yes was chosen, please highlight the changes

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API: (yes / no)
The schema: (yes / no / don't know)
The default values of configurations: (yes / no)
The wire protocol: (yes / no)
The rest endpoints: (yes / no)
The admin cli options: (yes / no)
Anything that affects deployment: (yes / no / don't know)

Documentation
Check the box below or label this PR directly.
Need to update docs?

[ ] doc-required
(Your PR needs to update docs and you will update later)

[x] doc-not-needed
(Please explain why)

[ ] doc
(Your PR contains doc changes)

[ ] doc-complete
(Docs have been already added)

This refers to https://github.com/apache/pulsar/issues/16783.

@eolivelli as commented above, this refers to https://github.com/apache/pulsar/issues/16783.
I don't find some time to see how to fix it, though XD.

After cherry-pick this to branch-2.10, build with mvn clean install -DskipTests
src/check-binary-license.sh fails with:

So remove label release/2.10.2


Webpack compilation error

When running with Typescript + Cypress 10
Error: Webpack Compilation Error
Module not found: Error: Can't resolve 'path' in '/Users/xxxx/WebstormProjects/canopy-angular/node_modules/cy-verify-downloads/src'

BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

If you want to include a polyfill, you need to:
	- add a fallback 'resolve.fallback: { "path": require.resolve("path-browserify") }'
	- install 'path-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
	resolve.fallback: { "path": false }

Module not found: Error: Can't resolve 'fs' in '/Users/xxxx/WebstormProjects/canopy-angular/node_modules/cy-verify-downloads/src'

Module not found: Error: Can't resolve 'crypto' in '/Users/xxxx/WebstormProjects/canopy-angular/node_modules/cy-verify-downloads/src'

BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

If you want to include a polyfill, you need to:
	- add a fallback 'resolve.fallback: { "crypto": require.resolve("crypto-browserify") }'
	- install 'crypto-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
	resolve.fallback: { "crypto": false }
    at Watching.handle [as handler] (/Users/xxxx/WebstormProjects/canopy-angular/node_modules/@cypress/webpack-preprocessor/dist/index.js:180:23)
    at /Users/xxxx/WebstormProjects/canopy-angular/node_modules/webpack/lib/Watching.js:290:9
    at Hook.eval [as callAsync] (eval at create (/Users/xxxx/WebstormProjects/canopy-angular/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:6:1)
    at Hook.CALL_ASYNC_DELEGATE [as _callAsync] (/Users/xxxx/WebstormProjects/canopy-angular/node_modules/tapable/lib/Hook.js:18:14)
    at Watching._done (/Users/xxxx/WebstormProjects/canopy-angular/node_modules/webpack/lib/Watching.js:287:28)
    at /Users/xxxx/WebstormProjects/canopy-angular/node_modules/webpack/lib/Watching.js:209:21
    at Compiler.emitRecords (/Users/xxxx/WebstormProjects/canopy-angular/node_modules/webpack/lib/Compiler.js:919:5)
    at /Users/xxxx/WebstormProjects/canopy-angular/node_modules/webpack/lib/Watching.js:187:22
    at /Users/xxxx/WebstormProjects/canopy-angular/node_modules/webpack/lib/Compiler.js:885:14
    at Hook.eval [as callAsync] (eval at create (/Users/xxxx/WebstormProjects/canopy-angular/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:6:1)
    at Hook.CALL_ASYNC_DELEGATE [as _callAsync] (/Users/xxxx/WebstormProjects/canopy-angular/node_modules/tapable/lib/Hook.js:18:14)
    at /Users/xxxx/WebstormProjects/canopy-angular/node_modules/webpack/lib/Compiler.js:882:27
    at /Users/xxxx/WebstormProjects/canopy-angular/node_modules/neo-async/async.js:2818:7
    at done (/Users/xxxx/WebstormProjects/canopy-angular/node_modules/neo-async/async.js:3522:9)
    at Hook.eval [as callAsync] (eval at create (/Users/xxxx/WebstormProjects/canopy-angular/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:6:1)
    at Hook.CALL_ASYNC_DELEGATE [as _callAsync] (/Users/xxxx/WebstormProjects/canopy-angular/node_modules/tapable/lib/Hook.js:18:14)
    at /Users/xxxx/WebstormProjects/canopy-angular/node_modules/webpack/lib/Compiler.js:736:33
    at /Users/xxxx/WebstormProjects/canopy-angular/node_modules/graceful-fs/graceful-fs.js:143:16
    at /Users/xxxx/Library/Caches/Cypress/10.3.1/Cypress.app/Contents/Resources/app/packages/server/node_modules/graceful-fs/graceful-fs.js:143:16
    at /Users/xxxx/Library/Caches/Cypress/10.3.1/Cypress.app/Contents/Resources/app/packages/server/node_modules/graceful-fs/graceful-fs.js:143:16
    at /Users/xxxx/Library/Caches/Cypress/10.3.1/Cypress.app/Contents/Resources/app/packages/server/node_modules/graceful-fs/graceful-fs.js:61:14

Hey,
This issue is not related to the package at all. Please, set up your compiler and config correctly. Also, don't forget to add all node.js polyfills. As an example:
https://github.com/elaichenkov/cy-verify-downloads/issues/51#issuecomment-1237978973
If it doesn't help you, then feel free to create a repository with the reproducible code. I'll take a look at it.

Fixed by adding to my webpackconfig:
        plugins: [new NodePolyfillPlugin()],
        resolve: {
          extensions: ['.ts', '.js'],
          fallback: {
            fs: require.resolve('browserify-fs'),
          }```


sslpsk2 -> sslpsk3

just renaming files and request changes for the change of package name from sslpsk2 to sslpsk3.
This is necessary so it will be a unique package in the pipy repo

wrong repo


Re: architecture of ResNet used for track initialization

Hi @cdoersch,
In the TAPIR paper, it is mentioned that the feature maps used for track initialization are computed using a TSM-ResNet, however in the code, particularly in tapir_model.py it seems that the feature extractor is a standard ResNet. Is it possible that the code available for tapir_model.py is an older version or is this indeed the intended implementation? Could you kindly confirm the same?
Regards,
Aditya

Thanks for the clarification!


Dependency issue due to pmmp moving protocol folder to subfolder

Since pocketmine\network\protocol\UpdateBlockPacket moved to pocketmine\network\mcpe\protocol\UpdateBlockPacket this plugin gives a unknown circular dependency error on load when compiled to phar (does not do it running from source).  Anyway, changing this line to the correct path seems to have fixed.

Seems to be working with the updated SimpleWarp.  I compiled this one to phar and it runs without the dependency error now


cannot download the pretrained weights

thanks for your great work, but I cannot download weights:
https://cloud.lip6.fr/index.php/s/sEiwuVj7UXWwSjf
https://cloud.lip6.fr/index.php/s/RutL5MG2a0fpv1F
can you give me another address

Sorry some URL has been changed, here is the new links:
Best model - https://nuage.lip6.fr/s/gfAgG9aW4d2RQ8z
Pretrained ResNet - https://nuage.lip6.fr/s/nCfa836Zcqyb2k9

Sorry some URL has been changed, here is the new links:
Best model - https://nuage.lip6.fr/s/gfAgG9aW4d2RQ8z
Pretrained ResNet - https://nuage.lip6.fr/s/nCfa836Zcqyb2k9

thx for quick reply,
by the way, what is your hyper parameters for training classifer model?

Sorry, I don't remember the hyper parameters I used, but I think it was pretty standard. Since it was only for pretraining I didn't do strong hyper parameters search.


Bump tackle-commons-rest version

Agreed that successfully build this was enough to merge (considering tackle-commons-rest:0.0.1 has NO changes compared to latest tackle-commons-rest:main-SNAPSHOT version)


Fix Python float being casted to C++ float instead of double

Fixes https://github.com/facebookresearch/moolib/issues/45

Might be related to this syntax error in one file?
https://github.com/facebookresearch/moolib/actions/runs/3004550242


Prevent mongoDB updateUser from adding id twice

Reasoning 💡
MongoDB Adapter
I noticed that when using the updateUser function, the id is basically copied and stored as an additional property. This seems unnecessary. This PR fixes this issue for the MongoDB adapter, I haven't checked if the same pattern exists within other adapters. In any case, it is not a big issue, but may save some bytes.

Checklist 🧢
- [ ] Documentation
- [ ] Tests

[x] Ready to be merged

Affected issues 🎟
Now that I did final check I actually found https://github.com/nextauthjs/next-auth/issues/4030. So not sure this is still relevant 🤦♂ - feels free to close.

Hi, thank you for the PR, but this repository is not being maintained anymore.
New PRs should be opened against the main repo as stated in the README file.
Here is the adapter source https://github.com/nextauthjs/next-auth/tree/main/packages/adapter-mongodb
Could you reopen it there? :pray:

Sure. True, I somewhat ended up the PR on wrong repo. Here you go https://github.com/nextauthjs/next-auth/pull/4066 :)


README file is incomplete.

please complete the file

Thank you for sharing this enhancement request. Will be fixed ASAP.

Nice work Joshua! Looks complete to me.


Fix commons-lang version

Description
Bump commons lang to 3.13
Issues Resolved
https://github.com/opensearch-project/security/issues/3300
Check List

[ ] New functionality includes testing
[ ] New functionality has been documented
[ ] Commits are signed per the DCO using --signoff

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

@willyborankin Why did close this out? Seems like we need it to ship 2.x

I'm just seeing this now. I think it would be better to reference the version from core's version.properties: https://github.com/opensearch-project/security/pull/3306


Need an indication that the shell is connecting when launching kubectl shell

Need a UI indicator while waiting for the shell to open when launching kubectl

On 2.5-head latest -
Launch Shell from dashboard.
It says Connecting.. and Connected


Open not live requirements

For this story on Pivotal.
Briefs should be described as being 'open' and not 'live'.
This PR is just a simple change of content and version bump.

:+1:


Questions about paper and code

Hi, thank you for your great work! I have several questions about the paper and code.

For the L2 distance, you discard one term here, why you do that?
I don't know how you only calculate the affinity matrix once for a frame with multiple instances? I think memory is instance-specific and for each instance, we have one memory, so the affinity should be calculated for each instance. I think it is the same with your test code.
I am new to this area, how can I get the quantity results? I seems that you only save the images.

Look forward to your reply.

Thank you for your reply and your contribution to the community~~

The paper (appendix section A) has been updated to reflect point (1).


sdl2 native unsupport arm64

please add native assemblies in runtimes

https://github.com/shshshdy/sdl-sharp/tree/main/SDL2.30.2-runtime

pull reqeust
#536


net/http: Client following redirects won't preserve Host header

Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (go version)?
go version go1.9.1 darwin/amd64

Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/timonwong/go"
GORACE=""
GOROOT="/usr/local/Cellar/go/1.9.1/libexec"
GOTOOLDIR="/usr/local/Cellar/go/1.9.1/libexec/pkg/tool/darwin_amd64"
GCCGO="gccgo"
CC="clang"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/kf/f_mg9bgj05v7dwjr_gm95g_w0000gn/T/go-build556164700=/tmp/go-build -gno-record-gcc-switches -fno-common"
CXX="clang++"
CGO_ENABLED="1"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"

What did you do?
It seems that #8027 was not resolved in #4800. In #4800, custom headers are copied, however, Host field in http.Request is not preserved even if the Location header is just a relative path, see following Go playground link for example:
https://play.golang.org/p/CG45o1eBz8
What did you expect to see?
>> SUCCESS
>> SUCCESS

What did you see instead?
>> ERROR: Got unexpected response code: 403
>> SUCCESS

CC @tombergan

Definitely a bug. Thanks for the repro.

Implementation notes:
As mentioned in Brad's comment here, the HTTP RFCs do not specify exactly which headers should be copied. The HTML Fetch Spec does specify which headers are carried through the fetch, but Fetch does not allow setting a custom Host header, so this issue cannot apply. This also implies that we cannot look to browsers for guidance because they cannot run into this issue.
One approach is to copy the original Host header through all redirect requests. This is apparently what Python does, however, there are good arguments that Python's behavior is wrong. What @timonwong proposes is what curl does: copy the Host header only if the location is relative. This seems reasonable to me.
It's also worth mentioning that setting req.Host different from req.URL.Host is a niche use case that should basically never be done unless the caller really knows what they are doing.


Question: exclude .ctor from coverage

Hey, I was wondering if there is a way to exclude .ctor from coverage?
I'm using Visual Studio 2017 if it makes any difference.
I have tried to read the documentation, but couldn't find out how to do it. I really appreciate this tool =) It's great and even becomes better the more i learn about it. Thanks!

I dont think it's a good idea to exclude ctor from coverage. we can test if some of dependencies are null or someting else if we are using a constructor dependency injection.
I hope you see what i'm explaining :)
Best regards.

Since AxoCover uses OpenCover and OpenCover respects the ExcludeFromCodeCoverageAttribute  you can mark your .ctor with ExcludeFromCode but I do not recommend it (otherwise you would not know which of your .ctors is covered and which is not.
    public class MyClass
    {
        private Logger logger;

        [ExcludeFromCodeCoverage]
        public MyClass()
        {
            this.logger = new Logger();
        }

        [ExcludeFromCodeCoverage]
        public MyClass(ILogger logger)
        {
            this.logger = logger;
        }
    }

You can change this behaviour in the settings


Cosmos partial update

I saw in documentation that connector now support partial update using ItemPatch but I haven't found any code about the implementation.
It will be really useful if you can provide me any sample code.
Thanks

@sachindedhia - which connector are you talking about?

This PR - https://github.com/Azure/azure-sdk-for-java/pull/27435 - has a link to the desing document and also is adding some tests that can be used as a sample
Design document: https://github.com/Azure/azure-sdk-for-java/files/9014885/Patch_On_Spark_Connector.pdf
Test: https://github.com/Azure/azure-sdk-for-java/pull/27435/files#diff-dc18c45cd0ea6e57b54d07908eba2df1346170ceda41bfa10aa263dee7d2ebbe

@FabianMeiswinkel , Thanks for the documentation, but my scenario is slightly different and not sure how to handle this using patch.
I've existing document in cosmos refer - KS1 example below : the document has already KS1 array in cosmos and I want to add another array for KS2 so the document would like - see KS1 & KS2 example below. so I've created dataframe as - see example df- also see my code for spark below - not sure how do I append to the array, any pointer will be really appreciated.
KS1 example:
{
"PupilMatchingRef": "XXXB",
"UPN": "Y887220217054",
"Surname": "XXX",
"Forename": "XXX",
"Gender": "F",
"DOB": "XXXX-09-25T00:00:00.000Z",
"CreatedAt": "0",
"LastModifiedAt": "0",
"KS1": [
{
"ACADYR": "2025/2026",
"DISC_MAT": "0",
"DISC_PSENG": "0",
"DISC_PSLISTEN": "0",
"DISC_PSMATHS": "0",
"DISC_PSNUM": "0",
"DISC_PSREAD": "0",
"DISC_PSSCIENCE": "0",
"DISC_PSSHAPE": "0",
}
],
"id": "59A3047E395CF2273B",
"_rid": "aQQ4ANvlYXImNgAAAAAACg==",
"_self": "dbs/aQQ4AA==/colls/aQQ4ANvlYXI=/docs/aQQ4ANvlYXImNgAAAAAACg==/",
"_etag": ""3800c4fc-0000-0d00-0000-62c201240000"",
"_attachments": "attachments/",
"_ts":<PHONE_NUMBER>
}
KS1 & KS2 example:
{
"PupilMatchingRef": "XXXB",
"UPN": "Y887220217054",
"Surname": "XXX",
"Forename": "XXX",
"Gender": "F",
"DOB": "XXXX-09-25T00:00:00.000Z",
"CreatedAt": "0",
"LastModifiedAt": "0",
"KS1": [
{
"ACADYR": "2025/2026",
"DISC_MAT": "0",
"DISC_PSENG": "0",
"DISC_PSLISTEN": "0",
"DISC_PSMATHS": "0",
"DISC_PSNUM": "0",
"DISC_PSREAD": "0",
"DISC_PSSCIENCE": "0",
"DISC_PSSHAPE": "0",
}
],
"KS2": [
{
"ACADYR": "2025/2026",
"DISC_MAT": "0",
"DISC_PSENG": "0",
"DISC_PSLISTEN": "0",
"DISC_PSMATHS": "0",
"DISC_PSNUM": "0",
"DISC_PSREAD": "0",
"DISC_PSSCIENCE": "0",
"DISC_PSSHAPE": "0",
}
],
"id": "59A3047E395CF2273B",
"_rid": "aQQ4ANvlYXImNgAAAAAACg==",
"_self": "dbs/aQQ4AA==/colls/aQQ4ANvlYXI=/docs/aQQ4ANvlYXImNgAAAAAACg==/",
"_etag": ""3800c4fc-0000-0d00-0000-62c201240000"",
"_attachments": "attachments/",
"_ts":<PHONE_NUMBER>
}
df -

spark code
writeConfigCosmos = {
"spark.cosmos.accountEndpoint" : self._config['EndPoint'],
"spark.cosmos.accountKey" : self._config['MasterKey'],
"spark.cosmos.database" : self._config['Database'],
"spark.cosmos.container" : collection, #e.g. "reference",
"spark.cosmos.write.strategy": "ItemPatch",
"spark.cosmos.write.patch.defaultOperationType": "Add",
"spark.cosmos.serialization.inclusionMode" : "NonNull",
    "spark.cosmos.write.bulk.enabled": "true",
    "mode" : write_config.get('mode', 'append')
}