Confusing features in dataset returned by get_torch_loader

I'm trying to use the dataloaders returned by pinder.core.loader.dataset.get_torch_loader for all-atom representations of the protein complexes. When I iterate over the keys present in a sample from one of these datasets, I get:
from pinder.core.loader.dataset import PinderDataset, get_torch_loader
train, val = [get_torch_loader(PinderDataset(split=split)) for split in ["train", "val"]]
for key in train.dataset[0].keys():
    print(key, type(train.dataset[0][key]))
    if type(train.dataset[0][key]) == dict:
        for key2 in train.dataset[0][key].keys():
            print("    ", key2, type(train.dataset[0][key][key2]), train.dataset[0][key][key2].shape)

### ------- Output ------- ###

target_complex <class 'dict'>
     atom_types <class 'torch.Tensor'> torch.Size([2556, 12])
     residue_types <class 'torch.Tensor'> torch.Size([2556, 1])
     atom_coordinates <class 'torch.Tensor'> torch.Size([2556, 3])
     residue_coordinates <class 'torch.Tensor'> torch.Size([2556, 3])
     residue_ids <class 'torch.Tensor'> torch.Size([2556])
     chain_ids <class 'torch.Tensor'> torch.Size([2556])
feature_complex <class 'dict'>
     atom_types <class 'torch.Tensor'> torch.Size([2556, 12])
     residue_types <class 'torch.Tensor'> torch.Size([2556, 1])
     atom_coordinates <class 'torch.Tensor'> torch.Size([2556, 3])
     residue_coordinates <class 'torch.Tensor'> torch.Size([2556, 3])
     residue_ids <class 'torch.Tensor'> torch.Size([2556])
     chain_ids <class 'torch.Tensor'> torch.Size([2556])
id <class 'str'>
sample_id <class 'str'>
target_id <class 'str'>

I have the following questions:
What is the difference between atom_coordinates and residue_coordinates?
For at least the first 10 examples in the train dataset, I find that
for i in range(10):
    print((train.dataset[i]['feature_complex']['residue_coordinates'] == train.dataset[i]['feature_complex']['atom_coordinates']).all())

returns True.
Can the loader be modified to also return atom name information?
The atom_types tensor provides only a one-hot encoding of element type, for example, running
train.dataset[0]['target_complex']['atom_types'].unique(dim=0)

returns
tensor([[0., 0., 0., 0., 1., 0., 0., 0., 0., 0., 0., 0.],
        [0., 0., 0., 1., 0., 0., 0., 0., 0., 0., 0., 0.],
        [0., 0., 1., 0., 0., 0., 0., 0., 0., 0., 0., 0.],
        [1., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0., 0.]])

This is confusing when compared to the Structure class, in which atom_name is encoded as elements of constants.BB_ATOMS and constants.SC_ATOMS (e.g. 'N', 'CA', 'C', 'O', 'CB', 'CG', etc.).
It would be useful/less confusing if the dataloader returned by get_torch_loader contained information that corresponded more closely to the data provided in the Structure class.

Hi @eswan01, thanks for the feedback on the example transform implementation. I agree that it would make sense to rename the misleading atom_types key to reflect that its actually encodings of elements and not atom types and also introduce an atom type encoding.
Regarding your first question

What is the difference between atom_coordinates and residue_coordinates?

In the PinderDataset (torch dataset), there is no difference. It appears this was an oversight when hijacking the existing transform that was targeting the torch-geometric dataset. In the torch-geometric dataset, the difference is that residue_coordinates tracks only the C-alpha atom coordinates (one per residue) and atom_coordinates tracks all-atom. Note the receptor.filter("atom_name", mask=["CA"]) below:
https://github.com/pinder-org/pinder/blob/bb62635bcb4186cf4f45696fc3da5082bb899f0a/src/pinder-core/pinder/core/loader/geodata.py#L118-L133
That structure2tensor function really just serves as an example transform for how one could go from Structure instances to Tensor-encoded data items. In the PinderDataset implementation, the default  torch-API transform defined is the structure2tensor_transform which essentially just wraps the structure2tensor method such that it accepts a Structure as input and returns a dict of tensors.
https://github.com/pinder-org/pinder/blob/bb62635bcb4186cf4f45696fc3da5082bb899f0a/src/pinder-core/pinder/core/loader/dataset.py#L238-L254
As you can see below, the current version uses all-atom coordinates for both residue_coordinates and atom_coordinates (the oversight):
https://github.com/pinder-org/pinder/blob/bb62635bcb4186cf4f45696fc3da5082bb899f0a/src/pinder-core/pinder/core/loader/dataset.py#L54-L63
I will push a fix to that default transform shortly 👍
Regarding the second question

Can the loader be modified to also return atom name information?

As I alluded to above, we can definitely adjust the info being returned by the default transform as you suggested. I will try to include that in the upcoming patch for the residue_coordinates bug.
That being said, the short answer to

Can the loader be modified to also return atom name information?
It would be useful/less confusing if the dataloader returned by get_torch_loader contained information that corresponded more closely to the data provided in the Structure class.

Absolutely! You can define whatever transform you desire, that's why the PinderLoader default return value of __getitem__ contains a tuple of (PinderSystem, Structure(<feature complex>), Structure(<target complex>))
https://github.com/pinder-org/pinder/blob/bb62635bcb4186cf4f45696fc3da5082bb899f0a/src/pinder-core/pinder/core/loader/dataset.py#L293-L299
You can specify your own transform and target_transform to apply to the feature_complex Structure and target_complex Structure. This closely follows the transform/target_transform concepts from the torch datasets + dataloader tutorial: https://pytorch.org/tutorials/beginner/basics/data_tutorial.html#creating-a-custom-dataset-for-your-files


Save the settings on the generator page

I see two options

via localstorage(when available)
Load settings via URL

You could also consider loading/downloading a settings file. Maybe in JSON.

Not a bad idea, but I think we kinda do have a standardised export format already(the URL we give the user) - don't you think that's already a very copy/pasteable format for settings?
Heck, for loading it would probably be relatively easy to just have a text field to paste a URL into, strip the part up until the ? and load the rest of it into the form, right?

Reminder for myself: This, but also a conversion for v0.1.x to v0.2.x before the code for #24 is released.


nom 5.0.1 update

Please consider updating nom to nom 5 series. It's been stable since Jun 24 and, since this is a significant shift in idioms, nom 4 support available now is only useful for people who are still writing code in nom 4 without migrating to nom 5.

nom is not one of the top 100 crates and is only included on the playground because it's a dependency for some other crate:
nom v4.2.3
└── weedle v0.10.0
    └── wasm-bindgen-webidl v0.2.51
        [build-dependencies]
        └── web-sys v0.3.28

As such, we only build the version of nom that is required. It's only exposed because we had to build it anyway. If you'd like the current version of nom to be present, you will need to either

Change weedle (and any requisite upstream users) to upgrade to nom5
Petition the Rust cookbook to include nom


error upgrading from 11.2.3 to 11.2.10

I wish I no longer have to see these error and manually fix them with my hand, in this case I am at a lost what has failed.
$ ng update @angular/cli @angular/core
Using package manager: 'npm'
Collecting installed dependencies...
Found 33 dependencies.
Fetching dependency metadata from registry...
Updating package.json with dependency @angular-devkit/build-angular @ "0.1102.10" (was "0.1102.3")...
Updating package.json with dependency @angular/cli @ "11.2.10" (was "11.2.3")...
Updating package.json with dependency @angular/compiler-cli @ "11.2.11" (was "11.2.4")...
Updating package.json with dependency @angular/animations @ "11.2.11" (was "11.2.4")...
Updating package.json with dependency @angular/common @ "11.2.11" (was "11.2.4")...
Updating package.json with dependency @angular/compiler @ "11.2.11" (was "11.2.4")...
Updating package.json with dependency @angular/core @ "11.2.11" (was "11.2.4")...
Updating package.json with dependency @angular/forms @ "11.2.11" (was "11.2.4")...
Updating package.json with dependency @angular/platform-browser @ "11.2.11" (was "11.2.4")...
Updating package.json with dependency @angular/platform-browser-dynamic @ "11.2.11" (was "11.2.4")...
Updating package.json with dependency @angular/router @ "11.2.11" (was "11.2.4")...
UPDATE package.json (1365 bytes)
⠸ Installing packages (npm)...npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/@angular-devkit/build-angular
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Conflicting peer dependency<EMAIL_ADDRESS>npm ERR! node_modules/@angular/localize
npm ERR!   peerOptional<EMAIL_ADDRESS>|| ^11.2.0-next" from<EMAIL_ADDRESS>npm ERR!   node_modules/@angular-devkit/build-angular
npm ERR!     dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See /home/yadav/.npm/eresolve-report.txt for a full report.
npm ERR! A complete log of this run can be found in:
npm ERR!     /home/yadav/.npm/_logs/2021-04-27T00_06_41_340Z-debug.log
✖ Package install failed, see above.
✖ Migration failed. See above for further details.

Duplicate of https://github.com/angular/angular-cli/issues/20375
Unfortunately, this is a defect in NPM 7.


Template Error on Imported Components with Bad Definitions

Hi, I'm using Telerik Kendo for Vue and they don't yet have correct type definitions for Vue3.
So this import:
import { Button as KButton } from '@progress/kendo-vue-buttons'

Results in a type of KButton: any  which is fine, that doesn't bother me.
But the template shows the tags Red as an error.  Any way to stop this?

Thank you!!


adding my medium profile

Hi! Your email address for this change doesn't match the email that signed the CLA. You can either add your new email address to the CLA or rebase your commits with your correct email address. Please feel free to reopen this PR if you doe either of those things.

Hi there!
I crosschecked the email address on my CLA and it tallies with the email I used to make the change.
<EMAIL_ADDRESS>find a snapshot of my CLA webpage below and please let me know what to do to fix it

You can see the other email address that was used here: https://github.com/google/season-of-docs/pull/731/checks


status checks: split "stats" out into separate, external, "clamd.extended" check

...so that a pause, possibly caused by the "stats" call, doesn't cause a healthcheck to fail.
https://trello.com/c/a1HWW3Bd/550-antivirus-api-crashes
The output of this is now a little ugly, having "clamd" and "clamd.extended" sections, but short of modifying the utils to be able to do deep merges, and seeing as this might not have any effect anyway, this is probably the most effective thing to do for now.
I note, looking at the "stats", that scraping these through prometheus might be an interesting experiment.

So, if I understand this right, the client.stats() check will now only be run if ?ignore_dependencies is false/not supplied?

Yes. I particularly like the symmetry/asymmetry of having both status and stats floating around here.


Windows: moya runserver runs but raises exception

Here's the traceback:
Traceback (most recent call last):
  File "C:\Users\Konstantin\appdata\local\scoop\apps\python\3.4.2\Lib\threading.py", line 921, in _bootstrap_inner
    self.run()
  File "C:\Users\Konstantin\Projects\moya\lib\site-packages\fs\osfs\watch_win32.py", line 353, in run
    self._iocp = CreateIoCompletionPort(INVALID_HANDLE_VALUE,None,0,1)
  File "C:\Users\Konstantin\Projects\moya\lib\site-packages\fs\osfs\watch_win32.py", line 72, in _errcheck_handle
    raise ctypes.WinError()
OSError: [WinError 6] The handle is invalid.```

**Important**: The server site still runs OK despite this message.

That's the auto-reload thread. I can't reproduce that on my Windows 7 machine. What version of Windows are you running?

I'm on Windows 10 Tech Preview with Python 3. Windows 10 should behave similarly to Windows 8.1 though.

I've made some changes that may fix this. Although I still don't have WIndows 10 here, but it works on Windows 7/8. Would you mind testing again?

Hi! The warning is no more there, thanks!
BTW, Moya is a total kickass. Unfortunately, I hadn't had much time experimenting with it, but what I've seen is fantastic.

Good to know, thanks! Let me know if you have any questions.


Clarifying cli usage for converting directories

Fixes #56
Added
# Usage: svgr [-d out-dir] [src-dir]

before the example

@wuweiweiwu thanks!

No problem! :)


Adds a category for tests using splittable DoFn

Excludes the category in all runners except direct.

R: @kennknowles

CC: @tweise @aljoscha @mxm @amitsela just noting for runner authors this other category that has been added and excluded.


userAgent: Rename SetUserAgent to SetAppInfo.

remove racy style boolean variable verification, use sync.Once
to SetAppInfo only once.
SetpAppInfo now part of API rather than Config just like other libraries.

Fixes #242

looks fine.

looks fine.

Great.. merging.


consider contribution to nixos-aarch64 image

Hi, thanks for that repo, this is really awesome, and thanks for the prebuild image!
I was wondering if it would be possible to upstream that build into https://github.com/Mic92/nixos-aarch64-images though I must admit that my knowledge about this stuff is very limited, so it may be as well not a good idea.

Part of the stated goal of that repo is to be able to be built on non-aarch64 platforms, and as the current state of the BPi-R3 requires a custom kernel configuration as well as a devicetree overlay (for the SD card) applied we can't modify the generic upstream aarch64 image and get a working image from that.
I'm going to refrain from attempting to add support for this target there as it would be at odds with the stated goals of that repo.
I also would need to work out a way to get the mt7986-default-bootcmd.patch into a state that it can be submitted for review upstream.  The patch currently is an ugly hack at best and I expect it's fairly brittle.  Once in an acceptable state, even if it's not something upstream u-boot wants to support it would at least be in a state where I would be okay proposing to including it into nixpkgs.
The disabling of FDT reallocation by setting FDT_HIGH="0xffffffffffffffff" is, at the very least, unacceptable.  It was me essentially throwing in the towel after trying to get it to boot the right way for 16 hours.

Understood, thank you for taking your time to write such an insightful answer, it helps me to understand all the nuances better.


"Unknown mode: [Electric/Gas  ]" error - new generation WH or consolidation of electric/gas modes?

I've been setting up the Econet integration for the first time in HA and immediately observed an error in the logs about an unknown mode:
Logger: pyeconet.equipment.water_heater
Source: /usr/lib/python3.9/site-packages/pyeconet/equipment/water_heater.py:60
First occurred: 4:15:09 PM (727 occurrences)
Last logged: 9:14:37 PM

Unknown mode: [Electric/Gas ]

Context: My Water Heater was warranty-swapped with a new unit ~1 week ago. The old (Installed August '21) had an "electric" mode available, not "Electric/Gas." I hadn't noticed before this error, but the app does indeed have an "Electric/Gas" mode listed (with no icon) where the "Electric" mode used to live.
Has anyone else seen a similar change/error? I don't know which generation my prior model was, but this new one describes itself as heatpumpWaterHeaterGen5, which is newer than what I saw in the API response examples.
Does anyone else have a gen5 unit yet? Is anyone with gen4 or older seeing an electric/gas mode appear?
get_locations response:
{
  "results": {
    "locations": [
      {
        "@AWAY": false,
        "@AWAYCONFIG": false,
        "@LOCATION_INFO": "XXX, XXX",
        "@LOCATION_NAME": "Home",
        "@LOCATION_STATUS": "I'm Home",
        "@VACATION": false,
        "@VACATIONCONFIG": false,
        "@WEATHER": "51°",
        "@WEATHER_F": 51,
        "@WEATHER_I": "clearn.png",
        "equiptments": [
          {
            "@ACTIVE": true,
            "@ALERTCOUNT": 0,
            "@AWAY": false,
            "@AWAYCONFIG": false,
            "@AWAY_MSG": "",
            "@BCONFIG": [
              {
                "align": "center",
                "name": "@SCHEDULESTATUS",
                "type": "TEXT_LABEL_VIEW",
                "value": ""
              },
              {
                "name": "@SCHEDULERESUME",
                "title": "Resume",
                "type": "BUTTON_VIEW",
                "value": ""
              },
              {
                "align": "center",
                "type": "TEXT_LABEL_VIEW",
                "value": "Hot Water Availability"
              },
              {
                "align": "center",
                "name": "@HOTWATER",
                "title": "Hot Water Availability",
                "type": "SINGLE_IMAGE_VIEW",
                "value": "ic_tank_hundread_percent_v2.png"
              }
            ],
            "@COMBUSTION": {
              "constraints": {
                "formatDecimal": 1,
                "green": 55,
                "lowerLimit": 0,
                "orange": 25,
                "red": 20,
                "units": "HRS",
                "upperLimit": 10000000
              },
              "status": "Compressor life is normal",
              "value": 100
            },
            "@CONFIG": [
              {
                "align": "center",
                "name": "@MODECONFIG",
                "title": "This Equipment should be set to ENERGY SAVING Mode for maximum efficiency",
                "type": "IMAGE_TEXT_BUTTON_VIEW",
                "value": {
                  "constraints": {
                    "bgcolor": "#008000",
                    "enumText": [
                      "Off           ",
                      "Energy Saver  ",
                      "Heat Pump     ",
                      "High Demand   ",
                      "Electric/Gas  ",
                      "Vacation      "
                    ],
                    "enumTextIcon": [],
                    "fontcolor": "#FFFFFF",
                    "icon": "ic_energy_saver",
                    "lowerLimit": 0,
                    "upperLimit": 5
                  },
                  "status": "Enable",
                  "value": 1
                }
              }
            ],
            "@CONNECTED": true,
            "@DRACTIVE": {
              "constraints": {
                "dialog": [
                  {
                    "message": "This should not impact the water temperature in your home. Do you want to opt out for this event ?",
                    "title": "Tank temperature has been changed in response to a Utility Load Control event",
                    "value": 1
                  }
                ]
              },
              "value": ""
            },
            "@DRESOVER": {
              "constraints": {
                "enumText": ["false", "true "],
                "enumTextIcon": [],
                "lowerLimit": 0,
                "upperLimit": 1
              },
              "status": "false",
              "value": 0
            },
            "@ENABLED": {
              "constraints": {
                "enumText": ["Disabled", "Enabled "],
                "enumTextIcon": ["ic_device_off.png", "ic_enabled.png"],
                "lowerLimit": 0,
                "upperLimit": 1
              },
              "status": "Enabled ",
              "value": 1
            },
            "@HOTWATER": "ic_tank_hundread_percent_v2.png",
            "@JA13STATUS": "",
            "@LEAKINSTALLED": {
              "constraints": {
                "align": "center",
                "bgcolor": "#bec2bf",
                "enumText": ["No ", "Yes"],
                "enumTextIcon": [],
                "fontcolor": "#000000",
                "lowerLimit": 0,
                "upperLimit": 1
              },
              "status": "",
              "title": "Leak sensor not installed",
              "value": 0
            },
            "@MODE": {
              "constraints": {
                "enumText": [
                  "Off           ",
                  "Energy Saver  ",
                  "Heat Pump     ",
                  "High Demand   ",
                  "Electric/Gas  ",
                  "Vacation      "
                ],
                "enumTextIcon": [
                  "ic_device_off.png",
                  "ic_energy_saver.png",
                  "ic_heat_pump.png",
                  "ic_high_demand.png",
                  "http://heaticon.png",
                  "ic_vacation.png"
                ],
                "lowerLimit": 0,
                "upperLimit": 5
              },
              "status": "High Demand   ",
              "value": 3
            },
            "@MODECONFIG": {
              "constraints": {
                "bgcolor": "#008000",
                "enumText": [
                  "Off           ",
                  "Energy Saver  ",
                  "Heat Pump     ",
                  "High Demand   ",
                  "Electric/Gas  ",
                  "Vacation      "
                ],
                "enumTextIcon": [],
                "fontcolor": "#FFFFFF",
                "icon": "ic_energy_saver",
                "lowerLimit": 0,
                "upperLimit": 5
              },
              "status": "Enable",
              "value": 1
            },
            "@MODEIMAGE": "",
            "@NAME": {
              "constraints": {
                "stringLength": 64
              },
              "value": "Heat Pump Water Heater"
            },
            "@OVERRIDE": {
              "constraints": {
                "bgcolor": "#FFFF00",
                "fontcolor": "#000000",
                "icon": "ic_high_level_alert.png"
              },
              "status": "",
              "value": ""
            },
            "@OVERRIDESTATUS": "",
            "@RESUME": false,
            "@RUNNING": "Compressor Running",
            "@SCHEDULE": false,
            "@SCHEDULERESUME": "",
            "@SCHEDULESTATUS": "",
            "@SETPOINT": {
              "constraints": {
                "error": [],
                "formatDecimal": 0,
                "isConversion": true,
                "lowerLimit": 110,
                "units": "deg F",
                "upperLimit": 140,
                "warning": [
                  {
                    "message": "CAUTION HOT WATER. Contact may cause serious burns to skin",
                    "value": 121
                  }
                ]
              },
              "value": 120
            },
            "@STATUS": "Enabled ",
            "@TANK": {
              "constraints": {
                "green": 40,
                "orange": 30,
                "red": 30
              },
              "status": "Element operating normally",
              "value": 100
            },
            "@TCONFIG": [
              {
                "align": "center",
                "name": "@MODEIMAGE",
                "type": "SINGLE_IMAGE_VIEW",
                "value": ""
              },
              {
                "align": "center",
                "name": "@RUNNING",
                "type": "TEXT_LABEL_VIEW",
                "value": "Compressor Running"
              },
              {
                "align": "center",
                "name": "@OVERRIDESTATUS",
                "type": "TEXT_LABEL_VIEW",
                "value": ""
              }
            ],
            "@TYPE": "heatpumpWaterHeaterGen5",
            "@VACATION": false,
            "@VALVE": {
              "constraints": {
                "dialog": [
                  {
                    "message": "Closing the shut off valve will disable the water heater",
                    "title": "Closing Valve",
                    "value": 0
                  }
                ],
                "error": []
              },
              "value": ""
            },
            "@VALVESTATUS": {
              "constraints": {
                "align": "center",
                "bgcolor": "#bec2bf",
                "fontcolor": "#000000"
              },
              "status": "",
              "title": "Shut-OFF Valve not installed",
              "value": 1
            },
            "actions": [
              "waterheaterScheduleView",
              "networkSettings",
              "waterheaterUsageReportView",
              "waterheaterHealthView"
            ],
            "device_name": "",
            "device_type": "WH",
            "mac_address": "",
            "serial_number": ""
          }
        ],
        "location_id": ""
      }
    ]
  },
  "success": true,
  "logs": "",
  "stack": ""
}

@rborkow thanks for the details. Noticed in the HA issue you mentioned you were able to "fix" it by update pyeconet. Do you mode opening a PR with the fix? If you can't I can try to get to this, but things are a little crazy for me at the moment.

@w1ll1am23 Yes, I'll open a PR soon as I can!

Just installed a newer water heater and was wondering why the data flowing to HA was so lossy until I saw this error in the logs. Thanks for the fix @rborkow! Would love to see this merged.

@powdahound Merged, and bumped in HA core - Hoping the update makes it into 2022.2.9

@rborkow Thank you! 🤞

@rborkow I'm using a HPWH from Rheem, and while I'm not seeing errors from pyeconet, it appears the home assistant integration is not totally functional, as I cannot set my water heater to "Electric/Gas" mode from the HA control.
From that integration I see the following:

But in my econet app, I see:

I am using HA 2022.11.5, and it's using pyeconet 0.1.15. Any ideas on where to look to get things working?

@rborkow @powdahound, any ideas?

@jat255 Do these devices actually support running in resistance electric mode with the heat pump turned off? I've never tried this "Electric/Gas" option and it seems odd to me that it doesn't have an icon in the EcoNet app.

It does; I have it in that mode currently, since we have it in a garage that gets a bit chilly in the winter months. The no icon in the app is weird, but it works when I change it to that mode (I see it switch to "Electric" on the units actual display)

Interesting. I can check mine later today and see if it's working for me.
Would high demand mode also work? Doesn't that cause it to use the HP + resistance in tandem?

The other modes work (Eco, Off, Heat Pump, etc.). I'm in the process of debugging, but it looks like when selecting "Electric" in home assistant, the MODE parameter is not getting set correctly. Here's what happens in set_mode() when setting to "High demand":
2022-12-19 11:43:55.204 DEBUG (SyncWorker_2) [pyeconet.equipment.water_heater] set_mode -- Inside set_mode; mode is WaterHeaterOperationMode.HIGH_DEMAND
2022-12-19 11:43:55.204 DEBUG (SyncWorker_2) [pyeconet.equipment.water_heater] set_mode -- text_modes is: ['Off ', 'Energy Saver ', 'Heat Pump ', 'High Demand ', 'Electric/Gas ', 'Vacation ']
2022-12-19 11:43:55.204 DEBUG (SyncWorker_2) [pyeconet.equipment.water_heater] set_mode -- payload is {'@ENABLED': 1, '@MODE': 3}

Here's "Eco":
2022-12-19 11:42:42.693 DEBUG (SyncWorker_4) [pyeconet.equipment.water_heater] set_mode -- Inside set_mode; mode is WaterHeaterOperationMode.ENERGY_SAVING
2022-12-19 11:42:42.693 DEBUG (SyncWorker_4) [pyeconet.equipment.water_heater] set_mode -- text_modes is: ['Off ', 'Energy Saver ', 'Heat Pump ', 'High Demand ', 'Electric/Gas ', 'Vacation ']
2022-12-19 11:42:42.693 DEBUG (SyncWorker_4) [pyeconet.equipment.water_heater] set_mode -- payload is {'@ENABLED': 1, '@MODE': 1}

And then here's "Electric" (notice there's no @MODE parameter):
2022-12-19 11:43:57.677 DEBUG (SyncWorker_0) [pyeconet.equipment.water_heater] set_mode -- Inside set_mode; mode is WaterHeaterOperationMode.ELECTRIC_MODE
2022-12-19 11:43:57.677 DEBUG (SyncWorker_0) [pyeconet.equipment.water_heater] set_mode -- text_modes is: ['Off ', 'Energy Saver ', 'Heat Pump ', 'High Demand ', 'Electric/Gas ', 'Vacation ']
2022-12-19 11:43:57.677 DEBUG (SyncWorker_0) [pyeconet.equipment.water_heater] set_mode -- payload is {'@ENABLED': 1}

Oh, this might be the issue (and fix): https://github.com/w1ll1am23/pyeconet/commit/c55ccc387f52482f318cd784e8d8f88250259394

Ok, yes, updating the code to what's in 0.1.17 appears to get it working as expected. Since I'm using a container install, I think I'll just need to wait for the next release of HA (since it appears to overwrite my changes when HA restarts), but I'm glad to see it working. Thanks @powdahound and @cpcowart!

@vangorrra or @w1ll1am23, do you know how to get this updated version of pyeconet into HA container? I thought opening an issue in HA would be the right place, but that was dismissed immediately, so I'm not sure where to request an update.

@jat255 I just opened a PR after seeing the issue you opened. I wasn't watching things and didn't know that the author of the fix hadn't opened a change on the HA side, sorry about that.

No worries! Thanks for bumping it just now. And thanks for the great library!


feat(cardeditor): implementation of the card code editor

Closes #1563
Summary
A code editor modal that supports code highlighting and language specific intellisense.
Change List (commits, features, bugs, etc)

Added monaco-editor/react npm package.
Created CardCodeEditor component
Created _card-code-editor.scss and added it to styles.scss
Created two new stories for the new component
Exported CardCodeEditor from index.js
Added test for CardCodeEditor

Acceptance Test (how to verify the PR)

Go to the new CardCodeEditor stories and play around.

@davidicus Agree that it should be a component by itself, rather than embedded as part of a dialog. I have a use case for this as a 80% section of a page. It seems like it also needs to adopt the height of it's parent (it is blowing out vertically on a small dialog)

@davidicus I'm not sure this component needs its own export, especially if we are framing it as a "Card" code editor.
Perhaps there is utility in providing a simple Monaco wrapper, as Jordan suggested, and calling it a CodeEditor?  And CardCodeEditor wraps in a modal, provides callbacks for our custom dashboard card json validation, etc?
I suggest we remove the CardCodeEditor package export and only scope this as being used by the CodeEditor component.

This perfectly fits the needs of the Dashboard editor though 👏  looking good

@stuckless @JordanWSmith15

If you exposed an "Editor" component that wrapped much of Manaco, then I wouldn't need add a dependency for it explicitly and that way we could be sure we were using the same copy/version instead of potentially having 2 versions pulled in.

It is in a dialog because that is what the spec I was building for required. That being said, I can definitely expose an editor component on it's own that I consume here.

Does monaco support gutters where you can attach errors to the gutters?  This was one reason I was looking at Ace, although to be fair, I didn't really look at Monaco, since I've used Ace in the past.

Monaco supports a lot of functionality and I believe most of the features that are available with VSCode. I have not see the errors in the gutters along the line numbers but Monaco has it on the scroller or minimap.

How much of an overhead is monaco-editor going to add to the bundle sizes? I'm wondering if components like this that tend to bring in a large set of other dependencies should be put into a separate component repo?

The package itself is about 5.5kB minified + gzipped
https://bundlephobia.com/result?p=<EMAIL_ADDRESS>What product is the editor requirement for? I will open up another issue to refactor this into its own component. I would like to add the product tags so we have the context in our priority call.
@bryancboyd I can remove the export

:tada: This PR is included in version 2.125.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Update in-cluster-client-configuration example

Update Dockerfile and README.md in example/in-cluster-client-configuration.

Update Dockerfile, no need to cross-compile locally；
Update README.md, add --image-pull-policy=IfNotPresent to use the local image.

@geange The original client-go code exists at https://github.com/kubernetes/kubernetes/tree/master/staging/src/k8s.io/client-go. Please directly open a PR against that directory.

Closing and reopening to test https://github.com/kubernetes/test-infra/pull/22879 (please ignore!)


Update postgresql_compatibility.md

Use markdown for all results tables.

Thanks!

In the current design, narrow_table doesn't do anything, so I plan to deprecate it... Will open an issue in a sec.


Copy as Markdown not escaping some characters

If the text itself includes asterisks or angle-brackets, they aren't escaped into * or < >
So the resulting markdown doesn't match the original. That is to say, this italicized and censored internal thought:
F*ck, what is going on?
becomes:
Fck, what is going on?*
The asterisk in the text isn't escaped, so it's treated as markdown when it shouldn't be.
This looks like it might be a Turndown issue, as escaping was fixed in the recent 5.0.0 release, so if you're using a version older than that you'll have the same bugs.

It's obviously confusing to ask an error about Markdown on a platform that supports Markdown, so I tried to display these in code syntax:
original HTML
F*ck, what is going on?

should be
*F\*ck, what is going on?*

not
*F*ck, what is going on?*

After my check, this is indeed a problem with Turndown. When I upgraded to Turndown 5.0.0, the problem was solved. Thank you for your reminder, please wait for me to release Copycat 2.4.1.

Still not escaping angle brackets.
Original: <<REBIRTH>>
Source: <<REBIRTH>>
Becomes: <\>
and
Original: <Shield of Sunset Light (Shield) (Set Equipment)>
Source: <Shield of Sunset Light (Shield) (Set Equipment)>
Becomes: ....nothing.
I did see a comment talking about more aggressive escaping rules (which included angle brackets) which didn't make it into the 5.0.0 release, so maybe it's possible with that custom rule?
Currently, if the formatted text includes < and >, it's misinterpreted as an HTML tag at some point along the way, and removed.

Copycat will decode HTML character entities into ordinary characters in advance, which causes this problem. After I removed the code that decoded HTML entities, the problem was solved, it will be released as version 2.4.2.


Viewer clock improvements

In master, it's impossible specify the clockViewModel instance to use for any child widgets that need it.  Viewer also doesn't expose the ClockViewModel and you have to dig into animation.viewModel.clockViewModel to get to it.  This makes it hard to write custom widgets that need to share the same ClockViewModel and are not directly tied to the lifetime of the
clockViewModel` created by Viewer (which gets destroyed when the Viewer is destroyed).
This change deprecates the Viewer clock constructor option and replaces it with clockViewModel.  If a custom clockViewModel is specified, it is passed through to any child widgets that need it and it is not destroyed on destruction.
We didn't have tests for the old functionality, but I added a test for the new parameter.

Why can't we just get the ClockViewModel that's created by the viewer?  Because you need it to stay around after the viewer is destroyed?

Also what happens if you want multiple viewers to share a single clock?  Is that still supported?  I'm using options.clock in at least one production app.

Also what happens if you want multiple viewers to share a single clock? Is that still supported? I'm using options.clock in at least one production app.

Sure, you get the same exact effect by making them share the same clockViewModel.  In fact, I wouldn't be surprised if there were potential bugs in the old behavior because you ended up with two clockViewModel instances controlling the same clock.  (plus, if anyone really needs the exact old behavior you can still create two clockViewModel instances that have the same clock and pass them too each Viewer).

Why can't we just get the ClockViewModel that's created by the viewer? Because you need it to stay around after the viewer is destroyed?

Yes, but also because in my use case, the ClockViewModel needs to exist before the Animation widget is even constructed.  Keep in mind that AnimationViewModel already requires an existing ClockViewModel instance, it just that previously the Viewer was always the one creating it.

This is ready unless either of you still have some reservations or more questions/comments.

I'm fine with this.  @hpinkos please merge when ready.

:+1: looks good to me!


"Cheatin' uh?" message.

Issue description:
I´ve got this issue with Kirki when i access the customizer panel, change any setting and save & close, when i click on any link on my page i get this message:

Further more i noticed that immediately after saving and closing the customizer every link on the page have the suffix “&customize_changeset_uuid= …”  with the customizer already closed.

and i guess that’s why the error message appears.
That suffix also stays in the browser path bar. If i'm in my root url (www.mysite.com) and access the customizer after i change something and close it the path bar address is now "www.mysite.com/?customize_changeset_uuid=34bc8801-c3b6-4c20-8d68-ad8888f38da2"
If i erase that suffix from the path bar everything works fine.
Tested with my own custom theme and also with your _s theme with same results.
Version used:
dev version 3.0.0-beta.1
Using theme_mods or options?
theme_mods
Code to reproduce the issue (config + field(s))

This has nothing to do with Kirki..
Recently changesets were implemented in the WP Core Customizer.
These "changesets" get deleted once published, so when you try to go to an already published changeset in the WP Customizer you get that message because it no longer exists.

I’m sorry to insist but i don’t know if i expressed myself right in the first place.
I´ve just made a fresh installation of WP with the current Kirki dev version and your _s theme and recorded a 20 second video of my issue, i would appreciate if you check it out.
Video link
Please note how WP throws the error the second time i access the customizer.
The issue is reproduce like this:
Access customizer -> change setting -> save & close -> access customizer again -> error
Doing this in a localhost.

As I said in my previous reply, this has nothing to do with Kirki.
This is default WP behaviour.
If you disable Kirki you'll still get the same results....

I disabled Kirki just to check if the behaviour is the same and.. it’s not.
It’s works without any error message. As it always worked till ~2 weeks ago.
I enable Kirki and error comes again.
You can see it here with a clean WP install + your _s theme with kirki disabled.
Video with Kirki disabled
Video with Kirki enabled
From what i can see with Kirki disabled when i change a setting in the customizer (like color) a suffix is added to the browser bar url  (the ?customize_changeset_uuid=34bc8801-c3b6-4c2… ) and when i hit the save button that url suffix is removed. So when i close the panel the url in the browser path is the same as before i opened the panel.
When Kirki is enabled and a setting is hanged that suffix is nor removed after i hit save and close the customizer panel.
Thus the browser url is different after the panel is closed, and WP throws the error when trying to access the panel a second time.
You can see this behavior in the videos in the browser path.
Maybe i'm expressing this issue with really bad English (i'm not native), and i’m sorry in advanced for it, but this cant be default behavior because i’m only getting this behavior from Kirki in the past week or two.

You're right, my bad. There's something wrong...
Reopened the issue, I'll try to figure this one out.
Thanks! 👍

Hey again!
I believe this was just fixed... At least in my tests it looks like this is working as expected now.
The issue was caused by a new feature that I was trying to add for collapsible fields (see #1187).

Just spend some time testing it.
So far so good.
Thanks

thanks for testing!!


Replace the linalgx op with generic op and enhance matmul config

Track https://github.com/intel/graph-compiler/issues/272

The microkernel pipeline has not support generic op yet, could we add a temp switch for generating linalgx to avoid breaking the pipeline, untill generic support of microkernel pipeline is added?

The microkernel pipeline has not support generic op yet, could we add a temp switch for generating linalgx to avoid breaking the pipeline, untill generic support of microkernel pipeline is added?

Yes, I could add both supports now. But even on the current pipeline, linalgx op doesn't support bufferization interface and cannot be lowered to memref semantic for microkernel use.

The microkernel pipeline has not support generic op yet, could we add a temp switch for generating linalgx to avoid breaking the pipeline, untill generic support of microkernel pipeline is added?

Yes, I could add both supports now. But even on the current pipeline, linalgx op doesn't support bufferization interface and cannot be lowered to memref semantic for microkernel use.

Now microkernel frontend pass has been refactored to be based on linalgx with tensor, so it should be enough


create deDupedAnnouncements struct in networkHandler -#275

For Part 1 of Issue #275. Create isolated private struct in networkHandler
goroutine that will de-duplicate announcements added to the batch. Also fix
a few minor typos.

That file rename though. Going to push small changes, would love feedback :)

De-duplicated announcement batch, going to tackle trickleDelay next :)


[d3d11] implement stateblock normalization

Implement d3d11 stateblock normalization to match what d3d11 does in state object creation.

I see many things like
if (pDesc->AlphaToCoverageEnable != 0) {
      pDesc->AlphaToCoverageEnable = 1;
}

Isn't AlphaToCoverageEnable already 1 if not 0?
It's better to use TRUE and FALSE.

It's to fix applications who don't initialize all the members so they are stuck with garbage data. D3D11 will enable those variables if they aren't equal to 0. So I force it back 1 to make it do what D3D11 does.  D3D11 is to blame for allowing values other than 1 to enable something.

I mean I guess I could, but by the time the code get's there I already corrected for it by setting it to 1. Also, D3D11 resets it back to 1. I'm only matching what it does.

This series of patches have immediate effect of fixing rendering issues on any game to test?

This patch mainly fixes reference count issues that usually show up in apitraces. Though, it may help games as well.

@ZeroFault

I mean, I guess I could, but by the time the code get's there I already corrected for it by setting it to 1

But then there's even less reason to pretend that these booleans are integers. This == 0 and == 1 is something I really don't like either.

I'll fix it, but BOOL is literally defined as an integer anyway. It's not pretending.


Allow consuming QR codes

Some IdPs prefer that users log in through QR code. For this to work, both the app must have a QR scanner function, and the OS-level QR-scanner must be able to find our app when a Wi-Fi configuration is scanned.
We need some discussion on how this would work. Can we make a QR-code with a special schema, such as letswifi://qr_callback, where the OS is able to find the app in the App Store or Play Store if it was not installed yet?

Pretty much duplicate of #45


When Edison is gone, will diagnostics works in the same way on cori?

Creating an issue cause i don't know where to post this question.

apparently the previous issue is for cori, closing this then.

I'm currently testing on Cori and there seems to be some small issues with syntax. It shouldn't be too bad. When this is working, we'll have a quick start guide for Cori as well.

Thanks!


fix(navbar): remove renderOpener and rename ariaLabel to just label

There is no need to keep the renderOpener prop as the navbar dropdowns should always be consistent when it comes to toggle buttons

:tada: This PR is included in version 4.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Remove file

Hi @brownd1978,
You have proposed changes to files in these packages:

JobConfig

which require these tests: build.
@Mu2e/write, @Mu2e/fnalbuild-users have access to CI actions on main.
:hourglass: The following tests have been triggered for f5c9ab47b1962a2c84b9261afb1fe4f16156f24a: build  (Build queue has 2 jobs)
About FNALbuild. Code review on Mu2e/Offline.

:sunny: The build tests passed at f5c9ab47b1962a2c84b9261afb1fe4f16156f24a.

Test
Result
Details

test with
:white_check_mark:
Command did not list any other PRs to include

merge
:white_check_mark:
Merged f5c9ab47b1962a2c84b9261afb1fe4f16156f24a at 932e8e6613254f5dedb9619cc08be572d705db56

build (prof)
:white_check_mark:
Log file. Build time: 11 min 10 sec

ceSimReco
:white_check_mark:
Log file.

g4test_03MT
:white_check_mark:
Log file.

transportOnly
:white_check_mark:
Log file.

POT
:white_check_mark:
Log file.

g4study
:white_check_mark:
Log file.

cosmicSimReco
:white_check_mark:
Log file.

cosmicOffSpill
:white_check_mark:
Log file.

ceSteps
:white_check_mark:
Log file.

ceDigi
:white_check_mark:
Log file.

muDauSteps
:white_check_mark:
Log file.

ceMix
:white_check_mark:
Log file.

rootOverlaps
:white_check_mark:
Log file.

g4surfaceCheck
:white_check_mark:
Log file.

FIXME, TODO
:white_check_mark:
TODO (0) FIXME (0) in 0 files

clang-tidy
:white_check_mark:
0 errors 0 warnings

N.B. These results were obtained from a build of this Pull Request at f5c9ab47b1962a2c84b9261afb1fe4f16156f24a after being merged into the base branch at 932e8e6613254f5dedb9619cc08be572d705db56.
For more information, please check the job page here.
Build artifacts are deleted after 5 days. If this is not desired, select Keep this build forever on the job page.


Elvis failed badarg in inaka/serpents#74

Check out this PR.
Stacktrace:
[
 {re,run,[<<"HDP.md">>,[<<"src/">>,<<".*">>|<<"*/*\\.erl">>],[{capture,none}]],[]},
 {elvis_file,'-filter_files/3-fun-2-',2,[{file,"src/elvis_file.erl"},{line,92}]},
 {lists,'-filter/2-lc$^0/1-0-',2,[{file,"lists.erl"},{line,1284}]},
 {lists,flatmap,2,[{file,"lists.erl"},{line,1248}]},
 {lists,flatmap,2,[{file,"lists.erl"},{line,1248}]},
 {elvis_config,resolve_files,2, [{file,"src/elvis_config.erl"},{line,136}]},
 {lists,map,2,[{file,"lists.erl"},{line,1237}]},
 {elvis_webhook,handle_pull_request,3,[{file,"src/elvis_webhook.erl"},{line,35}]}
]

In elvis_file:glob_to_regex/1 there a missing global option for re:replace/4.


AJAX requests to authenticated resources now use Bearer Token

They also update the bearer token as necessary.
TODO: dukecloak.js:33 needs to be enhanced to publish the loaded favourites to the view model directly instead of a window reload (would otherwise lead to a infinite loop)

I changed dukecloak.js as indicated. Works fine in Chrome and Firefox, but in IE 11 I get an error message "Unable to update token" and the synchronization does not work. Please have a look.


_.sortBy option for sorting null values to end

Currently, _.sortBy doesn't sort null values. I believe an optional param to decide what to do with null and possibly undefined (which currently defaults to end) would be a good feature.
It's a pretty simple addition, and I have already coded the feature into a project I'm working on, and can a do a PR if you believe this is a feature worth adding.

Hey, there are a number of issues currently open related to sort order for spurius values (namely NaN and undefined) #1768 https://github.com/jashkenas/underscore/pull/2041  #2042  and others.
We're probably going to leave null as is; but it should be easy enough to handle in the comparator function


Add legacy urls to dead-links checker

Overview
Our documentation's structure is changing quite often so to track if old links, that where published before in 3rd party platforms, social media or in botkube itself, still working we need to have a list of them and possibility to check 404 errors.
The solution won't be perfect (because tracking all changes will be tedious task) but at least this solution give us a hand on most cases.
AC

[ ] extend this script magefiles/magefile.go#23 (CheckDeadLinks) to check additional markdown (e.g. - archive-links.md)
[ ] provide archive-links.md markdown with old links, that needs to be supported.

@mszostok you had a list (not sure if you still have it, but it will be good for start)

Yes, here are the legacy URLs:
Works:

https://botkube.io/docs

https://botkube.io/privacy#privacy-policy

https://botkube.io/filters

https://botkube.io/installation/

https://botkube.io/configuration/resource/

https://botkube.io/configuration/communication/

https://botkube.io/installation/slack/#install-botkube-slack-app-to-your-slack-workspace

https://botkube.io/configuration/communication/#source-and-executor-bindings

https://botkube.io/docs/installation/slack/#install-botkube-slack-app-to-your-slack-workspace

https://botkube.io/docs/installation/socketslack/#obtain-bot-token

https://botkube.io/docs/installation/socketslack/#generate-and-obtain-app-level-token

https://botkube.io/docs/configuration/source

https://botkube.io/docs/installation/slack/

https://botkube.io/docs/installation/discord/#install-botkube-to-the-discord-server


feat(ecs): Set volume in task definition

Goal
Set volumes in the task definition, to fix an error during terraform apply:

[ERROR] eval: *terraform.EvalApplyPost, err: ClientException: Unknown volume 'config'.

Todos

[x] Test example.ts

Implementation Decisions

Explicitly set volume to an empty list if there are none. This seemed to better following the existing pattern of being explicit, but I don't feel strongly either way.

:tada: This PR is included in version 1.13.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


filebeat to es

Es uses SG，
I want to use filebeat to write logs to es. How to configure it?
Thank

Please do not ask questions here.
For that refer to https://groups.google.com/forum/#!forum/search-guard or, if you are a paying customer, contact our support.
Github is a place only for reporting bugs or feature requests.
If you report a bug please include always the following informations or the issue will likely be closed as invalid:

Search Guard and Elasticsearch version
Kibana plugin version
JVM version and operating system version
Number of nodes in your cluster
Description of the bug
sg_*.yml config files
kibana.yml file
elasticsearch.yml file

These informations are optional but are very valuable and
typically would lead to get bugs fixed faster:

Steps to reproduce
Logfiles on DEBUG level
A failing unittest


turborepo: Discovering symbol references and renaming doesn't work in VS Code

What version of Turborepo are you using?
latest, 1.10
What package manager are you using / does the bug impact?
npm, pnpm, Yarn v1
What operating system are you using?
Mac
Describe the Bug
Cannot discover all references for some symbol in VS Code (Context menu -> Find All References or Option+Shift+F12). Cannot confidently rename (F2) the same symbol and expect that all its references will be renamed as well.
Expected Behavior
All references of the symbol should be listed when searching for them. Renaming a symbol should rename all of its references.
To Reproduce
I followed the official guide.
Steps

npx create-turbo@latest
Open the new repo in VS Code
Open the packages/ui/src/card.tsx
Search for all references of the Card component (Context menu -> Find All References or Option+Shift+F12). Doesn't find them all.

If you now navigate to apps/web/app/page.tsx, then jump back to the card component and search again for its references, now there'll be an entry for apps/web/app/page.tsx, but still not for apps/docs/app/page.tsx (because we didn't navigate to that one yet). If you were to now rename the Card component to the CoolCard, only the apps/web/app/page.tsx's reference would get renamed, thus breaking the apps/docs/app/page.tsx.
These steps can be repeated by reloading VS Code: Cmd+Shift+P -> "Developer: Reload Window"
I've tried these steps for npm, pnpm and yarn v1.
Node: v21.1.0
OS: MacOS 14.1.1
VS Code: 1.84.2 (latest)
Reproduction Repo
No need, doesn't work out of the box

This is a limitation brought on by the way VSCode and tsserver work. Poking around in the TypeScript repo yields many issues on this subject. Here's one that links out to a great many other related issues: https://github.com/microsoft/vscode/issues/80087
It looks like this is a conscious performance trade-off made by the TypeScript team from what I'm seeing. Unfortunately, there's nothing we can do about this here in Turborepo it looks like.
If there's a technique that can make this work that you can point me to, that'd be great! I wasn't able to find a solution. Would be happy to take a PR for review, as well!

That's a shame it does not work.
Is there any news regarding this issue?
It helps a lot to see all the references for a component in the whole project

This is not a Turborepo issue as noted in my comment above. You'll want to check in on with the TypeScript repo to see if anything has been done.


prep for 1.7.3

did we need to update againg the packs ?

yep, I'm currently working on the "reverse" 💩

uffff

@p4535992 for the "magicitems" release, there's another p/r https://github.com/PwQt/magic-items-2/pull/92


add participants count to column in batch overview

Hey Carlos,
I just made a small adjustment by adding the participants count next to the graduates count, so we can get a better sense of how many started and how many completed successfully (in our opinion).

Best, Philip

Hey Carlos,
I changed the /batches route so that it gives you the totalParicipants and graduates count for every batch.
Pls let me know if I should make any adjustments.
Thank you!


Feature Request: Switch Widget

Maybe there's a way to accomplish what I'm looking for already, but I can't figure it out. I have pages which are composed of blocks. Each block can be one of several widgets. I would like to be able to switch between those widgets on the admin page. Consider the following configuration representing a list of blocks:
---
collections:
  - name: page
    label: Page
    folder: content/pages
    extension: yml
    create: true
    fields:
      - label: Page Title
        name: title
        widget: string
      - label: Page Content
        name: content
        widget: list
        field:
          label: Block
          widget: switch
          widgets:
            - type: image
            - type: markdown
            - type: custom-widget

A page edited by the above might look like the following:
---
title: Foo Bar Banana
content:
  - widget: image
    value: foo/bar/banana.png
  - widget: markdown
    value: bears and bananas
  - widget: custom-widget
    value: some value
  - widget: markdown
    value: other bears and other bananas
  - widget: image
    value: i/think/you/get/it.jpg

The key part being that you can add and reorder blocks, it will default its widget to the first one in the configuration, but the user can change the type of widget represented by that block.
Is this currently possible? Would it need to be implemented and if so would the netlify team be interested in either implementing this or accepting a PR?

#1066 seems to be what you are looking for, it is a work in progress. You can see the linked PR at https://github.com/netlify/netlify-cms/pull/1169.

Good stuff. Thanks!


Optimize jobserver try_acquire

First try jobserver::Client::try_acquire (available on jobserver 1.0.29), which will work:

If a fifo is used as jobserver
On linux and:

preadv2 with non-blocking read available (>=5.6)
/proc is available

On Windows
On wasm

if not, we will simply fallback to help thread implementation, spawning one
thread to maintain compatibility with other platforms.

I do not believe it is acceptable to vendor OnceLock. It is a bad idea for a low-maintenance crate to vendor code that may need a security update.

I do not believe it is acceptable to vendor OnceLock. It is a bad idea for a low-maintenance crate to vendor code that may need a security update.

Thanks for pointing out, under @the8472 's advice, I've replaced that with once_cell dependency and removed the vendoring of OnceLock.


SAA-60 changing ID's from Int to Long.

Is there a DDL change too, to use bigserial over serial types?

So technically there should be but I avoided as you said you were going to change the model.


Take app/vendors out of version control.

Discussed on issue #617.

Sent to Eliah.

Can you also document how to install libraries in app/vendors in https://github.com/google/personfinder/wiki/GettingStarted ?

Yeah, I just want to wait until it's submitted.

Can you also document how to install libraries in app/vendors in https://github.com/google/personfinder/wiki/GettingStarted ?

Yeah, I just want to wait until it's submitted.

SGTM


[Suggestion] Consider adding labels for self-hosted and cloud variants

Is there an existing issue for this feature?

[X] Yes, I have searched the existing issues and it doesn't exist.

Feature Description
It is becoming harder to triage issues, especially older ones. Adding labels would make it easier to separate self-hosted and cloud-variant issues.

Some options would be

For anyone looking here, it is possible via GitHub actions and this one: redhat-plumbers-in-action/advanced-issue-labeler
systemd repo has some good examples of using it<EMAIL_ADDRESS>I have been able to set it up in a few minutes as well, working great: https://github.com/Dasharo/dasharo-issues/commit/3a3912699b80b9cf8f6ef8cb116d16480f814f1f

source: https://github.com/orgs/community/discussions/44350#discussioncomment-8919921

Just newly submitted issues from what I understand. Maybe there is a way to run the labeler for all issues once before the action is set up.

I would like to work on this.

i would like to work on this


IOD-194 Adding Health Check

Description
This PR includes the following proposed change(s):
IOD-194
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Refactoring / Documentation
[ ] Version change

if your change is a breaking change, please add breaking change label to this PR
How Has This Been Tested?
Please describe the tests that you ran to verify your changes.
Does the change impact or break the Docker build?

[ ] Yes
[x] No

If Yes: Has Docker been updated accordingly?

[ ] Yes
[x] No

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have made corresponding changes to the documentation
[x] New and existing unit tests pass locally with my changes

@SDToews issues are resolved and ready for review


Any variable on dashboard breaks 'SELECT 1 UNION ALL SELECT 2;'

Duplicate of https://github.com/grafana/clickhouse-datasource/issues/132, which was closed, but still hasn't been fixed - tested in a fresh v2 build (as of today). Close this and reopen that one.

Describe the bug A clear and concise description of what the bug is.
Versions Grafana 8.5.5 Plugin 1.1.2
Query SELECT 1 UNION ALL SELECT 2;
To Reproduce Steps to reproduce the behavior: 1.
compose.yaml
1.1. docker compose up --detach 1.2. docker compose exec grafana grafana-cli plugins install grafana-clickhouse-datasource

add datasource clickhouse

open explore
http://localhost:3000/explore?left={"datasource":"ClickHouse","queries":[{"refId":"A","queryType":"sql","rawSql":"SELECT 1 UNION ALL SELECT 2;\r\n","meta":{"builderOptions":{"mode":"list","fields":[],"limit":100}},"format":1}],"range":{"from":"now-1h","to":"now"}}&orgId=1
and check that SELECT 1 UNION ALL SELECT 2; it is works
Greate new dashboard http://localhost:3000/dashboard/new?orgId=1
4.1. Add a new panel
4.2. switch into SQL Editor
4.3. paste SELECT 1 UNION ALL SELECT 2;
4.4. Run Query
4.5. POST 200 OK with rawSql: SELECT 1 UNION ALL SELECT 2;\r\n

add any variable
5.1. http://localhost:3000/dashboard/new?orgId=1&editview=templating
5.2. add var with the name query0

5.3. go back to panel and Run Query 5.4. POST 400 Bad Request with rawSql: SELECT 2 UNION ALL

Expected behavior POST 200 OK with correct SQL

This issue is fixed on main. We will create a new release soon.


keepalive problem in cache-node balancing

fixed in #61
keepalive problem cause - https://forum.nginx.org/read.php?2,293531,293535#msg-293535


[Feature Request] Bauble Creation

Feature:
The ability to create baubles that can be defined as:

Ring
Amulet
Belt
Head
Body
Charm
As well as the ability to trigger a command or a potion effect that turns off when removed. Rendering the baubles on body doesn't need to be added just the ability to make them.

I would like this too.

I really want this as well.


AzureCLI unable to set subscription when multiple are available

Required Information
Entering this information will route you directly to the right team and expedite traction.
Question, Bug, or Feature?
Type: Bug
Enter Task Name: AzureCLI
Environment

Server - Azure Pipelines
Agent - Hosted ubuntu-latest

Issue Description
When using a Service Connection that has a Service Principal with access to multiple subscriptions, the task fails with ERROR: The subscription of 'undefined' doesn't exist in cloud 'AzureCloud'.
Task logs

Starting: AzureCLI
==============================================================================
Task         : Azure CLI
Description  : Run Azure CLI commands against an Azure subscription in a PowerShell Core/Shell script when running on Linux agent or PowerShell/PowerSheell Core/Batch script when running on Windows agent.
Version      : 2.0.3
Author       : Microsoft Corporation
Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks/deploy/azure-cli
==============================================================================
/usr/bin/az --version
WARNING: You have 2 updates available. Consider updating your CLI installation. Instructions can be found at https://docs.microsoft.com/en-us/cli/azure/install-azure-cli
azure-cli                         2.0.77 *

command-modules-nspkg              2.0.3
core                              2.0.77 *
nspkg                              3.0.4
telemetry                          1.0.4

Python location '/opt/az/bin/python3'
Extensions directory '/home/vsts/.azure/cliextensions'

Python (Linux) 3.6.5 (default, Nov 22 2019, 05:32:22)
[GCC 5.4.0 20160609]

Legal docs and information: aka.ms/AzureCliLegal

Setting active cloud to: AzureCloud
/usr/bin/az cloud set -n AzureCloud
/usr/bin/az login --service-principal -u *** -p *** --tenant ***
[
   list of subscriptions (redacted)
]
/usr/bin/az account set --subscription undefined
ERROR: The subscription of 'undefined' doesn't exist in cloud 'AzureCloud'.
##[error]Error Code: [1]
##[error]Error: Error in setting up subscription
##[error]Script failed with error: ERROR: The subscription of 'undefined' doesn't exist in cloud 'AzureCloud'.

/usr/bin/az account clear
Finishing: AzureCLI

Hey @jvassbo ,
it looks like the AzureRM Service connection being used in the task, is missing subscription name. Can you verify if this is the case ?

Hi @hiyadav,
Our service connection is scoped on ManagementGroup level, so no - no defined subscription

That is probably the reason of the error. To set the subscription the task, derives the subscription name from the service endpoint (assumed to be scoped to subscription) being used in the task.
Work around for now would be to using subscription based/scoped endpoint.
To be able to solve this can you tell us if you are using yaml pipeline ? or were you able to add the endpoint from old editor with UX ?

We are using yaml pipeline.
This service connection needs to be scoped on this level for our functional requirements, so the workaround is not going to work for us, unfortunately.

I stand corrected, the workaround did work - even though our script does things outside of the scoped subscription.
Which makes me wonder, what excatly is the scope of a service connection in DevOps..?
Not sure if this should still be considered a bug, or if AzureCLI task just has a prerequisite that the used service connection is scoped on a subscription? (feel free to close the issue if so)

If the Azure SPN used to create the ARM service principal in ADO, has permission/role over all/many  subscriptions, then the command over those subscriptions are bound to succeed.
Azure CLI task needs to set a current subscription after log-in. This is required as otherwise, all commands will run on a subscription which is enabled/checked by default for the user.
However, I realize that the task can compromise setting subscription when the information is not available. @jalajmsft @pulkitaggarwl  to consider this.
Hence, marking it as enhancement.

We have tried to improve on the error message as well in this PR #12054

Hi @jvassbo
How you manage to create the service connection for multiple susbscriptions?
In Azure devops, when I create a service connection, I can just select one subscription, so, if I'm using the AzureCLI task, I just can select that service connection, and if my script is trying to access two subscriptions, it only can access the one selecte in the service connection, fails for the other one.
But according to your logs, your service connection can access several susbscriptions.
Thanks


fix: exceptions may not be raised when using noop span.

Hi there!
Thanks for opening this. Actually the error is that we are returning a noop
context when the span is noop and that is incorrect because although span
is noop you don't want to break propagation. I am finishing unit tests for
a PR on this.
On Mon, 18 May 2020, 06:46 谷溪<EMAIL_ADDRESS>wrote:

You can view, comment on, or merge this pull request online at:
https://github.com/jcchavezs/zipkin-php-opentracing/pull/31
Commit Summary

fix: exceptions may not be raised when using noop span.

File Changes

M src/ZipkinOpenTracing/Tracer.php
https://github.com/jcchavezs/zipkin-php-opentracing/pull/31/files#diff-25c66202aad94dec22819d4ca7e347b2
(4)

Patch Links:

https://github.com/jcchavezs/zipkin-php-opentracing/pull/31.patch
https://github.com/jcchavezs/zipkin-php-opentracing/pull/31.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/jcchavezs/zipkin-php-opentracing/pull/31, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAXOYATSLLZPBPBECUMIPM3RSC4SBANCNFSM4NDXLDOA
.

First PR to solve this issue:
https://github.com/openzipkin/zipkin-php/pull/146
José Carlos Chávez
man. 18. mai 2020 kl. 13:10 skrev José Carlos Chávez<EMAIL_ADDRESS>
Hi there!
Thanks for opening this. Actually the error is that we are returning a
noop context when the span is noop and that is incorrect because although
span is noop you don't want to break propagation. I am finishing unit tests
for a PR on this.
On Mon, 18 May 2020, 06:46 谷溪<EMAIL_ADDRESS>wrote:

You can view, comment on, or merge this pull request online at:
https://github.com/jcchavezs/zipkin-php-opentracing/pull/31
Commit Summary

fix: exceptions may not be raised when using noop span.

File Changes

M src/ZipkinOpenTracing/Tracer.php
https://github.com/jcchavezs/zipkin-php-opentracing/pull/31/files#diff-25c66202aad94dec22819d4ca7e347b2
(4)

Patch Links:

https://github.com/jcchavezs/zipkin-php-opentracing/pull/31.patch
https://github.com/jcchavezs/zipkin-php-opentracing/pull/31.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/jcchavezs/zipkin-php-opentracing/pull/31, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAXOYATSLLZPBPBECUMIPM3RSC4SBANCNFSM4NDXLDOA
.

Thanks for this @reasno. I just opened a PR replacing this one. Main reason
for not going with this PR is because this change breaks the context
propagation to downstreams when in a noop span and that is not desirable.
If there is a noop (meaning unsampled) we still want to propagate the
tracing context to avoid upstream to start traces by themselves and honour
the service starting the trace.
On Tue, 19 May 2020, 00:18 José Carlos Chávez<EMAIL_ADDRESS>wrote:

First PR to solve this issue:
https://github.com/openzipkin/zipkin-php/pull/146
José Carlos Chávez
man. 18. mai 2020 kl. 13:10 skrev José Carlos Chávez<EMAIL_ADDRESS>
:

Hi there!
Thanks for opening this. Actually the error is that we are returning a
noop context when the span is noop and that is incorrect because although
span is noop you don't want to break propagation. I am finishing unit tests
for a PR on this.
On Mon, 18 May 2020, 06:46 谷溪<EMAIL_ADDRESS>wrote:

You can view, comment on, or merge this pull request online at:
https://github.com/jcchavezs/zipkin-php-opentracing/pull/31
Commit Summary

fix: exceptions may not be raised when using noop span.

File Changes

M src/ZipkinOpenTracing/Tracer.php
https://github.com/jcchavezs/zipkin-php-opentracing/pull/31/files#diff-25c66202aad94dec22819d4ca7e347b2
(4)

Patch Links:

https://github.com/jcchavezs/zipkin-php-opentracing/pull/31.patch
https://github.com/jcchavezs/zipkin-php-opentracing/pull/31.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/jcchavezs/zipkin-php-opentracing/pull/31, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAXOYATSLLZPBPBECUMIPM3RSC4SBANCNFSM4NDXLDOA
.

Great. I am closing this one


add delete by multiple indexes functionality

Codecov Report
Patch coverage: 59.61% and project coverage change: -0.60 :warning:

Comparison is base (a651a77) 68.99% compared to head (27eada6) 68.40%.

Additional details and impacted files
@@             Coverage Diff              @@
##             master      #68      +/-   ##
============================================
- Coverage     68.99%   68.40%   -0.60%
- Complexity      464      472       +8
============================================
  Files            84       86       +2
  Lines          1516     1554      +38
  Branches        165      170       +5
============================================
+ Hits           1046     1063      +17
- Misses          413      429      +16
- Partials         57       62       +5

Impacted Files
Coverage Δ

src/main/java/seedu/address/model/Model.java
100.00% <ø> (ø)

...rc/main/java/seedu/address/model/ModelManager.java
92.53% <0.00%> (-7.47%)
:arrow_down:

...ess/logic/commands/DeleteMultipleIndexCommand.java
30.00% <30.00%> (ø)

...in/java/seedu/address/logic/parser/ParserUtil.java
80.35% <77.77%> (-0.50%)
:arrow_down:

...va/seedu/address/logic/commands/DeleteCommand.java
100.00% <100.00%> (ø)

...dress/logic/commands/DeleteSingleIndexCommand.java
100.00% <100.00%> (ø)

...eedu/address/logic/parser/DeleteCommandParser.java
100.00% <100.00%> (ø)

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

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


[ci] Quote argument to get-build-type.sh

When we run on master (rather than a PR),
$SYSTEM_PULLREQUEST_TARGETBRANCH isn't defined, since this isn't a
pull request. Make sure we still actually pass 2 arguments to
get-build-type.sh.
Fixes #5048.

Isn't the problem a missing condition: eq(variables['Build.Reason'], 'PullRequest') in the python lint job?
  - bash: ci/scripts/python-lint.sh $SYSTEM_PULLREQUEST_TARGETBRANCH
    displayName: Run Python lint
    continueOnError: true

Ah no, there are two "problems". The python lint one is in addition to the one you have fixed in here currently.

Hmm, this is odd. I don't understand why the Python bit has changed. Does that failure break master CI?

The quick lint job looks good, let's get this merged to unbreak master CI.


Revert "Fix the new page issue"

[Issue] https://github.com/Samsung/TAU-Design-Editor/issues/388
[Problem] Since TAU 1.1.5 tau.bundle.js is not available
[Solution] Revert commit 2d28c6730359a5f4e55f99a739afca65271a93b7.

This works well with 1.1.5 samples:
M_Sample_TAU_1.1.5.zip
W_Sample_TAU_1.1.5.zip


Update LLM Endpoint Validation Commands

Description
Update llm endpoint validation commands.
Unify curl command to /v1/chat/completions for both TGI and vLLM endpoints.
Issues
n/a
Type of change
List the type of change like below. Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds new functionality)
[ ] Breaking change (fix or feature that would break existing design and interface)
[x] Others (enhancement, documentation, validation, etc.)

Dependencies
None
Tests
Local tested

@letonghan,
Please check the CI issue.


Add documentation for how to enable a new hardware platform support

@rootfs ,
pre discussed with @marceloamaral , @jiangphcn , @jichenjc , @sunya-ch
personally I want to add a chapter in kepler-doc as enable a new hardware platform for kepler.
as a checklist for people when on board kepler with a new hardware platform as s390.
Here is the check list as overall design for this chapter, and assigned to people as task? and I hope we can make it with in this week, then submit to kubecorn as a proposal from our community.

[ ] Over all description. (#60 )
Phase 1
[ ] build kepler code on specific hardware platform from binary to container image.(@SamYuan1990 )
[ ] find out all existing metric as ebfp counter and cgroup to identify resource usage.(@SamYuan1990 , @marceloamaral , @jichenjc )
[ ] find power API to play role as rapi or acpi.(@jiangphcn )
Phase 2
[ ] model training logic(@sunya-ch , @jiangphcn )
[ ] model training docker image and deployment(@sunya-ch, @jiangphcn , @SamYuan1990 )

Hence, we can use an existing content as proposal to kubecorn.
WDYT?

I will try to completed a draft at Thursday night and let's discuss on slack.
Honestly, I have two speeches locally in recent, which makes me busy with time.


Bolt stuck because create-next-app is waiting a response

Describe the bug
I ran a sample prompt and bolt executed the first command:
Run command
npx create-next-app@latest youtube-clone --typescript --tailwind --eslint --app --src-dir --import-alias "@/*" && cd youtube-clone && npm install @heroicons/react date-fns
Bolt get stuck over this because the create next app command is waiting for a response
Console reads:
? Would you like to use Turbopack for next dev? › No / Yes
There is no way to input a response
Link to the Bolt URL that caused the error
http://<IP_ADDRESS>:3000/
Steps to reproduce

Start the development server or build the app
Run this prompt

> Build a YouTube clone with a modern UI using Next.js, TypeScript, App Router, and Tailwind CSS. Include core features:
>
> 1. Video grid layout with thumbnails and metadata 2. Video player page with title, description, and comments 3. Search functionality 4. Responsive design for mobile/desktop 5. Dark mode support 6. Video categories/filters 7. View count and timestamp display Use the following command to create the project:
> After setup, implement the features step-by-step, focusing on clean code architecture and best practices for Next.js and TypeScript.[object Object][object Object]

Bolt will return this

Certainly! I'll create a YouTube clone with the features you've requested using Next.js, TypeScript, App Router, and Tailwind CSS. Let's set up the project and implement the features step-by-step.
YouTube Clone with Next.js, TypeScript, and Tailwind CSS
Click to open Workbench
Run command
npx create-next-app@latest youtube-clone --typescript --eslint --tailwind --app --src-dir --import-alias "@/*" --use-npm && cd youtube-clone && npm install @heroicons/react

Expected behavior
Bolt must continue the process without waiting for an input
Screen Recording / Screenshot

Platform

OS: MacOS
Browser: Chrome Canary

Additional context
No response

Can confirm, redproducibly hangs for me too at this step when creating a Next App. I was able to circumvent this limitation by asking it to manually create the app in the prompt, avoiding ´create-next-app´:
Build a text-based role-playing game using Next.js, TypeScript, App Router, and Tailwind CSS. Include features like character creation, turn-based combat, inventory management, and a simple storyline. Implement state management for game progress and use server-side rendering for improved performance.

Avoid using ´create-next-app´ but create the required files and folder layout yourself instead.

Certainly the LLM should be calling these tools in a non-interactive mode, but alternatively, the (tool) prompt requiring user input should be displayed in the webContainer terminal where h user can respond to the waitig prompt, without having to reproduce the command entirely.
The solution is probably twofold:

prompt enginering
terminal integration within webContainers (to handle outliers gracefully)


Add password textbox option to Notifier

From the power users: Notifier could benefit from having an option to prompt for a password. Currently, one can only prompt for plaintext.

@ewpatton @josmas thinking of tackling this one. Is this the file I should look at?

Hey @kuan9611 that seems to be the right place.

@kuan9611 This post may also be relevant via StackOverflow.

@ewpatton @josmas PR here


[vtk] Build error

Host Environment

OS: win10
Compiler: vs2019

To Reproduce
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:112 (message):
Command failed: "C:/Program Files (x86)/Microsoft Visual Studio/2019/Enterprise/Common7/IDE/CommonExtensions/Microsoft/CMake/Ninja/ninja.exe" -v
Working Directory: D:/vcpkg/buildtrees/vtk/x64-windows-rel/vcpkg-parallel-configure
Error code: 1
See logs for more information:
D:\vcpkg\buildtrees\vtk\config-x64-windows-dbg-CMakeCache.txt.log
D:\vcpkg\buildtrees\vtk\config-x64-windows-rel-CMakeCache.txt.log
D:\vcpkg\buildtrees\vtk\config-x64-windows-out.log
Call Stack (most recent call first):
installed/x64-windows/share/vcpkg-cmake/vcpkg_cmake_configure.cmake:247 (vcpkg_execute_required_process)
ports/vtk/portfile.cmake:153 (vcpkg_cmake_configure)
scripts/ports.cmake:147 (include)
error: building vtk:x64-windows failed with: BUILD_FAILED
error: Please ensure you're using the latest port files with git pull and vcpkg update.
Then check for known issues at:
https://github.com/microsoft/vcpkg/issues?q=is%3Aissue+is%3Aopen+in%3Atitle+vtk
You can submit a new issue at:
https://github.com/microsoft/vcpkg/issues/new?template=report-package-build-failure.md&title=[vtk]+Build+error
Include '[vtk] Build error' in your bug report title, the following version information in your bug description, and attach any relevant failure logs from above.
vcpkg-tool version: 2022-12-14-7ae0d8527fb488fde10a89c2813802dc9b03b6f9
vcpkg-scripts version: d40bedd6f 2023-01-11 (5 hours ago)
Steps to reproduce the behavior:
.\vcpkg.exe install vtk[all]:x64-windows
Failure logs
-- Found SQLite3: D:/vcpkg/installed/x64-windows/include (found version "3.40.0")
-- VTK module debug building: VTK::IOSQL is being built
-- VTK module debug building: VTK::TestingIOSQL is being built
-- VTK module debug building: VTK::TestingGenericBridge is being built
-- VTK module debug building: VTK::FiltersAMR is being built
-- VTK module debug building: VTK::RenderingVolumeAMR is being built
-- VTK module debug building: VTK::RenderingRayTracing is being built
CMake Warning at D:/vcpkg/scripts/buildsystems/vcpkg.cmake:843 (_find_package):
By not providing "Findospray.cmake" in CMAKE_MODULE_PATH this project has
asked CMake to find a package configuration file provided by "ospray", but
CMake did not find one.
Could not find a package configuration file provided by "ospray" (requested
version 2.1) with any of the following names:
osprayConfig.cmake
ospray-config.cmake

Add the installation prefix of "ospray" to CMAKE_PREFIX_PATH or set
"ospray_DIR" to a directory containing one of the above files.  If "ospray"
provides a separate development package or SDK, be sure it has been
installed.
Call Stack (most recent call first):
CMake/vtkModule.cmake:4222 (find_package)
Rendering/RayTracing/CMakeLists.txt:58 (vtk_module_find_package)
CMake Error at CMake/vtkModule.cmake:4228 (message):
Could not find the ospray external dependency.
Call Stack (most recent call first):
Rendering/RayTracing/CMakeLists.txt:58 (vtk_module_find_package)
-- Configuring incomplete, errors occurred!
See also "D:/vcpkg/buildtrees/vtk/x64-windows-dbg/CMakeFiles/CMakeOutput.log".
See also "D:/vcpkg/buildtrees/vtk/x64-windows-dbg/CMakeFiles/CMakeError.log".
ninja: build stopped: subcommand failed.

Duplicate of https://github.com/microsoft/vcpkg/issues/25579.


make sure Sequence.any and Sequence.all always return boolean values

previous behaviour was returning the first falsy value or the last value for all / opposite for any

If you want to go this way, you can simplify more removing the result
variable. And don't forget to update the .inc.
Previous behavior was interesting as it was combining searching and mapping
the result for free. This need behavior, seems a little bit incomplete,
returning an iterator to the first falling iterator is also an interesting
behavior.

the new behaviour is more predictable in my eyes and mirrors more closely how its documented in the docs
and yeah, I moved the variable in the for loop since its not needed afterwards anymore, but I believe its more readable to have a intermediate variable here than to squish it into the if condition

Performance wise I think, it should be more efficient to remove the
variable completely. Since the compiler does not do any analysis, in fact
having the variable inside the loop force variable creation/destruction on
each loop. So either let the variable outside or remove it completely.

both those ideas make the code slightly less readable and less consistent with the rest of the code
String.trim_ also has a variable in a loop iteration thats only used once and is stored for convenience


Wireguard adds endpoint host to routing list without need.

I tried to setup router as WG client for a while. But it doesn't work on my setup.
After research, I realized that licu-wireguard application adds a static route somehow.
After removal of non needed record of endpoint from routing table (51.x.x.x in my setup), Wireguard starts working proper.
root@MainRouter:~# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default         <IP_ADDRESS>     <IP_ADDRESS>         UG    0      0        0 eth0.2
<IP_ADDRESS>        *               <IP_ADDRESS>   U     0      0        0 wg0
51.x.x.x        MainRouter.lan  <IP_ADDRESS> UGH   0      0        0 br-lan
<IP_ADDRESS>     *               <IP_ADDRESS>   U     0      0        0 br-lan
<IP_ADDRESS>     *               <IP_ADDRESS>   U     0      0        0 eth0.2

PS: MainRouter.lan is name of the router. (<IP_ADDRESS>)

Please report this against the OpenWrt wireguard package. LuCI is only the ui frontend to it.


SW-5657 Added deliverable and deliverable edit view to application

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#2898  👈
#2897
#2895
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @tommylau523 and the rest of your teammates on  Graphite

Merge activity

Jul 25, 7:03 PM EDT: @tommylau523 merged this pull request with Graphite.


ArrayNodes which reference another node are returned as Strings when schema is generated.

Expected Behaviour
Arrays should remain arrays when referenced
Actual Behaviour
Returned as strings
Reproduce Scenario (including but not limited to)
Steps to Reproduce
Create schema with node which references another array node as it's value
Platform and Version
All
Sample Code that illustrates the problem
Logs taken while reproducing problem

Fixed


Maximum function count limitation when initializing a new session

When creating a new session that imports modules and defines new functions, the number of allowed functions is limited to the default maximum count (4096).  This count value is reflected by the $MaximumFunctionCount built-in variable which can be modified.  But this doesn't help much during session initialization unless you have the foresight to include in one module an entry that sets the $MaximumFunctionCount variable.
During runspace binding on session initialization the number of defined functions and variables should not be limited to the default value.  Instead the session maximum count variables should be adjusted to accommodate.

Fixed by #2363


Update artifact tarball when spec.ignore changes

This commit adds a new field status.artifact.excludedPatternsChecksum which is used to detect changes on spec.ignore, that controls the exclusions for the object's status.artifact.
Fix: https://github.com/fluxcd/source-controller/issues/704

Hi, thanks for proposing this solution. Sharing a few thoughts about it:

Maybe it'd be better to not mix the terms. The spec has it as ignore, it'd be better to call the new field with the same name.
Ignore is an attribute of GitRepo and Bucket only. Adding the checksum field as part of artifact exposes it to all the other source types. Maybe it'd be better to introduce it in the status of GitRepo and Bucket only. There's already status.includedArtifacts in GitRepo. Maybe we could have ignored informtion there as well.

@darkowlzz you are pretty much reflecting my thoughts in https://github.com/fluxcd/source-controller/pull/710 :-)

Hey everyone! Thanks for the feedback!
I updated the PR with your suggestions. Please let me know if you see any other improvements.

Please rebase with upstream main, we've fixed the e2e tests.

Could you also update the spec docs in https://github.com/fluxcd/source-controller/tree/main/docs/spec/v1beta2 for both GitRepo and Bucket in the Status section towards the bottom of the docs with some documentation for the checksum field?

Hi guys, thanks for the support!
Please, let me know if you see any other improvements.

Hi, due to some recent changes in the main branch, we had to restructure a lot of the code in GitRepo reconciler. A rough work on fixing that is in https://github.com/fluxcd/source-controller/compare/gitrepo-rec-fixes . It changes how we figure out if the source needs to be reconciled completely or not, similar to detecting changes to spec.ignore in this PR. The new work introduces a contentConfigChecksum field in the API, which includes the ignore value and many other fields that contribute to a new artifact to be built https://github.com/fluxcd/source-controller/compare/gitrepo-rec-fixes?expand=1#diff-4472354d9c6813ee6537b2625d7aa7eef2522f48bc45548c1397f207ff85cbc9R214-R223 .
I'd recommend to wait for that change to be finalized and merged first, and then based on those changes, add a similar change for the Bucket reconciler for detecting ignore + all other config changes.
Sorry for this. It wasn't planned before but the solution to fixing other stuff covers the issue that this PR tries to fix.

@angelokurtis flux v0.31.0 was just released with the aforementioned improvements in the GitReporeconciler. Your initial issue https://github.com/fluxcd/source-controller/issues/704 is closed. But you can still add a similar change in the Bucket reconciler based on the GitRepo reconcile change in https://github.com/fluxcd/source-controller/commit/581695b4d621fccb9b6a264b5dbcedf97151cec0. We can introduce the same field contentConfigChecksum in the status of a Bucket object and use it to detect changes. This may also result in restructuring some parts of the Bucket reconciler, but I think that's okay. Feel free to ask any questions about it that you may have.

Superseded by #926


Allow LogWriter to pass down attributes/metadata

Datadog has a concept of "attributes", Bugsnag has a concept of "metadata". Both are very helpful for performing advanced telemetry - for example correlating traces with logs. Right now, Kermit doesn't seem to provide a way to log attributes/metadata.

Sorry for the delay here. A lot of these get bumped with "we'll look at it when we get done with ___", and there's always another ___.
Moving to discussions as well. Anyway...
The issue here is API design. Kermit is attempting to provide a common logging API that can reasonably be adapted to downstream logging systems. That makes the decision about what to include and not include somewhat difficult. For example, most logger implementations don't have a tag parameter. Android, however, does, and since the bulk of KMP editing is done by Android devs, generally speaking, not having tag would be a problem. Similarly, most logging systems have a concept of severity, but they don't all have the same levels.
For attributes and metadata, you start to leave the conceptual world of "logger" and move more to "telemetry". Adding a log writer to Kermit to write telemetry log strings makes sense, but adding other features of telemetry systems to a logger starts to feel more like there should be a common telemetry API that calls out to Kermit if needed, rather than the other way around.
Currently, for Crashlytics and Bugsnag specifically, to add this kind of data, you can just call out to CrashKiOS directly. I'm definitely not an expert in the telemetry domain, so if various systems attached metadata directly to the log statement itself, that approach wouldn't quite work.


File read

Hey,
Are you planning on adding standalone aep/aepx file to json & json -> aep/aepx file tools ?
And possibly a tool for creating aep/aepx projects using json from scratch.

No plans for this.


Question on the way implicit objectness is combined with class logits

https://github.com/chensnathan/YOLOF/blob/a44b7af0efa9b89d3e91db70bc9a39e49d5d0144/yolof/modeling/decoder.py#L105
Could you please explain why implicit objectness is combined with class logits like this? Thanks.

I have the same question, according to the paper, it should be multiply.


[Stack] component prop not available

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯
The <Stack /> component does not have a component prop. It will always return as a <div />.
Expected Behavior 🤔
Like almost every component in material-ui, there should be a component prop.

Your Environment 🌎

`npx @material-ui/envinfo`
browser used: Edge latest version
  System:
    OS: Windows 10 10.0.19042
    CPU: (8) x64 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz
    Memory: 21.79 GB / 31.73 GB
  Binaries:
    Node: 15.12.0 - C:\Program Files\nodejs\node.EXE
    npm: 7.6.3 - C:\Program Files\nodejs\npm.CMD
  Managers:
    pip3: 20.2.3 - C:\Python39\Scripts\pip3.EXE
  Utilities:
    Git: 2.31.0.
  IDEs:
    VSCode: 1.54.3 - C:\Users\matth\AppData\Local\Programs\Microsoft VS Code\bin\code.CMD
  Languages:
    Python: 3.9.2
  Browsers:
    Edge: Spartan (44.19041.423.0), Chromium (89.0.774.57)
    Internet Explorer: 11.0.19041.1

@matthewkwong2 Thanks for opening this issue. Yes, this is a hard requirement for this CSS utility component. The types are actually already designed to accept a component prop. The fix should be as easy as:
diff --git a/packages/material-ui/src/Stack/Stack.js b/packages/material-ui/src/Stack/Stack.js
index e4359933a5..81be5ed974 100644
--- a/packages/material-ui/src/Stack/Stack.js
+++ b/packages/material-ui/src/Stack/Stack.js
@@ -102,14 +102,14 @@ const StackRoot = experimentalStyled('div', {}, { name: 'Stack' })(style);
 const Stack = React.forwardRef(function Stack(inProps, ref) {
   const themeProps = useThemeProps({ props: inProps, name: 'MuiStack' });
   const props = extendSxProp(themeProps);
-  const { direction = 'column', spacing, divider, children, ...other } = props;
+  const { component = 'div', direction = 'column', spacing, divider, children, ...other } = props;
   const styleProps = {
     direction,
     spacing,
   };

   return (
-    <StackRoot styleProps={styleProps} ref={ref} {...other}>
+    <StackRoot as={component} styleProps={styleProps} ref={ref} {...other}>
       {divider ? joinChildren(children, divider) : children}
     </StackRoot>
   );
@@ -124,6 +124,11 @@ Stack.propTypes /* remove-proptypes */ = {
    * The content of the component.
    */
   children: PropTypes.node,
+  /**
+   * The component used for the root node.
+   * Either a string to use a HTML element or a component.
+   */
+  component: PropTypes.elementType,
   /**
    * Defines the `flex-direction` style property.
    * It is applied for all screen sizes.

Do you want to take on this issue?

Do you want to take on this issue?

@oliviertassinari I'm not familiar with how open source projects usually work. Do you wish me to fork the repository and open a pull request?

@matthewkwong2 This sounds about right, it would be great. Note that we would also likely need to run the scripts to update the documentation. The CI will let you know what are these scripts in questions.

assign this to me!

@silver-snoopy is already on it

@silver-snoopy is already on it

As this task was not assigned to anyone, so I thought I am free to give a PR. I didn't see your text, because I was busy editing the file.


[FEATURE REQUEST] Refactor merging Ansible variables

Is your feature request related to a problem? Please describe.
For upgrade mode, we use variables from a few sources:

manifest.yml - settings used for epicli apply but merged with current default configuration
main.yml - may contain only current default configuration or configuration provided by user but merged with current default configuration

Such logic has the following drawbacks:

Due to merging it's not possible to easily check which settings are from apply mode and which are current defaults
Due to merging it's not possible to check which settings were provided by user via config file (using -f flag)
Due to merging we have in main.yml many settings that are not supported/used in upgrade mode
main.yml is loaded automatically by Ansible at top level

Describe the solution you'd like
The var directory may contain the following files:

manifest.yml - contains only unmodified config from the last apply run (no merging); generated only for specified roles (to safe time)
defaults.yml - contains current default configuration, it may be used during upgrade to get default values for new settings; it seems there is no need to generate them automatically for all roles
main.yml - probably only for common role since it's not configurable
upgrade-config.yml - exists only when -f flag was used, settings provided by user that are supported in upgrade mode, they will override settings from other sources
manifest_merged_with_defaults.yml - optionally, equivalent of current manifest.yml, for backward compatibility - to avoid risky/breaking changes, treated as deprecated and to be removed in the future

Describe alternatives you've considered
n/a
Additional context
Feature needed for PostgreSQL upgrade.

DoD checklist

Changelog

[ ] updated
[ ] not needed

COMPONENTS.md

[ ] updated
[ ] not needed

Schema

[ ] updated
[ ] not needed

Backport tasks

[ ] created
[ ] not needed

Documentation

[ ] added
[ ] updated
[ ] not needed

[ ] Feature has automated tests
[ ] Automated tests passed (QA pipelines)

[ ] apply
[ ] upgrade
[ ] backup/restore

[ ] Idempotency tested
[ ] All conversations in PR resolved
[ ] Solution meets requirements and is done according to design doc
[ ] Usage compliant with license

Not going todo anymore feature requests for Epiphany.


No module named 'mobile'sam'

All parts of installation are working for me until trying to start the sam_server I'm getting the error message:
"from mobile_sam import sam_model_registry as sam_model_registry_mobile
ModuleNotFoundError: No module named 'mobile_sam'"

All parts of installation are working for me until trying to start the sam_server I'm getting the error message: "from mobile_sam import sam_model_registry as sam_model_registry_mobile ModuleNotFoundError: No module named 'mobile_sam'"

pls check here to install the mobile_sam dependency.


Add Ubuntu 20.04 (Focal) support

This branch is an attempt to add support for Ubuntu 20.04 LTS to our Packer and Ansible builds. Since this will be the first Ubuntu LTS upgrade within Mint since we started automating the builds, it had the potential to be a large effort to support. In the end, it was fairly minimal, but it forced some clarification between Mint and Ubuntu content.
It is not my intention for the UUG to start offering two images and a choice at InstallFests. This is solely being proposed so that we have a common target to develop for the next Mint release in a timely manner.
Every time I review these changes, I find more that I can't believe slipped my eye earlier, so I don't commit to them being done yet, but it's time to open them for public comment. I reserved the right to overwrite history and force push, especially while this remains in draft status.

Close enough. I still want to fiddle with kernel setup, but I also want to eventually get something merged. Someone ok this, plz.

Ok.
(Oh, you meant someone with approval power, I assume.)
On Thu, May 28, 2020 at 9:30 PM Mike Ripley<EMAIL_ADDRESS>wrote:

Close enough. I still want to fiddle with kernel setup, but I also want to
eventually get something merged. Someone ok this, plz.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/jmunixusers/cs-vm-build/pull/383#issuecomment-635704667,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAL3UHYFVUQ2W3SRK6EAZATRT4F4VANCNFSM4M5OKUHQ
.

--
Seth