Formatted codebase using autopep8

I used autopep8 to auto-format all the Python code to conform to the PEP 8 style guide.

Hello @AndrewHocking! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file website/forms/event_filter.py:

Line 22:80: E501 line too long (91 > 79 characters)
Line 78:80: E501 line too long (82 > 79 characters)

In the file website/forms/events.py:

Line 46:80: E501 line too long (202 > 79 characters)
Line 52:80: E501 line too long (114 > 79 characters)
Line 59:80: E501 line too long (82 > 79 characters)
Line 65:80: E501 line too long (106 > 79 characters)
Line 71:80: E501 line too long (96 > 79 characters)
Line 77:80: E501 line too long (117 > 79 characters)
Line 78:80: E501 line too long (113 > 79 characters)
Line 85:80: E501 line too long (132 > 79 characters)
Line 86:80: E501 line too long (130 > 79 characters)
Line 92:80: E501 line too long (233 > 79 characters)

In the file website/forms/people_filter.py:

Line 63:80: E501 line too long (82 > 79 characters)

In the file website/models/event/event.py:

Line 20:80: E501 line too long (81 > 79 characters)
Line 31:80: E501 line too long (85 > 79 characters)
Line 32:80: E501 line too long (83 > 79 characters)

In the file website/models/user/user.py:

Line 83:80: E501 line too long (107 > 79 characters)

In the file website/orm/event/event.py:

Line 62:40: E111 indentation is not a multiple of four
Line 62:40: E113 unexpected indentation
Line 62:73: E228 missing whitespace around modulo operator
Line 62:80: E501 line too long (88 > 79 characters)
Line 62:83: E225 missing whitespace around operator
Line 62:84: E231 missing whitespace after ':'
Line 62:85: E228 missing whitespace around modulo operator
Line 63:9: E122 continuation line missing indentation or outdented
Line 63:17: E251 unexpected spaces around keyword / parameter equals
Line 63:19: E251 unexpected spaces around keyword / parameter equals
Line 64:38: E128 continuation line under-indented for visual indent
Line 64:69: E228 missing whitespace around modulo operator
Line 64:79: E225 missing whitespace around operator
Line 64:80: E231 missing whitespace after ':'
Line 64:80: E501 line too long (84 > 79 characters)
Line 64:81: E228 missing whitespace around modulo operator
Line 65:9: E122 continuation line missing indentation or outdented
Line 65:80: E501 line too long (119 > 79 characters)
Line 66:13: E128 continuation line under-indented for visual indent
Line 66:80: E501 line too long (137 > 79 characters)
Line 92:1: E122 continuation line missing indentation or outdented
Line 94:9: E128 continuation line under-indented for visual indent
Line 97:48: E712 comparison to False should be 'if cond is False:' or 'if not cond:'
Line 106:28: E251 unexpected spaces around keyword / parameter equals
Line 106:30: E251 unexpected spaces around keyword / parameter equals
Line 110:28: E251 unexpected spaces around keyword / parameter equals
Line 110:30: E251 unexpected spaces around keyword / parameter equals
Line 115:24: E251 unexpected spaces around keyword / parameter equals
Line 115:26: E251 unexpected spaces around keyword / parameter equals
Line 116:13: E128 continuation line under-indented for visual indent
Line 118:24: E251 unexpected spaces around keyword / parameter equals
Line 118:26: E251 unexpected spaces around keyword / parameter equals
Line 119:13: E128 continuation line under-indented for visual indent
Line 121:24: E251 unexpected spaces around keyword / parameter equals
Line 121:26: E251 unexpected spaces around keyword / parameter equals
Line 122:13: E128 continuation line under-indented for visual indent
Line 124:24: E251 unexpected spaces around keyword / parameter equals
Line 124:26: E251 unexpected spaces around keyword / parameter equals
Line 125:13: E128 continuation line under-indented for visual indent

In the file website/orm/user/notifications.py:

Line 54:80: E501 line too long (101 > 79 characters)

In the file website/orm/user/user.py:

Line 70:80: E501 line too long (116 > 79 characters)
Line 74:20: E711 comparison to None should be 'if cond is not None:'

In the file website/routes/api/user.py:

Line 13:80: E501 line too long (183 > 79 characters)

In the file website/routes/ui/debug.py:

Line 518:80: E501 line too long (83 > 79 characters)
Line 519:80: E501 line too long (89 > 79 characters)

In the file website/routes/ui/events.py:

Line 54:80: E501 line too long (86 > 79 characters)
Line 59:80: E501 line too long (84 > 79 characters)
Line 118:80: E501 line too long (102 > 79 characters)
Line 119:80: E501 line too long (95 > 79 characters)
Line 168:80: E501 line too long (80 > 79 characters)

In the file website/routes/ui/people.py:

Line 4:80: E501 line too long (96 > 79 characters)
Line 27:80: E501 line too long (89 > 79 characters)
Line 74:80: E501 line too long (81 > 79 characters)


gnuradio-companion <IP_ADDRESS> crash on open on windows

Issue:
gnuradio-companion <IP_ADDRESS> crash on open on windows. Version 3.8.1 works fine.
(base) PS F:\apps\Conda> gnuradio-companion.exe
No such schema ?org.gnome.desktop.interface?
Traceback (most recent call last):
File "F:\apps\Conda\lib\runpy.py", line 193, in run_module_as_main
"main", mod_spec)
File "F:\apps\Conda\lib\runpy.py", line 85, in run_code
exec(code, run_globals)
File "F:\apps\Conda\Library\bin\gnuradio-companion.exe_main.py", line 102, in
File "F:\apps\Conda\Library\bin\gnuradio-companion.exe_main.py", line 95, in run_main
File "F:\apps\Conda\lib\site-packages\gnuradio\grc\main.py", line 73, in main
from .gui.Platform import Platform
File "F:\apps\Conda\lib\site-packages\gnuradio\grc\gui\Platform.py", line 26, in
from . import canvas
File "F:\apps\Conda\lib\site-packages\gnuradio\grc\gui\canvas_init_.py", line 21, in
from .param import Param
File "F:\apps\Conda\lib\site-packages\gnuradio\grc\gui\canvas\param.py", line 23, in
from .. import ParamWidgets, Utils, Constants
File "F:\apps\Conda\lib\site-packages\gnuradio\grc\gui\ParamWidgets.py", line 66, in
add_style_provider()
File "F:\apps\Conda\lib\site-packages\gnuradio\grc\gui\ParamWidgets.py", line 58, in add_style_provider
dark_theme = have_dark_theme()
File "F:\apps\Conda\lib\site-packages\gnuradio\grc\gui\ParamWidgets.py", line 49, in have_dark_theme
["gsettings", "get", "org.gnome.desktop.interface", "gtk-theme"]
File "F:\apps\Conda\lib\subprocess.py", line 411, in check_output
**kwargs).stdout
File "F:\apps\Conda\lib\subprocess.py", line 512, in run
output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['gsettings', 'get', 'org.gnome.desktop.interface', 'gtk-theme']' returned non-zero exit status 1.

Environment (conda list):

$ conda list

Details about  conda and system ( conda info ):

$ conda info

I can confirm that I see also see this in a Windows VM, and that <IP_ADDRESS> is not affected even with the same GTK, etc. installed. I'll do a little more digging to see if I can figure out what's happening.

Looks like an uncaught exception bug in <IP_ADDRESS> that mostly affects Windows and macOS. There's already an upstream fix: https://github.com/gnuradio/gnuradio/pull/3727. I'll pull that patch and make a new conda-forge build for <IP_ADDRESS>. Stand by.

Thanks for the report, @denis-sp! The PR should auto-merge once the build finishes in a couple hours, and then the packages will be up on the conda-forge repo a short while later.

I will test it once it's online.

It works fine. Though conda treat the previous build as latest.


Dynamic Navbar & Tabbar : title of the 1st page disappears

Hello !
I'm trying (with a lot of difficulties :'( ) to create a basic "tabbed" app.
The app has 2 principal tabs, and in each of them, you can go deeper and deeper in pages.
My issue : I finally succeeded in the task, except for one thing; if I want to use dynamic navigation, the navbar of the first page appears empty! If I remove the "dynamic-navbar", everything works well (except of course I do not have anymore the "dynamic" effect).
I do not know if it is related, but I also failed to implement the tab routing. So my "working" version is no as clean as I would have liked. But considering issue #238, perhaps it's the framework who fails at this task?
Thanks in advance if you can help me! :)
App.vue
<template>

    <f7-panel right reveal layout="dark">
      <f7-view>
        <f7-navbar title="Menu" />
      </f7-view>
    </f7-panel>

    <f7-views tabs navbar-through toolbar-through>

      <f7-view tab id="timeline">
        <f7-pages>
          <f7-page name="timeline">
            <f7-navbar title="Timeline" sliding />
            <f7-block inner inset>Timeline Content</f7-block>
            <f7-link href="/contact/">Voir un contacts</f7-link>
          </f7-page>
        </f7-pages>
      </f7-view>

      <f7-view tab id="contacts" active :dynamic-navbar="true">
        <f7-pages>
          <f7-page name="contacts">
            <f7-navbar title="Contacts" sliding />
            <f7-block inner inset>Contacts Content</f7-block>
            <f7-link href="/contact/">Voir un contacts</f7-link>
          </f7-page>
        </f7-pages>
      </f7-view>

      <f7-toolbar tabbar bottom>
        <f7-link tab-link="#timeline">Timeline</f7-link>
        <f7-link tab-link="#contacts" active>Contacts</f7-link>
      </f7-toolbar>

    </f7-views>

</template>

Contact.vue
<template>
  <f7-page name="contact">
    <f7-navbar back-link="Contacts" title="Pétunia" sliding />
    <f7-block-title>Un pitit titre</f7-block-title>
    <f7-list>
      <f7-list-item title="Go to Notebook" link="/notebook/" />
      <f7-list-item title="Info 2" />
    </f7-list>
  </f7-page>
</template>

Screenshots
The first tab shows its title as expected (there is not the dynamic navbar)

The second tab, with dynamic navigation, doesn't show its title

When using the "Voir un Contact" link in the 2nd tab, the contact page (named "Pétunia") opens as expected, and when I go back with swiping, it works perfectly, except that the title of the 1st page is still not here...

I do not know why it is working now, but I finally solved the issue after hours and hours of trying different solutions...
So, in case someone has the same issue one day, here is the skeleton of my app :)
app.vue
<template>

		<f7-panel right reveal layout="dark">
			<f7-view>
				<f7-navbar title="Menu" />
			</f7-view>
		</f7-panel>

		<f7-views tabs navbar-through toolbar-through>

			<f7-view tab id="timeline" url="/timeline/" active dynamic-navbar="true" />
			<f7-view tab id="contacts" url="/contacts/" dynamic-navbar="true" />

			<f7-toolbar tabbar bottom>
				<f7-link tab-link="#timeline" active>Timeline</f7-link>
				<f7-link tab-link="#contacts">Contacts</f7-link>
			</f7-toolbar>

		</f7-views>

</template>

contacts.vue
<template>
	<f7-page name="contacts">
		<f7-navbar title="Contacts" sliding />
		<f7-list>
			<f7-list-item title="Contacts Content" />
			<f7-list-item title="Open Contact Card" link="/contact/" />
		</f7-list>
	</f7-page>
</template>

timeline.vue
<template>
	<f7-page name="timeline">
		<f7-navbar title="Timeline" sliding />
		<f7-list>
			<f7-list-item title="Timeline Content" />
			<f7-list-item title="Open Event Card" link="/event/" />
		</f7-list>
	</f7-page>
</template>

contact.vue
<template>
	<f7-page name="contact">
		<f7-navbar back-link="Contacts" title="Contact" sliding />
		<f7-list>
			<f7-list-item title="Contact Card Content" />
			<f7-list-item title="Go to Notebook" link="/notebook/" />
		</f7-list>
	</f7-page>
</template>

event.vue
<template>
	<f7-page name="event">
		<f7-navbar back-link="Timeline" title="Event" sliding />
		<f7-list>
			<f7-list-item title="Event Content" />
		</f7-list>
	</f7-page>
</template>

notebook.vue
<template>
	<f7-page name="notebook">
		<f7-navbar back-link="Contact" title="Notebook" sliding />
		<f7-list>
			<f7-list-item title="Note Title 1" />
			<f7-list-item title="Note Title 2" />
		</f7-list>
	</f7-page>
</template>

routes.json
[{
		"path": "/contact/",
		"component": "contact.vue"
	},
	{
		"path": "/contacts/",
		"component": "contacts.vue"
	},
	{
		"path": "/home/",
		"component": "home.vue"
	},
	{
		"path": "/notebook/",
		"component": "notebook.vue"
	},
	{
		"path": "/timeline/",
		"component": "timeline.vue"
	},
	{
		"path": "/event/",
		"component": "event.vue"
	}
]


Add VSCodeTokenCredential

Do you need to export the types in index.d.ts too?

Yup. I always forget that's not generated here.


First stab at figuring out the number of very active mentors

Relates to #114
This is a work in progress pull request. The goal is to extract the number of very active mentors in a project based on number of comments they left in issues and pull requests.
In order to avoid including endless discussion threads that often go in circles the idea is to limit the number of issue comments and pr comments taken into consideration.
This is also where I need input:
As in many other issue-metrics stats I used https://github3.readthedocs.io/en/1.0.1/issues.html#github3.issues.issue.Issue.comments in order to iterate over comments. In the documentation it says the iterator can limit the number of comments considered. In my test case though it seems to ignore this parameter. Likely I mis-understood the use of the iterator?
Readiness Checklist
Author/Contributor

[ ] If documentation is needed for this change, has that been included in this pull request
[ ] run make lint and fix any issues that you have introduced
[x] run make test and ensure you have test coverage for the lines you are introducing

Reviewer

[x] Label as either bug, documentation, enhancement, infrastructure, or breaking

next step for this one looks like working on fixing the tests.

I fixed the linter errors, ran the tests.
Still on my TODO list:

Option to enable/disable this check.
Output of results.

Output added to markdown and call added - and fixed the issues with the original design.
Still missing:

Output in json.
Additional configuration options for disabling this feature and configuring e.g. cutoff for who is considered an active mentor.

In the last commit I added mentor counting results to json output. In addition max number of comments per issue as well as the cutoff number for heavily involved mentors are now configurable.
Tests seem to run through locally, including the ones I added.
make lint left two warnings.
With that I think this is ready for getting a closer look and feedback.
Wish you Happy Easter (no, no Easter eggs hidden here ;) )

Fixed merging errors.
There are two lint warnings still open that I can't figure out.

I can dig into some of these linting errors. I'll set aside some time this coming week.

@MaineC I was able to correct the linting errors and override some unreasonable linting rules. Ready to click the ready for review button?

Clicked the button.

@MaineC Feel free to review and integrate the change requests from @jmeridth.


log formatting is messed up and there is no scrolling

Steps:

Go to apps and install monitoring or some other rancher app.

Results:  The shell pops up but the formatting is bad.  The date field is taking up 2 lines and I can't scroll to see past information.

Fixed


Container has wrong size when it appears after expanding

Godot version
3.x a76316c, does not happen on master
System information
W10
Issue description

The size after appearing was the size I gave the container originally. I then duplicated the contents and after toggling visibility, it doesn't restore the expanded size, but the old one.
Steps to reproduce

Create a container and give it some size
Put miltiple controls inside the container, so that it expands
Toggle visibility of the container twice
The container will appear with its original size

Minimal reproduction project
BugScene.tscn.txt
Duplicate the TextureRects and toggle visibility of root.

Fixed on latest branch
It was another regression from #57900


Implement explicit lockfiles integration

Closes #21

[X] conda list --explicit extensions
[x] conda install | create extensions for the above output
[x] Tests
[ ] Docs

This is how the output of conda list --explicit would work, btw:
# This file may be used to create an environment using:
# $ conda create --name <env> --file <this file>
# platform: osx-arm64
@EXPLICIT
https://conda.anaconda.org/conda-forge/osx-arm64/bzip2-1.0.8-h93a5062_5.conda
https://conda.anaconda.org/conda-forge/osx-arm64/c-ares-1.23.0-h93a5062_0.conda
https://conda.anaconda.org/conda-forge/osx-arm64/ca-certificates-2024.2.2-hf0a4a13_0.conda
https://conda.anaconda.org/conda-forge/osx-arm64/icu-73.2-hc8870d7_0.conda
https://conda.anaconda.org/conda-forge/osx-arm64/jpeg-9e-h1a8c8d9_3.conda
https://conda.anaconda.org/conda-forge/osx-arm64/libcxx-16.0.6-h4653b0c_0.conda
https://conda.anaconda.org/conda-forge/osx-arm64/libdeflate-1.17-h1a8c8d9_0.conda
https://conda.anaconda.org/conda-forge/osx-arm64/libedit-3.1.20191231-hc8eb9b7_2.tar.bz2
https://conda.anaconda.org/conda-forge/osx-arm64/libev-4.33-h93a5062_2.conda
https://conda.anaconda.org/conda-forge/osx-arm64/libffi-3.4.2-h3422bc3_5.tar.bz2
https://conda.anaconda.org/conda-forge/osx-arm64/libiconv-1.17-h0d3ecfb_1.conda
https://conda.anaconda.org/conda-forge/osx-arm64/libwebp-base-1.3.2-hb547adb_0.conda
https://conda.anaconda.org/conda-forge/osx-arm64/libzlib-1.2.13-h53f4e23_5.conda
https://conda.anaconda.org/conda-forge/osx-arm64/llvm-openmp-17.0.6-hcd81f8e_0.conda
https://conda.anaconda.org/conda-forge/osx-arm64/lzo-2.10-h642e427_1000.tar.bz2
# Following lines added by conda-pypi
# pypi: gitpython==3.1.32 --python-version 3.9.9 --implementation cp
# pypi: platformdirs==4.2.2 --python-version 3.9.9 --implementation cp
# pypi: sphinx==4.2.0 --python-version 3.9.9 --implementation cp
# pypi: python-dateutil==2.8.1 --python-version 3.9.9 --implementation cp
# pypi: pathspec==0.8.1 --python-version 3.9.9 --implementation cp
# pypi: charset-normalizer==2.0.7 --python-version 3.9.9 --implementation cp
# pypi: tornado==6.1 --python-version 3.9.9 --implementation cp --abi cp39 --platform macosx_11_0_arm64
# pypi: gitdb==4.0.10 --python-version 3.9.9 --implementation cp
# pypi: black==21.6b0 --python-version 3.9.9 --implementation cp
# pypi: regex==2021.4.4 --python-version 3.9.9 --implementation cp --abi cp39 --platform macosx_11_0_arm64
# pypi: tzdata==2023.3 --python-version 3.9.9 --implementation cp
# pypi: pillow==8.3.2 --python-version 3.9.9 --implementation cp --abi cp39 --platform macosx_11_0_arm64

We can't print the URL for PyPI wheels because it wasn't kept around 😬

I'm not personally a fan of using the CLI flags here but these are the problems I faced trying to obtain something else:

There's no record of the origin URL for an installed PyPI package (see https://github.com/pypa/pip/issues/10736). This might change with PEP-710, but it's still a draft.
The environment markers (`name=version; python_version='2.7' etc) do not limit which wheels will be obtained, but which lines are accepted for inclusion in the request list given the current Python interpreter.

I wish there was a way to encode the constraints in a single string field (like a URI or something), but right now this is the only way, I think.

Thanks for the thorough review!

I'm not sure how I feel you expanding this format without a spec and a CEP since that's definitely a core functionality in conda

I do want the CEP. For the original format too. There's no standard to refer to other than the implementation. It should be straightforward.

There has to be other ways than implementing custom argv parsing and custom Python packaging standards parsing (big maintenance risk based on my experience)

conda has its own parsers but I only learnt that after writing this prototype. I'm sure we can find some parsers somewhere in packaging and friends too. Right now I'm mostly exploring how this idea would shape up, but I agree we need to polish this custom code better. Even the structure of the code could use some improvement.

Inline docs and high-level reasoning for some of the design decisions are sorely needed before merging this

Yep, just wanted to get some external confirmation that this idea is worth pursuing before writing details on something that might not fly. I take that this review is also a 👍 to proceed further?

I do want the CEP. For the original format too.

There you go: https://github.com/conda/ceps/pull/79

Hey @jezdez, I think I addressed most of your comments now. The PR is getting a bit too big so we can address further changes in new PRs. WDYT? After this PR I feel comfortable moving things to conda-incubator.

@jaimergp thank you for doing the rounds on the standardization, this'll be a net benefit!


run.dlang.io: failure to pass some command line options for "all dmd compilers"

Some compiler options don't work with "all dmd compilers", e.g. -betterC or -boundscheck=off, they result in std.conv.ConvException@/home/travis/dlang/dmd-2.084.0/linux/bin64/../../src/phobos/std/conv.d(2110): Can't parse string: bool should be case-insensitive 'true' or 'false'

That's probably because a different Docker image is used for this: https://github.com/dlang-tour/core-dreg


Add docstrings

It would be good to write some docstrings to describe public methods in api.py file.
Docstrings should be in format:
"""Short description.

Longer description
if needed.

Args:
    param1 (int): The first parameter.
    param2 (str): The second parameter.

Returns:
    int: Sum of param1 and length of param2.

Raises:
    ValueError: If arguments have wrong types.

"""

I'll do that.

@pduzinki There is #7 PR, but I think you can also take a look on this. Thanks! :relaxed:


New style for homepage

This PR contains cosmetic changes on then homepage.
Here is a snapshot on imgur.
The icons have been changed, realigned some elements, changed the font, removed the border radius, cleanup the usage of the containers and rows.
It goes with the PR on the https://github.com/baptistemanson/zf-mkdoc-theme named new-style-upgrade.

The icons are all free + CC except one which has a commercial license - which I transfer to the project.
The specific CSS for this homepage has been isolated in its own file in the theme folder called zend-expressive. I could have named it better, and probably will later.

Thanks!

@baptistemanson This looks like you merged develop to master, pushed, but did not add any commits...

@baptistemanson I went searching for the commits on your own repository, and cannot find them there, either...

@baptistemanson Steps you should take:

Fetch latest changes from this repository (I merged some CSS changes in #299): git fetch upstream
Rebase your new-style-for-homepage branch against master: git rebase upstream/master.
When you add your files and changes, you can put any component-specific CSS changes into the doc/book/css/zend-expressive.css file.

I'm going to create an alternate PR for the short-term that adds the install instructions into the jumbotron, as I'm not sure when you'll be available today. :smile:

I'll do this morning, thanks sorry for the confusion.

I will redo the PR then.


add doodle_jump game

A gravity defying creature trying to reach wants to higher steps, with your help. So keep your fingers on the keyboard and help the doodler.

assign it to me


Update guidance and hint text on declaring safeguarding issues page

Context
We want to avoid candidates being taken by surprise if they get a call from a provider asking about their criminal convictions.
Changes proposed in this pull request
This PR updates the guidance and hint text on the declaring any safeguarding issues page.
Before

After

Guidance to review
See prototype (https://apply-beta-prototype.herokuapp.com/application/6IZO5/suitability).
Link to Trello card
https://trello.com/c/Cc3DjaCr/1202-dev-content-change-to-safeguarding-section-following-decisions-about-how-providers-access-this-data
Things to check

[x] This code doesn't rely on migrations in the same Pull Request
[x] If this code includes a migration adding or changing columns, it also backfills existing records for consistency
[x] API release notes have been updated if necessary
[x] New environment variables have been added to the Azure config

looks great!


Introduce the documentation team

cc https://github.com/rust-lang/rfcs/pull/1683

r? @nikomatsakis
(rust_highfive has picked a reviewer for you, use r? to override)

🚆

This doesn't add a link to the docs team from https://www.rust-lang.org/en-US/community.html , which seems to be the main entry point to the teams page.

@quodlibetor oh nice catch! Will send a follow-up

https://github.com/rust-lang/rust-www/pull/475


Update Runtime Bundle Endpoints to use content type header instead of PATH

Refer to https://github.com/Activiti/Activiti/issues/1513

 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.

Codecov Report

Merging #7 into develop will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             develop       #7   +/-   ##
==========================================
  Coverage      58.88%   58.88%
  Complexity        54       54
==========================================
  Files             56       56
  Lines            625      625
  Branches          12       12
==========================================
  Hits             368      368
  Misses           252      252
  Partials           5        5

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2c9dce1...43d0668. Read the comment docs.


Update Regex in app.ts

This pull request updates the regex in app.ts based on ChatGPT suggestions.

Closing as test


OS 2.1: missing feature to project motion text change proposals

The new feature of changing motion text is very awesome! Many thanks for this, this is what I was personally looking for.
Allow me nevertheless a bug report:
Currently I can visualize a change proposed by a participant of the conventions:

What is now only missing are these 2 things:

I cannot find a way to project the view of the above screenshot. But this is what people like to see before they vote for or against a change.
It is already perfect that there are the thumbs up/down icon behind a change. When pressing e.g. thumbs up because the participants voted for the change, I cannot display the result. I mean I click on "Resolution" but in the projector still the unchanged motion text is shown. During a convention we often have the case that people want to see the final text before the next topic is called.

Could anybody please tell me how to get this feature? I once discovered and were so amazed. But now I don't know how to get this feature.

This is still a missing feature to project each view of motion. Currently only original view can be projected.

@emanuelschuetze Closed with PR #2796 .

Many thanks, however, the line numbering does not yet work correctly, see bug #3027.


Drop python 2.6 support

See this email thread as well:
https://groups.google.com/forum/#!topic/luigi-user/X8YA_JpQ8dQ

Should I assume no complaints as OK to merge? :)
@jcrobak @daveFNbuck

Merging for now to speed up Travis build times. At least. Anyone feel free to audit this decision.

Is Python 2.6 support a big deal to maintain? I don't think it is

It was a big deal when Spotify was relying on it. I just wanted to give a fair chance for other big users of luigi to object.
By the way @erikbern, it's time for you to re-introduce your patch where you were about to remove OptParse support. Now there's no blockers to remove it :D

What I meant is what's the cost of maintaining 2.6 support? Is it very high? If so, we should drop it. If it's low, we should keep it.
It seems low to me but I could be wrong

The optparse issue was actually in 2.7.9 btw

afaik some things can be simplified if we drop 2.6, like we can use functools.total_ordering for DateInterval

Ah, I see what you mean now. I think we shouldn't claim to maintain it without anybody using it. It could lead to strange bugs that tests don't cover and affect only 2.6. As I mentioned in my mail to<EMAIL_ADDRESS>

Well... we have 2.6 tests running in Travis so shouldn't that be almost enough?
But if no one uses it then sure let's just drop it. I don't care too much

Nope, evidently it's not enough: https://github.com/spotify/luigi/pull/793/files
The other major benefit is the speedup in Travis build times. We're talking about a few minutes at least it seems per PR iteration. It's really annoying to wait for all the tests to pass when developing heavily on luigi.

But 2.6 tests are run in parallel right?
Anyway let's drop it and see if people complain... should be easy to add back alter

2.6 is the main cause of test failures for my commits, because I like to
use test functions that aren't present. Glad to see it leaving.
On Thu, May 7, 2015 at 5:47 AM, Erik Bernhardsson<EMAIL_ADDRESS>wrote:

But 2.6 tests are run in parallel right?
Anyway let's drop it and see if people complain... should be easy to add
back alter
—
Reply to this email directly or view it on GitHub
https://github.com/spotify/luigi/pull/934#issuecomment-99850891.

The optparse issue was actually in 2.7.9 btw

@erikbern: Does this mean that we need to maintain optparse still? I'm not sure what you meant there. I really want to remove it!
In #612 it sounded it was just because Spotify needed it for whatever reason. I'm pretty sure that's not the case for Spotify anymore. Any reason to not repoen #612?

We can prob just remove optparse, not sure why anyone would use it


Container Registry - Made Code Example Consistent

@jawache,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


[FEATURE][Spark] Support partial sort and combine for reducing shuffle data size

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Search before asking

[X] I have searched in the issues and found no similar issues.

Describe the feature
In spark client, currently uniffle don't support merge for some ops supporting combine  to reduce data size. Due to this, in some cases, it will cause unnecessary network and performance regression.
Motivation
No response
Describe the solution
No response
Additional context
No response
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

I encounter this problem in our online jobs, but I don't dig into it. Anyway, from my side, this feature is an improvement.
cc @xianjingfeng @advancedxy @jerqi

You mean map side combine?

Yes

If we are going to support this feature, maybe a lot of client side code should be rewrote...😇

Yes. 🙆

we also have this demand. I met in hudi table which will use countByKey to evaluation work load.

any plan to support it?

any plan to support it?

haven't. If you want this, feel free to discuss more

how about use ExternalAppendOnlyMap to archive it, but it's may spill to disk, we can add a param to controll it. And I think if map side can be combine, it will reduce shuffle data and reduce data skew problems

ExternalAppendOnlyMap is used to handle huge data, I think it is not necessary. We can sort and combine in memory, then serialize the records. I did it in #1239 (developing) by this way. But I bind only the use of the remote merge feature.
I afraid that the proportion of being combined may be not high, since we use pipelined shuffle in rss, only partial record will be combined.

The client and server side merge are all needed.

I think the merging should work on the client side, not on the RSS server. It maximizes the utilization of executor resources, rather than placing the computation burden on the RSS server, whose resources are shared and need to ensure stability and the normal operation of core services.

And furthermore, I think the RSS server is best left to handle data transmission efficiently without any content processing. It should return whatever it receives from user tasks. All data content processing is preferably performed by the executors, allowing the RSS server to focus solely on efficient shuffle transmission. What do you think?

If you think RSS sever should not handle any content, you can save the shuffle date to 3rd remote filesystem, and read the shuffle data from this filesystem.
What is your purpose of using remote shuffle service?
For me, the main purpose for remote merge in shuffle side is that application will not use any local file as shuffle storage, then we can realize the separation of storage and computing, then support hybrid deployment.

I think the merging should work on the client side, not on the RSS server.

I think the zheng's design motivation is not same with you @KnightChess , if you want this, client merge design is OK for me, that is not conflict with remote merge. Right @zhengchenyu

Well, yes. I'm just offering a suggestion, sort in memory. There is no conflict!


Update Streamline DEVELOPER.md with registry dependency

Often people who try to build streamline locally face issues since the version of the registry dependencies mentioned in streamline are not available in the Hortonwork's nexus repo. Update docs to indicate registry dependencies and how to build them locally.

I wish we just release non-HDF artifacts of both projects and let Streamline refers non-SNAPSHOT version of Registry. We may want to allow referring SNAPSHOT version, but no longer released version.

Also related to #776 and https://github.com/hortonworks/registry/issues/170

We can either

Keep the registry dependency as SNAPSHOT version in streamline pom.xml and update the build instructions
Update the streamline pom.xml to the latest released registry version. In this case if we want some integration with registry, need to wait for the next release version.

@HeartSaVioR @harshach let me know your inputs.

Personally I think 2. as ideal.
Streamline is better to be treated as a use case of Registry, then Registry shouldn't force Streamline to update it too sooner, even following SNAPSHOT version. Does Streamline really need to catch up and keep up Registry tightly?
This doesn't represent Registry needs to consider backward compatibility, but looks like not all of Registry changes are necessary to Streamline.
ps. My 2 cents, maybe posting this to google group may help group more active.

Streamline depends on a few recent changes made in registry which is not available in 0.3.0, so for now SNAPSHOT version is required.
We need a new minor release for registry and then the streamline pom.xml can be updated to depend on that. Maybe it can be pushed to maven central to decouple from the Hortonworks releases.
cc @satishd


[docs] Improve installation process and instructions for Linux

Hi,
Related to https://github.com/openjournals/joss-reviews/issues/5135; the Linux command in the README.md file doesn't work when pasted in the command-line. I've submitted a quick PR for that, see #8
However, running the command I get:
Please run with privilege

Looking at the sources, it runs docker-compose --env-file .env -f Docker/docker-compose.yml up --build -d.
If I modify the command, and use docker compose instead, that runs fine on my computer without the need of root access (I did that step to run it rootless).
The script also appears to have some logic to ask the user the operating system,
echo "What operating system are you running?"
echo "1) Windows"
echo "2) Linux"
read -p 'Boot option: ' os
if [[ $os != 2 ]]
then
    echo "You gave an invalid option for the OS (either not 1/2 or Windows)."
    echo "Try again by reopening the file. Goodbye for now!"
    exit
fi

That doesn't look useful as there are two scripts, one of Linux and one for Windows. There could also be MacOS users that could not be sure which version to choose.
IMHO, it'd be easier to just list the docker compose command, and leave the operating system out. Or re-write the installation process to simplify it, and make sure the docs work for users on Linux and/or the possible issues & variations of commands are documented (e.g. maybe say "if you have docker compose, you can run this command... if you have not configured it as rootless you may need to use sudo, etc..").
Cheers
-Bruno

Hi,
I resolved the issues mentioned here, the readme has been updated accordingly. Docker compose commands are listed now rather than making use of shell scripts.
Thanks for the detailed feedback,
Jarl


Stuck on Connecting to Steam Public

I used to use this container previously and never had any issues but trying to get it going after the new game update, I keep getting stuck on "Connecting anonymously to Steam Public...". It gets hung up on this and never succeeds to download the server client. I tried binding 9001 and 80 to see if that made a difference but it didn't.
Ubuntu 22.04.1 LTS, amd64
    --name valheim-server \
    --cap-add=sys_nice \
    --stop-timeout 120 \
    -p 2456-2457:2456-2457/udp \
    -v /home/games/valheim/config:/config \
    -v /home/games/valheim/data:/opt/valheim \
    -e SERVER_NAME="My Server" \
    -e WORLD_NAME="Dec22" \
    -e SERVER_PASS="ragnar" \
    -e VALHEIM_PLUS=true \
    lloesche/valheim-server```

This sounds like it might be a 32bit library compatibility issue that we saw with older kernels. Can you try the latest version to see if it resolves the issue? There's also the :debian10 container tag that uses the old libraries but has no crossplay support.

I am having the same issue, also on Jammy Ubuntu.
Linux docker 5.15.0-56-generic #62-Ubuntu SMP Tue Nov 22 19:54:14 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
When you say try the latest version, what do you mean? The latest version of what?

Ok, I solved this in my case, which was specific to my environment. I am running my DNS resolver (pihole) also set up as a container. When this Valheim container started it didn't have any DNS resolution, because the pihole container is/was running on the same host. I had to tell the pihole container to use host networking instead of forwarded ports.

I'm running this on a Synology NAS and have been struggling with the container auto-updating and never finishing/starting. I initially followed all of the steps to do an update (before lloesche updated the docker image) and had the same result. After he updated the image in Docker Hub it works like a charm now.

Could you describe if you did something specific? I have the same problem and have a feeling this is due to the firewall not allowing the connection to steam to do updates...

I'm running this on a Synology NAS and have been struggling with the container auto-updating and never finishing/starting. I initially followed all of the steps to do an update (before lloesche updated the docker image) and had the same result. After he updated the image in Docker Hub it works like a charm now.

Could you describe what you did exactly? I have the same problem and have a feeling this is due to the firewall not allowing the container to access steam to update...

Is port 2568 also needed to be forwarded from the container?

Valheim needs ports 2456-2458, however, unless you are doing something out of the ordinary incoming ports should not affect the server updating itself since that is an outbound connection and NAT'ed on the way out.

Feb 10 15:37:06 assert_20230210153646_6.dmp[111]: error: Couldn't resolve host name
Feb 10 15:37:06 assert_20230210153646_6.dmp[111]: file ''/tmp/dumps/assert_20230210153646_6.dmp'', upload no: ''Couldn't resolve host name''

This looks like a DNS issue. Where is DNS running? If you console into the running container can you successfully resolve DNS addresses from within? My guess is no.

But then do I need to bridge 2458 from the container to host / NAS too? By default the image only bridges 2456-2457...
My setup is:

Forwarded Container -> Host UDP 2456-2457
Made firewall exception for UDP 2456-2458 on NAS
Opened port UDP 2456-2457 on Internet router

After the server has restarted or the DynDNS kicked in (presumably) I see the message "supervisord: valheim-server 02/12/2023 10:41:32: Game server connected failed" and I can't even connect via LAN IP, which is odd...
I tried:

root@valheim-server:/# cat /etc/resolv.conf
nameserver      <LOCAL_ROUTER_IP>
and LOCAL_ROUTER_IP points to the IP of my internet router. Should should this point to a fixed DNS server here, e.g. <IP_ADDRESS>? I'm not sure why this is necessary for LAN though...

Got this to work. It was a firewall problem. The container / docker was unable to talk to the NAS internally. What I did:
Take note of your docker bridge settings / IPs:

Go to your firewall settings and add a rule:

with the IP range of your docker bridge:

Note that the order of rules matters!
If you want your container to be reachable from the outside make sure to add a rule to open ports 2456-2457 in the synology firewall and forward them in your internet router too. Port 2458 is used by the Valheim server, but does not need to be forwarded.


weave on kubernetes - communication to other nodes no longer possible

What you expected to happen?
We expect communication between pods on different kubernetes nodes not to break
What happened?
Symptoms: pods on 1 kubernetes worker node stop being able to communicate with pods on other worker nodes. All other worker nodes remain fine. To work around the problem, we delete the weave pod on the affected worker node. Once the new pod is up, everything returns to normal.
After a while (anywhere between 24 and 96 hours) the problem happens again. Sometimes with the same worker node, sometimes with a different worker node.
When looking at the connections, some or all connections are using sleeve instead of fastdp.
How to reproduce it?
It is happening about 1x per 48 hours for us currently. We do not yet have a way to trigger the problem
To try and trigger the problem we disconnected the network on one of the worker nodes for a few seconds, but that did not do anything.
Anything else we need to know?
$ kubectl get nodes -o wide
NAME              STATUS   ROLES    AGE   VERSION   INTERNAL-IP   EXTERNAL-IP   OS-IMAGE                KERNEL-VERSION           CONTAINER-RUNTIME
kubem-01.p.nl01   Ready    master   45d   v1.14.6   <IP_ADDRESS>    <none>        CentOS Linux 7 (Core)   3.10.0-1127.el7.x86_64   docker://18.9.7
kubem-02.p.nl01   Ready    master   45d   v1.14.6   <IP_ADDRESS>    <none>        CentOS Linux 7 (Core)   3.10.0-1127.el7.x86_64   docker://18.9.7
kubem-03.p.nl01   Ready    master   45d   v1.14.6   <IP_ADDRESS>    <none>        CentOS Linux 7 (Core)   3.10.0-1127.el7.x86_64   docker://18.9.7
kubew-01.p.nl01   Ready    <none>   45d   v1.14.6   <IP_ADDRESS>    <none>        CentOS Linux 7 (Core)   3.10.0-1127.el7.x86_64   docker://18.9.7
kubew-02.p.nl01   Ready    <none>   45d   v1.14.6   <IP_ADDRESS>    <none>        CentOS Linux 7 (Core)   3.10.0-1127.el7.x86_64   docker://18.9.7
kubew-03.p.nl01   Ready    <none>   45d   v1.14.6   <IP_ADDRESS>    <none>        CentOS Linux 7 (Core)   3.10.0-1127.el7.x86_64   docker://18.9.7

created by kubespray 2.11
This runs in VMs on 3 hypervisors on-prem.
In my eyes the symptoms of this issue resembles https://github.com/weaveworks/weave/issues/3641 and https://github.com/weaveworks/weave/issues/3773
Versions:
$ weave version
        Version: 2.5.2 (version check update disabled)

        Service: router
       Protocol: weave 1..2
           Name: 7e:a4:fd:ed:fb:eb(kubew-03.p.nl01)
     Encryption: enabled
  PeerDiscovery: enabled
        Targets: 6
    Connections: 6 (5 established, 1 failed)
          Peers: 6 (with 30 established connections)
 TrustedSubnets: none

        Service: ipam
         Status: ready
          Range: <IP_ADDRESS>/18
  DefaultSubnet: <IP_ADDRESS>/18

$ kubectl version
Client Version: version.Info{Major:"1", Minor:"18", GitVersion:"v1.18.3", GitCommit:"2e7996e3e2712684bc73f0dec0200d64eec7fe40", GitTreeState:"clean", BuildDate:"2020-05-21T14:51:23Z", GoVersion:"go1.14.3", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"14", GitVersion:"v1.14.6", GitCommit:"96fac5cd13a5dc064f7d9f4f23030a6aeface6cc", GitTreeState:"clean", BuildDate:"2019-08-19T11:05:16Z", GoVersion:"go1.12.9", Compiler:"gc", Platform:"linux/amd64"}

Logs:
from this moment the communication problem started:
INFO: 2020/06/25 22:52:21.822433 overlay_switch ->[6e:d6:5e:a3:11:e7(kubem-03.p.nl01)] using sleeve
INFO: 2020/06/25 22:52:21.831501 overlay_switch ->[7a:ed:82:5e:d8:49(kubew-02.p.nl01)] using sleeve
INFO: 2020/06/25 22:52:21.840212 overlay_switch ->[b2:d9:ec:8b:d8:ff(kubem-01.p.nl01)] using sleeve
INFO: 2020/06/25 22:52:21.862142 overlay_switch ->[fa:b4:e9:63:60:33(kubem-02.p.nl01)] using sleeve
INFO: 2020/06/25 22:52:24.123512 overlay_switch ->[b6:55:d4:04:30:d3(kubew-01.p.nl01)] using sleeve

full logs of that worker node's weave pod are in https://gist.github.com/vernimmen-textkernel/110a8219a7ea33eeeea3997adf18bf6c

The problem reoccurred this time after 3 days. I've now enabled debug logging to get more information when it happens again.

And happened again this morning. The debug log for the broken pod (and some other details) is here: https://gist.github.com/vernimmen-textkernel/7b99aa7c076b4458684669dea4092c3f

And another one: https://gist.github.com/vernimmen-textkernel/a8e3959f2c856ca9519c05640eba7ab0
I have now applied the automatic weave pod restart when there are too many sleave connections as mentioned in issue 3773, so we probably won't notice more of this problem. I hope the above logs and debug logs are enough to find the cause of the problem.

Hi @vernimmen-textkernel
Where you get a message like this:
INFO: 2020/06/25 22:51:21.442962 ->[<IP_ADDRESS>:6783|fa:b4:e9:63:60:33(kubem-02.p.nl01)]: connection shutting down due to error: read tcp4 <IP_ADDRESS>:46468-><IP_ADDRESS>:6783: read: connection reset by peer

we need the logs of the other side, to see why it dropped the connection.
Could you please do weave status connections at the time of the outage to show what is and isn't working.
There are no errors or connection drops in the other two gists.
(Generally we can see what happened from INFO logs and don't need DEBUG)

I have thought that my networks problems are related to this issue.
In my case: Weave had never uses the sleeve mode.
After investigating a lot of issues on github I have found the solution for my problem:
Connection between nodes was cancalled and broken because the iptables rules were incorrect. It took me a lot of time to solve and understand this.
My kube-proxy.yaml not contains the xtables.lock-File.
So, weave-net uses the /run/xtables.lock file but kube-proxy not. So the two applications had a kind of race conditions while manipulating the iptables rules....

Lust checked. In my case (KOPS managed cluster) kube-proxy manifest have xtables.lock-File mount. Same for weave.
@nesc58
Can you show pls exact part you missed?

for my case if I would be able to check connectivity (from the weave pod) to the cluster services I would be able to setup liveness check.
The tricky part for me now - how to do this with weave since it's privileged pod with host networking. and I should do such checks over weave provided layer.
Anyone have ideas?

Hi,
apologies for the late reply.
The weave daemonset contains the following mounts. I have removed a lot of other lines (metadata, hostnetwork and so on).
containers:
- name: weave
  image: weaveworks/weave-kube:2.6.5
  ...
  volumeMounts:
    ...
    - name: xtables-lock
      mountPath: /run/xtables.lock
      readOnly: false
- name: weave-npc
  image: weaveworks/weave-npc:2.6.5
  ...
  volumeMounts:
  - name: xtables-lock
    mountPath: /run/xtables.lock
    readOnly: false
volumes:
...
- name: xtables-lock
   hostPath:
   path: /run/xtables.lock
  type: FileOrCreate

These mounts must also available to the kube-proxy containers.  (for me located at /etc/kubernetes/manifests/kube-proxy.yaml, I dont know were the static pod files stored on your system)
apiVersion: v1
kind: Pod
...
spec:
  hostNetwork: true
  containers:
    - name: kube-proxy
      image: gcr.io/google-containers/kube-proxy-amd64:v1.18.6
      command:
        - kube-proxy
        - --config=/var/lib/kubelet/kube-proxy.config
      securityContext:
        privileged: true
      volumeMounts:
        ...
        - mountPath: /run/xtables.lock
          name: iptableslock
          readOnly: false
  volumes:
     ...
    - hostPath:
        path: /run/xtables.lock
        type: FileOrCreate
      name: iptableslock

The mounts for kube-proxy missed on my system. When these mounts already set on your system, iptables modifications should work fine.
We had a lot of configuration issues. These issues resulted in a unstable running cluster. So I think that our problems differs a lot (i think).
Maybe kops  created all parameters correctly and there are no manually fixes needed.
Here's what configurations I changed:
We use debian linux distribution. So cgroups are managed by systemd by default. On other distributions the work is done by cgroupfs.
So I had to change the docker daemon to use systemd as cgroup driver. (default is cgroupfs). Therefore the configuration of kubelet must also changed to use the systemd cgroup driver. (https://github.com/kubernetes/kubeadm/issues/1394)
Next, there seems to be a bug in cgroup handling when a lot of containers started/recreated. In this case we had to change some kernel parameters.
I added cgroup_enable=memory cgroup.memory=nokmem to the GRUB_CMDLINE_LINUX (grub is the default bootloader for debian systems). (https://github.com/kubernetes/kubernetes/issues/70324#issuecomment-433612120 -> referenced issues)
On our clusters there were no crashed since these changes. I would say: The fix works for me but I can't say this is the universal solution for all problems. I'm unable to figure out all side effects of these changes.
I am sorry that i cannot help you furthermore.


Unable to create/compare screenshots of opened Share Sheet

Describe the bug
If a share sheet has been opened, and I try to perform any action thereafter (in my case was trying to capture a screenshot), the test fails. I have tried disabling the animations with: await detox.device.disableSynchronization();
Example share sheet:

To Reproduce

[ ] I have tested this issue on the latest Detox release and it still reproduces

Steps to reproduce:

In an app where sharing is possible (share sheet is present), disable the animations with await detox.device.disableSynchronization();
Open the share sheet
Try to do a screen capture or screenshot comparison

Expected behavior
Because the animations are disabled, I should be able to create a screenshot or compare it.
Device and Verbose Detox Logs
Device: Android Emulator - Pixel 3
Output using --debug-synchronization 200
detox[43318] INFO:  [actions.js] Sync LooperIdlingResourceInterrogationHandler: LooperIdlingResource-4944-mqt_js
detox[43318] INFO:  [actions.js] Sync UIModuleIdlingResource: com.wix.detox.reactnative.idlingresources.UIModuleIdlingResource
......
.F-.detox[43318] INFO:  [actions.js] Sync AnimatedModuleIdlingResource: com.wix.detox.reactnative.idlingresources.AnimatedModuleIdlingResource
detox[43318] INFO:  [actions.js] Sync AnimatedModuleIdlingResource: com.wix.detox.reactnative.idlingresources.AnimatedModuleIdlingResource
detox[43318] INFO:  [actions.js] Sync AnimatedModuleIdlingResource: com.wix.detox.reactnative.idlingresources.AnimatedModuleIdlingResource
detox[43318] INFO:  [actions.js] Sync AnimatedModuleIdlingResource: com.wix.detox.reactnative.idlingresources.AnimatedModuleIdlingResource
detox[43318] INFO:  [actions.js] Sync AnimatedModuleIdlingResource: com.wix.detox.reactnative.idlingresources.AnimatedModuleIdlingResource
detox[43318] INFO:  [actions.js] Sync AnimatedModuleIdlingResource: com.wix.detox.reactnative.idlingresources.AnimatedModuleIdlingResource
detox[43318] INFO:  [actions.js] Sync AnimatedModuleIdlingResource: com.wix.detox.reactnative.idlingresources.AnimatedModuleIdlingResource
detox[43318] INFO:  [actions.js] Sync AnimatedModuleIdlingResource: com.wix.detox.reactnative.idlingresources.AnimatedModuleIdlingResource
detox[43318] INFO:  [actions.js] Sync AnimatedModuleIdlingResource: com.wix.detox.reactnative.idlingresources.AnimatedModuleIdlingResource
detox[43318] INFO:  [actions.js] Sync AnimatedModuleIdlingResource: com.wix.detox.reactnative.idlingresources.AnimatedModuleIdlingResource
detox[43318] INFO:  [actions.js] Sync AnimatedModuleIdlingResource: com.wix.detox.reactnative.idlingresources.AnimatedModuleIdlingResource
detox[43318] INFO:  [actions.js] Sync AnimatedModuleIdlingResource: com.wix.detox.reactnative.idlingresources.AnimatedModuleIdlingResource

Environment (please complete the following information):

Detox: ^17.13.1
React Native: 0.63.3
Node: 14.4.0
Device: Android Emulator - Pixel 3
OS: Android version 9
Test-runner (select one): cucumber-js

@jpoisch it is virtually impossible to help with this minimal chunk of logs. Please provide more info, as requested by the issue template. More so, it is likely not as you describe it with respect to the share sheet, because your logs suggest RN-rooted animations running endlessly.


Api change.. where is a good place to farm dratinis?

anywhere you like to go to?

Before they changed the Api I was able find them around the tower of london a few times,close to the bridge.

@hunterd95 this is not reddit

San francisco or Cancun Mexico, now close thread


Make Linux binaries load all their dependencies via libdl

Godot version
master/main
System information
elf/linux distro
Issue description
The following is to avoid GNU symbol/module version issues on the medium/long run (it is probably OS agnostic).
Expected: distributed binaries should be pure and simple elf64, namely fetch everything they need from the system with libdl (dlopen/dlsym/dlclose). It means that for all distributed binaries, system dependencies should be limited to libdl,  that in their elf static loading module list, and no other undefined symbols other than the ones from the distributed binaries should be in the elf dynamic symbol section.
problem: the static libstdc++ and static libgcc do not support libdl and seems to pull glibc internal symbols into the dynamic symbol section.
Steps to reproduce
get some godot game binaries compiled and link with a recent glibc, and try to run it on an old glibc (~2years should be enough) (or with another c/elf runtime which has a libdl)
Minimal reproduction project
No response

This would be interesting to do, as it'd allow you to use a recent Linux distribution to build binaries that could run on old Linux distributions (without having to use a container running an old Linux distribution to build binaries).
However, is this a viable approach for graphical applications that need to use OpenGL/Vulkan?

In this current state, c++ is not meant for binary-only distribution.
The userland container trick is shaby at best, since some games rely on direct /dev /sysfs interface (for instance feral interactive game loader), which is linux  version specific in spite of "ABI stability", namely those containers would have to package the right linux version too. In other words, a really-working/fully tested full vm plus 3D driver "pass-thru", that for each game...
2 major ways:
1 - eat the bullet and get in control: move godot towards conservative C (not gcc/clang only) and assembly.
2 - fix libgcc/libstdc++: either outmatch microsoft money (irony) to make gcc devs fix them, or fork them and fix them yourself (at the part required). Namely adding a libdl mode and removing any dependency on glibc internal symbols.

Closing, as this is not a problem we can address in any way. Neither 1. nor 2. are viable a	approaches for us, and any efforts of this kind should be tackled upstream.


themes/powerline-multiline uses command_exists before base.plugin.bash loaded

When I use the powerline-multiline theme, I get "command_exists: command not found".
I think it's because the base.plugin.bash plugin is not yet loaded.
I have tried adding bash-it enable base.plugin.bash to my .bashrc, but themes are always loaded first, so this does not solve the problem.
Perhaps the base plugin should always be loaded internally? Or perhaps themes / plugins that depend on it should always explicitly load it themselves as a dependency?

Here is where the theme calls command_exists:

https://github.com/Bash-it/bash-it/blob/d25835fbb90fd5ea86bc808ca0b10a3a60b3a8c5/themes/powerline-multiline/powerline-multiline.theme.bash#L89

I've also noticed that the battery plugin also uses it:

https://github.com/Bash-it/bash-it/blob/d25835fbb90fd5ea86bc808ca0b10a3a60b3a8c5/plugins/available/battery.plugin.bash#L5

Yes, that's right - Bash-it does not have any kind of dependency management for plugins/themes or the like.
There are two issues here, that need to be looked at separately:
Plugin dependencies
The battery plugin uses command_exists, which is defined in the base plugin - this is just one example, there are probably more than that. In this case, it works if you enable both base and battery, since they are loaded in alphabetical order, which means that command_exists will be available once battery is loaded.
There is no check for this, however. Making this more robust would require to introduce dependencies and creating a dependency tree upon loading. We're not going to tackle that at the moment...
Themes using functionality from plugins
This is indeed an issue. Enabling the base plugin (which you only need to do once by running bash-it enable plugin base - don't do this from your ~/.bashrc) will not help, since the loading order looks like this (in bash_it.sh):

lib/composure.bash
Base Theme
lib/*.bash, which loads the BASH_IT_THEME from appearance.sh
Aliases
Completions
Plugins
custom/*.bash

You can clearly see that plugins are loaded after the theme. Two ways to fix this:

Change the order, so that the theme is loaded last. This would allow themes to use any plugin functionality, with the above caveat that there's no dependency management.
Move the command_exists function into either the lib/appearance.sh or into the themes/base.theme.bash file. Potentially use an if safeguard around it to avoid defining it again.

@tswicegood @edubxb - what do you think?

Pretending for a minute that we have a real dependency tree, themes would always be leaves. It doesn't make sense for plugins to depend on themes, so it could make sense to always load enabled plugins prior to loading the selected theme.

I agree - now someone needs to make that change and verify that it doesn't have any side effects... PRs welcome...


Fixed possible socket allocator memory leak (#96), if csp_socket() fails.

Fixed general socket allocator memory leak by csp_socket(CSP_SO_CONN_LESS) -> csp_close().

In order to test these fixes, the unit test needed access to the internal csp_conn_t array in csp_conn.c, in order to verify things have been closed/opened.
I added csp_conn_get_array() in the internal csp_conn.[ch], and included this header in the unit test. There are other ways of making it testable, this is just the simplest I could think of.


Ingesting MySQL via the UI results in failed Airflow task due to MySQLConfig Error

Hello,
https://user-images.githubusercontent.com/42276144/150373085-9ba805f0-da28-49f6-856b-3e5bd2dfe86d.mov
In the above video, I am using the UI to create a new Ingestion.  It immediately fails.  The error that is given in the Airflow logs is that there is a validation error in the MySQL Config that filter_pattern is an "extra field"
I am on v0.7.0
*** Reading local file: /airflow/logs/my_ingest_3/my_ingest_3/2022-01-20T00:05:00+00:00/1.log
[2022-01-20, 15:42:20 UTC] {taskinstance.py:1035} INFO - Dependencies all met for <TaskInstance: my_ingest_3.my_ingest_3 scheduled__2022-01-20T00:05:00+00:00 [queued]>
[2022-01-20, 15:42:20 UTC] {taskinstance.py:1035} INFO - Dependencies all met for <TaskInstance: my_ingest_3.my_ingest_3 scheduled__2022-01-20T00:05:00+00:00 [queued]>
[2022-01-20, 15:42:20 UTC] {taskinstance.py:1241} INFO -
--------------------------------------------------------------------------------
[2022-01-20, 15:42:20 UTC] {taskinstance.py:1242} INFO - Starting attempt 1 of 1
[2022-01-20, 15:42:20 UTC] {taskinstance.py:1243} INFO -
--------------------------------------------------------------------------------
[2022-01-20, 15:42:20 UTC] {taskinstance.py:1262} INFO - Executing <Task(PythonOperator): my_ingest_3> on 2022-01-20 00:05:00+00:00
[2022-01-20, 15:42:20 UTC] {standard_task_runner.py:52} INFO - Started process 37826 to run task
[2022-01-20, 15:42:20 UTC] {standard_task_runner.py:76} INFO - Running: ['airflow', 'tasks', 'run', 'my_ingest_3', 'my_ingest_3', 'scheduled__2022-01-20T00:05:00+00:00', '--job-id', '108', '--raw', '--subdir', 'DAGS_FOLDER/my_ingest_3.py', '--cfg-path', '/tmp/tmp_weaex3w', '--error-file', '/tmp/tmpkk8q_qxu']
[2022-01-20, 15:42:20 UTC] {standard_task_runner.py:77} INFO - Job 108: Subtask my_ingest_3
[2022-01-20, 15:42:20 UTC] {logging_mixin.py:109} INFO - Running <TaskInstance: my_ingest_3.my_ingest_3 scheduled__2022-01-20T00:05:00+00:00 [running]> on host 5f7d0d56251d
[2022-01-20, 15:42:20 UTC] {taskinstance.py:1427} INFO - Exporting the following env vars:
AIRFLOW_CTX_DAG_OWNER=airflow
AIRFLOW_CTX_DAG_ID=my_ingest_3
AIRFLOW_CTX_TASK_ID=my_ingest_3
AIRFLOW_CTX_EXECUTION_DATE=2022-01-20T00:05:00+00:00
AIRFLOW_CTX_DAG_RUN_ID=scheduled__2022-01-20T00:05:00+00:00
[2022-01-20, 15:42:20 UTC] {taskinstance.py:1703} ERROR - Task failed with exception
Traceback (most recent call last):
  File "/usr/local/lib/python3.9/site-packages/airflow/models/taskinstance.py", line 1332, in _run_raw_task
    self._execute_task_with_callbacks(context)
  File "/usr/local/lib/python3.9/site-packages/airflow/models/taskinstance.py", line 1458, in _execute_task_with_callbacks
    result = self._execute_task(context, self.task)
  File "/usr/local/lib/python3.9/site-packages/airflow/models/taskinstance.py", line 1514, in _execute_task
    result = execute_callable(context=context)
  File "/usr/local/lib/python3.9/site-packages/airflow/operators/python.py", line 151, in execute
    return_value = self.execute_callable()
  File "/usr/local/lib/python3.9/site-packages/airflow/operators/python.py", line 162, in execute_callable
    return self.python_callable(*self.op_args, **self.op_kwargs)
  File "/airflow/dag_managed_operators/metadata_ingestion.py", line 5, in metadata_ingestion_workflow
    workflow = Workflow.create(kwargs['workflow_config'])
  File "/ingestion/src/metadata/ingestion/api/workflow.py", line 150, in create
    return cls(config)
  File "/ingestion/src/metadata/ingestion/api/workflow.py", line 68, in __init__
    self.source: Source = source_class.create(
  File "/ingestion/src/metadata/ingestion/source/mysql.py", line 31, in create
    config = MySQLConfig.parse_obj(config_dict)
  File "pydantic/main.py", line 578, in pydantic.main.BaseModel.parse_obj
  File "pydantic/main.py", line 406, in pydantic.main.BaseModel.__init__
pydantic.error_wrappers.ValidationError: 1 validation error for MySQLConfig
filter_pattern
  extra fields not permitted (type=value_error.extra)
[2022-01-20, 15:42:20 UTC] {taskinstance.py:1270} INFO - Marking task as FAILED. dag_id=my_ingest_3, task_id=my_ingest_3, execution_date=20220120T000500, start_date=20220120T154220, end_date=20220120T154220
[2022-01-20, 15:42:20 UTC] {standard_task_runner.py:88} ERROR - Failed to execute job 108 for task my_ingest_3
Traceback (most recent call last):
  File "/usr/local/lib/python3.9/site-packages/airflow/task/task_runner/standard_task_runner.py", line 85, in _start_by_fork
    args.func(args, dag=self.dag)
  File "/usr/local/lib/python3.9/site-packages/airflow/cli/cli_parser.py", line 48, in command
    return func(*args, **kwargs)
  File "/usr/local/lib/python3.9/site-packages/airflow/utils/cli.py", line 92, in wrapper
    return f(*args, **kwargs)
  File "/usr/local/lib/python3.9/site-packages/airflow/cli/commands/task_command.py", line 292, in task_run
    _run_task_by_selected_method(args, dag, ti)
  File "/usr/local/lib/python3.9/site-packages/airflow/cli/commands/task_command.py", line 107, in _run_task_by_selected_method
    _run_raw_task(args, ti)
  File "/usr/local/lib/python3.9/site-packages/airflow/cli/commands/task_command.py", line 180, in _run_raw_task
    ti._run_raw_task(
  File "/usr/local/lib/python3.9/site-packages/airflow/utils/session.py", line 70, in wrapper
    return func(*args, session=session, **kwargs)
  File "/usr/local/lib/python3.9/site-packages/airflow/models/taskinstance.py", line 1332, in _run_raw_task
    self._execute_task_with_callbacks(context)
  File "/usr/local/lib/python3.9/site-packages/airflow/models/taskinstance.py", line 1458, in _execute_task_with_callbacks
    result = self._execute_task(context, self.task)
  File "/usr/local/lib/python3.9/site-packages/airflow/models/taskinstance.py", line 1514, in _execute_task
    result = execute_callable(context=context)
  File "/usr/local/lib/python3.9/site-packages/airflow/operators/python.py", line 151, in execute
    return_value = self.execute_callable()
  File "/usr/local/lib/python3.9/site-packages/airflow/operators/python.py", line 162, in execute_callable
    return self.python_callable(*self.op_args, **self.op_kwargs)
  File "/airflow/dag_managed_operators/metadata_ingestion.py", line 5, in metadata_ingestion_workflow
    workflow = Workflow.create(kwargs['workflow_config'])
  File "/ingestion/src/metadata/ingestion/api/workflow.py", line 150, in create
    return cls(config)
  File "/ingestion/src/metadata/ingestion/api/workflow.py", line 68, in __init__
    self.source: Source = source_class.create(
  File "/ingestion/src/metadata/ingestion/source/mysql.py", line 31, in create
    config = MySQLConfig.parse_obj(config_dict)
  File "pydantic/main.py", line 578, in pydantic.main.BaseModel.parse_obj
  File "pydantic/main.py", line 406, in pydantic.main.BaseModel.__init__
pydantic.error_wrappers.ValidationError: 1 validation error for MySQLConfig
filter_pattern
  extra fields not permitted (type=value_error.extra)
[2022-01-20, 15:42:20 UTC] {local_task_job.py:154} INFO - Task exited with return code 1
[2022-01-20, 15:42:20 UTC] {local_task_job.py:264} INFO - 0 downstream tasks scheduled from follow-on schedule check

I'd have to guess that this is probably related to this previous bug I submitted:
https://github.com/open-metadata/OpenMetadata/issues/1826
But since this is done all through the UI, I'm not sure what I can do to get this to work without changing the code.

I exec'd into the openmetadata/ingestion docker container and changed my json config in /airflow/dag_generated_configs to be "table_filter_pattern" instead of "filter_pattern" and reran the DAG via the UI and it seems to be working now.


Implementation of event cards other event times in front page.

PT-1050 PT-1107.
NOTE: This needs new API https://github.com/City-of-Helsinki/palvelutarjotin/pull/191

NOTE: Tests fails because API is not published yet

The API changes are now merged and live! It seems like the loading indicator is too big 😞 . @Sartonon any ideas how to fix it?


Fix String value issues in grub_config

Ensure that Boolean values are converted to Strings
Ensure the String values have quotes around them if not already
present

Fixes #44, #45

@raphink Up for a review?

Hello.  I'm wondering when this will be merged to master and pushed to the forge?
Thank you
Tom


bug: 404 https://github.com/Atlastix/tap-redis

Closed by https://github.com/meltano/hub/pull/1304


Remove invalid Markdown backticks in std.path

To fix https://github.com/dlang/dmd/pull/8325

I'm not sure I understand, here's the diff from DAutoTest of the resulting HTML:
-    Note that on Windows, both the backslash (\) and the slash (/)
+    Note that on Windows, both the backslash (\) and the slash (/)
     are in principle valid directory separators.  This module treats them
     both on equal footing, but in cases where a new separator is
     added, a backslash will be used.  Furthermore, the buildNormalizedPath

BTW with a quick grep I found more instances of double-backticks.

I'm not sure I understand, here's the diff from DAutoTest of the resulting HTML:

Are you referring to my comment about using
$(D `\`)

instead? I mean that both slashes are supposed to be strings. Originally, they would have been
$(D `/`)

and
$(D `\`)

where the backticks make them strings where the backslash doesn't have to be escaped - e.g. $(D "\\"). However, someone came along and mass-replaced $(D ... ) with backslashes, which then screwed up any case where backslahes were used as string delimeters. The way to fix this is not to get rid of the "extra" backticks but to stop using backticks instead of $(D ...). If ddoc can't handle backtick strings in $(D ...) anymore, then that's a serious bug in ddoc that needs to be fixed.

BTW with a quick grep I found more instances of double-backticks.

Any case where backticks were used as string delimiters would have been screwed up by any attempt to mass-replace $(D ...) with backticks, so it doesn't surprise me at all if we ended up with double backticks in a number of places.

As the DAutoTest output above shows the consecutive backticks are not currently producing the desired output—they surround the slash with two empty code spans instead of wrapping it in a code span.
Markdown collapses consecutive backticks, so my upcoming markdown support will treat ``\`` and `\` identically and would thus produce the correct output. The problem in dlang/dmd#8325 would be fixed by the upcoming Markdown support for collapsing consecutive backticks. However the markdown branch doesn't yet support consecutive backticks but does support backslash escapes, and that caused the failure. It seems to me that this PR is the correct fix for dlang/dmd#8325, and also has the happy effect of producing the desired output in master.

Markdown collapses consecutive backticks, so my upcoming markdown support will treat \ and \ identically and would thus produce the correct output.

When you say that, do you mean that two backticks in a row are treated the same as one backtick or that two backticks in a row will result in the output having a single backtick? What we want here is to treat these as strings - the equivalent of "/" and "\\" except that it uses backticks for string delimiters instead of double quotes so that the escaping isn't necessary. If there's a clean way to do that with escaping the backticks rather than using $(D...), then fine, but these should be string literals with backticks in the final result.
Either way, whatever you do with markdown support, $(D...) with backticks in it still needs to treat them as backticks and not markdown, or it will break all of the existing inline code samples that use backticks for string literals.

Markdown collapses consecutive backticks, so my upcoming markdown support will treat ''\'' and '\' identically and would thus produce the correct output.

When you say that, do you mean that two backticks in a row are treated the same as one backtick or that two backticks in a row will result in the output having a single backtick? What we want here is to treat these as strings - the equivalent of "/" and "\" except that it uses backticks for string delimiters instead of double quotes so that the escaping isn't necessary. If there's a clean way to do that with escaping the backticks rather than using $(D...), then fine, but these should be string literals with backticks in the final result.

Yes, under Markdown multiple backticks in a row will be treated the same as a single backtick for creating a code span, provided the span is closed with the same number of backticks. If you want to output a backtick character you can backslash-escape it like \`.
Note that for the documentation this PR addresses in std.path it appears that the backticks are not currently displayed (see the red line in the DAutoTest output), and from the context of the paragraph I don't believe that the original author wanted a backtick character to display. Rather I believe they intended to make code spans that displayed a backslash and a forward slash.

Either way, whatever you do with markdown support, $(D...) with backticks in it still needs to treat them as backticks and not markdown, or it will break all of the existing inline code samples that use backticks for string literals.

So far as I can tell, $(D...) is not treated specially in ddoc processing—backticks inside it are treated just the same as backticks outside it. So today $(D `stuff in backticks`) would be double-wrapped by two code spans.

I don't believe that the original author wanted a backtick character to display. Rather I believe they intended to make code spans that displayed a backslash and a forward slash.

Nope. The backticks were supposed to be displayed. @CyberShadow changed it from
'\'

to
`\`

in #1267.
The PR description says: "Fixed a few char/string literals so they're in valid D syntax". A backslash on its own isn't valid D syntax. But a backslash in backticks is a string literal.
That was back in 2.063. The backticks were displayed then. DDoc only got backtick support with 2.067 (https://github.com/dlang/dmd/commit/26c5de42214c788ab42d96694a994c3eb8ae976a).

Nice research. In that case maybe it has been broken since 2.067?

In that case maybe it has been broken since 2.067?

Yearp.

So what's the consensus here: do we go with `/` or $(D `/`)?
I don't really mind and it seems to me to be a purely aesthetic choice. I just want one solution to get merged, s.t. the DMD PR is no longer blocked.

I don't really mind and it seems to me to be a purely aesthetic choice.

It's not. The intended result is that in the rendered documentation, a string literal is displayed. The contents of the backticks is not D source code, so it should not be highlighted as such. You broke it in #6391, so, please take the opportunity to fix it.
This should have been caught by DAutoTest's HTML diff before #6391 was merged, and to this day I still don't understand why it didn't work there, or why #6391 was merged before ensuring that the changes were correct.

Changed it to $(D `/`) then.

ping @wilzbach

Finally got around addressing the final nits. We should be good to go here now?


panda can't install a module in windows(appveyor)

Testing the module Auth::SCRAM on appveyor it seems it cannot find the PKCS5 module in the ecosystem.
panda installdeps .
resolve stage failed for Auth::SCRAM: Dependency PKCS5 is not present in the module ecosystem
  in method get-deps at C:\rakudo\share\perl6\site\sources\582CB7486602954A4601BDCE5A0EAC54B05DA58A (Panda) line 181
  in method resolve at C:\rakudo\share\perl6\site\sources\582CB7486602954A4601BDCE5A0EAC54B05DA58A (Panda) line 224
  in sub MAIN at C:\rakudo\share\perl6\site/resources/E0D978079BB5081DE986D058BB8AB08252F05CC8 line 28
  in block <unit> at C:\rakudo\share\perl6\site/resources/E0D978079BB5081DE986D058BB8AB08252F05CC8 line 152
Failure Summary

I am not sure but maybe it has something to do with filenames having only uppercase letters. On windows these files are converted to lower case if I recall it correctly.

Found the solution! Panda is not completely aware of all the modules when it is installed in the rakudo star distribution. I needed to add the command panda update just before the panda installdeps . command in the appveyor config file.


Implement delete_if_empty for StudyArea class in MODFLOW

@jsadler2 Should this be closed?

This was resolved yes. Closing


Bab parameter on amlSearchByNumber

searchByIDNumber(documentNumber = "", country = "", dob = "") {
        if (documentNumber.length < 5)
        {
            throw new Error("Document number should contain at least 5 characters.");
        }
        return this._callAPI({
            "documentnumber": documentnumber,  // <- error
            "country": country,
            "dob": dob
        });
    }

should be
searchByIDNumber(documentNumber = "", country = "", dob = ""){
        if (documentNumber.length < 5)
        {
            throw new Error("Document number should contain at least 5 characters.");
        }
        return this._callAPI({
            "documentnumber": documentNumber,
            "country": country,
            "dob": dob
        });
    }

@jeremyevith please take a look at this issue. We will need to use this feature

This issue has been fixed in 1.2.7.


Bluetooth: controller: Fix compile error when PHY update disabled

Fixed compile error when PHY update feature is disabled.
Signed-off-by: Vinayak Kariappa Chettimada<EMAIL_ADDRESS>

@Qbicz FYI

Codecov Report

Merging #9540 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #9540   +/-   ##
=======================================
  Coverage   52.17%   52.17%
=======================================
  Files         215      215
  Lines       26013    26013
  Branches     5594     5594
=======================================
  Hits        13572    13572
  Misses      10183    10183
  Partials     2258     2258

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a4d1e36...ba89764. Read the comment docs.


v1.6: install: Update the chart versions

All of these chart versions should be updated to the latest v1.6
release, that is v1.6.5.

This change is

@joestringer there is also requirements.yaml that only supports exact versions. I think we should update it too. Helm v3 replaced requirements.yaml with dependencies key in Chart.yaml (item number 3 here), which supports semver spec.

test-me-please


A way to generate automatically-numbered coords

It is great that xarray supports dimensions without coords, but sometimes I think it would be useful to be able to easily opt into autogenerated coords from 0 to n-1.  This can be useful to obtain DataArrays for pointwise indexing:
import xarray as xr
ds = xr.Dataset()
# a list of selected indices for each layer
ds['selected'] = (['layer', 'selected-i'], [
    [0, 1, 2],
    [1, 5, 3],
])

# normally, concatenation would drop layer data
print(xr.concat(ds['selected'], dim='selected-i'))
# <xarray.DataArray 'selected' (selected-i: 6)>
# array([0, 1, 2, 1, 5, 3])
# Dimensions without coordinates: selected-i

# if you generate coords from 0 to n-1 for layer, however, the resulting DataArray
# contains 'layer' indices for use in pointwise indexing
print(xr.concat(ds
                .assign_coords(layer=list(range(ds.sizes['layer'])))
                ['selected'], dim='selected-i'))
# <xarray.DataArray 'selected' (selected-i: 6)>
# array([0, 1, 2, 1, 5, 3])
# Coordinates:
#     layer    (selected-i) int64 0 0 0 1 1 1
# Dimensions without coordinates: selected-i

My issue with the above is that layer=list(range(ds.sizes['layer'])) is verbose and fails to be DRY. My thought for such an API is that xarray could maybe have a special constant for auto-assignment, usable in any method that takes input coords:
print(xr.concat(ds
                .assign_coords(layer=xr.AUTO)
                ['selected'], dim='selected-i'))

(Additionally, perhaps xr.AUTO could be a function/class, so that xr.AUTO(start) produces indices starting at start.)

If I understand correctly, instead of writing xr.Dataset({'foo': ('x', data)}, {'x': range(len(data))}), you want to be able to write something like xr.Dataset({'foo': ('x', data)}, {'x': xr.AUTO_NUMBER})?
I agree that it's sometimes convenient to automatically get coordinates 0 to n-1, but using range() is also pretty convenient, so I'm not sure we really need this shortcut.

I think this relates to the discussion about the evenly spaced coordinate (issue #1650).
I thought the possible API would be
xr.Dataset({'foo': ('x', data)}, {'x': slice(None)})

where it will construct a evenly spaced coordinate.
But I am not sure if we should add this API now or after #1650 is implemented.


Add test coverage for ILockingApi['getRank' | 'getLeaderboard']

Summary
This adds missing tests for ILockingApi['getRank' | 'getLeaderboard'] that were marked as TODO.
Changes

Add test coverage for ILockingApi['getRank]
Add test coverage for ILockingApi['getLeaderboard]

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.01%) to 93.688%

Files with Coverage Reduction
New Missed Lines
%

src/routes/transactions/entities/tests/human-description.builder.ts
1
90.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.01%

Covered Lines:
6367

Relevant Lines:
6570

💛  - Coveralls


Force the use of ubuntu-24.04

Description
ubuntu-latest is currently raising warnings.
For more details, see https://github.com/actions/runner-images/issues/10636
How has this been tested:

[ ] Covered by existing integration testing
[ ] Added integration testing to cover
[X] Verified all A/C passes

[ ] develop
[X] master
[ ] tag/other branch

[ ] Test environment

[ ] Shared Packet K8s cluster
[ ] New Packet K8s cluster
[ ] Kind cluster

[ ] Have not tested

it must be merged as it's a key fix and the workflows are passing well.


Seq item details

Following up on the discussion about #41, I used the documentation for List.map2 and List.map3 as a template for how to add example code.
These two documents deviate from the recommendation in the #41 discussion that examples should be in a new section, and this pull request follows their template. If desired, I'll be happy to update the pull request, though.

Should be live now with the sample embedded.


Speech to Text Python program

I can create a simple speech to text python program and can create a markdown to explain it so
The markdown will contain photos  for better understanding
And I can also create a Jupyter notebook for the same with the required code to implement the steps instructed in markdown

Can you please assign me this ??

Awesome, please make sure to include in your README how others can contribute to your project. Push your python program in "projects/vault-of-scripts" directory and the Juputer notebook in "projects/" directory to keep things organized!


feature(docs): add docs

Render markdown docs using sphinx
Starlight imports them automatically when exported to given folder

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:
:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.

Files
Coverage Δ

src/shipany/bot/actions/state_action/v1.py
100.00% <ø> (ø)

src/shipany/bot/web/events.py
100.00% <ø> (+27.27%)
:arrow_up:

src/shipany/bot/web/server.py
94.73% <ø> (ø)

... and 3 files with indirect coverage changes


Mohon tambah fitur rukiyatul hilal

Mohon tambakan rukiyatul hilal biar akurat @ahmedeltaher @sigitbn @

I can't understand this, could you please write in English?

I can't understand this, could you please write in English?

new moon (crescent) based location.
when new moon mean it is beginning new hijri month

Please add fitured calender hijri by rukiyatul hilal and wujudul hilal
mamad
Pada tanggal Jum, 26 Mar 2021 12:23, KadzalikLab @.***>
menulis:

I can't understand this, could you please write in English?
new moon (crescent) based location.
when new moon mean it is beginning new hijri month
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ahmedeltaher/Prayer-Times-Android-Azan/issues/25#issuecomment-807945326,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOQ5UC43E6YZQBWMRTAWJCTTFQK63ANCNFSM4XRF47DQ
.


Fix/attestation user infos

:tada: This PR is included in version 0.10.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Gradle's published Javadocs are in a format that the javadoc tool in modern JDKs can't properly link to

Current Behavior
Gradle's current published Javadocs (https://docs.gradle.org/8.4/javadoc/)

require HTML4 format fragments at the end of the links (e.g. Project.html#getName--),
but the supplemental files (element-list) trick the new, smart javadoc implementation into generating them in HTML5 format (e.g. Project.html#getName()),
so the deep links don't work properly.

Also, Gradle's Javadocs are missing the links to JDK built-in classes.
Expected Behavior

Gradle plugin authors using the latest JDKs should be able to generate Javadocs that correctly deep-link into Gradle's Javadocs.
Gradle's Javadocs should also have links to JDK built-in classes.

The possible solutions I see:

Ideally, start using Java 17's javadoc and generate modern HTML5, which would also fix the links to JDK classes

https://github.com/gradle/gradle/blob/v8.4.0/build-logic/documentation/src/main/groovy/gradlebuild/docs/GradleJavadocsPlugin.java#L106-L109

If the docs have to stay in HTML4 format, remove the element-list file, keeping only package-list, and use "offline linking" to add links to JDK built-in classes

This element-list file being there is what misleads the new, smart javadoc implementation – if there is an element-list, then it calls readElementList(in, urlpath, false, 0, false), otherwise it does the same with a true as the last parameter (isOldFormDoc)
https://github.com/gradle/gradle/blob/v8.4.0/build-logic/documentation/src/main/groovy/gradlebuild/docs/GradleJavadocsPlugin.java#L113-L126
https://github.com/morganstanley/gradle-plugin-application/blob/v2.0.1/build.gradle.kts#L152-L216 (my previous solution using offline linking)

Context (optional)

Required here: https://github.com/morganstanley/gradle-plugin-application/pull/13
Also relevant here: https://github.com/gradle/gradle/issues/18274#issuecomment-1825161020

Steps to Reproduce

Build a Gradle plugin using Java 17 toolchain (it can even be set to --release 8)
Generate Javadocs for it via javadoc -link 'https://docs.gradle.org/8.4/javadoc/'
Deep links to exact Gradle APIs won't work properly, because the URL fragment won't match the anchors in Gradle's Javadoc HTMLs

Reproduction: https://github.com/morganstanley/gradle-plugin-application/pull/13

E.g. build/docs/javadoc/com/ms/gradle/application/Application.html#finalizeProperties() has this:

See Also:
Property.finalizeValue()

Gradle version
8.4
Build scan URL (optional)
No response
Your Environment (optional)
No response

Thank you for providing a valid report.
The issue is in the backlog of the relevant team, but this area of Gradle is currently not a focus one, so it might take a while before a fix is made.

When fixing this we should make sure this is not a problem in the Gradle Javadoc task.


Cargo.toml workspace package fields

Hi,
A quite useful feature of cargo workspace is to share fields between crates, either packages or dependencies might particularly concern covector as it seems it's not able to resolve these:

./Cargo.toml:[workspace.dependencies]
anyhow = "1.0"

./crates/server/Cargo.toml[dependencies]
anyhow = { workspace = true }

Giving the following error on covector init in the root of my mono repo:
Cannot destructure property 'version' of 'parsedTOML.package' as it is undefined.

Effection:
  - task generator [127]
  - task generator function [9]
  - all count=61 generator function [8]
  - task generator [6]
  - task generator [5]
  - task generator [4]
  - start generator function [3]

Published in #266 🎉 . Closing, but feel free to reopen if you are still running into issues.


[BUG] There's a VM stuck in terminating after upgrade

Describe the bug

After finishing an upgrade from v1.1.1 to v1.1.2-rc1 there's a VM that is still showing up as terminating. You won't see it in the Harvester VM list because the namespace is harvester-system, but you can see it if you check via embedded Rancher in the explorer.
To Reproduce
Steps to reproduce the behavior:

Create a single node cluster with v1.1.1
Upgrade to v1.1.2
Finish upgrade
Check for VMs in harvester-system namespace
Expected behavior

The VM should finish terminating and delete after upgrade
Support bundle

support bundle still showing upgrade thing.zip
Environment

Harvester ISO version: v1.1.2-rc1
Rancher version: Single node docker v2.7.1
Underlying Infrastructure (e.g. Baremetal with Dell PowerEdge R630): libvirt single node Harvester VM with

Additional context
Add any other context about the problem here.
This was seen on a VM that had been prepped with all of the pre-upgrade tasks. I'm going to try to repro with the minimum setup.

update labels and change severity to 1 as this bug will affect cluster stability when scaling.
could be reproduced on Rancher both v2.7.1 and v2.6-5d91d1afdd7d88da6c0530080b16a5ad6dae8d17-head with Harvester v1.1.2-rc1 (upgraded from v1.1.0 or v1.1.1)

This should be caused by https://github.com/harvester/harvester/issues/2677, the VirtualMachine resource exists due to the wrangler.cattle.io/VMController.UnsetOwnerOfPVCs finalizer (VMI and virt-launcher pod doesn't exist).
kind: VirtualMachine
metadata:
  annotations:
    harvesterhci.io/removedPersistentVolumeClaims: upgrade-repo-hvst-upgrade-p9w6j-disk-0
    harvesterhci.io/vmRunStrategy: Always
    harvesterhci.io/volumeClaimTemplates: '[{"metadata":{"name":"upgrade-repo-hvst-upgrade-p9w6j-disk-0","creationTimestamp":"null","annotations":{"harvesterhci.io/imageId":"harvester-syste
m/harvester-iso-ffrk2"}},"spec":{"accessModes":["ReadWriteMany"],"resources":{"requests":{"storage":"10Gi"}},"storageClassName":"longhorn-harvester-iso-ffrk2","volumeMode":"Block"},"status"
:{}}]'
    kubevirt.io/latest-observed-api-version: v1
    kubevirt.io/storage-observed-api-version: v1alpha3
    network.harvesterhci.io/ips: '[]'
    sim.harvesterhci.io/creationTimestamp: "2023-02-22T02:04:05Z"
  creationTimestamp: "2023-02-22T02:04:05Z"
  finalizers:
  - wrangler.cattle.io/VMController.UnsetOwnerOfPVCs
  generation: 1

Please help see if this still happens after v1.1.2-rc2.

@noahgildersleeve If you still have the env, please see if removing the finalizer removes the VM. Thanks!

should be fixed by: https://github.com/harvester/harvester/pull/3508

@noahgildersleeve We can test this with master-head ISO or wait for v1.1.2-rc2

Verified fixed on v1.1.2-rc3. Close this issue.
Result

The upgrade-repo vm have been deleted after upgrade from v1.1.1 to v1.1.2-rc3

We can delete the existing VM after upgrade on singe node, two nodes and four nodes airgapped upgrade test.

Test Information

Test Environment: 1, 2 and 4 nodes Harvester on kvm and bare machines
Harvester version: v1.1.2-rc3

Verify Steps

Provision a single or multi nodes Harvester cluster
Provision an RKE2 guest cluster on it
Create a new VM
offline upgrade to v1.1.2-rc3
Start the off VM
Check the VM state after upgrade
Delete the existing VM


apply POM change to fix issue with npm install on windows

thanks to @grkvlt for this fix

LGTM, good to merge.


[DO NOT MERGE] chore: landing page, banner, nav updates

Homepage updates:

new section for differential expression
re-ordering of sections
new image for explorer section

Nav updates

removing "beta" label from CellGuide link
adding DE link with "new" label

Banner added

banner added to

@sethfeingold I added a DO NOT MERGE for this PR, so we don't accidentally merge this into main before the Explorer side releases the feature at launch time 👌
Thank you!


Games can not be launched after closing GoG Galaxy

(As version 2.4 isnt working for me I use 2.3 even after doing all of the steps carefully a few times) After the plugin is installed and it works as expected I fully close GoG Galaxy. After opening it all of the plugin's games are shown as "Install" in grey and the only way to fix it is to connect it again in the setting.

Thanks for your help!

I think this is the same issue as #10

Yeah it is the same issue so I'll leave close this one but the other one (#10) will remain open.


feat(backups): add support for local, dropbox and gdrive strategies for backups

Description:
resolves #1971
resolves #2214
resolves #2215

How Has This Been Tested?
Manually

Screenshots (if appropriate):

Types of changes:
New feature

Checklist:

[x] My code follows the code style of this project.
[x] I have reviewed and updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes where needed.
[ ] All new and existing tests passed.
[x] My commits have been squashed into a concise set of changes.

Coverage decreased (-0.3%) to 20.175% when pulling d5fbef962da12b431057a1ce01f17e258aab6fb6 on korhaliv:feat/scb-dropbox into 26aa66f6956b63daeab49f66b3d835f0b87b8f67 on LN-Zap:next.

@mrfelton csp for prod updated


Support application/x-www-form-urlencoded

Handle content-type: application/x-www-form-urlencoded with https://github.com/nox/serde_urlencoded as suggest by @carllerche on Gitter.

As an initial step, I would add a field here that is basically is_json: bool and if false, use serde_urlencoded::from_bytes to decode.
Eventually, arbitrary deserialization formats will be supported, but as an initial step, hard coding json vs. form-urlencoded is fine.
And yes, when the future is first created, it needs to check if the content type is "application/json" or form encoded. This would happen here: https://github.com/carllerche/tower-web/blob/2fb07a75272a120f0bffc165961b8d5d9c8c5fb1/src/extract/serde.rs#L101


Can't hide drag-handle icon

I can't hide drag-handle icon when using *ngIf
The querySelector will not find an element with dragHandle Class:
https://github.com/ObaidUrRehman/ng2-drag-drop/blob/968ebbac52747c73b54f21bf09eea48322670e10/src/directives/draggable.directive.ts#L210
"ng2-drag-drop": "^2.9.2",
dragElement will be null here:
https://github.com/ObaidUrRehman/ng2-drag-drop/blob/968ebbac52747c73b54f21bf09eea48322670e10/src/directives/draggable.directive.ts#L199
Stacktrace:
ERROR TypeError: Cannot read property 'classList' of null
    at Function.webpackJsonp.../../../../ng2-drag-drop/src/shared/dom-helper.js.DomHelper.getElementWithValidClassList (dom-helper.js:62)
    at Function.webpackJsonp.../../../../ng2-drag-drop/src/shared/dom-helper.js.DomHelper.addClass (dom-helper.js:38)
    at Draggable.webpackJsonp.../../../../ng2-drag-drop/src/directives/draggable.directive.js.Draggable.applyDragHandleClass (draggable.directive.js:148)
    at Draggable.set [as dragEnabled] (draggable.directive.js:78)
    at updateProp (core.es5.js:11122)
    at checkAndUpdateDirectiveInline (core.es5.js:10822)
    at checkAndUpdateNodeInline (core.es5.js:12364)
    at checkAndUpdateNode (core.es5.js:12303)
    at debugCheckAndUpdateNode (core.es5.js:13167)
    at debugCheckDirectivesFn (core.es5.js:13108)

Example:

someOtherStuff

		<mat-icon class="drag-handle md-24" aria-label="Move Card">open_with</mat-icon>

someOtherStuff

@amperboy you are hiding the drag handle element instead of using the dragEnabled property on the draggable element. Setting this property sets/removes the drag handle cursor on the drag element.
Anyway, this is a bug and needs to be fixed. It shouldn't throw an error if the element is not found.

@ObaidUrRehman I also use dragEnabled Attribute to disable the dragability. But my stakeholder also want to hide the icon when dragging a component is disabled. As workaround I'm using the [hidden] directive.

Ok, I understand your use case. Will fix
On Thu, Oct 12, 2017 at 11:50 AM, Marco<EMAIL_ADDRESS>wrote:

@ObaidUrRehman https://github.com/obaidurrehman I also use dragEnabled
Attribute to disable the dragability. But my stakeholder also want to hide
the icon when dragging a component is disabled. As workaround I'm using the
[hidden] directive.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ObaidUrRehman/ng2-drag-drop/issues/100#issuecomment-336037075,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABplrButQ2I08Ija6Ox-cMgIiMc7iyJjks5srbbDgaJpZM4P18z0
.

Fixed in v3.0.1