Fix lbrynet concurrency issues

Lbryum is not designed to be thread safe. We need to have lbrynet use lbryum in a single threaded manner, except in the case of when lbryum makes a network call to lbryum-server, which can be called on a separate thread asynchronously.
https://github.com/lbryio/lbryum/commit/ad0662e6b858c48f4c6a180d94d2399347bcc880
This commit adds a broadcast option to the claim command, separating the act of making a transaction, and broadcasting a transaction (  broadcasting a transaction is just a send to lbyum server ).
https://github.com/lbryio/lbryum/commit/e5fd46e7aa41003248fb77fc9f277c0d0205a432
This commit reorganizes getvalueforname command into multiple functions. getvaluforname command makes a lbryum server call and also accesses internal state.  Thus lbrynet needs to be able to do these things separately.  We create requestvalueforname command which just makes a query to lbryum server to get the proof for the value of name, and we also create a _verify_proof function that does the parsing of the proof from the lbryum server.
https://github.com/lbryio/lbryum/commit/14bafecf6271da41cf032888005e8a9183881094
This is a simple unit test for the _verify_proof function created in the above commit.

LGTM

Added some comments for how to use getvalueforname and requestvalueforname, merging.


Needs update for SR 3.4

stimulus_reflex_testing won't load when the app is using the pre-releases of StimulusReflex 3.4.  I get this error when rspec is setting up:
  uninitialized constant StimulusReflex::Channel

As of at least StimulusReflex 3.4.0-pre8, this class no longer exists, and I don't see an obvious replacement.
EDIT
SR still defines StimulusReflex::Channel it is but not available during bundler setup.

Turns out SR still defines StimulusReflex::Channel it is but not available during bundler setup.
If I change my Gemfile to
gem "stimulus_reflex_testing"

and require "stimulus_reflex_testing in spec/rails_helper.rb I can get past the missing constant error.  Then I get this error:
       undefined method `stream_name' for #<StimulusReflex::TestCase::TestChannel:0x00007f815c05b498>

stream_name is defined on StimulusReflex::Channel  Is there an instance the TestChannel could delegate to?

See: https://github.com/hopsoft/stimulus_reflex/pull/346

I've got this figured out on my box.  StimulusReflex::TestCase::TestChannel needs a few methods added to make it quack like StimulusReflex::Channel.  Will send a PR next chance I get.

I'm seeing an error when using https://github.com/podia/stimulus_reflex_testing/pull/7. After adding require: false to the Gemfile as mentioned, I get this:
Failure/Error: require "stimulus_reflex_testing/rspec"

NameError:
  uninitialized constant StimulusReflex::TestCase
# ./spec/rails_helper.rb:23:in `<top (required)>'

I'm on Rails 5.2, maybe that has something to do with it?

@ksweetie try this in rails_helper.rb:
require "stimulus_reflex_testing"
require "stimulus_reflex_testing/rspec"

@existentialmutt that did the trick, thank you so much!


#{column_name}_rank is undefined

I tried using the newly release feature of getting  relative rank, but am getting an undefined method error.

I encountered the same issue but discovered it wasn't actually an issue. The PR rmammina is referring to, https://github.com/mixonic/ranked-model/pull/137, isn't in a released version yet.

Lol, yes that'd be it :) We do plan to do a release but there is more to come on this feature so we're waiting on that to be settled first :)


Daily Luck Calendar?

Thanks a lot for your app @MouseyPounds, it's really handy!
I was wondering how the daily luck (as reported by the fortune teller on TV) is calculated. Is the calculation made at runtime (without any way to guess it) or is it using a predefined seed passed to a random() function?
Put simply, my question is: Would it be technically possible to have a calendar (as for the mines or train) on stardew-predictor with the Daily Luck for a given day?
Thanks!

Today I noticed that the daily luck was absent from Stardew Predictor and was very surprised.
Please add this feature!

The rng for dailyLuck is affected by stepsTaken. As this varies based on play, this predictor cannot provide predicitons. This is the same for dishOfTheDay, whether an NPC sends a gift, and weather. To predict these you either need to manually track steps and enter the information into a tool, or have a mod running in game which will make this prediction for you.


Don't make flutter drive gate iOS devices.

cc @yjbanov: I was able to get drive working on devices after this and a previous change. LMK if there is anything else to be done to enable the same on bots.

LGTM, but not sure we should submit until the waterfall clears up.

LMK if there is anything else to be done to enable the same on bots

I'll do the dashboard change myself. As for the waterfall bots, we don't have any devices on those, so this change should not affect them.


add x64dbg plugin manager

https://github.com/horsicq/x64dbg-Plugin-Manager

that allows you to install plugins and one of them is https://github.com/LFriede/x64dbg-updater that allows you to easilly upgrade x64dbg to latest version as in flare-vm isn't lastest one, so i think it also will simplify your life, i have manually installed on my side and works very well

Thank you for your feedback! We've been working on major updates to FLARE VM over the last year.
The now revamped FLARE VM has just been released and will make the project more open and maintainable.
Please check out our blog post at https://www.mandiant.com/resources/blog/flarevm-open-to-public and give the new installation a try.
If this problem still persists with the new installation, please report:

new tools or tool-related issues at https://github.com/mandiant/VM-Packages/issues
ideas and issues related to the installer script and configuration at https://github.com/mandiant/flare-vm/issues

Please note that we use this message to close all legacy issues in this repository. We look forward to your feedback and support for the next generation of FLARE VM.


[PE-D][Tester A] Undo/Redo feature does not persist between sessions

Data-modifying commands do not appear to be saved between sessions. In the below example, I cleared the entire contact list, exited the program, and re-opened the program. I was then unable to undo the clear command to get the pre-loaded default commands back.
I'm not sure if this is intended or not, but users may be confused by this behaviour since there is no mention that the undo command only tracks commands executed within that program session. If so, it might be helpful to include it in the user guide so users aren't caught off guard by this behaviour!
After clearing:

After reopening:

Labels: severity.Medium type.FunctionalityBug
original: Andrew22Teoh/ped#4

Normally undo/redo do not persist between sessions.


use postgresql 9.6 for the newest SLES and openSUSE releases

Awesome @tampakrap thanks for the PR !!!


updated data

Hi,
I notice that qa data is re-uploaded with comment "Re-upload correct data". I wonder what changes are made?
Thanks!

When converting our private repo to this publicly-released version, I made a mistake when retrieving hard negatives (distractors) for input queries (in short, I mistakenly used a different embedder for the query and the passage). Thus, the hard negatives in the initial data from this repo aren't as hard as the data that we used in our experiments. I re-ran the retrieval to get the correct (hardest) negatives, and that's in the new version of the data release.
I re-ran the experiments in the paper on the previously-uploaded incorrect data and found that the results were virtually unchanged, which is perhaps interesting unto itself.
Hope that helps, happy to answer any further questions you might have about it.

Thank you for your clarification! Another small question: is the following document updated as well?
https://nlp.stanford.edu/data/nfliu/lost-in-the-middle/nq-open-contriever-msmarco-retrieved-documents.jsonl.gz

Yes, that file was updated as well.


gmxtopology reader only create one residue with gmx-2016

Using a tpr file from gromacs-2016 and running in the propane/atomistic folder of csg-tutorials:
$ ~/votca/src/csg/src/tools/csg_map --no-map --top topol.tpr --trj conf.gro  --out conf2.gro

The residue number differs in conf.gro and conf2.gro.
It seems atoms->nres is 1even though there should be multiple copies of it.
Back when #162 was fixed (f986dc5907f7be4de22a2465280d5eb0843c8a94), it seemed to have worked!

I investigated that further and it seems this is broken at least since gromacs-5. (I tested gromacs-2016, gromacs-5.1 and gromacs-5.0).

Related to #344


Set up back-end for login

Specs

3 Log-In types:
a. Exec Member
b. Club Director
c. Bus Driver
Start looking at how each type of user can view a different part of the application

@Samyakkumar Do we want to update the existing user schema for this? Perhaps changing the 'isAdmin' field to a 'Role' field that is an enum. Maybe something like ['Exec', 'Director', 'Driver'] ?

He never responded lol but I think that makes sense! @matthewbrown77

There are a number of different options for configuring login. We could use a cookie-based approach, similar to the example in the next.js repo. We could also use something like the next-session package. I'm not sure if there is any type of "standard" approach that the club would like us to use.

Hmm if there is some existing logic that would make the job easier than go with that, all we need is for different user types/user profiles to be able to see only the data that is for them. Ideally a user would not have to log in every single time they open the website on a certain device, but if that is more difficult to implement it is not necessary. I guess in summary you can move forward with whatever you think would work best here.
Also, @matthewbrown77 I just realized, could you add another field in the log-in schema for associated "Club"? For admin we can just say "All" and for everyone else they will have a String associated with which club they work at. Let me know if I should clarify anything.

I can add that field to the user schema. We can also decide how long we want sessions to last before expiring in our meeting tomorrow. It's a simple change to make.


invite users to lexbox when adding to an org

this will be a close copy of the invite feature when adding users to a project.
There will need to be some tweaks done in the UserController.AcceptEmailInvitation method to account for the user being invited to an org. And EmailService.SendCreateAccountEmail` will need to be modified to add org and make project optional.

I would like to also add a checkbox to the dialog called "Invite if missing" then the invite email will only be sent if that box is checked. If it's not checked and the user doesn't exist then we show an error to the user informing them that the user didn't exist.


Consultation on making a request

I'm creating pull request about https://github.com/vitmalina/w2ui/issues/2136
This issue occur on Jquery version >=3.2.0 with  w2ui-1.5 branch.
My fix code is removing recs.scrollTop() from w2ui-1.5 branch like current master(w2ui-2.0)
However, when I change w2grid.js(1.5) then such bug occur using Jquery version < 3.2.0.
So, Can I change the code?

Please submit the PR to 1.5 branch, not master


[Device Support Request] Legrand Adorne WNAL63W1 Wireless Dimmer

Is your feature request related to a problem? Please describe.
I am unable to use this wireless dimmer in ZHA. I can bind the dimming function only, but it is reversed in that when I press the lower button, the brightness increases, and vice-versa. I cannot get the on/off function to work.
Describe the solution you'd like
Would like to be able to bind this wireless dimmer to a zigbee lamp. It has a single on/off push button, and raise/lower dimmer buttons. It is battery powered.  Here is a link to the product. https://www.legrand.us/wiring-devices/designer-switches-and-outlets/adorne-wireless-smart-dimmer-with-netatmo-white/p/wnal63w1

Device signature
{
  "node_descriptor": "NodeDescriptor(logical_type=<LogicalType.EndDevice: 2>, complex_descriptor_available=0, user_descriptor_available=1, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress: 128>, manufacturer_code=4129, maximum_buffer_size=89, maximum_incoming_transfer_size=63, server_mask=10752, maximum_outgoing_transfer_size=63, descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True, *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=True, *is_full_function_device=False, *is_mains_powered=False, *is_receiver_on_when_idle=False, *is_router=False, *is_security_capable=False)",
  "endpoints": {
    "1": {
      "profile_id": 260,
      "device_type": "0x0104",
      "in_clusters": [
        "0x0000",
        "0x0001",
        "0x0003",
        "0x000f",
        "0x0020",
        "0xfc01"
      ],
      "out_clusters": [
        "0x0000",
        "0x0003",
        "0x0006",
        "0x0008",
        "0x0019",
        "0xfc01"
      ]
    }
  },
  "manufacturer": " Legrand",
  "model": " Remote dimmer switch",
  "class": "zigpy.device.Device"
}

Diagnostic information
{
  "home_assistant": {
    "installation_type": "Home Assistant OS",
    "version": "2022.11.4",
    "dev": false,
    "hassio": true,
    "virtualenv": false,
    "python_version": "3.10.7",
    "docker": true,
    "arch": "aarch64",
    "timezone": "America/New_York",
    "os_name": "Linux",
    "os_version": "5.15.61-v8",
    "supervisor": "2022.11.2",
    "host_os": "Home Assistant OS 9.3",
    "docker_version": "20.10.18",
    "chassis": "embedded",
    "run_as_root": true
  },
  "custom_components": {},
  "integration_manifest": {
    "domain": "zha",
    "name": "Zigbee Home Automation",
    "config_flow": true,
    "documentation": "https://www.home-assistant.io/integrations/zha",
    "requirements": [
      "bellows==0.34.2",
      "pyserial==3.5",
      "pyserial-asyncio==0.6",
      "zha-quirks==0.0.86",
      "zigpy-deconz==0.19.0",
      "zigpy==0.51.5",
      "zigpy-xbee==0.16.2",
      "zigpy-zigate==0.10.3",
      "zigpy-znp==0.9.1"
    ],
    "usb": [
      {
        "vid": "10C4",
        "pid": "EA60",
        "description": "*2652*",
        "known_devices": [
          "slae.sh cc2652rb stick"
        ]
      },
      {
        "vid": "1A86",
        "pid": "55D4",
        "description": "*sonoff*plus*",
        "known_devices": [
          "sonoff zigbee dongle plus v2"
        ]
      },
      {
        "vid": "10C4",
        "pid": "EA60",
        "description": "*sonoff*plus*",
        "known_devices": [
          "sonoff zigbee dongle plus"
        ]
      },
      {
        "vid": "10C4",
        "pid": "EA60",
        "description": "*tubeszb*",
        "known_devices": [
          "TubesZB Coordinator"
        ]
      },
      {
        "vid": "1A86",
        "pid": "7523",
        "description": "*tubeszb*",
        "known_devices": [
          "TubesZB Coordinator"
        ]
      },
      {
        "vid": "1A86",
        "pid": "7523",
        "description": "*zigstar*",
        "known_devices": [
          "ZigStar Coordinators"
        ]
      },
      {
        "vid": "1CF1",
        "pid": "0030",
        "description": "*conbee*",
        "known_devices": [
          "Conbee II"
        ]
      },
      {
        "vid": "10C4",
        "pid": "8A2A",
        "description": "*zigbee*",
        "known_devices": [
          "Nortek HUSBZB-1"
        ]
      },
      {
        "vid": "0403",
        "pid": "6015",
        "description": "*zigate*",
        "known_devices": [
          "ZiGate+"
        ]
      },
      {
        "vid": "10C4",
        "pid": "EA60",
        "description": "*zigate*",
        "known_devices": [
          "ZiGate"
        ]
      },
      {
        "vid": "10C4",
        "pid": "8B34",
        "description": "*bv 2010/10*",
        "known_devices": [
          "Bitron Video AV2010/10"
        ]
      }
    ],
    "codeowners": [
      "@dmulcahey",
      "@adminiuga",
      "@puddly"
    ],
    "zeroconf": [
      {
        "type": "_esphomelib._tcp.local.",
        "name": "tube*"
      },
      {
        "type": "_zigate-zigbee-gateway._tcp.local.",
        "name": "*zigate*"
      },
      {
        "type": "_zigstar_gw._tcp.local.",
        "name": "*zigstar*"
      }
    ],
    "dependencies": [
      "file_upload"
    ],
    "after_dependencies": [
      "onboarding",
      "usb",
      "zeroconf"
    ],
    "iot_class": "local_polling",
    "loggers": [
      "aiosqlite",
      "bellows",
      "crccheck",
      "pure_pcapy3",
      "zhaquirks",
      "zigpy",
      "zigpy_deconz",
      "zigpy_xbee",
      "zigpy_zigate",
      "zigpy_znp"
    ],
    "is_built_in": true
  },
  "data": {
    "ieee": "**REDACTED**",
    "nwk": 22710,
    "manufacturer": " Legrand",
    "model": " Remote dimmer switch",
    "name": " Legrand  Remote dimmer switch",
    "quirk_applied": false,
    "quirk_class": "zigpy.device.Device",
    "manufacturer_code": 4129,
    "power_source": "Battery or Unknown",
    "lqi": 232,
    "rssi": -85,
    "last_seen": "2022-11-27T18:16:46",
    "available": true,
    "device_type": "EndDevice",
    "signature": {
      "node_descriptor": "NodeDescriptor(logical_type=<LogicalType.EndDevice: 2>, complex_descriptor_available=0, user_descriptor_available=1, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress: 128>, manufacturer_code=4129, maximum_buffer_size=89, maximum_incoming_transfer_size=63, server_mask=10752, maximum_outgoing_transfer_size=63, descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True, *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=True, *is_full_function_device=False, *is_mains_powered=False, *is_receiver_on_when_idle=False, *is_router=False, *is_security_capable=False)",
      "endpoints": {
        "1": {
          "profile_id": 260,
          "device_type": "0x0104",
          "in_clusters": [
            "0x0000",
            "0x0001",
            "0x0003",
            "0x000f",
            "0x0020",
            "0xfc01"
          ],
          "out_clusters": [
            "0x0000",
            "0x0003",
            "0x0006",
            "0x0008",
            "0x0019",
            "0xfc01"
          ]
        }
      }
    },
    "active_coordinator": false,
    "entities": [
      {
        "entity_id": "binary_sensor.legrand_remote_dimmer_switch_binaryinput",
        "name": " Legrand  Remote dimmer switch"
      },
      {
        "entity_id": "button.legrand_remote_dimmer_switch_identify",
        "name": " Legrand  Remote dimmer switch"
      },
      {
        "entity_id": "sensor.legrand_remote_dimmer_switch_battery",
        "name": " Legrand  Remote dimmer switch"
      }
    ],
    "neighbors": [],
    "endpoint_names": [
      {
        "name": "DIMMER_SWITCH"
      }
    ],
    "user_given_name": null,
    "device_reg_id": "59b0239b4e83b7f2c65e002adf970589",
    "area_id": "patio",
    "cluster_details": {
      "1": {
        "device_type": {
          "name": "DIMMER_SWITCH",
          "id": 260
        },
        "profile_id": 260,
        "in_clusters": {
          "0x0000": {
            "endpoint_attribute": "basic",
            "attributes": {
              "0x0004": {
                "attribute_name": "manufacturer",
                "value": " Legrand"
              },
              "0x0005": {
                "attribute_name": "model",
                "value": " Remote dimmer switch"
              }
            },
            "unsupported_attributes": {}
          },
          "0x0003": {
            "endpoint_attribute": "identify",
            "attributes": {},
            "unsupported_attributes": {}
          },
          "0x000f": {
            "endpoint_attribute": "binary_input",
            "attributes": {
              "0x0055": {
                "attribute_name": "present_value",
                "value": 0
              }
            },
            "unsupported_attributes": {}
          },
          "0x0020": {
            "endpoint_attribute": "poll_control",
            "attributes": {
              "0x0000": {
                "attribute_name": "checkin_interval",
                "value": 13200
              }
            },
            "unsupported_attributes": {}
          },
          "0x0001": {
            "endpoint_attribute": "power",
            "attributes": {
              "0x0020": {
                "attribute_name": "battery_voltage",
                "value": 24
              },
              "0x0021": {
                "attribute_name": "battery_percentage_remaining",
                "value": 0
              }
            },
            "unsupported_attributes": {
              "0x0021": {
                "attribute_name": "battery_percentage_remaining"
              },
              "0x0033": {
                "attribute_name": "battery_quantity"
              },
              "0x0031": {
                "attribute_name": "battery_size"
              }
            }
          },
          "0xfc01": {
            "endpoint_attribute": "manufacturer_specific",
            "attributes": {},
            "unsupported_attributes": {}
          }
        },
        "out_clusters": {
          "0x0003": {
            "endpoint_attribute": "identify",
            "attributes": {},
            "unsupported_attributes": {}
          },
          "0x0006": {
            "endpoint_attribute": "on_off",
            "attributes": {},
            "unsupported_attributes": {}
          },
          "0x0008": {
            "endpoint_attribute": "level",
            "attributes": {},
            "unsupported_attributes": {}
          },
          "0x0000": {
            "endpoint_attribute": "basic",
            "attributes": {},
            "unsupported_attributes": {}
          },
          "0xfc01": {
            "endpoint_attribute": "manufacturer_specific",
            "attributes": {},
            "unsupported_attributes": {}
          },
          "0x0019": {
            "endpoint_attribute": "ota",
            "attributes": {},
            "unsupported_attributes": {}
          }
        }
      }
    }
  }
}

Additional logs
Paste any additional debug logs here.
Don't remove the extra line breaks outside the ``` marks.

Additional context
I have a ZHA quirk that i installed on my system, but it did not work for this product. I believe you can see it in the diagnostics.

My understanding is that once you bind the devices directly together they can communicate independently of HA/ZHA, so its up to the firmware on the devices to communicate properly. In this case where things are not working as you expect, you might actually need to use HA/ZHA to interpret and facilitate proper communication between the devices. What lamp device are you using?
FYI, according to the diagnostics info, it does not look like you are using a quirk.
#1934 was recently merged to provide specific support for the Radiant version of this Legrand switch, but the signatures are identical, so I would expect this to apply to your Adorne switch as well. I'm not sure if this code has made it into a release yet though. I have some additional code I added to my quirk to support all the button triggers natively in HA Automations. I've attached the file that you'll need to rename and remove the .txt extension.
legrand_wireless_dimmer.py.txt

Steven,
I appreciate the help. One thing I realized afterwards is that I didn't remove & re-pair my dimmer after adding the quirk.
I did try to use the legrand_wireless_dimmer.py quirk, and it still doesn't work properly. The adorne wireless dimmers are different from the Radiant dimmers in that they have a single on/off push-button and not an up & down push button. I'm not sure what else internally is different; I've got some Radiant switches & wireless switches but I can't remember if Legrand sent me any wireless Radiant dimmers.
I'm trying to bind it to a hue lamp. All I'm really trying to accomplish is being able to use the Bticino toggle switch relays along with some wireless dimmers. If the netatmo integration is ever fixed, I could install the hue lamps and dimmers directly to the Legrand gateway, and setup an automation in HA for the Bticino relays using Zigbee2MQTT. I've already tested the toggle switch automation through Z2M and it works. I just need the dimmers there now. It would be nice though to also have the Bticino relay in ZHA so I could bind it directly to the hue lamps.

Here is a pic of what I see when trying to reconfigure the device.

Here is my diagnostic info with the quirk

Diagnostic information
{
  "home_assistant": {
    "installation_type": "Home Assistant OS",
    "version": "2022.11.5",
    "dev": false,
    "hassio": true,
    "virtualenv": false,
    "python_version": "3.10.7",
    "docker": true,
    "arch": "aarch64",
    "timezone": "America/New_York",
    "os_name": "Linux",
    "os_version": "5.15.61-v8",
    "supervisor": "2022.11.2",
    "host_os": "Home Assistant OS 9.3",
    "docker_version": "20.10.18",
    "chassis": "embedded",
    "run_as_root": true
  },
  "custom_components": {},
  "integration_manifest": {
    "domain": "zha",
    "name": "Zigbee Home Automation",
    "config_flow": true,
    "documentation": "https://www.home-assistant.io/integrations/zha",
    "requirements": [
      "bellows==0.34.4",
      "pyserial==3.5",
      "pyserial-asyncio==0.6",
      "zha-quirks==0.0.87",
      "zigpy-deconz==0.19.1",
      "zigpy==0.51.6",
      "zigpy-xbee==0.16.2",
      "zigpy-zigate==0.10.3",
      "zigpy-znp==0.9.1"
    ],
    "usb": [
      {
        "vid": "10C4",
        "pid": "EA60",
        "description": "*2652*",
        "known_devices": [
          "slae.sh cc2652rb stick"
        ]
      },
      {
        "vid": "1A86",
        "pid": "55D4",
        "description": "*sonoff*plus*",
        "known_devices": [
          "sonoff zigbee dongle plus v2"
        ]
      },
      {
        "vid": "10C4",
        "pid": "EA60",
        "description": "*sonoff*plus*",
        "known_devices": [
          "sonoff zigbee dongle plus"
        ]
      },
      {
        "vid": "10C4",
        "pid": "EA60",
        "description": "*tubeszb*",
        "known_devices": [
          "TubesZB Coordinator"
        ]
      },
      {
        "vid": "1A86",
        "pid": "7523",
        "description": "*tubeszb*",
        "known_devices": [
          "TubesZB Coordinator"
        ]
      },
      {
        "vid": "1A86",
        "pid": "7523",
        "description": "*zigstar*",
        "known_devices": [
          "ZigStar Coordinators"
        ]
      },
      {
        "vid": "1CF1",
        "pid": "0030",
        "description": "*conbee*",
        "known_devices": [
          "Conbee II"
        ]
      },
      {
        "vid": "10C4",
        "pid": "8A2A",
        "description": "*zigbee*",
        "known_devices": [
          "Nortek HUSBZB-1"
        ]
      },
      {
        "vid": "0403",
        "pid": "6015",
        "description": "*zigate*",
        "known_devices": [
          "ZiGate+"
        ]
      },
      {
        "vid": "10C4",
        "pid": "EA60",
        "description": "*zigate*",
        "known_devices": [
          "ZiGate"
        ]
      },
      {
        "vid": "10C4",
        "pid": "8B34",
        "description": "*bv 2010/10*",
        "known_devices": [
          "Bitron Video AV2010/10"
        ]
      }
    ],
    "codeowners": [
      "@dmulcahey",
      "@adminiuga",
      "@puddly"
    ],
    "zeroconf": [
      {
        "type": "_esphomelib._tcp.local.",
        "name": "tube*"
      },
      {
        "type": "_zigate-zigbee-gateway._tcp.local.",
        "name": "*zigate*"
      },
      {
        "type": "_zigstar_gw._tcp.local.",
        "name": "*zigstar*"
      }
    ],
    "dependencies": [
      "file_upload"
    ],
    "after_dependencies": [
      "onboarding",
      "usb",
      "zeroconf"
    ],
    "iot_class": "local_polling",
    "loggers": [
      "aiosqlite",
      "bellows",
      "crccheck",
      "pure_pcapy3",
      "zhaquirks",
      "zigpy",
      "zigpy_deconz",
      "zigpy_xbee",
      "zigpy_zigate",
      "zigpy_znp"
    ],
    "is_built_in": true
  },
  "data": {
    "ieee": "**REDACTED**",
    "nwk": 16487,
    "manufacturer": " Legrand",
    "model": " Remote dimmer switch",
    "name": " Legrand  Remote dimmer switch",
    "quirk_applied": true,
    "quirk_class": "zhaquirks.legrand.dimmer.RemoteDimmer",
    "manufacturer_code": 4129,
    "power_source": "Battery or Unknown",
    "lqi": 255,
    "rssi": -77,
    "last_seen": "2022-11-30T18:23:06",
    "available": true,
    "device_type": "EndDevice",
    "signature": {
      "node_descriptor": "NodeDescriptor(logical_type=<LogicalType.EndDevice: 2>, complex_descriptor_available=0, user_descriptor_available=1, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress: 128>, manufacturer_code=4129, maximum_buffer_size=89, maximum_incoming_transfer_size=63, server_mask=10752, maximum_outgoing_transfer_size=63, descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True, *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=True, *is_full_function_device=False, *is_mains_powered=False, *is_receiver_on_when_idle=False, *is_router=False, *is_security_capable=False)",
      "endpoints": {
        "1": {
          "profile_id": 260,
          "device_type": "0x0104",
          "in_clusters": [
            "0x0000",
            "0x0001",
            "0x0003",
            "0x000f",
            "0x0020",
            "0xfc01"
          ],
          "out_clusters": [
            "0x0000",
            "0x0003",
            "0x0006",
            "0x0008",
            "0x0019",
            "0xfc01"
          ]
        }
      }
    },
    "active_coordinator": false,
    "entities": [
      {
        "entity_id": "binary_sensor.legrand_remote_dimmer_switch_binaryinput",
        "name": " Legrand  Remote dimmer switch"
      },
      {
        "entity_id": "button.legrand_remote_dimmer_switch_identify",
        "name": " Legrand  Remote dimmer switch"
      },
      {
        "entity_id": "sensor.legrand_remote_dimmer_switch_battery",
        "name": " Legrand  Remote dimmer switch"
      }
    ],
    "neighbors": [],
    "endpoint_names": [
      {
        "name": "DIMMER_SWITCH"
      }
    ],
    "user_given_name": null,
    "device_reg_id": "59b0239b4e83b7f2c65e002adf970589",
    "area_id": "patio",
    "cluster_details": {
      "1": {
        "device_type": {
          "name": "DIMMER_SWITCH",
          "id": 260
        },
        "profile_id": 260,
        "in_clusters": {
          "0x0000": {
            "endpoint_attribute": "basic",
            "attributes": {},
            "unsupported_attributes": {}
          },
          "0x0001": {
            "endpoint_attribute": "power",
            "attributes": {
              "0x0020": {
                "attribute_name": "battery_voltage",
                "value": 24
              },
              "0x0021": {
                "attribute_name": "battery_percentage_remaining",
                "value": 0
              }
            },
            "unsupported_attributes": {
              "0x0021": {
                "attribute_name": "battery_percentage_remaining"
              },
              "0x0033": {
                "attribute_name": "battery_quantity"
              },
              "0x0031": {
                "attribute_name": "battery_size"
              }
            }
          },
          "0x0003": {
            "endpoint_attribute": "identify",
            "attributes": {},
            "unsupported_attributes": {}
          },
          "0x000f": {
            "endpoint_attribute": "binary_input",
            "attributes": {
              "0x0055": {
                "attribute_name": "present_value",
                "value": 0
              }
            },
            "unsupported_attributes": {}
          },
          "0x0020": {
            "endpoint_attribute": "poll_control",
            "attributes": {
              "0x0000": {
                "attribute_name": "checkin_interval",
                "value": 13200
              }
            },
            "unsupported_attributes": {}
          },
          "0xfc01": {
            "endpoint_attribute": "legrand_cluster",
            "attributes": {},
            "unsupported_attributes": {}
          }
        },
        "out_clusters": {
          "0x0000": {
            "endpoint_attribute": "basic",
            "attributes": {},
            "unsupported_attributes": {}
          },
          "0x0003": {
            "endpoint_attribute": "identify",
            "attributes": {},
            "unsupported_attributes": {}
          },
          "0x0006": {
            "endpoint_attribute": "on_off",
            "attributes": {},
            "unsupported_attributes": {}
          },
          "0x0008": {
            "endpoint_attribute": "level",
            "attributes": {},
            "unsupported_attributes": {}
          },
          "0x0019": {
            "endpoint_attribute": "ota",
            "attributes": {},
            "unsupported_attributes": {}
          },
          "0xfc01": {
            "endpoint_attribute": "legrand_cluster",
            "attributes": {},
            "unsupported_attributes": {}
          }
        }
      }
    }
  }
}

That looks like the zigbee interview/joining issue I experienced. I had very sporadic results joining the device to ZHA with the firmware shipped on the wireless dimmer. I had to purchase the Legrand Smart Gateway to get the firmware updated to the latest, which according to the Legrand tech support fixed a lot of zigbee connectivity issues with 3rd party coordinators. The firmware I'm running is 31 as shown in the Legrand Control app; ZHA displays it as 0x001f4203.
I could sometimes get better results by continuously pressing the config button during the joining process.

That looks like the zigbee interview/joining issue I experienced. I had very sporadic results joining the device to ZHA with the firmware shipped on the wireless dimmer. I had to purchase the Legrand Smart Gateway to get the firmware updated to the latest, which according to the Legrand tech support fixed a lot of zigbee connectivity issues with 3rd party coordinators. The firmware I'm running is 31 as shown in the Legrand Control app; ZHA displays it as 0x001f4203.
I could sometimes get better results by continuously pressing the config button during the joining process.

I just paired it to the Legrand gateway, its version 28. I'll try to force it to 31 and start over. thanks again

also, not sure if this is significant info, but when I'm pressing buttons on the adorne dimmer, I see the following in the logbook:
If I press dimmer paddle "lower", I see...

Legrand Remote dimmer switch Stop event was fired with parameters: {'options_mask': None, 'options_override': None}

Followed by...

Legrand Remote dimmer switch Move event was fired with parameters: {'move_mode': <MoveMode.Up: 0>, 'rate': 100, 'options_mask': None, 'options_override': None}

When I press dimmer paddle "raise", I see...

Legrand Remote dimmer switch Stop event was fired with parameters: {'options_mask': None, 'options_override': None}

followed by...

Legrand Remote dimmer switch Move event was fired with parameters: {'move_mode': <MoveMode.Down: 1>, 'rate': 100, 'options_mask': None, 'options_override': None}

When I press the single on/off button, there is no event data. I pressed it multiple times, got nothing.
Press "dim lower" and I see.....

event_type: zha_event
data:
device_ieee: 64:62:66:ff:fe:61:a0:4b
unique_id: 64:62:66:ff:fe:61:a0:4b:1:0x0008
device_id: 59b0239b4e83b7f2c65e002adf970589
endpoint_id: 1
cluster_id: 8
command: move
args:
- 0
- 100
params:
move_mode: 0
rate: 100
options_mask: null
options_override: null
origin: LOCAL
time_fired: "2022-12-01T03:07:02.962111+00:00"
context:
id: 01GK5TDRXJHEAAT24ZW1ZQKNZQ
parent_id: null
user_id: null

and then...

event_type: zha_event
data:
device_ieee: 64:62:66:ff:fe:61:a0:4b
unique_id: 64:62:66:ff:fe:61:a0:4b:1:0x0008
device_id: 59b0239b4e83b7f2c65e002adf970589
endpoint_id: 1
cluster_id: 8
command: stop
args: []
params:
options_mask: null
options_override: null
origin: LOCAL
time_fired: "2022-12-01T03:07:03.038186+00:00"
context:
id: 01GK5TDRZYDYFAZCKNE4H601C9
parent_id: null
user_id: null

When I press "dim raise" I see.....

event_type: zha_event
data:
device_ieee: 64:62:66:ff:fe:61:a0:4b
unique_id: 64:62:66:ff:fe:61:a0:4b:1:0x0008
device_id: 59b0239b4e83b7f2c65e002adf970589
endpoint_id: 1
cluster_id: 8
command: move
args:
- 1
- 100
params:
move_mode: 1
rate: 100
options_mask: null
options_override: null
origin: LOCAL
time_fired: "2022-12-01T03:07:47.052562+00:00"
context:
id: 01GK5TF3ZCWA868DCV8FTKG3WX
parent_id: null
user_id: null

followed by.....

event_type: zha_event
data:
device_ieee: 64:62:66:ff:fe:61:a0:4b
unique_id: 64:62:66:ff:fe:61:a0:4b:1:0x0008
device_id: 59b0239b4e83b7f2c65e002adf970589
endpoint_id: 1
cluster_id: 8
command: stop
args: []
params:
options_mask: null
options_override: null
origin: LOCAL
time_fired: "2022-12-01T03:07:47.064904+00:00"
context:
id: 01GK5TF3ZR34JT8QRXWCDTBKDH
parent_id: null
user_id: null

This is probably because your OnOff cluster is not bound. Your image shows a yellow X on both the OnOff and LevelControl clusters, so I would have not expected events on either cluster, but perhaps the LevelControl bound during the initial pairing. I'm by no means an expert, but I think you'll need to get both the clusters bound for this to work. If re-pairing is not successful you can also try manual binding.
-Navigate to the device, click the 3 dots menu next to the Reconfigure button, and click Manage zigbee device.
-Select the Bindings tab.
-Under the Bindable Devices drop-down, select your zigbee coordinator device.
-Click the Bind button.
Since the dimmer is a battery powered SED (sleepy end device) you'll have to press the config button and/or the other buttons to wake it up to receive the command. In my experience, the bind button just keeps spinning even though it succeeds. And I retry it a few times, you can close the dialog to clear the spinning bind button for a retry.

I was unsuccessful at binding. I really appreciate all the help. I'm not sure what else I can do at this point.

I'm attaching my debug log here. Hoping to get this one sorted out also. On/Off doesn't work, and the DIM_UP / DIM_DOWN functions are reversed on the switch. When I press Dim Down, it reports a DIM_UP and vice versa. Thanks.
home-assistant_zha_2022-12-23T02-06-00.909Z.log

I was able to create an external converter in Zigbee2MQTT to support this dimmer.
Is there any information I could use from that to create a working quirk in ZHA?
When I press the on/off button on the dimmer, I see this in the Z2M log:
MQTT publish: topic 'zigbee2mqtt/Patio Light 1', payload '{"brightness":120,"color_mode":"xy","linkquality":148,"power_on_behavior":null,"state":"OFF","update":{"installed_version":"1.93.11","state":"available"},"update_available":null}'

@brantmacga I have three of these dimmers in the house currently. I've found the reliability of the switches using the Legrand hub to be terrible, and am trying to test out using the Home Assistant SkyConnect device to directly communicate with them instead. I'm new to Home Assistant and to ZHA, but not new to programming. Please feel free to reach out if you are interested in working on this with me.


Breakpoints of record and most all tables need revisiting after seasonizing

We're assuredly breaking too much at some viewport sizes now to accomodate columns that no longer exist.

This actually changed very little but showing # decks in cardstable and update of docs is in 0c3354f3.


ISPN-2183 get all implementation

https://issues.jboss.org/browse/ISPN-2183

There are some JCache TCK issues I need to look into still.

Updated to fix tck issues.

This needs to be updated after https://github.com/infinispan/infinispan/pull/3354 is integrated.

To be honest now that the putAll JIRA is complete I need to redo parts of this to use the new collections.  Let me update that first.

Updated with new changes and rebased.

Rebased again.

Rebased and also properly tested nontx and tx stress and regular tests.

@wburns @danberindei is this ready to go?

@gustavonalle No unfortunately not just yet.

Okay it seems to pass the core test suite and the stress tests seem to be fine now as well.

Integrated, thanks Will and Radim!


Table 'mydb.sessions' doesn't exist

When using sqlalchemy with mysql, http://localhost:port/get shows below error.
I think there's no table named 'sessions' in mysql.
how can i create it or where's create table statement.
thank you in advance.

sqlalchemy.exc.ProgrammingError
sqlalchemy.exc.ProgrammingError: (mysql.connector.errors.ProgrammingError) 1146 (42S02): Table 'gentok.sessions' doesn't exist
[SQL: SELECT sessions.id AS sessions_id, sessions.session_id AS sessions_session_id, sessions.data AS sessions_data, sessions.expiry AS sessions_expiry
FROM sessions
WHERE sessions.session_id = %(session_id_1)s
LIMIT %(param_1)s]
[parameters: {'session_id_1': 'session:0497ac5b-323d-4496-95a0-c26414f49035', 'param_1': 1}]
(Background on this error at: http://sqlalche.me/e/f405)

Was just looking into this myself. Should there or is there any documentation for this? I'm assuming we'll need a table similar to what's here: https://github.com/fengsp/flask-session/blob/master/flask_session/sessions.py#L477

If you don't set SESSION_SQLALCHEMY, flask_session will create it's own db instance, and the session table is created with this db instance. Thus session table will not be created by calling created_all with your db instance.
Quick fix:
db.init_app(app)
app.config['SESSION_SQLALCHEMY'] = db
Session(app)

Im not sure about those assumptions.
Case of my, I didn't set app.config['SESSION_SQLALCHEMY'] = db, session did not created it's own instance, session complained about sessions table not found (in my current db).
I've just added one more create_all() call for it.
# function to create database in first attemtp to use it
@app.before_first_request
def startup():
    # create tables from our models
    db.create_all()
    # create session tables
    app.session_interface.db.create_all()

This will create session tables in an existent database, no need to delete it.
Maybe that auto call to create_all() has been removed at some point.
Btw, what I am facing is a lot of problems with python3 and this library.

Im not sure about those assumptions.
Case of my, I didn't set app.config['SESSION_SQLALCHEMY'] = db, session did not created it's own instance, session complained about sessions table not found (in my current db).
I've just added one more create_all() call for it.
# function to create database in first attemtp to use it
@app.before_first_request
def startup():
    # create tables from our models
    db.create_all()
    # create session tables
    app.session_interface.db.create_all()

This will create session tables in an existent database, no need to delete it.
Maybe that auto call to create_all() has been removed at some point.
Btw, what I am facing is a lot of problems with python3 and this library.

This should be fixed now from 0.6.0. However, it might be good to have a warning run when no SESSION_SQLALCHEMY etc is set.


Autorest Regen Preview to 3.0.0-alpha.20240305.4 by Mingzhe Huang from refs/pull/4315/head

Triggered from https://github.com/Azure/autorest.csharp/pull/4315

API change check
API changes are not detected in this pull request.


Helm operator to respond to Namespace resources.

Feature Request
Describe the problem you need a feature to resolve.
I'd like to be able to apply a Helm chart in response to a Namespace resource, using labels or annotations on the Namespace resource. I think it is fairly common to want to have operators do things in response to off-the-shelf Helm resources, and Namespace is one of those.
Describe the solution you'd like.
A few potential features might be needed:

Helm operator would need to be able to handle cluster-scoped resources (currently can only handle namespaced resources)
It seems that Helm Operator can only operate on CRDs -- due to the fact that it needs to set a HelmAppStatus on the resource
Would need a way to pass labels and annotations into the values of the Helm chart, since we can't add a spec to Namespace.

/language helm

Hi @davidnortonjr-sps,
Thank you for raise this RFE. Could you please describe further what do you mean with I'd like to be able to apply a Helm chart in response to a Namespace resource? Are you looking for the scenario where the operator will watch a specific namespace and then when it is created/edit/update/delete the Helm chart will be applied?
Regards your comment Helm operator would need to be able to handle cluster-scoped resources (currently can only handle namespaced resources), I'd like to share that the Operators project has new layout since 1.0+ and they are cluster scope by default.
In this way, I'd like to recommend you migrate your project to the new layout (1.0+). See; https://sdk.operatorframework.io/docs/building-operators/helm/migration/. Note that the version 0.19.x can receive only bug fixes and the previous versions are no longer supported.

Also, would like to raise an EP in https://github.com/operator-framework/enhancements where you would detail more how it would work?

Lets have more discussion here before anyone starts an enhancement proposal.

Hi @davidnortonjr-sps,
It is open for a while without a response in the raised questions made https://github.com/operator-framework/operator-sdk/issues/4046#issuecomment-710147046 for we have a better understanding of the RFE wish by you here as your scenario.
In this way, shows that you might figure out that is no longer required and then would be fine close this one. However, if you see that it is something that we could address then, could you please ping us to re-open this or raise a new issue by providing the. further details. Also, maybe add the steps to reproduce the issue/scenario that you are trying to solve with the current behaviour and then, with its outcome after this RFE could be very helpful as well. I'd like to indeed recommend you add the use cases scenarios as well such as "I am as a Helm operator-based developer, I'd like to ... so that I could to do ...". It would be very helpful for we have a better understanding of your scenario. May the steps to reproduce it
Really thank you for your collab with btw.


Chocolatey Support for GreenTunnel

Is your feature request related to a problem? Please describe.
Inclusion of GreenTunnel into https://chocolatey.org/ for easier downloading (1.7.6+)
Describe alternatives you've considered
Terminal download alternatives for Windows is hard to come by.

An unofficial community package request was recently raised here:
https://github.com/chocolatey-community/chocolatey-package-requests/issues/1346
I've volunteered to implement this and am actively working toward creating a package for both the GUI and CLI versions. Progress can be tracked at that issue.
@SadeghHayeri, if you're interested in maintaining these, I'd be happy to help you get set up and coordinate a handoff once they're up and running.

Packages have been created and are now available for consumption from Chocolatey's Community Repository:
https://community.chocolatey.org/packages/green-tunnel-gui
https://community.chocolatey.org/packages/green-tunnel-cli


AOI

AOI selection is twice, i.e. in AOI and in parameters. We should merge all to one?

solved, by using just the sepal-ui standard aoi selection (more flexibility)


"import xxxxx" without any warnings in the error list.

Describe the bug

Steps to Reproduce

Create a Python Application.
type import xxxxx.

Expected behavior
Displays a green squiggly line under xxxxx and a warning in the error list.

Additional context and screenshots
No green squiggly lines and warnings.

Logs

Output for Pylance in the Output panel

Info: (9784) Pylance language server 2024.2.2 (pyright version 1.1.348, commit cfb1de0c) starting
Info: (9784) Server root directory: file:///c%3A/program%20files/microsoft%20visual%20studio/2022/preview/common7/ide/extensions/microsoft/python/core/pylance/dist
Info: (9784) Starting service instance "PythonApplication3"
Info: Un-registering request handler for 02b1ea61-5009-494e-a1c9-ead895eabc4e failed.
Info: (9784) Found 1 source file
Info: (9784) Background analysis(1) root directory: file:///c%3A/program%20files/microsoft%20visual%20studio/2022/preview/common7/ide/extensions/microsoft/python/core/pylance/dist
Info: (9784) Background analysis(1) started
Info: (9784) Indexer background runner(2) root directory: file:///c%3A/program%20files/microsoft%20visual%20studio/2022/preview/common7/ide/extensions/microsoft/python/core/pylance/dist (index)
Info: (9784) Indexing(2) started
Info: (9784) scanned(2) 14 files over 1 exec env
Info: (9784) indexed(2) 5 files over 1 exec env
Info: (9784) Indexing finished(2).

#7827 , #7830 , #7831 , #7832 repro with pylance version >= 2023.12.103, which indicates the bugs might be caused by one of the pyrx commits from 1/4/2024 - 1/10/2024.

The commit that caused all these regressions has been narrowed down to https://github.com/microsoft/pyrx/commit/bad397c6c7a04e40ec917e3da412cd7b04e74f2d


Remove ability to implement on_runtime_upgrade in pallets from macros

Breaking change:

pallets can't declare on_runtime_upgrade anymore.
pallet on_runtime_upgrade is removed from pallets:

system
contracts
offences
staking
vesting

User of those pallets must be careful that they are up to date or to trigger the runtime upgrade manually in on_runtime_ugprade definition at the runtime level.
Description
This PR doesn't remove the execution of pallet's on_runtime_upgrade, it only remove the ability to implemented from the macros: pallet and decl_module.
Maybe in the future we can have some implementation inside pallet on_runtime_upgrade like very little one like the version or stuff like this ?
Also we could use the implementation of post_upgrade to define some checks.
This PR also remove the ability to remove to implement pre_upgrade / post_upgrade in the macros. Maybe we can keep them though.
TODO:

polkadot doesn't need to manually call the removed on runtime upgrade.

[ ] system
[ ] contracts
[ ] offences
[ ] staking
[ ] vesting

谢谢，您的邮件已收到，我会及时查看

where does api-noteworthy goes? does it also mean it goes in the release notes @thiolliere? I am sure runtime-noteworthy stuff will go to the Runtime version of the release notes.

I see, considering we suggest ppl to use polkadot release as a standard substrate release I think the API notes should be there, but I don't know if it is the case.
The thing is that the polkadot runtime will not change, only the substrate API of pallets and FRAME

@thiolliere Can I throw one wrench in here?
This takes away people's ability to define (the equivalent of) on_pallet_initialization functions. They currently depend on using on_runtime_upgrade to set pallet genesis config values in case the pallet is added via runtime upgrade.
Do you expect people to do this via custom migration?
While I agree that people should mostly opt for custom/runtime-level migrations, I'm somewhat hesitant to just remove the feature wholesale.
I assume you considered and rejected marking it as deprecated and/or dangerous?

This PR doesn't remove the execution of pallet's on_runtime_upgrade, it only remove the ability to implemented from the macros: pallet and decl_module.

Why not remove this as well? Or ideally emit a warning about it for now. Ideally no one should depend on AllPallets as OnRuntimeUpgrade anymore. Because currently even if you don't haave the macros you could still implement it manually for Pallet<T>.

No the macro implements it with no-op so user cannot reimplement it. It would be double implementation of trait on type.
The reason I was thinking is that we can check the storage version match the latest one in post_upgrade automatically for example. Or other similar stuff.
But we can do in a follow-up if people here prefer so.

This PR doesn't remove the execution of pallet's on_runtime_upgrade, it only remove the ability to implemented from the macros: pallet and decl_module.

How would I execute it from the pallet when not using the macro?

@thiolliere Can I throw one wrench in here? This takes away people's ability to define (the equivalent of) on_pallet_initialization functions. They currently depend on using on_runtime_upgrade to set pallet genesis config values in case the pallet is added via runtime upgrade. Do you expect people to do this via custom migration? While I agree that people should mostly opt for custom/runtime-level migrations, I'm somewhat hesitant to just remove the feature wholesale. I assume you considered and rejected marking it as deprecated and/or dangerous?

I don't really know how to mark it as deprecated easily, also nobody should be blocked because they are removed. It is not difficult to call the migration at the runtime level.
For the purpose of "initialization" of new pallet in runtime, I understand the usecase, I also think that for such usecase we would actually want something more complete, like genesis config allow to define a type to have information about what to put at initialisation, there is no similar type for runtime upgrade.
I'm personally not completely opposed to keep them. Maybe our mistake is to not benchmark the runtime upgrade properly. If the runtime upgrade is correctly benchmarked then it should as safe as a regular on_initialize.

This PR doesn't remove the execution of pallet's on_runtime_upgrade, it only remove the ability to implemented from the macros: pallet and decl_module.

How would I execute it from the pallet when not using the macro?

The idea of the PR is to remove this ability, the only way to define it is to declare the pallet without using the FRAME macros.
Also we might remove it from executive as well https://github.com/paritytech/substrate/pull/10434#issuecomment-987757040

@thiolliere Can I throw one wrench in here? This takes away people's ability to define (the equivalent of) on_pallet_initialization functions. They currently depend on using on_runtime_upgrade to set pallet genesis config values in case the pallet is added via runtime upgrade. Do you expect people to do this via custom migration?

Yes, setting genesis values by using on_runtime_upgrade is also not a good idea. What would the genesis values be? How can the user configure them? This is just wrong.

While I'm for removing the on_runtime_upgrade in the pallet. We had last week a discussion where we came up with one legitimate example of using on_runtime_upgrade in a pallet. This is when we bump the transaction version, pallets should be made aware of this to may remove stored calls as they may could fail to decode or may to decode to something broken. However, maybe we could move that into a new hook on_transaction_version bumped or something similar and remove on_runtime_upgrade.

if we consider that some on_transaction_version hook are useful I think we should keep on_runtime_upgrade and just not use it for big migration and always have a precise estimation of weight.

given the new input, I suppose we can just remove the current on_runtime_upgrades implementations from our code base to set an example for others to follow, but keep the functionality in the code, for now.

I agree with Kian.
I think our usage of on_runtime_upgrade is not the best when it do migration which are not correctly benchmark and which can cost a lot of weight.
In the future we should avoid such automatic migration in our pallet.
But on_runtime_upgrade still seems useful to execute some small and correctly benchmarked stuff.
For this reason I'll close the PR.
Removing the individual on_runtime_upgrade for pallets can be done in separate PR when it makes sense.


Remove custom tailwind setup

Currently, this example is using the same tailwind setup as the https://github.com/supabase/supabase.
It would be better if this example didn't require a custom tailwind config and was more generalised.

i'm interested to know if anyone has succeffully migrated this config to app router.
I'm a good day into this error:
Import trace for requested module:
./styles/globals.css
./app/layout.tsx
⨯ ./styles/globals.css
Module parse failed: Unexpected character '@' (1:0)

@tailwind base;
| @tailwind components;
| @tailwind utilities;

i've got everything but the sink in my content array:
module.exports = ui({
content: [
'./app///.{js,ts,jsx,tsx,mdx}', // Note the addition of the app directory.
'./app/**/.{js,ts,jsx,tsx,mdx}',
'./pages//*.{js,ts,jsx,tsx,mdx}',
'./components//.{js,ts,jsx,tsx,mdx}',
'./lib/.{js,ts,jsx,tsx,mdx}',
'./styles/**/.{js,ts,jsx,tsx,mdx,css}',
'./_blog/.mdx',
<EMAIL_ADDRESS>


Add basic guidance if docker isn't running

Apply is far from the only place that we would expect docker failures. However, since #180 wasn't actually as bad as expected, let's not bother investing the time and energy yet to get this right.


chore: add support for multi-arch image publish

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@0a68c40). Click here to learn what that means.
Patch has no changes to coverable lines.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@           Coverage Diff           @@
##             main       #4   +/-   ##
=======================================
  Coverage        ?   76.75%
=======================================
  Files           ?       13
  Lines           ?     1540
  Branches        ?        0
=======================================
  Hits            ?     1182
  Misses          ?      227
  Partials        ?      131

Flag
Coverage Δ

unit-tests
76.75% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Fix #874: Enable using BoltJS without passing a botId

Summary
Fixes #874
Currently, when using an app that only makes use of a user token, the ignoreSelf middleware will throw an error because it expects a botId to always be present.
This PR removes the error thrown (and corresponding test) if a botId is not present in the incoming event's payload.
Requirements (place an x in each [ ])

[x] I've read and understood the Contributing Guidelines and have done my best effort to follow them.
[x] I've read and agree to the Code of Conduct.

@misscoded Thanks, the test also looks good to me 👍


When get RPM resource, make sure linked_composes unique.

JIRA: PDC-935

Better have unit test cover this case.

Looks good to me, but a test case would be nice.

@erichuanggit  @lubomir  Added the test case. Please review.

:+1:

Merged as d64f808e. I removed the forgotten print in test case.


Add ZHT to my itoken2 wallet?

How is this done please?
Hello hello??

below is the tutorial, you can refer to it.
https://github.com/consenlabs/token-profile#token-profile-guideline


Does the sampling result include the original image and mask

Thank you very much for providing the code.
Download BRAST2020 data set and preprocess it into (1,240,240) according to the method in the paper.

The training and sampling process were successfully carried out, but the sampling result was a little strange, including the original image and mask.Because the final image generated in the paper only has a mask.So I wonder if I'm doing something wrong.
And here's the sampling result.

My sincere thanks to you again. and look forward to your reply.

@guanzhenghua In the below-mentioned code - the sample is the output mask - and I think it's only output segmentation - I don't know how you are getting everything included.
sample, x_noisy, org = sample_fn(
model,
(args.batch_size, 3, args.image_size, args.image_size), img,
clip_denoised=args.clip_denoised,
model_kwargs=model_kwargs,
)
Can you share the pre-processing code - the original 3D to 2d slice wise folder code.

@saisusmitha of course, it is easy to slice 3D to 2D, i will show the code later.
I processed the data in the author's way, From the picture, it should be fine.
I'm sure the data preprocessing is fine, but the result does include a mixture of the original and the segmentation, so i wonder and need the author's answer. Have you run this program successfully.
maybe we can talk more in email<EMAIL_ADDRESS>I am looking forward to your email.
import nibabel as nib
import os
import numpy as np
path_in = r'H:\数据\新建文件夹\BraTS2020_TrainingData\MICCAI_BraTS2020_TrainingData'
path_out = r"H:\数据\新建文件夹\BraTS2020_croped_240"
start_second = True
list_four = [0,1,2,3,4]
num = 0
for root, dirs, files in os.walk(path_in):#root表示文件夹路径，dirs为空，files文件夹里的文件名
print(num)
num+=1
if start_second == False:#because the first root is not right,so use the "start_second" just for drop out it
for i in range(26, 75):
file_name = os.path.split(root)
nii_four = os.listdir(root)  # 0 1 2 3 4
        sub_dir = os.path.join(path_out, file_name[-1])
        sub_dir_add = "{}{}".format(sub_dir,"_"+str(i))
        os.mkdir(sub_dir_add)

        for j in list_four:
            sample_raw = nib.load(os.path.join(root,nii_four[j]))
            affine = sample_raw.affine.copy()
            hdr = sample_raw.header.copy()
            sample_np = np.asarray(sample_raw.get_fdata())
            sample_np = sample_np[:, :, i]
            gen = nib.Nifti1Image(sample_np, affine, hdr)

            rename = nii_four[j].split(".")
            rename = "{}_{}{}".format(rename[0],i,rename[1])
            nib.save(gen, os.path.join(sub_dir_add,rename))

start_second = False

@saisusmitha of course, it is easy to slice 3D to 2D, i will show the code later.
I processed the data in the author's way, From the picture, it should be fine.
I'm sure the data preprocessing is fine, but the result does include a mixture of the original and the segmentation, so i wonder and need the author's answer. Have you run this program successfully.
maybe we can talk more in email<EMAIL_ADDRESS>I am looking forward to your email.
import nibabel as nib
import os
import numpy as np
path_in = r'H:\数据\新建文件夹\BraTS2020_TrainingData\MICCAI_BraTS2020_TrainingData'
path_out = r"H:\数据\新建文件夹\BraTS2020_croped_240"
start_second = True
list_four = [0,1,2,3,4]
num = 0
for root, dirs, files in os.walk(path_in):#root表示文件夹路径，dirs为空，files文件夹里的文件名
print(num)
num+=1
if start_second == False:#because the first root is not right,so use the "start_second" just for drop out it
for i in range(26, 75):
file_name = os.path.split(root)
nii_four = os.listdir(root)  # 0 1 2 3 4
        sub_dir = os.path.join(path_out, file_name[-1])
        sub_dir_add = "{}{}".format(sub_dir,"_"+str(i))
        os.mkdir(sub_dir_add)

        for j in list_four:
            sample_raw = nib.load(os.path.join(root,nii_four[j]))
            affine = sample_raw.affine.copy()
            hdr = sample_raw.header.copy()
            sample_np = np.asarray(sample_raw.get_fdata())
            sample_np = sample_np[:, :, i]
            gen = nib.Nifti1Image(sample_np, affine, hdr)

            rename = nii_four[j].split(".")
            rename = "{}_{}{}".format(rename[0],i,rename[1])
            nib.save(gen, os.path.join(sub_dir_add,rename))

start_second = False

@saisusmitha of course, it is easy to slice 3D to 2D, i will show the code later.
I processed the data in the author's way, From the picture, it should be fine.
I'm sure the data preprocessing is fine, but the result does include a mixture of the original and the segmentation, so i wonder and need the author's answer. Have you run this program successfully.
maybe we can talk more in email<EMAIL_ADDRESS>I am looking forward to your email.

Copying the code directly will look strange, please forgive me for using the screenshot of the code.

@saisusmitha the author answer this question in #13, it is true thar the sampling result include the original image and mask, so in order to get perfert mask which is sampled by original image, should another operate that is add the threshold to separate the profile and the mask.


Python version required

Should the first line of the preprocessor.py be
#!/usr/bin/env python2.7 ?

Python 3 compatibility merged in fff1c6bab75ee7035e59c0e270b259fcb37a17c9.


Error: e.split is not a function

VS Code Version: 1.85 Insiders, Copilot Chat pre-release
OS Version: Windows 11

Steps to Reproduce:

Open Chat view and select sparkle and proposed query "What are some best practices for writing clean code?":

Error: 'e.split is not a function`

Also trying another suggested query:

I also encountered this problem, any idea why this happens?

If you see this again can you share the Copilot Chat log, or check whether that error shows up in the Window or Extension Host output channels?

Here's the issue again https://github.com/microsoft/vscode-copilot/issues/3128 and includes a consistent repro

Hi there, I'm having the same issue when using the chat view on side panel only. Using quick chat, everything works fine.

https://github.com/microsoft/vscode-copilot-release/issues/652 @pyrenaicus


Suggest layout for form

Suggest Layout for the form to make it more attractive

Hey!
I would love to work on this issue.

@kanishkaa24 you currently have two assigned issue
You can first finish them and then I will assign you

Okay
Thank you !

Hey!
I would like to work on this issue. Should we use Figma to design the form and can you send the template of the form?

@Aniket31-coder the current form looks fine but if you have a better template which may go good with the project you can share the template and we can have a discussion over it

You can use figma to create the basic layout and if approved you can create the form using material UI components for which you will be getting extra points

Okay, sure. Thanks for guiding!!

Hey!
I have created a basic layout, please let me know if any changes are required!!

That's look Pretty Cool @Aniket31-coder
Just One Question will it go good with our Background as it is also yellow in Color
If you Can attach a screenshot of the complete homepage then it will be easy to decide
Else the design is Awesome

Yes, that's the reason I chose yellow, I will send you the complete homepage soon!
Thanks!

Sure would be happy to merge your work
On Sun, 27 Dec 2020, 1:22 pm Aniket31-coder<EMAIL_ADDRESS>wrote:

Yes, that's the reason I chose yellow, I will send you the complete
homepage soon!
Thanks!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Tejas1510/Athavani/issues/5#issuecomment-751437332,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APMNZKK7Z4YCH26P7747JFDSW3RSXANCNFSM4VJGF3SQ
.

Hi,
I have done making the final layout and the complete homepage looks like this.

But when we start writing the text goes between two colors yellow and white

Could you please tell if it is fine or suggest any changes which would make the text go in a single color?

@Aniket31-coder the design looks good but I would suggest to choose a different colour for the form as it gets mixed with background
It should clearly evident rest everything is ok
For text input let it be simple black

Okay, sure!

Hey!
I have changed the color as per your feedback!

Could you tell if this color looks good?

Go ahead and make a Pr @Aniket31-coder
It looks good to me

Thanks for helping me and accepting my idea!

As I have one issue assigned, Can I work on this one too?

This issue is completed


[BUG] Always set sysctls and modules

Similar to https://github.com/gravitational/gravity.e/issues/3897
If a sysctl happens to be set at install time, the autofix code won't  configure the setting at boot. This can be commonly caused by install gravity on a node, uninstalling gravity, than re-installing gravity. On the reinstall the sysctls will have been set by the first install, and as such the sysctl configuration at boot will be missing.
Relevant code: https://github.com/gravitational/gravity/blob/master/lib/checks/autofix/autofix.go#L108-L118

I think simplest would be to generate the sysctl file and the list of modules to load unconditionally - there will be no need for autofix.

I believe the sysctl side of this was done but not linked to the ticket, however, it wasn't done for kernel modules and OSS users are seeing problems in the install -> uninstall -> install scenario with missed modules.


WormholeB0 BERT Large Slow/Fast Dispatch Bad PCC and Hang

Describe the bug
Currently when running bert large perf on WH, we can achieve one run with bad pcc.
In slow dispatch, if we run again, we just get bad PCC again. In fast dispatch, we hang if we run again.
To Reproduce
Onagrebenisan/bert-large-on-wh, run the following twice in a row
TT_METAL_LOGGER_LEVEL=debug pytest tests/models/bert_large_perf/test_bert_batch_dram.py::test_bert_batch_dram[phiyodr/bert-large-finetuned-squad2-9-384-True-True-True-0.98]

Expected behavior
You should see a crappy PCC with the following log
PCC on wormhole_b0 for bert batch dram is expected to be poor

and then running again (if in fast dispatch), you should get a hang.

This issue has grown extremely stale. Does this still apply? Can we close this and re-open it when we run into new issues?

Yes, this is way out of date.


CASE session fails when commissioning second device in a row

Problem
When commissioning the accessory device for the first time CASE session is established fine, however after factory resetting the device and commissioning it once again with different node ID it fails on the controller side due to no memory error. The condition that fails is located in the following line: https://github.com/project-chip/connectedhomeip/blob/master/src/credentials/CHIPCert.cpp#L244
Steps to reproduce:

Commission the accessory with Python CHIP controller and some node ID (e.g. 1):

connect -ble 3840 20202021 1
zcl NetworkCommissioning AddThreadNetwork 1 0 0 operationalDataset=hex:000300000f02081111111122222222051000112233445566778899aabbccddeeff01021234 breadcrumb=0 timeoutMs=1000
zcl NetworkCommissioning EnableNetwork 1 0 0 networkID=hex:1111111122222222 breadcrumb=0 timeoutMs=1000
close-ble

Resolve IP address with resolve<PHONE_NUMBER> 1 - it will succeed.
Factory reset the device.
Commission the accessory once again with different node ID (e.g. 2):

connect -ble 3840 20202021 2
zcl NetworkCommissioning AddThreadNetwork 2 0 0 operationalDataset=hex:000300000f02081111111122222222051000112233445566778899aabbccddeeff01021234 breadcrumb=0 timeoutMs=1000
zcl NetworkCommissioning EnableNetwork 2 0 0 networkID=hex:1111111122222222 breadcrumb=0 timeoutMs=1000
close-ble

Resolve IP address with resolve<PHONE_NUMBER> 2 again - it will fail.

Logs on the accessory side:
'I: 72134 [IN]CASE Server received SigmaR1 message. Starting handshake. EC 0x20003898\r\n'
'D: 72144 [SC]Waiting for SigmaR1 msg\r\n'
'D: 72148 [SC]Received SigmaR1 msg\r\n'
'D: 72151 [SC]Peer assigned session key ID 12\r\n'
'D: 72209 [SC]Sent SigmaR2 msg\r\n'
'I: 72310 [EM]Received message of type 63 and protocolId 0 on exchange 56472\r\n'
'E: 72317 [SC]Received error (255) during CASE pairing process\r\n'
'I: 72324 [IN]CASE Session establishment failed: CHIP Error 4084 (0x00000FF4): Invalid CASE parameter\r\n'

Logs on the controller side:
[1625463797.529033][459:658] CHIP:DIS: Node ID resolved for 0x0000000000000009 to [fd11:22::7cf8:11af:95ed:a205]:11097
[1625463797.529059][459:658] CHIP:CTL: SyncSetKeyValue on PairedDevice9
Node address has been updated
[1625463797.529367][459:658] CHIP:CTL: OperationalDiscoveryComplete for device ID 9
[1625463797.529378][459:658] CHIP:CTL: Enabling CASE session establishment for the device
[1625463797.529391][459:658] CHIP:CTL: SyncSetKeyValue on PairedDevice9
[1625463797.529395][459:658] CHIP:IN: Marking old secure session for device 0x0000000000000009 as expired
[1625463797.529409][459:658] CHIP:CTL: SyncSetKeyValue on PairedDevice9
[1625463797.529415][459:658] CHIP:CTL: SyncSetKeyValue on StartKeyID
[1625463797.529698][459:658] CHIP:SC: Sent SigmaR1 msg
[1625463797.747842][459:658] CHIP:EM: Received message of type 49 and protocolId 0 on exchange 56458
[1625463797.747889][459:658] CHIP:EM: Rxd Ack; Removing MsgId:00000000 from Retrans Table
[1625463797.747901][459:658] CHIP:EM: Removed CHIP MsgId:00000000 from RetransTable
[1625463797.747929][459:658] CHIP:SC: Received SigmaR2 msg
[1625463797.747939][459:658] CHIP:SC: Peer assigned session key ID 1
[1625463797.748543][459:658] CHIP:EM: Piggybacking Ack for MsgId:00000000 with msg
[1625463797.748686][459:658] CHIP:CTL: Device connection failed. Error CHIP Error 4011 (0x00000FAB): No memory
Failed to commission: 4011

It seems that root cause of a problem is that CHIP Device Controller stores only one instance of certificates here: https://github.com/project-chip/connectedhomeip/blob/master/src/controller/CHIPDeviceController.h#L341. Maximal capacity is 3, so it can store root cert, ICA and NOC. First two of them are loaded on the controller init and third one during CASE session with accessory. After first CASE session array is full and on the new CASE session with another device there is not space for another NOC.
Proposed Solution
Store here: https://github.com/project-chip/connectedhomeip/blob/master/src/controller/CHIPDeviceController.h#L341 an array of objects with size equal to the number of paired devices instead of single object?

@kkasperczyk-no, thank you for the detailed analysis and the logs.
I think the main issue is that we are loading the peer's operational cert in the local credentials set to validate it. We should update the validation code to not load the peer's cert in the local set (so that the local credentials are not mutated with each CASE session).
Each device (including controllers) will have one set of credentials per fabric. So a controller should have only one of these (per fabric) to communicate with any number of peer devices (on the same fabric).
cc: @jpk233

@kkasperczyk-no, thank you for the detailed analysis and the logs.
I think the main issue is that we are loading the peer's operational cert in the local credentials set to validate it. We should update the validation code to not load the peer's cert in the local set (so that the local credentials are not mutated with each CASE session).
Each device (including controllers) will have one set of credentials per fabric. So a controller should have only one of these (per fabric) to communicate with any number of peer devices (on the same fabric).
cc: @jpk233

I agree with this, and after testing this solution it seems to resolve the issue. Will roll the fix into our open CASE changes.

@jpk233 , it'll make it harder to support concurrent CASE session setups in future.

@jpk233 , it'll make it harder to support concurrent CASE session setups in future.

Filed https://github.com/project-chip/connectedhomeip/issues/8342 to track this.

The cost of loading necessary credentials (in time), versus the cost of keeping them in memory (in space) is mis-balanced.
Loading a cert is somewhat "costly" (but not egregiously so), in comparison with keeping the decoded certs in memory for the entire duration of a session establishment.
Overall, the operational credentials are used in a single message handling step.
Here are the messages and their use of credentials:

Sending Sigma1: requires access to root public key from root cert. Could argue for separately caching root public keys away from root certs, after validation of install of a root.
Processing Sigma1: requires access to all root public keys and the fabric+node IDs of each NOC. Again, this is data that could have been pre-cached at NOC install in a "secondary" way, since a fabric+node ID is 128 bits total
Sending Sigma2: requires sending NOC/ICAC array for only current NOC, and signing with NOC's operational private key (i.e. does not require loading certs for the NOC). The NOC/ICAC data can be copied as is without actually parsing anything.
Processing Sigma2: requires validating NOC/ICAC/RCAC chain. This is the only time a full validation is needed. The NOC and ICAC are actually already in memory in the incoming message, so there is only need to load the RCAC cert (unless you assume it's prevalidated, which it is, then it's not needed to actually load it as long as the root public key is available to validate the ICAC
Sending Sigma3/Processing Sigma3: same as for Sigma2 in terms of cert access, but reverse roles of which peer has to validate.

Overall, the lifetime requirement of access for NOC chain is a single message processing or construction step, and the rest only needs access to the root public key of the shared fabric determined at Sigma1. I would recommend refactoring CASESession.cpp to only load the needed certificates at the right time, and also to consider caching some metadata about the installed certificates so that if only one item (e.g. root public key) is needed, it can be more easily looked-up than having the load the "certificate sets".
The current methodology of access will not scale to large numbers of fabrics for multi-admin, even if single CASE session is allowed at one time.


Custom Grammars - Where to Start

I'm using AvaloniaEdit and am using it as a replacement for a WPF RichTextBox I was using in a custom control.
Look at the AE docs it says I need to implement IRegistryOptions but I can't find any examples of what any of the requirements are for doing so. This is all pretty complex stuff and I can't find anything to give me a nudge in the right direction.
I found a message saying to look at the implementation for AvaloniaEdit but the link is now a 404 and looking over all the branches it seems to have vanished.
My requirements are really simple.
I just have a handful of key words to be green and a handful of keywords to be Red but I just cannot figure out what to do with the interface. It all seems geared up for a much more complex use case and I'm left struggling a bit to be honest.
Are there any docs I'm missing or examples?

I don't think TextmateSharp is the piece you should use for that. I'd use AvaloniaEdit's transformers for that.
Basically you need to write a line transformer that just change the chunk style when you find a match in your line.
You can find a custom transformer here: https://github.com/AvaloniaUI/AvaloniaEdit/blob/master/src/AvaloniaEdit.TextMate/GenericLineTransformer.cs


2 issues when running games in fullscreen mode (lesser fps and some random drops)

Hi!
I noticed these 2 issues when running Wine games in fullscreen mode.
Notice that this happened just with certain Wine games and regardless of the Wine patch used (vanilla or Staging or Gallium Nine) and it appeared a month ago or so.
No native game had this issue but I didn't play many of them lately.
I recorded 4 videos that should explain the situation (I tried 2 games):
· The 1st one is PES 2013 running with Wine Gallium Nine.
The video is quite long but I put a timeline in the description to easily check the issues.
At first the game suffers some random fps drops that once appear they somehow enter in a constant loop, by pressing Alt+Enter I was able to exit the fullscreen and the issue disappeared.
Then I found out that in general the performances are slightly worst when playing fullscreen, if you compare the Gallium Hud when I switch the two mode you'll see that it's way more stable when windowed.
· The 2nd video is Stronghold Crusader II running with vanilla Wine.
After a few seconds it can bee seen that the "drop loop" kicks in and the fps start to regularly drop, it also suffer some lower fps at this point.
Once windowed the loop goes away and the fps are becoming more stable, then when switching back to fullscreen the issue doesn't appear anymore but IMO it would've if I played more.
· The 3rd video is PES 2013 running without any Window Manager (I just had some xterm in the .xinitrc)
The game suffer no issues when fullscreen and the performances are similar to the 1st video when running windowed, switching to windowed with Alt+Enter makes no difference here.
· The 4th video is Stronghold Crusader II running without any Window Manager (I just had some xterm in the .xinitrc)
Same as above, the loop never appear and the performances are the same whether is fullscreen or windowed.
So at the end:
Some Wine games suffer some lesser stability and this strange "drop loop" when running fullscreen on JWM; no problems if windowed or without JWM.
Unfortunately I had no time to test another WM, I'll if needed.
Hope this post was helpful, my specs are:
Arch Linux (all testing repos activated)
Mesa-git (from this repo)
Wine-Gaming-Nine from the AUR
R9 380
Xeon e3-1245

Hi, what version of JWM are you running, and what packages were updated a month ago when you began to notice this problem.
As you may realize this could be any number of things, and probably not related to JWM itself.
You might try rolling back to the package versions you previously had to see which package is causing the issue.
Did you update JWM at some point and notice it then? (Are you running the latest git?)
Did you notice it after other packages were updated?

Hi!
I was running 2.3.6 yesterday when I recorded those videos and today I installed the git version (through AUR) and the same issue appears on 2.3.7
I noticed this issue some time ago but then I thought it was just that specific game (F.E.A.R. 2) and I didn't really check out what was creating it.
Anyway i tried out some other WM (twm, ratpoison) and PES runs fine at fullscreen there, no issue at all.
I'll try to downgrade later to see if I'm able to avoid this issue.


rewrite actor profile ingestion to use commit cids

Oh - adding a test to the ingester package for this would be lovely 😓


CodeClimate badges for private repos

Thanks for the great work all.
Has anyone has been able to get shields' CodeClimate badges working for private repos? I've tried a couple different ways to config the URL, but none work. I know CC has their own badges, but I'm not a fan of them and want all the badges I have to match, style-wise.

Hello @gretzky ,
Even though I have never actually used CodeClimate, I recently rewrote all the badges relating to this service (see #1387 and #1368), so I may be able to shed some light on the issue and possibly work on a solution. The API documentation mentions that a token should be provided for authenticated calls. I'm guessing that doing so would probably allow to retrieve the relevant data from private repositories. With the current implementation, Shield's CodeClimate badges do not support providing a token, hence why all your attempts have failed so far.
Some other services such as CircleCI or CodeCov seem to have an optional token parameter that can be inserted in the badge's URL, I'm guessing we could add similar support for CodeClimate. We would need to have a look at what CodeClimate's token model is and how finely you can tune the token settings, as we wouldn't want sensitive information to be accessible by anyone looking at the badge's URL. :wink:
Cheers,
Pyves

Hey @PyvesB, thanks for the response. I found the CircleCI implementation, which is what I started digging into. I'd be happy to do some more further digging-- I'll make a fork and see if I can pull anything off.

Passing secrets to the shields server is not a great idea. While we try to keep things secure, we don't guarantee it, and would like not to put other people's data at risk. The circle handling is an anomaly. Is is possible we could accomplish this use case through self-hosting, as we do for github?


add support for gpt-4-vision

I didn't know where to put the IMAGE_EXTENSIONS var so just hard coded it for now
The vision model isn't happy if max_tokens isn't set (it was truncating the response) so I hardcoded it in sendchat, I expect we can remove this when it moves out of preview.
I added a dependency on Pillow to requirements.in to get the image dimensions
Work left to do

[x] figure out where to put the IMAGE_EXTENSIONS var
[x] update docs

The test for whether someone has access to the vision-preview model is a bit of a cludge - when it moves out of beta and folks on azure and openrouter get access to it we should do something a bit nicer. I'm thinking have the model keep track of the available models and we can just ask it if it supports the vision one.


Add z index comp

Objects on the same layer cann be ordered with z(value: number) comp.
Closes #167

Looks good, thanks!


pessimistic-txn: support lock wait timeout (#5680)

What have you changed?
Cherry pick #5680

/run-all-tests

@MyonKeminta @sticnarf @AndreMouche PTAL

/run-all-tests

@MyonKeminta @AndreMouche PTAL. I have added it to release note and https://github.com/pingcap/tidb/pull/13165 is merging.

LGTM

@MyonKeminta @AndreMouche PTAL. Thanks!


[docs] Embed more examples into the README

The TLS cert generation should be more opinionated, in an effort to make it clearer to users up-front.

[x] Show an example of the CertificateSigningRequest (from /examples) in the README itself
[x] Make the "get the k8s cluster CA cert" step more obvious
[x] Ensure that the reader adds this value to .caBundle

Can also consider using https://github.com/campoy/embedmd as a CI step to keep the examples up-to-date.

Closed in #10.


Deploy in Lark

Deploy in Lark

Linked to issue #896

Changes made as suggested :)

@vasvi-sood and @abhishek-iiit pls make the required changes so that we can proceed towards the merge

- docusaurus/static/img/docs/howto/IM_platform/deploy-lark.webp
+ docusaurus/static/img/docs/howto/deploy-lark/deploy-lark.webp

Thank you for the feedback. Changes made as suggested :)

Please rename docusaurus/static/img/docs/howto/IM_platform/deploy-lark.webp to docusaurus/static/img/docs/howto/deploy-lark/deploy-lark.webp

I added the changes as suggested previously. will delete the IM_platform folder at the end of the merging of all PR :)

ping @lijiarui

ping @lijiarui


Rule creation with YAML

Possibilidade de criar rules em formato yaml e compartilhar com a comunidade:
Senhas.yaml
CPF.yaml
Biofac.yaml

@teixeira0xfffff Can you, please, provide additional informations like reference about what to be inside the YAML file (Example or Github YAML file reference) to inspirate the design?


Im having a trojan virus warning

Dont know if thats an error but my antivirus says its a trojan, should i just whitelist it and ignore it?

It's open source. If you can't read the code and think it's untrustworthy then don't install it. Up to your instincts bro

please check already closed issues about "virus".


Perform an audit of the ibm.com Library for the Arabic development

User Story

As a [user role below]:
DDS Development Lead / Architect

I need to:
understand the scope of the work required to render Arabic web pages properly

so that I can:
properly instruct the scrum master and developers regarding the work involved

Additional information

The design research will inform the work for this issue.  (#1638)
{{user insights}}
{{user metrics}}

Acceptance criteria

[ ] List of the changes required to each component and pattern to support Arabic web pages
[ ] {{State another}}
[ ] {{And another}}

Re-opening since closed by stalebot.  Still need this audit. Who should conduct audit? Design? Dev? BA?@RobertaJHahn @jeffchew @wonilsuhibm

@ljcarot Included in our Leadership meeting agenda.  Might need to talk about priorities.  Design resources are booked in the current sprint.

Next step:  Linda to send the RTL storybook link to Amid for his review.

Let's keep this one open, but figure out next steps on our testing on this @ljcarot @wonilsuhibm @RobertaJHahn .

Created a calendar reminder for Jan 7, 2021 to include the planning in the Leadership meeting agenda.


Handle common prefixes in variant alleles

Signed-off-by: Angelica Ochoa<EMAIL_ADDRESS>

Just based on the variants Tom had shared in issue #34 I noticed there were common prefixes that the standardization script didnt resolve so the script handles that now. I'm not sure if it will resolve all of the issues reported in #34 but it will at least address some

Nice this solve my issue #30 as well - Thank you!


gtk.ApplicationWindow.glib.toGObject is ambiguous

I am unable to type assert IObject returned from gtk.Builder to gtk.ApplicationWindow
Here is short snippet:
package main

import (
	"log"
	"os"

	"github.com/gotk3/gotk3/gtk"
)

const template string = "<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated with glade 3.20.3 -->
<interface>
  <requires lib="gtk+" version="3.20"/>
  <object class="GtkApplicationWindow" id="Window"/>
</interface>
"

func main() {
	gtk.Init(&os.Args)

	if builder, err := gtk.BuilderNew(); err != nil {
		log.Fatal(err)
	} else if err := builder.AddFromString(template); err != nil {
		log.Fatal(err)
	} else if winObj, err := builder.GetObject("Window"); err != nil {
		log.Fatal(err)
	} else {
		window := winObj.(*gtk.ApplicationWindow)
		window.ShowAll()
	}

	gtk.Main()
}

Which outputs:
# command-line-arguments
./main.go:28:19: gtk.ApplicationWindow.glib.toGObject is ambiguous
./main.go:28:19: impossible type assertion:
	*gtk.ApplicationWindow does not implement glib.IObject (missing glib.toGObject method)

From definition of ApplicationWindow in  application_window.go, you can see why:
// ApplicationWindow is a representation of GTK's GtkApplicationWindow.
type ApplicationWindow struct {
	Window

	// Interfaces
	glib.ActionMap
	glib.ActionGroup
}

All of Window, glib.ActionMap and glib.ActionGroup implements IObject interface, but there is no default toGObject method defined on the Application window, which causes ambiguity.
Fix1: Added missing inline code for better readibility.

This is related to #232


SubQuery?

Hi,
How I can create subQuery with your framework or can I create subquery with this?
Thank you.

Hi, can you explain more detail what you need or provide example?

On 20 Mar 2019, at 17:50, Hasan Gedik<EMAIL_ADDRESS>wrote:
Hi,
How I can create subQuery with your framework or can I create subquery with this?
Thank you.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Hi,
this is my QueryBuilder:
_sqlbuilder = new QueryBuilder("dbo.Category", new[] { "Id" }, "Id", "Level", "Code", "Title", "Year", "ParentId", "CreatedDate", "CreatedBy", "ChangedDate", "ChangedBy");
I need this sql result:
  SELECT * FROM   dbo.Category c WHERE c.Id IN (   SELECT t1.ParentId FROM dbo.Category t1    LEFT JOIN dbo.Category ON dbo.Category.Id = t1.ParentId    LEFT JOIN dbo.Cpi AS k1 ON k1.CategoryId = t1.Id    WHERE t1.[Archive] = 0 AND t1.[Code] NOT IN ('tt','yy')    AND [k1].[Department] IN ('xxx')   )
But I don't know how I can create this query with queryDesigner.

This library making only filter for incoming query. It cannot build queries, just specify where and orderby, sorry.20 мар. 2019 г. 20:51 пользователь Hasan Gedik<EMAIL_ADDRESS>написал:Hi,
this is my QueryBuilder:
_sqlbuilder = new QueryBuilder("dbo.Category", new[] { "Id" }, "Id", "Level", "Code", "Title", "Year", "ParentId", "CreatedDate", "CreatedBy", "ChangedDate", "ChangedBy");
I need this sql result:
SELECT * FROM dbo.Category c WHERE c.Id IN ( SELECT t1.ParentId FROM dbo.Category t1  LEFT JOIN dbo.Category ON dbo.Category.Id = t1.ParentId  LEFT JOIN dbo.Cpi AS k1 ON k1.CategoryId = t1.Id  WHERE t1.[Archive] = 0 AND t1.[Code] NOT IN ('tt','yy')  AND [k1].[Department] IN ('xxx') )
But I don't know how I can create this query with queryDesigner.
—You are receiving this because you commented.Reply to this email directly, view it on GitHub, or mute the thread.