'dict' object cannot be interpreted as an integer

I tried to reproduce the code for training on vcoco dataset, but there was a problem, and the error message was as follows:
`Traceback (most recent call last):
File "main.py", line 322, in
main(args)
File "main.py", line 269, in main
args.clip_max_norm, args.model_name)
File "/media/wit-2080/72e8833a-507d-4969-9f18-1fd1ff669f74/WTL/DOQ-main/engine.py", line 43, in train_one_epoch
for samples, targets in metric_logger.log_every(data_loader, print_freq, header):
File "/media/wit-2080/72e8833a-507d-4969-9f18-1fd1ff669f74/WTL/DOQ-main/util/misc.py", line 228, in log_every
for obj in iterable:
File "/home/wit-2080/anaconda3/envs/pytorch1.7.1/lib/python3.7/site-packages/torch/utils/data/dataloader.py", line 435, in next
data = self._next_data()
File "/home/wit-2080/anaconda3/envs/pytorch1.7.1/lib/python3.7/site-packages/torch/utils/data/dataloader.py", line 1085, in _next_data
return self._process_data(data)
File "/home/wit-2080/anaconda3/envs/pytorch1.7.1/lib/python3.7/site-packages/torch/utils/data/dataloader.py", line 1111, in _process_data
data.reraise()
File "/home/wit-2080/anaconda3/envs/pytorch1.7.1/lib/python3.7/site-packages/torch/_utils.py", line 428, in reraise
raise self.exc_type(msg)
ValueError: Caught ValueError in DataLoader worker process 0.
Original Traceback (most recent call last):
File "mtrand.pyx", line 905, in numpy.random.mtrand.RandomState.choice
TypeError: 'dict' object cannot be interpreted as an integer
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/wit-2080/anaconda3/envs/pytorch1.7.1/lib/python3.7/site-packages/torch/utils/data/_utils/worker.py", line 198, in _worker_loop
data = fetcher.fetch(index)
File "/home/wit-2080/anaconda3/envs/pytorch1.7.1/lib/python3.7/site-packages/torch/utils/data/_utils/fetch.py", line 44, in fetch
data = [self.dataset[idx] for idx in possibly_batched_index]
File "/home/wit-2080/anaconda3/envs/pytorch1.7.1/lib/python3.7/site-packages/torch/utils/data/_utils/fetch.py", line 44, in
data = [self.dataset[idx] for idx in possibly_batched_index]
File "/media/wit-2080/72e8833a-507d-4969-9f18-1fd1ff669f74/WTL/DOQ-main/datasets/vcoco.py", line 50, in getitem
random_index = [idx] + get_sim_index(sim_im_num, self.nohoi_index, self.sim_index[idx])
File "/media/wit-2080/72e8833a-507d-4969-9f18-1fd1ff669f74/WTL/DOQ-main/datasets/stitch_images.py", line 51, in get_sim_index
random_index = np.random.choice(sim_index, sample_num, replace=True)
File "mtrand.pyx", line 907, in numpy.random.mtrand.RandomState.choice
ValueError: a must be 1-dimensional or an integer`
The experimental environment I adopted was Ubuntu16.04, Python3.7, Pytorch1.7.1, and the hardware device I used was 2080ti GPU*2, batchsize 2 per GPU. I tried training QPIC in the same environment and everything worked. I have tried to download annotations from Google Drive 3 times for training, so I can rule out the network problems caused by the tag file damaged during the download. According to the code, I inferred that there was a problem with pictures. I used complete COCO2014train /val in the data set and screened only pictures with vcoco tags. The same error occurred in the two types of data sets, which can run normally on QPIC. I want to know how to solve this problem. I m looking forward to your reply. Thank you again for your help.

It seems that sim_index is not a 1-dimensional  array. can your print the sim_index before the line 51 in get_sim_index?

It seems that sim_index is not a 1-dimensional array. can your print the sim_index before the line 51 in get_sim_index?

Thank you for your reply. I tried to print out sim_index before line51, but I found the following error and could not print the sim_index:
def get_sim_index(sample_num, nohoi_index, sim_index):
    for i in range(len(nohoi_index)):
        if nohoi_index[i] in sim_index:
            sim_index.remove(nohoi_index[i])
    print("+++++++++++++++++++++++++++++++")
    print("sim_index")
    print("+++++++++++++++++++++++++++++++")
    random_index = np.random.choice(sim_index, sample_num, replace=True)
    return list(random_index)

The same error has been encountered with this notation and cannot display the sim_index content
def get_sim_index(sample_num, nohoi_index, sim_index):
    print("+++++++++++++++++++++++++++++++")
    print("sim_index")
    print("+++++++++++++++++++++++++++++++")
    for i in range(len(nohoi_index)):
        if nohoi_index[i] in sim_index:
            sim_index.remove(nohoi_index[i])
    random_index = np.random.choice(sim_index, sample_num, replace=True)
    return list(random_index)

This way the program will get stuck and cannot display the sim_index content.
I infer from the paper that the code in this part may be related to the stitching way in the process of data enhancement, I don't know whether it is correct.I m looking forward to your reply. Thank you again for your help.

print(sim_index) instead of print("sim_index"), make sure your load the correct pickle file.
if the sim_index is not a 1-dimensional array , your can check the self.sim_index have load pickle file in vcoco.py

print(sim_index) instead of print("sim_index"), make sure your load the correct pickle file. if the sim_index is not a 1-dimensional array , your can check the self.sim_index have load pickle file in vcoco.py

Thank you for your reply.The above error was caused when I typed the issue, the actual code has no corresponding error, and the result is the same as described. In addition, we tried to print it in vcoco. py, modified as follows
    def get_sim_index(self):
        self.sim_index = pickle.load(open('data/v-coco/annotations/sim_index_vcoco.pickle', 'rb'))
        print("==========================================")
        print(self.sim_index)
        print("==========================================")

and the result shows
{'index': [4203, 4578, 2105, 4532, 3951, 3016, 5194, 4662, 1703, 2220, 1092, 990, 596, 3723, 515, 4658], 'cos': array([1.        , 0.8254187 , 0.80570924, 0.80315   , 0.79597265,
       0.7808205 , 0.7796549 , 0.7756003 , 0.773574  , 0.7721612 ,
       0.7712145 , 0.7696761 , 0.769509  , 0.76844037, 0.76691663,
       0.765468  ], dtype=float32)}, {'index': [4204, 1333, 1340, 3350, 1458, 4480, 2461, 798, 3214, 2198, 3712, 764, 3487, 3894, 860, 981], 'cos': array([1.        , 0.8411544 , 0.84098417, 0.83964956, 0.83717054,
       0.8365972 , 0.83565295, 0.8346963 , 0.82870823, 0.8275825 ,
       0.8273761 , 0.8264537 , 0.82584995, 0.8244393 , 0.8241825 ,
       0.8235995 ], dtype=float32)},

Sorry, we found that we provided the wrong file, the file link will update soon!

the correct file is uploaded

Sorry, it is a bug casued by incorrect file "sim_index_vcoco.pickle" and it actually only include 'index'(this is why report TypeError: 'dict' object cannot be interpreted as an integer and ValueError: a must be 1-dimensional or an integer). The correct file will be uploaded soon. Thank you for finding this bug!

Thank you for your reply. Everything is fine after replacing the new one sim_index_vcoco.pickle

Sorry, we found that we provided the wrong file, the file link will update soon!

Thank you for your reply. Everything is fine after replacing the new one sim_index_vcoco.pickle。
In addition, I would like to know what the parameters in sim_index_vcoco.pickle represent, and would appreciate for some explanation. We have seen a similar prior.pickle in qpic and still don't know its meaning after printing.
Thank you again for your help. And I look forward to your reply!


How to set environment variables or pass structure data when submitting job?

Organization Name: Private Test
Short summary about the issue/question:
How to set environment variables or pass structure data when submitting job?
I used to use jobEnv to set structure like:
  "jobEnvs": {
    "TASK_NAME": "the_task",
    "USER_NAME": "someone",
    "JOB_TYPE": [
      "train",
      "test"
    ],
    "trainSets": [
      "xxx", "yyy"
    ],
    "extra_config": {
      "ROOT_DIR": "/opt/outputs",
      "TRAIN": {
        "MAX_ITER": 1
      }
    }
  }

But I can not find any doc or code to submit with jobEnv in v0.14.0.
OpenPAI Environment:

OpenPAI version: v0.14.0

Thanks!

if you want to use v2 api, pls refer to parameters in protocol spec

@abuccts  It seems that parameters can be accessed YAML value when submitting job. But the trouble I met is that I wanna access the value inside the running job or container.

You can either add arguments for your code to accept those parameters,
main.py --root-dir <% $parameters.root_dir %> --max-iter <% $parameters.max_iter %>

or use a JSON string (e.g. json.dumps in py) as a parameter and export to env/write to file by yourself.
parameters:
  env: '{"jobEnvs": {"TASK_NAME": "the_task", "USER_NAME": "someone", "JOB_TYPE": ["train", "test"], "trainSets": ["xxx", "yyy"], "extra_config": {"ROOT_DIR": "/opt/outputs", "TRAIN": {"MAX_ITER": 1}}}}'
...
commands:
- export CONFIG=<% $parameters.env %>

@abuccts , So much for the help, and it helps a lot.
And could you please add a new feature when submitting new job(v2), which may directly set the environment. I love jobEnvs in v1.
Thanks again!

we may do it via a kube runtime plugin, which could export such parameters to env


review climate data

Our latest plot of the climate data has some obviously wrong values, including a strange line of data and a handful that are out of range. I assume these came in with GROA or maybe SRDB (I think it's been a long time since I've looked at this figure).

Ummmm I've never seen anything like that in the SRDB data 🤔 but 🤷♂

Ummmm I've never seen anything like that in the SRDB data 🤔 but 🤷♂

I just checked and it was not there after we added SRDB. So, it presumably comes from GROA.

I just checked and it was not there after we added SRDB. So, it presumably comes from GROA.

Phew :)

Phew :)

There appears to be some bad data from Taylor_2017_tari: very low precip for at least 4 sites in India (Kodayar)

I believe that strange line of data comes mostly or entirely from Xu_2015_proa, imported via GROA. I don't see an explanation in the paper as to climate data source, but study system includes 164 plots spanning elevation gradient, so presumably climate is extrapolated as a function of elevation. I'm not sure if this is the most accurate possible for that location, but at least we have an explanation. I haven't verified against original data yet, but it seems unlikely that this is an error in GROA or ForC.

@teixeirak yes, that's an error - the intermediate data sheet is in this folder - it's the litterfall data file, and by the looks of things I just accidentally copied across the values from the adjacent column.
I've corrected in ForC_sites
Are there any others that look out?

Many thanks, @beckybanbury , and sorry to ping you on a weekend. No need to respond right away. (I'm pushing to solve some problems for a deadline this week, but we can just avoid questionable records at this point.)
It's hard to say if everything looks right now.  Taylor 2017 has a number of records with very high precip, and so I started trying to check some. I verified that one was correct  (Swer) but found one error (Wooroonooran National Park Bellenden Ker). Then, I got caught up trying to understand what's going on with the La Fortuna Forest Reserve, which has 5 sites with identical coordinates but different climate entered, but only seems to have one site when you go to the original pub. That will need to be solved, but I have to drop it for now.

I have reviewed the most egregious outliers. However, there are almost certainly some errors. It would be good to check the ForC climate data against a global database to identify values that are way off (e.g., units error during data entry).

@teixeirak happy to help with this if you'd like, particularly the data from Taylor 2017 that I entered - I remember reviewing some of the C flux values that looked off at the time, but didn't check climate data so closely. Happy to spend some time reviewing if you'd like - just let me know how you want to approach this!

Thanks, @beckybanbury. I sent an email about this. More narrowly, figuring out what's going on with La Fortuna (see here) would be helpful.

@beckybanbury , thanks for working on this!
Based on the plots, let's flag sites "climate.data.suspect" if any of the following are true:

temperature difference > 5C
warmest or coldest month difference > 7.5C
log(precip) difference >1

You could just flag with a "1", or better yet list the variable(s) that is/are off.

@beckybanbury , if you're able to complete the step above this week while @Troger4 is still with us, she could check the climate values that are way off.

@teixeirak sorry - somehow I missed your previous comment! I've flagged with the name of the variable that is suspect. It doesn't look like there's too many.

@Troger4 , please use the climate.data.suspect field in this file to identify the sites with suspicious climate data. It is coded to indicate which value is bad. When one value is bad, but please double check the others. In case the original pub does not report climate data, please replace the bad value with "NI".

Also note: this file and the master ForC_sites DO NOT MATCH because sites missing coordinates are not included in the former.
Also,  please create a new column in this file to note when you've reviewed the climate data.

@mawilliams99 , this is an issue that you can get started on as an intro to the ForC data work.
There's a lot of discussion above, but summarizing here--

We (specifically Becky Banbury Morgan, @beckybanbury ) identified some climate records in ForC (sites.csv) that are very different from values pulled from a global database. We'll want to go back to the original publications to check those.
Climate data are in the file sites.csv (https://github.com/forc-db/ForC/blob/master/data/ForC_sites.csv). The metadata files explaining each field in the SITES table is here: https://github.com/forc-db/ForC/blob/master/metadata/sites_metadata.csv.
Sites with suspect data are flagged in the climate.data.suspect field in this file  (https://github.com/forc-db/ForC/blob/master/data/extracted_site_data/ForC_sites_climate_data.csv).  It is coded to indicate which value is bad. When one value is bad, but please double check the others. In case the original pub does not report climate data, please replace the bad value with "NI" (missing value code for "no information").

I'll message you separately to make sure this makes sense.

@mawilliams99 or @ValentineHerr , this should be a quick task-- could one of you please merge the field climate.data.suspect field in this file  (https://github.com/forc-db/ForC/blob/master/data/extracted_site_data/ForC_sites_climate_data.csv) into the corresponding field in the master sites file? (The difference between the two is that the master includes a few sites with no coordinates.)  The motivation for this is that reviewing the climate data doesn't have to happen with high priority, but we want to be sure to review any suspect data on sites we may send to EFDB.

I'll work on this now

Looks like Yenisei 2lu and Yenisei 26lh/lw are missing from the file (beside sites without latitudes).
I'll go ahead and merge anyways as I believe that you (@teixeirak) have been working with this site recently.

Thanks! This is very helpful.
Those two sites would be very similar to the other Yenisei sites, which don't have suspect data, so this is fine.
@mawilliams99 , please be sure to check the climate.data.suspect field in sites for all the studies that you review. We should avoid sending any of those values to EFDB (better to replace with NA, unless there's some really good reason to believe that the current data are correct (e.g., steep topographic gradients that would make the site quite different from most of the surrounding areas)


[BUG] StorageInputStream::reset function throw Stream mark expired. when invoking reset method

Hi
I am using azure storage version 12.28.1 (azure storage common version 12.27.1)
When try to use inputstream used by blobClient.openInputStream we got inputstream from type StorageInputStream
Calling to reset of this stream throw "Stream mark expired"
Attached content of the reset method.
public synchronized void reset() {
if (this.markedPosition + this.markExpiry < this.currentAbsoluteReadPosition) {
throw LOGGER.logExceptionAsError(new RuntimeException(MARK_EXPIRED));
}
this.reposition(this.markedPosition);
}
Could you please let me know what needs to be done that reset should be work.
I am using another code that invoke the reset method
Thanks,
Itay

Hi @ihudedi could you please include the full call stack (similar to https://github.com/Azure/azure-sdk-for-java/issues/31924) so that the storage team may better assist you?
/cc @ibrahimrabab


Follow symlinks to the real location of path.txt

This change ensures that the script can always find the correct location of paths.txt, even when the script is executed from a symlink.
Example:
Symlink in question:
lrwxrwxrwx 1 user users 57 Jul 21 13:38 cloud_config_workaround -> .tools/cloud_config_workaround/cloud_config_workaround.sh

Before proposed change, with symlink execution (incorrect PATHS_FILE value):
./cloud_config_workaround
/home/user/bin/paths.txt

After proposed change, with symlink execution (correct PATHS_FILE value):
./cloud_config_workaround
/home/user/bin/.tools/cloud_config_workaround/paths.txt

Thanks!


Drag-Panning breaks when disabling PinchableScrollRect while dragging

Reproduction steps:

Set up a PinchableScrollRect in a window that you can show/hide (e.g. gameObject.SetActive()) at the press of a key (e.g. hide it with Esc)
show the window
start dragging around with your mouse to pan. Without releasing the mouse button, press Esc (or whichever key you designated to disabling the GameObject containing the PinchableScrollRect) to close the window
show the window again
dragging to pan doesn't work anymore.

The PinchableScrollRect will remain stuck in this state. If you hold down your mouse button and press Esc again, and then open it again, the first drag-pan will work - but after that it will stop working again.
I checked the code, and I think it has to do with the way that PinchableScrollRect.OnPinchStart and OnPinchEnd call base.OnEndDrag and base.OnBeginDrag respectively. This leads to states where, after releasing the mouse button, ScrollRect.m_Dragging remains true.
Thanks for this awesome component! Except for this behaviour, it works really well and feels great to interact with.

Thank you for the report. Will take a look on this.


Add support for phar

This patch will add support for creating an phar for each new release.
The intention behind this pull request is to be able to use an phar instead of the composer dependency to fulfill the task of uploading the generated coverage report.
Things that need to be done:

[x] To be able to add the created phar during the travis build to the release, an github api access token has to be added to the travis.yml. Please provide me an encrypted github access token so i can update this pull request.

See https://docs.travis-ci.com/user/deployment/releases/ and https://docs.travis-ci.com/user/environment-variables/#Defining-encrypted-variables-in-.travis.yml for further details.
Please let me know if i could provide any further details.

@MaSpeng thanks for your contribution.
The pr looks good, just needs some adjustments. You added this installation alternative in the beginning and since this is an alternative and not the recommended way it should be after the current one.
The other detail is the deploy. Would it be possible to do it in CircleCI? We do not use travis for our builds. In this case we only have it in this project to have an example.

@rtfpessoa I updated the readme and moved the instruction at the end of the installation description.
Regarding the upload of the created phar using CircleCi, as far as i could find out it should be possible.
See an small example how it should work: https://gist.github.com/AGmakonts/ef49d60ea09daed210ef47812b9d03b6
Currently i haven't access to CircleCi as an build environment so i am unable to create an test for the required configuration. You might help me with that?
Otherwise i could remove the changes from the travis configuration.

@rtfpessoa I reverted the changes to the travis ci configuration and updated the CircleCi configuration to create an phar on creating an new release/tag. It will create the phar and upload it to the github release archive.
If not already done, an environment named GITHUB_TOKEN with an token wich as access to the repository has to be added to the CircleCi project settings.
I have successfully tested it with an free account from CircleCi.

I just added the key to the CircleCI environment. I will merge this an see if it works.
Can you just add a title before the instructions in the readme like: Alternative Installation (using phar)

@MaSpeng I will have to rever this back. I did not completely understand what this plugin does.
We are doing the tags manually and this plugin seems to rely on a tag.
I guess we can export the phar in circle ci but in github will be harder since there is no good way to manage major, minor, path releases from the build server.

@rtfpessoa The ci configuration will run the deployment commands (creation of the phar and uploading to the github release) only if the build has been triggered by the creation of an tag (manually or automatically is the same) and if the tag follows semver (x.x.x).
The plugin will use the github api to attach the provided file to the provided tag during the build.
For me i used the provided CircleCi configuration with an fork of this repo. After i created an release/tag on github, CircleCi has run a build. As an result i got a version with the attached phar.
See: https://github.com/MaSpeng/php-codacy-coverage/releases/tag/1.4.2.
As i understood there should be no problem because the build, creation of the phar and upload will only be executed after a new tag has been created.

Ahhh, that makes a lot of sense. I guess I was confused. I think now it should be running.
https://github.com/codacy/php-codacy-coverage/releases/tag/1.4.2
Thanks for your help and patience.


Complete/kill everything for an aborted workflow

Well, I noticed only a minute ago that there is a patch being discussed already for this case, @ticoann made #6572 ... :(
I didn't notice killWorkflow() was called for both 'aborted' and 'force-complete' workflows. It would be easier to just kill/complete everything for workflows having this state transition, as well as less error prone. However, I do agree that it may be useful to have cleanup and logcollect jobs running for force-completed workflows, though I don't know whether people would really care if they lose some of these remaining jobs...
@ericvaandering @ticoann what do you guys think?

Since Seangchan decoupled workflow completion from these utilitarian jobs, cleanup and logcollect became less annoying, though there may be requests staying in the system if sites go out of Normal and jobs need to run there.

I think this PR is no longer relevant, so closing it.


Protect endless reconciliation of operations -  245

#245

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Ali Khlifi seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

/retest-required

/retest-required

/retest-required

/hold

/retest-required

/retest-required

/retest-required

/retest-required

/retest-required


Feature change language & Fullscreen options in settings

Including options in settings to allow:

Open Hydra Launcher in Fullscreen mode or custom resolution.
Change the Language system for a custom one.

Everything is saved as userPreferences, so if you clear your Hydra Launcher Cache, everything is reset.
I hope you guys can implement or use part of the code.
Once again, thanks for the project Hydra Launcher.

Someone from Los Broxas quem review my PR? I would like to contribute with those features for Hydra Launcher.

Fixed points about Style and Select component for Language.
Removed Input Fields for Resolution.

Ok, i took a better look into your PR. There are some problems:

A lot of comments
Your PR aims to do 2 things (persist screen resolution and change language)
None of these things seems done
Your options inside the Select are hard coded. If you want to work on this feature, you need to figure out a way to dinamically load your options so we dont have to revisit this component every time a new localization is added

I will have to close this PR, and I suggest you do only one thing per PR.

does not seems so hard to make it dynamic, its vasically do the sabe thaat the localization plugin does, reading the folders at the localization directory. u can use the same var it uses and convert the local code back to language name

does not seems so hard to make it dynamic, its vasically do the sabe thaat the localization plugin does, reading the folders at the localization directory. u can use the same var it uses and convert the local code back to language name

will take a look at the language changer later this week if no one does, seems funny

ok


atom-beautify doesn't beauty of a html section

Description
The results of beautification are not what I expect.
Expected Results
The beautified code should have looked like:
<script>
    var m;
</script>

Steps to Reproduce

Add code to Atom editor
Run command Atom Beautify: Beautify Editor
This beautified code does not look right!

Debug
Here is a link to the debug.md Gist: https://gist.github.com/anonymous/7a54ebba49f8d62e6563
Checklist

[x] I have tried uninstalling and reinstalling Atom Beautify to ensure it installed properly
[x] Searched for existing Atom Beautify Issues at https://github.com/Glavin001/atom-beautify/issues
so I know this is not a duplicate issue
[x] Generated debugging information and added link for debug.md Gist to this issue

I can reproduce the defect.  I am working it.

@prettydiff , I can work, too. But I have to begin. Is there the fast FAQ about Atom &  atom-beautify & bug-fix?

@oshliaer The problem will be in https://github.com/prettydiff/prettydiff/blob/master/lib/markuppretty.js
Clone prettydiff and look at lib/markuppretty.js.  The problem is most likely in the markuppretty__tokenize_content function in the condition where ext === true.  I am guessing that the markup parser is attempting to parse script code as a segment of content (it gets passed to the JavaScript parser later) but it isn't finding the closing script tag correctly.  There are some conventions in place to prevent early termination in the case of string literals, regular expressions, comments, and other areas of JavaScript that may contain a closing HTML script tag in a passively ignored way.

@oshliaer If you are working this just let me know if you have any questions.  I think I may have found the problem as I had to jump into the library for the issue I am currently working https://github.com/prettydiff/prettydiff/issues/275
I don't want to step on your feet.  Since you have expressed interest I don't want to deprive you of the chance to contribute.
Some additional information is that the unit tests are run with npm install in the project directory.

Ok. @prettydiff , I'll try today soon.

No hurry.  I have a huge backlog of tasks that have stacked up over the past week and I will be in and out a bunch today trying to tackle some family responsibilities.

Published resolution to v1.16.23.


String characters after a newline are missing in VARIABLES pane

VS Code Version: 1.54.2
OS Version: MacOS Big Sur 11.2.1

Using the following go program:
package main

import (
	"fmt"
	"runtime"
)

func main() {
	str1 := "\nabc\ndef\n"
	str2 := `
abc
def
`
	str3 := "abc\ndef\n"
	str4 := `abc
def
`

	fmt.Println("------")
	fmt.Println(str1)
	fmt.Println("------")
	fmt.Println(str2)
	fmt.Println("------")
	fmt.Println(str3)
	fmt.Println("------")
	fmt.Println(str4)
	fmt.Println("------")
	runtime.Breakpoint()
}

which outputs
------

abc
def

------

abc
def

------
abc
def

------
abc
def

------

We observe the following missing content in the VARIABLES pane while seeing the expected pretty-printed multi-line values in DEBUG CONSOLE, in hover and in Copy Value. This is surprising given the DAP's wording "The variable's value. This can be a multi-line text, e.g. for a function the body of a function". The multi-line text is hardly a valid option if it results in truncated display. Supposedly this was fixed/introduced based on https://github.com/microsoft/vscode/issues/73845. It is not clear from that issue if the discrepancy between Variables Pane and other elements is intentional.

\cc @hyangah

From the issue you linked, and https://github.com/microsoft/vscode/issues/69768, it sounds like the debug adapter is supposed to decide whether to escape the newlines based on the context, and "copy value" has its own context if you want to handle that differently. The js-debug debug adapter shows \n in the variables view. Does that make sense?


Fixes and dev tools update

Update pip-tools, fix pytest configuration for local testing and fix some problems which yielded warnings.
See commit messages for exact details.

Codecov Report

Merging #351 (997d0c6) into develop (a626f55) will increase coverage by 1.56%.
The diff coverage is 96.79%.

@@             Coverage Diff             @@
##           develop     #351      +/-   ##
===========================================
+ Coverage    93.38%   94.94%   +1.56%
===========================================
  Files          133      318     +185
  Lines         4940    10833    +5893
  Branches       450      719     +269
===========================================
+ Hits          4613    10285    +5672
- Misses         240      415     +175
- Partials        87      133      +46

Impacted Files
Coverage Δ

apartment/api/serializers.py
100.00% <ø> (ø)

...tions/0008_add_uuid_to_apartment_project_models.py
100.00% <ø> (ø)

apartment_application_service/wsgi.py
100.00% <ø> (ø)

application_form/api/sales/views.py
96.57% <ø> (ø)

application_form/api/serializers.py
100.00% <ø> (ø)

...tions/0021_application_date_of_birth_ssn_suffix.py
100.00% <ø> (ø)

...ations/0038_applicationapartment_apartment_uuid.py
70.00% <ø> (ø)

...orm/migrations/0040_lotteryevent_apartment_uuid.py
70.00% <ø> (ø)

...ations/0042_apartmentreservation_apartment_uuid.py
70.00% <ø> (ø)

...ct_terminated_to_reservation_agreement_canceled.py
100.00% <ø> (ø)

... and 124 more

... and 108 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Satellite crashing(ish)

For some reason every now and then the satellite disconnects from home assistant and the only way to get it working again is to goto the wyoming satellite integration and restart it. Then it will pick me up again for a few minutes or so. Then just randomly stop reacting to the wake word again. Theres no errors in any of the logs on the PI. It just looks like its sitting there waiting like normal. Although, the wake word just stops working. Not sure if I should post this here or on the wake word repo. Thanks. This is so awesome regardless.

I have the same problem. Apart from that the solution is - just as you are saying - awesome.

Yeah, I've noticed similar instability when making configuration changes to the services I have running on the satellite. I have a habit of doing a hard sudo reboot and then opening up the Devices & Services and reloading the device through the Wyoming integration. I wish there was a way to stream logs back or push config changes without the hassle of SSHing into the machine, but I'm sure it'll only get easier over time.

I've had the same issue...I found replacing the SD card with a "ScanDisk High Endurance" Sd card( in 1 unit to test) solves most issues I've had the satellite running for a month with no problems


fix: Semantic Release

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Hi @hsluoyz can you please tell why this PR has closed ?

This is Java, not Node.js


Support (ba)sh shell sessions

(Original issue 349 created by thatch on 2008-07-27T00:13:00+00:00)
I envision a ShellConsoleLexer that uses BashLexer (perhaps with other lexers as well, for the output of commands like 'diff' or python console sessions).  So I don't forget, this is what it looks like on an Ubuntu box
{{{
user@host:~/path$ ls -a
.  ..  a  b  c
user@host:~/path$ diff -u a b
--- a   2008-07-26 17:10:07.000000000 -0700
+++ b   2008-07-26 17:10:10.000000000 -0700
@@ -1,3 +1,3 @@
a
-b
+x
c
user@host:~/path$ echo \

a
a
user@host:~/path$ su
root@host:~#
sh-3.1$ # on hardy
sh$ # on etch
}}}

(Original issue was assigned to thatch)
(Original issue 349 last updated on 2009-01-03T16:11:01+00:00)
(Issue automaticaly closed due to status in Bitbucket: resolved)

(Original comment by thatch on 2008-12-29T16:55:28+00:00)
I applied v3 of the patch in my branch.  At some point it could be split out into a super-simple prompt (say, ^[$#]\\s+, designed for tutorials) and a complex one which matches more real-world prompts (for use with a pastebin).

(Original comment by thatch on 2008-08-15T06:05:59+00:00)
Still not finished, pushing to 0.12

(Original comment by thatch on 2008-07-30T07:23:50+00:00)
Yes, I agree that prompts can (and will) vary.  However as used in tutorials (say, embedded in a readme file in reST), the prompt is usually not too crazy.  I'm attaching my working version for review, see what you think.  Interestingly enough, your list above is pretty much what I arrived at independently (is always_notify_reporter email notification off?).

(Original comment by gbrandl on 2008-07-27T20:20:53+00:00)
Hmm. Prompt styles are very variable, so there's a dilemma: If you recognize very generic prompts like "$", "#" and "%", with "sh"-style prefixes and user@host:dir and user@host dir-style prefixes, that also poses the danger of false positives. It's not very helpful to only recognize Ubuntu prompts.


Can't pull sql expres (failed to register layer: failed to find link target for nvraid)

When pulling down the 'microsoft/mssql-server-windows-express:latest' container, the following error pops up when extracting the last layer.

The nvraid.sys file can be found on my disk.
I was able to run it in the past, but I had to remove containers, volumes, etc to make some space on my disk.
Any idea why this is happening?

I uninstalled Docker EE, though it wasn't easy to get rid of all docker install files.
After reinstalling it started to work again.


No graphs in Service

Rancher Version:
1.2.0-pre3
Docker Version:
1.12.1
OS and where are the hosts located? (cloud, bare metal, etc):
Ubuntu 16
Setup Details: (single node rancher vs. HA rancher, internal DB vs. external DB)
Single node rancher
Environment Type: (Cattle/Kubernetes/Swarm/Mesos)
Cattle
Steps to Reproduce:
Create consul from catalog
Results:

VM825:35 WebSocket connection to 'ws://rancher.dev.exness.local/v1/containerstats/9bf612f6911e9f69dbcec6e6823952254f34853d7dfc863e011970840e974131?token=eyJhbGciOiJSUzI1NiJ9.eyJleHAiOjE0NzU1OTMzMjMsInN1YiI6ImNhdHRsZSIsImlzcyI6Imh0dHA6XC9cL2NhdHRsZS5pbyIsImhvc3RVdWlkIjoiZjVmYmZkMDItNDQxMi00ZDhhLWJhNTktNmZhZDIxMTdkMTBhIiwiY29udGFpbmVySWRzIjp7IjliZjYxMmY2OTExZTlmNjlkYmNlYzZlNjgyMzk1MjI1NGYzNDg1M2Q3ZGZjODYzZTAxMTk3MDg0MGU5NzQxMzEiOiIxaTEyIn0sImlhdCI6MTQ3NTU5MzAyMywia2lkIjoiZGVmYXVsdCJ9.GcDOzHWgdE10wVcQc0olZYTVZKmelYBtLbXfXx-6x7vFktbTKpugKnPAycgWfozBN1Ww0947j0Y9_DCf2PEB35F3Y6JMiU3RTXLSFu2sO9W5uMPsjEh8nGmlzzB4xwMwVj3UscusknozRhVHgwIzd8K3VYbaNjDSeAJABE1zdC_7Qa6KKGSjg_w5Sx9UqHqsnOn6oIanA5282hk83z2GQE0qTQG-oRDDyROZfj0JblXUvabVd4WddYV2HIHuSa1aezdgq_OfnSejeFGyf4s_V_vWymgEUjRKgxF56u-3R7TKl4icldPjG8DiilJibxY4O8NDIAwUQ0hC75A5cU_fWQ&sockId=62' failed: HTTP Authentication failed; no valid credentials availableWrappedWebSocket @ VM825:35connect @ socket.js:50e @ ember.prod.js:497invoke @ ember.prod.js:991flush @ ember.prod.js:1055flush @ ember.prod.js:863end @ ember.prod.js:177run @ ember.prod.js:299_runExpiredTimers @ ember.prod.js:686_boundRunExpiredTimers @ ember.prod.js:146
socket.js:217 Socket error (state=connecting, id=62)
socket.js:169 Socket 62 closed
subscribe.js:131 Subscribe ping (projectId=1a7, sockId=54)

I have tried to logout/login but no success
Expected:

@cjellick  what might cause it failed to connect to the websocket in this case?

Typically firewalls or loadbalancers in front of rancher prevent websocket connections. @boskiv were you able to get this working?

@boskiv were you able to resolve this? If you could check this with the latest -pre release, avoiding an -rc candidate, feel free to reopen.


Remove outdated Fuchsia concepts

Fuchsia will soon remove all support for Component Framework version 1 (CFv1)
components (recognized by component manifests ending in .cmx).
Notably, some of the flutter tool commands for Fuchsia devices--
notably, but not limited to, those related to CFv1--are outdated, and
either do not work today or soon won't work.
This PR removes the outdated components and commands, replacing some
with the newer version, or simply removing the non-working features,
in some cases.
Fixes: #107334
Summary of changes

Removed *.cmx files, and their parent directories (*/fuchsia/meta/) from:

dev/benchmarks/
dev/integration_tests (flutter_gallery and ui)
examples (hello_world)

Removed the build fuchsia command (and tests) from flutter_tools. This command is not currently used in Fuchsia developer workflows. It may eventually be re-implemented for CFv2 components.
Replaced the fuchsia session_control command wrapper with an equivalent ffx command wrappers (via fuchsia_ffx.dart) for ffx session add and ffx session show.
Removed tiles_ctl.dart, which was used to launch flutter apps outside of a session. With CFv2, flutter components must run within a session.
Updated tools and tests to use ffx session ... instead of the deprecated session_control command.

Pre-launch Checklist

[x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
[x] I read the [Tree Hygiene] wiki page, which explains my responsibilities.
[x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement].
[x] I signed the [CLA].
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is [test-exempt].
[x] All existing and new tests are passing.

@akbiggs @arbreng - FYI, this is my first attempt, and I would not be surprised if it fails. I'm not familiar with how to set up a local environment for testing flutter/flutter changes yet, so I didn't get a chance to test the PR locally.
I'm sure there's more to be done, but let me know if you see any concerns with the overall approach.
I think this is aligned with what we discussed, in general.

Yeah, it breaks pretty quickly, actually. I'll look into how to build locally and upload changes as soon as I can do that without errors.

Ready for review!

Yes, will do.

To facilitate the review and help reference this PR after submission, could we list out concretely in the PR description:

What commands and components were removed
What commands have been updated

Done

@christopherfujino Does this PR fall on you expertise for a review?


Revision 472 import error

Steps to reproduce

juju deploy postgresql --channel 14/edge, the current revision for this is 472

Expected behavior
The application eventually settle to Active state, and the database is available for use.
Actual behavior

The application is in error state. E.g.:
postgresql/0   error     idle   0        <IP_ADDRESS>           hook failed: "storage-attached"

From the debug-logs, it seems this is the cause:
unit.postgresql/0.pgdata-storage-attached ModuleNotFoundError: No module named 'psycopg2._psycopg'

Full debug-log in later section.
Versions

Operating system:
The juju machine is<EMAIL_ADDRESS>
Juju CLI:
3.5.3-ubuntu-amd64

Juju agent:
3.5.3

Charm revision:
472

LXD:
The juju machine is openstack VMs.
Log output

Juju debug log:

unit-postgresql-0: 14:31:06 INFO juju Starting unit workers for "postgresql/0"
unit-postgresql-0: 14:31:06 INFO juju.worker.apicaller [3130dc] "unit-postgresql-0" successfully connected to "<IP_ADDRESS>:17070"
unit-postgresql-0: 14:31:06 INFO juju.worker.apicaller [3130dc] password changed for "unit-postgresql-0"
unit-postgresql-0: 14:31:06 INFO juju.worker.apicaller [3130dc] "unit-postgresql-0" successfully connected to "<IP_ADDRESS>:17070"
unit-postgresql-0: 14:31:06 INFO juju.worker.upgrader no waiter, upgrader is done
unit-postgresql-0: 14:31:06 INFO juju.worker.migrationminion migration migration phase is now: NONE
unit-postgresql-0: 14:31:06 INFO juju.worker.logger logger worker started
unit-postgresql-0: 14:31:06 ERROR juju.worker.meterstatus error running "meter-status-changed": charm missing from disk
unit-postgresql-0: 14:31:06 INFO juju.worker.uniter unit "postgresql/0" started
unit-postgresql-0: 14:31:06 INFO juju.worker.uniter resuming charm install
unit-postgresql-0: 14:31:06 INFO juju.worker.uniter.charm downloading ch:amd64/postgresql-472 from API server
unit-postgresql-0: 14:40:33 INFO juju.worker.uniter hooks are retried true
unit-postgresql-0: 14:40:33 WARNING unit.postgresql/0.pgdata-storage-attached Traceback (most recent call last):
unit-postgresql-0: 14:40:33 WARNING unit.postgresql/0.pgdata-storage-attached   File "/var/lib/juju/agents/unit-postgresql-0/charm/./src/charm.py", line 18, in <module>
unit-postgresql-0: 14:40:33 WARNING unit.postgresql/0.pgdata-storage-attached     import psycopg2
unit-postgresql-0: 14:40:33 WARNING unit.postgresql/0.pgdata-storage-attached   File "/var/lib/juju/agents/unit-postgresql-0/charm/venv/psycopg2/__init__.py", line 51, in <module>
unit-postgresql-0: 14:40:33 WARNING unit.postgresql/0.pgdata-storage-attached     from psycopg2._psycopg import (                     # noqa
unit-postgresql-0: 14:40:33 WARNING unit.postgresql/0.pgdata-storage-attached ModuleNotFoundError: No module named 'psycopg2._psycopg'
unit-postgresql-0: 14:40:33 ERROR juju.worker.uniter.operation hook "pgdata-storage-attached" (via hook dispatching script: dispatch) failed: exit status 1
unit-postgresql-0: 14:40:33 INFO juju.worker.uniter awaiting error resolution for "storage-attached" hook

Additional context

Hi, @yhaliaw, rev. 472 is an arm64 revision, if you are deploying on amd64 the revision is 472. You can verify the revision using juju info postgresql --arch=amd64<EMAIL_ADDRESS>There are some protections available on the K8s charm we should port, to get a more obvious error message

@yhaliaw I believe the @dragomirp above has addressed your issue and we have nothing to fix on the charm side.
Therefore resolving the issue, feel free to reopen if the further assist necessary!


Warning class does not extend BaseException

It appears that the Warning class does not extend from BaseException, however it is being treated as an exception and thrown from this line:
https://github.com/HelloFax/hellosign-php-sdk/blob/v3/library/HelloSign/Client.php#L906
In PHP7 and above this will generate the following error
Cannot throw objects that do not implement Throwable

Thanks for bringing this to our attention @nater540 . We will queue this for investigation, but feel free to address the issue with a pull request of your own if you wish.

I have a branch created for this but I don't have permissions to push to origin. Any suggestions? I suppose I need to become a contributor? Thanks in advance.

@jeffgrove You'll need to make a pull request against our primary branch. When we have time we'll review it and provide feedback or integrate your changes. Thanks for contributing!

@desmondw @nater540
Created a pull request. Not sure if I did it right. This is my first foray into open source.


React Refresh and Webpack Dependency Errors

I can't seem to resolve this error with between react / npm / nodejs / react refresh / and react refresh webpack ... This outputs when running / installing the Ubuntu GUI
Run npm audit for details.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: chia-blockchain@undefined
npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/react-refresh
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS><0.10.0" from<EMAIL_ADDRESS>npm ERR! node_modules/@pmmmwh/react-refresh-webpack-plugin
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.

simple upgrade @pmmmwh/react-refresh-webpack-plugin to 0.5.0


Data refresh record difference reporting

Fixes

Fixes #466 by @AetherUnbound
Description

This PR adds a few new steps to the data refresh DAGs which gather the record counts for a provided media table from the API before and after the data refresh, and then report the difference to Slack.
The easiest way of adding this to the DAG was to include a few PostgresOperator steps which would query the record count before and after the refresh. Unfortunately, the PostgresOperator doesn't push the return value to XComs by default. In order to facilitate that behavior here (and in future DAGs), I added a PostgresResultOperator. This operator is identical to the PostgresOperator, save that it allows a handler to be passed in, which in-turn is passed down to the PostgresHook when PostgresHook::run is called. It also returns the results of the provided handler function, so it can be referenced as an XCom downstream. I don't love that we have essentially vendored the PostgresOperator with a slightly tweaked interface, but I don't presume there will be many changes that we need to incorporate going forward (seeing as there were only half a dozen changes to the file in as many months recently). Nevertheless, I added some tests for this operator to ensure it's functioning as expected.
It's worth noting that we're using a row count estimate here rather than the exact row count. Discussion around this can be found on our Make WordPress Slack: https://wordpress.slack.com/archives/C02012JB00N/p1659039686501669. The TL;DR is that an exact count is extremely slow and the estimation method we're using is pretty darn accurate.
:warning: NOTE: We will need to add the postgres_openledger_api connection to production Airflow before this is run. It was introduced in #513 but it doesn't appear to be listed under the connections in Airflow yet.
Screenshots
DAG Definition (with new steps)

Sample Slack message

Testing Instructions

Testing for this is a bit complex, so let me know if any of these steps fail or require a bit more explanation:

Prerequisite: set up your local Airflow instance so it can communicate with a local API stack. @stacimc's instructions in #397 (under "Testing Instructions") are useful for these steps, with the caveat that AIRFLOW_CONN_DATA_REFRESH can now just be http://<IP_ADDRESS>:8001 or http://host.docker.internal:8001 for linux & Mac respectively.
In the API project directory, run the following (this will set up an actual difference in records to be reported)

just recreate
just init
just exec "upstream_db psql -U deploy openledger -c \"DELETE FROM image_view WHERE provider = 'flickr'\""

Trigger image_data_refresh DAG (either by enabling it in the UI or triggering a run)
When the DAG gets to the wait_for_ingest_upstream step, you may notice it go from up_for_reschedule to up_for_retry. This appears to be a result of https://github.com/apache/airflow/issues/23411, which we'll try to address in another PR. Wait a few seconds, then clear the wait_for_ingest_upstream step. This will allow the DAG to proceed as normal
Check the report_record_counts step and see that it shows a similar message to the screenshot!

Checklist

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

Developer Certificate of Origin

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

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

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

Developer's Certificate of Origin 1.1

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

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

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

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

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

Given this ^, can you expand on the benefits of using the new Operator instead of using a PostgresHook in a PythonOperator? Do you think this could be used in some of the other places we're currently interacting with the DB? 😮

Sure! I'm not sure if it could be used in place now, but I believe that the "run this query and post the results to XComs" paradigm is something we will definitely use in the future. Since this operator also takes whatever callable we want to hand into the postgres hook, it's robust to more than just SELECT COUNT and the ilk. It also prevents us from having to have multiple functions down the line that are of the form:

def get_pg_results(postgres_conn_id: str, sql: str):
    hook = PostgresHook(postgres_conn_id)
    results = hook.run(sql, handler=lambda c: ...)
    return results

...

get_results = PythonOperator(
    task_id=...,
    python_callable=get_pg_results,
    op_kwargs={
        "postgres_conn_id": PG_CONN_ID,
        "sql": ...,
    }
)

And instead simply use:

get_results = PostgresResults(
    task_id=...,
    postgres_conn_id=PG_CONN_ID,
    sql=...,
    handler=lambda c: ...
)

Another advantage of the latter is that we only have to write the tests against PostgresResults to ensure it behaves as expected, rather than writing tests against every get_pg_results-like function. If we needed to pass in a more complicated handler, we could have that be a defined function (rather than an in-line lambda) and test against that instead!

postgres_openledger_api connection has been added! Merging 🚀


Incorrect interaction between rtl languages and table columns

Description
When using an rtl language /  setting the text dir to rtl directly,  table columns go right to left, as they should. But their numbering is still left to right, as can be observed when using a fill function.
#set text(dir:rtl)

#table(
  columns: (1fr,1fr,1fr),
  fill: (col,row) => {
    if col == 0 {
      red
    }
    else {
      white
    }
  },
  [1],
  [2],
  [3],
  [1],
  [2],
  [3],
  [1],
  [2],
  [3],
  [1],
  [2],
  [3],
  [1],
  [2],
  [3],
  [1],
  [2],
  [3],
)

In this example I would expect the first column (with 1s) to be red, not the last column.
Reproduction URL
https://typst.app/project/pA69dJ-jBVCi95eIyQf31N
Operating system
Web app, Linux
Typst version

[X] I am using the latest version of Typst

Likely related to #1386 , which was fixed with #3037 . Table RTL in particular was also reworked in #3239 .
So, this should be fixed in the next update, as seen below. :)

Great, Thanks!


Terrible performance on GTX 960M

Describe the bug
Runs at 15 fps on full screen, otherwise 24 fps (on deferred).
To Reproduce
Try on a low-end desktop/laptop.
Expected behaviour
Run at a higher fps.
Screenshots
N.A.
Desktop (please complete the following information):

OS: Windows 10
Version: master (37909791dc3693b8b48bc4276f10ad4a403b8803)
Hardware: GPU: 960M, RAM: 16 GiB, CPU: N.A.

Additional context
100% GPU usage, so GPU bound. Downloading NSight to look into it further.

Looked into it more, it's because my VRAM ran out and it's using shared memory instead.

https://github.com/TeamWisp/Procedural-Ray-Tracing/issues/248

Duplicate with #248, Closing


Asynchronous code can mess with inputlist

This is kind of a strange issue, and it arises out of situations that weren't possible before support for running code asynchronously was available. Because you can now execute VimL code after a delay, it's possible to execute some code that messes with the display of inputlist() after inputlist() has been executed, and before the user has typed an answer.
You can see the issue arising here: https://github.com/Galooshi/vim-import-js/issues/17
My plugin ALE checks for problems after a short delay, and can display some results after checks have been made, which can come after the inputlist prompt is open. After some experimentation, it appears that calling an empty function with timer_start, which ticks when the list is open, can move the user's cursor, and could potentially cause other issues.
After a little bit of thinking, I have the following suggestions for improvements to Vim:

Prevent whatever causes the cursor to move when a timer function ticks.
Re-render the inputlist prompt after changes to highlights, signs, or anything which could potentially break it.
Consider not displaying the results of :echo or :echomsg at all while the inputlist prompt is open. We could consider still displaying the results of :echoerr or throw.

Let me know what you think.

An asynchronous callback should never display a message to the user at the command line.  It will interfere with what the user is doing.  You can open a small window to put any status or messages.
I'll fix that the prompt of inputlist() is messed up by the redraw after a callback is invoked.

Cheers, Bram!


Implement Snyk github action CI for scanning vulnerabilities

Description
Implement Snyk marketplace action to perform static code analysis.
Scanning dependency vulnerabilities and license scan is option.
Checklist

[x] Add snyk scan for vulnerability and license scan
[x] Add snyk for static code analysis

Snyk dependency, license and code analysis added in the GHA workflow.
PFB screenshot for evidence.


RE: TMS web app

Hi,
How to set up web app on server? Please, may you describe server job setup or server installation.steps
Searching dosent work on website? Your demo dont work too : http://static.tms.mooo.com/app/  I've got the same problem.
Thanks

How to set up web app on server
Web app have backend, that work as simple proxy for bypass CORS.
/app/via?url=
It don't open source, because it may have security problems for me, it work like proxy.

demo don't work too
Backend sometimes down, yes

I wonder whether @vvdy managed to set up web app on server?
Now when plugin disappeared from the app stores, this topic became relevant to me.


Add quickwit to ArtifactHub

It seems that is repository is not yet tracked by artifacthub.io. In fact it seems that there are already 2 community packages already present (https://artifacthub.io/packages/search?ts_query_web=quickwit).
Adding a package to artifacthub is super straight forward: You just need to sign-up and than add a artifacthub-repo.yml file to your repository.
ArtifactHub will than regularly scan your helm repository for new chart verions.
The ArtifactHub allows @glasskube to get notified about about new helm chart versions, which will kick off our internal ci/cd pipeline.

It was added in 4e12080

indeed! thanks @M0NsTeRRR


Make it easy to opt out of next/babel preset components

Feature request
Is your feature request related to a problem? Please describe.
Sometimes the provided babel plugins conflict with what I want to do. For example, I would like to use class instead of className and Preact with Next.js.
However, styled-jsx's babel plugin is overwriting my classes:

since I use Tailwind instead of styled-jsx, I would like to turn the styled-jsx plugin off.
There is an old issue to opt out of styled-jsx, but this no longer works since plugins are no longer self identifying:
GitHub Source
You cant simply do myPreset.plugins.filter any more because there is no identifying name for the plugins. You can't rely on order because the order varies depending on env.
in order to do what i need i am having to copy out the entire source of the babel plugin in order to delete the specific plugin I need.
Describe the solution you'd like
I would like a simple way to opt out of the babel plugins. I think the best way is to simply attach the name of the plugin to each plugin, so that the user can filter in a babel.config.js:
// note: this is just my proposal - this doesnt actually work bc plugins arent self identifying
const nextbabel = require("next/babel");

const wrapNextBabel = (api) => {
  const temp = nextbabel(api);
  temp.plugins = templ.plugins.filter(plugin => plugin.name !== 'styled-jsx')
  return temp;
};
return {
  presets: [wrapNextBabel],
  plugins: [],
};

(btw - Next.js' typescript fails when you use babel.config.js as oppose to .babelrc - i ended up routing .babelrc to a babel-preset.js in order to trick Next.js)
Describe alternatives you've considered
maintaining this ugly ass fork haha

i think this is a pretty easy PR. if you approve the idea i would be happy to PR> basically just attaching string names to each babel plugin.

I think the better solution would be for the styled-jsx plugin to correctly no-op when you don't use styled-jsx 🤔

ok.. that one might be a bit above my ability haha.
i was just trying to generalize from my bad experience - if i have to opt out of this plugin, i might need to opt out of any of the other plugins - so i'd like next/babel to help me.
but i think its also good to no-op styled-jsx when it is not used. could potentially save a lot of kb in wasteful generated classnames.

but i think its also good to no-op styled-jsx when it is not used. could potentially save a lot of kb in wasteful generated classnames.

This isn't the case already if you don't use styled-jsx though. Maybe you have a <style jsx> somewhere 🤔

ahh you're right. i accidentally left some in there when i copied some boilerplate.


Allow for speedUp and stop based on provided gasValues from consumer

opening this as a draft as it relies on https://github.com/MetaMask/controllers/pull/521
this adds a new interface GasValues which can be used to dynamically set values for speedUp and stopTransaction which can be used instead of our previously existing fixed rates.
this will allow consumers to set custom gas values (in hex) for both those actions.

Thanks @Gudahtt! I've added the validation in stopTransaction now as well.

@Gudahtt fixed spelling and removed unnecessary optional chaining


fix(Select): options in the select component will be overwritten due to timing of React.setState

SUMMARY

This PR fix the problem that when user undo delete of a native filter, the options under column is gone. The root cause is due to the setState mechanism of the react hook. In the Select component, there is one case that we update the component selectOptions which based on the incoming props:
useEffect(() => {
    fetchedQueries.current.clear();
    setSelectOptions(
      options && Array.isArray(options) ? options : EMPTY_OPTIONS,
    );
    setAllValuesLoaded(false);
}, [options]);

and a logic we use useEffect to update selectOptions:
 useEffect(() => {
    if (selectValue) {
      // ...
      if (options.length > 0) {
        setSelectOptions([...options, ...selectOptions]);
      }
    }
}, [labelInValue, isAsync, selectOptions, selectValue]);

So there is a problem that useEffect knows the state has changed, but the value taken at this time is still the old value.
The solution is we can pass an updater function to transform it so we can use the pending state.  see https://beta.reactjs.org/reference/usestate#passing-an-updater-function-to-setstate.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

before
https://user-images.githubusercontent.com/81597121/135208961-d9acdead-f57a-4ae7-9283-82e613bf3486.mov
after
https://user-images.githubusercontent.com/11830681/148423959-55dca159-b34d-4bc6-9e03-e33ef787c9a2.mov
TESTING INSTRUCTIONS

ADDITIONAL INFORMATION

[x] Has associated issue: https://github.com/apache/superset/issues/16887
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

Thank you for the excellent PR description! This helps a LOT. :D


fix: switch to prerelase kafkajs lib for concurrency improvement

https://github.com/tulios/kafkajs/pull/1258

Close #42


String: Implement Knuth—Morris—Pratt Algorithm in C++

assign it to me

@Duzzuti, are you still working on this? If not, @akgmage, please assign this to me.


Group DM Additions

I added a GroupManager to the Group object to change it's name and icon and I also added a method to JDAClient to create new Group DMs because I nedded this for a project. See commits for details. I had a good reason to mess with Requester.java, don't worry...

Additionally to my review I would like you to fix the commits of this PR to not include merge commits. Please look into resetting branches and force pushing to get a single commit.

sorry about all the random commits
I'm still kinda new to this aspect of git, so things got messed up pretty fast

The endpoint works on the default route however the response only includes the first recipient. I just tested this.
This needs to get investigated but adding a different version can be done by simply using v6/users/@me/channels not the entire url.

You did not fix the indentation for all files. Please go through all your changes and use 4 spaces

Wow im smart
I didn't even notice i could have done that, thanks for pointing it out

I'm gonna put this on hold as it is not yet finished and should be revisited after the Requester rewrite is completed.
Reference experimental/okhttp for the requester rewrite.
Required Changes:

[ ] Indentation to only use spaces
[ ] Route endpoint not including base
[ ] Bracket placement/formatting

An additional review will be done once we revisit this pull request.
We are planning to switch to the v6 base in the requester rewrite which should fix issues with the endpoint.

okay

@LAX1DUDE do you still have any intention to fix the things @MinnDevelopment listed above?

stupid email
I replied 4 days ago that I am out of town and will finish when I'm home, if now is the time to do so.
I guess it didn't go through for some reason sorry


Getting an error unable to cast COM object of type

VSCode Version:1.0.0
OS Version:Windows 7 Enterprise

Visual C++ 2015 14.0.23026 is installed in the machine
Visual studio is not installed
Steps to Reproduce:
Getting the below error when building a console application using dotnet run command in command line
Unexpected error writing debug information -- 'Unable to cast COM object of type 'System.__ComObject' to interface type 'Microsoft.Cci.ISymUnmanagedWriter5'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{DCF7780D-BDE9-45DF-ACFE-21731A32000C}' failed due to the following error: No such interface supported (Exception from HRESULT: 0x80004002 (E_NOINTERFACE)).'

I am very sorry to hear you are having issues with VS Code. Reading your description it seems that the issue originates from an extension and not VS Code itself. Thereby I will close this issue and kindly ask you to report this issue against the extension repository.
Most extensions are on GitHub as well so it should be easy to file it against the extension. If you open an extension on the market place, click on the Support link to find out more.

Thanks again for your feedback!


Addition of install for push notifications package.

Should this be in openwhisk at all?

IMO, the question for this package, like a few others in various stages of progress, is it something that is considered an essential package that would/could be leveraged by a many customer/user scenarios or demos; if so, then they should be installed as part of the "core" system to make it useful (apart from system, utils) out-of-the-box.

we should document the git clone and install.sh steps for external packages and not install them. this is creating a core dependence on external packages.
core packages are ones we will continue to provide in whisk.system, do you disagree?

So the course of action should be to document the installation steps for open (not deliver the .sh files to open at all). The installation steps will be: 1. Run git clone https://github.com/openwhisk/wsk-pkg-pushnotifications.git "$dir" 2. Run the install.sh script from the clone

@nwspeete-ibm is this still a valid PR?

The steps are documented in the push package and open on how to install. This is no longer a valid PR because of the decision to have git clone and install.sh steps for external packages.


(Github) issues best practices as part of the development process?

Having a section on issues best practices, particularly as it relates to development, would be useful. E.g.:

All non-trivial commits should tie back to a single issue
Issues should have acceptance criteria (and... other stuff... possibly user stories/etc, but could get too much into "product" land)
Issues should be closed via commit messages to better create a paper trail to document issue origination to code commit.
Label usage

... something like that anyway? I personally favor Github Issues, but this section could be agnostic (or have separate issue tracker carveouts?)

I personally think "Issues best practices" targets certain size of projects. If you look at the rest of the best(common) practices in this document, you see that apart from being very code oriented, you can apply them on small personal projects as well.
But lets keep this issue open.

I added issue 32. It doesn't discuss "issues best practices" directly, but you might be interested. If you don't mind I close this issue.


Pre commit fixes

lychee failures:
[docs/community.md]:
✗ [500] https://slack.osfw.dev/ | Failed: Network error: Internal Server Error

[docs/events.md]:
✗ [404] https://www.youtube.com/watch?v=A9GrlQsQc7Q?start=8152 | Failed: Network error: Not Found
✗ [429] https://vimeo.com/488140434 | Failed: Network error: Too Many Requests

Both vimeo and youtube work so only problem is slack.osfw.dev

In addition to previous lychee failures there is also:

https://mirroronet.pl/pub/mirrors/FOSDEM/2020/K.4.601/firmware_itsoecs.mp4 - video can't be played becase the file is corrupt
https://www.amd.com/system/files/TechDocs/24593.pdf - redirected, doesn't go directly to wanted document

@krystian-hebel rebased and added fixes. Is it correct now? Indent was hard to see (2 spaces only and wasn't rendered on GitHub correctly)


Create mixins for Angular table column directives

🧹 Tech Debt
Multiple column types are likely to mix-in the FractionalWidthColumnAPI and/or the GroupableColumnAPI. The Angular directives for those column types will also expose those APIs. We should have mixins for those directives. Once we have them, we should update the Text and Anchor column types to use them.

Re-opening as #1587 was reverted in #1591
An Angular issue describes why using TypeScript Mixins does not work for Angular Directives and recommends checking out how Angular Material handles mixins. I didn't look but we can check what Angular Material does and see if it's useful for us.

tldr - After looking into the approach that Angular Material uses, it doesn't see particularly useful for us. Closing this as not planned because there isn't a clear path forward to is significantly better than our current approach of copy/pasting between directives.
The approach taken in Angular Material is to mixin a base class that isn't a @Directive and doesn't contain any properties marked as @Input. Instead, that mixed in base class provides only the TS implementation of the getter(s) and setter(s) for properties. Then, the actual @Directive has to configure an inputs array as part of its decorator, which in our case also has to rename each input to follow our naming conventions. Therefore, our implementation would need to look something like the following:
@Directive({
    selector: 'nimble-table-column-text',
    // eslint-disable-next-line @angular-eslint/no-inputs-metadata-property, @angular-eslint/no-input-rename
    inputs: ['fractionalWidth: fractional-width', 'minPixelWidth: min-pixel-width', 'groupIndex: group-index', 'groupingDisabled: grouping-disabled']
})
export class NimbleTableColumnTextDirective extends mixinFractionalWidthColumnAPI(mixinGroupableColumnAPI(NimbleTableColumnBaseDirective<TableColumnText>)) {
    /* implementation specific to the text column */
}

It's not ideal to have to call the mixin function and still have to know all the properties & their mapped inputs. This also doesn't allow a mixin to add a new input without having to update each usage of that mixin. I attempted to single-source the input string within the mixin file, but that didn't work because the mixin is in a different entry point (table-column rather than table-column/text); therefore, the string array isn't statically known at compile time like is required.
Additionally, the above approach didn't actually work because all of the @Inputs coming from NimbleTableColumnBaseDirective were lost from the type. This may be a solvable problem, but we decided that it wasn't worth further attempts to solve it since the general direction of the approach already seemed to be adding significant complexity to our code while still requiring a decent amount of code duplication across each directive.


Broken running forked livescript

lsc 1.5.0 would be broken when running the following directly.
require! cluster

if cluster.is-master
  console.log \master
  cluster.fork!
else
  console.log \worker
  process.disconnect!

require! cluster
       ^
SyntaxError: Unexpected token !

This has been introduced by #562.
process.execPath now points to Node, so fork is executed as JS.
I can't thing a clear solution, sometimes we need execPath pointing node, sometimes pointing lsc.

As I see it, the problem here is not that execPath needs to point to lsc; it's that lsc shouldn't be messing around with process.argv. If I remove the code from command.ls and node.ls that does so, this example works fine, and I bet the shelljs functionality fixed in #562 also continues to work.
The node.ls behavior was introduced in commit 9090c59, way back in the coco days. The motivation stated in that commit was to make relative require work with --eval and --stdin. Removing the process.argv assignment from that code doesn't seem to break relative require with --eval or --stdin when I tested it.
The command.ls behavior was introduced in response to #569, in commit c959444. This is partly a case of piling a hack on top of the previous hack, and partly a case of asking for the wrong thing: the reporter asked for [ 'node', '/home/derk/test.ls', 'hello' ] but should have asked for [ 'node', 'lsc', '/home/derk/test.ls', 'hello' ] (or [ 'lsc', '/home/derk/test.ls', 'hello' ], but we know thanks to #562 that this has undesirable effects).
Basically, I think both of those hacks should be removed and process.argv should be left as node intended.


What is the correct way to know whether a library is valid to send a setLibraryDebuggable request for?

I'm currently sending setLibraryDebuggable request for all libraries in an isolate when my debugger attaches. However, when trying to attach to a Flutter app I got the following error:

setLibraryDebuggable: illegal 'libraryId' parameter: libraries/@9040228

It seems to be because this libraryId was dart._internal:
{
  "type":"@Library",
  "fixedId":true,
  "id":"libraries/@9040228",
  "name":"dart._internal",
  "_vmName":"dart._internal@9040228",
  "uri":"dart:_internal"
}

I can exclude this library by name so I never send setLibraryDebuggable for it, but I don't know whether there may be others like this in future. What's the convention for libraries that cannot be sent? Will they all start with dart:_? Should I exclude anything with a _vmName?

For now I'm excluding anything that starts dart:_ but it'd still be nice to have confirmation if this is a reasonable rule.

@bkonyi @rmacnak-google could you provide and answer to this issue (e.g. is this expected to work for private internal libraries - if it is not expected to work then we should mark it as such and close an issue).

Note that this prevents debugging of dart:_http implementation - so maybe we should permit it?


adding --run flag

changing default behavior to only list the files that are problematic. use --run or -r to actually run the fix. This is very useful when fixing production environment and you want to know which files the tool will fix.

Fixed in #10


add citations and descriptions to metadata

so that these can be shown online

@mikabr i think we can close this?


Unable to DELETE the keda CRD scaledobjects.keda.sh

Report
I was trying to uninstall old keda 2.3,0 from cluster but unfortunately, I couldn't delete the following CRD
kubectl delete customresourcedefinition scaledobjects.keda.sh
The below ones are removed
kubectl delete customresourcedefinition clustertriggerauthentications.keda.sh
kubectl delete customresourcedefinition scaledjobs.keda.sh
kubectl delete customresourcedefinition triggerauthentications.keda.sh
Then I ran the below command which ran succsfully
helm uninstall keda -n keda
But when I checked the crds ,I could see scaledobjects.keda.sh in terminating state,and I am unable to install any new keda version in Azure AKS ,when I run the below command
helm install keda kedacore/keda --namespace keda --version 2.10.1 --set nodeSelector."kubernetes.io/os"=linux
I am getting the below error
Error: INSTALLATION FAILED: rendered manifests contain a resource that already exists. Unable to continue with install: CustomResourceDefinition "scaledobjects.keda.sh" in namespace "" exists and cannot be imported into the current release: invalid ownership metadata; label validation error: missing key "app.kubernetes.io/managed-by": must be set to "Helm"; annotation validation error: missing key "meta.helm.sh/release-name": must be set to "keda"; annotation validation error: missing key "meta.helm.sh/release-namespace": must be set to "keda"
The above error I feel is due to the old scaledojects in the AKS cluster.
Is there a way to remove the unremoved CRD scaledobjects.keda.sh from the AKS cluster
Expected Behavior
Should be able to delete the crd (scaledobjects.keda.sh) and run the below command successfully in Azure Kubernetes
The above error I feel is due to the old scaledojects in the AKS cluster.
Is there a way to remove the unremoved CRD scaledobjects.keda.sh from the AKS cluster.
Actual Behavior
kubectl delete customresourcedefinition scaledobjects.keda.sh
The below ones are removed
kubectl delete customresourcedefinition clustertriggerauthentications.keda.sh
kubectl delete customresourcedefinition scaledjobs.keda.sh
kubectl delete customresourcedefinition triggerauthentications.keda.sh
Then I ran the below command which ran succsfully
helm uninstall keda -n keda
But when I checked the crds ,I could see scaledobjects.keda.sh in terminating state,and I am unable to install any new keda version in Azure AKS ,when I run the below command
helm install keda kedacore/keda --namespace keda --version 2.10.1 --set nodeSelector."kubernetes.io/os"=linux
Error: INSTALLATION FAILED: rendered manifests contain a resource that already exists. Unable to continue with install: CustomResourceDefinition "scaledobjects.keda.sh" in namespace "" exists and cannot be imported into the current release: invalid ownership metadata; label validation error: missing key "app.kubernetes.io/managed-by": must be set to "Helm"; annotation validation error: missing key "meta.helm.sh/release-name": must be set to "keda"; annotation validation error: missing key "meta.helm.sh/release-namespace": must be set to "keda"
The above error I feel is due to the old scaledojects in the AKS cluster.
Is there a way to remove the unremoved CRD scaledobjects.keda.sh from the AKS cluster
Steps to Reproduce the Problem

Logs from KEDA operator
The helm uninstall -n keda command removed the keda so no logs ,but the crd scaledobejcts.sh is still there
example

### KEDA Version

2.3.0

### Kubernetes Version

1.25

### Platform

Microsoft Azure

### Scaler Details

_No response_

### Anything else?

_No response_

Hi
Do you still have any resource in that CRD? What do you see if you execute kubectl get so -A? If there is any resource you will need to patch them to remove the finalizer, they are blocking the deletion.
Latest versions have the process documented: https://keda.sh/docs/2.11/deploy/#uninstall

I could see these much resources
@JorTurFer The probelm was I was unable to delete .
kubectl delete customresourcedefinition scaledobjects.keda.sh

You can't delete the CRD because there are objects using it (all the objects in the picture). When you delete a CRD, k8s tries to delete all the CRs, but ScaledObject has a finalizer, so it's waiting until KEDA removes the finalizer (and KEDA has been removed, so it can't remove the finalizers), that's why you have to delete the finalizers from existing ScaledObjects before deleting the CRD

BTW, why have you removed KEDA instead of just upgrade it using helm directly? Deleting KEDA you have to remove all the related resources and redeploy them once KEDA is updated. If you just upgrade KEDA using helm, all the ScaledObjects can be there and you don't need to do anymore

@JorTurFer thanks for the response...
I removed keda using helm uninstall -n keda command and got removed. But the scaledobject.sh crd is still there we removed without competing removing the scaledobject
as when we tried deleting the crd  kubectl delete customresourcedefinition scaledobjects.keda.sh,it was stuck and we proceeded with the next steps of keda unistall and tired installing the new version with the below command
helm install keda kedacore/keda --namespace keda --version 2.10.1 --set nodeSelector."kubernetes.io/os"=linux.
As you mentioned we have to remove the finalizers from where do we need to remove the finalizers as we are bit unsure

If you check any ScaledObject, you will see metadata.finalizers, you have to remove them to unlock the ScaledObject, otherwise the ScaledObject is locked until KEDA removes the finalizer. As it's documented in the link I sent, you can remove them programmatically:
for i in $(kubectl get scaledobjects -A \
  -o jsonpath='{"-n "}{.items[*].metadata.namespace}{" "}{.items[*].kind}{"/"}{.items[*].metadata.name}{"\n"}');
do kubectl patch $i -p '{"metadata":{"finalizers":null}}' --type=merge
done

The problem is that until there is at least one ScaledObject in the cluster, you can't delete the CRD. For future updates, I suggest using helm upgrade instead of uninstall/install because helm doesn't allow us to remove the finalicers AFAIK... maybe we can improve the charts using hooks to enforce the CRD deletion before any other stuff 🤔

I did a edit of a scaled object and could see finalizer ,do you mean i need to remove those from the scaled objects

yes, that's it

@JorTurFer
When i did an edit it manually opened a notepad,shall i manaully remove all the finalizers from each of the scaled objects,the one that is marked in the screenshot below

Yes, you can do it and you have to do it for unlocking the ScaledObjects and then, you will be able to delete the CRD

Just a query
The command that you gave
for i in $(kubectl get scaledobjects -A
-o jsonpath='{"-n "}{.items[].metadata.namespace}{" "}{.items[].kind}{"/"}{.items[*].metadata.name}{"\n"}');
do kubectl patch $i -p '{"metadata":{"finalizers":null}}' --type=merge
done
I am using vscode not sure how to run shall i copy and paste and run

Yeah, or place it in a bash script, or in the worst case, delete the finalizer manually Xd

I am deleting the finalizers manually now the count is reducing when i delete the finalizer and save the scaler..Seems like this was holding on to the keda.scaledobject.sh
.Hopefullly i can delete the CRD ( kubectl delete customresourcedefinition scaledobjects.keda.sh)  then

@JorTurFer

We have deleted the finalizers proceeding with the below command
kubectl delete customresourcedefinition scaledobjects.keda.sh

@JorTurFer  Thanks so much for the support we have succefully deployed the Keda .
Seems like we have to redeploy all the scaledobjects again as we have deleted.
Is there any inplace upgrade of keda using helm we are using the below command to install the keda
helm install keda kedacore/keda --namespace keda --version 2.10.1 --set nodeSelector."kubernetes.io/os"=linux

Yes, you can use helm upgrade --install keda kedacore/keda --namespace keda --version 2.10.1 --set nodeSelector."kubernetes.io/os"=linux to upgrade the helm release with the version that you want. If you upgrade KEDA using helm, all the ScaledObjects will persist

@JorTurFer  Thnaks
If I have to uninstall a particular Keda version say 2.10.1 can i have correct steps on the process how that can be done. The Keda documentation commands where bit confusing previously I had followed the same steps which I mentioned in the issue part based on this github link which I itself raised and the response that I got from Keda .
https://github.com/kedacore/keda/issues/2004
Can I have the correct steps.Say we need to uninstall keda 2.3.0 and Install 2.10.1

Buen the linked issue is from KEDA 1 to KEDA 2, it's a mejor versio change.
In this case, as is a minor version, just use helm upgrade

@JorTurFer  the thing is if we need to unistall a particular keda version from a cluster what all steps are needed.Could you please share that if possible

Latest versions have the process documented: keda.sh/docs/2.11/deploy/#uninstall

I sent you in my first message :)
you need to remove KEDA custom resources (SO, SJ,...) and then helm uninstall....

I guess this is solved, I close it

PS /home/nithin> helm upgrade --install keda kedacore/keda --namespace keda --version 2.10.1 --set nodeSelector."kubernetes.io/os"=linux
Error: UPGRADE FAILED: failed to create resource: Deployment in version "v1" cannot be handled as a Deployment: json: cannot unmarshal object into Go struct field PodSpec.spec.template.spec.nodeSelector of type string
@JorTurFer  when i try to upgrade I am getting the above error

Hello,
You don't need to set that selector because it's already added as default because KEDA only works on linux nodes. In your case, the problem is that the selector has to be escaped, but as I said, you can just remove it because it's already set:

Try again without the --set and let me know how it goes :)

@JorTurFer  after the upgrade we can see there are restarts for the keda-admission-webhooks,its not that common ,is this something that we have to be worried about
PS C:\Users\nidicula\OneDrive - RM PLC\WORK\Assessor\AKsSetupPOC\NginxIngressTesting> kubectl logs keda-admission-webhooks-65c5866465-8bt58 -n keda
2023-09-01T11:09:12Z    INFO    controller-runtime.metrics      Metrics server is starting to listen    {"addr": ":8080"}
2023-09-01T11:09:12Z    INFO    setup   Starting admission webhooks
2023-09-01T11:09:12Z    INFO    setup   KEDA Version: 2.10.0
2023-09-01T11:09:12Z    INFO    setup   Git Commit: ee28bf69389bca7bf6d5edd83e2bc3940254114c
2023-09-01T11:09:12Z    INFO    setup   Go Version: go1.19.7
2023-09-01T11:09:12Z    INFO    setup   Go OS/Arch: linux/amd64
2023-09-01T11:09:12Z    INFO    setup   Running on Kubernetes 1.25      {"version": "v1.25.6"}
2023-09-01T11:09:12Z    INFO    controller-runtime.builder      skip registering a mutating webhook, object does not implement admission.Defaulter or WithDefaulter wasn't called       {"GVK": "keda.sh/v1alpha1, Kind=ScaledObject"}
2023-09-01T11:09:12Z    INFO    controller-runtime.builder      Registering a validating webhook        {"GVK": "keda.sh/v1alpha1, Kind=ScaledObject", "path": "/validate-keda-sh-v1alpha1-scaledobject"}
2023-09-01T11:09:12Z    INFO    controller-runtime.webhook      Registering webhook     {"path": "/validate-keda-sh-v1alpha1-scaledobject"}
2023-09-01T11:09:12Z    INFO    controller-runtime.webhook.webhooks     Starting webhook server
2023-09-01T11:09:12Z    INFO    Starting server {"kind": "health probe", "addr": "[::]:8081"}
2023-09-01T11:09:12Z    INFO    Starting server {"path": "/metrics", "kind": "metrics", "addr": "[::]:8080"}
2023-09-01T11:09:12Z    INFO    controller-runtime.certwatcher  Updated current TLS certificate
2023-09-01T11:09:12Z    INFO    controller-runtime.webhook      Serving webhook server  {"host": "", "port": 9443}
2023-09-01T11:09:12Z    INFO    controller-runtime.certwatcher  Starting certificate watcher
PS C:\Users\nidicula\OneDrive - RM PLC\WORK\Assessor\AKsSetupPOC\NginxIngressTesting>

Definitively, the admission webhook should be restarting. Could you share the logs from the previous container? I'd need also the output of kubetl describe pod

@JorTurFer thanks for the prompt reponse.Can you please clarify which previous container.I have done a describe pod of the keda admission webhook will this suffice
PS C:\Users\nidicula\OneDrive - RM PLC\WORK\Assessor\AKsSetupPOC\NginxIngressTesting> kubectl describe pod keda-admission-webhooks-65c5866465-8bt58 -n keda
Name:             keda-admission-webhooks-65c5866465-8bt58
Namespace:        keda
Priority:         0
Service Account:  keda-operator
Node:             aks-linux8core-34370389-vmss0002k2/<IP_ADDRESS>
Start Time:       Wed, 30 Aug 2023 17:59:14 +0530
Labels:           app=keda-admission-webhooks
app.kubernetes.io/component=operator
app.kubernetes.io/instance=keda
app.kubernetes.io/managed-by=Helm
app.kubernetes.io/name=keda-admission-webhooks
app.kubernetes.io/part-of=keda-operator
app.kubernetes.io/version=2.10.0
helm.sh/chart=keda-2.10.1
name=keda-admission-webhooks
pod-template-hash=65c5866465
Annotations:
Status:           Running
IP:               <IP_ADDRESS>
IPs:
IP:           <IP_ADDRESS>
Controlled By:  ReplicaSet/keda-admission-webhooks-65c5866465
Containers:
keda-admission-webhooks:
Container ID:    containerd://a09c0f99334fb6337854ada76120179758f13550f528bf2ff804dd9fe50ac304
Image:           ghcr.io/kedacore/keda-admission-webhooks:2.10.0
Image ID:        ghcr.io/kedacore/keda-admission-webhooks@sha256:8c062db679a95626966f29f9ad26c179acea91105b6258da897b5ed930461267
Port:            9443/TCP
Host Port:       0/TCP
SeccompProfile:  RuntimeDefault
Command:
/keda-admission-webhooks
Args:
--zap-log-level=info
--zap-encoder=console
--zap-time-encoding=rfc3339
--cert-dir=/certs
State:          Running
Started:      Fri, 01 Sep 2023 18:51:08 +0530
Last State:     Terminated
Reason:       OOMKilled
Exit Code:    137
Started:      Fri, 01 Sep 2023 18:12:56 +0530
Finished:     Fri, 01 Sep 2023 18:51:06 +0530
Ready:          True
Restart Count:  25
Limits:
cpu:     50m
memory:  100Mi
Requests:
cpu:      10m
memory:   10Mi
Liveness:   http-get http://:8081/healthz delay=25s timeout=1s period=10s #success=1 #failure=3
Readiness:  http-get http://:8081/readyz delay=20s timeout=1s period=10s #success=1 #failure=3
Environment:
WATCH_NAMESPACE:
POD_NAME:         keda-admission-webhooks-65c5866465-8bt58 (v1:metadata.name)
POD_NAMESPACE:    keda (v1:metadata.namespace)
Mounts:
/certs from certificates (ro)
/var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-wtkwh (ro)
Conditions:
Type              Status
Initialized       True
Ready             True
ContainersReady   True
PodScheduled      True
Volumes:
certificates:
Type:        Secret (a volume populated by a Secret)
SecretName:  kedaorg-certs
Optional:    false
kube-api-access-wtkwh:
Type:                    Projected (a volume that contains injected data from multiple sources)
TokenExpirationSeconds:  3607
ConfigMapName:           kube-root-ca.crt
ConfigMapOptional:
DownwardAPI:             true
QoS Class:                   Burstable
Node-Selectors:              kubernetes.io/os=linux
Tolerations:                 node.kubernetes.io/memory-pressure:NoSchedule op=Exists
node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:

The problem is that you need to assign more resources to the pod. It's restarting due to OOMKill. If you use helm for deploying KEDA, you can use these values to set the resources.

@JorTurFer  we have used the following command to upgrade Keda

Can you please let know how we can pass the values

Hey,
Sure, as that's helm usage related, you can find all the related information on their docs: https://helm.sh/docs/helm/helm_upgrade/
You have multiple options, overriding them inline, providing your values files, etc

@JorTurFer  Just got confused on that part .Can we have the command to set a particular spec to the Keda .Like I need to set a particular spec to the Keda Pod .As the above link is not clear on how we can set a particular spec

Hi @nidiculageorge
My previous comment has a link to helm docs about upgrade command. There you can see how you can set values during helm installation:

The values that you have to update are these: https://github.com/kedacore/charts/blob/main/keda/values.yaml#L348-L372
Sorry but I won't provide the command to you as IMHO it's totally outside KEDA's scope and it's more related with your specific job and use case than with KEDA. I'll help you with any issue related with KEDA, but I won't give you the job already done, sorry


Automatic polling

Description:
Bug reported to me that Automatic is not polling correctly. Added track_point_in_time event listener to requery the automatic service every so often.
Related issue (if applicable): fixes #
Pull request in home-assistant.io with documentation (if applicable): home-assistant/home-assistant.io#
Example entry for configuration.yaml (if applicable):

Checklist:
If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated in home-assistant.io

If code communicates with devices, web services, or a:

[x] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] New dependencies have been added to the REQUIREMENTS variable (example).
[ ] New dependencies are only imported inside functions that use them (example).
[ ] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[ ] New files were added to .coveragerc.

If the code does not interact with devices:

[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] Tests have been added to verify that the new code works.

There are two types of platforms for the device_tracker component. There are components that provide a get_scanner(…) method that will return a scanner object which will be polled at some interval for devices using get_devices(…).
Then there are the platforms that define a setup_scanner(…) method. These platforms are themselves responsible for getting the data (push, poll, whatever) and call the see method when it finds new data.
In the case of automatic, it seems like the platform defines setup_scanner(…) but uses a scanner pattern under the hood. It means that the methods get_device_name and scan_devices can be removed too.

Also, you should be able to use track_utc_time_change if you don't want to keep registering a new listener.

Cool thanks for feedback - removing those props and changing to track time change

🐬


Scoped logging helper functions

I'd like to be able to capture the logs from a specific block of go-astiav/ffmpeg code and be able to correlate a specific code block with specific log output.
I don't think doing this is possible in a perfect way, but I'm still pretty new to FFmpeg's c api and wanted to ask to make sure I'm not missing a better way to accomplish this task.
I'm picturing an api in go-astiav that looks sort of like
astiav.WithScopedLogger(myLogCallback, func() {
  // lots of go-astiav/ffmpeg code in here that has the logger overwritten/scoped somehow into this calling goroutine's instance of myLogCallback
})

I'm guessing this would have to set the ffmpeg logger to a threadsafe c dispatching function that can connect back to goroutine IDs/scopes somehow - not exactly sure of specifics here and I'm not exactly sure how this should best be implemented though.
Happy to contribute code/testing help here if I can, been having a great time working with astiav so far.

First off thanks for the kind words ❤
The way ffmpeg logging works, you won't be able to correlate logs to a block of code directly. You will however be able to correlate them to certain objects, and if those objects are specific to your block of code, you will be able to correlate logs to your block of code indirectly.
The ffmpeg log callback is global therefore you can only have one. Its signature is func(c Classer, l LogLevel, fmt, msg string) and what is the most important for you is the first argument c Classer. A Classer is an object with a method Class() *Class. Objects implementing this interface are for instance CodecContext or FormatContext.
Therefore if in your block of code you create such objects, you can save their reference and if in the log callback you get them in the Classer argument, then you know this log belongs to your block of code.
You will however also get logs without a classer (which can be nil in the log callback) and won't be able to determine whether it belongs to your block of code.
Does that answer your question?

Yeah, it definitely does! I think I should be able to get that to work. Thanks for the info!
I think there's a mechanism to get this to work more cleanly in the future (lots of user-transparent wrapping of this functionality could eventually make the API I'm looking for).
Are you interested in proposals/code that provides non 1-1 ffmpeg api functionality, but creates a more general user-friendly api?


Use a custom 'locator' state event rather than m.room.create. [rei:wedf/a]

This notably lets us re-use existing rooms if desired.
I also rip out the parts that store the schedule in the matrix room. These make it unnecessarily confusing as we have 2 sources of truth and provided privacy leaks where some of the information was private (e.g. speaker e-mail addresses).
Some exceptions — room state we keep around:

new locator, which just serves to correlate rooms with what's in the schedule
person overrides (after they accept an e-mail invite) — I've rebranded these as overrides to try to make it more obvious why we have them and how they interact with the ones in the underlying schedule.

Stacked PR Chain: rei:wedf/a

PR
Title
Status
Merges Into

#130
Allow disabling IRC bridge by not configuring one, to prevent crash

-

#131
Fix !schedule view falling over with long schedules

#130

#133
(Draft) Try to disconnect the Conference bot from being so reliant on Pentabarf (best effort)

#131

#132
(Draft) Add a JSON schedule loader

#133

#134
(Draft) Fix some misc bugs

#132

#135
(Draft) Disable features relating to Q&A if desired

#134

#136
(Draft) Refactor the backends to be called backends

#135

#137
👉 (Draft) Use a custom 'locator' state event rather than m.room.create.

#136

#138
(Draft) Add a schedule cache as a fallback for if the original schedule goes offline

#137

#139
(Draft) Add a status command to get some information about the bot and its situation

#138

Wooot neat that was killing me. One source to rule them all !


docs: fix order of --no-deps when pip installing in editable mode

The current documentation will trigger the following error:
ERROR: --no-deps is not a valid editable requirement. It should either be a path to a local project or a VCS URL (beginning with bzr+http, bzr+https, bzr+ssh, bzr+sftp, bzr+ftp, bzr+lp, bzr+file, git+http, git+https, git+ssh, git+git, git+file, hg+file, hg+http, hg+https, hg+ssh, hg+static-http, svn+ssh, svn+http, svn+https, svn+svn, svn+file).

In editable mode, --no-deps is just required to be before the -e.

Thanks!


[7] Create API endpoint for GET Surveys

Why
To test out the capability of Livebook to document an API, we need to have a local API against which we can run query against.
Acceptance

Add endpoint GET v1/surveys.
Follow the structure from the Nimble Survey list API :

Done in https://github.com/nimblehq/liveman-demo-api/pull/25


Undefined names (low priority)

We've got undefined names in a couple of spots around the codebase. See this linter log. I'm calling this low-priority because if neither tests nor users have caught these then apparently these units aren't terribly important.

Closed by #57


Why is there a hover effect but no action on the team name?

On Firefox (+ mabe others), there is a hover effect but no action on class="sc-header--team-name" - should we remove the effect or add an action such as optional link?

yea let's remove the hover effect

@dharness Wouldn't it be nice if this issue was auto-closed now based on the linked PR being merged? :heart_eyes:

Sometimes an issue may be completed across multiple PRs though