init wechaty_puppet structure

update first runnable python-wechaty-puppet version.
But, there are many TODO list we need to fix later.

Great to see we are starting building the wechaty-puppet in Python!
Please make this PR pass the CI, and we will be able to merge it after the CI turns green.
Thank you very much!

@huangaszaq please help me to review codes.

Thank you so much for de-couple our Python Wechaty code by splitting them into different repo/modules!
The code looks good to me and I have left some comments, please feel free to merge it when you feel its ready, and let's continue to improve it by iterating via PRs!

LGTM


No version for Mac OS X 32?

Description of the problem or steps to reproduce
CPU error when attempting to run on original white polycarbonate MacBook with Intel Core-Duo “Yonah” CPU which is 32-bit only.
Specifications
Micro version 2.0.0

Commit hash: cfcb2e45
OS: Mac OS X 10.6.9 “Snow Leopard”
Terminal: Mac OS X Terminal

The most recent version of Go no longer supports the target darwin/386, but it's still possible to use older versions to build for that target. I have uploaded a micro-2.0.8-osx32.tar.gz file to the 2.0.8 releases page which you should be able to use. It is unlikely that this target will be added to the autobuilder though because it requires using an old version of Go to compile.

But you still support Linux32.

Loren

Sent from my iPhone

On Dec 14, 2020, at 11:25 AM, Zachary Yedidia<EMAIL_ADDRESS>wrote:

The most recent version of Go no longer supports the target darwin/386, but it's still possible to use older versions to build for that target. I have uploaded a micro-2.0.8-osx32.tar.gz file to the 2.0.8 releases page which you should be able to use. It is unlikely that this target will be added to the autobuilder though because it requires using an old version of Go to compile.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Yes the reason for supporting Linux32 is that Go supports Linux32. The Go compiler no longer supports OSX32 (and neither does Apple), which is why I haven't included osx32 binaries in the past. Anyway you should be able to get a working binary for osx32 now, since I have compiled and uploaded a special version.

Thank you!

Loren

On Dec 14, 2020, at 7:22 PM, Zachary Yedidia<EMAIL_ADDRESS>wrote:
Yes the reason for supporting Linux32 is that Go supports Linux32. The Go compiler no longer supports OSX32 (and neither does Apple), which is why I haven't included osx32 binaries in the past. Anyway you should be able to get a working binary for osx32 now, since I have compiled and uploaded a special version.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/zyedidia/micro/issues/1944#issuecomment-744874491, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADHCYIAZLH2JIORZ5OC52DLSU2T45ANCNFSM4U2RDULQ.


Bot API Server is sending wrong message_thread_id

When a user replies to the Bot's message on the "GENERAL" topic of any forum the Bot API attaches a totally random message_thread_id with the incoming Message update to the bot.
Hence using this message_thread_id in sendMessage or any other method to send messages will fail throwing the following error:
{
  "ok": false,
  "error_code": 400,
  "description": "Bad Request: message thread not found"
}

The behavior is correct. See https://github.com/tdlib/telegram-bot-api/issues/356#issuecomment-1405378400.

Thanks for the reply. Now I understand this is the intended behavior.
But when the received message_thread_id is utilized in a method such as sendMessage, the bot generates an error. Shouldn't it, instead, send the message to the General Topic rather than throwing an error?

You don't need to specify message_thread_id, if you want to reply a message that doesn't belong to a topic. Actually, you never need to specify message_thread_id explicitly when replying to a message without allow_sending_without_reply.

Thanks @levlam, yeah I'm aware of that.
The actual reason why I had to open up this issue was an issue with my Telegram Bot API wrapper library. Whenever the incoming message is from a Topic the message_thread_id will be set automatically on the reply method (a context-aware alias for sendMessage). And you already know the rest of the story. When the user responds to a bot message in General Topic, there's a valid message identifier present as message_thread_id but when used with sendMessage the API call fails.
I think if the chat is a forum, and message_thread_id is present the API could just send the message to the General Topic in this case (if message_thread_id is a root id of a message in the General Topic). Just my thoughts.
Thanks for your responses again :)

I understand how this works, thanks again.
I'm closing this issue as this is not a bug or problem with the Bot API.


Rename buy_preimage_internal and buy_preimage_external

Rename buy_preimage_internal to buy_preimage_from_federation
Rename buy_preimage_external to buy_preimage_over_lightning

We need to rename these because they're confusing names. Can you think of any better ones?

Strong :+1: . Since internal/external are relative and have opposite meaning between gateway and federation/client these were confusing.

rebased


Error in com.github.keeleysam.recipes.Opera.munki?

The following errors occurred:
A Python exception occurred during the execution of autopkg, see the console log for more details.
[ERROR] IOError: [Errno 2] No such file or directory: u'/AutoPkg/Cache/com.github.keeleysam.recipes.Opera.munki/Opera.dmg'
feels like a typo - the file exists. I don't see anything obvious in the recipe. Started around  2:00pm (EST) on Feb 12. Asked on the group list and at least one other person is seeing the same behavior. BTW, my AutoPkg is off of / instead of the default ~

works, Thanks!
On Fri, Feb 13, 2015 at 11:07 AM, Samuel Keeley<EMAIL_ADDRESS>wrote:

Closed #20 https://github.com/autopkg/keeleysam-recipes/issues/20 via
f62cd1b
https://github.com/autopkg/keeleysam-recipes/commit/f62cd1bec0390086e21e665a87e3777ae84bdca8
.
—
Reply to this email directly or view it on GitHub
https://github.com/autopkg/keeleysam-recipes/issues/20#event-235475162.


[Enhancement]: Changing the title and icon of the web app

I can do this. Please assign me this issue under Gssoc'24.

@Sumkaur02 I"ll assign this issue to you .
Also change the icon to logo.svg.
Kindly read the README.md and CONTRIBUTING.md file before the contribution.
I'll add the GSSOC label later you can start working on it.

@Sumkaur02  are you working on it?

@Sumkaur02 are you working on it?

Yes I have started working on it.

@BhavaniSaranga12
kindly make this change today only.
Before contributing fork the repo properly (read contribution.md file).
If not followed properly it will not be accepted.
if you need any assistance tag me here

@itsmohit097 I just want to know which one of these you will prefer

@itsmohit097 I just want to know which one of these you will prefer

Pick white one


libcamera URL broken

Updating or installing the new raspberry-pi-nix version isn't possible, as the libcamera URL seems to be invalid.
The culprit is the following Commit: 0ffba0a5bfb541fc4cb3041a33d956ddd71fc512
After downgrading to Commit 97c85054d16579b5bbc3e31ea346e273990f0f93 Everything works perfectly fine.

Ah, it's the + in the url: https://github.com/nix-community/raspberry-pi-nix/commit/0ffba0a5bfb541fc4cb3041a33d956ddd71fc512#diff-206b9ce276ab5971a2489d75eb1b12999d4bf3843b7988cbe8d687cfde61dea0R36
I think that was fixed in a more recent nix version. So, we should use the SHA instead of the tag for that pin.

The issue has been resolved. Thank you for your help.
As you pointed out, it was the nix version that I was using causing the issue.
I upgraded from 2.18.5 to the latest (2.23.3) and now everything works perfectly fine.
Closing the issue :)


Overlay network support (notably VXLAN)

Issue type
[ X] Feature request
[ ] Bug report
[ ] Documentation
Environment

Python version: 3.6.1
NetBox version: 2.2.8

This has been a dupe several times, but I'll try to make a use case for it as this was missing the last time.
**Request support for overlay networks, especially with VXLAN. **
Use Case:
Overlay networks (e.g. managed by VMware NSX, Cisco ACI, etc.)  are now being deployed more often to decouple virtual machine from the physical network resources, to support multi-tenant and/or multi-security zone environments. With the upcoming of GENEVE as a potential successor to VXLAN the thing is on the road to mainstream (my2c).
Without a proper support for the abstraction layer, systems are in limbo when it comes to documentation We can create a VM, we can assign IP addresses but be cannot assign a (overlay) network to these systems.
The same goes for the network infrastructure managing the overlay/underlay, e.g. we would need to define a gateway as a routing in/out tunnel device but can only create the physical (VLAN) side with netbox.
We tried a custom field but we've hit limits as this isn't shown by default and we lack some support in find/sort etc.
Required fields:

Virtual Network Identifier (VNI) (perhaps additional to VLAN for assignment).
VNI group (as an alternative to VLAN group)

VNI is a neutral expression which holds true for VXLAN or GENEVE deployments.
I would suggest to clone the VLAN field in the first instance but allow for an identifier of 24 bits (integer).
Optional (would be not as important today)

VTEP as a feature of a network device (hypervisor host, switch, router) with an IP, VLAN, control plane and control plane mode (e.g. EVPN, multicast, etc.) as possible options
Control Plane to VNI mapping

Examples:

VM is assigned an interface and an IP. IP/IP subnet is linked to a VNI.

A device can have VLAN interface but also one or more VNI interfaces.

A VNI is local or spans multiple sites

Best case: A hypervisor host has a VTEP A on VLAN B with IP C. Assigned to control plane D which is running in mode E. VNIs F-H are assigned to the control plane D. VMs I and J are running in the VNI, etc.

I am not sure I can contribute anything to Python, libraries etc.
#1725 #1058 #1324

While this would be an amazing feature, attempting to model the myriad approaches to overlay networking on the market today is too big a bite for us to take at this stage of NetBox's development. Sadly, I have to reject this request.


Failing to marshal a package should not result in hard failure during publishing

Failing to marshal a single package currently blocks the publishing of all subsequent packages, this is undesirable.
https://github.com/ossf/package-feeds/blob/ce53f3ea/cmd/scheduled-feed/main.go#L45-L50 is the relevant code chunk.

Seems sensible that this shouldn't lead to a complete loss of the subsequent package data. This might be somewhere to add another event, and simply continue.

Now that #123 has merged I'll look to update publishPackages() to handle errors on a per package basis, using errPub to align with poll()


Transpose result is 'same as' when empty, 1x0 and 1x1

Towards #1800

Current coverage is 97.09% (diff: 100%)

Merging #1828 into master will increase coverage by <.01%

@@             master      #1828   diff @@
==========================================
  Files            87         87
  Lines         11305      11307     +2
  Methods           0          0
  Messages          0          0
  Branches       1875       1875
==========================================
+ Hits          10976      10978     +2
  Misses          207        207
  Partials        122        122

Powered by Codecov. Last update 5a3b144...a6eeb56


TESTED ON Asus rog-flow-x13-2022 , Works grate ,ty

thanks dude , open source is the way to go
i do not care about noise i work with headphones any way so i like my cpu to run cool and smooth

#13


RPC Protocol

We'd like to expose an RPC protocol that wallets can use to perform actions on behalf of the customer. This will require the customerd rearchitecture.
Open questions:

What kind of RPC? JSON-RPC might be easiest to integrate. Do wallets already use JSON-RPC for other things?
Can we reach out to wallet developers directly for feedback?

Our requirements are straightforward - we just need to expose the CLI API as RPC commands - and most RPC protocols ought to support it. I think we should go with JSON-RPC because it has libraries [1] in most languages and is used by bitcoind [2] and Zcash [3], so wallet developers should be able to integrate it easily.
The API should mimic the CLI arguments we presently expose.
[1]:
[2]: https://en.bitcoin.it/wiki/API_reference_(JSON-RPC)
[3]: https://zcash.readthedocs.io/en/latest/rtd_pages/zig.html#zcash-integration-guide

https://github.com/paritytech/jsonrpc looks like it's actively developed and might be a good fit for Zeekoe's use-case.
Questions:

Would adding paritytech/jsonrpc increase compile time?
Would you have to define the interface twice (once for the CLI once for JSON-RPC)? You could use a macro to avoid the duplication, but maybe there's a more elegant way to do it with a trait.

See also: https://github.com/boltlabs-inc/zeekoe/issues/191#issuecomment-953317591


Fix issues pointed out by Clippy

This makes clippy happy again. Unneeded clone and an exhaustive match of
a return value.

@Thomasdezeeuw I'm looking into this UDS test. I don't think it should be flakey, but it's making my PR fail as well. Sorry about that

Should be good after merging master!

I've rebased on master, will merge once CI is green.


multiple readings

for your info: iOS atom app allows to read 4x Atomfast at the same time. BLE signal is just displayed in cps, live view. then you press one and you get the graph...
Any chance to display more than 1 reading?

I'm not ready to answer it right now :)

i saw the youtube video.

can you just explain if you believe your beta version can keep a connection for 20min?
do you see a difference in reaction time between an Android or the watch?
thanks

can you just explain if you believe your beta version can keep a connection for 20min?
What do you mean? The application can be running as long as you want. Or as long as the battery allows.  Ok. I'll try to run it and keep it on for 20-30 minutes.

do you see a difference in reaction time between an Android or the watch?
The Atom Fast device notify about any changes every 2 seconds. So the application updates values when it receives changes.

can you just explain if you believe your beta version can keep a connection for 20min?

What do you mean? The application can be running as long as you want. Or as long as the battery allows.  Ok. I'll try to run it and keep it on for 20-30 minutes.

exactly! for your info, some iOS versions of Atom would loose connection after 5 or 10min, very annoying when it drops like that.

do you see a difference in reaction time between an Android or the watch?

The Atom Fast device notify about any changes every 2 seconds. So the application updates values when it receives changes.
good. as long as it is similar to android app, we're good and BLE update works.

Ok. I've been testing it for an hour. No issues were found. I tried to disconnect it (moved it outside, wait for couple of minutes and brought it back). The device reconnects it by itself. Looks quite stable and tough. But as I can said, the application is soo simple and basic for now :)

2 more questions:
i have up to 6 different Atomfast. how will i be able to select one with a Fenix 6? (mac address...?)
I know that iOS Atom app can crash in the bus or train where there are dozens of bluetooth devices offering handshake. Can you test your device in a place where there are 50 people and see if BTE passive check crashes the app?

2 more questions:
i have up to 6 different Atomfast. how will i be able to select one with a Fenix 6? (mac address...?)
I know that iOS Atom app can crash in the bus or train where there are dozens of bluetooth devices offering handshake. Can you test your device in a place where there are 50 people and see if BTE passive check crashes the app?

You can select a device in "Scan". Unfortunately Garmin doesn't allow to get mac addresses of devices, so there are should be one of them laying close to the Garmin device. The closest atomfast should have the maximum rssi value.

For now I'm far away from any place with buses or trains :)

You can select a device in "Scan". Unfortunately Garmin doesn't allow to get mac addresses of devices, so there are should be one of them laying close to the Garmin device. The closest atomfast should have the maximum rssi value.

For now I'm far away from any place with buses or trains :)

You can select a device in "Scan". Unfortunately Garmin doesn't allow to get mac addresses of devices, so there are should be one of them laying close to the Garmin device. The closest atomfast should have the maximum rssi value.

how do you filter atomfast from other BTE devices? during scanning

For now I'm far away from any place with buses or trains :)

You can select a device in "Scan". Unfortunately Garmin doesn't allow to get mac addresses of devices, so there are should be one of them laying close to the Garmin device. The closest atomfast should have the maximum rssi value.

how do you filter atomfast from other BTE devices? during scanning

For now I'm far away from any place with buses or trains :)

how do you filter atomfast from other BTE devices? during scanning

By checking of supported BLE serives.

how do you filter atomfast from other BTE devices? during scanning

By checking of supported BLE serives.

@mickrose555  Ok. Now I have several answers here.
Yes. It's possible to connect several AtomFasts to a Garmin device.  My application doesn't support it yet, but I'm going to think about this architecture and UX (yeah I'm really bad in UX).
I dont know how many devices can be connected at the same time. The Garmin documentation says nothing about this and the Garmin forum says it depends on the device/SDK version. Unfortunately I have the only AtomFast and can't check it.
Today I went to a supermarket with my atom device and tried to find it there. According to my Android there were about 18-20 devices around. No problems where found with this. I don't think there are problems with this. But anything can happen. It needs to be tested on different Garmins.

@mickrose555  Ok. Now I have several answers here.
Yes. It's possible to connect several AtomFasts to a Garmin device.  My application doesn't support it yet, but I'm going to think about this architecture and UX (yeah I'm really bad in UX).
I dont know how many devices can be connected at the same time. The Garmin documentation says nothing about this and the Garmin forum says it depends on the device/SDK version. Unfortunately I have the only AtomFast and can't check it.
Today I went to a supermarket with my atom device and tried to find it there. According to my Android there were about 18-20 devices around. No problems where found with this. I don't think there are problems with this. But anything can happen. It needs to be tested on different Garmins.

@mickrose555  Ok. Now I have several answers here.
Yes. It's possible to connect several AtomFasts to a Garmin device.  My application doesn't support it yet, but I'm going to think about this architecture and UX (yeah I'm really bad in UX).
I dont know how many devices can be connected at the same time. The Garmin documentation says nothing about this and the Garmin forum says it depends on the device/SDK version. Unfortunately I have the only AtomFast and can't check it.
Today I went to a supermarket with my atom device and tried to find it there. According to my Android there were about 18-20 devices around. No problems where found with this. I don't think there are problems with this. But anything can happen. It needs to be tested on different Garmins.

great!
now remember there are 2 ways, as confirmed on any iOS with Atom freeApp: real pairing (active) and passive reading of multiple atomfast. i am sharing these details just to inform you, not to request this nice-to-have feature. when opening iOS atom app, it scans BLE, filters only atomfast (this is where it can crash in a public place->bug) and reads cps value for each listed/detected atomfast. at this point, no device is selected. nice feature also: each device gets a nickname which is remembered. useful for me because the atomfast left part and right part of the car help me understand where is the anomaly...
(i really like the Fenix 6 sapphire so I will try to get it-> i would never have it if it wasn't for your app!!!)
thanks

@mickrose555  Ok. Now I have several answers here.
Yes. It's possible to connect several AtomFasts to a Garmin device.  My application doesn't support it yet, but I'm going to think about this architecture and UX (yeah I'm really bad in UX).
I dont know how many devices can be connected at the same time. The Garmin documentation says nothing about this and the Garmin forum says it depends on the device/SDK version. Unfortunately I have the only AtomFast and can't check it.
Today I went to a supermarket with my atom device and tried to find it there. According to my Android there were about 18-20 devices around. No problems where found with this. I don't think there are problems with this. But anything can happen. It needs to be tested on different Garmins.

great!
now remember there are 2 ways, as confirmed on any iOS with Atom freeApp: real pairing (active) and passive reading of multiple atomfast. i am sharing these details just to inform you, not to request this nice-to-have feature. when opening iOS atom app, it scans BLE, filters only atomfast (this is where it can crash in a public place->bug) and reads cps value for each listed/detected atomfast. at this point, no device is selected. nice feature also: each device gets a nickname which is remembered. useful for me because the atomfast left part and right part of the car help me understand where is the anomaly...
(i really like the Fenix 6 sapphire so I will try to get it-> i would never have it if it wasn't for your app!!!)
thanks


OCPBUGS-14783: Fix NetworkPolicy to work over IPv4 and IPv6

What this PR does / why we need it:
The implementation added now, validates the ClusterNetwork CIDR used to build the HostedCluster CR. The CIDR added to the NetworkPolicy now matches the ClusterNetwork stack in order to block egress traffic
Which issue(s) this PR fixes:
Fixes #OCPBUGS-14783
Checklist

[x] Subject and description added to both, commit and PR.
[x] Relevant issues have been referenced.
[ ] This change includes docs.
[x] This change includes unit tests.

/jira refresh

/jira refresh

https://github.com/openshift/hypershift/pull/2795#issuecomment-1632009179

Thx!
/approved

/lgtm

/retest-required

/retest-required

/retest-required

/retest-required

Cesar's approve didn't take
/approve


Create a proof-of-concept for Pinia migration

Migration to Pinia

Feel free to respond to this PR/RFC/proposal with

additional migration PRs (or commits)
comments suggesting changes to the approach

Goals

To completely eliminate all uses of Vuex, gradually replacing them with Pinia
To do the upgrade in a gradual way, entering a transition period where Vuex and Pinia coexist

Side-goals

Removal of the verbosity introduced by module and action constants
To create helpers, utils and patterns for testing store usage consistently in unit tests
Abandon the usage of the controversial useStore helper in favour of modular useX from Pinia stores

Steps

Install Pinia and test compatibility (this PR)

Replace Vuex stores with their Pinia counterparts

state -> state

getters -> getters

mutations and actions -> actions
In this stage we must determine if we must use mutations as actions. Pinia allows changing the state directly in the components (which was frowned upon by Vuex) so we could do away with mutations in theory. But having them and following the Vuex principle makes transition smoother and keeps state changes limited to one file instead of scattered around the codebase.

Update tests, tests involving changes to the Vuex store now need to be updated to work with Pinia.

beforeEach
setActivePinia(createPinia())

in the test case
const xyzStore = useXyz()
expect(xyzStore.state).to // ...

Remove unused constants from

~/constants/mutation-types.js
~/constants/action-types.js
~/constants/store-modules.js

-1. In the end, with no Vuex stores remaining, Vuex and all associated dependencies will be removed. The store/index.js file can also be removed after the complete migration to Pinia. The disableVuex: false flag should also be removed.
Conventions
Nomenclature

In the transition, we name stores after their Vuex counterparts.

active.js → activeStore / useActive

State is unchanged, except that it is now an arrow function that returns the dictionary.
Mutations become the camelCasedVersions of their constant names

SET_ACTIVE_MEDIA_ITEM → setActiveMediaItem

Type hinting
In the interest of a quick migration, we can continue to use the existing type definitions for the state and the various mutations/actions from the types.d.ts file. Some definitions in the file may be out of date (as was the case for ActiveMediaState), so a cursory glance to check that would be useful.
Procedure
To minimise disruption, each store will be changed using a lock-based approach where the developer takes a lock on the store using a notification to the group, makes a PR updating a single store and its usages and this lock is released after the PR is merged.
This prevents PRs from diverging too much and allows a seamless transition for all involved.
Fixes

Addresses #756 by @sarayourfriend
Addresses #831 by @obulat
PR description
This PR

sets up Pinia alongside Vuex
updates the smallest store, active, to Pinia
updates associated tests

Checklist

[x] My pull request has a descriptive title (not a vague title like Update index.md).
[x] My pull request targets the default branch of the repository (main) or a parent feature branch.
[x] My commit messages follow best practices.
[x] My code follows the established code style of the repository.
[x] I added or updated tests for the changes I made (if applicable).
[ ] I added or updated documentation (if applicable).
[x] I tried running the project locally and verified that there are no visible errors.

Developer Certificate of Origin

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

Oh yeah, this was just a test to see if things work and if this is the right direction to proceed in, before we start migrating some of the more massive modules

@dhruvkb this looks excellent, great initial proof of concept. I'd love to see this followed up with a Pina RFC next week to outline further next steps in more detail.

-1. In the end, with no Vuex stores remaining, Vuex and all associated dependencies will be removed. The store/index.js file can also be removed after the complete migration to Pinia.

We should also make a note to remove the disableVuex: false flag from the pinia configuration.

@dhruvkb for this project it might be helpful to lay out each of the stores, how they're related, which ones depend on each other and how best to migrate them.
I think there are stores that commit across each other (in particular IIRC search and media do this) and we'd need to convert them in the correct order for it to work (and confirm we can call Pinia store actions from within a Vuex mutation?)

I'd be nice to stick mutations in the Pinia store, if only because it'll make them significantly easier to test without having to rely on triggering them via some component interaction.
I think it would be better to approach this on a case-by-case basis, @sarayourfriend . Some mutations are very simple, created only because there is no way of changing the state from the actions in Vuex. One of them is FETCH_START_MEDIA, which simply does state.fetchState = true. I don't see a point of testing such a mutation.
But there are, of course, larger mutation functions that do need to be kept, and converted into actions.

One of them is FETCH_START_MEDIA, which simply does state.fetchState = true. I don't see a point of testing such a mutation.

Agreed that testing that directly wouldn't make sense but we would want to test that that does happen as part of a fetch media transction. Without being able to spy on the function that causes that state to change, i'm not sure how you'd write that test. If the action was like this:
async fetchMedia() {
  state.isFetching = true
  try {
    await doFetching()
    // ... etc
  } catch (e) {
    state.fetchError = // ...
    return // ...
  } finally {
    state.isFetching = false
  }
}

Without encapsulating the fetch-state mutations there's no (non-convoluted) way to unit test that they're happening. You can't make assertions after calling fetchMedia that isFetching is true because you'll be introducing a data race in the test against doFetching returning (which in the test should be immediate); or you'll be relying on very specific event loop behaviors that probably aren't guaranteed.
Compare to if you use functions for the fetch-state modifications:
async fetchMedia() {
  this.startFetch()
  try {
    await doFetch()
    // ...
  } catch (e) {
    this.failFetch(e)
    return // ...
  } finally {
    this.finishFetch()
  }
}

In the test you could jest.spyOn(store, 'startFetch') and so on to verify that they're called as expected.
In that case you would want to test each of those functions as well to verify that those units work as expected, even if it's a single line :shrug:

@dhruvkb
Did you have any time to look into this?

In your time researching, did you come across any opinions about whether to use the object or function callback syntax for defining a store? I strongly prefer the function callback syntax because I feel like it more closely mirrors the way state is created in setup (in fact, it's exactly the same) and it also makes having private helper functions possible (compared to the object syntax where all the functions on the definition object will be public). It also eliminates this usage which I've generally found to be a good thing for comprehensibility in JavaScript generally.

Can you give an example of two ways of defining a store, @sarayourfriend ? I can only see one in Pinia docs:
export const useStore = defineStore('main', { // other options... })

@obulat just to clairfy, is the goal to merge this branch once the RFC is approved?

@sarayourfriend I would prefer that.

I'd think we should decide to tackle the Pinia milestone before introducing the dependency, and then focus on migrating the whole store as it's not recommended to keep both Vuex and Pinia coexisting at the same time.

I'd think we should decide to tackle the Pinia milestone before introducing the dependency, and then focus on migrating the whole store as it's not recommended to keep both Vuex and Pinia coexisting at the same time.

@krysal can you add that comment to the RFC? There's some discussion in there about what that guidance in the docs actually means: https://github.com/WordPress/openverse/pull/174/files#r813094475
@dhruvkb did some good investigation that clarified the situation for me personally. Curious what you think about it.

My opinion is that big PRs that change a lot of things can

get stuck in reviews
frequently get stale and need to be constantly updated
block work in other PRs that might want to use the new code or change the old one

Since Vuex and Pinia can coexists (which although not-recommended, works quite well) we should not hesitate to use their coexistence to migrate stores in several small PRs that can be merged fairly quickly.

Reconfirming that this looks good! LGTM.


Resolve Issue #2100

https://github.com/akiran/react-slick/issues/2100 add in all files slick-theme

@Ricardo-Bonin Thanks for investigating the issue.
We are not facing the issue on our docs site. So closing this for now.

I suggest you give it an inspection. I inspected the documentation site and found the same problem

.


Handle AddActions requests from the Java AppServer

This allows the datastore to maintain a list of tasks associated with a transaction.

https://ocd.appscale.com:8080/job/Daily Build/2365/


Exception ContentNotFound on GetFriendlyUrl in situation when content was deleted

We have cases when content was deleted in Optimizely, but not reindexed in find and we trying to get the URL of the removed content.
Is it possible to return an empty string for that case? So we won't need to handle the error at our level.
How to reproduce:

remove content and try to call GetFriendlyUrl with content reference of the removed content
exception ContentNotFound raised

@marisks your comments on this issue?

@valdisiljuconoks no comments :)


forgot the .md

Forgot to add the .md, does this file is not doing anything atm. Until the, .md is added this won't work.

Thanks!


DirectLine not responding to client

Github issues should be used for bugs and feature requests. Use Stack Overflow for general "how-to" questions.
Version
Version 3
Direct Line
Describe the bug
Send Hello to bot, activities are not sent back
To Reproduce
Steps to reproduce the behavior:
On a bot with directline interface, if you send a Hi to a bot, you get no response back
Expected behavior
Give a clear and concise description of what you expected to happen.
Bot is not answering to client
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
[bug]
[javascript]

When I try to publish an activity, I'm getting error :
{ url: 'https://directline.botframework.com/v3/directline/conversations/5Ynkct7yQco5lmOIhUmx7A/activities',
method: 'POST',
headers: { error: 'no response from server' },
errObj:
{ Error: read ECONNRESET
at TLSWrap.onread (net.js:659:25)
errno: 'ECONNRESET',
code: 'ECONNRESET',
syscall: 'read',
response: undefined },

I found a error on azure channels log:

04/12/2018 18:38:26
There was an error sending this message to your bot: HTTP status code BadGateway

The Microsoft Bot Framework team prefers that how to questions be submitted on Stack Overflow. The official Bot Framework Github repos are the preferred platform for submitting bug fixes and feature requests.

It was not a how to. I had some bots working for months and they suddenly stopped. Magically, next day they started working again.
Lessons learned, it is too dangerous to rely on one API and uncertain support.

Hi @10p30pl3
I'm sorry you've run into this issue.  I notice that the time you posted this corresponded with the enforcement of TLS 1.2 https://blog.botframework.com/2018/11/06/announcement-azure-bot-service-enforcing-transport-layer-security-tls-1-2/  Could your issue have potentially been related to this?

Hi @EricDahlvang thanks for your response.
I'l take a on TLS1.2 info.
Regarding the datacenter, it seems that the problem occurred on the websocket connection. Is there any action item I was supposed to do ?
Thank you again

@10p30pl3 No, I don't believe there are any action items if you are not experiencing issues anymore.
I've also been told there were some transient issues with some Direct Line bots earlier this week, related to a service deployment.  Your issue may have been due to that.
Please do let us know if you continue to experience problems.


When will radar chart be supported

When will radar chart be supported

I like that,
I will implement it ASAP.
Stay tuned!
Thanks!

Now we have implemented RadarChart (thanks to @payam-zahedi)
check it out.


Added Jarvis Powered voice assistant project

Implemented the Jarvis powered voice assistant in Python Projects

This is a voice assistant with which one can interact with one-on-one and can chat or query any voice based response. It is made from over a dozen python libraries.
Close #3390

Checklist:

[x] I have mentioned the issue number in my Pull Request.
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have created a helpful and easy to understand README.md

@MohitGupta121 @TusharKesarwani @pranjay-poddar please review my PR.

@MohitGupta121 done!

@jaivsh please resolves conflicts

Hi @MohitGupta121 I've resolved the issues. Please check PR


changelog: v75-beta

date: 15-Apr-2020
foreword: These are all the changes since the last changelog (v74-beta).

FF75 Release notes
FF75 for developers
FF75 compatibility
FF75 security advisories

changelog: [all changes]

all user.js updates for Firefox v74 are detailed in the ToDo: diffs FF74-FF75 issue

includes links to the commits made for each pref, links to bugzilla tickets, our discussions etc.

for all the rest see the full list of pref changes below

all pref changes:

new active prefs:

user_pref("browser.privatebrowsing.forceMediaMemoryCache", true); // [FF75+]
user_pref("media.memory_cache_max_size", 16384);

new in 75beta but commented out by default

//user_pref("javascript.options.jit_trustedprincipals", true); // [FF75+] [HIDDEN PREF]

commented out:

//user_pref("dom.event.clipboardevents.enabled", false);

removed from the user.js:

user_pref("browser.search.region", "US"); // [HIDDEN PREF]
user_pref("browser.search.geoip.url", "");
  // ^^ FYI: the .url pref was actually deprecated

Any and all help, suggestions, recommendations, links, tips and tricks, questions, thank you's or what have you are welcome - signup/login and start typing - thanks

Due to security.remote_settings.intermediates.enabled I can now open site (over https) which previously were broken due to security.nocertdb (1222). I wonder if we could enable 1222 by default. AFAIK it is only commented because of many broken pages.
FYI: I increased security.remote_settings.intermediates.downloads_per_poll to get the certs faster.

Tip: don't use "enable" etc ... use pref values (because prefs names and values can be ambiguous) and the words active/inactive to refer to whether we make a pref commented out or not
I'm not making 1222 active: it's too disruptive: passwords aren't available. It was never inactive because it broke pages - first I've heard of that (not that I've tested it or anything)
TB use it, to avoid disk writes at the very least. Not sure about the cache attach anymore since FPI (not sure if FPI is used on certs) and RFP timing mitigations

Don't know where else to put this, but on 1211 option 2 says enabled for EV certificates only. I think it's worth stating that EV certificates are dead/meaningless info.


ChannelValue not taking :host styles

Describe the bug
In channel-value/channel-value.component.scss there is this field
:host {
    display: inline-flex;
    align-items: center;
}

but this style applied neither on storybook nor on showcase.
What is the expected behavior?
Styles should go through so that the component pxb-channel-value can be properly vertically aligned in an info list item. This is also what React Component Library did in ChannelValue's React Counter Part.
What are the steps to reproduce?

Go to showcase
See the list of info list items

Screenshots or links to minimum reproduction example
In showcase,

What is your environment?
Browser

[ ] Internet Explorer
[ ] Edge
[ ] Safari
[x] Chrome
[ ] Firefox

Operating System

[x] MacOS
[ ] Windows
[ ] Other

This happened when we switched to view encapsulation of none. We need to go through the components and see which ones were using :host styles before and do a little refactoring to remove the need for these rules (try to move the styles elsewhere).


Problem moving users with csv

I am trying to move multiple users from one org to another with a csv.  In my spreadsheet I have 2 columns the first is user and the second is org.  I have the latest version and the command I am typing is
gam csv moveuser.csv gam update user ~user org ~org when I hit enter i get the following error:

There are about 1000 users I am trying to move and I've tried cutting that number down even to just 1 in the spreadsheet but doesn't change anything.

I also came across this issue. I downgraded back down to 4.30 in order to run my batch command job. I didn't have nearly as many users to move; only ~40, but I still received that 'line 71' error.

When I was first trying I was using ver 4.30 and it looked like it was working fine but in console I noticed the accounts didn't get moved at all.  That's what prompted me to check for an update.

abusby78,
What's your Windows version?
Ross
On Tue, Sep 26, 2017 at 2:41 PM, abusby78<EMAIL_ADDRESS>wrote:

When I was first trying I was using ver 4.30 and it looked like it was
working fine but in console I noticed the accounts didn't get moved at all.
That's what prompted me to check for an update.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/jay0lee/GAM/issues/601#issuecomment-332344570, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AIU8LwlxpM-tJ4LuiqU9XlAPD_OHBdiQks5smW90gaJpZM4Pk5rf
.

--
Ross Scroggs
<EMAIL_ADDRESS>

This is probably because 4.31 uses new pyinstaller 3.3 and python 2.7.14.
will take a look.
On Sep 26, 2017 7:07 PM, "Ross Scroggs"<EMAIL_ADDRESS>wrote:

abusby78,
What's your Windows version?
Ross
On Tue, Sep 26, 2017 at 2:41 PM, abusby78<EMAIL_ADDRESS>wrote:

When I was first trying I was using ver 4.30 and it looked like it was
working fine but in console I noticed the accounts didn't get moved at
all.
That's what prompted me to check for an update.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/jay0lee/GAM/issues/601#issuecomment-332344570, or
mute
the thread
<https://github.com/notifications/unsubscribe-auth/AIU8LwlxpM-
tJ4LuiqU9XlAPD_OHBdiQks5smW90gaJpZM4Pk5rf>
.

--
Ross Scroggs
<EMAIL_ADDRESS>—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/jay0lee/GAM/issues/601#issuecomment-332361554, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AEaMsL1WmSZY7JVPGWb6-A7ac9s2KdVnks5smYPGgaJpZM4Pk5rf
.

Jay,
I'm not having any problems with PyInstaller 3.2 and Python 2.7.13
Ross
On Tue, Sep 26, 2017 at 4:11 PM, Jay Lee<EMAIL_ADDRESS>wrote:

This is probably because 4.31 uses new pyinstaller 3.3 and python 2.7.14.
will take a look.
On Sep 26, 2017 7:07 PM, "Ross Scroggs"<EMAIL_ADDRESS>wrote:

abusby78,
What's your Windows version?
Ross
On Tue, Sep 26, 2017 at 2:41 PM, abusby78<EMAIL_ADDRESS>wrote:

When I was first trying I was using ver 4.30 and it looked like it was
working fine but in console I noticed the accounts didn't get moved at
all.
That's what prompted me to check for an update.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/jay0lee/GAM/issues/601#issuecomment-332344570, or
mute
the thread
<https://github.com/notifications/unsubscribe-auth/AIU8LwlxpM-
tJ4LuiqU9XlAPD_OHBdiQks5smW90gaJpZM4Pk5rf>
.

--
Ross Scroggs
<EMAIL_ADDRESS>—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/jay0lee/GAM/issues/601#issuecomment-332361554, or
mute
the thread
<https://github.com/notifications/unsubscribe-auth/AEaMsL1WmSZY7JVPGWb6-
A7ac9s2KdVnks5smYPGgaJpZM4Pk5rf>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/jay0lee/GAM/issues/601#issuecomment-332362143, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AIU8L_e_zlubVSn_mkxRAgpNN25QAx_nks5smYSigaJpZM4Pk5rf
.

--
Ross Scroggs
<EMAIL_ADDRESS>

Ross,
I’m using Windows 10 Pro.
Alex

Ross, looks like PyInstaller 3.3 may require us to back out some of the changes from PR #346.
When I commented out those changes csv commands on Windows started working again. Can you test and confirm when you have a moment?

Jay,
Will do.
Ross
On Tue, Sep 26, 2017 at 5:48 PM, Jay Lee<EMAIL_ADDRESS>wrote:

Ross, looks like PyInstaller 3.3 may require us to back out some of the
changes from PR #346 https://github.com/jay0lee/GAM/pull/346.
When I commented out those changes csv commands on Windows started working
again. Can you test and confirm when you have a moment?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/jay0lee/GAM/issues/601#issuecomment-332376406, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AIU8L5hVmyXR7SdGC7awCEyYrsiVJWMTks5smZtqgaJpZM4Pk5rf
.

--
Ross Scroggs
<EMAIL_ADDRESS>

OK, Ross submitted a fix to remove the special code that was causing the issue, I've rebuilt 4.31 on Windows and uploaded, please try downloading 4.31 again and see if that solves. Note that if you downloaded the original 4.31 MSI, Windows may give you grief about it being the same version so an uninstall/reinstall may be necessary.

Wow, I can’t believe how fast this got fixed. You guys are awesome. By the way, I absolutely love GAM, it makes my life a lot easier.
Thanks a lot
Alex
Sent from my iPhone

On Sep 27, 2017, at 5:03 AM, Jay Lee<EMAIL_ADDRESS>wrote:
OK, Ross submitted a fix to remove the special code that was causing the issue, I've rebuilt 4.31 on Windows and uploaded, please try downloading 4.31 again and see if that solves. Note that if you downloaded the original 4.31 MSI, Windows may give you grief about it being the same version so an uninstall/reinstall may be necessary.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Is there a flag isQuickAccessOpened / isCommandPaletteOpend?

Context

[X] This issue is not a bug report. (please use a different template for reporting a bug)
[X] This issue is not a duplicate of an existing issue. (please use the search to find existing issues)

Description
Hello,
I am using monaco in a JavaFX application.
The scrolling behavior with the mouse wheel for scrolling through the commands in the command palette is some how unsmooth  when using the monaco editor in the browser provided by JavaFX-WebEngine.
I would like to manipulate this behavior programmatically by capturing the mouse wheel events. But I would like to do this only if the command palette is opened by the user. How do i know the command palette is opened? Is there a function or flag like isQuickAccessOpened / isCommandPaletteOpend that i can use?
I know the best way would be to fix the WebEngine-Behaviour because in a normal modern browser every thing is fine. But for a quick solution  this would be very helpful option.
Thanks!

I think that the value of mouseWheelScrollSensitivity is not adjusted when the command palette gets open. Therefor there are large jumps of the cursor when using the mouse wheel.

Thank you very much @tamayika . You code worked!
I have still a question. Is it possible to change the mouseWheelScrollSensitivity for the editor.contrib.quickInputWidget? or is there another parameter which i could take for the opened editor.contrib.quickInputWidget?

mouseWheelScrollSensitivity does not effect in quickInput scroll.
Maybe mouseWheelScrollSensitivity is not referenced in quickInput.

mouseWheelScrollSensitivity does not effect in quickInput scroll. Maybe mouseWheelScrollSensitivity is not referenced in quickInput.

i wonder why this is not a problem in a normal browser like firefox or chrome.
Is there a way to change the scroll behavior of quickInput ?
what i am doing now is really a dirty hack. I trigger keyDown or keyUp after capturing the scroll events when the quickInfo is open.

Maybe there is a difference between modern browsers and JavaFX WebEngine in scroll behavior.
You can check monaco(vscode) scroll behavior at below codes.
https://github.com/microsoft/vscode/blob/250a8f36c93721830b0ef2e39dc065d6944d9912/src/vs/base/browser/ui/scrollbar/scrollableElement.ts
https://github.com/microsoft/vscode/blob/250a8f36c93721830b0ef2e39dc065d6944d9912/src/vs/base/common/scrollable.ts#L225

We closed this issue because we don't plan to address it in the foreseeable future. If you disagree and feel that this issue is crucial: we are happy to listen and to reconsider.
If you wonder what we are up to, please see our roadmap and issue reporting guidelines.
Thanks for your understanding, and happy coding!


Update coingate.php (more accurate pricing)

In case of payment with BTC (or AltCoin), do not format to just 2 digits. This will result in 0.00 prices for things that cost €10,- for instance. 0.00 prices result in Api Error.

Thank you for your input. We implemented your improvement


[Request] Page 343 "Check Credit Limit" - Move variables

Move the variables var:

    NewOrderAmountLCY: Decimal
    DeltaAmount: Decimal;

To "protected var" to allow to retrieve them in an extension page.

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


update copyright notice, other minor changes

@catch22 listed you as a maintainer for DESCRIPTION file.  That ok?

Actually, let me rebase that a bit...


Make aoc_case apply uppercase/lowercase name transformations

It's impossible for aoc_case usage to satisfy the linter atm because the same name gets used verbatim in two contexts that generate contradictory warnings.

Fixed.


feat: add git_config query

This adds highlighting to git_config files. From what I can tell the only query needed is the included section_header query, since git_config files have a pretty simple syntax.

Can section headers be nested? I don't really see the point of highlighting delimiters if they are all on the same level regardless. Do you have some specific use-base in mind?
Also, can you please remove the dot from the test file name? If you Neovim to detect the file type reliable prefer a modeline instead, like this: ; vim:ft=gitconfig.

Can section headers be nested? I don't really see the point of highlighting delimiters if they are all on the same level regardless. Do you have some specific use-base in mind?

I don't think headers can be nested. My use case is just that I use rainbow-delimiters for all my delimiter highlighting except unit types (like () in rust, which I like to be gray - my standard parenthesis color).
If you prefer not to include this in rainbow-delimiters, I will just have to do my own highlighting in gitconfig files.

Also, can you please remove the dot from the test file name? If you Neovim to detect the file type reliable prefer a modeline instead, like this: ; vim:ft=gitconfig.

I renamed the file and added modeline instead.

I think this is more suited to your personal config (~/.config/nvim/after/queries/git_config/rainbow-delimiters.scm). It's just one simple pattern, so it's not hard to maintain either. Please file an issue if there are any problems with maintaining your own query in your Neovim configuration.
I am trying to put myself in the shoes of some regular user: he opens a Git config file and then finds that the section headers are highlighted all weirdly for apparently no reason. This would violate the principle of least astonishment. I don't think section headers really qualify as delimiters if there can never be more than one level.
I am open to counter-arguments though.

I think this is more suited to your personal config (~/.config/nvim/after/queries/git_config/rainbow-delimiters.scm). It's just one simple pattern, so it's not hard to maintain either. Please file an issue if there are any problems with maintaining your own query in your Neovim configuration.

I am fine with just maintaining this myself, and if I notice any problems I will file an issue.

I am trying to put myself in the shoes of some regular user: he opens a Git config file and then finds that the section headers are highlighted all weirdly for apparently no reason. This would violate the principle of least astonishment. I don't think section headers really qualify as delimiters if there can never be more than one level.
I am open to counter-arguments though.

As a counter-argument, I would think that a user of this plugin would expect it to be active in all files they open (at least that is basically my expectation). Of course if there is no treesitter parser there is nothing we can do, or if the parser gives us very little to work with like in math in latex, it is also hard to give the "expected" behavior. But overall I think that users would expect highlighting of (), [], {}, <> pairs in almost all files.

I agree in principle, but let's take a step back: what is even the point of rainbow delimiters? It provides alternating highlighting of nested delimiters so users can immediately see the levels of hierarchy and which delimiters belong together. The definition of "delimiter" is somewhat flexible, e.g. we could consider the def foo(): in Python to be a delimiter without a closing counterpart, and it might make sense to have a sort of rainbow-blocks query in Python.
However, without any nesting are we gaining anything over just using regular Tree-sitter highlighting? I don't think so because there is no alternating. The end result looks the same, but now we have all the computational and cognitive overhead of rainbow delimiters; we are checking for nesting levels which will never exist. You could have defined the same pattern in highlight.scm with a capture named @GitConfSectionBracket and then define highlighting like :hi link @GitConfSectionBracket RainbowDelimiterRed or some other group.

I agree in principle, but let's take a step back: what is even the point of rainbow delimiters? It provides alternating highlighting of nested delimiters so users can immediately see the levels of hierarchy and which delimiters belong together.

That is probably the intended point of rainbow delimiters, but I would expect that some users (like me) use rainbow-delimiters to highlight delimiters in general. (Though again, I am fine with you sticking to the intended use. rainbow-delimiters is customizable enough that I can do what I want with it by making custom queries.)

The definition of "delimiter" is somewhat flexible, e.g. we could consider the def foo(): in Python to be a delimiter without a closing counterpart, and it might make sense to have a sort of rainbow-blocks query in Python.

I had thought about creating a rainbow-blocks query for Python myself, but it is currently impossible, yes. If iter_matches is ever fixed, we should be able to do it though.

However, without any nesting are we gaining anything over just using regular Tree-sitter highlighting? I don't think so because there is no alternating. The end result looks the same, but now we have all the computational and cognitive overhead of rainbow delimiters; we are checking for nesting levels which will never exist. You could have defined the same pattern in highlight.scm with a capture named @GitConfSectionBracket and then define highlighting like :hi link @GitConfSectionBracket RainbowDelimiterRed or some other group.

There are a few ways of doing what I want, but I generally like to keep extra files/code to a minimum. In this case I prefer to use rainbow-delimiters.scm over highlight.scm, since I am much more used to working with rainbow-delimiters. (Also, when there is no nesting + basically always small file sizes, rainbow-delimiters is really not doing much.)

Eh, I'm still not convinced and I think it would be more perceived as more unexpected than expected. If more people come forward who want it I will put it in, but for now let's leave things as they are.

Ok, I will just close this for now then.
As a last comment: I think people are used to the pre-treesitter rainbow parenthesis kind of plugin in other editors, so I still think that it is most common to always expect parenthesis highlighting.


2311 dashboard portfolio columns

I completed implementation, please review it
Issue: #60

The old table could compress itself hiding certaing columns if the window is too small, see here

Please investigate if ANT table allows that too

The old table could compress itself hiding certaing columns if the window is too small, see here

Please investigate if ANT table allows that too

In the old table, hiding certain columns was done manually. Unfortunately in antd it's also the only option.
I have added "column-hide-small" class where necessary.

There is nothing shown on the favorite section now, yet the pagination component suggests there is plenty. Please check @VerevkinAlexander

@sschiessl-bcp
The problem occurred because "MarketsTable" component depends on "PaginatedList" which was modified previously for switching to "bitshares-ui-style-guide" Table. So I created "PaginatedListOld" component which fixes "MarketsTable".
Should I rewrite "MarketsTable" for using "bitshares-ui-style-guide" Table?
Should I rewrite "MarketsTable" for using "bitshares-ui-style-guide" Table?

What other components use PaginatedList, and would require the "Old" way?

Assets (/explorer/assets) after selecting "Prediction market assets".

Assets (/explorer/assets) after selecting "Prediction market assets".

Thanks.
Please refactors Assets and MarketTable to use the new PaginatedList. For MarketsTable this might require that you integrate MarketsRow into the MarketTable class to stick to the new dataSource format.

I refactored MarketTable, changed data structure, to use the new PaginatedList. For Assets, I decided to use Antd List component instead of PaginatedList. Also, I merged the latest changed from develop branch. Please review my solution. Maybe we should add Antd List to the bitshares-ui-style-guide?

I refactored MarketTable, changed data structure, to use the new PaginatedList. For Assets, I decided to use Antd List component instead of PaginatedList. Also, I merged the latest changed from develop branch. Please review my solution. Maybe we should add Antd List to the bitshares-ui-style-guide?

Where is that list used?

When there is no data in the list it displays

Please notice that the text "No Data" is falling off of the bottom of the component. Please adjust such that the image has enough space

Where is that list used?

It used on Explorer tab => prediction market assets

When there is no data in the list it displays

Please notice that the text "No Data" is falling off of the bottom of the component. Please adjust such that the image has enough space

ok. I will do it asap

Please adjust the visuals

The table should be aligned like in the picture for Open Orders and activity as well.

Adjust the combobox to be using styleguide

If table doesnt fit, enable scrollbar

It seems that the footer does not have to correct number of cells when the screen is smaller

Please adjust the visuals

The table should be aligned like in the picture for Open Orders and activity as well.

Adjust the combobox to be using styleguide

If table doesnt fit, enable scrollbar

It seems that the footer does not have to correct number of cells when the screen is smaller

I fixed it, please review it

I fixed it, please review it

Forwarded.


Wrong Translation

https://github.com/marcrobledo/acnl-editor/blob/a1dcc2b961942cca0d894950414296726cdcf33d/data/acnl_items_de.js#L901
In german it's "Kiki-&-Lala-Tapete"

Fixed in 2b10e084a6a6febb318830fa422a5a6d0712091e


Levels

HI,
How can i create more levels? Are you planning on doin that?

Here is how i managet to have up to 10 levels:
Add a new class called "Levels"
put 10 public static final strings there and put your level setups inside them (you can copy the level from the Board-class in one of them and use it as a sample to create the others in the other strings).
In the Board class set the level-string to the first string of the Level-class
go into the TAdapter class inside the Board class and add cases for the number keys to the switch-statement.
put the same stuff like in the case for the r-key into them and above this content set the level-string to the matching string of the Levels-class.
if you start the game now, you can change the level with the number-keys
additional tip:
above the switch you will find
if (isCompleted) {
return;
}
Better remove this there and place it inside the cases for the arrow-keys.
so you are still able to restart or change the level, of you solved one.
actual you only can close the window, if you solved the level.

I want to keep the games simple so that beginners can understand it. I might have some upgrades in my e-books.

HI,
How can i create more levels? Are you planning on doin that?

@ KudosColin
you can look into my one, to see, how i managed it:
AngryBirdsSokoban
Now with a dialog for unlimites level-list.


ubuntu安装报错 Command '['ninja', '-v']' returned non-zero exit status 1.

raceback (most recent call last):
File "/usr/local/lib/python3.11/site-packages/torch/utils/cpp_extension.py", line 2107, in _run_ninja_build
subprocess.run(
File "/usr/local/lib/python3.11/subprocess.py", line 571, in run
raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['ninja', '-v']' returned non-zero exit status 1.
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/app/ComfyUI/nodes.py", line 1894, in load_custom_node
module_spec.loader.exec_module(module)
File "", line 940, in exec_module
File "", line 241, in call_with_frames_removed
File "/app/ComfyUI/custom_nodes/ComfyUI_OOTDiffusion_CXH/init.py", line 1, in
from .OodGenerater import Ood_CXH
File "/app/ComfyUI/custom_nodes/ComfyUI_OOTDiffusion_CXH/OodGenerater.py", line 6, in
from .preprocess.humanparsing.aigc_run_parsing import Parsing
File "/app/ComfyUI/custom_nodes/ComfyUI_OOTDiffusion_CXH/preprocess/humanparsing/aigc_run_parsing.py", line 7, in
from .parsing_api import load_atr_model, load_lip_model, inference
File "/app/ComfyUI/custom_nodes/ComfyUI_OOTDiffusion_CXH/preprocess/humanparsing/parsing_api.py", line 11, in
from . import networks
File "/app/ComfyUI/custom_nodes/ComfyUI_OOTDiffusion_CXH/preprocess/humanparsing/networks/init.py", line 2, in
from networks.AugmentCE2P import resnet101
File "/app/ComfyUI/custom_nodes/ComfyUI_OOTDiffusion_CXH/preprocess/humanparsing/networks/init.py", line 2, in
from networks.AugmentCE2P import resnet101
File "/app/ComfyUI/custom_nodes/ComfyUI_OOTDiffusion_CXH/preprocess/humanparsing/networks/AugmentCE2P.py", line 22, in
from modules import InPlaceABNSync
File "/app/ComfyUI/custom_nodes/ComfyUI_OOTDiffusion_CXH/preprocess/humanparsing/modules_/init.py", line 1, in
from .bn import ABN, InPlaceABN, InPlaceABNSync
File "/app/ComfyUI/custom_nodes/ComfyUI_OOTDiffusion_CXH/preprocess/humanparsing/modules_/bn.py", line 10, in
from .functions import *
File "/app/ComfyUI/custom_nodes/ComfyUI_OOTDiffusion_CXH/preprocess/humanparsing/modules_/functions.py", line 11, in
backend = load(name="inplace_abn",
^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/torch/utils/cpp_extension.py", line 1309, in load
return jit_compile(
^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/torch/utils/cpp_extension.py", line 1719, in jit_compile
write_ninja_file_and_build_library(
File "/usr/local/lib/python3.11/site-packages/torch/utils/cpp_extension.py", line 1832, in write_ninja_file_and_build_library
run_ninja_build(
File "/usr/local/lib/python3.11/site-packages/torch/utils/cpp_extension.py", line 2123, in run_ninja_build
raise RuntimeError(message) from e
RuntimeError: Error building extension 'inplace_abn': [1/5] /usr/local/cuda/bin/nvcc --generate-dependencies-with-compile --dependency-output inplace_abn_cuda.cuda.o.d -DTORCH_EXTENSION_NAME=inplace_abn -DTORCH_API_INCLUDE_EXTENSION_H -DPYBIND11_COMPILER_TYPE="gcc" -DPYBIND11_STDLIB="libstdcpp" -DPYBIND11_BUILD_ABI="cxxabi1011" -isystem /usr/local/lib/python3.11/site-packages/torch/include -isystem /usr/local/lib/python3.11/site-packages/torch/include/torch/csrc/api/include -isystem /usr/local/lib/python3.11/site-packages/torch/include/TH -isystem /usr/local/lib/python3.11/site-packages/torch/include/THC -isystem /usr/local/cuda/include -isystem /usr/local/include/python3.11 -D_GLIBCXX_USE_CXX11_ABI=0 -D__CUDA_NO_HALF_OPERATORS -D__CUDA_NO_HALF_CONVERSIONS -D__CUDA_NO_BFLOAT16_CONVERSIONS -D__CUDA_NO_HALF2_OPERATORS --expt-relaxed-constexpr -gencode=arch=compute_86,code=sm_86 --compiler-options '-fPIC' --expt-extended-lambda -std=c++17 -c /app/ComfyUI/custom_nodes/ComfyUI_OOTDiffusion_CXH/preprocess/humanparsing/modules/src/inplace_abn_cuda.cu -o inplace_abn_cuda.cuda.o
FAILED: inplace_abn_cuda.cuda.o
/usr/local/cuda/bin/nvcc --generate-dependencies-with-compile --dependency-output inplace_abn_cuda.cuda.o.d -DTORCH_EXTENSION_NAME=inplace_abn -DTORCH_API_INCLUDE_EXTENSION_H -DPYBIND11_COMPILER_TYPE="gcc" -DPYBIND11_STDLIB="libstdcpp" -DPYBIND11_BUILD_ABI="cxxabi1011" -isystem /usr/local/lib/python3.11/site-packages/torch/include -isystem /usr/local/lib/python3.11/site-packages/torch/include/torch/csrc/api/include -isystem /usr/local/lib/python3.11/site-packages/torch/include/TH -isystem /usr/local/lib/python3.11/site-packages/torch/include/THC -isystem /usr/local/cuda/include -isystem /usr/local/include/python3.11 -D_GLIBCXX_USE_CXX11_ABI=0 -D__CUDA_NO_HALF_OPERATORS -D__CUDA_NO_HALF_CONVERSIONS -D__CUDA_NO_BFLOAT16_CONVERSIONS__ -D__CUDA_NO_HALF2_OPERATORS__ --expt-relaxed-constexpr -gencode=arch=compute_86,code=sm_86 --compiler-options '-fPIC' --expt-extended-lambda -std=c++17 -c /app/ComfyUI/custom_nodes/ComfyUI_OOTDiffusion_CXH/preprocess/humanparsing/modules_/src/inplace_abn_cuda.cu -o inplace_abn_cuda.cuda.o
/bin/sh: 1: /usr/local/cuda/bin/nvcc: not found
[2/5] /usr/local/cuda/bin/nvcc --generate-dependencies-with-compile --dependency-output inplace_abn_cuda_half.cuda.o.d -DTORCH_EXTENSION_NAME=inplace_abn -DTORCH_API_INCLUDE_EXTENSION_H -DPYBIND11_COMPILER_TYPE="gcc" -DPYBIND11_STDLIB="libstdcpp" -DPYBIND11_BUILD_ABI="cxxabi1011" -isystem /usr/local/lib/python3.11/site-packages/torch/include -isystem /usr/local/lib/python3.11/site-packages/torch/include/torch/csrc/api/include -isystem /usr/local/lib/python3.11/site-packages/torch/include/TH -isystem /usr/local/lib/python3.11/site-packages/torch/include/THC -isystem /usr/local/cuda/include -isystem /usr/local/include/python3.11 -D_GLIBCXX_USE_CXX11_ABI=0 -D__CUDA_NO_HALF_OPERATORS -D__CUDA_NO_HALF_CONVERSIONS_ -D__CUDA_NO_BFLOAT16_CONVERSIONS__ -D__CUDA_NO_HALF2_OPERATORS__ --expt-relaxed-constexpr -gencode=arch=compute_86,code=sm_86 --compiler-options '-fPIC' --expt-extended-lambda -std=c++17 -c /app/ComfyUI/custom_nodes/ComfyUI_OOTDiffusion_CXH/preprocess/humanparsing/modules_/src/inplace_abn_cuda_half.cu -o inplace_abn_cuda_half.cuda.o
FAILED: inplace_abn_cuda_half.cuda.o
/usr/local/cuda/bin/nvcc --generate-dependencies-with-compile --dependency-output inplace_abn_cuda_half.cuda.o.d -DTORCH_EXTENSION_NAME=inplace_abn -DTORCH_API_INCLUDE_EXTENSION_H -DPYBIND11_COMPILER_TYPE="gcc" -DPYBIND11_STDLIB="libstdcpp" -DPYBIND11_BUILD_ABI="cxxabi1011" -isystem /usr/local/lib/python3.11/site-packages/torch/include -isystem /usr/local/lib/python3.11/site-packages/torch/include/torch/csrc/api/include -isystem /usr/local/lib/python3.11/site-packages/torch/include/TH -isystem /usr/local/lib/python3.11/site-packages/torch/include/THC -isystem /usr/local/cuda/include -isystem /usr/local/include/python3.11 -D_GLIBCXX_USE_CXX11_ABI=0 -D__CUDA_NO_HALF_OPERATORS -D__CUDA_NO_HALF_CONVERSIONS_ -D__CUDA_NO_BFLOAT16_CONVERSIONS__ -D__CUDA_NO_HALF2_OPERATORS__ --expt-relaxed-constexpr -gencode=arch=compute_86,code=sm_86 --compiler-options '-fPIC' --expt-extended-lambda -std=c++17 -c /app/ComfyUI/custom_nodes/ComfyUI_OOTDiffusion_CXH/preprocess/humanparsing/modules_/src/inplace_abn_cuda_half.cu -o inplace_abn_cuda_half.cuda.o
/bin/sh: 1: /usr/local/cuda/bin/nvcc: not found
[3/5] c++ -MMD -MF inplace_abn_cpu.o.d -DTORCH_EXTENSION_NAME=inplace_abn -DTORCH_API_INCLUDE_EXTENSION_H -DPYBIND11_COMPILER_TYPE="gcc" -DPYBIND11_STDLIB="libstdcpp" -DPYBIND11_BUILD_ABI="cxxabi1011" -isystem /usr/local/lib/python3.11/site-packages/torch/include -isystem /usr/local/lib/python3.11/site-packages/torch/include/torch/csrc/api/include -isystem /usr/local/lib/python3.11/site-packages/torch/include/TH -isystem /usr/local/lib/python3.11/site-packages/torch/include/THC -isystem /usr/local/cuda/include -isystem /usr/local/include/python3.11 -D_GLIBCXX_USE_CXX11_ABI=0 -fPIC -std=c++17 /O2 -c /app/ComfyUI/custom_nodes/ComfyUI_OOTDiffusion_CXH/preprocess/humanparsing/modules/src/inplace_abn_cpu.cpp -o inplace_abn_cpu.o
FAILED: inplace_abn_cpu.o
c++ -MMD -MF inplace_abn_cpu.o.d -DTORCH_EXTENSION_NAME=inplace_abn -DTORCH_API_INCLUDE_EXTENSION_H -DPYBIND11_COMPILER_TYPE="gcc" -DPYBIND11_STDLIB="libstdcpp" -DPYBIND11_BUILD_ABI="cxxabi1011" -isystem /usr/local/lib/python3.11/site-packages/torch/include -isystem /usr/local/lib/python3.11/site-packages/torch/include/torch/csrc/api/include -isystem /usr/local/lib/python3.11/site-packages/torch/include/TH -isystem /usr/local/lib/python3.11/site-packages/torch/include/THC -isystem /usr/local/cuda/include -isystem /usr/local/include/python3.11 -D_GLIBCXX_USE_CXX11_ABI=0 -fPIC -std=c++17 /O2 -c /app/ComfyUI/custom_nodes/ComfyUI_OOTDiffusion_CXH/preprocess/humanparsing/modules/src/inplace_abn_cpu.cpp -o inplace_abn_cpu.o
In file included from /usr/local/lib/python3.11/site-packages/torch/include/ATen/core/Generator.h:11,
from /usr/local/lib/python3.11/site-packages/torch/include/ATen/CPUGeneratorImpl.h:3,
from /usr/local/lib/python3.11/site-packages/torch/include/ATen/Context.h:3,
from /usr/local/lib/python3.11/site-packages/torch/include/ATen/ATen.h:7,
from /app/ComfyUI/custom_nodes/ComfyUI_OOTDiffusion_CXH/preprocess/humanparsing/modules/src/inplace_abn_cpu.cpp:1:
/app/ComfyUI/custom_nodes/ComfyUI_OOTDiffusion_CXH/preprocess/humanparsing/modules/src/inplace_abn_cpu.cpp: In function ‘void leaky_relu_backward_cpu(at::Tensor, at::Tensor, float)’:
/app/ComfyUI/custom_nodes/ComfyUI_OOTDiffusion_CXH/preprocess/humanparsing/modules/src/utils/checks.h:11:40: warning: ‘at::DeprecatedTypeProperties& at::Tensor::type() const’ is deprecated: Tensor.type() is deprecated. Instead use Tensor.options(), which in many cases (e.g. in a constructor) is a drop-in replacement. If you were using data from type(), that is now available from Tensor itself, so instead of tensor.type().scalar_type(), use tensor.scalar_type() instead and instead of tensor.type().backend() use tensor.device(). [-Wdeprecated-declarations]
11 | #define CHECK_CPU(x) AT_CHECK(!(x).type().is_cuda(), #x " must be a CPU tensor")
|                                ~~~~~~~~^~
/app/ComfyUI/custom_nodes/ComfyUI_OOTDiffusion_CXH/preprocess/humanparsing/modules/src/utils/checks.h:15:28: note: in expansion of macro ‘CHECK_CPU’
15 | #define CHECK_CPU_INPUT(x) CHECK_CPU(x); CHECK_CONTIGUOUS(x)
|                            ^~~~~~~~~
/app/ComfyUI/custom_nodes/ComfyUI_OOTDiffusion_CXH/preprocess/humanparsing/modules_/src/inplace_abn_cpu.cpp:86:3: note: in expansion of macro ‘CHECK_CPU_INPUT’
86 |   CHECK_CPU_INPUT(z);
|   ^~~~~~~~~~~~~~~
In file included from /usr/local/lib/python3.11/site-packages/torch/include/ATen/core/ivalue.h:4,
from /usr/local/lib/python3.11/site-packages/torch/include/ATen/core/List_inl.h:4,
from /usr/local/lib/python3.11/site-packages/torch/include/ATen/core/List.h:490,
from /usr/local/lib/python3.11/site-packages/torch/include/ATen/core/IListRef_inl.h:3,
from /usr/local/lib/python3.11/site-packages/torch/include/ATen/core/IListRef.h:631,
from /usr/local/lib/python3.11/site-packages/torch/include/ATen/DeviceGuard.h:3,
from /usr/local/lib/python3.11/site-packages/torch/include/ATen/ATen.h:9:
/usr/local/lib/python3.11/site-packages/torch/include/ATen/core/TensorBody.h:225:30: note: declared here
225 |   DeprecatedTypeProperties & type() const {
|                              ^~~~
/app/ComfyUI/custom_nodes/ComfyUI_OOTDiffusion_CXH/preprocess/humanparsing/modules_/src/utils/checks.h:11:40: warning: ‘at::DeprecatedTypeProperties& at::Tensor::type() const’ is deprecated: Tensor.type() is deprecated. Instead use Tensor.options(), which in many cases (e.g. in a constructor) is a drop-in replacement. If you were using data from type(), that is now available from Tensor itself, so instead of tensor.type().scalar_type(), use tensor.scalar_type() instead and instead of tensor.type().backend() use tensor.device(). [-Wdeprecated-declarations]
11 | #define CHECK_CPU(x) AT_CHECK(!(x).type().is_cuda(), #x " must be a CPU tensor")
|                                ^~
/app/ComfyUI/custom_nodes/ComfyUI_OOTDiffusion_CXH/preprocess/humanparsing/modules_/src/utils/checks.h:15:28: note: in expansion of macro ‘CHECK_CPU’
15 | #define CHECK_CPU_INPUT(x) CHECK_CPU(x); CHECK_CONTIGUOUS(x)
|                            ^
/app/ComfyUI/custom_nodes/ComfyUI_OOTDiffusion_CXH/preprocess/humanparsing/modules_/src/inplace_abn_cpu.cpp:87:3: note: in expansion of macro ‘CHECK_CPU_INPUT’
87 |   CHECK_CPU_INPUT(dz);
|   ^~~~~~~~~~~~~~~
/usr/local/lib/python3.11/site-packages/torch/include/ATen/core/TensorBody.h:225:30: note: declared here
225 |   DeprecatedTypeProperties & type() const {
|                              ^~~~
In file included from /usr/local/lib/python3.11/site-packages/torch/include/ATen/ATen.h:11:
/app/ComfyUI/custom_nodes/ComfyUI_OOTDiffusion_CXH/preprocess/humanparsing/modules_/src/inplace_abn_cpu.cpp: In lambda function:
/app/ComfyUI/custom_nodes/ComfyUI_OOTDiffusion_CXH/preprocess/humanparsing/modules_/src/inplace_abn_cpu.cpp:89:36: warning: ‘at::DeprecatedTypeProperties& at::Tensor::type() const’ is deprecated: Tensor.type() is deprecated. Instead use Tensor.options(), which in many cases (e.g. in a constructor) is a drop-in replacement. If you were using data from type(), that is now available from Tensor itself, so instead of tensor.type().scalar_type(), use tensor.scalar_type() instead and instead of tensor.type().backend() use tensor.device(). [-Wdeprecated-declarations]
89 |   AT_DISPATCH_FLOATING_TYPES(z.type(), "leaky_relu_backward_cpu", ([&] {
|                              ^~
/usr/local/lib/python3.11/site-packages/torch/include/ATen/core/TensorBody.h:225:30: note: declared here
225 |   DeprecatedTypeProperties & type() const {
|                              ^~
/app/ComfyUI/custom_nodes/ComfyUI_OOTDiffusion_CXH/preprocess/humanparsing/modules_/src/inplace_abn_cpu.cpp: In lambda function:
/app/ComfyUI/custom_nodes/ComfyUI_OOTDiffusion_CXH/preprocess/humanparsing/modules_/src/inplace_abn_cpu.cpp:91:32: warning: ‘T* at::Tensor::data() const [with T = double]’ is deprecated: Tensor.data() is deprecated. Please use Tensor.data_ptr() instead. [-Wdeprecated-declarations]
91 |     auto z = z.data<scalar_t>();
|                ~~~~~~~~~~~~~~^~
/usr/local/lib/python3.11/site-packages/torch/include/ATen/core/TensorBody.h:247:7: note: declared here
247 |   T * data() const {
|       ^~
/app/ComfyUI/custom_nodes/ComfyUI_OOTDiffusion_CXH/preprocess/humanparsing/modules/src/inplace_abn_cpu.cpp:92:34: warning: ‘T at::Tensor::data() const [with T = double]’ is deprecated: Tensor.data() is deprecated. Please use Tensor.data_ptr() instead. [-Wdeprecated-declarations]
92 |     auto dz = dz.data<scalar_t>();
|                 ~~~~~~~~~~~~~~~^~
/usr/local/lib/python3.11/site-packages/torch/include/ATen/core/TensorBody.h:247:7: note: declared here
247 |   T * data() const {
|       ^~
/app/ComfyUI/custom_nodes/ComfyUI_OOTDiffusion_CXH/preprocess/humanparsing/modules/src/inplace_abn_cpu.cpp: In lambda function:
/app/ComfyUI/custom_nodes/ComfyUI_OOTDiffusion_CXH/preprocess/humanparsing/modules_/src/inplace_abn_cpu.cpp:91:32: warning: ‘T at::Tensor::data() const [with T = float]’ is deprecated: Tensor.data() is deprecated. Please use Tensor.data_ptr() instead. [-Wdeprecated-declarations]
91 |     auto z = z.data<scalar_t>();
|                ~~~~~~~~~~~~~~^~
/usr/local/lib/python3.11/site-packages/torch/include/ATen/core/TensorBody.h:247:7: note: declared here
247 |   T * data() const {
|       ^~
/app/ComfyUI/custom_nodes/ComfyUI_OOTDiffusion_CXH/preprocess/humanparsing/modules/src/inplace_abn_cpu.cpp:92:34: warning: ‘T at::Tensor::data() const [with T = float]’ is deprecated: Tensor.data() is deprecated. Please use Tensor.data_ptr() instead. [-Wdeprecated-declarations]
92 |     auto *dz = dz.data<scalar_t>();
|                 ~~~~~~~~~~~~~~~^~
/usr/local/lib/python3.11/site-packages/torch/include/ATen/core/TensorBody.h:247:7: note: declared here
247 |   T * data() const {
|       ^~
/app/ComfyUI/custom_nodes/ComfyUI_OOTDiffusion_CXH/preprocess/humanparsing/modules/src/inplace_abn_cpu.cpp: In function ‘void elu_backward_cpu(at::Tensor, at::Tensor)’:
/app/ComfyUI/custom_nodes/ComfyUI_OOTDiffusion_CXH/preprocess/humanparsing/modules_/src/utils/checks.h:11:40: warning: ‘at::DeprecatedTypeProperties& at::Tensor::type() const’ is deprecated: Tensor.type() is deprecated. Instead use Tensor.options(), which in many cases (e.g. in a constructor) is a drop-in replacement. If you were using data from type(), that is now available from Tensor itself, so instead of tensor.type().scalar_type(), use tensor.scalar_type() instead and instead of tensor.type().backend() use tensor.device(). [-Wdeprecated-declarations]
11 | #define CHECK_CPU(x) AT_CHECK(!(x).type().is_cuda(), #x " must be a CPU tensor")
|                                ^~
/app/ComfyUI/custom_nodes/ComfyUI_OOTDiffusion_CXH/preprocess/humanparsing/modules_/src/utils/checks.h:15:28: note: in expansion of macro ‘CHECK_CPU’
15 | #define CHECK_CPU_INPUT(x) CHECK_CPU(x); CHECK_CONTIGUOUS(x)
|                            ^
/app/ComfyUI/custom_nodes/ComfyUI_OOTDiffusion_CXH/preprocess/humanparsing/modules_/src/inplace_abn_cpu.cpp:104:3: note: in expansion of macro ‘CHECK_CPU_INPUT’
104 |   CHECK_CPU_INPUT(z);
|   ^~~~~~~~~~~
/usr/local/lib/python3.11/site-packages/torch/include/ATen/core/TensorBody.h:225:30: note: declared here
225 |   DeprecatedTypeProperties & type() const {
|                              ^~~~
/app/ComfyUI/custom_nodes/ComfyUI_OOTDiffusion_CXH/preprocess/humanparsing/modules_/src/utils/checks.h:11:40: warning: ‘at::DeprecatedTypeProperties& at::Tensor::type() const’ is deprecated: Tensor.type() is deprecated. Instead use Tensor.options(), which in many cases (e.g. in a constructor) is a drop-in replacement. If you were using data from type(), that is now available from Tensor itself, so instead of tensor.type().scalar_type(), use tensor.scalar_type() instead and instead of tensor.type().backend() use tensor.device(). [-Wdeprecated-declarations]
11 | #define CHECK_CPU(x) AT_CHECK(!(x).type().is_cuda(), #x " must be a CPU tensor")
|                                ^~
/app/ComfyUI/custom_nodes/ComfyUI_OOTDiffusion_CXH/preprocess/humanparsing/modules_/src/utils/checks.h:15:28: note: in expansion of macro ‘CHECK_CPU’
15 | #define CHECK_CPU_INPUT(x) CHECK_CPU(x); CHECK_CONTIGUOUS(x)
|                            ^
/app/ComfyUI/custom_nodes/ComfyUI_OOTDiffusion_CXH/preprocess/humanparsing/modules_/src/inplace_abn_cpu.cpp:105:3: note: in expansion of macro ‘CHECK_CPU_INPUT’
105 |   CHECK_CPU_INPUT(dz);
|   ^~~~~~~~~~~~~~~
/usr/local/lib/python3.11/site-packages/torch/include/ATen/core/TensorBody.h:225:30: note: declared here
225 |   DeprecatedTypeProperties & type() const {
|                              ^~~~
/app/ComfyUI/custom_nodes/ComfyUI_OOTDiffusion_CXH/preprocess/humanparsing/modules_/src/inplace_abn_cpu.cpp: In lambda function:
/app/ComfyUI/custom_nodes/ComfyUI_OOTDiffusion_CXH/preprocess/humanparsing/modules_/src/inplace_abn_cpu.cpp:107:36: warning: ‘at::DeprecatedTypeProperties& at::Tensor::type() const’ is deprecated: Tensor.type() is deprecated. Instead use Tensor.options(), which in many cases (e.g. in a constructor) is a drop-in replacement. If you were using data from type(), that is now available from Tensor itself, so instead of tensor.type().scalar_type(), use tensor.scalar_type() instead and instead of tensor.type().backend() use tensor.device(). [-Wdeprecated-declarations]
107 |   AT_DISPATCH_FLOATING_TYPES(z.type(), "elu_backward_cpu", ([&] {
|                              ~~~~^~
/usr/local/lib/python3.11/site-packages/torch/include/ATen/core/TensorBody.h:225:30: note: declared here
225 |   DeprecatedTypeProperties & type() const {
|                              ^~
/app/ComfyUI/custom_nodes/ComfyUI_OOTDiffusion_CXH/preprocess/humanparsing/modules_/src/inplace_abn_cpu.cpp: In lambda function:
/app/ComfyUI/custom_nodes/ComfyUI_OOTDiffusion_CXH/preprocess/humanparsing/modules_/src/inplace_abn_cpu.cpp:109:32: warning: ‘T* at::Tensor::data() const [with T = double]’ is deprecated: Tensor.data() is deprecated. Please use Tensor.data_ptr() instead. [-Wdeprecated-declarations]
109 |     auto z = z.data<scalar_t>();
|                ~~~~~~~~~~~~~~^~
/usr/local/lib/python3.11/site-packages/torch/include/ATen/core/TensorBody.h:247:7: note: declared here
247 |   T * data() const {
|       ^~
/app/ComfyUI/custom_nodes/ComfyUI_OOTDiffusion_CXH/preprocess/humanparsing/modules/src/inplace_abn_cpu.cpp:110:34: warning: ‘T at::Tensor::data() const [with T = double]’ is deprecated: Tensor.data() is deprecated. Please use Tensor.data_ptr() instead. [-Wdeprecated-declarations]
110 |     auto dz = dz.data<scalar_t>();
|                 ~~~~~~~~~~~~~~~^~
/usr/local/lib/python3.11/site-packages/torch/include/ATen/core/TensorBody.h:247:7: note: declared here
247 |   T * data() const {
|       ^~
/app/ComfyUI/custom_nodes/ComfyUI_OOTDiffusion_CXH/preprocess/humanparsing/modules/src/inplace_abn_cpu.cpp: In lambda function:
/app/ComfyUI/custom_nodes/ComfyUI_OOTDiffusion_CXH/preprocess/humanparsing/modules_/src/inplace_abn_cpu.cpp:109:32: warning: ‘T at::Tensor::data() const [with T = float]’ is deprecated: Tensor.data() is deprecated. Please use Tensor.data_ptr() instead. [-Wdeprecated-declarations]
109 |     auto z = z.data<scalar_t>();
|                ~~~~~~~~~~~~~~^~
/usr/local/lib/python3.11/site-packages/torch/include/ATen/core/TensorBody.h:247:7: note: declared here
247 |   T * data() const {
|       ^~
/app/ComfyUI/custom_nodes/ComfyUI_OOTDiffusion_CXH/preprocess/humanparsing/modules/src/inplace_abn_cpu.cpp:110:34: warning: ‘T at::Tensor::data() const [with T = float]’ is deprecated: Tensor.data() is deprecated. Please use Tensor.data_ptr() instead. [-Wdeprecated-declarations]
110 |     auto *dz = dz.data<scalar_t>();
|                 ~~~~~~~~~~~~~^~
/usr/local/lib/python3.11/site-packages/torch/include/ATen/core/TensorBody.h:247:7: note: declared here
247 |   T * data() const {
|       ^~
c++: warning: /O2: linker input file unused because linking not done
c++: error: /O2: linker input file not found: No such file or directory
[4/5] c++ -MMD -MF inplace_abn.o.d -DTORCH_EXTENSION_NAME=inplace_abn -DTORCH_API_INCLUDE_EXTENSION_H -DPYBIND11_COMPILER_TYPE="_gcc" -DPYBIND11_STDLIB="libstdcpp" -DPYBIND11_BUILD_ABI="cxxabi1011" -isystem /usr/local/lib/python3.11/site-packages/torch/include -isystem /usr/local/lib/python3.11/site-packages/torch/include/torch/csrc/api/include -isystem /usr/local/lib/python3.11/site-packages/torch/include/TH -isystem /usr/local/lib/python3.11/site-packages/torch/include/THC -isystem /usr/local/cuda/include -isystem /usr/local/include/python3.11 -D_GLIBCXX_USE_CXX11_ABI=0 -fPIC -std=c++17 /O2 -c /app/ComfyUI/custom_nodes/ComfyUI_OOTDiffusion_CXH/preprocess/humanparsing/modules/src/inplace_abn.cpp -o inplace_abn.o
FAILED: inplace_abn.o
c++ -MMD -MF inplace_abn.o.d -DTORCH_EXTENSION_NAME=inplace_abn -DTORCH_API_INCLUDE_EXTENSION_H -DPYBIND11_COMPILER_TYPE="gcc" -DPYBIND11_STDLIB="libstdcpp" -DPYBIND11_BUILD_ABI="cxxabi1011" -isystem /usr/local/lib/python3.11/site-packages/torch/include -isystem /usr/local/lib/python3.11/site-packages/torch/include/torch/csrc/api/include -isystem /usr/local/lib/python3.11/site-packages/torch/include/TH -isystem /usr/local/lib/python3.11/site-packages/torch/include/THC -isystem /usr/local/cuda/include -isystem /usr/local/include/python3.11 -D_GLIBCXX_USE_CXX11_ABI=0 -fPIC -std=c++17 /O2 -c /app/ComfyUI/custom_nodes/ComfyUI_OOTDiffusion_CXH/preprocess/humanparsing/modules/src/inplace_abn.cpp -o inplace_abn.o
/app/ComfyUI/custom_nodes/ComfyUI_OOTDiffusion_CXH/preprocess/humanparsing/modules/src/inplace_abn.cpp: In function ‘std::vectorat::Tensor mean_var(at::Tensor)’:
/app/ComfyUI/custom_nodes/ComfyUI_OOTDiffusion_CXH/preprocess/humanparsing/modules/src/inplace_abn.cpp:9:15: warning: ‘at::DeprecatedTypeProperties& at::Tensor::type() const’ is deprecated: Tensor.type() is deprecated. Instead use Tensor.options(), which in many cases (e.g. in a constructor) is a drop-in replacement. If you were using data from type(), that is now available from Tensor itself, so instead of tensor.type().scalar_type(), use tensor.scalar_type() instead and instead of tensor.type().backend() use tensor.device(). [-Wdeprecated-declarations]
9 |     if (x.type().scalarType() == at::ScalarType::Half) {
|         ~~~~~~^~
In file included from /usr/local/lib/python3.11/site-packages/torch/include/ATen/core/Tensor.h:3,
from /usr/local/lib/python3.11/site-packages/torch/include/ATen/Tensor.h:3,
from /usr/local/lib/python3.11/site-packages/torch/include/torch/csrc/autograd/function_hook.h:3,
from /usr/local/lib/python3.11/site-packages/torch/include/torch/csrc/autograd/cpp_hook.h:2,
from /usr/local/lib/python3.11/site-packages/torch/include/torch/csrc/autograd/variable.h:6,
from /usr/local/lib/python3.11/site-packages/torch/include/torch/csrc/autograd/autograd.h:3,
from /usr/local/lib/python3.11/site-packages/torch/include/torch/csrc/api/include/torch/autograd.h:3,
from /usr/local/lib/python3.11/site-packages/torch/include/torch/csrc/api/include/torch/all.h:7,
from /usr/local/lib/python3.11/site-packages/torch/include/torch/extension.h:5,
from /app/ComfyUI/custom_nodes/ComfyUI_OOTDiffusion_CXH/preprocess/humanparsing/modules/src/inplace_abn.cpp:1:
/usr/local/lib/python3.11/site-packages/torch/include/ATen/core/TensorBody.h:225:30: note: declared here
225 |   DeprecatedTypeProperties & type() const {
|                              ^~
/app/ComfyUI/custom_nodes/ComfyUI_OOTDiffusion_CXH/preprocess/humanparsing/modules/src/inplace_abn.cpp: In function ‘at::Tensor forward(at::Tensor, at::Tensor, at::Tensor, at::Tensor, at::Tensor, bool, float)’:
/app/ComfyUI/custom_nodes/ComfyUI_OOTDiffusion_CXH/preprocess/humanparsing/modules_/src/inplace_abn.cpp:22:15: warning: ‘at::DeprecatedTypeProperties& at::Tensor::type() const’ is deprecated: Tensor.type() is deprecated. Instead use Tensor.options(), which in many cases (e.g. in a constructor) is a drop-in replacement. If you were using data from type(), that is now available from Tensor itself, so instead of tensor.type().scalar_type(), use tensor.scalar_type() instead and instead of tensor.type().backend() use tensor.device(). [-Wdeprecated-declarations]
22 |     if (x.type().scalarType() == at::ScalarType::Half) {
|         ~~~~^~
/usr/local/lib/python3.11/site-packages/torch/include/ATen/core/TensorBody.h:225:30: note: declared here
225 |   DeprecatedTypeProperties & type() const {
|                              ^~
/app/ComfyUI/custom_nodes/ComfyUI_OOTDiffusion_CXH/preprocess/humanparsing/modules_

有人遇到过吗

/usr/local/lib/python3.11/site-packages/torch/include/ATen/core/TensorBody.h:225:30: note: declared here
225 |   DeprecatedTypeProperties & type() const {
|                              ^~~~
/app/ComfyUI/custom_nodes/ComfyUI_OOTDiffusion_CXH/preprocess/humanparsing/modules_/src/inplace_abn.cpp: In function ‘std::vectorat::Tensor edz_eydz(at::Tensor, at::Tensor, at::Tensor, at::Tensor, bool, float)’:
/app/ComfyUI/custom_nodes/ComfyUI_OOTDiffusion_CXH/preprocess/humanparsing/modules_/src/inplace_abn.cpp:35:15: warning: ‘at::DeprecatedTypeProperties& at::Tensor::type() const’ is deprecated: Tensor.type() is deprecated. Instead use Tensor.options(), which in many cases (e.g. in a constructor) is a drop-in replacement. If you were using data from type(), that is now available from Tensor itself, so instead of tensor.type().scalar_type(), use tensor.scalar_type() instead and instead of tensor.type().backend() use tensor.device(). [-Wdeprecated-declarations]
35 |     if (z.type().scalarType() == at::ScalarType::Half) {
|         ~~~~^~
/usr/local/lib/python3.11/site-packages/torch/include/ATen/core/TensorBody.h:225:30: note: declared here
225 |   DeprecatedTypeProperties & type() const {
|                              ^~
/app/ComfyUI/custom_nodes/ComfyUI_OOTDiffusion_CXH/preprocess/humanparsing/modules_/src/inplace_abn.cpp: In function ‘at::Tensor backward(at::Tensor, at::Tensor, at::Tensor, at::Tensor, at::Tensor, at::Tensor, at::Tensor, bool, float)’:
/app/ComfyUI/custom_nodes/ComfyUI_OOTDiffusion_CXH/preprocess/humanparsing/modules_/src/inplace_abn.cpp:48:15: warning: ‘at::DeprecatedTypeProperties& at::Tensor::type() const’ is deprecated: Tensor.type() is deprecated. Instead use Tensor.options(), which in many cases (e.g. in a constructor) is a drop-in replacement. If you were using data from type(), that is now available from Tensor itself, so instead of tensor.type().scalar_type(), use tensor.scalar_type() instead and instead of tensor.type().backend() use tensor.device(). [-Wdeprecated-declarations]
48 |     if (z.type().scalarType() == at::ScalarType::Half) {
|         ~~~~^~
/usr/local/lib/python3.11/site-packages/torch/include/ATen/core/TensorBody.h:225:30: note: declared here
225 |   DeprecatedTypeProperties & type() const {
|                              ^~
/app/ComfyUI/custom_nodes/ComfyUI_OOTDiffusion_CXH/preprocess/humanparsing/modules_/src/inplace_abn.cpp: In function ‘void leaky_relu_backward(at::Tensor, at::Tensor, float)’:
/app/ComfyUI/custom_nodes/ComfyUI_OOTDiffusion_CXH/preprocess/humanparsing/modules_/src/inplace_abn.cpp:64:15: warning: ‘at::DeprecatedTypeProperties& at::Tensor::type() const’ is deprecated: Tensor.type() is deprecated. Instead use Tensor.options(), which in many cases (e.g. in a constructor) is a drop-in replacement. If you were using data from type(), that is now available from Tensor itself, so instead of tensor.type().scalar_type(), use tensor.scalar_type() instead and instead of tensor.type().backend() use tensor.device(). [-Wdeprecated-declarations]
64 |     if (z.type().scalarType() == at::ScalarType::Half) {
|         ~~~~^~
/usr/local/lib/python3.11/site-packages/torch/include/ATen/core/TensorBody.h:225:30: note: declared here
225 |   DeprecatedTypeProperties & type() const {
|                              ^~
c++: warning: /O2: linker input file unused because linking not done
c++: error: /O2: linker input file not found: No such file or directory
ninja: build stopped: subcommand failed.


⚠ WSINGRESOS - GENERICO has degraded performance

In f28a647, WSINGRESOS - GENERICO (https://srvshyweb.yucatan.gob.mx/cgi-bin/wspd_cgi.sh/WService=wsingresos/internet/servicios/wsGenericoPagosWeb.r) experienced degraded performance:

HTTP code: 200
Response time: 2254 ms

Resolved: WSINGRESOS - GENERICO performance has improved in 8a2053c after 20 minutes.