Fixed cachegroup deliveryservice ISE

What does this PR (Pull Request) do?

[x] This PR fixes #2932

Which Traffic Control components are affected by this PR?

Traffic Ops

What is the best way to verify this PR?
Create a cachegroup with no severs.
Perform the following command:
curl -XPOST --cookie $mc -Lvsk https://localhost:6443/api/1.4/cachegroups/473/deliveryservices -d @cachegroup_deliveryservice.json | jq .
The following criteria are ALL met by this PR

[x] This PR includes tests OR I have explained why tests are unnecessary

I don't think I could test anything useful.

[x] This PR includes documentation OR I have explained why documentation is unnecessary

No new significant updates.

[x] This PR includes an update to CHANGELOG.md OR such an update is not necessary

No new significant updates.

[x] This PR includes any and all required license headers
[x] This PR ensures that database migration sequence is correct OR this PR does not include a database migration
[x] This PR DOES NOT FIX A SERIOUS SECURITY VULNERABILITY (see the Apache Software Foundation's security guidelines for details)

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/trafficcontrol-PR/3658/
Test FAILed.

you could write a test that tries to
POST api/1.4/cachegroups/473/deliveryservices where 473 has zero caches and ensure that a 400 comes back...

retest this please

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/trafficcontrol-PR/3668/
Test PASSed.


Extend kernel dependencies in v3.10 doc

Description
Not all of the Kernel dependencies were mentioned in the documentation.
Related issues/PRs
partly fixes https://github.com/projectcalico/calicoctl/issues/1444
Todos

[ ] Backport to older versions

 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.

Deploy preview for calico ready!
Built with commit a1b67bd57e3ec6dce6f7bb56f51ea088b77ca67b
https://deploy-preview-3076--calico.netlify.com

What is your thinking around the separate Calico and Felix list?
I think it should be one list and not try to identify what modules are required for any specific components. I also think it is unclear what is meant by Calico as I would normally assume that Calico includes Felix.
@fasaxc This list looks right to me but you would know much better than me, would you take a look please?

Agreed, felix is the only component that touches the dataplane so it's really just one list.

Thank you i updated the PR to contain only one list


Use --enable-preview when testing against JDK 19

Plus a few minor improvements in the Jenkinsfile to make adding that --enable-preview arg easier.
Not sure referencing DEFAULT_JDK_VERSION from the BuildEnvironment class will work correctly, so let's see if CI passes...

Not sure referencing DEFAULT_JDK_VERSION from the BuildEnvironment class will work correctly, so let's see if CI passes...

Well it didn't work, so I changed that part.


Bug on multi-select

There's a bug in the multi-select where any item you click or start a drag on remains selected, so when you drag another item, it brings all the previously clicked items as well
https://imgur.com/a/82W97sn
I click-dragged character1.txt but the other came together. This only happens after you select an item, before that click-drag works fine

@Syed-Sheharyar This should be fixed at v0.0.21


eosio_assert write error message to console

I wrote a contract with the following code:
    void printerr()
    {
        eosio_assert(1 == 2, "One is not equal to two.");
    }

If I push the action using cleos I do not receive the error message only a generic assert failed:
Error 3050003: eosio_assert_message assertion failure
I can see the error message from nodeos if I use --contracts-console.  Is there any way to see the error message using cleos or eosjs?
Thank you

Did you find the answer? It will be useful for testing.

https://github.com/EOSIO/eos/issues/4547 contain the answer: You need to use --verbose-http-errors for nodeos.


mobile SERP

Hi @ecoron , thanks a lot for your script and I'm wondering if I can scrape the SERP as mobile device. I've seen the user_agent.py and I've switched the computer and mobile user agent. I guess it's not a good idea, as the warning below:
2018-07-24 10:25:30,725 - scrapcore.scraper.selenium - ERROR - Skip it, no such element - SeleniumSearchError
Exception in thread [google]SelScrape:
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/dist-packages/scrapcore/scraper/selenium.py", line 600, in wait_until_serp_loaded
    str(self.page_number)
  File "/usr/local/lib/python3.6/dist-packages/selenium/webdriver/support/wait.py", line 80, in until
    raise TimeoutException(message, screen, stacktrace)
selenium.common.exceptions.TimeoutException: Message:
Screenshot: available via screen

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.6/dist-packages/scrapcore/scraper/selenium.py", line 606, in wait_until_serp_loaded
    self.webdriver.find_element_by_css_selector(selector).text
  File "/usr/local/lib/python3.6/dist-packages/selenium/webdriver/remote/webdriver.py", line 589, in find_element_by_css_selector
    return self.find_element(by=By.CSS_SELECTOR, value=css_selector)
  File "/usr/local/lib/python3.6/dist-packages/selenium/webdriver/remote/webdriver.py", line 955, in find_element
    'value': value})['value']
  File "/usr/local/lib/python3.6/dist-packages/selenium/webdriver/remote/webdriver.py", line 312, in execute
    self.error_handler.check_response(response)
  File "/usr/local/lib/python3.6/dist-packages/selenium/webdriver/remote/errorhandler.py", line 237, in check_response
    raise exception_class(message, screen, stacktrace)
selenium.common.exceptions.NoSuchElementException: Message: {"errorMessage":"Unable to find element with css selector '#navcnt td.cur'","request":{"headers":{"Accept":"application/json","Accept-Encoding":"identity","Connection":"close","Content-Length":"105","Content-Type":"application/json;charset=UTF-8","Host":"<IP_ADDRESS>:58099","User-Agent":"Python http auth"},"httpVersion":"1.1","method":"POST","post":"{\"using\": \"css selector\", \"value\": \"#navcnt td.cur\", \"sessionId\": \"d1d12330-8f2b-11e8-8bc9-69459efa1ced\"}","url":"/element","urlParsed":{"anchor":"","query":"","file":"element","directory":"/","path":"/element","relative":"/element","port":"","host":"","password":"","user":"","userInfo":"","authority":"","protocol":"","source":"/element","queryKey":{},"chunks":["element"]},"urlOriginal":"/session/d1d12330-8f2b-11e8-8bc9-69459efa1ced/element"}}
Screenshot: available via screen

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3.6/threading.py", line 916, in _bootstrap_inner
    self.run()
  File "/usr/local/lib/python3.6/dist-packages/scrapcore/scraper/selenium.py", line 761, in run
    self.search()
  File "/usr/local/lib/python3.6/dist-packages/scrapcore/scraper/selenium.py", line 701, in search
    self.wait_until_serp_loaded()
  File "/usr/local/lib/python3.6/dist-packages/scrapcore/scraper/selenium.py", line 610, in wait_until_serp_loaded
    raise SeleniumSearchError('Stop Scraping, seems we are blocked')
scrapcore.scraping.SeleniumSearchError: Stop Scraping, seems we are blocked

Traceback (most recent call last):
  File "/usr/local/lib/python3.6/dist-packages/serpscrap/csv_writer.py", line 11, in write
    w = csv.DictWriter(f, my_dict[0].keys(), dialect='excel')
IndexError: list index out of range
None
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/dist-packages/serpscrap/csv_writer.py", line 11, in write
    w = csv.DictWriter(f, my_dict[0].keys(), dialect='excel')
IndexError: list index out of range

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/tmp/serpscraper1.py", line 21, in <module>
    results = scrap.as_csv('/tmp/output')
  File "/usr/local/lib/python3.6/dist-packages/serpscrap/serpscrap.py", line 134, in as_csv
    writer.write(file_path + '.csv', self.results)
  File "/usr/local/lib/python3.6/dist-packages/serpscrap/csv_writer.py", line 17, in write
    raise Exception
Exception

Is there any other method to apply to mobile SERP as well?
Any suggestions would be really appreciated.
C

i would recommend to use the chrome headless instead, since selenium/phantomjs is detected very fast.
i'm not tested yet if its possible to get the mobile results by default


Add build constraints for non cgo

Closes https://github.com/mattn/go-sqlite3/issues/757

Coverage remained the same at 50.364% when pulling fc06e553050f9a45829cdcde48931526ec7e79f8 on noncgo into 67c1376b46fb54cb953532f136c9b8accefca46b on master.


404 at /machine/img/provision-use-case.png

I found a broken link : https://docs.docker.com/machine/img/provision-use-case.png
I arrived on this page through: https://courses.edx.org/

This looks like a broken link on an external website, which is not something we can fix; I'd recommend reporting it there.


BugReporting

Describe the bug
I don't know what is the bug on StackBlitz. But you can find a bug in your code editor. :)
Link to the blitz that caused the error
https://stackblitz.com/edit/node-qeved9
Steps to reproduce

Go and make a project the type will be node.js
A few moments later a button will appear its saying File a bug

Expected behavior
A button it saying File a bug was appeared when i tapped that it was move me here the bug reporting on github.com
Screenshots
No response
Platform
Browser name  = Chrome
Full version  = 92.0.4515.115
Major version = 92
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/92.0.4515.115 Safari/537.36
performance.memory = {
  "totalJSHeapSize": 131000000,
  "usedJSHeapSize": 123000000,
  "jsHeapSizeLimit": 747000000
}

Additional context
No response

Good one! :joy:


Fix since from time picker in final code for lab 3

Super simply one, this is clearly supposed to be MINUTES not SECONDS

 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.


Per Style Extract Option with Custom Named Styles

Bug Report or Feature Request (mark with an x)

[ ] bug report -> please search issues before submitting
[x] feature request

Versions.

@angular/cli: 1.0.0-rc.2
node: 7.7.2
os: linux x64
@angular/common: 2.4.9
@angular/compiler: 2.4.9
@angular/core: 2.4.9
@angular/forms: 2.4.9
@angular/http: 2.4.9
@angular/platform-browser: 2.4.9
@angular/platform-browser-dynamic: 2.4.9
@angular/router: 3.4.9
@angular/cli: 1.0.0-rc.2
@angular/compiler-cli: 2.4.9
Desired functionality.

The features provided by #3401 have been very helpful, however, I have a need for an additional option for styles which would override the global --extract-css option on a per stylesheet basis.
Example:
"styles": [
  "styles.scss",
  { "input": "preload.scss", "output": "preload-styles", "extract": True }
],

My usecase is I am wanting the main styles to be loaded asynchronously via the javascript bundle to allow the page content to load, but keep a small stylesheet which is loaded immediately. The small stylesheet generally contains minimal styles for my loading screen and loading animation.
Obviously, I can manually compile my preload styles and inline them into my index.html to achieve the same effect, but it would be nice to have this accomplished all in the build step.

We use extract with another meaning in the CLI. Extracting CSS in builds is opposed to keeping the CSS inside a JS bundle (as webpack does by default).
I agree with your usecase and think it would be a nice feature to have. Would just name it something like inline instead.

@seglberg I'd recommend you to explore ngx-build-plus to customize your build for this feature. In case you find that it's not possible to satisfy your use case, please open a new issue. Thanks! :)


SPDX file with invalid Created value is flagged as valid by tools-java

fusionforge.spdx.json.txt
pyspdxtools -i fusionforge.spdx.json
ERROR:root:There have been issues while parsing the provided document:
Error while parsing Document: ["time data '2024-02-08T16:01:17.629Z' does not match format '%Y-%m-%dT%H:%M:%SZ'"]

java-tools 1.1.8 says:
This SPDX Document is valid.

It seems tools-python is right, no decimal part for seconds is allowed by the spec.

I just checked the spec for the created field and I agree, the decimals are not allowed.
Once I'm done with the 3.0 version, I'll look into this issue.


Additional tests for measure.py, table.py, padding.py and containers.py, as well as some possible code fixes

Type of changes

[x] Bug fix (See description under table.py and containers.py)
[ ] New feature
[ ] Documentation / docstrings
[x] Tests
[ ] Other

Checklist

[x] I've run the latest black with default args on new code.
[ ] I've updated CHANGELOG.md and CONTRIBUTORS.md where appropriate.
[x] I've added tests for new code.
[x] I accept that @willmcgugan may be pedantic in the code review.

Description
Some additional tests in response to #37 for the following files:

measure.py

test_null_get: Checks for cases where Measurement.get() should return Measurement(0, 0)
test_measure_renderables: Tests that measure_renderables returns the correct Measurement object

table.py

test_append_column: Checks whether headers are correctly added to self.columns in Table. I'm not too sure if this test is meaningful enough though.
test_rich_measure: Checks whether the __rich_measure__ method of Table returns the correct Measurement object for several cases
Tried to add a test for lines 496-497, however I can't engineer a case where the code in try would raise a ValueError:try:
    second_max_column = max(
        width if allow_wrap and width != max_column else 0
        for width, allow_wrap in zip(widths, wrapable)
    )
except ValueError:
    second_max_column = 0

Afaik, a ValueError would only be thrown by max() in a situation where an empty sequence is passed to it. But for us to get to the try/except, both widths and wrapable would have to be valid, which would in turn generate valid arguments for the max() function. Because of this, I'm not convinced a try/except for a ValueError is necessary in the function and hence removed it from the method..

padding.py

test_indent: Tests the indent method of Padding. Also not sure if this test is meaningful enough.
test_rich_console: Tests the output of the __rich_console__ method

containers.py

test_lines_justify Tests the outputs of the justify method for Lines
It seems the if next_word is None: condition in line 156 of conatiners.py will never be triggered as next_word will only be None if index == len(spaces), however the preceeding if index < len(spaces):  skips the execution of the if next_word is None: condition.

if index < len(spaces):
        if next_word is None: # Only occurs if index==len(spaces)?
            space_style = Style.null()
        else:
            style = word.get_style_at_offset(console, -1)
            next_style = next_word.get_style_at_offset(console, 0)
            space_style = style if style == next_style else line.style

Propose removing the if/else like so and have made a corresponding change in the PR:if index < len(spaces):
        style = word.get_style_at_offset(console, -1)
        next_style = next_word.get_style_at_offset(console, 0)
        space_style = style if style == next_style else line.style

Looking forward to your feedback!

@MoltenMuffins This is looking good.
You may be correct about that ValueError.
I don't understand why codecov is saying the coverage decreased!

@willmcgugan Hi, thanks for looking at my WIP! I was trying to figure out where the coverage decrease was coming from, but it seems it isn't from any of the files I made changes to (provided I'm intepreting the codecov report correctly). I have also added tests for containers.py to the PR and have marked it ready for review.
I also realize that codecov ignores several files that I have added tests for, should these be removed?

Looking at the codecov report
It seems the following files are being ignored?

‘tests/test_containers.py’
‘tests/test_table.py’
‘tests/test_measure.py’
‘tests/test_padding.py’
‘tests/table.py’

Screenshot:

That is strange. The tests/ directory is excluded from coverage, but I have no idea why it would ignore table.py.
Nothing in the configuration I could see that could cause this, and I'm sure it was working previously.
Safe to say, something has gone wrong with codecov. This PR has definitely increased coverage.

Thanks.

Glad I could help! :+1:


Fixed #13677 -- Propogated database choice from ModelFormSet queryset to ModelForm's choices.

Moved the patch by @dgouldin to current Django.

I'm not entirely in favor of this patch, I just moved it up from Django 1.2 - I think the use of get_queryset() might lead to performance issues, especially since it is called on every BaseModelForm creation.

I don't think there are performance issues because get_queryset()._db doesn't evaluate the queryset. I would expect the using argument also be applied to model.save() to avoid the workaround described at https://stackoverflow.com/questions/37740848/use-a-specific-database-with-a-modelform? Documentation for the new argument is needed.

To answer your questions on IRC:

to use the 'using' in 'save' calls, we need to keep it on the modelform - would you name it 'using' or '_using'?
I don't see a need for the underscore prefix.

I'm not quite sure where I'm to document the new parameter – it'll definitely have to go into topics/forms/modelform.txt, but I haven't found a place in ref/ where it'd go. Is there something I overlooked?
The link for ModelForm is here: docs/topics/forms/modelforms.txt:.. class:: ModelForm. Preceding this change, that could be moved to ref/forms/models.txt and the __init__() parameters documented in some detail.

I added the using attribute, and I will add documentation next week. After that, I'll be offline for two weeks, and will respond to further comments after that.

Hah, "two weeks".
As there is no real place to add the using attribute, I added a short reference documentation of ModelForm. As I am not a native speaker, I'd appreciate any comment on my phrasing there. Other than that I'd consider this PR ready for review. 👓

I rebased against current master. The test is no longer ready for merging due to a deprecation notice:
django.utils.deprecation.RemovedInDjango31Warning: `TestCase.multi_db` is deprecated. Databases available during this test can be defined using multiple_database.tests.ModelFormsetUsingTestCase.databases.

Could you point me at an example of a test case that was migrated from multi_db to databases? I'd be willing to apply that change here, too.

Use git log -S multi_db to find the relevant commit (8c775391b78b2a4a2b57c5e89ed4888f36aada4b).

Fixed the tests, separated the documentation into a separate commit. Should be good to go now.

Hey @rixx are you still working on this?

Closing due to inactivity.


Can't read re-segmented Xenium data

Hello,
I have re-run cell segmentation for my Xenium data using Xenium Ranger version <IP_ADDRESS> to benefit from its improved segmentation algorithm. I can't read the re-segmented data with spatialdata_io.xenium(), even though the original output can be read. I have spatialdata-io version 0.1.4.

Error message
sample1_v2 = spatialdata_io.xenium(sample1_loc)

INFO     reading
         /mnt/storage/vaquerizas/xenium/outputs/XR_0014511/00145
         11/outs/cell_feature_matrix.h5

---------------------------------------------------------------------------
KeyError                                  Traceback (most recent call last)
Cell In[6], line 1
----> 1 sample1_v2 = spatialdata_io.xenium(sample1_loc)

File /mnt/storage/vaquerizas/liz/spatial/xenium/python_analysis/spatialdata_env/lib/python3.10/site-packages/spatialdata_io/_utils.py:46, in deprecation_alias.<locals>.deprecation_decorator.<locals>.wrapper(*args, **kwargs)
     44 class_name = f.__qualname__
     45 rename_kwargs(f.__name__, kwargs, aliases, class_name)
---> 46 return f(*args, **kwargs)

File /mnt/storage/vaquerizas/liz/spatial/xenium/python_analysis/spatialdata_env/lib/python3.10/site-packages/spatialdata_io/readers/xenium.py:227, in xenium(path, cells_boundaries, nucleus_boundaries, cells_as_circles, cells_labels, nucleus_labels, transcripts, morphology_mip, morphology_focus, aligned_images, cells_table, n_jobs, imread_kwargs, image_models_kwargs, labels_models_kwargs)
    218     labels["nucleus_labels"], _ = _get_labels_and_indices_mapping(
    219         path,
    220         XeniumKeys.CELLS_ZARR,
   (...)
    224         labels_models_kwargs=labels_models_kwargs,
    225     )
    226 if cells_labels:
--> 227     labels["cell_labels"], cell_labels_indices_mapping = _get_labels_and_indices_mapping(
    228         path,
    229         XeniumKeys.CELLS_ZARR,
    230         specs,
    231         mask_index=1,
    232         labels_name="cell_labels",
    233         labels_models_kwargs=labels_models_kwargs,
    234     )
    235     if cell_labels_indices_mapping is not None and table is not None:
    236         if not pd.DataFrame.equals(cell_labels_indices_mapping["cell_id"], table.obs[str(XeniumKeys.CELL_ID)]):

File /mnt/storage/vaquerizas/liz/spatial/xenium/python_analysis/spatialdata_env/lib/python3.10/site-packages/spatialdata_io/readers/xenium.py:446, in _get_labels_and_indices_mapping(path, file, specs, mask_index, labels_name, labels_models_kwargs)
    443     real_label_index = real_label_index[1:]
    445 if version < packaging.version.parse("2.0.0"):
--> 446     expected_label_index = z["seg_mask_value"][...]
    448     if not np.array_equal(expected_label_index, real_label_index):
    449         raise ValueError(
    450             "The label indices from the labels differ from the ones from the input data. Please report "
    451             f"this issue. Real label indices: {real_label_index}, expected label indices: "
    452             f"{expected_label_index}."
    453         )

File /mnt/storage/vaquerizas/liz/spatial/xenium/python_analysis/spatialdata_env/lib/python3.10/site-packages/zarr/hierarchy.py:511, in Group.__getitem__(self, item)
    509         raise KeyError(item)
    510 else:
--> 511     raise KeyError(item)

KeyError: 'seg_mask_value'

Is this related to #150 ? i.e. is Xenium Ranger reanalysis not supported?
Thanks in advance for your help with this.

Hi thanks for reporting. The code branch that is executed detects that the data is versioned with a number < 2.0.0. It could be that using XR <IP_ADDRESS> changes some specific data to the newest version but not the global data versioning.
I would suggest to manually parse the data in this case; you can see information and tutorials on how to proceed in the linked issue #150, and you could use the xenium.py code as a starting point.

Hi, thanks for the reply. I'll try adapting the code from spatialdata_io/readers/xenium.py to parse this format. I'll let you know if I figure out what's actually been changed in the resegmentation.
FWIW, I had a look at how the version is detected by spatialdata_io.readers.xenium, and it's technically being detected correctly, as this is what the relevant parts of my experiment.xenium file look like:
{
    "major_version": 4,
    [...snipped...]
    "instrument_sw_version": "<IP_ADDRESS>",
    "analysis_sw_version": "xenium-<IP_ADDRESS>",
     [...snipped...]
    },
    "xenium_explorer_files": {
    [...snipped...]
    },
    "xenium_ranger": {
        "run_id": "0014511",
        "version": "xenium-<IP_ADDRESS>",
        "command_line": "xeniumranger resegment --id=0014511 --xenium-bundle=/mnt/scratch/egi12/xenium/output-XETG00207__0014511__Region_1__20240315__115210/ --jobmode=slurm --disable-ui=true"
    },
    "segmentation_stain": ""
}

Thanks for sharing the details. Maybe a fix could involve looking for xenium_ranger in the metadata and when the field is available, using this specific version for determining the code branch used by xenium() in spatialdata-io.

I managed to read in the data by adapting the code from spatialdata_io/readers/xenium.py to use the branches appropriate for version >= 2.0.0. So I think your idea to use the version in the xenium_ranger field in the metadata would work.
Caveats: 1) I didn't read in the transcripts as I don't need them for my current analysis 2) although I didn't get any errors/warnings, I don't know for sure that all the output is correct as I'm not super familiar with the data structures.

@liz-is I have this same issue with xeniumranger 3.0.1 resegment.
Do you still the code you changed spatialdata_io/readers/xenium.py, so I could work off of it, please?
Were you able to get the transcripts loaded in as well?
Thank you very much in advance. same error. I am on spatialdata 0.2.5.post0.


Update and rename mcleod to mcleod.json

and remove extra comma in conform JSON object

Lookin' good, thanks!


feat(catalog-import): Add instructions to Pull Request description when registering a new component

Hey, I just made a Pull Request!

Enhances the pull request description to guide the recipient for when a new pull request is added to GitHub.

NB: I added the name of their backstage instance and a link to get straight to the Backstage Base URL. When using GitHub.com, I suppose there could be a scenario where users might not want to expose the name of their catalog even if their components are open source, but I'd consider that an edge case because if their code is truly open source, the info about them having a named catalog or it's URL may be as well? I believe having that info would make it a lot easier to proceed with the next step. Open to opinions on it.
:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[x] Screenshots attached (for UI changes)

I think this is quite specific for every adopter. Maybe we should make the summary and body configurable from the outside? I also think that the generated YAML file itself should be passend in as a template from the outside. We for example would like to introduce some comments that give custom instructions (like where our documentation is) and pre fill some fields. That could solve topics like #3678 too.

@Fox32 I do like that idea.  I wonder if we take step steps,

A more simple version of what I put here just to get SOMETHING into the PR text for now, and then
Spin out a new issue to externalize/template the content?  e.g., it could pull from a URL or something like that, or even just make it pull in something from the deployed app which can be customized on each instance, but identifying the mechanics of that potentially pulled separately?

If you agree, we could either merge this as is and spint out the new issue, or simplify this say by removing the last sentence just to say,

This pull request adds a Backstage entity metadata file
to this repository so that the component can be added to the
software ${appTitle} software catalog.
After this pull request is merged, the component will become available.

Thoughts?

I'd say this is a good start and can be iterated on. Definitely better then a blank PR with no description.
Longer term I could also see this perhaps pulling in an appropriate PR template from the target repo (if found).


Added additional support for loading (implicit parent data) and exporting (in the context of exportplink) fam files

Added additional support for loading (implicit parent data) and exporting (in the context of exportplink) fam files

Can you resubmit this from your forked repository?  Thanks!


automations add ins?

it would be great to have on Automation Editor graphical to have a delete button to delete de automations you dont what and i think a thing that could be great to have is to add ors and ands on conditions | e &
Component/platform:
Description of problem:
Expected:
Problem-relevant configuration.yaml entries and steps to reproduce:

Traceback (if applicable):

Additional info:

You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum. Thanks!

sorry thank you


feat: pr title description

Description
Please include a summary of the change and which issue is fixed.
List any external dependencies that are required for this change.

[ ] PR title and description are to the point and understandable
[ ] I have performed a self-review of my own code'

@Jossilainen  dette er en test pr så trenger ikke godkjenning


Add Unit Test Coverage to CI

Proposed Changes
Add in Go unit test results from the "pkg" folder to our CI and PR process. Tests are run via GitHub actions and  reports are sent to Codecov for review. As of now, this is only informational reporting and is a nonblocking check on PRs.
Types of Changes
Added 2 new files:
unitcoverage.yaml: Added a new github action to execute go test and produce code coverage results.
.codecov.yml: Configuration for how Codecov status checks are shown on GitHub.

Verification
Committing to a branch (or opening a PR) triggers a new action:

Which once run add a Codecov check and links to a report:

Linked Issues
https://github.com/k3s-io/k3s/issues/3444
Further Comments
The decision to use Codecov and Github actions was one of simplicity, visibility and cost (Free). Only 2 files have been added, and they are both visible to all developers. No other configuration is needed (especially avoiding any separate website config), giving the same experience across all work-spaces. Other ideas considered were: rolling/hosting our own code cov reports, Coveralls, and Codacy.
Further integration with Codecov (such as adding in Github app/bot to our repo) was rejected to keep things simple and allow for an evaluation period. Drone testing results can be integrated into the reports in the future.

If we're going to run tests here, can we remove the go test from https://github.com/k3s-io/k3s/blob/master/scripts/validate#L36 ?

I have removed the go test from validate @brandond.

Need to reopen this.


feat: validate Delivery response

fixes PRO-4312
BREAKING CHANGE: This changes the interface to ApiClient.
This PR supports:

Validating the Delivery Response.  It checks for requestId which will catch most integration errors.
Simplify the ApiClient code by accepting any and handling the validation internally.

TODO - I need to update the axios and got examples.
TESTING=Unit tests.  I'll try this in a code base after merging the PR.

I tried using the npm link code in an example project and it didn't work.


Unit 6: Fix for installing notebook dependencies

Fixes https://github.com/huggingface/deep-rl-class/issues/251.
Currently, this notebook can't be run because of an error while installing the dependencies.
The error comes from trying to install the stable-baselines3 package. They are aware of this bug and working on it for the next version. Their current workaround is to use the 65.5.0 version of setuptools by running pip install setuptools==65.5.0. For more information, see https://github.com/DLR-RM/stable-baselines3/issues/1324.
Adding the line setuptools==65.5.0 at the top of the requirements-unit6.txt file doesn't solve the problem since pip doesn't have a way to install packages in order (see https://github.com/pypa/pip/issues/2362).
Therefore, the solution is to add a new code cell to the notebook to run pip install setuptools==65.5.0 before installing requirements-unit6.txt.

The same issue is happening in the notebook from Unit 1. As a solution, the same code cell is added to notebook 1. Fixes https://github.com/huggingface/deep-rl-class/issues/253 and https://github.com/huggingface/deep-rl-class/issues/255.

This helped thanks!

Thanks a lot for this fix!! 🔥

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


Provisioning Kafka connectors takes too much time

Despite the connector type (custom or confluent), deployment takes ~6m 30s.
In addition, even if the status is set to PAUSED, the connector is provisioned as RUNNING.
custom
confluent_connector.nats_sink: Creation complete after 6m27s [id=clcc-......]
confluent_connector.nats_source: Creation complete after 6m27s [id=clcc-......]

confluent
confluent_connector.dynamodb_sink: Creation complete after 6m12s [id=lcc-......]
confluent_connector.http_sink: Creation complete after 6m12s [id=lcc-......]

Actually, connectors get provisioned roughly in 2m 20s.

@dobeerman thanks for creating this issue!

In addition, even if the status is set to PAUSED, the connector is provisioned as RUNNING.

Currently, we do not support the provisioning of "PAUSED" connectors.

Actually, connectors get provisioned roughly in 2m 20s.

TF Provider's code does include a manual timeout as a workaround for other issues. See https://github.com/confluentinc/terraform-provider-confluent/issues/43#issuecomment-1293804274 for more details, thank you!


[release-0.4] Update k8s.io/apimachinery and golang.org/x/net

Fixes HTTP/2 CVE
Backport of https://github.com/medik8s/node-healthcheck-operator/pull/251 and https://github.com/medik8s/node-healthcheck-operator/pull/253
ECOPROJECT-1731

only mutation test failed
/override build-and-unit-test
/override e2e-k8s

/lgtm


Explicit column sizes in responsive grid

It looks like explicit column sizes like col col-20 etc. don't work properly in a responsive grid after the breakpoints.
When you look at the following codepen, everything seems as you expect at the first.
The columns on the right side are divided into 20 percent and the remaining space.
http://codepen.io/uloco/pen/vNeqZa
But after resizing the browser / content area into a smaller size, the breakpoint kicks in and the .col-20 area doesn't apply its explicit size anymore and the both columns fill the entire space evenly.
I don't think this is expected behaviour...

Greetings @uloco!
My sensors indicate that you need to update your issue through our custom issue form. We are now requiring all issues to be submitted this way, to ensure that we have all of the information necessary to fix them as quickly as possible.
Click Here To Update Your Issue
I will have no choice but to close this issue if it is not resubmitted through the form. Please fill out the rest of the form, so that I may use my friendly robot powers to assist you.
Thank you!

Greetings @uloco!
I've closed this issue because my sensors indicated it was old and inactive, and may have already been fixed in recent versions of Ionic. However, if you are still experiencing this issue, please feel free to reopen this issue by creating a new one, and include any examples and other necessary information, so that we can look into it further.
Thank you for allowing me to assist you.


API consistency: duration, interval and other time-related parameters

As this discussion rises, we should handle this issue before it becomes too big:

what is the rule for time-related parameters ?

Here are some thoughts:

time-based parameters are better handled in samples as the behaviour is less prone to machine error (e.g. weird behaviour of round()-like functions).
if in samples, we let the user double-check the parameters, it is extra work
if in seconds, it is consistent with mne but it requires an additional sfreq parameter (or is it?)

Proposed solution:

as most of the matlab signal processing functions work, I advice to have for all functions the sfreq=1 parameters. Therefore without explicit call of the parameters, all time-related parameters are set to an "equivalent` in samples.

Here is some caveats:

converting and roundings will be handled by ALL functions when necessary. Therefore, we should build a very consistent way to handle time-based parameters, i.e. having functions to convert_time_to_samples, check_if_samples_array, etc.
naming convention should be as consistent and as user-friendly as possible. Therefore universal names such as duration or interval should always be used if the function can handle both samples or time. If not, the function parameters should be explicit e.g. samples_duration, time_duration and these should be used with scarcity (only in low-level or private functions).

From I have experienced on the past week, I would advize to go for interval and duration in seconds. Why? Because for the study of bruxism events, scoring methods are based on durations in seconds (for example, the rules are: bursts should last "at least 0,25s", burst should be apart of less than 3s to be reunited within the same episode, and tonic episodes are at least 2s long). As well, using seconds instead of samples makes it easier for the generation of the clinical report.
All in all, as for many cases we are "undecided" for samples or seconds, but we are "imposed" for these cases, it would appear more logical to use time in seconds.
But I agree, it imposes consistency regarding hte rounding operations to pass from time to samples.

We had a huge rounding issue while using time. Therefore, now the routine on all epoching strategy is in samples to avoid shift between epochs, see #78


Functions with 'void' parameter list return "ESP_ERR_INVALID_ARG" (documentation) (IDFGH-11163)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

General issue report
I wonder if there is a reason why functions without parameters (void) can return "ESP_ERR_INVALID_ARG" according to the documentation. I found two such functions in "esp_wifi.h", I don't know if there are more functions in the project:

esp_wifi_start
esp_wifi_clear_ap_list

If this is because underlaying functions can return the ESP_ERR_INVALID_ARG error, I could understand, but I find it very confusing because the "main" API functions that users call do not take parameters.

hi @nkaaf
sorry for late reply
It is indeed because the function called inside the api returns ESP_ERR_INVALID_ARG, and we'll discuss whether to change the internal handling or change the description of the api to make it more accurate


Allow configurable parent channel

Adds configuration object of PR https://github.com/hopsoft/stimulus_reflex/pull/318 to this PR.
This way https://github.com/hopsoft/stimulus_reflex/pull/318  and https://github.com/hopsoft/stimulus_reflex/pull/322 use the same configuration API.

Closing this in favor of https://github.com/hopsoft/stimulus_reflex/pull/339


Long Code Block

So I was trying to find a way to wrap really long syntax highlighted blocks in a div element so there'd be a vertical scrollbar, but I can't seem to find a way to do it. A user posted a really long code snippet in an issue on one of my repo's and it's impossible to navigate the page. Is there a way to get a vertical scrollbar on syntax highlighted blocks?

Moved to the correct tracker https://github.com/github/markup/issues/893


Undefined symbols for architecture x86_64: "_getrandom" on Mac OS X

:bug: Bug report
Description
Compilation failed on Mac OS X on travis CI.
Undefined symbols for architecture x86_64:
            "_getrandom", referenced from:
                nanorand::entropy::unix::entropy_from_system::h55951253ee7e2e83 in libnanorand-a83c92296e1a29be.rlib(nanorand-a83c92296e1a29be.nanorand.ow5fw3sw-cgu.6.rcgu.o)
          ld: symbol(s) not found for architecture x86_64

Link: https://travis-ci.org/github/Kogia-sima/sailfish/jobs/750030765
Also, getrandom syscall is only available if the kernel supports. We must check the availability on runtime.
https://github.com/rust-random/getrandom/blob/master/src/linux_android.rs#L27-L38
Environment

Software
Version

rustc
1.48.0 (stable)

OS
Mac OS X 10.13.6

for now can I suggest using the getrandom feature?

Yeah, it seems we need getrandom feature to compile on macOS

honestly getrandom is always the preferred method of operation, it's just not default because zero-dep by default

@aspenluxxxy Thanks for your suggestion. I think it is better to call getrandom syscall on only linux or android, rather than cfg(unix)

@Kogia-sima can you test the latest master?

@aspenluxxxy I am sorry for the delay in my response. Now I got an another error.
$  cargo test --target x86_64-apple-darwin --manifest-path sailfish/Cargo.toml --no-default-features
    Updating crates.io index
    Updating git repository `https://github.com/aspenluxxxy/nanorand-rs.git`
 Downloading crates ...
  Downloaded version_check v0.9.2
  Downloaded ryu v1.0.5
  Downloaded itoap v0.1.0
   Compiling version_check v0.9.2
   Compiling ryu v1.0.5
   Compiling itoap v0.1.0
   Compiling nanorand v0.5.2-alpha.0 (https://github.com/aspenluxxxy/nanorand-rs.git#cee036fb)
error[E0425]: cannot find function `entropy_from_system` in module `crate::entropy`
  --> /Users/runner/.cargo/git/checkouts/nanorand-rs-844ffc2303295f82/cee036f/nanorand/src/rand/wyrand.rs:35:19
   |
35 |         crate::entropy::entropy_from_system(&mut entropy);
   |                         ^^^^^^^^^^^^^^^^^^^ not found in `crate::entropy`
   |
help: consider importing this function
   |
3  | use crate::entropy::darwin::entropy_from_system;
   |

https://github.com/Kogia-sima/sailfish/runs/1627227339

try now

Thank you all your work! Now CI passed.
https://github.com/Kogia-sima/sailfish/runs/1627368931?check_suite_focus=true


Don't work python script

Traceback (most recent call last):
File "./zabbix-mongodb.py", line 17, in
class MongoDB(object):
File "./zabbix-mongodb.py", line 243, in MongoDB
mongodb = MongoDB()
NameError: name 'MongoDB' is not defined
I have this error execute /etc/zabbix/zabbix-mongodb/bin/zabbix-mongodb.py
version mongodb
mongod --version
db version v4.2.0

It looks like the name of your mongodb is incorrect,  and why are you using parenthesis?
mongodb = MongoDB()


numpy array written as strings

numpy arrays with float values are written as strings. When converted to a list of floats, it's all going well.
MWE:
import toml
import numpy

numpy.random.seed(0)
x = numpy.random.rand(3)
a = {"a": x}
print(toml.dumps(a))

b = {"b": x.tolist()}
print(toml.dumps(b))

a = [ "0.5488135039273248", "0.7151893663724195", "0.6027633760716439",]

b = [ 0.5488135039273248, 0.7151893663724195, 0.6027633760716439,]

FYI: this behaviour (+ fix) is explained in the README

Cool, thanks!


Notification template page - when edit image is not display

Describe the bug

when edit image is not display in edit form

https://www.berrycast.com/conversations/fa487e7e-adc4-54e5-94d6-f9bcec86016d


fix: update to eye v10.2.3

fix: update to eye v10.2.3

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

npm package (@latest dist-tag)
GitHub release
v15.2.3

Your semantic-release bot :package::rocket:


No systray menu showing on Linux

I have a Go app which needs to run on Linux, Windows, macOS. Getlantern has been a bit flakey for me and I am looking for something better. WebView falls a little short too. But one thing at a time.
I've tried the fyne systray and it works for me on Windows and Mac but not on Linux. Using the example code, I get the Icon but nothing more. Linux is my main development environment. Then I compile it again on Windows and macOS. Not cross-compiled.
I've tested on Linux Mint 20.3 Cinnamon with go 1.18.1. I get the icon and nothing else. It also did the same nothing on Ubuntu 20.04 and nothing at all on Fedora 35. Seems fine on Windows 10 and macOS.
And yes. The getlantern version works fine on the same systems. Except when they release new bugs.
Nothing other than vanilla installs here. In the debug testing, I created clean VMs (VMware 16) using Mint 20.3 (Cinnamon) and Ubuntu 20.04. Nothing special was installed other than the recommended OS updates. The behaviour matched my Development PC's Mint 20.3.
On Fedora 35 I did not get an icon either. But I'm hoping it's part of the same issue.
Using only the example code... And go 1.18.1 on Mint 20.3 Cinnamon. Not a VM but an Intel PC. Also using VScode.
The icon shows up. Hovering over the icon says "Awesome App". Right-click the icon and a tall skinny blank rectangle sometimes pops up (.5" w x 2" h). No text.
Looking forward to getting this going so I can stop using getlantern.
Thanks
go.mod:
module fsystray

go 1.18

require fyne.io/systray v1.9.0

require (
	github.com/godbus/dbus/v5 v5.0.4 // indirect
	golang.org/x/sys v0.0.0-20200515095857-1151b9dac4a9 // indirect
)

main.go:
package main

import (
	"fmt"
	"io/ioutil"
	"time"

	"fyne.io/systray"
	"fyne.io/systray/example/icon"
)

func main() {
	onExit := func() {
		now := time.Now()
		ioutil.WriteFile(fmt.Sprintf(`on_exit_%d.txt`, now.UnixNano()), []byte(now.String()), 0644)
	}

	systray.Run(onReady, onExit)
}

func onReady() {
	systray.SetTemplateIcon(icon.Data, icon.Data)
	systray.SetTitle("Awesome App")
	systray.SetTooltip("Lantern")
	mQuit := systray.AddMenuItem("Quit", "Quit the whole app")
	go func() {
		<-mQuit.ClickedCh
		fmt.Println("Requesting quit")
		systray.Quit()
		fmt.Println("Finished quitting")
	}()

	// We can manipulate the systray in other goroutines
	go func() {
		systray.SetTemplateIcon(icon.Data, icon.Data)
		systray.SetTitle("Awesome App")
		systray.SetTooltip("Pretty awesome棒棒嗒")
		mChange := systray.AddMenuItem("Change Me", "Change Me")
		mChecked := systray.AddMenuItemCheckbox("Checked", "Check Me", true)
		mEnabled := systray.AddMenuItem("Enabled", "Enabled")
		// Sets the icon of a menu item. Only available on Mac.
		mEnabled.SetTemplateIcon(icon.Data, icon.Data)

		systray.AddMenuItem("Ignored", "Ignored")

		subMenuTop := systray.AddMenuItem("SubMenuTop", "SubMenu Test (top)")
		subMenuMiddle := subMenuTop.AddSubMenuItem("SubMenuMiddle", "SubMenu Test (middle)")
		subMenuBottom := subMenuMiddle.AddSubMenuItemCheckbox("SubMenuBottom - Toggle Panic!", "SubMenu Test (bottom) - Hide/Show Panic!", false)
		subMenuBottom2 := subMenuMiddle.AddSubMenuItem("SubMenuBottom - Panic!", "SubMenu Test (bottom)")

		systray.AddSeparator()
		mToggle := systray.AddMenuItem("Toggle", "Toggle some menu items")
		shown := true
		toggle := func() {
			if shown {
				subMenuBottom.Check()
				subMenuBottom2.Hide()
				mEnabled.Hide()
				shown = false
			} else {
				subMenuBottom.Uncheck()
				subMenuBottom2.Show()
				mEnabled.Show()
				shown = true
			}
		}

		for {
			select {
			case <-mChange.ClickedCh:
				mChange.SetTitle("I've Changed")
			case <-mChecked.ClickedCh:
				if mChecked.Checked() {
					mChecked.Uncheck()
					mChecked.SetTitle("Unchecked")
				} else {
					mChecked.Check()
					mChecked.SetTitle("Checked")
				}
			case <-mEnabled.ClickedCh:
				mEnabled.SetTitle("Disabled")
				mEnabled.Disable()
			case <-subMenuBottom2.ClickedCh:
				panic("panic button pressed")
			case <-subMenuBottom.ClickedCh:
				toggle()
			case <-mToggle.ClickedCh:
				toggle()
			case <-mQuit.ClickedCh:
				systray.Quit()
				fmt.Println("Quit2 now...")
				return
			}
		}
	}()
}

For Gnome based desktops you need to install and enable the gnome-shell-extension-appindicator, which we should add to the documentation.
With that enabled the icon will certainly appear and the menu should as well.
For the empty menu I appreciate you have tested many different distros, but were they all running the same (cinnamon?) desktop/window manager? I can replicate the empty menu on Cinnamon but wondering if we can narrow it down to just that one software...

Mint says:
$ lsb_release -a
No LSB modules are available.
Distributor ID:	Linuxmint
Description:	Linux Mint 20.3
Release:	20.3
Codename:	una

$ wmctrl -m
Name: Mutter (Muffin)
Class: N/A
PID: N/A
Window manager's "showing the desktop" mode: N/A

$ cat /etc/X11/default-display-manager
/usr/sbin/lightdm

Ubuntu says:
$ lsb_release -a
No LSB modules are available.
 I got no icon or anything else. Though, I've not used Fedora in many many years. Is Fedora supposed to work?

Distros that use modern Gnome will need to install an appindicator/systray plugin as they have removed support by default.

OK I think I cracked it, let me know if this PR fixes things please @precisionpete

Going to assume this is resolved as that is what my testing indicates.

@andydotxyz I'm not able to get the current master working on Linux Mint 20.3
2022/05/27 19:29:08 Failed to register our icon with the notifier watcher, maybe no tray running?

@andydotxyz I'm not able to get the current master working on Linux Mint 20.3

Can you be more specific please? Mint ships in 4 variants with different desktop environments.
My guess is that the configuration you are using does not have a appindicator compliant system tray (either none at all, or a legacy one?)

Sorry. Here's more:
$ wmctrl -m
Name: Mutter (Muffin)
Class: N/A
PID: N/A
Window manager's "showing the desktop" mode: N/A

$ cat /etc/X11/default-display-manager
/usr/sbin/lightdm

It looks like "Mutter" means that Gnome is loaded, which means the previous comment applies:

For Gnome based desktops you need to install and enable the gnome-shell-extension-appindicator, which we should add to the documentation.
With that enabled the icon will certainly appear and the menu should as well.

Did you try that, and/or does it help?

added that package, not sure how to "enable" it. Doesn't show up in tweaks and there is no ~/.local/share/gnome-extensions

Sorry I am no expert and it varies from distro to distro.
Or there is the source docs instead https://github.com/ubuntu/gnome-shell-extension-appindicator


[ci skip] [cf admin skip] NO_CI adding inspection update-grayskull

Checklist

[ ] Used a personal fork of the feedstock to propose changes

@tswast, I'd recommend using inspection: update-grayskull if you're going to automerge.  pip check will often pass even  if dependency constraints aren't updated correctly and this recipe has enough dependencies that that's likely to happen. This is now a dependency of bigquery so I just wanted to make sure things don't get broken downstream.


Grunt newer messing up webfont and spritesmith tasks

Due to unknown problem with newer those tasks are not handling new files while prefixed with newer.
Waiting for a fix tschaub/grunt-newer/issues/45

Rejected since there is no chance newer will do any proper handling in this two cases.


Add support for javaOptions field

Adds the functionality that we had in 1.1 and which is documented in the wiki. It provides an alternative way to set the JAVA_OPTIONS environment variable.

I’ve been receiving mixed signals on this - can you close the related bug as ‘will not fix’?

On Dec 11, 2018, at 3:58 PM, Ryan Eberhard<EMAIL_ADDRESS>wrote:
@rjeberhard commented on this pull request.
In model/src/test/resources/oracle/kubernetes/weblogic/domain/v2/domain-sample-3.yaml https://github.com/oracle/weblogic-kubernetes-operator/pull/611#discussion_r240788170:

@@ -29,6 +31,9 @@ spec:
annotations:
time: midnight
serverPod:

 env:

Russ, I thought we had agreed that we would leave the javaOptions field out of the domain schema and just use env/JAVA_OPTIONS? It's simpler just to have one schema element.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub https://github.com/oracle/weblogic-kubernetes-operator/pull/611#discussion_r240788170, or mute the thread https://github.com/notifications/unsubscribe-auth/ACL7YJ2h35-6K6uw3YwSfBlecZb_LYueks5u4BxdgaJpZM4ZOCkG.


[external-storage] set aws key using vars

please, add the check in strato.sh if the aws keys are provided when the S3 bucket name is set


WIP: Refactor gateway chart

This makes a few changes to the gateway chart. These changes should have zero impact on Istioctl.

Stop setting .name by default (for helm only). If .Release.Name is set and .name is not, use that as the name
Rename istio-ingressgateway chart to gateway. This has minimal impact right now - just the output of helm ls is changed. It is backwards compatible for upgrade. This is useful for https://github.com/istio/release-builder/pull/757; then users can do helm install my-ingress istio/gateway instead of istio/istio-ingress.
Move all values from gateways.istio-ingressgateway.xyz to top level (xyz). To ensure backwards compatibility, we will merge gateways.istio-ingressgateway on top of (higher priority) the top level. This is also how istioctl will continue to work the same without changes. This allows users to do things like --set type=ClusterIP.

Example of use the new gateway chart to install an egressgateway:
helm template istio-egressgateway istio/gateway --set injectionTemplate=gateways --set labels.app=istio-egressgateway --set labels.istio=egressgateway --set type=ClusterIP

This is almost identical to existing egress gateway usage:

```diff
2c2
< # Source: istio-egress/templates/poddisruptionbudget.yaml
---
> # Source: gateway/templates/poddisruptionbudget.yaml
14c14
<     operator.istio.io/component: "EgressGateways"
---
>     operator.istio.io/component: "IngressGateways"
22c22
< # Source: istio-egress/templates/serviceaccount.yaml
---
> # Source: gateway/templates/serviceaccount.yaml
34c34
<     operator.istio.io/component: "EgressGateways"
---
>     operator.istio.io/component: "IngressGateways"
36c36
< # Source: istio-egress/templates/role.yaml
---
> # Source: gateway/templates/role.yaml
46c46
<     operator.istio.io/component: "EgressGateways"
---
>     operator.istio.io/component: "IngressGateways"
52c52
< # Source: istio-egress/templates/rolebindings.yaml
---
> # Source: gateway/templates/rolebindings.yaml
62c62
<     operator.istio.io/component: "EgressGateways"
---
>     operator.istio.io/component: "IngressGateways"
71c71
< # Source: istio-egress/templates/service.yaml
---
> # Source: gateway/templates/service.yaml
84c84
<     operator.istio.io/component: "EgressGateways"
---
>     operator.istio.io/component: "IngressGateways"
91a92,96
>       name: status-port
>       port: 15021
>       protocol: TCP
>       targetPort: 15021
>     -
102c107
< # Source: istio-egress/templates/injected-deployment.yaml
---
> # Source: gateway/templates/injected-deployment.yaml
114c119
<     operator.istio.io/component: "EgressGateways"
---
>     operator.istio.io/component: "IngressGateways"
130c135
<         operator.istio.io/component: "EgressGateways"
---
>         operator.istio.io/component: "IngressGateways"
133,135d137
<         prometheus.io/port: "15020"
<         prometheus.io/scrape: "true"
<         prometheus.io/path: "/stats/prometheus"
137a140,143
>         prometheus.io/path: /stats/prometheus
>         prometheus.io/port: "15020"
>         prometheus.io/scrape: "true"
>
148a155,156
>             - containerPort: 15021
>               protocol: TCP
173,174d180
<           - name: ISTIO_META_ROUTER_MODE
<             value: standard
176,177c182,183
<           - name: egressgateway-certs
<             mountPath: "/etc/istio/egressgateway-certs"
---
>           - name: ingressgateway-certs
>             mountPath: "/etc/istio/ingressgateway-certs"
179,180c185,186
<           - name: egressgateway-ca-certs
<             mountPath: "/etc/istio/egressgateway-ca-certs"
---
>           - name: ingressgateway-ca-certs
>             mountPath: "/etc/istio/ingressgateway-ca-certs"
183c189
<       - name: egressgateway-certs
---
>       - name: ingressgateway-certs
185c191
<           secretName: "istio-egressgateway-certs"
---
>           secretName: "istio-ingressgateway-certs"
187c193
<       - name: egressgateway-ca-certs
---
>       - name: ingressgateway-ca-certs
189c195
<           secretName: "istio-egressgateway-ca-certs"
---
>           secretName: "istio-ingressgateway-ca-certs"
225c231
< # Source: istio-egress/templates/autoscale.yaml
---
> # Source: gateway/templates/autoscale.yaml
237c243
<     operator.istio.io/component: "EgressGateways"
---
>     operator.istio.io/component: "IngressGateways"
</details>

Open questions:
* Can we make the labels automatically set based on name, while not breaking users?
* Can we enable injection automatically, while not breaking users?
* Can we handle the ingress-specific `istio-ingressgateway-ca-certs` secrets in some way? Can we just remove these at some point?

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@howardjohn: PR needs rebase.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Closing in favor of https://github.com/istio/istio/pull/34874


tf.contrib.seq2seq.sequence_loss documentation incorrect

The function returns a tensor with rank = 0, 1, 2 depending on its arguments. This is inconsistent with its docstring's description of the return:  https://github.com/tensorflow/tensorflow/blob/master/tensorflow/contrib/seq2seq/python/ops/loss.py#L58
I will submit a PR soon to fix the doc.
NOTE: Only file GitHub issues for bugs and feature requests.  All other topics will be closed.
For general support from the community, see StackOverflow.
To make bugs and feature requests more easy to find and organize, we close issues that are deemed
out of scope for GitHub Issues and point people to StackOverflow.
For bugs or installation issues, please provide the following information.
The more information you provide, the more easily we will be able to offer
help and advice.
What related GitHub issues or StackOverflow threads have you found by searching the web for your problem?
irrelevant
Environment info
Operating System:
irrelevant
Installed version of CUDA and cuDNN:
(please attach the output of ls -l /path/to/cuda/lib/libcud*):
If installed from binary pip package, provide:

A link to the pip package you installed:
The output from python -c "import tensorflow; print(tensorflow.__version__)".

If installed from source, provide

The commit hash (git rev-parse HEAD)
The output of bazel version

If possible, provide a minimal reproducible example (We usually don't have time to read hundreds of lines of your code)
What other attempted solutions have you tried?
Logs or other output that would be helpful
(If logs are large, please upload as attachment or provide link).

Thanks for the help. Please link the PR when you have submitted it.

This looks fixed in master, and it will roll out over time.  Thank you!  I'm closing this; please reopen if I've missed something.


Seemingly broken IsoSurface on MacOS

The isosurface renderer on macos seems broken, as the screenshot shows.
To reproduce:

Open VAPOR, load data /little_glade/shaomeng/cm1.nc (/glade/p/cisl/vast/vapor/Bugs/cm1.nc)
Create an isosurface renderer, change the isovalue to be 1.331, and enable this renderer.
The rendering result seems broken. It looks correct on cisl-vapor though.

Platform: macos+intel

This is some sort of driver bug. I'm at my wits end with these things. Here is what is happening:
int FindInitialCell(...)
{
    return 0; // Do nothing
    // Finds the initial cell
}

void main()
{
    // If I return here, the resulting image is correct
    intersections = FindInitialCell(...);
    // If I return here, the resulting image is corrupted
}

I have tried other datasets of higher resolution on my mac without this issue. It appears to be somehow localized to this dataset and only at the highest resolution.

It appears this happens when you run out of GPU RAM

An additional note relating to my original comment about the driver bug: In GLSL, if a variable is not used to compute the final result, it is optimized out. If the optimizer removes enough texture variables so that the data fits within RAM, there will be no glitches. For some reason, the optimizer is able to optimize out the textures if I return before calling the function FindInitialCell, but not if said function immediately returns 0.

We probably really shouldn't use OpenGL for renderers that are more
complicated than Contour Renderer...
On Fri, Jun 28, 2019 at 12:40 PM StasJ<EMAIL_ADDRESS>wrote:

An additional note relating to my original comment about the driver bug:
In GLSL, if a variable is not used to compute the final result, it is
optimized out. If the optimizer removes enough texture variables so that
the data fits within RAM, there will be no glitches. For some reason, the
optimizer is able to optimize out the textures if I return before calling
the function FindInitialCell, but not if said function immediately
returns 0.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/NCAR/VAPOR/issues/1627?email_source=notifications&email_token=AAGG6JKDHVGSKHOZOSP67EDP4ZLKDA5CNFSM4HT7ECPKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODY23XDY#issuecomment-506837903,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAGG6JN24FACXC3L7B7R43TP4ZLKDANCNFSM4HT7ECPA
.


Tests, setup certifi package to avoid SSL warnings

Please note that in the diff there are a lot more changes due to either mixed newline characters or extraneous white spaces in the original file

Thank you!


[ENHANCEMENT] Improve untriaged label workflow to ignore issues created by maintainers

Is your feature request related to a problem?
We use the untriaged workflow to add the untriaged label to all new issues, as described in https://github.com/opensearch-project/.github/issues/133
This is a good mechanism to ensure each repository has the right processes in place to routinely triage issues, where the label is manually removed. It also supports accountability, because we can simply check for untriaged issues that have had that label for some time.
But this does add unnecessary overhead to maintainers, who often create the majority of all issues in a repository, particularly when breaking down large epics or initiatives into subtasks. This can lean to temporary spikes in the untriaged metrics until the newly created issues are manually cleaned up.
What solution would you like?
By definition, a triaged issue is one which maintainers have deemed valid. So the untriaged workflow should simply skip any issues created by maintainers. I'm not sure of the best programmatic way to access the maintainer list from within the workflow, but suspect that the newly baselined CODEOWNERS files will help.
What alternatives have you considered?
None so far.
Do you have any additional context?
Related to https://github.com/opensearch-project/.github/issues/102

It would be amazing to turn the untriaged workflow into a proper GitHub app similar to DCO with features such as this one, so we don't have to configure a manual workflow in every repo.

This can lean to temporary spikes in the untriaged metrics until the newly created issues are manually cleaned up.

Sounds like you are trying to 'game' the graph, could you provide more detail on where is that graph is and how your team acts on it?
For the repos I maintain there are no graphs that we monitor; we use GitHub queries during our weekly triage [1].

Security Team Triage Agenda [1] https://github.com/opensearch-project/security/blob/main/TRIAGING.md#is-there-an-agenda-for-each-week

Opensearch Dashboards has solved this issue like this. https://github.com/opensearch-project/OpenSearch-Dashboards/pull/6193

We'd have to edit 100+ workflows :( It would be really great to have a bot that does this across the entire org.


[World-of-the-Storytellers-WoS] fix: try to fix rolltemplate css error

Changes / Comments
I'm trying to fix the error that rolltemplate styling isn't work...
change media query
change some classes in css file
I hope to solve the problem this time.
Roll20 Requests
Comments are very helpful for reviewing the code changes. Please answer the relevant questions below in your comment.

[ ] Does the pull request title have the sheet name(s)? Include each sheet name.
[ ] Is this a bug fix?
[ ] Does this add functional enhancements (new features or extending existing features) ?
[ ] Does this add or change functional aesthetics (such as layout or color scheme) ?
[ ] If changing or removing attributes, what steps have you taken, if any, to preserve player data ?
[ ] If this is a new sheet, did you follow Building Character Sheets standards ?

If you do not know English. Please leave a comment in your native language.

Character Sheet Info Roll20 Internal Use only.


KeyError when trying to use wordpress_json

Using:

Python 3.5
Wordpress 4.6
wordpress_json 0.2.2
Json Basic Authentication 0.1
WP REST API 2.0-beta13.1
WP REST API - Meta Endpoints 0.1.0

I tried a simple example similar to what is provided in the README:
url = 'http://minilogbook.com/wp-json'
user = 'minorsecond'
password = '*********'

wp = WordpressJsonWrapper(url, user, password)

posts = wp.get_posts()

and I get:
Traceback (most recent call last):
  File "/Users/rwardrup/DEV/miniLogbook/bin/slm.py", line 20, in <module>
    posts = wp.get_posts()
  File "/Users/rwardrup/miniconda3/envs/miniLogbook/lib/python3.4/site-packages/wordpress_json/__init__.py", line 69, in api_method
    return self._request(method_name, **kw)
  File "/Users/rwardrup/miniconda3/envs/miniLogbook/lib/python3.4/site-packages/wordpress_json/__init__.py", line 267, in _request
    '[%s] %s' % (http_response.json()[0].get('code'),
KeyError: 0

I am having the same error.  Any idea when this started happening so I might kick it back a commit or too?

I'm not sure. I only began experimenting with it yesterday. Let me know how I can help though.

The traceback you get is a legitimate bug in the code that handles HTTP errors. I have a pull-request(https://github.com/stylight/python-wordpress-json/pull/3) up to fix that.
The error thrown is most likely a
404 Not Found :  [rest_no_route] No route was found matching the URL and request method

This is because wordpress apparently changed the API endpoints for v2. Try the following instead and it should work, even with the current bug.
url = 'http://minilogbook.com/wp-json/wp/v2'

I've also created a PR to fix the README(https://github.com/stylight/python-wordpress-json/pull/4).

Thanks, @droustchev
There seems to be another issue, though I'm not sure if it's on my end: 400 bad request. I peered into the code and, if I put a print statement in line 262, it seems I am getting a response. If someone else can replicate this, I'll create another issue.
http_response = requests.request(
            method,
            self.site + endpoint,
            auth=self.auth,
            params=params,
            json=data,
            headers=headers
        )

        print(http_response.content)

Traceback (most recent call last):
  File "/Users/rwardrup/DEV/miniLogbook/bin/slm.py", line 17, in <module>
    posts = wp.get_posts()
  File "/Users/rwardrup/miniconda3/envs/miniLogbook/lib/python3.4/site-packages/wordpress_json/__init__.py", line 69, in api_method
    return self._request(method_name, **kw)
  File "/Users/rwardrup/miniconda3/envs/miniLogbook/lib/python3.4/site-packages/wordpress_json/__init__.py", line 270, in _request
    http_response.json()[0].get('message'))
wordpress_json.WordpressError: 400 Bad Request :  [None] None

b'[{"id":1,"date":"2016-08-14T21:28:27","date_gmt":"2016-08-14T21:28:27","guid":{"rendered":"http:\\/\\/minilogbook.com\\/?p=1"},"modified":"2016-08-14T21:28:27","modified_gmt":"2016-08-14T21:28:27","slug":"hello-world","type":"post","link":"http:\\/\\/minilogbook.com\\/hello-world\\/","title":{"rendered":"Hello world!"},"content":{"rendered":"
Welcome to WordPress. This is your first post. Edit or delete it, then start writing!<\\/p>\\n"},"excerpt":{"rendered":"
Welcome to WordPress. This is your first post. Edit or delete it, then start writing!<\\/p>\\n"},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"format":"standard","categories":[1],"tags":[],"_links":{"self":[{"href":"http:\\/\\/minilogbook.com\\/wp-json\\/wp\\/v2\\/posts\\/1"}],"collection":[{"href":"http:\\/\\/minilogbook.com\\/wp-json\\/wp\\/v2\\/posts"}],"about":[{"href":"http:\\/\\/minilogbook.com\\/wp-json\\/wp\\/v2\\/types\\/post"}],"author":[{"embeddable":true,"href":"http:\\/\\/minilogbook.com\\/wp-json\\/wp\\/v2\\/users\\/1"}],"replies":[{"embeddable":true,"href":"http:\\/\\/minilogbook.com\\/wp-json\\/wp\\/v2\\/comments?post=1"}],"version-history":[{"href":"http:\\/\\/minilogbook.com\\/wp-json\\/wp\\/v2\\/posts\\/1\\/revisions"}],"wp:attachment":[{"href":"http:\\/\\/minilogbook.com\\/wp-json\\/wp\\/v2\\/media?parent=1"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\\/\\/minilogbook.com\\/wp-json\\/wp\\/v2\\/categories?post=1"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\\/\\/minilogbook.com\\/wp-json\\/wp\\/v2\\/tags?post=1"}],"curies":[{"name":"wp","href":"https:\\/\\/api.w.org\\/{rel}","templated":true}]}}]'

@minorsecond It seems your server may not be sending back a response containing a code and message. On mine I get something like this back for 404:
{"code":"rest_no_route","message":"No route was found matching the URL and request method","data":{"status":404}}
This results in an exception being raised like this:
wordpress_json.WordpressError: 404 Not Found : [rest_no_route] No route was found matching the URL and request method

Version 0.2.3 has been released to fix this issue: https://pypi.python.org/pypi/wordpress_json/0.2.3
Thanks for reporting it and for the fix @droustchev


@denniscareers Twitter account deleted

Find alternate/preferred Dennis twitter account

It's been renamed to @lifeatdennis

fixed in 35d6008


Feature - Suggestion: Logo

I mean, like 65-80% of language have those, so... why not?
But no pressure

A logo? I already have one :) Its on the website

oh. so what about on the readme?

oh well, a background gotta go to waste, then


Add functionality to advance the model stepwise

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-1.6%) to 96.637%

Totals

Change from base Build<PHONE_NUMBER>:
-1.6%

Covered Lines:
546

Relevant Lines:
565

💛  - Coveralls


Synchronize access MERGEOK

I'm removing the need for this, but keep it thread safe for now.
@baldersheim or @lesters

I think it would be sufficient to just just a ConcurrentHashHap similar to what is done in LargeRankExpressions.

I needed it sorted for consistent config generation and added a method that returned a sorted list     public Collection expressions() {
return expressions.values().stream().sorted().collect(Collectors.toUnmodifiableList());
}


OSSL_CMP_validate_msg(): make sure to reject protection type mismatch

Do not accept password-based protection if signature-based is expected and no secret is available and
do not accept signature-based protection if password-based is expected and no trust anchors available.
Checklist

[x] documentation is added or updated
[x] tests are added or updated

@DDvO the use of FUZZING_BUILD_MODE_UNSAFE_FOR_PRODUCTION in CMP code seems fairly weird to me. Is it mostly code that should use ossl_assert() instead?

@DDvO the use of FUZZING_BUILD_MODE_UNSAFE_FOR_PRODUCTION in CMP code seems fairly weird to me. Is it mostly code that should use ossl_assert() instead?

The point of using FUZZING_BUILD_MODE_UNSAFE_FOR_PRODUCTION in crypto/cmp/cmp_vfy.c is to disable various checks on CMP messages received in order to enable more aggressive fuzzing.
This demonstrates that even with those checks not present, which emulates bad messages being received and not rejected, the remaining code does not crash.
See also #11386.
Consequently, most of the 'negative' tests in cmp_vfy_test.c must be disabled with FUZZING_BUILD_MODE_UNSAFE_FOR_PRODUCTION because they would fail due to the disabled message validation checks.

Asking @openssl/committers for 2nd review.

This pull request is ready to merge

Argh, I just noticed that cherry-picking the fix to 3.0 causes a build error because meanwhile the function OSSL_CMP_CTX_set0_trustedStore  had been renamed to OSSL_CMP_CTX_set0_trusted on the master.
How to cure this? The change needed is
diff --git a/test/cmp_vfy_test.c b/test/cmp_vfy_test.c
index 23117760d1..ed8e1b3143 100644
--- a/test/cmp_vfy_test.c
+++ b/test/cmp_vfy_test.c
@@ -153,7 +153,7 @@ static int test_validate_msg_mac_alg_protection(int miss, int wrong)
     SETUP_TEST_FIXTURE(CMP_VFY_TEST_FIXTURE, set_up);

     fixture->expected = !miss && !wrong;
-    if (!TEST_true(miss ? OSSL_CMP_CTX_set0_trusted(fixture->cmp_ctx, NULL)
+    if (!TEST_true(miss ? OSSL_CMP_CTX_set0_trustedStore(fixture->cmp_ctx, NULL)
                    : OSSL_CMP_CTX_set1_secretValue(fixture->cmp_ctx, sec_1,
                                                    wrong ? 4 : sizeof(sec_1)))
             || !TEST_ptr(fixture->msg = load_pkimsg(ip_waiting_f, libctx))) {

Shall I push a fixup commit on openssl-3.0 or can I even amend and force-push it there
or is the only option to have an urgent fixup PR for 3.0? I tentatively opened it in #19859.


Reduced logging

Consolidates router IP reporting to the xDrip load line
Only log first attempt unless data is available

Still seeing duplicates:
Starting oref0-ns-loop at Sun Oct 27 13:33:02 PDT 2019:
Connected to <IP_ADDRESS>, testing for xDrip API availability
Load from local xDrip timed out, likely not connected to xDrip hotspot
Got CGM results from Nightscout
Connected to <IP_ADDRESS>, testing for xDrip API availability
Load from local xDrip timed out, likely not connected to xDrip hotspot
Got CGM results from Nightscout
Found recent valid BG:

Is the script being invoked multiple times?


DEVITO_LOGGING doesn't seem to be respected

The log level in master is set to WARNING but Travis logs still show log messages that shouldn't show up at that level.

This is traced to test_autotuner.py. This is an example but this is done in multiple tests in this file. Fix coming soon.

great

Looks like the AT tests are forcing a temporary drop in debug level and re-instating the default instead of the previous log-level:
https://github.com/opesci/devito/blob/master/tests/test_autotuner.py#L36
If only we had a utility to do that in a more pythonic way :snake: ... something like the decorator in #429, maybe? :wink:

I also note in passing that the logger interjection in those tests looks quite horrific, IMHO. Can we think of a better way to test the AT behaviour without relying on log string?

I'm not sure how to, I'm checking that the Operator is actually invoked as many times as expected, and the output data isn't available after AT execution, so... I'm all ears for suggestions! Perhaps I'm missing some obvious way?

and the output data isn't available after AT execution

Well, I guess if the AT is truly stateless, that's as far as we can go... :frowning: Anyway, not the source of the problem, just visually annoying.

Fixed by #442 . Closing.


Can't manage 2nd implemente - weapon

I'm adding a second implement - weapon but when I try to manage and add any weapon in the inventory, this is no saved. I'm getting this error in console:
Uncaught (in promise) TypeError: impl is null
[Detected 1 package: pf2e-thaum-vuln]
    deleteImpEffect helpers.js:25

Pf2e 5.1.2
Foundry 11 (305)

Try this:

Press f12
Select the thaumaturge token
in the console window, type _token.actor.unsetFlag("pf2e-thaum-vuln","selectedImplements")

You will need to re-add your first implement again. Let me know if that helps. If not, please let me know what weapon you're trying to apply, if you've altered it at all, if it's in the compendium or in the items tab, etc. Just as much information as possible.

that helped, thank you!


Root route remains always active

I noticed that active is being applied always to the root route regardless the current active location. I wrote a few tests to verify since I am not completely familiar with this project.
Let me know If you would like to investigate and try to fix the issue.
Thank you for this project :)

Just like with a <Route>, you need to use the exact prop (<NavLink exact to='/'>...</NavLink>) if you don't want / to match every location. The <NavLink> actually uses a <Route> internally to determine whether or not it matches, so you can use any of the <Route> path configuration props (exact, strict, and sensitive) in a <NavLink>.

Ok, a friend suggested me exact. Got it! Thanks.

@pshrmn thank you! :)


Released version 1.3 cannot be used from Python 3

The released version 1.3 from PyPI fails with TabError: inconsistent use of tabs and spaces in indentation. As the issue seems to be fixed in master, I would suggest to perform a new release. The issue can e.g. be seen in https://travis-ci.org/blue-yonder/devpi-builder/jobs/32638794.

The bug report is quite old, but I have to agree: a new version would be nice. I'm currently facing the exact same trivial issue.

Can you please check against v1.5 and let me know if this is still an issue? Apologies on the delay here.

v1.4 worked fine with py3k, so I guess this can be closed

Sorry, this fell of my stack. Latest release (1.6) works great on Python 3.


Logfile

Please follow the guide below

You will be asked some questions and requested to provide some information, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your issue (like that [x])
Use Preview tab to see how your issue will actually look like

WARNING
All the invalid issues will be rejected!!

Before going further

If your problem is a bug with the youtube-dl program or a request for new site support please report it here

Make sure you are using the latest youtube-dl-gui version: Options > About tab. If it's not please download & install the latest version for your OS and check if your issue still persists

Make sure you are using the latest youtube-dl version: Click the Update button on the main screen and check if your issue still persists

Make sure you searched the bugtracker for similar issues including closed ones

[x] I assure that my problem is NOT with youtube-dl
[x] I've verified and I assure that I'm running youtube-dl-gui 0.3.8
[x] I assure that i am using the latest version of youtube-dl
[x] Searched bugtracker

What is the purpose of your issue?

[ ] Bug during the download process (encountered problems after hitting the Download button)
[ ] Bug other (encountered other problems with youtube-dl-gui)
[ ] Feature request (request for a new functionality)
[x] Question
[ ] Other

Description of your issue, suggested solution and other information. Please make sure the description is worded well enough to be understood.
Why are my logfile always empty when I open it. Sometimes I get problem and need the logfile to send to the people ho can fix it on youtube dl. The checkbox enable logfiel are checked its that not enough?

Why are my logfile always empty when I open it. Sometimes I get problem and need the logfile to send to the people ho can fix it on youtube dl. The box enable logfiel are checked its that not enough?

Hi,
By default, only the Error & Warning messages are being recorded.
If you want to log the youtube-dl Debug output you need to pass the -v option under Options>Commands.

Hi
Thanks for answer maybe this option can get implemented in the new gui?

If you mean logging the debug output by default, no since this will make the logfile hard to read. If you mean adding it as an option (checkbox, etc..), yes it's already in the TODO list.

You know exactly what i mean i really like that. I look forward to the new gui are you going to release it soon maybe? i am very hopeful about that because i often use Youtube dlg its very good probably the best program a have seen.
Thanks for good answer.

I'm definitely not good with deadlines. I want to believe that the new ui will be available until the end of this year. Those are the issues that we have to take care before merging back to master and making a new release.

Hi
I have some suggestions for the new gui i write them here.
Add Swedish language so its possible to choose Swedish language and embed into file when downloading.
An option to see which version of Youtube dl which are in use or maybe get an notification when a new version of Youtube dl are released.
Possible to download a hole tv serie with lot of episodes so you dont need to copy and paste each link.
Maybe someone else had write this i dont know.
Now i wait for the new gui and i will have patience.

Your first two suggestions are already in my TODO list.
The last one seems like a youtube-dl issue. Maybe there is a way already, i guess this is relative to the youtube-dl extractor being used.

Hi
I dont know what you mean abot wich Youtube dl ectractor being used to download a tv serie at time.

youtube-dl has a list of extractors which are responsible for extracting informations about the requested url.
What i meant in my previous comment was that if the corresponding extractor supports series extraction, you should be able to download all the episodes from a tv serie at once, else you should add support to the corresponding extractor.

Were can i find information about this if i want to do that. I look on the link above you have in your comment and there are svt but i dont know how i should do to to try to download a list of episodes at once. Should i make a request to Youtube dl or what?

You could try to implement it yourself. Check those for help:

https://github.com/rg3/youtube-dl#developer-instructions
irc channel #youtube-dl webchat on freenode (to talk to someone, maybe they could guide you)

Or make a new issue and ask the developers to add support (if it's possible).

Thanks for your time but i are not so good to make this i cant anything about programming. Maybe i make an issue and hope they can implement it.
Thanks for answer and a good program which i use very often.


[HUDI-7013] Drop table command cannot delete dir even when purge is enable

Change Logs
In some case even when purge is set true, truncate or drop but dir cannot be deleted
Impact
delete dir with recursive
Risk level (write none, low medium or high below)
If medium or high, explain what verification was done to mitigate the risks.
Documentation Update
Describe any necessary documentation update if there is any new feature, config, or user-facing change

The config description must be updated if new configs are added or the default value of the configs are changed
Any new feature or user-facing change requires updating the Hudi website. Please create a Jira ticket, attach the
ticket number here and follow the instruction to make
changes to the website.

Contributor's checklist

[ ] Read through contributor's guide
[ ] Change Logs and Impact were stated clearly
[ ] Adequate tests were added if applicable
[ ] CI passed

    // Recursively delete table directories     if (purge) {       logInfo("Clean up " + basePath)       val targetPath = new Path(basePath)       val engineContext = new HoodieSparkEngineContext(sparkSession.sparkContext)       val fs = FSUtils.getFs(basePath, sparkSession.sparkContext.hadoopConfiguration)       FSUtils.deleteDir(engineContext, fs, targetPath, sparkSession.sparkContext.defaultParallelism)     }
but :
public static boolean deleteDir(       HoodieEngineContext hoodieEngineContext, FileSystem fs, Path dirPath, int parallelism) {     try {       if (fs.exists(dirPath)) {         FSUtils.parallelizeSubPathProcess(hoodieEngineContext, fs, dirPath, parallelism, e -> true,             pairOfSubPathAndConf -> deleteSubPath(                 pairOfSubPathAndConf.getKey(), pairOfSubPathAndConf.getValue(), true)         );         boolean result = fs.delete(dirPath, false);         LOG.info("Removed directory at " + dirPath);         return result;       }     } catch (IOException ioe) {       throw new HoodieIOException(ioe.getMessage(), ioe);     }     return false;   }
boolean result = fs.delete(dirPath, false);  this cause dir cannot be delete

@danny0405

@hudi-bot run azure

@hudi-bot run azure

@hudi-bot run azure

@hudi-bot run azure

azure seems had some problem，would be cancel soon after run


fix: Attempt to fix issue with item assignment

About
This pull request attempts to fixes this bug
Checklist

[x] I've ran pre-commit to format and lint the change(s) made.
[ ] I've checked to make sure the change(s) work on 3.8.6 and higher.
[ ] This fixes/solves an Issue.

(If existent):

[ ] I've made this pull request for/as: (check all that apply)

[ ] Documentation
[ ] Breaking change
[ ] New feature/enhancement
[x] Bugfix

Have you tested it?

The issue seems to occur randomly so I can't really test it/we don't know when it occurs

@Damego merge or no merge?

Now this
Traceback (most recent call last):
  File "C:\Users\User\OneDrive\python\discord bots\mangalib-bot\source\main.py", line 23, in <module>
    client.start()
  File "C:\Users\User\AppData\Local\Programs\Python\Python310\lib\site-packages\interactions\client\bot.py", line 134, in start
    raise e from e
  File "C:\Users\User\AppData\Local\Programs\Python\Python310\lib\site-packages\interactions\client\bot.py", line 132, in start
    self._loop.run_until_complete(self._ready())
  File "C:\Users\User\AppData\Local\Programs\Python\Python310\Lib\asyncio\base_events.py", line 646, in run_until_complete
    return future.result()
  File "C:\Users\User\AppData\Local\Programs\Python\Python310\lib\site-packages\interactions\client\bot.py", line 391, in _ready
    await self._login()
  File "C:\Users\User\AppData\Local\Programs\Python\Python310\lib\site-packages\interactions\client\bot.py", line 396, in _login
    await self._websocket._establish_connection(self._shards, self._presence)
  File "C:\Users\User\AppData\Local\Programs\Python\Python310\lib\site-packages\interactions\api\gateway\client.py", line 196, in _establish_connection
    await self._handle_connection(stream, shard, presence)
  File "C:\Users\User\AppData\Local\Programs\Python\Python310\lib\site-packages\interactions\api\gateway\client.py", line 264, in _handle_connection
    self._dispatch_event(event, data)
  File "C:\Users\User\AppData\Local\Programs\Python\Python310\lib\site-packages\interactions\api\gateway\client.py", line 414, in _dispatch_event
    before = model(**old_obj._json)
  File "C:\Users\User\AppData\Local\Programs\Python\Python310\lib\site-packages\interactions\api\models\attrs_utils.py", line 120, in __init__
    super().__init__(**kwargs)
  File "C:\Users\User\AppData\Local\Programs\Python\Python310\lib\site-packages\interactions\api\models\attrs_utils.py", line 80, in __init__
    self.__attrs_init__(**passed_kwargs)  # type: ignore
  File "<attrs generated init interactions.api.models.message.Message>", line 8, in __attrs_init__
  File "C:\Users\User\AppData\Local\Programs\Python\Python310\lib\site-packages\attr\converters.py", line 43, in optional_converter
    return converter(val)
TypeError: fromisoformat: argument must be str

@EdVraz


Minimal UI module makes the Easy Timekeeping UI shrink

Fixed since release v1.2.0
While the docked UI does not respond to Minimal UI "minimalism" in the way that default UI elements like the Players panel does, it is no longer impacted by them. If you want a minimal experience, use the Show/Hide UI hotkey, or set the unfocused fade value to fade the Easy Timekeeping UI into the background when it's not in use.


Update Dockerfile

Description
Fixes https://github.com/gruntwork-io/terragrunt-action/issues/39
Release Notes (draft)

Added / Removed / Updated [X].
Migration Guide
N/A

@denis256 Could you take a look?

Hi,
I think this approach will basically revert changes to not run terragrunt as root


Some functionality like get_all

I am really wanting to use aiocache with fastapi, but my caching problem centers around a pattern where many values are kept, then all processed simultaneously. Is there any way to get all the values in a cache as a useful iterable datastructure before using something clear() to empty the cache?

Sounds useful for debugging

Hey @csajedi not all caches implement a function to return all keys that are currently stored. For your use case, you should keep somewhere the list of keys you want to interact with and then you can use multi_get to retrieve all those values at the same time.


How to change theme from default minima to this?

Hello, I'm a newbie of jekyll blog system. I created blog folder by:
cd ~
jekyll new myBlog
bundle install
bundle exec jekyll serve
So I can preview the website at <IP_ADDRESS>:4000
However, when I try to change the default minima theme by following the readme.md. I met errors when running jekyll serve command.
In detail, I did the operations below:

edit the _config.yml by adding the lines below:

remote_theme<EMAIL_ADDRESS>- jekyll-remote-theme # add this line to the plugins list, cuz I already have one

change the theme config in _config.yml as:

theme: minimal

add the gem line in Gemfile:

gem "github-pages", group: :jekyll_plugins

Run the bundle install at the path of ~/myBlog
This step may meet error about version confilict.
I fix these errors by removing some version words in Gemfile

Run the bundle exec jekyll serve
I meet different types of errors.

Is there any standard steps about changing the jekyll theme for newbie?
Thank you very much and I spent one whole day for changing theme for jekyll! I feel very frustrated now :(

@sonictl Did you ever resolve this issue? I am running into the same problems so it would be helpful if you could share your solution!


Improv tracer - async support, patch, test coverage and X-Ray escape hatch

Issue #, if available: #28, #11, #10
Description of changes:

[x] Accept list of modules to be patched
[x] Update tests
[x] Test cold start annotation behaviour
[x] Create subsegment entity/type (put_annotation, etc.)
[x] Implement thread safe current_subsegment -> subsegment
[x] Update decorators to use own subsegment to prevent race conditions
[x] Support async
[x] Support aiohttp
[x] Expose escape hatch mechanism for X-Ray
[x] Update docs on async, patch modules, and escape hatch
[x] Update example
[x] Update example tests
[ ] Bump version

UX for async
Customer needs to control the loop and await all coroutines
@tracer.capture_method      # will prime this coroutine
async def greeting_2(name, message):
    return dummy_response

@tracer.capture_method      # will prime this coroutine
async def greeting(name, message):
    blah = await greeting_2(name, message)
    return dummy_response, blah

def lambda_handler(evt, ctx):
    loop = asyncio.get_event_loop()
    loop.run_until_complete(greeting(name="Foo", message="Bar"))
   # or gather() if multiple need to be awaited

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Overall, it looks good but I have questions regarding whether the tracer implementation is not too specific to X-Ray.

I dropped additional provider feature. Instead, this PR now tackles enhancements for Tracer - Async support, patch specific modules, and an escape hatch mechanism

Thank you once again @nmoutschen for the review :) It's now published in 0.9.0


Fix: Added a max retry limit on the docker helper pull

Fixes: https://github.com/coollabsio/coolify/issues/3395
-> As I can not reproduce the issue this is an attempted fix to fix the rate limit issue a lot of people are having.
Duplicates (issues that turned into the one linked)

https://github.com/coollabsio/coolify/issues/2930
https://github.com/coollabsio/coolify/issues/3355

The backup process changed, so this is not needed, but thanks for the PR!


improving the data for the digest emails

Comment by @rishig on #11761 below.

I'll copy out a summary of my thoughts from before. This was in the context of specifically coming up with a machine learning way to do this, but I think the basic idea or looking through a bunch of messages and getting some intuition from that holds whether or not we do it with ML.
I've posted thoughts on a next step at https://chat.zulip.org/#narrow/stream/127-integrations/topic/Custom.20weekly.20digest/near/720550.
* Each email should include 3-6 messages from the last week's worth of messages on streams that the user is subscribed to. (We can deal with PMs in a V2, since by default we sending a missed message email for PMs already.) The goal is to pick 3-6 messages that maximize the chance the user clicks through into the zulip realm.

To keep this sane (and shipable), the way I would do the V1 is:
* Restrict to picking messages that are the first message of their topics.

* For each such message, compute a user-independent "interestingness" score (more below)

* For each stream, compute the 3 messages with the highest interestingness score

* For each user, pick the 6 messages that have the highest interestingness score, among the streams they are subbed to (as a followup maybe throw out mentions, or more generally anything else they would have gotten an email about).

For the interestingness step, I would
* From czo and maybe other realms you're a part of, copy out the first messages from every topic, for every public stream you're a part of (we can discuss in PMs how to handle access to czo data)

* By hand, label a few hundred messages with good/bad, or with a sliding scale, of how interesting they are (this shouldn't take too long; I think I could do it myself in a few hours).

* Come up with a list of easy to compute features, like "length of message", "has images", "account age of person sending the message", "number of messages in thread", "number of messages in thread that have a lot of words", "number of emoji reactions", "has topic", "is default stream", "is private stream", etc. and see which ones seem to correlate.

After doing the by-hand labelling, you may already have a pretty good intuition for what features matter. If not, we can do a basic regression to figure out which 2-3 features seem the most predictive and give scores based on that.

Comment by @timabbott below:

I think once this bit of tooling is done, we might want to talk about making the gather_hot_conversations algorithm better. E.g. number of emoji reactions would be a good factor for it to consider. The current algorithm is pretty naive: Basically get some conversations with a lot of messages and a lot of senders. I think we'd probably be better off having a scoring function for a conversation that has more of this sort of structure:
* +3 points per message in the thread (we don't want to over-weight this, because long effectively 1:1 support threads take over otherwise)

* +20 points per distinct sender

* +10 points per emoji reaction on messages in the thread

* +30 points if it's in one of your pinned streams.

* -50 points if the current user is mentioned (they already got an email)

* Etc.

(I gave very little thought to the actual numbers there; I just think conceptually we want this sort of structure for doing the selection that's based on scoring and picking the conversation(s) with the best score, rather than adding together lists from a couple mediocre algorithms).